Hello Java developers, my name is Matt Ravel and today I'd like to show you how to develop Microfront ends for Java microservices. Let's get it up So this screencast is based on a blog post I wrote called micro front ends for Java microservices read through the blog post right to learn all about micro front ends what they can do and About Jay hipster and all that and you know these are the different steps But in the repository for this blog post there's a demo dot a doc Basically a demo script that I created that is written in ASCII doctor and thanks to my handy-dandy ASCII doctor plug-in it renders nicely and it's the same thing as the blog post But it's just a condensed set of instructions so I can do this screencast for you and it all works quite nicely So we're gonna use Jay hipster for this and you might be wondering you know What is Jay hipster? Well, if you go to Jay hipster tech you can learn more but in summary and it's very basic When it started it was just an application generator that generated a spring back end and an angular jazz front end So that's how long it's been around since like 2014 before spring boot was even around and then when spring boot came out We you know adopted that as the back end framework and then over the years we've added Angular Not angular jazz right angular to and above is angular and then also react and view this set of instructions We'll guide us through everything and we're gonna basically build a gateway with spring cloud gateway And then we'll build a blog at microservice that has tags and posts and Entries and then a store microservice which just has products and you can upload images for those products So each app will also contain a micro front end and the reason for this is Jay hipsters default microservices Architecture actually generates a monolith on the gateway and the whole point of microservices is to kind of make everything Independently deployable right you should be able to work on the blog application and not have to redeploy the gateway And so up until we had micro front end support if you modified You know fields or entities and the blog microservice and it required UI changes Well, then you had to deploy the blog and the gateway and that's kind of violates the whole principle microservices So micro front ends allow you to package the front end for the blog with the blog artifact And so that means you can just deploy that and then the gateway will suck in the blog UI at runtime So it's pretty slick You'll need Java 11 node 16 Docker desktop and Jay hipster to complete this tutorial So I'm just gonna go ahead and put that on the right there and make sure I have all those installed So Java 17. Yeah. Yeah, it'll work and node. I do know that node 18 has issues with Jay hipster 7 So make sure and use node 16 and then Docker I Have running and Jay hipster. I'll just go ahead and install that just in case I'm using the wrong version. So Jay hipster 7 7 9 3 is the latest version. And if you use 7 9 4 If that happens to come out then everything should work there too. And so the table of contents here We're going to build, you know, Java microservices of spring boot and webflux So I'm going to use webflux for everything the gateway is going to be webflux regardless Because spring cloud gateway only supports webflux at this point. It doesn't support spring mvc And then we're going to run our microservices and then I'll show you how the micro front ends work And how you can get zero turnaround, which is awesome when you're working on UIs and then we'll build And run it with Docker will switch identity providers because it ships with key code by default And then we'll deploy it with Kubernetes. I don't know if I'll do that because it takes a while But then we'll have fun doing it. So I've installed Jay hipster 7 9 3 there. Let's just make sure Yep, and then we'll create a new directory. I'll do this in my downloads directory I got some stuff in there 8 micro front ends Jay hipster Now clear that out and we'll download the reactive microservices jdl that I created That's probably been like a year and a half and we'll compare that with the micro front ends version So we'll start with Jay hipster download reactive ms.jdl and this downloads it from a jdl samples repository So you can see that right there. That's on github. And then if we did it for micro front ends It'll download that one too. And then if you have the intelligent command line launcher installed you can do idea diff one Versus the other And you can see here the major difference is first of all i'm using react That's why i'm wearing the react shirt and then service discovery type is console The reason for that is we're going to make that the default in j hipster 8 And then instead of you know specifying the entities that'll show up in the gateway We're going to use micro front ends and say hey those micro front ends pull them from the blog and the store And then we do have to specify the client frameworks for the microservices now So has to have a react if you want to use cypress for testing that you have to specify that as well And then i changed the service discovery type and beyond that there's you know, not a whole lot of difference down here I don't need those microservice specifications anymore You know what goes where and i did add a couple new things for deployment with the docker and with kubernetes So otherwise, you know pretty much the same just subtle differences to support micro front ends And so there is this j hipster jdl plugin created by a guy at jetbrains It's pretty awesome. So if you want to actually modify, you know jdl in your ide and get co-completion And you know telling you when your syntax is wrong and everything I highly recommend that you can see there It's got five stars only four votes But you know I was definitely one of them and then to generate a microservices architecture with micro front-end support You run the following command. So j hipster jdl that reactive micro front ends jdl And then what i'm going to do is use mono repository And the reason for this is just demo purposes because if I didn't use it It would create a git repo for each microservice, which is probably how you want to do things in production It just makes it so it's one repo this workspaces command Makes it so mpm can run commands from the top level directory and applies to all the other directories Or the other projects. So I'm going to start with that And then while that's running you can see over here If you did want to change from react to view if you want to, you know, try this out Certainly use this demo script you can override the defaults in that jdl file with client dash framework, you know angular Or view and the reason for angular x is at one point, you know, we need to distinguish between angular js and angular and It's just legacy. So we will be defaulting to angular or changing that to angular for J hipster eight And so once that process is completed We'll go into the gateway directory and start key cloak and console using docker compose And you know what we could probably get started on that now. So go into gateway And start up key cloak.  So it has all these aliases if you see jh there It's got a whole bunch of them So that's how I start up key cloak and then I can start up console as well jh console up And you know, those aliases are the same as these commands right over here Oh, well console loader config. I'm on an m1 max. And so that's why you know, there's that warning there But everything should still work and if we were to you know, open up docker desktop here You can see them running there. So that should be working And then if you're open up, you know, local host 8500 that's where console is running So that's all good to go And so we can start with gradle W to start that gateway and you can also use npm run app start But you know one command shorter than the other So I don't know I want to use one over the other But if you can't remember whether you know created the app with uh, maybe on a gradle Then that might be a use for that npm app start command And so we can open the root directory in intelligent And this will allow us to kind of show how everything's working We have obviously the gateway here and we have the blog here But let's look at the gateway first because that's got the micro front end setting for webpack uses module federation right From webpack. So if we were to go into this webpack micro front end file here We can see that uses a module federation plugin and the remotes are blog and store And it expects to be a little remotely, you know load those and it's got a bunch of shared objects as well Between you know this gateway and you know that microservice so currently we don't allow you to mix and match right you can't have like you know React in one microservice and view and another because these shared You know artifacts aren't going to play well together if you do something like that So currently we expect you to use the same client framework for each of your microservices And so that's you know the gateway that's sucking those in and then if we were to go to like, you know the blog and look at its webpack configuration You'll see that it specifies also the module federation plugin, but then it Basically exposes the entity's menu and the entity's route. So if we were to look at this file You can see it's got all the entities in there Right and then if we look at routes That's got the routes that'll be sucked into the gateway as well and allow everything to work So that's how the micro front ends are configured. Put that on the right there And see if everything's running Looks like it is so we can exit out of that one exit out of that one and open up local host 8080 Make that a bit bigger And then if we click sign in it'll redirect us to key cloak And we can log in And of course google chrome is smart enough to be like hey admin admin. What are you doing?   So if you're looking the console here You can probably see you know 404 when it tried to actually grab those So now we'll want to start the let's say the blog microservice And this does depend on neo4j. I believe it is so jh neo4j up And then start it up All right, now that that blog is up and running we can refresh the page And there it is right. So if we want to create a new post we could be like first post which is always fun And uh some content And we don't have any blog so we can just save it and it's all working right it's talking to that database correctly So, you know, we could do the same for the store. Let's go back to our instructions and see what I'm supposed to do Yep, open the store and you'll see there's also this uh mpm run docker db up command Which can be handy if you don't know if you're using like mongo or neo4j or postgres or whatnot So if we go to store and then mpm run docker db up We're using mongo in this instance. So it's it's actually pulling that one down since I didn't have it installed locally And while that's going I should make sure and let you know that I think it's uh It's in our preferences here in docker You probably have to up your resources, right? I think the defaults are maybe a few cpus and I've upped it to six And then the memory is the big one because you know, we got a lot going on here a lot of containers And uh, so you might have to bump those up to get everything working What'll happen if you don't is uh, you know things just won't start because there's not enough memory Okay, so long goes up and now we can start it with gradle If we were to look at console You can see that The blog it doesn't like it what happened over here Source was empty. Uh, this is something new that I've seen where uh the health check for a neo4j doesn't work So we might have to comment that out But I think it's you know the app works, right? Like it's just uh something with that neo4j reactive health indicator It works fine when you're using spring mvc We saw this upgrading j hipster to spring boot three, but I didn't expect it to happen with spring boot 275 because what we're using everything still works. It's just like a false failure Or a problem with console. Uh, if we refresh here, um the store Come on. There it is. So the store, you know works and now if we were to refresh this one Then our entities are there for the store. So we could create a new project or product Um, I like beer. So let's uh, choose a file there And there we go And now we're you know saving to that mongo db repository. So slick. That's all working And so now I'm going to show you how to use zero turnaround All right development that sparks joy because why wouldn't you want to have joy sparked in your life in the gateway? All right, that's up here We can run MPM start and this will open up a development server Running webpack on port 9000 and so basically any changes you make will immediately be available here So that's using browser sync and so we can modify Gateway source main web app the home tsx to basically make a quick change So let's make sure and grab this we're going to put it below the h2 And then we're going to see this right here And we're going to go over here find that home dot tsx because we use typescript for everything and Jay hipster. So in the gateway look for that h2 Right down here Add it right here So I can just paste that in look you there. Hi. I'm a quick at it. So all that's working looks nice And uh, you'll see, you know, everything just happens right away. So pretty slick if we remove it It'll get removed right away too So nice zero turnaround when you're working on, you know, specific apps in this microservices environment But you do have to do the MPM start for them to get that, you know, quick turnaround And so if you wanted to get in the store directory, for instance, that's the one down here We can do MPM start as well And that'll start up on a different port So there's no port conflicts. Jay hipster is smart enough and then if we were to, you know, open this up a bit And go into product, right? This is you'll notice it doesn't have all the entities in here So what it allows you to do is just work on that specific microservice So it's still got the shell and we do require the gateway to be running The reason for that is just we didn't want to like incorporate Authentication and all that logic into each microservice. So it's just like a bare shell And then if you need to, you know, do authentication, whatever it does that on the gateway and comes back here So that's why we did it that way. It was just easier and you know, why complicate things And so in the wrapper around the div and product dot tsx, we can change it to have a background color So we want to see that, right? This otherwise you will change before you can command tab back to your browser. So BG info got to remember that class name BG info And then product tsx go over here Find it product tsx there it is Now we're looking for a row Or a div right there we go Boom Yeah, look at that. So if you were to go back to the gateway though And look here or even here right on 9000 and go to product It's not here because this one is not, you know, realizing what's changed on that UI. So It's still just isolated to whatever you're doing with that npm start command in each of those microservices And then the back end has Zero turnaround abilities to thanks to spring boot dev tools So if you modify the back end class and recompile it spring boot will reload that as well So it's pretty slick. I'm not going to show this and as far as looking under the hood of micro front ends We already talked about that, you know, looking at those webpack micro front end.js files And both of the gateway and in the blog All right, now what I'd like to do is show it all running in docker. So we're going to stop, you know, all these Various commands exit exit And we have all these docker images running.  So because of that, I created this whole docker compose directory with everything in it So we can open that up and check it out And there's a central server configuration, which has the application configuration that spreads or gets distributed to all the microservices So we're going to build docker images for each application By running this command from the root So that'll work if you're on a normal intel device, but I'm on apple silicon. So I actually have to use this command npm run docker arm 64 And so you can do npm run if you want to see like all the commands, right that are available So you can see you can build them for each individual one from the top level Or you can even go into each one and build them that way But because I use the work spaces command, that's why I can do everything from the top level so npm run And all that's running I can mention that to make key cloak work in this environment You do have to modify your etsy host file to have a mapping from You know one two seven zero zero one to key cloak And that's because how docker traditionally works is it communicates like from the blog app to neo4j Using a dns name that docker recognized. So it's like neo4j blog or something like that And that'll works because it's never exposed to the ui But in this case when you log in with key cloak, it's going to redirect and show key cloak in the browser So I haven't figured out a better solution This one seems pretty easy to do and it works. So You'll need to do that or it just will basically give you a you know host not found when it does that redirect So now that all those docker images are created we can start it up with docker compose up Or in the wrong directory so docker compose And so if you added dash d then you would you know not see any of this and you'd have to use docker desktop to see All the logs happening I like the prettiness of the logs and all the different colors and So that's why I did it this way and then you can kind of see when things are starting up So if you did open docker compose you can kind of or docker desktop you can see the individual ones So, you know one thing in here is You can see it kind of happening I'm not sure where the log was. It was easier the last time I used this so But basically there is a there's a pause, right? It's like waiting 60 seconds Well the gateway's already up. Maybe my machine machine's faster than normal That one's still going. I don't know. Well, let's use uh Old console to find out where are we at? So it looks like things are up and running We started an issue with neo4j, but like I said, that's been an issue with neo4j and source was empty even though it's up So the way you can do I'm going to show you how to fix this real quick I'll close that one if you go into the blog And you go into application Config right here, and you go into like help help um Yeah, management endpoint help you can go down here and do neo4j Enabled false So that's like actuators uh neo4j health check that's not working. Um, so I don't know why but you know hasn't been for a bit now But everything should be running. So if we want to go to, you know, local host 8080 here You can log in go to key cloak, you know, that's running. You can see it's up in our browser there and yes, cool. Sorry And uh, you know, we could do a post create a new post Howdy Happy Friday. It's Friday where I am December night there So that's all working Product right you can see that that change we made in the product is is in there and then you know nothing on the home So, you know, everything's working from that perspective and now what we could do is switch identity provider So we can we can close all these with a simple c I'll make this a little more visible here And so first we're going to register a regular web application on oszero So go to oszero.com Put this over here back to our instructions So log in I already have an account so Continue with github here Next one password it's pretty slick and then remember this for 30 days Oh, it doesn't like it try another method Security key got my ube key right here Remember for 30 days click it So if I go to applications, I can create a new application And we'll call it micro front ends And make it a regular web application click create And then we'll need to switch to the setting tabs and configure our application settings So the most important thing is a couple callbacks This one right here. So spring security expects a callback URL like this Typically, it's like, you know, right here, it's like oszero or octa or something like that The reason we use oidc is because we use the same callback URL whether using kiko or octa or oszero And then We'll allow a logout URL of localhost 8080 So those are the only things we need to do there and then we can save it And then in the roles section Create a new role So I think that's under what users security And we'll click the link Roles so we already have those in there There they are into user management And then a new user Which I already have and let's look at this user here They've already been assigned those roles right role user and role admin So you want to create a new user because you don't use you know the user you use to create, you know Your management account. So if you were to create a new one Let's just go here and create a user Or let me show you you create, you know email password or pre-password and then once you create it There is a next section. So let's see. I probably have an email. I haven't used here You'll notice here that it's pending the email registration, right? So one thing you have to do is is go to your email or set email as verified So otherwise like this won't work and then you go to the roles And you know assign those new roles there And then the next thing you need to do is add the groups claim or these groups, right role user role admin To the id token that's returned from out zero. So that's under actions flows And select login So we don't need a tour here. We just want to add a new action. So we're going to install a custom action We're going to call it add roles So create action Add roles And we're going to set it to uh, you know post login and node 16 And then we're going to grab this code here And you're going to see that changes the namespace to j hipster.tech And once they're authorized it adds their preferred username as an email And custom claim in the id token and the access token So we'll save that And deploy it and now if we go to the login flow We can drag it in there There we are apply it And then we can edit the docker compose application dot yml and append this yaml block so we can actually You know specify these os zero settings. So the cool thing is that you know, basically Bring security allows us to just override the defaults for key cloak and it'll start using, you know, a different identity provider. So If we go into that docker compose directory Right in central server config here And we don't even need these anymore And we need the os zero domain which we have back in our browser here That's this guy Well, let's get it from our app. So we make sure and not Mess it up That's the domain Put it right there Then you'll need it down here and make sure and have that trailing slash on there and then The client id the client secret And this audience here is created by apis And so by default there won't be an api But you can see there is one right here for me or go into there. It might be able to see the full URL Yeah, you can see v2. So you do have to create one. It doesn't create one by default But if you do it will be basically api v2 And so now we can stop all our docker containers, which we already did Docker ps nothing's running And we can start with docker compose up again, but make sure we save this file, right? I can check console to see if things are starting up Maybe they're already done. All right, let's try it. We'll close 8080 Now if we click sign in Should redirect os zero There we are except Authorizing the app and it comes back and now we're logged in with our os zero account. So, you know We can see all of our posts that we created earlier Um, or we could add a new one, right? We do like beer $10 in some states There we are You can also use octa for your identity provider if you're developing apps or apis and you want to add authentication to it We recommend you use os zero first It's just more developer friendly and you don't have to talk to any sales people You can just as you scale up you can pay with credit card, which is nice But for octa you can see j hipster's documentation It's very similar, but I recommend using the cli and uh, you know, you can actually do Whereas it octa octa apps create j hipster and it'll do everything for you So i'm trying to get that same sort of ability with os zero cli That's why I showed you through the web interface right now is because uh, the cli will just create a regular web app for you It won't actually do the actions for you won't do the roles for you But octa cli will actually create all that for you. So that's pretty slick and then you just configure it You know similarly down here and then if you want to deploy with kubernetes There is you know all of that in there. It did create a kubernetes folder For us. So if we were to go to you know, the kubernetes directory outside of docker compose You can see it's got all the files in there and you can just run kubectl apply dash f and it'll deploy To whatever, you know namespace you provide it. So this is what I specified You also you always should use, you know a different namespace in the default because then you can blow it away if you need to And we're clustering the uh, mongo Uh db for the store there and then everything else is just prompts that you normally get if you were to actually You could create, you know make dir k8s and cd into it and If you run J hipster kubernetes It'll prompt you for these various values and these are what I chose. So I didn't have to you know run a generator So I hope you enjoyed this demo and it helped you how to better, you know deploy your microservices with j hipster Use micro front ends if you can because then your microservices can be independently deployable Instead of having a monolith ui on the gateway So you can find the code on github At off zero micro front ends j hipster example And of course the blog post is on the os zero blog there Micro front ends for java microservices if you liked this video Please follow me on twitter. I'm at m rable My team is at octadev and of course Subscribe to our youtube channel so you can watch more videos like this that will brighten your day and make you a better developer Thanks. Cheers


