(soft techno upbeat music) >> Hi there. Welcome back to Las Vegas. This is Dave Villante with Paul Gillon. Reinvent day one and a half. We started last night, Monday, theCUBE after dark. Now we're going wall to wall. Today. Today was of course the big keynote, Adam Selipsky, kind of the baton now handing, you know, last year when he did his keynote, he was very new. He was sort of still getting his feet wet and finding his guru swing. Settling in a little bit more this year, learning a lot more, getting deeper into the tech, but of course, sharing the love with other leaders like Peter DeSantis. Tomorrow's going to be Swamy in the keynote. Adrian Cockcroft is here. Former AWS, former network Netflix CTO, currently an analyst. You got your own firm now. You're out there. Great to see you again. Thanks for coming on theCUBE. >> Yeah, thanks. >> We heard you on at Super Cloud, you gave some really good insights there back in August. So now as an outsider, you come in obviously, you got to be impressed with the size and the ecosystem and the energy. Of course. What were your thoughts on, you know what you've seen so far, today's keynotes, last night Peter DeSantis, what stood out to you? >> Yeah, I think it's great to be back at Reinvent again. We're kind of pretty much back to where we were before the pandemic sort of shut it down. This is a little, it's almost as big as the, the largest one that we had before. And everyone's turned up. It just feels like we're back. So that's really good to see. And it's a slightly different style. I think there were was more sort of video production things happening. I think in this keynote, more storytelling. I'm not sure it really all stitched together very well. Right. Some of the stories like, how does that follow that? So there were a few things there and some of there were spelling mistakes on the slides, you know that ELT instead of ETL and they spelled ZFS wrong and something. So it just seemed like there was, I'm not quite sure just maybe a few things were sort of rushed at the last minute. >> Not really AWS like, was it? It's kind of remind the Patriots Paul, you know Bill Belichick's teams are fumbling all over the place. >> That's right. That's right. >> Part of it may be, I mean the sort of the market. They have a leader in marketing right now but they're going to have a CMO. So that's sort of maybe as lack of a single threaded leader for this thing. Everything's being shared around a bit more. So maybe, I mean, it's all fixable and it's mine. This is minor stuff. I'm just sort of looking at it and going there's a few things that looked like they were not quite as good as they could have been in the way it was put together. Right? >> But I mean, you're taking a, you know a year of not doing Reinvent. Yeah. Being isolated. You know, we've certainly seen it with theCUBE. It's like, okay, it's not like riding a bike. You know, things that, you know you got to kind of relearn the muscle memories. It's more like golf than is bicycle riding. >> Well I've done AWS keynotes myself. And they are pretty much scrambled. It looks nice, but there's a lot of scrambling leading up to when it actually goes. Right? And sometimes you can, you sometimes see a little kind of the edges of that, and sometimes it's much more polished. But you know, overall it's pretty good. I think Peter DeSantis keynote yesterday was a lot of really good meat there. There was some nice presentations, and some great announcements there. And today I was, I thought I was a little disappointed with some of the, I thought they could have been more. I think the way Andy Jesse did it, he crammed more announcements into his keynote, and Adam seems to be taking sort of a bit more of a measured approach. There were a few things he picked up on and then I'm expecting more to be spread throughout the rest of the day. >> This was more poetic. Right? He took the universe as the analogy for data, the ocean for security. Right? The Antarctic was sort of. >> Yeah. It looked pretty, >> yeah. >> But I'm not sure that was like, we're not here really to watch nature videos >> As analysts and journalists, You're like, come on. >> Yeah, >> Give it the meat >> That was kind the thing, yeah, >> It has always been the AWS has always been Reinvent has always been a shock at our approach. 100, 150 announcements. And they're really, that kind of pressure seems to be off them now. Their position at the top of the market seems to be unshakeable. There's no clear competition that's creeping up behind them. So how does that affect the messaging you think that AWS brings to market when it doesn't really have to prove that it's a leader anymore? It can go after maybe more of the niche markets or fix the stuff that's a little broken more fine tuning than grandiose statements. >> I think so AWS for a long time was so far out that they basically said, "We don't think about the competition, we are listen to the customers." And that was always the statement that works as long as you're always in the lead, right? Because you are introducing the new idea to the customer. Nobody else got there first. So that was the case. But in a few areas they aren't leading. Right? You could argue in machine learning, not necessarily leading in sustainability. They're not leading and they don't want to talk about some of these areas and-- >> Database. I mean arguably, >> They're pretty strong there, but the areas when you are behind, it's like they kind of know how to play offense. But when you're playing defense, it's a different set of game. You're playing a different game and it's hard to be good at both. I think and I'm not sure that they're really used to following somebody into a market and making a success of that. So there's something, it's a little harder. Do you see what I mean? >> I get opinion on this. So when I say database, David Foyer was two years ago, predicted AWS is going to have to converge somehow. They have no choice. And they sort of touched on that today, right? Eliminating ETL, that's one thing. But Aurora to Redshift. >> Yeah. >> You know, end to end. I'm not sure it's totally, they're fully end to end >> That's a really good, that is an excellent piece of work, because there's a lot of work that it eliminates. There's are clear pain points, but then you've got sort of the competing thing, is like the MongoDB and it's like, it's just a way with one database keeps it simple. >> Snowflake, >> Or you've got on Snowflake maybe you've got all these 20 different things you're trying to integrate at AWS, but it's kind of like you have a bag of Lego bricks. It's my favorite analogy, right? You want a toy for Christmas, you want a toy formula one racing car since that seems to be the theme, right? >> Okay. Do you want the fully built model that you can play with right now? Or do you want the Lego version that you have to spend three days building. Right? And AWS is the Lego technique thing. You have to spend some time building it, but once you've built it, you can evolve it, and you'll still be playing those are still good bricks years later. Whereas that prebuilt to probably broken gathering dust, right? So there's something about having an vulnerable architecture which is harder to get into, but more durable in the long term. And so AWS tends to play the long game in many ways. And that's one of the elements that they do that and that's good, but it makes it hard to consume for enterprise buyers that are used to getting it with a bow on top. And here's the solution. You know? >> And Paul, that was always Andy Chassy's answer to when we would ask him, you know, all these primitives you're going to make it simpler. You see the primitives give us the advantage to turn on a dime in the marketplace. And that's true. >> Yeah. So you're saying, you know, you take all these things together and you wrap it up, and you put a snowflake on top, and now you've got a simple thing or a Mongo or Mongo atlas or whatever. So you've got these layered platforms now which are making it simpler to consume, but now you're kind of, you know, you're all stuck in that ecosystem, you know, so it's like what layer of abstractions do you want to tie yourself to, right? >> The data bricks coming at it from more of an open source approach. But it's similar. >> We're seeing Amazon direct more into vertical markets. They spotlighted what Goldman Sachs is doing on their platform. They've got a variety of platforms that are supposedly targeted custom built for vertical markets. How do successful do you see that play being? Is this something that the customers you think are looking for, a fully integrated Amazon solution? >> I think so. There's usually if you look at, you know the MongoDB or data stacks, or the other sort of or elastic, you know, they've got the specific solution with the people that really are developing the core technology, there's open source equivalent version. The AWS is running, and it's usually maybe they've got a price advantage or it's, you know there's some data integration in there or it's somehow easier to integrate but it's not stopping those companies from growing. And what it's doing is it's endorsing that platform. So if you look at the collection of databases that have been around over the last few years, now you've got basically Elastic Mongo and Cassandra, you know the data stacks as being endorsed by the cloud vendors. These are winners. They're going to be around for a very long time. You can build yourself on that architecture. But what happened to Couch base and you know, a few of the other ones, you know, they don't really fit. Like how you going to bait? If you are now becoming an also ran, because you didn't get cloned by the cloud vendor. So the customers are going is that a safe place to be, right? >> But isn't it, don't they want to encourage those partners though in the name of building the marketplace ecosystem? >> Yeah. >> This is huge. >> But certainly the platform, yeah, the platform encourages people to do more. And there's always room around the edge. But the mainstream customers like that really like spending the good money, are looking for something that's got a long term life to it. Right? They're looking for a long commitment to that technology and that it's going to be invested in and grow. And the fact that the cloud providers are adopting and particularly AWS is adopting some of these technologies means that is a very long term commitment. You can base, you know, you can bet your future architecture on that for a decade probably. >> So they have to pick winners. >> Yeah. So it's sort of picking winners. And then if you're the open source company that's now got AWS turning up, you have to then leverage it and use that as a way to grow the market. And I think Mongo have done an excellent job of that. I mean, they're top level sponsors of Reinvent, and they're out there messaging that and doing a good job of showing people how to layer on top of AWS and make it a win-win both sides. >> So ever since we've been in the business, you hear the narrative hardware's going to die. It's just, you know, it's commodity and there's some truth to that. But hardware's actually driving good gross margins for the Cisco's of the world. Storage companies have always made good margins. Servers maybe not so much, 'cause Intel sucked all the margin out of it. But let's face it, AWS makes most of its money. We know on compute, it's got 25 plus percent operating margins depending on the seasonality there. What do you think happens long term to the infrastructure layer discussion? Okay, commodity cloud, you know, we talk about super cloud. Do you think that AWS, and the other cloud vendors that infrastructure, IS gets commoditized and they have to go up market or you see that continuing I mean history would say that still good margins in hardware. What are your thoughts on that? >> It's not commoditizing, it's becoming more specific. We've got all these accelerators and custom chips now, and this is something, this almost goes back. I mean, I was with some micro systems 20,30 years ago and we developed our own chips and HP developed their own chips and SGI mips, right? We were like, the architectures were all squabbling of who had the best processor chips and it took years to get chips that worked. Now if you make a chip and it doesn't work immediately, you screwed up somewhere right? It's become the technology of building these immensely complicated powerful chips that has become commoditized. So the cost of building a custom chip, is now getting to the point where Apple and Amazon, your Apple laptop has got full custom chips your phone, your iPhone, whatever and you're getting Google making custom chips and we've got Nvidia now getting into CPUs as well as GPUs. So we're seeing that the ability to build a custom chip, is becoming something that everyone is leveraging. And the cost of doing that is coming down to startups are doing it. So we're going to see many, many more, much more innovation I think, and this is like Intel and AMD are, you know they've got the compatibility legacy, but of the most powerful, most interesting new things I think are going to be custom. And we're seeing that with Graviton three particular in the three E that was announced last night with like 30, 40% whatever it was, more performance for HPC workloads. And that's, you know, the HPC market is going to have to deal with cloud. I mean they are starting to, and I was at Supercomputing a few weeks ago and they are tiptoeing around the edge of cloud, but those supercomputers are water cold. They are monsters. I mean you go around supercomputing, there are plumbing vendors on the booth. >> Of course. Yeah. >> Right? And they're highly concentrated systems, and that's really the only difference, is like, is it water cooler or echo? The rest of the technology stack is pretty much off the shelf stuff with a few tweets software. >> You point about, you know, the chips and what AWS is doing. The Annapurna acquisition. >> Yeah. >> They're on a dramatically different curve now. I think it comes down to, again, David Floyd's premise, really comes down to volume. The arm wafer volumes are 10 x those of X 86, volume always wins. And the economics of semis. >> That kind of got us there. But now there's also a risk five coming along if you, in terms of licensing is becoming one of the bottlenecks. Like if the cost of building a chip is really low, then it comes down to licensing costs and do you want to pay the arm license And the risk five is an open source chip set which some people are starting to use for things. So your dis controller may have a risk five in it, for example, nowadays, those kinds of things. So I think that's kind of the the dynamic that's playing out. There's a lot of innovation in hardware to come in the next few years. There's a thing called CXL compute express link which is going to be really interesting. I think that's probably two years out, before we start seeing it for real. But it lets you put glue together entire rack in a very flexible way. So just, and that's the entire industry coming together around a single standard, the whole industry except for Amazon, in fact just about. >> Well, but maybe I think eventually they'll get there. Don't use system on a chip CXL. >> I have no idea whether I have no knowledge about whether going to do anything CXL. >> Presuming I'm not trying to tap anything confidential. It just makes sense that they would do a system on chip. It makes sense that they would do something like CXL. Why not adopt the standard, if it's going to be as the cost. >> Yeah. And so that was one of the things out of zip computing. The other thing is the low latency networking with the elastic fabric adapter EFA and the extensions to that that were announced last night. They doubled the throughput. So you get twice the capacity on the nitro chip. And then the other thing was this, this is a bit technical, but this scalable datagram protocol that they've got which basically says, if I want to send a message, a packet from one machine to another machine, instead of sending it over one wire, I consider it over 16 wires in parallel. And I will just flood the network with all the packets and they can arrive in any order. This is why it isn't done normally. TCP is in order, the packets come in order they're supposed to, but this is fully flooding them around with its own fast retry and then they get reassembled at the other end. So they're not just using this now for HPC workloads. They've turned it on for TCP for just without any change to your application. If you are trying to move a large piece of data between two machines, and you're just pushing it down a network, a single connection, it takes it from five gigabits per second to 25 gigabits per second. A five x speed up, with a protocol tweak that's run by the Nitro, this is super interesting. >> Probably want to get all that AIML that stuff is going on. >> Well, the AIML stuff is leveraging it underneath, but this is for everybody. Like you're just copying data around, right? And you're limited, "Hey this is going to get there five times faster, pushing a big enough chunk of data around." So this is turning on gradually as the nitro five comes out, and you have to enable it at the instance level. But it's a super interesting announcement from last night. >> So the bottom line bumper sticker on commoditization is what? >> I don't think so. I mean what's the APIs? Your arm compatible, your Intel X 86 compatible or your maybe risk five one day compatible in the cloud. And those are the APIs, right? That's the commodity level. And the software is now, the software ecosystem is super portable across those as we're seeing with Apple moving from Intel to it's really not an issue, right? The software and the tooling is all there to do that. But underneath that, we're going to see an arms race between the top providers as they all try and develop faster chips for doing more specific things. We've got cranium for training, that instance has they announced it last year with 800 gigabits going out of a single instance, 800 gigabits or no, but this year they doubled it. Yeah. So 1.6 terabytes out of a single machine, right? That's insane, right? But what you're doing is you're putting together hundreds or thousands of those to solve the big machine learning training problems. These super, these enormous clusters that they're being formed for doing these massive problems. And there is a market now, for these incredibly large supercomputer clusters built for doing AI. That's all bandwidth limited. >> And you think about the timeframe from design to tape out. >> Yeah. >> Is just getting compressed It's relative. >> It is. >> Six is going the other way >> The tooling is all there. Yeah. >> Fantastic. Adrian, always a pleasure to have you on. Thanks so much. >> Yeah. >> Really appreciate it. >> Yeah, thank you. >> Thank you Paul. >> Cheers. All right. Keep it right there everybody. Don't forget, go to thecube.net, you'll see all these videos. Go to siliconangle.com, We've got features with Adam Selipsky, we got my breaking analysis, we have another feature with MongoDB's, Dev Ittycheria, Ali Ghodsi, as well Frank Sluman tomorrow. So check that out. Keep it right there. You're watching theCUBE, the leader in enterprise and emerging tech, right back. (soft techno upbeat music)

