>>mm We're entering the fourth grade era of VM ware Executive management From its beginnings in the late 90s is a Silicon Valley startup. It's five founders quickly built the company and it ended up as one of the greatest acquisitions in the history of enterprise tech when EMC bought VM ware for $625 million as a public company. But still under EMC's governance, paul Maritz was appointed Ceo in 2000 and eight and set the company on a journey to build what he called at the time. The software mainframe meaning the company's platform would run any application at high performance with low overhead and world class recovery. Pat Gelsinger took over the Ceo reins in 2012 and through organic investments and clever m and a set of course for the software defined data center and after some early miscalculations in cloud, realigned the company strategy to successfully partner with hyper scale hours and position the company for the multi cloud future. The hallmarks of VM where over the course of its history have been great engineering that led to great products, loyal customers and a powerful ecosystem. The other telling attribute of VM where is it? CEOs have always had a deep understanding of technology and its latest Ceo is no different. It's our pleasure to welcome raghu Raghuram back to the cube the fourth Ceo of VM ware and yet another Silicon Valley Ceo graduated from the IIttie rgu, great to see you again and congratulations on your new role. >>Thanks. It's great to be here. >>Okay, five months in 1st 100 days what we have focused on that journey to become the Switzerland of multi cloud, tell us about your early experience as ceo >>it's been fantastic. Uh our customers, all our employees, all our partners have been very welcoming and of course I've given me great input. What we've been able to do in the last 100 days is to really crystallize the strategy and focus it around what I'm sure we're gonna be spending a lot of time talking about. And that's about the multi cloud era of computing that most enterprises are going to go through over the next decade. And so that's really what I've been up to and you'll see the results of that in next week's uh we involved and uh where we would be talking about the strategy and some product announcements that go along with the strategy and so it's a very exciting time to be at Vandenberg. >>Yeah, I mean, I referenced it in my intro, it's almost like the light bulb went off when VM ware realized, wow, this cloud build out is just an opportunity for us and that's really what you're doing with the multi cloud as you're building on top of all the infrastructure that the hyper cloud vendors are putting out there. Maybe you can talk about that, that opportunity and what customers are telling you. >>Yeah, it's uh here is how I describe what has happened in the industry. Right, and what will happen in the industry. So, if you look at the the past decade, as cloud became a mainstream thing, most customers pick the cloud, they built their first digital applications into it, the ones that serve their mobile users or end users with digital products and that worked great for them. Then they step back and say, okay, how many modernize everything that we're doing has become a digital company. And when you go from 10, of your portfolio, 100% of your application portfolio being modernized. What has to happen is you got to go from figuring out, okay, how am I gonna put everything in one cloud to what does the application need and how do I put it on the right place? I look at the same time, the industry has also evolved from being uh predominantly supplied by one cloud provider to multiple cloud providers. At the same time, the thanks to companies like IBM where the data center has been transformed into a private cloud. The edges growing up to be its own location for a cloud sovereign clouds are going. So truly what has happened is it's become a multi cloud world. And customers are saying in addition to just being cloud first, I want to be cloud smart. And so this distributed era of computing that we are entering is what we are seeing in the industry. And what the empire is trying to do is to say, look, let's provide customers with the fastest way of getting to this multi cloud era of computing so that they can go fast, they can spend less and most importantly, they can be free, in other words, choose the right application, right cloud for right applications and have control over how they deploy and use their applications and data. That really is a strategy that we are putting in place. This is something that we've been working towards in the last couple of years now. I'm accelerating that and making that the main piece of what we end, where is doing in order to do that, we have a great opportunity to take partner even better with all of our cloud provider partners and that's where the Switzerland of the industry comes in without impending spin, especially, we have great partnership with the cloud players, great partnerships with infrastructure players. We truly can be a neutral partner to the customers as they look at all these choices and make the right choices for their applications. >>So, I want to ask you about this multi cloud when when the early multi cloud narrative came out where I go, I was saying, look, multi cloud is really multi vendor, you you've got workloads and apps running on different, different clouds. And then increasingly, the promise and your promises, we're going to abstract the underlying complexity of those clouds and we're going to give you an experience whether it's on premise, hybrid into a cloud. Across clouds. Eventually out to the edge, it's gonna be a singular, substantially identical, if not identical experience and we're going to manage the whole kit and caboodle. And how where are we in that first of all? Is that the right way to think about it? Where are we in that sort of transition from plugging into any, you know, a cloud? I'm compatible with the cloud to it's a singular sort of VM ware cloud if you will. >>Yeah. So, um, so I wanna clarify something that he said because this tends to be very commonly confused by customers use the word abstraction. And usually when people think of abstraction, they think it hides capabilities of the uh, cloud providers. That's not what we are trying to. In fact, that's the last thing we're trying to do. What we're trying to do is to provide a consistent developer experience regardless of where you want to build your application so that you can use the cloud provider services if that's what you want to use. But the deficit cops toolchain, the runtime environment, which turns out to be Cuban aires and how you control the kubernetes environment. How do you manage and secure and connect all of these things. Those are the places where we are adding the value. Right. And so really the VM ware value proposition is you can build on the cloud of your choice but providing these consistent elements. Number one, you can make better use of us, your scarce developer or operator resources and expertise. Right. And number two, you can move faster and number three can spend less as a result of this. So that's really what we're trying to do, but not. So I just wanted to clarify the word abstraction in terms of their way, we're still, I would say in the early stages, so if you look at what customers are trying to do, they're trying to build these Greenfield applications and there is an entire ecosystem emerging around Campaneris. There is still kubernetes is not a developer platform. The developer experience on top of kubernetes is highly inconsistent. And so those are some of the areas where we are introducing new innovations with our towns, our application platform. And then if you take enterprise applications, what does it take to have enterprise applications running all the time, be entirely secure, etcetera, etcetera. That's where the we ever cloud assets that are traditionally this fear based come into play and we've got this now in all of the clouds but it's still in the early days from uh on Azure and google et cetera. How do you manage and secure those things again? We're in the early days. So that's where we are. I would say, >>yeah, thank you for that clarification, I want to sort of come back to that and just make sure we understand it. So for example, if I'm a developer and I want to take advantage of, let's say graviton uh and build an app on that, that so maybe it's some kind of data intensive app or whatever it is. I can do that. You won't restrict me from doing that at the same time. If I want to use the VM where management experience across all my clouds, I can do that as well. Is that the right way to think about it? >>Yeah, exactly. So the management experience by the way, and this is the other thing that gets missed in the remember dialogue because we've been so phenomenally successful with this fear. There's a misperception that everything we are doing atmosphere today works only on top. So everything we're doing at BM wear works only on top of the sphere. That's not the case. Take management, for example, our management portfolio is modular and independent of these, which means it can manage the Graviton application that you're building, right. It can manage a traditional, these fear based application, it can manage rage application, it can manage VM based applications, can manage computer based applications. Uh so it's truly uh, overall management layer. So that is really what we're trying to do. Same thing with our kubernetes example. Right, So our communities control plane allows you to control these kubernetes clusters. Whether the clusters are utilizing gravity and whether clusters are utilizing these fear based crew binaries environments. >>Okay, that's great. So it's kind of a set up question because my next question relates to project Monterey, Because, you know, I've always said when I write about about these things, when I saw Nitro, I saw Graviton, I saw project monitor, I said uh everybody needs a Nitro Nitro or a graviton because new workloads are coming. It's not just the X 86 can handle everything anymore asap whether it's sequel server, whatever we've got new workloads that are coming ai ml data intensive edge workloads, et cetera. Is that how we should think of? Project Monterrey. Where are you in Project Monterey? Why is it so important? Help people understand that? >>Yeah. Project mantra is super exciting for a couple of different reasons. One is uh in its first iteration and uh we announced project monitoring and last being well, we continue to build and we're making great progress along with the hardware partners that we are working with um in its first hydration it allows um um some of the functions that you would expect in the software defined data center to be offloaded into these montri processors. The smart nick processes. Right. So what that does, is it clears up the core CPU for other application functions. Right, so you get better scalability, more resource utilization, etcetera, etcetera. The second thing it does is because some of the software defined data center functions are done in the smart make um it gets accelerated as well. Because it takes advantage of the special accelerators that are there security functions, manageability functions, networking functions etcetera, etcetera. So that's that what you're alluding to is overall it's the v sphere, the sX Hyper Visor complimentary itself. That's moving into the specialized processors which allows the hyper Visor will be built into these smart mix, which means the main CPU can be an intel. CPU can be an M D C P. You can be an arm. CPU can be whatever it is you want in the future. So truly enables Monte CPU heterogeneous computing. So that's that's why this is exciting. And of course because it is the sphere, it can happen in the data centers, it can happen in Carlos. It can happen in Sovereign clouds. It can happen in the public clouds all over a period of time. And >>and potentially the Edge I would presume in the future. >>Sorry. Yeah, that's a great point. Thanks for pointing that out. In fact, the Edge is one of the most important places that will happen because we need these low latency applications such as in the telco case for example, right. Or we need these applications that have specialized processing the required. If you're setting up a cashier less store and you need to process and you need a lot of influence engines. So, Monterey helps with all of those things. >>I want to make sure our audience understands. It's because the software defined data center was awesome but but it also created waste in the sense that you have all these offload functions in storage and networking and security running on on x 86 processors which may not be the most efficient way. So emerging architectures around arm might be less expensive, maybe more cost effective, lower power. Uh maybe they do memory management differently. So there are these offload use cases. But as well you we talked about the edge there could be a lot of edge use cases that or whatever whether it's arm or in video etcetera. So now you're driving that optionality for customers so you can support more workloads of the future. >>Yeah, so this is exactly if you think about in europe when you talked about the embers evolution, the inverse core DNA has always been to master hydrogen. Itty right. And what we're seeing is this world of heterogeneous hardware coming alive. Right. You talked about Professor hydrogen Itty including GPU chips and so on. There is a memory architecture heterogeneous, their storage architecture heterogeneous. And so the idea is that regardless of what you use, how do you provide the best workload platform and a consistent way of managing all of these things and reducing the complexity while gaining the efficiency benefits and the other benefits that you talked about. >>So speaking of geniality that brings me to Tansu, you know early on people thought, oh wow containers, that's gonna kill VM where this is the opposite happened. You guys leaned in as as you have as a sign of great leadership these days. You don't get defensive, you just, you know, get the trend is your friend, as they say, give us the update on on Tan xue. Why is that so important to the future? >>Yeah. So if you look at any enterprises portfolio right, they are looking at it and saying look, there's a whole set of applications that I need to modernize. Now. The question becomes how do you modernize these applications in a way that it is essentially done with these microservices architectures and so on and so forth. In that context, how do I maximize the developer productivity and provide a great developer experience because there is not enough developers in the world to modernize every application that that's in every enterprise. Right. So, Tan xue is our answer to help enterprises modernize their applications and deliver in a way that the developed makes the developers very productive on the cloud of their choice. So that is really the strategic intent of Tancill and the core building block for Tan xue is of course kubernetes as you well know, Kubernetes has become the common infrastructure abstraction across clouds. So if you want portability for traditional VM based applications, he used this fear, if you want portability for traditional for containerized microservices applications, you assume kubernetes, that's how companies companies are thinking about it. And so that's the first thing that we did now. The second is you've got developers building applications all over the place. So now, just like you used to have physical server sprawl and now and then VM sprawl these days you have cluster sprawl, kubernetes, cluster sprawl and tons of mission control affects as a multi cloud, multi cluster kubernetes control plan works on the chaos and everything else that some of the Sun. The third point of Tanzania is the developer experience and we have introduced Andrew application platform, which is really focused on delivering a great developer experience on top of any Cuban Aires. So that's really how we're building out the towns of portfolio. And then of course we got Spring and uh as you well know a majority of enterprise applications today are java and if you want to modernize java, you use spring boot and so we had tremendous success with our uh spring boot technology and our startup, Springdale Ohio capabilities and so on and so forth. So that's the entirety of the towns of portfolio. It's multi cloud, it's kubernetes agnostic. Of course it runs great on this fear but it's really the approach making developers productive in the enterprise >>awesome. Thank you for that. I know we're tight on time but it's like speed dating with you raghu. So I'm gonna go on to another topic. Really important topic of security, you've made obviously some big acquisitions, there are things like carbon black, you've got a lot of stuff going on with, with, with endpoint, with end user computing, I'm first interested in sort of how you organize it looks like you're putting security and the networking piece together and then what's your swim lane? It seems like you're, you're focused obviously on your infrastructure. You're not trying to be all things to all people. Help us understand your strategy in that regard. >>Yeah, I mean security is a massive space, Right? And you covered very well. Hundreds and thousands of security problems that customers want to be solving. What we are focused on is how do we simplify the security problem for the customers? And we're doing it through three wells. The first one is we are baking security into the platforms that customers used ones. Right. But there are more obvious fear our workspace one, our container platform etcetera, etcetera. Right? Cloud platforms. So that's the first thing that we're doing. The second is we are putting um, bringing together, we're taking an end to end view of security, which is everything from an end user connecting from home to the corporate network or the sassy, sassy applications to the Windows devices they are using to the data center applications they're using to the club. Right? So we're taking a holistic view of security. So which means we want to combine our network security assets with our endpoint security assets with our workload security assets. That is why we bought all of those things together under one roof. And the third is we are instrumental in all of these and collecting signals from all of these and pulling it into the cloud and turning security into a machine learning and the data problem, right? And that is where the problem. Black cloud comes in and by doing that, we are able to provide a holistic view of where uh customer security posture, right? And these sensors can be on BMR platforms, on non BMR platforms etcetera. And so so that's really how we are approaching it. I mean there's the emerging industry term for a policy XDR. You might follow that. So that's really what we're trying to do. >>Outstanding. Last question and I know, I know we got to go. You mentioned the spin that's happening in november. That's an exciting time for a lot of reasons. I think the ecosystem, you know, emphasizing your independence but also gives you control of your balance sheet, regaining control of your balance sheet, tongue in cheek there. But it's important because all this, this cloud build out this multi cloud, exposing the primitives, leveraging the primitives and the A. P. I. S. Of these clouds making them identical across all these estates. That's not trivial and you're obviously gonna need resources to do that. So maybe you can talk about that and how you see the future playing out organic inorganic, maybe a little lemon A in there. What's your approach? How are you thinking about that? >>Yeah. So we are very excited with the impending spain, which like you said is on track to happen early november. Um and if you think about the spin, there are three aspects that we are excited about. The first aspect is uh we have a great relationship with Dell Tech, the company right. What we have done is we have codified that into a framework agreement that covers the gold market and technology collaboration and we are super excited by that and that baselines against what we do today and then as incentives on both sides to continue to grow that tremendously. So we're gonna continue being, doing that and that's going to continue being a great partner at the same time. From a partnership point of view, is truly going to be a Switzerland of the industry. So previously companies that were otherwise a little bit more competitive with dull now no longer have that reservation in partnering very deeply with us. I'm totally, like you said from a capital structure point of view, it gives us the flexibility to use to do em in a should we decide to do so in the future right? And use both equity and cash for them in a so so that's the capital structure, flexibility, the Switzerland positioning and the continuing great relationship with dull Those are the benefits of the spin >>love and the partner ecosystem has always been a source of, of innovation and it's a big part of the flywheel, the power of many versus the resources of one Ragu, Thanks so much for coming back in the queue. Best of luck. We're really excited for you and for the future of VM ware. >>Thank you and thanks for all the great work that you do and look forward to continuing to read your great research, >>appreciate that. And thank you for >>watching the cubes, continuous >>Coverage of VM World 2021. Keep it right there. >>Thank you. Mhm. Yeah.