Pallar warrior. Yeah, bit to the left. I need to use snakes on the sky somehow. I'm trying to... Keep reliant. Scatter. PS it. Pallar into trap. Charge me. MC warrior. Won't get it. He can kill me here. MC warrior. Kick on me. Got the playoff. Sacrifice. Got it. I'm trying to see now. Scatter. Trap. I'm trying to get into trap. Fair. I'm trying to kill him. Dead. I don't know why. Should be winning. Now the warrior Pallar. I saw him. I'm trying to kill him. I'm seeing him. I'm going to see him. Jump him down. Trap. He's blocking stone. I'm trying to kill him. Fairing Pallar. I'm trying to kill him. Maybe I can fit. No, I can't get it. I'm trying to kill him.  Got it. I'm trying to start playing second game. Maybe I'm dead here. Maybe I'm dead here. I'm going to scatter. I'm going to scatter. Dead here. Nice charge.  Literally behind the pool. I think charge is the most bugged out of every spell. In terms of line. The pathing is so fucked. If it's Pallar warrior we don't care. We don't care. We can win, we can win, I believe.  I'm going to take some distance. I have snake here. If you charge me it's good. Nice, I'm going in. I'm pushing this wall. I'm going to shrink it hard to influence them. Got a sack. Nice. Second sack. I'm moving the warrior away from you. Yeah, I'm burning Pallar. He's running away. He's not doing anything. Yeah. Can you move out of that? I can do it. Yeah, in a second. Hit my kit. I got hard.  You're CC. He might be going to use this one. Pallar shrink it. I think it is. Getting the freedom. I'm moving Pallar. I'm moving this guy. Yeah, I'll PSG. Fuck. I couldn't fear in time. One second cooling. Maybe I should be burning Pallar. Pallar's fed. I think you should be using slow trap out there. By the way, if you're going to not CC. I'm second boost now. Hitting you. I can choke. Burning Pallar. Can you silence him? Yeah, I'm burning. Fear. I have no mana. Pallar's zoom, but you're low. Drinking. Shield you. If you're not pushing and you're keeping him far. In this room. Put the frost trap. You can even scatter frost trap. We're not getting scatters on Pallar anyway. I zone Pallar. You just hyper pump worry.  I swear to God. Going in. Going to get a hodge. I'll set this. Both charges used. Yeah, I'm pushing first now. My snakes won't survive. Sacrifice. I can pick me if you want. Fear. Just like it. I'm going open field. I'm trying to see if you can spot me. It's fine too. I think it's a hodge. No fear. Can you freedom? Yeah, I do. I need the freedom sooner. We don't have enough pressure to get him off. This is the problem.  I push in. I get fear on Pallar.  It is weird. I don't remember Warriors ever doing this much damage in original Wrath.  It's almost impossible to MC the warrior against Warrior Pallar. You have to literally stand and cast it for 10 seconds or so to actually get it. You have to go for a kick, you have to go for a reflect, and you have to go for a kick again most likely. Probably a resist at some point. It's just not reliable. We lost 200mmR. Just from dumbass losses and pet bug related losses.  Pushing. You use second charge on me. Trying to get the sack, didn't get it. Fearing, resist. One of the Warriors eyes is facing me. The other one is somewhere over here. I can fear in 9. I can fear Pallar soon. I'm going away. I'm actually going to stay on Pillar. I can't cross the whole map. There's no way. Can you CC Pallar?  And so did the Pallar, so they died. But like Pallar didn't... I don't get it. Didn't use bubble. I think he used both sacks. He definitely used single target sack. Resisted a fear.  Just stood there tanking. No wool, nothing. I don't get it.