>>Hello everyone. Welcome back to the Cube Live, AWS Reinvent 2022. This is our first day of three and a half days of wall to wall coverage on the cube. Lisa Martin here with Dave Valante. Dave, it's getting louder and louder behind us. People are back. They're excited. >>You know what somebody told me today? Hm? They said that less than 15% of the audience is developers. I'm like, no way. I don't believe it. But now maybe there's a redefinition of developers because it's all about the data and it's all about the developers in my mind. And that'll never change. >>It is. And one of the things we're gonna be talking about is app modernization. As customers really navigate the journey to do that so that they can be competitive and, and meet the demands of customers. We've got an alumni back with us to talk about that. AJ Patel joins us, the SVP and GM Modern Apps and Management business group at VMware. Aj, welcome back. Thank >>You. It's always great to be here, so thank you David. Good to see >>You. Isn't great. It's great to be back in person. So the VMware Tansu team here back at Reinvent on the Flow Shore Flow show floor. There we go. Talk about some of the things that you guys are doing together, innovating with aws. >>Yeah, so it's, it's great to be back after in person after multiple years and the energy level continues to amaze me. The partnership with AWS started on the infrastructure side with VMware cloud on aws. And when with tanza, we're extending it to the application space. And the work here is really about how do you make developers productive To your earlier point, it's all about developers. It's all about getting applications in production securely, safely, continuously. And tanza is all about making that bridge between great applications being built, getting them deployed and running, running and operating at scale. And EKS is a dominant Kubernetes platform. And so the better together story of tanu and EKS is a great one for us, and we're excited to announce some sort of innovations in that area. >>Well, Tanu was so front and center at VMware Explorer. I wasn't at in, in VMware Explorer, Europe. Right. But I'm sure it was a similar kind of focus. When are customers choosing Tanu? Why are they choosing Tanu? What's, what's, what's the update since last August when >>We, you know, the market settled into three main use cases. One is all about developer productivity. You know, consistently we're all dealing with skill set gap issues. How do we make every developer productive, modern developer? And so 10 is all about enabling that develop productivity. And we can talk quite a bit about it. Second one is security's front and center and security's being shifted left right into how you build great software. How do you secure that through the entire supply chain process? And how do you run and operationalize secure at runtime? So we're hearing consistently about making secure software supply chain heart of what our solution is. And third one is, how do I run and operate the modern application at scale across any Kubernetes, across any cloud? These are the three teams that are continuing to get resonance and empowering. All of this is exciting. David is this formation of platform teams. I just finished a study with Bain Consulting doing some research for me. 40% of our organization now have some form of a central team that's responsive for, for we call platform engineering and building platforms to make developers productive. That is a big change since about two years ago even. So this is becoming mainstream and customers are really focusing on delivering in value to making developers productive. >>Now. And, and, and the other nuance that I see, and you kinda see it here in the ecosystem, but when you talk about your customers with platform engineering, they're actually building their, they're pointing their business. They gonna page outta aws, pointing their businesses to their customers, right? Becoming software companies, becoming cloud companies and really generating new forms of revenue. >>You know, the interesting thing is, some of my customers I would never have thought as leading edge are retailers. Yeah. And not your typical Starbucks that you get a great example. I have an auto parts company that's completely modernizing how they deliver point of sale all the way to the supply chain. All built on ES at scale. You're typically think of that a financial services or a telco leading the pack. But I'm seeing innovation in India. I'm seeing the innovation in AMEA coming out of there, across the board. Every industry is becoming a product company. A digital twin as we would call it. Yeah. And means they become software houses. Yeah. They behave more like you and I in this event versus a, a traditional enterprise. >>And they're building their own ecosystems and that ecosystem's generating data that's generating more value. And it's just this cycle. It's, >>It's a amazing, it's a flywheel. So innovation continues to grow. Talk about really unlocking the developer experience and delivering to them what they need to modernize apps to move as fast and quickly as they want to. >>So, you know, I think AWS coin this word undifferentiated heavy lifting. If you think of a typical developer today, how much effort does he have to put in before he can get a single line of code out in production? If you can take away all the complexity, typically security compliance is a big headache for them, right? Developer doesn't wanna worry about that. Infrastructure provisioning, getting all the configurations right, is a headache for them. Being able to understand what size of infrastructure or resource to use cost effectively. How do you run it operationally? Cuz the application team is responsible for the operational cost of the product or service. So these are the un you know, heavy lifting that developers want to get away from. So they wanna write great code, build great experiences. And we've always talked about frameworks a way to abstract with the complexity. And so for us, there's a massive opportunity to say, how do I simplify and take away all the heavy lifting to get an idea into production seamlessly, continuously, securely. >>Is that part of your partnership? Because you think about a aws, they're really not about frameworks, they're about primitives. I mean, Warner Vos even talks about that in his, in his speech, you know, but, but that makes it more challenging for developers. >>No, actually, if you look at some of their initial investments around proton and et cetera work, they're starting to do, they're recognized, you know, PS is a bad, bad word, but the outcomes a platform as a service offers is what everybody wants. Just talking to the AWS leaders, responsible area, he actually has a separate build team. He didn't know what to call the third team. He has a Kubernetes team, he has a serverless team and has a build team. And that build team is everything above Kubernetes to make the developer productive. Right. And the ecosystem to bring together to make that happen. So I think AWS is recognizing that primitives are great for the elite developers, but if they want to get the mass scale and adoption in the business, it, if you will, they're gonna have to provide richer set of building blocks and reduce the complex and partnership like ours. Make that a reality. And what I'm excited about is there's a clear gap here, and t's the best platform to kind of fill that gap. Well, >>And I, I think that, you know, they're gonna double down triple, I just wrote about this double down, triple down on the primitives. Yes. They have to have the best, you know, servers and storage and database. And I think the way they, they, I call it taping the seams is with the ecosystem. Correct. You know, and they, nobody has a, a better ecosystem. I mean, you guys are, you know, the, the postage child for the ecosystem and now this even exceeds that. But partnering up, that's how they >>Continue to, and they're looking for someone who's open, right? Yeah. Yeah. And so one of the first question is, you know, are you proprie or open? Because one of the things they're fighting against is the lock in. So they can find a friendly partner who is open source, led, you know, upstream committing to the code, delivering that innovation, and bring the ecosystem into orchestrated choreography. It's like singing a music, right? They're running a, running an application delivery team is like running a, a musical orchestra. There's so many moving parts here, right? How do you make them sing together? And so if Tan Zoo and our platform can help them sing and drive more of their services, it's only more valuable for them. And >>I think the partners would generally say, you know, AWS always talking about customer obsession. It's like becomes this bromine, you go, yeah, yeah. But I actually think in the field, the the sellers would say, yeah, we're gonna do what the customer, if that means we're gonna partner up. Yeah. And I think AWS's comp structure makes it sort >>Of, I learned today how, how incentives with marketplaces work. Yeah. And it is powerful. It's very powerful. Yeah. Right. So you line up the sales incentive, you line up the customer and the benefits, you line up bringing the ecosystem to drive business results and everybody, and so everybody wins. And which is what you're seeing here, the excitement and the crowd is really the whole, all boats are rising. Yeah. Yeah. Right, right. And it's driven by the fact that customers are getting true value out of it. >>Oh, absolutely. Tremendous value. Speaking of customers, give us an example of a customer story that you think really articulates the value of what Tanzi was delivering, especially making that developer experience far simpler. What are some of those big business outcomes that that delivers? >>You know, at Explorer we had the CIO of cvs and with their acquisition of Aetna and CVS Health, they're transforming the, the health industry. And they talked about the whole covid and then how they had to deliver the number of, you know, vaccines to u i and how quickly they had to deliver on that. It talked about Tanu and how they leverage, leverage a Tanza platform to get those new applications out and start to build that. And Ro was basically talking about his number one prior is how does he get his developers more productive? Number to priority? How does he make sure the apps are secure? Number three, priority, how does he do it cost effectively in the world? Particularly where we're heading towards where, you know, the budgets are gonna get tighter. So how do I move more dollars to innovation while I continue to drive more efficiency in my platform? And so cloud is the future. How does he make the best use of the cloud both for his developers and his operations team? Right? >>What's happening in serverless, I, in 2017, Andy Chassy was in the cube. He said if AWS or if Amazon had to build all over again, they would build in, in was using serverless. And that was a big quote. We've mined that for years. And as you were talking about developer productivity, I started writing down all the things developers have to do. Yep. With it, they gotta, they gotta build a container image. They said they gotta deploy an EC two instance. They gotta allocate memory, they gotta fence off the apps in a virtual machine. They gotta run the, you know, compute against the app goes, they gotta pay for all that. So, okay, what's your story on, what's the market asking for in terms of serverless? Because there's still some people who want control over the run time. Help us sift through that. >>And it really comes back to the application pattern or the type you're running. If it's a stateless application that you need to spin up and spin down. Serverless is awesome. Why would I wanna worry about scaling it up in, I wanna set up some SLAs, SLIs service level objectives or, or, or indicators and then let the systems bring the resources I need as I need them. That's a perfect example for serverless, right? On the other hand, if you have a, a more of a workflow type application, there's a sequence, there's state, try building an application using serverless where you had to maintain state between two, two steps in the process. Not so much fun, right? So I don't think serverless is the answer for everything, but many use cases, the scale to zero is a tremendous benefit. Events happen. You wanna process something, work is done, you quietly go away. I don't wanna shut down the server started up, I want that to happen magically. So I think there's a role of serverless. So I believe Kubernetes and servers are the new runtime platform. It's not one or the other. It's about marrying that around the application patterns. I DevOps shouldn't care about it. That's an infrastructure concern. Let me just run application, let the infrastructure manage the operations of it, whether it's serverless, whether it's Kubernetes clusters, whether it's orchestration, that's details right. I I I shouldn't worry about it. Right. >>So we shouldn't think of those as separate architectures. We should think of it as an architecture, >>The continuum in some ways Yeah. Of different application workload types. And, and that's a toolkit that the operator has at his disposal to configure and saying, where does, should that application run? Should I want control? You can run it on a, a conveyance cluster. Can I just run it on a serverless infrastructure and and leave it to the cloud provider? Do it all for me. Sure. What, what was PAs? PAs was exactly that. Yeah. Yeah. Write the code once you do the rest. Yeah. Okay. Those are just elements of that. >>And then K native is kinda in the middle, >>Right? K native is just a technology that's starting to build that capability out in a standards way to make serverless available consistently across all clouds. So I'm not building to a, a lambda or a particular, you know, technology type. I'm building it in a standard way, in a standard programming model. And infrastructure just >>Works for me on any cloud. >>The whole idea portability. Consistency. >>Right. Powerful. Yep. >>What are some of the things that, that folks can expect to learn from VMware Tan to AWS this week at the >>Show? Yeah, so there's some really great announcements. First of all, we're excited to extend our, our partnership with AWS in the area of eks. What I mean by that is we traditionally, we would manage an EKS cluster, you visibility of what's running in there, but we weren't able to manage the lifecycle With this announcement. We can give you a full management of lifecycle of S workloads. Our customers have 400 plus EKS clusters, multiple teams sharing those in a multi-tenanted way with common policy. And they wanna manage a full life cycle, including all the upstream open source component that make up Kubernetes people. That ES is the one thing, it's a collection of a lot of open, open source packages. We're making it simple to manage it consistently from a single place on the security front. We're now making tons of service mesh available in the marketplace. >>And if you look at what service MeSHs, it's an overlay. It's an abstraction. I can create an idea of a global name space that cuts across multiple VPCs. I'm, I'm hearing at Amazon's gonna make some announcements around VPC and how they stitch VPCs together. It's all moving towards this idea of abstractions. I can set policy at logical level. I don't have to worry about data security and the communication between services. These are the things we're now enabling, which are really an, and to make EKS even more productive, making enterprise grade enterprise ready. And so a lot of excitement from the EKS development teams as well to partner closely with us to make this an end to end solution for our >>Customers. Yeah. So I mean it's under chasy, it was really driving those primitives and helping developers under continuing that path, but also recognizing the need for solutions. And that's where the ecosystem comes in, >>Right? And the question is, what is that box? As you said last time, right? For the super cloud, there is a cloud infrastructure, which is becoming the new palette, but how do you make sense of the 300 plus primitives? How do you bring them together? What are the best practices, patterns? How do I manage that when something goes wrong? These are real problems that we're looking to solve. >>And if you're gonna have deeper business integration with the cloud and technology in general, you have to have that >>Abstraction. You know, one of the simple question I ask is, how do you know you're getting value from your cloud investment? That's a very hard question. What's your trade off between performance and cost? Do you know where your security, when a lock 4G happens, do you know all the open source packages you need to patch? These are very simple questions, but imagine today having to do that when everybody's doing in a bespoke manner using the set of primitives. You need a platform. The industry is shown at scale. You have to start standardizing and building a consistent way of delivering and abstracting stuff. And that's where the next stage of the cloud journey >>And, and with the economic environment, I think people are also saying, okay, how do we get more? Exactly. We're in the cloud now. How do we get more? How do we >>Value out of the cloud? >>Exactly. Totally. >>How do we transform the business? Last question, AJ for you, is, if you had a bumper sticker and you're gonna put it on your fancy car, what would it say about VMware tan zone aws? >>I would say tan accelerates apps. >>Love >>It. Thank you so much. >>Thank you. Thank you so much for joining us. >>Appreciate it. Always great to be here. >>Pleasure. Likewise. For our guest, I'm Dave Ante. I'm Lisa Martin. You're watching The Cube, the leader in emerging and enterprise tech coverage.