>>from around the globe. It's the Cube with digital coverage of AWS reinvent 2020 sponsored by Intel and AWS. Yeah, welcome back to the Cubes. Live coverage of AWS reinvent 2020. It's virtual this year over three weeks. Next three weeks we're here on the ground, covering all the live action. Hundreds of videos Walter Wall coverage were virtual not in person this year. So we're bringing all the interviews remote. We have Deepak Singh, vice president of Compute Services. A range of things within Amazon's world. He's the container guy. He knows all what's going on with open source. Deepak, great to see you again. Sorry, we can't be in person, but that's the best we could do. Thanks for coming on. And big keynote news all year all over the keynote. Your DNA is everywhere in the keynote. Thanks for coming on. >>Yeah. Now, no thanks for having me again. It's always great to be on the Cube. Unfortunately, not sitting in the middle of the floral arrangement, which I kind of miss. I know, but it waas great morning for us. We had a number of announcements in the container space and sort of adjacent to that in the developer and operator experience space about making it easy for people to adopt things like containers and serverless. So we're pretty excited about. And his keynote today and the rest agreement. >>It's interesting, You know, I've been following Amazon. Now start a three invent. I've been using Amazon since easy to started telling that garment that story. But you look like the mainstream market right now. This is a wake up call for Cloud. Um, mainly because the pandemic has been forced upon everybody. I talked to Andy about that he brought up in the keynote, but you start to get into the meat on the bone here. When you're saying OK, what does it really mean? The containers, the server Lis, Uh, the machine learning all kind of tied together with computers getting faster. So you see an absolute focus of infrastructures of service, which has been the bread and butter for Amazon web services. But now that kinda you know, connective tissue between where the machine learning kicks in. This is where I see containers and lambda and serve Earless really kicking ass and and really fill in the hole there because that's really been the innovation story and containers air all through that and the eks anywhere was to me the big announcement because it shows Amazon's wow vision of taking Amazon to the edge to the data center. This is a big important announcement. Could you explain E. K s anywhere? Because I think this is at the heart of where customers are looking to go to its where the puck is going. You're skating to where the puck is. Explain the importance of eks anywhere. >>Yeah, I'll actually step back. And I talked about a couple of things here on I think some of the other announcements you heard today like the smaller outposts, uh, you know, the one you and do you outpost skills are also part of that story. So I mean, if you look at it, AWS started thinking about what will it take for us to be successful in customers data centers a few years ago? Because customers still have data centers, they're still running there On our first step towards that Waas AWS in many ways benefits a lot from the way we build hardware. How what we do with nitro all the way to see C two instance types that we have. What we have a GPS on our post waas. Can we bring some of the core fundamental properties that AWS has into a customer data center, which then allowed PCs any KS and other AWS services to be run on output? Because that's how we run today. But what we started hearing from customers waas That was not enough for two reasons. One, not all of them have big data centers. They may want to run things on, you know, in a much smaller location. I like to think about things like oil rates of point of sale places, for they may have existing hardware that they still plan to use and intend to use for a very long time with the foundational building blocks easy to EBS. Those get difficult when we go on to hardware. That is not a W s hardware because be very much depend on that. But it containers we know it's possible. So we started thinking about what will it take for us to bring the best of AWS toe help customers run containers in their own data center, so I'll start with kubernetes, so with que binaries. People very often pick Kubernetes because they start continue rising inside their own data centers. And the best solution for them is Cuban Aires. So they learn it very well. They understand it, their organizations are built around it. But then they come to AWS and run any chaos. And while communities is communities, if you're running upstream, something that runs on Prem will run on AWS. They end up in two places in sort of two situations. One, they want to work with AWS. They want to get our support. They want to get our expertise second, most of them once they start running. Eks realized that we have a really nice operational posture of a D. K s. It's very reliable. It scales. They want to bring that same operational posture on Prem. So with the ts anywhere what we decided to do Waas start with the bits underlying eks. The eks destroyed that we announced today it's an open source communities distribution with some additional pieces that that we had some of the items that we use that can be run anywhere. They're not dependent on AWS. You don't even have be connected to a W s to use eks destro, but we will Patrick. We will updated. It's an open source project on get help. So that's a starting point that's available today. No, Over the next several months, what will add is all of the operational to link that we have from chaos, we will make available on premises so that people can operate the Cuban and these clusters on Prem just the way they do on AWS. And then we also announced the U. K s dashboard today which gives you visibility into our communities clusters on AWS, and we'll extend that so that any communities clusters you're running will end up on the dashboard to get a single view into what's going on. And that's the vision for eks anywhere, which is if you're running communities. We have our operational approach to running it. We have a set of tools that we're gonna that we have built. We want everybody to have access to the same tools and then moving from wherever you are to aws becomes super easy cause using the same tooling. We did something similar with the C s as well the DCs anywhere. But we did it a little bit differently. Where in the CSU was centralized control plane and all we want for you is to bring a CPU and memory. The demo for that actually runs in a bunch of raspberry PiS. So as long as you can install the C s agent and connect to an AWS region, you're good to go. So same problem. Different, slightly different solutions. But then we are customers fall into both buckets. So that's that's the general idea is when we say anywhere it means anywhere and we'll meet you there >>and then data centers running the case in the data center and cloud all good stuff. The other thing that came out I want you to explain is the importance of what Andy was getting to around this notion of the monolith versus Micro Services at one slightly put up. And that's where he was talking about Lambda and Containers for smaller compute loads. What does it mean? What was he talking about there? Explain what he means by that >>that Z kind of subtle and quite honestly, it's not unique to London containers. That's the way the world was going, except that with containers and with several functions with panda. You got this new small building blocks that allow you to do it that much better. So you know you can break your application off. In the smaller and smaller pieces, you can have teams that own each of those individual pieces each other pieces. Each of these services can be built using architecture that you secret, some of them makes sense. Purely service, land and media gateway. Other things you may want to run on the C s and target. Ah, third component. You may have be depending on open source ecosystem of applications. And there you may want to run in communities. So what you're doing is taking up what used to be one giant down, breaking up into a number of constituent pieces, each of which is built somewhat independently or at least can be. The problem now is how do you build the infrastructure where the platform teams of visibility in tow, what all the services are they being run properly? And also, how do you scale this within an organization, you can't train an entire organ. Communities overnight takes time similar with similarly with server list eso. That's kind of what I was talking about. That's where the world is going. And then to address that specific problem we announced AWS proton, uh, AWS program is essentially a service that allows you to bring all of these best practices together, allows the centralized team, for example, to decide what are the architectures they want to support. What are the tools that they want to support infrastructure escort, continuous delivery, observe ability. You know all the buzzwords, but that's where the world's going and then give them a single framework where they can deploy these and then the developers can come into self service. It's like I want to build a service using Lambda. I don't even learn how toe put it all together. I'm just gonna put my coat and pointed at this stock that might centralized team has built for me. All I need to do is put a couple of parameters, um, and I'm off to the races and not scale it to end, and it gives you the ability to manage also, So >>it's really kind of the building blocks pushing that out to the customer. I gotta ask you real quick on the proton. That's a fully managed service created best. Could you explain what that means for the developer customer? What's the bottom line? What's the benefit to >>them? So the biggest benefit of developers if they don't need to become an expert at every single technology out there, they can focus on writing application court, not have to learn how to crawl into structure and how pipelines are built and what are the best practices they could choose to do. So the developers, you know, modern and companies Sometimes developers wear two hats and the building off, the sort of underlying scaffolding and the and the build applications for application development. Now all you have to do is in writing an application code and then just go into a proton and say, This is architecture, that I'm going to choose your self, service it and then you're off to the races. If there's any underlying component that's changing, or any updates are coming on, put on it automatically take care off updates for you or give you a signal that says, Hey, the stock has to be updated first time to redeploy accord so you can do all of that in a very automated fashion. That's why everything is done. Infrastructures Gold. It's like a key, uh, infrastructure and told us, and continuous delivery of sort of key foundational principles off put on. And what they basically do is doing something that every company that we talked oh wants to do. But only a handful have the teams and the skill set to do that. It takes a lot of work and it takes ah lot of retraining. And now most companies don't need to do that. Or at least not in that here. So I think this is where the automation and manageability that brings makes life a lot easier. >>Yeah, a lot of drugs. No docker containers. They're very familiar with it. They want to use that. Whatever. Workflow. Quickly explain again to me so I can understand fully the benefit of the lamb container dynamic. Because what was the use case there? What's the problem that you solve? And what does it mean for the developer? What specifically is going on there? What's the What's the benefit? Why would I care? >>Yeah, eso I'll actually talked about one of the services that my team runs called it of your stature. AWS batch has a front time that's completely serverless. It's Lambda and FBI did play its back in the PCs running on the city right? That's the better the back end services run on their customers. Jobs in the running. Our customers are just like that. You know, we have many customers out there that are building services that are either completely service, but they fit that pattern. They are triggered by events. They're taking an event from something and then triggering a bunch of services or their triggering an action which is doing some data processing. And then they have these long running services, which almost universally in our running on containment. How do you bring all of this together into a single framework, as opposed to some people being experts on Lambda and some people being experts and containers? That's not how the real world works. So trying to put all of this because these teams do work together into a single framework was our goal, because that's what we see our customers doing, and I think they'll they'll do it. More related to that is the fact that Lambda now supports Dr Images containing images as a packaging format because a lot of companies have invested in tooling, toe build container images and our land. I can benefit from that as well. While customers get all the, you know, magic, The Lambda brings you >>a couple of years ago on this on the Cube. I shared this tweet out earlier in the week. Andy, we pressed and even services launches like, would you launch build Amazon on Lamb? Day says we probably would. And then he announced to me And he also I think you mentioned the keynote that half of Amazon's new APS are built on lambda. >>Yeah, that's good. This >>is a new generation of developers. >>Oh, absolutely. I mean, you should talk to the Lambda today also, but even like even in the container side, almost half of the new container customers that we have on AWS in 2020 have chosen target, which is serverless containers. They're not picking E c s or E. T. S and running at least two. They're running it on target the vast majority of those two PCs, but we see that trend on the container side as well, and actually it's accelerating. More and more and more new customers will pick target, then running containers on the city. >>Deepak, great to chat with you. I know you gotta go. Thanks for coming on our program. Breaking down the keynote analysis. You've got a great, um, focus area is only going to get hotter and grow faster and a lot more controversy and goodness coming at the same time. So congratulations. >>Thank you. And always good to be here. >>Thanks for coming on. This is the Cube Virtual. We are the Cube. Virtual. I'm John for your host. Thanks for watching.