وأقول في القرآن ما جاءت به آياته فهو الكاريم المنزاله وأقول قال الله جل جلاله والمصطف الهدي ولا أتأوله الحمد لله رب العالمين له الحمد الحسن والثناء الجميل وأشدوا الله إلا الله وحده لا شريك له يقول الحق وهو يهدي سبيل وأشدوا أن محمد عبده ورسوله صلى الله عليه وعليه وعليه وأصحابه والتابعين لهم بإحسان إلى يوم الدين أما بعد إن شاء الله تعالى في هذه المنزل أريد أن أتحدث عن الملل من مجالسي ذكر المجالسي يصبح بورد يجب أن يقوم بسيطة وفتاق إذا كان في حلقه أو في سرق المنزل إذا كان يجب أن يجب أن يتحدث في بعض المنزل ويجب أن يتحدث إلى ألقا أو أدرس يجب أن يتحدث ويجب أن يتحدث وعدم الملل but the person doesn't get tired من مجالسي لغوي إذا كان يتحدث في مكان where he's watching a movie for example he's got his laptop in front of him and he's watching a movie or he's watching a series he doesn't get bored or tired of it but he gets tired of listening to a lecture and this really shows a bightful e-man that the weak e-man of this individual is very weak because Allah described the people of true e-man whose e-man is rooted and is grounded الله تعالى يسرب بعدهم إنما المؤمنون الذين إذا ذكر الله وجلت قلوبهم وإذا تليت عليهم آيات وزادتهم إيمانا وعلى ربهم يتوكلون الله سرب about the believers that the believers are إنما المؤمنون الذين إذا ذكر الله when Allah is mentioned they are captivated by the mentioning of Allah الله تعالى's words and also the also the Hadith إنما المؤمنون الذين إذا ذكر الله when Allah is mentioned وجلت قلوبهم their hearts it trembles it moves they get affected by the remembrance of Allah and the mentioning of Allah this is the type of people that the believers are and the ayah of Allah إنما المؤمنون الذين are nothing except because this is it's Hassar it's called Al-Hassar Al-Hassar in Arabic language is إثبات الحكمي للمدكور ونفع عن معده it's restricting something to a particular thing and negating it from everybody and anything else you're saying here إنما المؤمنون الذين أفضلون are the only ones that what who when Allah is mentioned سبحانه وتعالى وجلت قلوبهم their hearts move so the people of Iman when they go to Majalis with Zikr the circles of knowledge the places where the deen of Allah has spoken about سبحانه وتعالى they get carried away time they don't even know how long they've been sitting there for and from the beginning to the end of focus they're benefiting whereas people have a weak Iman when they watch a series online or they watch a I mean a movie they get carried away they get carried away and so it's a contradiction both of these situations you're sitting down how is it that one situation you're really focused and the other situation you're not focused it's a contradiction here but then it goes back to something it comes from something which is the Iman of this person is weak so they go to the Majalis with Zikr and you see them يوني and they get carried away and they get carried away and they get carried away and you see them يعني يعني looking at their time hoping for how long how long is this going to take when it comes to مجالس اللغو you see them straight away eyes are open يعني the movie they're watching it they might even spend the whole night watching it سبحان الله I remember parents coming to me in this country in the UAE complaining to me about their children my child watches series after series back to back he starts a series and then he's watching one series after the other after the other back to back he might spend the whole entire day not moving from his place just watching يعني how could someone just sit there and just gaze at a screen like that watching something if he's with friends again or he's talking to his friends or he's laughing with his friends and they're having conversations he's very focused and he's alert he doesn't get tired he can spend the whole night talking to his friends like when it comes to the remembrance of Allah if he goes to حالقة درس he's tired he can't do it so this is a contradiction that I want إن شاء الله all of us to look into think about it and the whole idea for this contradiction series brothers and sisters is that we get out of this situation we realize something is not right why are we like this here and not here that's the whole aim and objective behind these series إن شاء الله إن شاء الله ما شاء الله لأخرى المستخدمين ، وإنظروا أن تكون هناك كثير من التحديات التي يمكنك أن تنتهي لك على يوم التحديات إذا كنت تفعل ذلك مع فرصة سعيدة للتحديات الدينة والله. ستكون تحديد من كل شخص الذي يفعل من one of our videos as a result of your like or subscribe. That's an easy two-second action that you definitely don't want to miss out on. Do it now, click like and subscribe and don't forget to make that intention.