>> [Narrator] From San Francisco, it's theCUBE. Covering Radio 2018, brought to you by VMware. >> Hey, welcome back everyone. This is theCUBE's exclusive coverage of Radio 2018. We are in San Francisco for their VMware's Radio 2018. It's their R&D fiesta, party. As Steve Harris said, former CTO, it's like a sales kickoff for engineers. It's a great time, but it's also serious. A lot of real serious discussion and of course people are flexing their technical muscle and stretching their minds. And I'm here with one of the chief operator, one of the main principals and legend in VMware, Raghu Raghuram. Chief Operating Officer, new title. Chief Operating Officer, Products and Cloud Services. >> That's right. >> Great to see you. >> Great to see you, John. >> What year did you join VMware? >> 2003 (chuckling) >> 15 years >> So, you've seen many of these radios. >> Yes, it's one of the highlights of the year for me. >> Yeah, super important architect of VMware, great part of the community, leader, architect of the AWS relationship. >> [Raghu] Sure >> Part of that movement with Andy Jassy, Sanjay Poonen. This is the 14th year of radio and VMware has changed a lot since you joined. It's now a world class organization. Getting check marks for one of the best places to work. Certainly for engineers it's like a great party environment. Take a minute to explain the radio culture, it's 14th year, there's t-shirts behind us, to commemorate the key milestones, where it's come from, where it's gone, your thoughts on the program and the community. >> Yeah, I mean this is in fact one of the unique characteristics of VMware. I have checked around with my peers in the industry and I don't think any other tech company of our size does this. Radio stands for R&D innovation offsite. Like you said, we started fourteen years ago just to take a bunch of engineers out from their daily grinds and say, "what could we be building fundamentally that's groundbreaking?" So, I would say it's a cross between a wild science fair and a research conference. In fact, both of these go hand in hand at this place. People publish papers and there is a selection committee just like in serious conferences. In fact, Ray had some amazing stats for this year's submissions and the selection is very very rigorous. At the same time, you'll go upstairs and you'll see the exhibition hall where there are all kinds of things that are displayed. Things that could be very well incremental things in the next release and things that are wild and wacky off the wall that we might never ever do. So, it's really the full gamut. Another interesting thing is we've gone bigger. We are getting people from pretty much all parts of the Emirate. I think there is representation from 25 companies. >> [John] How many engineering centers are there roughly? I mean, there's core centers and then you have engineers all over the world. How many engineers, ballpark? >> I would say, in terms of medium to big size centers, there are probably over a dozen across the globe and literally every continent. Clearly, in the US we have four big centers. In Europe, we have three at least. In Asia, we have another three or four. So, we definitely have over 10. >> I mean everyone who knows the VMware and also knows theCUBE, for nine years, well this is our ninth year covering VMworld, all you gotta do is look at VMworld and you can tell one thing right out of the gate. Very community oriented. All the decisions are made in the community. Also, people who know VMware know you're highly an engineering organization. >> [Raghu] Yep. >> This is not like a lot of marketing fluff. Although, you do have some good marketing here and there, but the point is it's an engineering culture with community. This is unique. I've seen companies that don't walk the talk on "community engineering". They have silos, there's a lot of infighting. How have you- How has VMware preserved a culture of innovation amongst their peers when it's competitive as hell inside VMware? One to be smart, achieve the success. But, also, VMware has always been in always a moving market. How do you guys do it? What's the secret sauce? >> I mean, there's not a single thing. Like you said, culture is something that happens over time and is preserved over time and is preserved through people. It's not like anything you can write down, right? Of course you can write it down. But, it won't be worth the paper it's written down on unless it's practiced everyday by other people. And so, I think that is the key thing here. Right from the get go, customer centric innovation has ruled the rules here. So, the question to ask always is great innovation, look at it from a customer end point of view. I think that matters a lot here. Secondly, there is a lot of emphasis on breaking the rules in terms of doing something disruptive, right? And, the engineers that come here tend to be the kind to respond to that, right? And then lots of venues. Like this is not the only thing that we do, right? We do these things called borathons, which is our internal version of hackathons. We do regional versions of these things. Each of the teams, like the business units, have their own little R&D innovation activities that go on. >> They have a playground. They can basically go outside the scope of their job. >> Exactly. >> Get an idea, a passion, an idea and go after it and not have to worry about anything. >> Yup, exactly. >> [John] With a path to commercialization, if it hits. >> Yeah, that's what I was gonna say. We have a fairly high success rate, I would say, of taking things that we see here and turning them into product and eventually into monetizable businesses. All the things that go into the product features. >> Give some examples of historically, successes, notables, and then also talk about some ones that aren't notable that have come out. I know a lot has come out of this, the numbers are clear. What are some highlights that have come out of the radio event that have been blockbuster successes? >> A lot of the things that you see in the networking today came out of radio. Things about doing security and networking from the hypervisor up, came from here. What you see today as vSAN, had its roots here. What you see today with the app defense and the security stuff, had its roots here. A lot of the features that are in vSphere today, especially the storage vMotion and so on and so forth, was first showcased here. This goes on and on and on. We also have a lot of things that have shown up here that we have not pursued. For example, almost like an eBay for VM capacity. We didn't pursue it. God knows, that could've been a huge idea. (laughing) >> It's the misses too. >> Yeah, there's the misses too. But, that's the whole point of this. >> Yeah. There's parts to creativity. How much creativity goes on at this event? I mean there's certainly a lot of barnstorming, brainstorming, or whatever you wanna call it. A lot of interaction, physical face to face. How much creativity is happening you think here? >> Yeah, so a few years back they introduced a couple of things. One is a instant birds of a feather. Where you can literally go to a whiteboard and say, "hey let's discuss this topic," and set up a time and then people show up. There's this other one they call Lightning Rounds, which literally happens over drinks I think tomorrow or something. Where people come in and it's lots of the mini gauntlet where nothing is scripted. All sorts of crazy ideas keep flowing. I would say those are two examples where there's a lot of on the spot creativity. As a company, the R&D teams have gotten more dispersed. This is the opportunity for people to get together even within the same business unit or across business units and say let's go solve this problem. You and I have been talking about this on email, let's talk about it face to face. Hey, let's bring somebody else in that's relevant to this conversation as well. So, those are the kind of things that go on here that spark the creativity. And then of course, the exhibits. When people start thinking about these exhibits and talking to people that are showing there, other ideas get spawned off as well. >> Raghu, talk about just from your experience, you got a great track record, and certainly it was in VMware, it goes back to the early 2000s. What is your observation on the innovation formula? What's been the consistent constant of innovation? As the waves have changed- I mean, I've been in Palo Alto for 19 years now, in my 20th year. Even Palo Alto's changed. So, the world's changed, modern. And we'll get to the Amazon deal in a second. Certainly cloud's here. What have you seen as the constant innovation variable? >> What I would say is this. Fundamentally the people that we tend to recruit into VMware are by large what we call, or at least I call, platform thinkers. So, they think of building a fundamental piece of technology that can be possibly be used in 10 different ways, and they build it for one particular use case. And then, the questions goes back to, now we've done this, what else can we do with this foundational technology? If you look at vSphere, does the same thing. If you look at networking, same thing. Storage is the same thing. So, I would say that is the constant. That's one constant here. Which is, how do you build fundamentally a platform that could be used in very different ways. >> Some will also say systems thinking. >> Exactly, so that's a compliment. >> The cloud is a system. >> (mumbles) I think Paul Maritz is a 2010 picture. Although, some of the calls didn't come out. He kind of generally had the architecture. >> Yeah, yeah >> He nailed it (laughs) >> There are a few people like Paul in the world and absolutely he nailed it. >> Dave and I would give him a lot of credit for that. Okay, let's talk about Amazon Web Services. Certainly Radio's now 14th year. At what point did the cloud start clicking in? You said there's some misses, the eBay for VMs. Certainly cloud is on the radar. >> Yeah >> And vCloud, we know what happened there. Pat talked about how you guys really took that opportunity, which is, you made lemonade out of some lemons there with that product. That's my words, not his. When did cloud first appear on the horizon in Radio and how do you see that happening now as we talk multi-cloud? >> You missed the alumni session today. One of the early engineers said when he was interviewed by Mendel, which was in 1999, Mendel is of course the founder and first chief scientist here. He said he foresaw the event. When the engineer asked him, "how are we gonna make money on this?" He thought there would be a day when people just rent computer capacity from a data center instead of going out and buying gear. In some ways- >> He predicted >> He predicted >> Cloud operations >> Back in the company's starting days. But really I think we saw this in 2005, 2006, 2007. At the same time actually as Amazon saw this. But, the big difference was we were growing 100% a year on core business and we had our hands full that way. We felt like as a software company the way to play it was by delivering technology to other people to build it. So, that's when it really made it's way here, in Radio and in the products. >> And by the way, it wasn't obvious to many people in the industry at that time, to Amazon. I've had many conversations with Andy Chassy and he now uses the term being misunderstood. They were completely misunderstood unless you were an entrepreneur who was using EC-2 just to avoid seed money. 'Cause it was a dream for entrepreneur's at that time. I remember that clearly. That was not obvious. It really wasn't obvious until about 2010, nine, 10. So you guys were growing. Missed that. Radio is not about missing it. It's about identifying. >> Exactly. >> So, how does it translate today for Amazon? >> The Amazon relationship, if you think about the technical underpinnings of it, clearly we did a vCloud error. We learned a lot on that. Within some of our engineers, the question that was asked was, "what if we could run a cloud on top of other peoples clouds?" And we did experiments with nested virtualization. We did experiments with bare metal. And then we chose the start of our model. So, that's one of the technical early indicators of what we could do on other people's clouds. So, that's a big thing. The rest of the things we're doing with respect to elastically growing capacity and all those things, came from experiments that were shown up here. So, that was the connection back to Radio. In terms of the Amazon partnership itself, a lot of it was driven from the customer end. As we were thinking about VCN not working the way we wanted it to work, we went back to the customers and said, "what is wrong with this picture?" And, the answer that came back was very clear. They said, we like the hybrid idea, but we want the hybrid to be VMware on prem and Amazon in the cloud because 70% of our customers turned out to be AWS customers. And at the same time AWS was hearing the same thing. Why don't you guys team up instead of being either or? That's what led to the partnership. >> Your team at VMware came as the cloud native piece? >> Yeah >> Aspect of it. So Kubernetes is on the horizon. Not on the horizon, in your face. And you've got service mesh over the top. >> Yep, yep >> That's up the stack. It's networking. >> Yep, exactly. >> Still needs to do networking. >> Yeah, exactly. >> It's like, you guys must be like, hey we love what's going on up there. Come down to the store. >> Yeah. So, the boundary between what is application platform and infrastructure platform is constantly changing. Kubernetes, when it started out people said oh it's an application platform. Now it turns out its actually infrastructure. Same thing in networking. So what we see is, things were the lower level of the infrastructure constructs, the same idea is applied at the next level up. That's why we love Kubernetes. We love Service Mesh. We love similar concepts that are coming about in storage and security it's one- >> A unified stack is coming. >> Yep, exactly. >> Just someone fix networking and then the holy grail, programmable networks. >> Yep >> When are they coming? >> At the application level. >> Let's go >> Yeah >> Holy grail is finally here. It's not where you thought it was gonna be. >> It is at both places, right. I mean, it's tying back to the conventional layer, two layer, three stuff because that's also important still. >> Raghu, I love having a chat with you. It's great to chat. >> Good to see you again John. >> Super impressive with the work you've been doing. Love the cloud deal with Amazon, you know that. Love what's going on at Kubernetes and containerization. Love what's going on with Service Mesh, unified stack. Love cryptocurrency, which I didn't get to ask you. >> Yep >> Thumbs up? >> Crazy things going on there too >> Thumbs up, okay, thumbs up. >> We're watching the cryptocurrency. >> Watching, token economics coming right behind it. It's theCUBE bringing you all the action here at Radio. We're the signal. 2018, Radio 2018. I'm theCUBE with Raghu. I'll be right back with more coverage after this short break. (upbeat music)