From around the globe, it's theCUBE with coverage of KubeCon and CloudNativeCon Europe 2020 virtual. Brought to you by Red Hat, the CloudNative Computing Foundation and ecosystem partners. Hi and welcome back to theCUBE's coverage of KubeCon CloudNativeCon Europe 2020's virtual event. I'm Stu Miniman and happy to welcome back to the program two of our CUBE alumni. We're going to be talking about storage in this Kubernetes and container world. First of all, we have Sam Warner. He is the vice president of storage offering management at IBM and joining him is Brent Compton, senior director of storage and data architecture at Red Hat. Sam and Brent, thank you for joining us and we get to really dig in as to the kind of the combined IBM and Red Hat activity in this space. Of course, both companies very active in the space ahead of the acquisition. And so excited to hear about what's going forward. Sam, maybe if we could start with you as the TUP, both Red Hat and IBM have had their conferences this year. We've heard quite a bit about how Red Hat, the solutions they've offered, the open source activity is really a foundational layer for much of what IBM's doing. When it comes to storage, what does that mean today? First of all, I'm really excited to be virtually at KubeCon this year. And I'm also really excited to be with my colleague Brent from Red Hat. This is I think the first time that IBM Storage and Red Hat Storage have been able to get together and really articulate what we're doing to help our customers in the context of Kubernetes and also with OpenShift and the things we're doing there. So I think you'll find, as we talked today that there's a lot of work we're doing to bring together the core capabilities of IBM Storage that have been helping enterprises with their core applications for years alongside the incredible open source capabilities being developed by Red Hat and how we can bring those together to help customers continue moving forward with their initiatives around Kubernetes and rebuilding their applications to be developed once deploy anywhere, which runs into quite a few challenges for storage. So Brent and I are excited to talk about all the great things we're doing, excited about getting to share it with everybody else at KubeCon. Yes, so of course containers when they first came out were for stateless environments. And we knew that, we've seen this before, those of us that live through the wave of virtualization, you kind of have a first generation solution, what application, what environments can be used. But as we've seen the huge explosion of containers and Kubernetes, there's going to be a maturation of the stack, storage is a critical component of that. So yeah, Brent, if you could bring us up to speed, you're steeped and have a long history in this space. The challenges that you were hearing from customers and where are we today in 2020 for this set? Thanks, Stu.  So traditional apps that are moving towards a more agile environment. That's where we've seen, in fact, our collaboration with IBM and particularly the DB2 team. And that's where we've seen as they've gone to a microservices container-based architecture, we've seen a poll from the marketplace say, in addition to inventing new cloud native apps, we want our tried, true, and tested apps, I mean, such as DB2, such as MQ, we want those to have the benefits of a Red Hat OpenShift agile environment. And that's where the collaboration between our group and Sam's group comes in together, is providing the storage and data services for those state collapse. Great, Sam, you know, IBM, you've been working with this storage administrator for a long time. What challenges are they facing when we go to the new architectures? Is it still the same people? It might there be a different part of the organization where you need to start in delivering these solutions? That's a really, really good question. And it's interesting because I do spend a lot of time with storage administrators and the people who are operating the IT infrastructure. And what you'll find is that the decision maker isn't the IT operations or storage operations people. These decisions about implementing Kubernetes and moving applications to these new environments are actually being driven by the business lines, which is, I guess, not so different from any other major technology shift. And the storage administrators now are struggling to keep up. So the business lines would like to accelerate development. They want to move to a develop once deploy anywhere model. And so they start moving down the path of Kubernetes in order to do that. They start leveraging middleware and components that are containerized and easy to deploy. And then they're turning to the IT infrastructure teams and asking them to be able to support it. And when you talk to the storage administrators, they're trying to figure out how to do some of the basic things that are absolutely core to what they do, which is protecting the data in the event of a disaster or some kind of a cyber attack, being able to recover the data, being able to keep the data safe, ensuring governance and privacy of the data. These things are difficult in any environment, but now you're moving to a completely new world. And the storage administrators have a tough challenge ahead of them. And I think that's where IBM and Red Hat can really come together with all of our experience and our very broad portfolio with incredibly enterprise hardened storage capabilities to help them move from their more traditional infrastructure to a Kubernetes environment. All right, Brent, maybe if you could bring us up to date, when we look back at like OpenStack, Red Hat had a few projects from an open source standpoint actually meets an acquisition to help bolster the open source storage world. In the container world, we saw some of those get ported over. There's new projects. There's been a little bit of argument as to the various different ways to do storage. And of course we know storage has never been a single solution. There's lots of different ways to do things, but where are we with the options out there? What's the recommendation from Red Hat and IBM as to how we should look at that? I want to bridge your question to Sam's earlier comments about the challenges facing the storage admin. So if we start with the word agility, I mean, what does agility mean for in a data world? We're conscious for agility from an application development standpoint, but if you use the term, of course we've been used to the term DevOps, but if we use the term data ops, what does that mean? What does that mean to in the past four decades, when a developer or someone deploying in production wanted to create new storage or data resources, it typically, they typically filed a ticket and waited. So in the agile world of OpenShift and Kubernetes, it's everything is self-service and on-demand. What kind of constraints and demands does that place on the storage and data infrastructure? So now I'll come back to your questions, Stu. So yes, at the time that Red Hat was very heavily into OpenStack, Red Hat acquired Ceph, well acquired Ink Tank and a majority of the Ceph developers who are most active in the community. And that became the de facto software-defying storage for OpenStack, but actually from the last time that we spoke at KubeCon, the Rook project has become very popular there in the CNCF as a way effectively to make software-defying storage systems like Ceph simple. So effectively the power of Ceph made simple by Rook inside of the OpenShift operator framework. People want that power that Ceph brings, but they want the simplicity of self-service on-demand. And that's kind of the fusion, the coming together of traditional software-defying storage with agility in a Kubernetes world. So Rook, Ceph, OpenShift container storage. Wonderful, and I wonder if we could take that a little bit further. A lot of the discussion these days, and I hear it every time I talk to IBM and Red Hat, is how customers are using hybrid clouds. So obviously that has to have an impact on storage. Moving data is not easy. There's a little bit of nuance there. So how do we go from what you were just talking about into a hybrid environment? I guess I'll take that one to start. And Brent, please feel free to chime in on it. So first of all, from an IBM perspective, you really have to start at a little bit higher level and at the middleware layer. So IBM is bringing together all of our capabilities, everything from analytics and AI to application development and all of our middleware and packaging them up in something that we call cloud packs, which are pre-built catalogs of containerized capabilities that can be easily deployed in any OpenShift environment, which allows customers to build applications that can be deployed both on-premises and then within public cloud. So in a hybrid, multi-cloud environment. Of course, when you build that sort of environment, you need a storage and data layer, which allows you to move those applications around freely. And that's where the IBM storage suite for cloud packs comes in. We've actually taken the core capabilities of the IBM software-defined storage portfolio, which give you everything you need for high-performance block storage, scale-out file storage and object storage. And then we've combined that with the capabilities that we were just discussing from Red Hat, which, including OCS and Ceph, which allow you a customer to create a common agile and automated storage environment, both on-premises in the cloud, giving consistent deployment and the ability to orchestrate the data to where it's needed. I'll just add onto that. I mean, as Sam noted, and as probably most of you are aware, hybrid cloud is at the heart of the IBM acquisition of Red Hat with Red Hat OpenShift. The stated intent of Red Hat OpenShift is to become the default operating environment for the hybrid cloud. So effectively bring your own cloud wherever you run. So that is at the very heart of the synergy between our companies, made manifest by the very large portfolios of software which have been moved to many of which to run in containers and embodied inside of IBM CloudPacks. So IBM CloudPacks backed by Red Hat OpenShift on wherever you're running, on-premises in a public cloud. And now with this storage suite for CloudPacks that Sam referred to, also having a deterministic experience. That's one of the things as we work, for instance, deeply with the IBM DB2 team. One of the things that was critical for them is they couldn't have their customers when they run on AWS have a completely different experience than when they ran on-premises say on VMware or on-premises on Bermittal. Critical to the DB2 team to give their customers deterministic behavior wherever they ran. Right, so Sam, I think any of our audience that have followed this space have heard Red Hat's story about OpenShift and how it lives across multiple cloud environments. I'm not sure that everybody is familiar with how much of IBM's storage solutions today are really just software driven. So, and therefore, if I think about IBM, it's like, okay, I can buy storage or yes, they can live in the IBM cloud, but from what I'm hearing from Brent and you and from what I know from previous discussions, this is independent and can live in multiple clouds leveraging this underlying technology and can leverage the capabilities from those public cloud offer. That right, Sam? Yeah, that's right. And we have the most comprehensive portfolio of software-defined storage in the industry. Maybe to some it's a well-kept secret, but those that use it know the breadth of the portfolio. We have everything from the highest performing scale out file system to object store that can scale into the exabytes. We have our block storage as well, which runs within the public clouds and can extend back to your private cloud environment. When we talk to customers about deploying storage for hybrid multicloud in a container environment, we give them a lot of paths to get there. We give them the ability to leverage their existing sand and infrastructure through the CSI drivers container storage interface. So our whole physical on-prem infrastructure supports CSI today. And then all the software that runs on our arrays also supports running on top of the public clouds, giving customers then the ability to extend that existing sand infrastructure into a cloud environment. And now with storage suite for cloud packs, as Brent described earlier, we give you the ability to build a really agile infrastructure leveraging the capabilities from Red Hat that give you a fully extensible environment and common way of managing and deploying both on-prem and in the cloud. So we give you a journey with our portfolio to get from your existing infrastructure today. You don't have to throw it out, get started with that and build out an environment that goes both on-prem and in the cloud. Yeah, and Brent, I'm glad that you started with database because it's not something that I think most people would think about in a Kubernetes environment. Do you have any customer examples you might be able to give? Maybe anonymized, of course. Just talking about how those mission critical applications can fit into the new modern architectures.  But what I'd add to that, so that's kind of frequently where they start because applications based on structured data remain at the heart of a lot of enterprises. But I would say workload category number two are is all things machine learning, analytics, AI. And we're seeing an explosion of adoption within the OpenShift. And of course, IBM CloudPak for data is a key market participant in that machine learning and analytics space. So an explosion of the usage of OpenShift for those types of workloads. And I'm just going to touch just briefly on an example going back to our kind of data pipeline and how it started with databases but it just, it explodes. For instance, data pipeline automation where you have data coming into your apps that are Kubernetes based, that are OpenShift based. Well, maybe you'll end up inside of Watson Studio inside of IBM CloudPak for data. But along the way, there are a variety of transformations that need to occur. Let's say that you're at a big bank you need to effectively as it comes in you need to be able to run a CRC to ensure to attest that when you modify the data for instance in a real time processing pipeline that when you pass it on to the next stage that you can guarantee, well that you can attest that there's been no tampering of the data. So that's an illustration where it began very with the basics of basic applications running with structured data with databases where we're seeing the state of the industry today is tremendous use of these Kubernetes and OpenShift based architectures for machine learning analytics made more simple by data pipeline automation through things like OpenShift container storage through things like OpenShift serverless where you have scalable functions and whatnot. So yeah, it began there but boy I tell you what it's exploded since then. Yeah, it's great to hear not only traditional applications but as you said, so much interest and need for those new analytics use cases. So absolutely that's where it's going. Sam, one other piece of the storage story of course is not just that we have stateful usage but talk about data protection if you could and how things that I think of traditionally my backup restore and the like how does that fit into the whole discussion we've been having? Yeah, when you talk to customers it's one of the biggest challenges they have honestly in moving to containers is how do I get the same level of data protection that I use today? The environments are in many cases more complex from a data and storage perspective. You want to be able to take application consistent copies of your data that could be recovered quickly. And in some cases even reused you can reuse the copies for dev test for application migration, there's lots of or for actually AI or analytics there's lots of use cases for the data but a lot of the tools and APIs are still very new in this space. IBM has made prior doing data protection for containers a top priority for our spectrum protect suite and we provide the capabilities to do application aware snapshots of your storage environment so that a Kubernetes developer can actually build in the resiliency they need as they build applications and a storage administrator can get a pane of glass and visibility into all of the data and ensure that it's all being protected appropriately and provide things like SLA. So I think it's about the fact that the early days of Kubernetes tended to be stateless now that people are moving some of their more mission critical workloads the data protection becomes just as critical as anything else you do in the environment so the tools have to catch up. So that's a top priority of ours and we provide a lot of those capabilities today and you'll see if you watch what we do with our spectrum protect suite we'll continue to provide the capabilities that our customers need to move their mission critical applications to a Kubernetes environment. All right and Brent one other question looking forward a little bit we've been talking for the last couple of years about how serverless can plug into this entire Kubernetes ecosystem the K-Native project is one that IBM and Red Hat have been involved with. So for OpenShift and serverless I'm sure he's leveraging K-Native what is the update today? The update is effectively adoption inside of a lot of cases like the big banks but also other top the largest companies in the world and other industries as well. So if you take the words event driven architecture many of them are coming to us with that's kind of top of mind of them is the need to say I need to ensure that when data first hits my environment I can't wait, I can't wait for a scheduled batch job to come along and process that data and maybe run an inference. I mean the classic case is you're ingesting a chest X-ray and you need to immediately run that against an inference model to determine if the patient has pneumonia or COVID-19 and then kick off another serverless function to anonymize the data to send back in to retrain your model. So the need and so you mentioned serverless and of course people would say well I can handle that just by really smart batch jobs but kind of one of the other parts of serverless that sometimes people forget but smart companies are aware of is that serverless is inherently scalable. So zero to end scalability. So as data is coming in, hitting your Kafka bus, hitting your object store, hitting your database. I don't know if you picked up the community project Debezium where something hits your relational database and that can automatically trigger an event onto the Kafka bus so that your entire architecture becomes event-driven. All right, well, Sam, let me give you the final let me let you have the final word, excuse me on the IBM in this space and what you want them to have is takeaways from KubeCon 2020 Europe. I'm actually going to talk to I think the storage administrators if that's okay because if you're not involved right now in the Kubernetes projects that are happening within your enterprise, they are happening and there will be new challenges. You've got a lot of investments you've made in your existing storage infrastructure. We at IBM and Red Hat can help you take advantage of the value of your existing infrastructure, the capabilities, the resiliency, the security you've built into it for the years and we can help you move forward into a hybrid multicloud environment built on containers. We've got the experience and the capabilities between Red Hat and IBM to help you be successful because it's still a lot of challenges there but our experience can help you implement that with the greatest success. I appreciate it. All right, Sam and Brent, thank you so much for joining. It's been excellent to be able to watch the maturation in this space over the last couple of years. Thank you. All right, we'll be back with lots more coverage from KubeCon, CloudNativeCon Europe 2020, the virtual event, I'm Stu Miniman and thank you for watching the Kube.


Hi everybody and greetings from Seoul, South Korea. As a U.S. ambassador to the Republic of Korea and former commander of the amazing Sixth Fleet, I'd like to extend my heartiest congratulations on your 70th anniversary. No exaggeration, I loved Sixth Fleet and living in Naples. It was my best tour as a flag officer. The history, the people I work with, the missions we had were all simply incredible. Now when I got to Naples, my boss was Admiral Lobster Fitzgerald. He told me something that I never forgot. Our C2 lay down was as strange then as it is now. I was a Sixth Fleet commander, but also his deputy at NAVIR and NAVAF. He told me that the deputy jobs were administrative, and what was really important was the Sixth Fleet job. He said to make Sixth Fleet relevant because it mattered and it resonated with the people living in Europe. So, keep it relevant, Lobster said, and we did. Just as Admiral Francketti is doing now and Admiral Fogo before her. Thanks to Admiral Francketti's leadership, Sixth Fleet continues to be a wonderful place to serve with amazing sailors and Marines to safeguard the United States and our allies. So once again, congratulations on your anniversary and I wish you all continued success for many more years to come.


Introducing the UTV chainsaw mount by Razerback Off-Road. The mount is constructed from a powder-coated aluminum exoskeleton surrounding a high-grade ultra-high-density plastic holster. The UTV chainsaw mount is designed to be as dependable as the people that use it and as tough as the saw it holds. We utilize this high-density plastic to protect your chain blades while also holding up to their bite over and over again. When stored, a platform supports the chainsaw motor and features bungee tie-down locations for a stable ride down the trail keeping your bumper spikes and felling docks from getting dulled while traveling. Securing your saw is as easy as tightening the two lock screws. You can choose to either secure the locks with a linchpin or padlock for additional protection from theft. But wait, there's more. Our side-by-side chainsaw mount is fully adjustable vertically and rotationally allowing for a variety of angles to fit your needs. You can choose either the it-fits mount that bolts directly to any RBO rack or the roll bar mount to attach anywhere you have room on your cage. If you order online today, we'll give you a 30-day money-back guarantee. And the peace of mind knowing your product is manufactured right here in the USA. Order your UTV chainsaw mount online now at razorbackoffroad.com.


From around the globe, it's theCUBE with digital coverage of AWS re-invent Executive Summit 2020 sponsored by Accenture and AWS. Welcome everyone to theCUBE virtual and our coverage of the Accenture Executive Summit part of AWS re-invent 2020. I'm your host, Rebecca Knight. Today we are talking about the power of three and what happens when you bring together the scientific know-how of a global bio-pharmaceutical powerhouse in Takeda, a leading cloud services provider in AWS and Accenture's ability to innovate, execute and deliver innovation. Joining me to talk about these things, we have Aaron, sorry, Arjun Beatty. He is the Senior Managing Director and Chairman of Accenture's Diamond Leadership Council. Welcome Arjun. Thank you. Carl Hick, he is the Chief Digital and Information Officer at Takeda. Pleasure to be here. Thank you, Rebecca. And Brian Bohan, Global Director and Head of the Accenture AWS Business Group at Amazon Web Services. Thanks so much for coming on. Thanks Rebecca, good to see you. Thank you. So as I said, we're talking today about this relationship between your three organizations. Carl, I want to talk with you. I know you're at the beginning of your cloud journey. What was the compelling reason? Why move to the cloud and why now? Yeah, no, thank you for the question. So as a biopharmaceutical leader, we're committed to bringing better health and a brighter future to our patients. We're doing that by translating science into some really innovative and life-transporting therapies. But throughout, we believe that there's a responsible use of technology, of data, and of innovation. And those three ingredients are really key to helping us deliver on that promise. And so while I think I'll call it this cloud journey, it's always been a part of our strategy. And we've made some pretty steady progress over the last years with a number of local diverse approaches to the digital and AI. We just weren't seeing the impact at scale that we wanted to see. And I think that there's a need ultimately to accelerate and broaden that shift. And we were commenting on this earlier, but it's been highlighted by a number of factors. One of those has been certainly the number of the large acquisitions we've made, Shire being the most pressing example. But also the global pandemic, both of those highlight the need for us to move faster at the speed of cloud ultimately. And so we started thinking outside of the box because it was taking us too long and we decided to leverage the strategic partner model. And it's giving us a chance to think about our challenges very differently. We call this the power of three. And ultimately our focus is singularly on our patients. I mean, they're waiting for us. We need to get there faster. It can't take years. And so I think that there is a focus on innovation at a rapid speed so we can move ultimately from treating conditions to keeping people healthy. So as you are embarking on this journey, what are some of the insights you want to share about what you're seeing so far? Yeah, no, it's a great question. So I mean, look, maybe right before I highlight some of the key insights, I would say that with cloud now as the launchpad for innovation, our vision all along has been that in less than 10 years we want every single to kid associate or employee to be empowered by an AI assistant. And I think that that's going to help us make faster, better decisions that'll help us fundamentally deliver transformative therapies and better experiences to that ecosystem, to our patients, to physicians, to payers, et cetera, much faster than we previously thought possible. And I think that technologies like cloud and edge computing together with a very powerful I'll call it data fabric is going to help us to create this real-time, I'll call it the digital ecosystem. The data has to flow ultimately, seamlessly between our patients and providers or partners or researchers, et cetera. And so we've been thinking about this, I'll call it, we call it sort of this pyramid that helps us describe our vision. And a lot of it has to do with ultimately modernizing the foundation, modernizing and re-architecting the platforms that drive the company, heightening our focus on data, which means that there's an accelerated shift towards enterprise data platforms and digital products. And then ultimately, really an engine for innovation sitting at the very top. And so I think with that, there's a few different, I'll call it insights that are quickly kind of zooming into focus, I would say. One is this need to collaborate very differently. Not only internally, but how do we define ultimately and build a connected digital ecosystem with the right partners and technologies externally? I think the second component that maybe people don't think as much about, but I find critically important is for us to find ways of really transforming our culture. We have to unlock talent and shift the culture certainly as a large biopharmaceutical very differently. And then lastly, you've touched on it already, which is innovation at the speed of cloud. How do we reimagine that? How do ideas go from getting tested in months to kind of getting tested in days? How do we collaborate very differently? And so I think those are three, perhaps of the larger, I'll call it insights that the three of us are spending a lot of time thinking about right now. So Arjun, I want to bring you into this conversation a little bit, let's delve into those a bit. Talk first about the collaboration that Carl was referencing there. How have you seen that it is enabling colleagues and teams to communicate differently and interact in new and different ways, both internally and externally, as Carl said. No, thank you for that. And I've got to give Carl a lot of credit because as we started to think about this journey, it was clear it was a bold ambition. It was something that we had all to do differently. And so the concept of the power of three that Carl has constructed has become a label for us as a way to think about what are we going to do to collectively drive this journey forward? And to me, the unique ways of collaboration means three things. The first one is that what is expected is that the three parties are going to come together and it's more than just the sum of our resources. And by that I mean that we have to bring all of ourselves, all of our collective capabilities. As an example, Amazon has amazing supply chain capabilities. They are one of the best at supply chain. So in addition to resources, when we have supply chain innovations, that's something that they're bringing in addition to just talent and assets. Similarly for Accenture, right? We do a lot in the talent space. So how do we bring our thinking as to how we apply best practices for talent to this partnership? So as we think about this, so that's the first one. The second one is about shared success. Very early on in this partnership, we started to build some foundations and actually developed seven principles that all of us would look at as the basis for this shared success model. And we continue to hold that sort of in the forefront as we think about this collaboration. And maybe the third thing I would say is this one team mindset. So whether it's the three of our CEOs that get together every couple of months to think about this partnership or it is the governance model that Carl has put together which has all three parties in the governance and every level of leadership. We always think about this as a collective group so that we can keep that front and center. And what this I think ultimately has enabled us to do is it's allowed us to move at speed, be more flexible and ultimately all be looking at the target the same way, the North side the same way. Ryan, what about you? What have you observed and what are you thinking about in terms of how this is helping teams collaborate differently? Yeah, absolutely. And Arjun made some great points there. And I think if you really think about what he's talking about, it's that diversity of talent, diversity of skill and viewpoint and even culture. And so we see that in the power of three. And then I think if we drill down into what we see at Takeda and frankly, Takeda was really, I think pretty visionary and on their way here in taking this kind of cross functional approach and applying it to how they operate day to day. So moving from a more functional view of the world to more of a product oriented view of the world. So when you think about we're going to be organized around a product or a service or a capability that we're going to provide to our customers or our patients or donors in this case, it implies a different structure all together in a different way of thinking, right? Because now you've got technical people and business experts and marketing experts all working together in this sort of cross collaboration. And what's great about that is it's really the only way to succeed with cloud, right? Because the old ways of thinking where you've got application people and infrastructure people and business people is suboptimal, right? Because we can all access this tools and these capabilities and the best way to do that is in a cross kind of a, you know, cross collaborative way. And so this is product oriented mindset and Takeda was already on, I think has allowed us to move faster in those areas. Carl, I want to go back to this idea of unlocking talent and culture. And this is something that both Brian and Arjun have talked about too. People are an essential part they're at the heart of your organization. How will their experience of work change and how are you helping reimagine and reinforce a strong organizational culture? Particularly at this time when so many people are working remotely? Yeah, it's a great question. And it's something that, you know, I think we all have to think a lot about. I mean, I think, you know, driving this, this color, this digital and data kind of capability, building takes a lot of thinking. So, I mean, there's a few different elements in terms of how we're tackling this. One is we're recognizing and it's not just for the technology organization or for those actors that we're innovating with but it's really across, you know, all of Takeda. We're working through ways of raising what I'll call the overall digital literacy of the organization. You know, what are the, you know, what are the skills that are needed almost at a baseline level even for a global biopharmaceutical company? And how do we deploy? I'll call it those learning resources very broadly. And then secondly, I think that, you know, we're very clear that there's a number of areas where there are very specialized skills that are needed. My organization is one of those. And so, you know, we're fostering ways in which, you know, we're very kind of quickly kind of creating avenues, excitement for associates in that space. So one example specifically is we use, you know, during these very much sort of remote sort of days, we use what we call global IT me days. And we set a day aside every single month. And this last Friday, you know, we create during that time, it's time for personal development. And we provide active seminars and training on things like, you know, for robotic process automation, data analytics, cloud. And this last month, we've been doing this for months and months now, but in this last month, more than 50% of my organization participated. And there's this huge positive shift, both in terms of access and excitement about really harnessing those new skills and being able to apply them. And so I think that that's, you know, one element that can be considered. And then thirdly, of course, every organization has to work on, how do you prioritize talent acquisition and management and competencies that you can't reskill? I mean, there are just some new capabilities that we don't have. And so there's a large focus that I had with our executive team and our CEO and thinking through those critical roles that we need to activate in order to kind of to build on this business led cloud transformation. And lastly, probably the hardest one, but the one that I'm most jazzed about is really this focus on changing the mindsets and behaviors. And I think there, you know, this is where the power of three is really kind of coming together nicely. I mean, we're working on things like, you know, how do we create this patient obsessed curiosity and really kind of unlock innovation with a real kind of a growth mindset? And the level of curiosity that's needed, not to just continue to do the same things, but to really challenge the status quo. So that's one big area of focus. We're having the agility to act just faster. I mean, to worry less, I guess I would say about kind of the standard chain of command, but how do you make more speedy, more courageous decisions? And this is places where we can emulate the way that a partner like AWS works, or how do we collaborate across the number of boundaries? You know, and I think Arjun spoke eloquently to a number of partnerships that we can build so we can break down some of these barriers and use these networks, whether it's within our own internal ecosystem or externally to help to create value faster. So a lot of energy around ways of working, and we'll have to check back in, but I mean, we're early in on this mindset and behavioral shift, but a lot of good early momentum. Carl, you've given me a good segue to talk to Brian about innovation because you said a lot of the things that I was the customer obsession and this idea of innovating much more quickly. Obviously now the world has its eyes on drug development and we've all learned a lot about it in the past few months and accelerating drug development is of great interest to all of us. Brian, how does a transformation like this help a company's ability to become more agile and more innovative at quicker speed too? Yeah, no, absolutely. And I think some of the things that Carl talked about just now are critical to that, right? I think where sometimes folks fall short is they think, you know, we're going to roll out the technology and the technology is going to be the silver bullet or in fact, it is the culture. It is the talent and it's the focus on that that's going to be the determinant of success. And I will say, you know, in this power of three arrangement, Carl talked a little bit about the pyramid, talent and culture and that change and the kind of thinking about that has been a first class citizen since the very beginning, right? That absolutely is critical for being there. And so that's been key. And so we think about innovation at Amazon and AWS and Carl mentioned some of the things that, you know, partner like AWS can bring to the table is we talk a lot about builders, right? So we're kind of obsessive about builders. And what we mean by that is we at Amazon, we hire for builders, we cultivate builders and we like to talk to our customers about it as well. And it also implies a different mindset, right? When you're a builder, you have that curiosity, you have that ownership, you have that stake and whatever I'm creating, I'm going to be a co-owner of this product or the service, right? Getting back to that kind of product oriented mindset. And it's not just the technical people or the IT people who are builders, it is also the business people as Carl talked about, right? So when we start thinking about innovation, again, where we see folks kind of get into a little bit of a innovation pilot paralysis is that you can focus on the technology, but if you're not focusing on the talent and the culture and the processes and the mechanisms, you're going to be putting out technology, but you're not going to have an organization that's ready to take it and scale it and accelerate it, right? And so that's been absolutely critical. So just a couple of things we've been doing with Takeda and Takeda's really been leading the way is think about a mechanism and a process and it's really been working backward from the customer, right? In this case, again, the patient and the donor. And that was an easy one because the key value of Takeda is to be a patient focused biopharmaceutical, right? So that was embedded in their DNA. So that working back from that patient, that donor was a key part of that process. And that's really deep in our DNA as well and eccentric. And so we're able to bring that together. The other one is getting used to experimenting and even perhaps failing, right? And being able to iterate and fail fast and experiment and understanding that, you know, some decisions, what we call it at Amazon are two-way doors, meaning you can go through that door, not like what you see and turn around and go back. And cloud really helps there because the cost of experimenting and the cost of failure is so much lower than it's ever been. You can do it much faster and the implications are so much less. So just a couple of things that we've been really driving with Takeda around innovation that's been really critical. Carl, where are you already seeing signs of success? Yeah, no, it's a great question. And so we chose, you know, with our focus on innovation to try to unleash maybe the power of data digital in focusing on what I call sort of a maven. So we chose our plasma-derived therapy business. And, you know, the plasma-derived therapy business unit, it develops critical life-saving therapies for patients with rare and complex diseases. But what we're doing is by bringing kind of our energy together, we're focusing on creating, I'll call it state-of-the-art, digitally connected donation centers. And we're really modernizing, you know, the donor experience right now. We're trying to improve also, I'll call it the overall plasma collection process. And so we've selected a number of, I'll call it very high-speed pilots that we're working through right now, specifically in this area. And we're seeing really great results already. And so that's one specific area of focus. Arjun, I want you to close this out here. Any ideas, any best practices, advice you would have for other pharmaceutical companies that are at the early stage of their cloud journey? Sorry, was that for me? Yes, sorry, Arjun. Yeah, no, I was breaking up a bit. No, I think the key is what's sort of been great for me to see is that when people think about cloud, you know, you always think about infrastructure technology. The reality is that the cloud is really the true enabler for innovation at innovating at scale. And if you think about that, right, and all the components that you need, ultimately, that's where the value is for the company, right? Because yes, you're going to get some cost synergies and that's great. But the true value is in how do we transform the organization in the case of Takeda and our life sciences clients, right? We're trying to take a 14-year process of research and development that takes billions of dollars and compress that, right? Tremendous amounts of innovation opportunity. You think about the commercial aspect, lots of innovation can come there. The plasma derived therapy is a great example of how we're going to really innovate to change the trajectory of that business. So I think innovation is at the heart of what most organizations need to do and the formula, the cocktail that Takeda has constructed with this Fuji program really has all the ingredients that are required for that success. Great, well, thank you so much. Arjun, Brian, and Carl was really an enlightening conversation. Thank you, it's been a lot of fun. Thank you. It's been fun. Thanks, Rebecca. And thank you for tuning in to the Cube Virtual's coverage of the Accenture Executive Summit.


In this module, you will see gender is also defined a kind of learning. This idea may easily be derived from the things which we have discussed in the previous modules, that every time we enter in a new phase of life, in a new context, in new role, and in new activities, we learn something. When we say we learn something, that is the norms, social order. So that's why we are calling here that gender is a kind of learning. How? Gender development continues beyond adolescence. It is a process of learning new roles in new contexts with different norms. We enter in jobs, for example. We are part of a new place of interaction, that is a new market, in a new institution, where we have to learn new norms and expectations, that is new social order. In every market, in every context of interaction, the expectations and norms are different from the previous phase of development and previous context. So we have to act and behave, for example, as secretary, as liars, managers, teachers. These are different roles in different places, and there are different patterns of interactions. So definitely our behavior, our ways of talk, etc. Everything is monitored by new set of norms and expectations. These new roles add more gender expectations. So every time we enter in a new context, so we add a new set of expectations with it. We enter into new relations if we talk about social institutions. First, we talked about workplaces and now social institutions. For example, our relations as husbands, wives, mothers, aunts, uncles, brothers, sisters. In every social role, definitely we have to learn according to the role a new set of expectations. Now we become men and women with new identity. All these are our identities, person is the same. The same person is functioning sometime as mother, sometime as wife, sometime as friend. So we have different roles and when we adopt a new role, so indirectly we have to adopt a new set of norms. The social expectations for these roles will be different from the previous phases or the places of interaction. Gender development, if we take it up, it is a set of different places, different experiences, different roles and norms at different stages of life. So this is how we can define what is gender development. It is this interaction of different contexts, norms and roles which make it a complex process. This is not a straightforward concept. This is not something that linearly develops in a straight line. So there are so many factors which are involved, which influence each other, which overlap and which make up what we call gender development. We as child, boy, girl, friend, husband, wife, professional, do not remain the same individual. It shows that it is a dynamic process as well. But the social order and norms alone do not define our gender. When we use this term gender in this context, remember we are talking about cultural gender. It never means natural gender or biological sex. It does not mean that we are male, but after these experiences with the passage of time, our gender development makes us a female or we were female and become a male. No, not like that. It is cultural gender. Our individual response to norms is different. So how a person does not remain the same when he passes through different phases of gender development? Because our response to different phases and contexts is different. Our experiences are different. They also play a role with it. To understand how a person remains the same or how a person changes, his or her personality changes, thinking changes, behavior changes with the passage of time when that person socially develops, culturally develops, to understand this idea that we have discussed in this module. I would suggest you to take a fiction short novel or short story, not a full novel if you do not like it. Here you would see different characters of the fiction. You will find some character that remains the same from the beginning to the end of the fiction. But there would be some other characters who change with different contexts and phases and stages of the story. The person or the character which remains the same, we call it flat. The other is called dynamic character. So to understand this idea, you will do this. Recall any novel or short story you have read and write a portrait of such character.


Hi everyone, Joe for jaspyscasebrakes.com doing a random team break for pick your team 3, OPG Platinum. So basically, in pick your team 3 we had these 14 teams kind of straggling a little bit. So we pulled those out and we turned into a random team break. An extra twist is that we're also giving away a sealed box of 1920 OPG Platinum. This one, this, exactly this one right here. And that'll go to the name on top. The second name will get the Canadian, so on and so forth. So everyone's guaranteed something. And the name on top could potentially get a box. So we're just randomizing your names and matching up with a team. We're not randomizing that list right there. So big thanks to this group for making it happen. Good luck. Let's roll it, randomize that list four and a one, five times. One, two, three, four, and a one, fifth and final time. Name on top gets the box, Jack, congrats.  All right, so congrats to you, Jack, Steve Birch. We'll put a little rooftop next to your name because so you'll know that you won that in a filler. We'll do the same for the rest. Steve Birch, you've got the Canadians, Nicholas with the Hurricanes and Blackhawks, Steve with the Panthers, Matthew with the Kings, Steve with the Senators, Brian with the Knights, Steve with the Islanders and Predators, Brian with the Sharks, Nicholas with the Jets, Steve with the Coyotes and the Flames and Charles with the Columbus blue jackets. In a separate video, it will be that break itself. We'll see you for that later, Jaspiescasewakes.com.


Internet hospitals are emerging in China as a new forum for doctors to conduct diagnosis and treatment activities based on the internet, becoming integral to the development of the medical field with increasing reforms and policies in China's medical and health system. And Fazu Internet Hospital serves as an example to discuss the operations and functional positioning of developing Internet Hospital medical services in relation to physical hospitals, considering platform operation, management, and network security, while highlighting advantages and limitations for reference. This article was authored by Li Huazhi, Pei Yin, Jingjing Ren, and others.