(upbeat music) >> Hey, everyone, welcome back to Las Vegas, "theCube" is on our fourth day of covering AWS re:Invent, live from the Venetian Expo Center. This week has been amazing. We've created a ton of content, as you know, 'cause you've been watching. But, there's been north of 55,000 people here, hundreds of thousands online. We've had amazing conversations across the AWS ecosystem. Lisa Martin, Paul Gillan. Paul, what's your, kind of, take on day four of the conference? It's still highly packed. >> Oh, there's lots of people here. (laughs) >> Yep. Unusual for the final day of a conference. I think Werner Vogels, if I'm pronouncing it right kicked things off today when he talked about asymmetry and how the world is, you know, asymmetric. We build symmetric software, because it's convenient to do so, but asymmetric software actually scales and evolves much better. And I think that that was a conversation starter for a lot of what people are talking about here today, which is how the cloud changes the way we think about building software. >> Absolutely does. >> Our next guest, Holger Mueller, that's one of his key areas of focus. And Holger, welcome, thanks for joining us on the "theCube". >> Thanks for having me. >> What did you take away from the keynote this morning? >> Well, how do you feel on the final day of the marathon, right? We're like 23, 24 miles. Hit the ball yesterday, right? >> We are going strong Holger. And, of course, >> Yeah. >> you guys, we can either talk about business transformation with cloud or the World Cup. >> Or we can do both. >> The World Cup, hands down. World Cup. (Lisa laughs) Germany's out, I'm unbiased now. They just got eliminated. >> Spain is out now. >> What will the U.S. do against Netherlands tomorrow? >> They're going to win. What's your forecast? U.S. will win? >> They're going to win 2 to 1. >> What do you say, 2:1? >> I'm optimistic, but realistic. >> 3? >> I think Netherlands. >> Netherlands will win? >> 2 to nothing. >> Okay, I'll vote for the U.S.. >> Okay, okay >> 3:1 for the U.S.. >> Be optimistic. >> Root for the U.S.. >> Okay, I like that. >> Hope for the best wherever you work. >> Tomorrow you'll see how much soccer experts we are. >> If your prediction was right. (laughs) >> (laughs) Ja, ja. Or yours was right, right, so. Cool, no, but the event, I think the event is great to have 50,000 people. Biggest event of the year again, right? Not yet the 70,000 we had in 2019. But it's great to have the energy. I've never seen the show floor going all the way down like this, right? >> I haven't either. >> I've never seen that. I think it's a record. Often vendors get the space here and they have the keynote area, and the entertainment area, >> Yeah. >> and the food area, and then there's an exposition, right? This is packed. >> It's packed. >> Maybe it'll pay off. >> You don't see the big empty booths that you often see. >> Oh no. >> Exactly, exactly. You know, the white spaces and so on. >> No. >> Right. >> Which is a good thing. >> There's lots of energy, which is great. And today's, of course, the developer day, like you said before, right now Vogels' a rockstar in the developer community, right. Revered visionary on what has been built, right? And he's becoming a little professorial is my feeling, right. He had these moments before too, when it was justifying how AWS moved off the Oracle database about the importance of data warehouses and structures and why DynamoDB is better and so on. But, he had a large part of this too, and this coming right across the keynotes, right? Adam Selipsky talking about Antarctica, right? Scott against almonds and what went wrong. He didn't tell us, by the way, which often the tech winners forget. Scott banked on technology. He had motorized sleds, which failed after three miles. So, that's not the story to tell the technology. Let everything down. Everybody went back to ponies and horses and dogs. >> Maybe goes back to these asynchronous behavior. >> Yeah. >> The way of nature. >> And, yesterday, Swami talking about the bridges, right? The root bridges, right? >> Right. >> So, how could Werner pick up with his video at the beginning. >> Yeah. >> And then talk about space and other things? So I think it's important to educate about event-based architecture, right? And we see this massive transformation. Modern software has to be event based, right? Because, that's how things work and we didn't think like this before. I see this massive transformation in my other research area in other platforms about the HR space, where payrolls are being rebuilt completely. And payroll used to be one of the three peaks of ERP, right? You would size your ERP machine before the cloud to financial close, to run the payroll, and to do an MRP manufacturing run if you're manufacturing. God forbid you run those three at the same time. Your machine wouldn't be able to do that, right? So it was like start the engine, start the boosters, we are running payroll. And now the modern payroll designs like you see from ADP or from Ceridian, they're taking every payroll relevant event. You check in time wise, right? You go overtime, you take a day of vacation and right away they trigger and run the payroll, so it's up to date for you, up to date for you, which, in this economy, is super important, because we have more gig workers, we have more contractors, we have employees who are leaving suddenly, right? The great resignation, which is happening. So, from that perspective, it's the modern way of building software. So it's great to see Werner showing that. The dirty little secrets though is that is more efficient software for the cloud platform vendor too. Takes less resources, gets less committed things, so it's a much more scalable architecture. You can move the events, you can work asynchronously much better. And the biggest showcase, right? What's the biggest transactional showcase for an eventually consistent asynchronous transactional application? I know it's a mouthful, but we at Amazon, AWS, Amazon, right? You buy something on Amazon they tell you it's going to come tomorrow. >> Yep. >> They don't know it's going to come tomorrow by that time, because it's not transactionally consistent, right? We're just making every ERP vendor, who lives in transactional work, having nightmares of course, (Lisa laughs) but for them it's like, yes we have the delivery to promise, a promise to do that, right? But they come back to you and say, "Sorry, we couldn't make it, delivery didn't work and so on. It's going to be a new date. We are out of the product.", right? So these kind of event base asynchronous things are more and more what's going to scale around the world. It's going to be efficient for everybody, it's going to be better customer experience, better employee experience, ultimately better user experience, it's going to be better for the enterprise to build, but we have to learn to build it. So big announcement was to build our environment to build better eventful applications from today. >> Talk about... This is the first re:Invent... Well, actually, I'm sorry, it's the second re:Invent under Adam Selipsky. >> Right. Adam Selipsky, yep. >> But his first year. >> Right >> We're hearing a lot of momentum. What's your takeaway with what he delivered with the direction Amazon is going, their vision? >> Ja, I think compared to the Jassy times, right, we didn't see the hockey stick slide, right? With a number of innovations and releases. That was done in 2019 too, right? So I think it's a more pedestrian pace, which, ultimately, is good for everybody, because it means that when software vendors go slower, they do less width, but more depth. >> Yeah. >> And depth is what customers need. So Amazon's building more on the depth side, which is good news. I also think, and that's not official, right, but Adam Selipsky came from Tableau, right? >> Yeah. So he is a BI analytics guy. So it's no surprise we have three data lake offerings, right? Security data lake, we have a healthcare data lake and we have a supply chain data lake, right? Where all, again, the epigonos mentioned them I was like, "Oh, my god, Amazon's coming to supply chain.", but it's actually data lakes, which is an interesting part. But, I think it's not a surprise that someone who comes heavily out of the analytics BI world, it's off ringside, if I was pitching internally to him maybe I'd do something which he's is familiar with and I think that's what we see in the major announcement of his keynote on Tuesday. >> I mean, speaking of analytics, one of the big announcements early on was Amazon is trying to bridge the gap between Aurora. >> Yep. >> And Redshift. >> Right. >> And setting up for continuous pipelines, continuous integration. >> Right. >> Seems to be a trend that is common to all database players. I mean, Oracle is doing the same thing. SAP is doing the same thing. MariaDB. Do you see the distinction between transactional and analytical databases going away? >> It's coming together, right? Certainly coming together, from that perspective, but there's a fundamental different starting point, right? And with the big idea part, right? The universal database, which does everything for you in one system, whereas the suite of specialized databases, right? Oracle is in the classic Oracle database in the universal database camp. On the other side you have Amazon, which built a database. This is one of the first few Amazon re:Invents. It's my 10th where there was no new database announced. Right? >> No. >> So it was always add another one specially- >> I think they have enough. >> It's a great approach. They have enough, right? So it's a great approach to build something quick, which Amazon is all about. It's not so great when customers want to leverage things. And, ultimately, which I think with Selipsky, AWS is waking up to the enterprise saying, "I have all this different database and what is in them matters to me." >> Yeah. >> "So how can I get this better?" So no surprise between the two most popular database, Aurora and RDS. They're bring together the data with some out of the box parts. I think it's kind of, like, silly when Swami's saying, "Hey, no ETL.". (chuckles) Right? >> Yeah. >> There shouldn't be an ETL from the same vendor, right? There should be data pipes from that perspective anyway. So it looks like, on the overall value proposition database side, AWS is moving closer to the universal database on the Oracle side, right? Because, if you lift, of course, the universal database, under the hood, you see, well, there's different database there, different part there, you do something there, you have to configure stuff, which is also the case but it's one part of it, right, so. >> With that shift, talk about the value that's going to be in it for customers regardless of industry. >> Well, the value for customers is great, because when software vendors, or platform vendors, go in depth, you get more functionality, you get more maturity you get easier ways of setting up the whole things. You get ways of maintaining things. And you, ultimately, get lower TCO to build them, which is super important for enterprise. Because, here, this is the developer cloud, right? Developers love AWS. Developers are scarce, expensive. Might not be want to work for you, right? So developer velocity getting more done with same amount of developers, getting less done, less developers getting more done, is super crucial, super important. So this is all good news for enterprise banking on AWS and then providing them more efficiency, more automation, out of the box. >> Some of your customer conversations this week, talk to us about some of the feedback. What's the common denominator amongst customers right now? >> Customers are excited. First of all, like, first event, again in person, large, right? >> Yeah. >> People can travel, people meet each other, meet in person. They have a good handle around the complexity, which used to be a huge challenge in the past, because people say, "Do I do this?" I know so many CXOs saying, "Yeah, I want to build, say, something in IoT with AWS. The first reference built it like this, the next reference built it completely different. The third one built it completely different again. So now I'm doubting if my team has the skills to build things successfully, because will they be smart enough, like your teams, because there's no repetitiveness and that repetitiveness is going to be very important for AWS to come up with some higher packaging and version numbers.", right? But customers like that message. They like that things are working better together. They're not missing the big announcement, right? One of the traditional things of AWS would be, and they made it even proud, as a system, Jassy was saying, "If we look at the IT spend and we see something which is, like, high margin for us and not served well and we announced something there, right?" So Quick Start, Workspaces, where all liaisons where AWS went after traditional IT spend and had an offering. We haven't had this in 2019, we don't have them in 2020. Last year and didn't have it now. So something is changing on the AWS side. It's a little bit too early to figure out what, but they're not chewing off as many big things as they used in the past. >> Right. >> Yep. >> Did you get the sense that... Keith Townsend, from "The CTO Advisor", was on earlier. >> Yep. >> And he said he's been to many re:Invents, as you have, and he said that he got the sense that this is Amazon's chance to do a victory lap, as he called it. That this is a way for Amazon to reinforce the leadership cloud. >> Ja. >> And really, kind of, establish that nobody can come close to them, nobody can compete with them. >> You don't think that- >> I don't think that's at all... I mean, love Keith, he's a great guy, but I don't think that's the mindset at all, right? So, I mean, Jassy was always saying, "It's still the morning of the day in the cloud.", right? They're far away from being done. They're obsessed over being right. They do more work with the analysts. We think we got something right. And I like the passion, from that perspective. So I think Amazon's far from being complacent and the area, which is the biggest bit, right, the biggest. The only thing where Amazon truly has floundered, always floundered, is the AI space, right? So, 2018, Werner Vogels was doing more technical stuff that "Oh, this is all about linear regression.", right? And Amazon didn't start to put algorithms on silicon, right? And they have a three four trail and they didn't announce anything new here, behind Google who's been doing this for much, much longer than TPU platform, so. >> But they have now. >> They're keen aware. >> Yep. >> They now have three, or they own two of their own hardware platforms for AI. >> Right. >> They support the Intel platform. They seem to be catching up in that area. >> It's very hard to catch up on hardware, right? Because, there's release cycles, right? And just the volume that, just talking about the largest models that we have right now, to do with the language models, and Google is just doing a side note of saying, "Oh, we supported 50 less or 30 less, not little spoken languages, which I've never even heard of, because they're under banked and under supported and here's the language model, right? And I think it's all about little bit the organizational DNA of a company. I'm a strong believer in that. And, you have to remember AWS comes from the retail side, right? >> Yeah. >> Their roll out of data centers follows their retail strategy. Open secret, right? But, the same thing as the scale of the AI is very very different than if you take a look over at Google where it makes sense of the internet, right? The scale right away >> Right. >> is a solution, which is a good solution for some of the DNA of AWS. Also, Microsoft Azure is good. There has no chance to even get off the ship of that at Google, right? And these leaders with Google and it's not getting smaller, right? We didn't hear anything. I mean so much focused on data. Why do they focus so much on data? Because, data is the first step for AI. If AWS was doing a victory lap, data would've been done. They would own data, right? They would have a competitor to BigQuery Omni from the Google side to get data from the different clouds. There's crickets on that topic, right? So I think they know that they're catching up on the AI side, but it's really, really hard. It's not like in software where you can't acquire someone they could acquire in video. >> Not at Core Donovan. >> Might play a game, but that's not a good idea, right? So you can't, there's no shortcuts on the hardware side. As much as I'm a software guy and love software and don't like hardware, it's always a pain, right? There's no shortcuts there and there's nothing, which I think, has a new Artanium instance, of course, certainly, but they're not catching up. The distance is the same, yep. >> One of the things is funny, one of our guests, I think it was Tuesday, it was, it was right after Adam's keynote. >> Sure. >> Said that Adam Selipsky stood up on stage and talked about data for 52 minutes. >> Yeah. Right. >> It was timed, 52 minutes. >> Right. >> Huge emphasis on that. One of the things that Adam said to John Furrier when they were able to sit down >> Yeah >> a week or so ago at an event preview, was that CIOs and CEOs are not coming to Adam to talk about technology. They want to talk about transformation. They want to talk about business transformation. >> Sure, yes, yes. >> Talk to me in our last couple of minutes about what CEOs and CIOs are coming to you saying, "Holger, help us figure this out. We have to transform the business." >> Right. So we advise, I'm going quote our friends at Gartner, once the type A company. So we'll use technology aggressively, right? So take everything in the audience with a grain of salt, followers are the laggards, and so on. So for them, it's really the cusp of doing AI, right? Getting that data together. It has to be in the cloud. We live in the air of infinite computing. The cloud makes computing infinite, both from a storage, from a compute perspective, from an AI perspective, and then define new business models and create new best practices on top of that. Because, in the past, everything was fine out on premise, right? We talked about the (indistinct) size. Now in the cloud, it's just the business model to say, "Do I want to have a little more AI? Do I want a to run a little more? Will it give me the insight in the business?". So, that's the transformation that is happening, really. So, bringing your data together, this live conversation data, but not for bringing the data together. There's often the big win for the business for the first time to see the data. AWS is banking on that. The supply chain product, as an example. So many disparate systems, bring them them together. Big win for the business. But, the win for the business, ultimately, is when you change the paradigm from the user showing up to do something, to software doing stuff for us, right? >> Right. >> We have too much in this operator paradigm. If the user doesn't show up, doesn't find the click, doesn't find where to go, nothing happens. It can't be done in the 21st century, right? Software has to look over your shoulder. >> Good point. >> Understand one for you, autonomous self-driving systems. That's what CXOs, who're future looking, will be talked to come to AWS and all the other cloud vendors. >> Got it, last question for you. We're making a sizzle reel on Instagram. >> Yeah. >> If you had, like, a phrase, like, or a 30 second pitch that would describe re:Invent 2022 in the direction the company's going. What would that elevator pitch say? >> 30 second pitch? >> Yeah. >> All right, just timing. AWS is doing well. It's providing more depth, less breadth. Making things work together. It's catching up in some areas, has some interesting offerings, like the healthcare offering, the security data lake offering, which might change some things in the industry. It's staying the course and it's going strong. >> Ah, beautifully said, Holger. Thank you so much for joining Paul and me. >> Might have been too short. I don't know. (laughs) >> About 10 seconds left over. >> It was perfect, absolutely perfect. >> Thanks for having me. >> Perfect sizzle reel. >> Appreciate it. >> We appreciate your insights, what you're seeing this week, and the direction the company is going. We can't wait to see what happens in the next year. And, yeah. >> Thanks for having me. >> And of course, we've been on so many times. We know we're going to have you back. (laughs) >> Looking forward to it, thank you. >> All right, for Holger Mueller and Paul Gillan, I'm Lisa Martin. You're watching "theCube", the leader in live enterprise and emerging tech coverage. (upbeat music)

(light music) >> Hello, welcome back everybody to theCUBE's coverage in New York City of AWS Summit 2022. I'm John Furrier, host of theCUBE. We had Dave Vellante, Lisa Martin here earlier. I'm going to wrap it up here with James Forrester, last interview of the day here in New York. Wish we would have had another day. It's a packed house, 10,000 people. James Forrester's the VP Worldwide Technical Leader for VMware's Cloud on AWS. On AWS is a big distinction. James, welcome to theCube. Thanks for coming on. >> Thank you so much, John. It's great to be here. >> So I think it's been like six years since the announcement of VMware's Cloud on AWS, which is a separate instance, separate hardware, but it's changed the game for VMware. You guys have done a lot of work, successful traction with customers. Clarified, I remember at that time, it really clarified VMware's Cloud play. Which then gave VMware more time to work on what it's doing now, which is, you know, using all their assets and their operations with Tanzu, Monterey, Cloud Native, Cross Cloud. What they call you guys call Cross Cloud, I call Super Cloud, action, a lot of stuff happening. So thanks for coming on. Okay. So first question is, what's the future look like for VMware's Cloud on AWS? >> Super bright, super bright. And there's a couple of great reasons for that. I think firstly, what we're seeing is that customers have now made enough progress in their cloud journeys. Many of them have chosen AWS and they're going full force. We're going to help them go faster. We're going to help them get there and get native to those adjacent services much quicker with more confidence and more resiliency. So it's a super exciting time to be doing what we do. >> You know, VMware has had a steady install base, okay. I mean basically it's like almost ingrained in the operations. What do you guys see as that next level step up function? Because you know, obviously Broadcom is buying VMware. Obviously that utility will be in place, but there's more. There's more there that customers can tap into. This is the promise of the cross-cloud. How do you talk about that when you got the AWS action? How does that all integrate? >> Yeah, absolutely. And of course, because so many customers are going to AWS on their own cloud journeys right now, what we get to have the conversation about is how they can get there more confidently. And so for customers who are just starting out, who are looking at their application portfolios, who have a ton of skilled IT professionals who they want to bring into that cloud journey, they can use the skills they already have. For those folks who are a little bit further along but they may be finding that refactoring their applications is more complex, more difficult that they anticipated, we give them a way of moving with confidence and with much less risk so they can do those cloud journeys that they anticipated. >> You know, James, I want to get your thoughts on what the state of the current situation is, vis-à-vis, your customers and your customers' appetite for AWS services. 'Cause one of the promises of the original deal was clarifying messaging but more importantly, customers can get the VMware Cloud and take advantage of the higher level services on AWS. What's the update there? What's the current state of the art? What's some of the patterns that you're seeing on the uptake of services and how they're working together? >> Yeah, it's a great call out. And honestly, one of the misconceptions that I address right out of the gate is that somehow going VMware Cloud takes you away from those services. It doesn't, it gets you closer to them. Full, direct, native access to all of those hundreds of great AWS services. So what we often find is that customers have their enterprise data, inside data workloads in their data centers. But what they want to do is get that up next to the AWS services that can use it, like Redshift and Athena and Glue. They can move those workloads right adjacent to those services to start using them right away. So it's a great way to look at the platform. >> So one of the observations that's pretty well understood right now by most people, I'd say 90%, if not more, not a hundred percent 'cause I've heard people like not get it, but it's pretty clear that the operating model for the the enterprise will be hybrid as a steady state. I don't think there's any debate on that unless you think there is. >> Do you feel the same- >> No debate. No debate. >> Okay. Hybrid's a steady state. What does that mean as clients start to think about edge and their data centers. 'Cause now the private cloud is back in the game. So I've heard people talk about private cloud, which we, I think we coined the term with Dave, Wikibon years ago, but it kind of went away because that was not the public cloud. So public cloud won, on premise didn't go away. We saw Amazon with Outpost. So now they're like, I can still have stuff on prem and run it in a cloud operations. So they're calling that private cloud, I think. So you're starting to hear the same things. What it means basically is that hybrid is winning. It's the standard. What does the hybrid environment look like from a VMware perspective as you guys look at that and have been building that out 'cause you have customers that are on premises. >> Yeah. >> Is it just to the cloud and back? Is it, is there any changes? Is there new connective tissue? Is there a glue layer? What's the operating model for VMware customers? >> Well, customers wanted those same benefits from public cloud agility, cost benefits, elasticity, innovation, sovereignty, sustainability, but they wanted to be able to do that everywhere. They wanted it in their data centers. They wanted it at the edge. And as you've pointed out public cloud delivered that for customers. AWS first out there delivering that for customers. Now with innovations like VMware Cloud and AWS outpost, we're able to bring that back into the data center. We're able to bring those same benefits of public cloud into the customers on-prem environment. And you're right. We see hybrid just rolling and rolling and being able to offer our solution across all of it. >> Yeah, we're big fans of VMware because theCube's 12 years old, we've been at every VMworld. Now they're calling it VMware Explorer, the events coming up. So the folks watching, plug for VMware Explorer, formerly VMworld, it's on the schedule. Content catalog just came out last week. It's looking pretty good. So put a plug out there. We'll be there with theCube, two sets. So you know, if you're going to VMworld, now Explorer go register, get up there. It's in San Francisco, always a great event. vSphere and vSAN, always great products. But you got Carbon Black, you got Security. So these things have all been working kind of pistons for VMware. Tanzu, I know Raghu and those guys are doing it. Craig McLuckie and team, they're working on that. You got Tanzu, you got Monterey. That's the new cloud native thing. How is that tracking vis-à-vis, the operating model of the the core engine, vSphere, vSAN and others. And then with the native services of Cloud. So you got AWS Cloud with VMware Cloud, vSphere, vSAN, Carbon Black, and Security. And then you got the Tanzu over here. How are those three things coming together? >> Well, the services that customers know and love first and foremost that they've been running the mission critical workloads on, vSphere, vSAN, NSX. What VMware cloud and AWS is, is a packaging together of those services. So customers don't have to configure it all themselves and do the heavy lifting. We manage and run it on their behalf. What we are adding to that most recently with Tanzu is now the ability to run containers within the same environment. 'Cause customers tell us they've got parts of their organization that are very much on vSphere VMs. Parts of their organization are moving to containers. We want be able to provide a single operating model, a single layer, a single way of managing all of that. No matter where it's deployed. >> You know, remember back in the day, when Raghu wasn't the CEO, Carl Eschenbach was there, Sanjay Poonen was there. Carl's now at Sequoia Capital, Raghu's a CEO. Sanjay's kind of looking for a next gig. I always said, why doesn't vSphere and NSX become that abstraction layer and commoditize the network so that white boxes and Dell and HP could all play in that layer? It just never happened yet. Is that something you guys talk about at all? Like, I mean in the, in the smokey room, in the execs, is that happening? What's the vision? >> Well, we always work backwards- from customers, right? (John laughing) And what customers are telling us is they want us to help them with that undifferentiated heavy lifting. So who knows where that could take us, but right now we're very focused on helping those customers move with confidence to the cloud. >> You didn't take the bait on that one. I appreciate that. (James laughing) Okay. So let's get some perspective. You're out with customers. What are the big things that you're seeing right now from your customers right now? 'Cause you look behind us here, 10,000 people at this event. This is not a no-show. This is not a throwaway event in, you know, somewhere in the corner of the world. This is New York City, only one summit. This is bigger than Snowflake Summit and that was packed. So from an event standpoint, this is pretty a big game statement here for AWS. These companies are not experiencing headwinds, they're changing. So what are your customers telling you around what they're looking at for the cloud native architecture? I mean obviously the digital transformation is continuing, obviously clouds here. And again, we were saying earlier, this is the first time in history that the cloud hyperscalers have been in market during a so-called downturn. So there's no other data. 2008, I wouldn't call 'em up and running. They were building, but AWS, Azure, others, these cloud players they're in market. And so you're starting to see kind of some data coming out saying, Hey, this thing's still working, the engine of innovation is cranking out and it's not slowing down the digital transformation. It might change the capital markets and valuations but it's not changing customers. That's what I'm hearing. Now, you probably would agree with that, right? >> James: I think that's exactly right. >> Okay. So let's stay with that. If you believe that, then it's like, okay, what are they doing? So what are customers doubling down on? What are some of the patterns you're seeing in the environment today that you could share with the audience? >> Yeah, so I think first and foremost is that steady transition to the cloud to deliver all of those benefits, agility, cost, elasticity, innovation, sovereignty, sustainability that hasn't gone away at all. In fact, it's only accelerated. With workloads like virtual desktops, which became so critical during COVID the need to be able to provide that kind of scalable elastic capacity has only increased. Now, coupled with that, most of these customers are already on a cloud journey. And while some folks may have had the luxury of letting that go a little bit more slowly, nowadays the urgency is pervasive across all of the industries that we get to talk to in New York. Everyone needs to go faster. Everybody's not seeing the progress that they expected that we think we can help them deliver. So the opportunity I think that's come out of COVID is more workloads, different use cases, disaster recovery, ransomware- >> Is that more of an awareness or reality or both? >> Both. Absolutely. >> Okay. So let me ask the next question. 'Cause this is a good conversation, I think. I agree a hundred percent. We're seeing the same exact thing. Now let's talk about how companies are thinking about the real opportunity that's emerged, which is refactoring the business model without actually changing the makeup of the organization per se, to take on new territories and potentially take over categories. >> James: Mm hmm. >> So I mean a data warehouse and a data cloud's kind of the same thing. Snowflake probably wouldn't like me saying that they're a data warehouse because they call themselves a data cloud, but it's kind of the same thing, just refactored on AWS. >> James: Yep. >> That's a super cloud. So that's an opportunity for everyone to do that in every vertical. How many customers are actually thinking that way and actually taking steps to pursue that, capture that opportunity? Or do you agree it's the opportunity? >> No, I think that that is an opportunity and I love that idea of super cloud in that what I think customers have started to realize, over the last couple of years in particular, is it's very difficult to take advantage of all of those great cloud services if your applications are still behind a whole lot of different layers of firewalls and so forth. So getting the application close to those services, in proximity to those services is that first step in modernization. Then it doesn't have to be a change the wings on the plane while it's flying conversation, which- >> John: Yeah. >> You know, is very risky for a lot of organizations. >> John: Exactly. >> It's a let's get the plane going a little bit faster. Let's get the plane going a little bit smoother, and let's get the plane to its destination with less risk. >> You know, James, that reminds me of the old school conversations of non disruptive operations. Remember those days? >> James: I do, yeah. >> Mostly around storage and, and servers. But that's what basically what you're saying. Transform while operating, right? >> James: Exactly. >> So this is, you can do both. You got to make time and it's a talent question too. I'd love to get your thoughts on how customers are thinking about who do you put on which task. 'Cause you want your A players on both areas. You don't want all your A players, what I hear, CSOs and CIOs telling me is that, I put all my A players on transformation, I got no one running the business. >> James: Mm hmm. >> So you got to kind of balance. That's a cultural team decision. >> It's a cultural team decision. It's also a skills marketplace decision. >> John: Yeah. >> And there's a practical reality to the skills that are available and how fast you can hire them. So a big part of the conversation that we have is when customers have existing skills sets, plug those into their transformation, plug those into their business outcomes. I like to use the phrase, "Let's make heroes out of IT" because they can be a much more critical player than they think they can be. Yeah, IT basically is not even around anymore. It's part of the organization. And then you have data science and data engineering coming in. So it's, you know, IT is not a department anymore, it's the company >> Exactly right. >> If you're kind of going down that road, yeah. >> Yeah. Alright, so final question. What's the biggest change you've seen and observed in your current year and a half? You know, we're coming out of COVID, knowing what was before, what sea change, what inflection point are we in now? How would you describe this current market? 'Cause again, we're kind of in a unique market. You know, you got crypto around the corner, people getting attracted to that, little bubbly obviously, reality of cloud and 2.0 or super cloud emerging. On premise is not going away. Edge exploding on the industrial side, especially with machine learning coming along. So this operating model is clearly in sight. What's the biggest observation you've noticed. >> I think it's the sense of urgency over the last couple of years in that most customers I talked to are no longer relaxed about the timing of delivering cloud capabilities to their organizations. Most customers are on sort of a transformation journey of their own and digital transformation and cloud transformation are absolutely fundamental to that. >> One more real quick follow up question if you don't mind, 'cause I appreciate your time. One of the things that's come up a lot in our conversations is the role of the ecosystem. Not only as a part of the business model but also validation of the enablement that cloud offers companies. You have an enabling platform, your ecosystem is well known. And so your customers are starting to develop ecosystems. So if the cloud model kind of trickles like downstream, ecosystem is kind of a proof of something. >> James: Mm hmm. >> What's your view of all this ecosystem discussion as we transform this next generation? >> Yeah, I think it touches on a couple of things. So obviously there is a technology ecosystem, which is evolving very rapidly in support of cloud and cloud transformation. But what's interesting, I think is the business ecosystem that's evolving around it. We're seeing our customers evolve their own businesses to assume that those cloud capabilities will be available to them. And if the cloud capabilities are not available to them in a timely fashion, then the ecosystem starts to have a domino effect. So the ecosystems are interdependent between business, and technology, and skills, and talent. And I think that's a great to be >> James Forrester, they're going to shut us down. The speakers are on, they're going to pull the plug. Thanks for being our last interview here in New York City and bringing us home. Really appreciate you taking the time to come on theCube. >> John, thanks so much. Great to be here, really enjoyed it. Okay. We are wrapping it up here in New York City. I'm John Ford with theCube, great day. For Lisa Martin, Dave Vellante, and the entire crew of theCube here on the ground. Live in person events are back. theCube hybrid, get online, check out our coverage there. The SiliconANGLE and thecube.net. I'm John Furrier signing off from New York City. See you next time. (light music)

>>The cube presents HPE discover 2022 brought to you by HPE, >>Where back you watching the Cube's coverage. HPE discover 2022. This is day three, Dave Valante with John furrier. Ricky Cooper is here. He is the vice president slash newly minted SP we're gonna talk about that of global and transformational partners at VMware and rock LA Vista. Who's the vice president of worldwide GreenLake cloud services at the transformation, the transformational partner of Hewlett Packard enterprise guys. Welcome to the program. Thanks for coming >>On. Thank you. Thank you very much. Thank >>You. So really interesting title and you've got a new role. Yeah. Right. Explain that. >>Well, I'm the interim SVP for the channel and for the commercial business at VMware, I also have the global, my existing role is global and transformational partners. So that's our, you know, our largest OEMs and also the transformational partners, which is more the, you know, the, the reseller stroke, um, services element of our business. >>I remember in, uh, John and I started the cube in 2010. Yeah. And the second show we did, third show actually was wasm world 2010. >>And Ritz was the CEO at the time, huge >>Booth. It was amazing. And, and HP at the time was all over, you know, of, of the cube and of course, world, and you guys have been partners for a long, long time Roco. So maybe give us a little bit >>Of the history AB absolutely. So for 20 years, H P H P has been partnered with VMware in delivering virtualization technology and solutions to our customer base. And while that partnership is strong, and I remember some of the market share numbers were like 45% of VMware software stack is running on HPE servers and technology. I think about how that's evolved, right? Like strong history, strong partnership. And when I say strong, I'm not talking about marketing fluff, I'm not talking about slideware. I'm talking about at a ground level that the account teams get together and talk about what those customers that they're working with. They get together and figure out what outcome they're trying to solve for. And we bring that technology together. Now, layering GreenLake GreenLake is taking at the heart of what VMware does with their software stack, combining it with our infrastructure solutions and providing IAS, PAs and CAS capabilities to our customers at the edge in their core, whether it's a data center or, um, colo, as well as providing the common operating model into public cloud. And so we embrace, and the partnership is only getting stronger because of what VMware does with us now with GreenLake, which is everything, what HPE is >>About that is well, well said, I gotta say, I gotta say that was purposely. That was really crisp and, and not to kind of go back and look at the history of the cube, but we've been covering both of you guys. Mm-hmm, <affirmative> deeply been watching the transformation of both companies. It's so clear that VMware is so deep in the operational side of it. Yeah. It's been one of the hallmarks of VMware mm-hmm <affirmative>, uh, vSphere, um, all that technology. You guys have been powering with the hardware now, GreenLake, we had a demo yesterday with the storage team, they're provisioning, storage, Amazon storage, and on premise and edge. So we see VMware as a massive service layer in this new model. Very key. How deep, uh, is it going now with the GreenLake? Can you share what's different with the relationship, I get the account deep account partner sharing, but now that green Lake's out there, you have an ecosystem. VMware has an ecosystem. Absolutely. A big one. Yeah. You know, so take >>This and is really where we're looking to improve things. So let me, let me start by saying, we've just been voted the 20, 20, uh, partner of the year, uh, here with HPE this week. And that news is out there and, uh, was issued a couple of days ago, which is fantastic for the two companies and shows the direction where we are now and where we're looking to go forward. I think there's a lot of work to be done behind the scenes. As we emerge as an independent company, there's a lot of work to be done behind the scenes on how we look at our broader ecosystem and certainly our largest OEMs of which, you know, HPE, as Roco said, 20 years of great partnership there, the next stage is how do we really get the teams equipped and plug into GreenLake? Um, you know, we've had a relationship very well known with Dell for the last, you know, for the last five years, we've grown that business at an amazing rate. We've got a whole bunch of personnel still working on, on those areas. We're in a position now where we can sort of redeploy some of those, um, over some of the headcount to really drive our mission here with our other partners. And certainly with HPE, >>Well, the integration piece that you guys have co co-engineering on that's well documented. Yeah. But with the ecosystem specifically, this is a net new thing for GreenLake and frankly, us analysts. And we had IDC on yesterday. We're looking at that as a benchmark, we're gonna be measuring GreenLake success by how well the ecosystem is so correct. Welcome to the party, VMware and HPE. That is it. You didn't have to have that big ecosystem cuz you had the channel, your HP had a strong channel mm-hmm <affirmative> but now it's an ecosystem game. Talk about that. >>Customers have that expectation, right? And if you think about what we've built, we've got an ecosystem we re we, um, announced Mar the marketplace for GreenLake right now, VMware has their own marketplace, but by standardizing on their technology in our private cloud enterprise, which was also announced here at discover, which is deeply rooted with VMware technology in it, we now are able to take advantage of their marketplace. Plus all the others that we're bringing into GreenLake and effectively solve for the customer's most complex business problems. Because if you want to be successful, you have to think that the world is open and hybrid. And that means partnerships with everybody mm-hmm <affirmative> you can't think I won't partner because they're a competitor or they may have a product that competes with me. It starts and ends with what the customer wants and needs and solving for that business objective. That means partnering well. >>Well you guys have, you know, they're they own the operator it ops. Yeah. I would say ops op side, clearly mm-hmm <affirmative>. And with the cloud native momentum that VMware has and what you guys have been doing, I just see a nice fit there. What are some of the customers say? I mean, what's some of the, what's the, what's the market telling you with GreenLake and VMware? What's the number one thing people love? Well, >>Just, just look at GreenLake at its core. And the very simplistic pays your grow model, right? The hardware doesn't grow without software. You don't scale the hardware or scale it back without software. And so what are we doing in within GreenLake? We're taking the VMware stack and we're scaling it with the hardware up and down for customers. They no longer have to worry about the balancing act between how much infrastructure I have to buy. How much software do I have to marry up to it? Are they outta sync? Right? We're solving that together for our customers. That's what they want at, at a very simplistic view, right? Then they say, Hey, give me the life cycle management of this platform, right? I don't wanna have to spend it cost operations, have employees dealing with very rudimentary life cycle management and the toil that it comes with. That's a big cost element when customers are creating snowflakes, mm-hmm <affirmative> in their it operations, they're adding cost. And what we're doing through this partnership, what we're doing with private cloud enterprise is eliminating that toil and, and helping optimize that operating mind >>You're simplifying. Oh, absolutely. >>So I wanna standardizing there a little bit as well. Right? So that, that's a, a great point and BRCA has made several there, but the next stage for us and what we've been talking about a lot this week is how do we sort of standardize what are the three or four things that customers are gonna recognize this partnership for? You know, be that, um, anywhere workspace be that multi-cloud, what are the three or four things that we can say, Hey, these two companies together are fantastic. And how do you then security get up and yeah. Security, security. Yeah. How do you then get that up and running in a green lake environment, but also on the back end, ensure that your operations are seamless and it's a great customer experience. >>So Ricky, that and Roco, I want to, uh, rewind two clicks back in the context of standards in the partner conversation, the ecosystem conversation, are you at a point where you can cuz you're basically saying you can cross pollinate the ecosystems and the partnerships. Yeah. But you got different, you know, business practices, different legal contracts and so forth. Are you able to create standardization at that layer within the partners beyond just YouTube within your respective ecosystems? Is that it sounds like that's a really difficult challenge, but it could deliver customer benefit in terms of reducing >>Friction. Absolutely. It does. And that's what we've gotta work towards. So right now operation wise, contract wise, that's exactly what we're here working through. It's not easy, but the teams are all fully behind it and that's the Nirvana for us is to be in that >>Position. Well, and, and what I really like where we are in this partnership at, in a point in time, VMware is spun off from Dell. If there's any confusion by our customer base, that VMware is going to not only work with us as they've done traditionally, but maybe get closer and not worry about this standardization, this approach, this ecosystem of players. I mean, you know, Ricky and I talked about this, like this only gets better. Yeah. Because of that. >>Yeah. The market dynamics are your friend right now. I think, yeah. That's definitely the case and the history is key, but the technical trends that we had an earlier panel on here, uh, with the technologists coming together, mm-hmm, <affirmative>, there's big changes happening. The edge is exploding rapidly accelerating with machine learning. You're seeing it ops turn into ML ops mm-hmm <affirmative>, you're starting to see the edged industrial edge explode, um, even into space. So like you have technology shifts. Yeah. And IDC pointed out that the B2B growth trends, even it spend, you want even call it, it spend or cloud spend or cloud ops is still up to the right. Yeah. Even during recession. >>And that is where all the opportunity is. So, you know, not just focusing on what we do today, let's think outside the box, we're doing some great things together, you know, in the, in the AI space and we've Invidia and between the two teams, some amazing things are happening and we've just gotta continue that. But focus is gonna be essential in the early stages to make sure you've got two or three things built out very well. And then the rest of the business that's already happening out there between the two companies is a bit more programmatic. >>Yeah. It's interesting. The V the VMware relationship with the hyperscale. I know we've covered, uh, the AWS announcement like six years ago. I forget what it was, Dave, four 60 years. Ragoo was there with Andy Ja, pat Gelsinger and, and, uh, all the top dogs there, but that's just Amazon. It's still the VMware instances on the cloud there. Yeah. The customers we're hearing here at GreenLake is that they want the single pain in cloud hate. They use that term. It's kind of an old term. That's kind of what we're seeing. They >>Still want it because nobody's giving it to 'em. >>So this, and then outpost, which is launched four years ago, kind of not working well for Amazon because EKS and open standards and, and other hardware platforms, which is essentially hardware mm-hmm <affirmative>, which is not Amazon's game. And they're, although they do great hardware in the cloud, but they're not, they're not hardware people >>Wait. So you're talking about like the public cloud guys trying to get into the edge, but look, the world is hybrid in no point, in instance, in time, do I ever believe that Azure will be able to control AWS nor GCP versus place versa? Right? And then this idea that you can go from the outside in is interesting, but where data's created, where the applications are, where the digital and the analog world meet as at the edge and for our customers, they're creating transactions and data at the edge. Mm-hmm, <affirmative>, that's where the control plane should start not in the public. And so, given that, and working with VMware, we're able to say where the data lives, where the application is sitting, where the digital transformation is happening. It's from the inside out that you provide a standard operating model across all your clouds, right? They're never gonna be able to give that to you unless you're a hundred percent in their cloud, including what they do at the edge. What we're doing with GreenLake is saying, we're giving you that edge to colo, to core data center, to public cloud operating model, that you're not having multiple snowflakes of an operating model for each one of those clouds. And VMware is at the core of that. >>And it's a global model. And Ricky, I'm guessing from your, what I would call an accent that you weren't born in America. Correct. I know where this Yankee fan was. >>Yeah. >>That's a >>Don't pin Yankee fan on the >>That's fan. Yeah. Okay. So despite 1986 we'll >>So >>I wanted to ask if, how you're able to take these standards overseas. Um, and because of course, you know, you know, well, John, as do I, different countries of different, different projects, governance issues, are you able to take this to make this a global? >>Absolutely. And, and the work I was talking about within Nvidia and HP is a great example because we've gone the other way. It's coming from Asia, where we've set up some best practice in the work that they're doing there, and it's coming across into Europe and coming across into the us. So it's all about finding, you know, finding the right solutions that we were talking about earlier. What's going to work, building out, investing that's something. I think that we we've missed a trick on, you know, through, through the past sort of four or five years, VMware really leaning in and really holding a hand here of HPE. The team were a huge team, turned up to the, to, to this event from all over the world. They're here demonstrating exactly what you're talking about, the standards with Nvidia, that message. And then you take that and make sure that it's not a snowflake just happening in Asia. You're bringing it across the world and, and you're getting the, you know, the impetus and the, uh, push behind that. >>You say, snowflake, I think of snowflake. We just covered their event too. Yeah. Yeah. Not snowflake and snowflake. Um, um, but final question as we wrap up, um, we got world converted to now called VMware Explorer. Yeah. So we're gonna be there again on the floor, two sets with the cube, um, that's changing. What can we expect to see from the relationship? What's the scorecard gonna look like? What, what's the metrics you guys are measuring yourselves on and what can customers expect from the HPE, um, VMware next level relationship partnership? >>Uh, for me, it's very simple. We measure our success based on the customer response. Are we solving for what they want us to be solving for? And that will prove itself out in how we're solutioning for them, the feedback that they give us and this discover event in terms of what we've released, the announcements between private cloud enterprise, the marketplace, um, what we're doing with this relationship since the Dell spinoff, the feedback has been amazing. Amazing, great. And I am thankful, thankful for the partnership. >>Awesome. Wrap way to bring us home Rocko. Thank you for that. And thank you, Ricky, for coming on the great, great >>Job you guys been great. Thank you. Thank you. >>Thanks very much. All right. And thank you for watching this, Dave Valante for John furrier day three of HPE, discover 2022. You're watching the cube, the leader in live enterprise and emerging tech coverage. We'll be right back.

>>Welcome back to the big apple, everybody. The Cube's continuous coverage here of MongoDB world 2022. We're at the new Javet center. It's it's quite nice. It was built during the pandemic. I believe on top of a former bus terminal. I'm told by our next guest Tony bear, who's the principal at DB insight of data and database expert, longtime analyst, Tony. Good to see you. Thanks for coming >>On. Thanks >>For having us. You face to face >>And welcome to New York. >>Yeah. Right. >>New York is open for business. >>So, yeah. And actually, you know, it's interesting. We've been doing a lot of these events lately and, and especially the ones in Vegas, it's the first time everybody's been out, you know, face to face, not so much here, you know, people have been out and about a lot of masks >>In, >>In New York city, but, but it's good. And, and this new venue is fantastic >>Much nicer than the old Javits. >>Yeah. And I would say maybe 3000 people here. >>Yeah. Probably, but I think like most conferences right now are kind of, they're going through like a slow ramp up. And like for instance, you know, sapphires had maybe about one third, their normal turnout. So I think that you're saying like one third to one half seems to be the norm right now are still figuring out how we're, how and where we're gonna get back together. Yeah. >>I think that's about right. And, and I, but I do think that that in most of the cases that we've seen, it's exceeded people's expectations at tenants, but anyway sure. Let's talk about Mongo, very interesting company. You know, we've been kind of been watching their progression from just sort of document database and all the features and functions they're adding, you just published a piece this morning in venture beat is time for Mongo to get into analytics. Yes. You know? Yes. One of your favorite topics. Well, can they expand analytics? They seem to be doing that. Let's dig into it. Well, >>They're taking, they've been taking slow. They've been taking baby steps and there's good reason for that because first thing is an operational database. The last thing you wanna do is slow it down with very complex analytics. On the other hand, there's huge value to be had if you would, if you could, you know, turn, let's say a smart, if you can turn, let's say an operational database or a transaction database into a smart transaction database. In other words, for instance, you know, let's say if you're, you're, you're doing, you know, an eCommerce site and a customer has made an order, that's basically been out of the norm. Whether it be like, you know, good or bad, it would be nice. Basically, if at that point you could then have a next best action, which is where analytics comes in. But it's a very lightweight form of analytics. It's not gonna, it's actually, I think probably the best metaphor for this is real time credit scoring. It's not that they're doing your scoring you in real time. It's that the model has been computed offline so that when you come on in real time, it can make a smart decision. >>Got it. Okay. So, and I think it was your article where I, I wrote down some examples. Sure. Operational, you know, use cases, patient data. There's certainly retail. We had Forbes on earlier, right? Obviously, so very wide range of, of use cases for operational will, will Mongo, essentially, in your view, is it positioned to replace traditional R D BMS? >>Well, okay. That's a long that's, that's much, it's >>Sort of a loaded question, but >>That's, that's a very loaded question. I think that for certain cases, I think it will replace R D BMS, but I still, I mean, where I, where I depart from Mongo is I do not believe that they're going to replace all R D D BMSs. I think, for instance, like when you're doing financial transactions, you know, the world has been used to table, you know, you know, columns and rows and tables. That's, it's a natural form for something that's very structured like that. On the other hand, when you take a look, let's say OT data, or you're taking a look at home listings that tends to more naturally represent itself as documents. And so there's a, so it's kind of like documents are the way that let's say you normally see the world. Relational is the way that you would structure the world. >>Okay. Well, I like that. So, but I mean, in the early days, obviously, and even to this day, it's like the target for Mongo has been Oracle. Yeah. Right, right. And so, and then, you know, you talk to a lot of Oracle customers as do I sure. And they are running the most mission, critical applications in the world, and it's like banking and financial and so many. And, and, and, you know, they've kind of carved out that space, but are we, should we be rethinking the definition of, of mission critical? Is that changing? >>Well, number one, I think what we've traditionally associated mission critical systems with is our financial transaction systems and to a less, and also let's say systems that schedule operations. But the fact is there are many forms of operations where for instance, let's say you're in a social network, do you need to have that very latest update? Or, you know, basically, can you go off, let's say like, you know, a server that's eventually consistent. In other words, the, do you absolutely have, you know, it's just like when you go on Twitter, do you naturally see all the latest tweets? It's not the system's not gonna crash for that reason. Whereas let's say if you're doing it, you know, let's say an ATM banking ATM system, that system better be current. So I think there's a delineation. The fact is, is that in a social network, arguably that operational system is mission critical, but it's mission critical in a different way from a, you know, from, let's say a banking system. >>So coming back to this idea of, of this hybrid, I think, you know, I think Gartner calls it H tab hybrid, transactional analytics >>Is changed by >>The minute, right. I mean, you mentioned that in, in your article, but basically it's bringing analytics to transactions bringing those, those roles together. Right. Right. And you're saying with Mongo, it's, it's lightweight now take, you use two other examples in your article, my SQL heat wave. Right. I think you had a Google example as well, DB, those are, you're saying much, much heavier analytics, is that correct? Or >>I we'll put it this way. I think they're because they're coming from a relational background. And because they also are coming from companies that already have, you know, analytic database or data warehouses, if you will, that their analytic, you know, capabilities are gonna be much more fully rounded than what Mongo has at this point. It's not a criticism of a Mongo MongoDB per >>Per, is that by design though? Or ne not necessarily. Is that a function of maturity? >>I think it's function of maturity. Oh, okay. I mean, look, to a certain extent, it's also a function of design in terms of that the document model is a little, it's not impossible to basically model it for analytics, but it takes more, you know, transformation to, to decide which, you know, let's say field in that document is gonna be a column. >>Now, the big thing about some of these other, these hybrid systems is, is eliminating the need for two databases, right? Eliminating the need for, you know, complex ETL. Is, is that a value proposition that will emerge with, with Mongo in your view? >>You know, I, I mean, put it this way. I think that if you take a look at how they've, how Mongo is basically has added more function to its operations, someone talking about analytics here, for instance, adding streaming, you know, adding, adding, search, adding time series, that's a matter of like where they've eliminated the need to do, you know, transformation ETL, but that's not for analytics per se for analytics. I think through, you know, I mean through replication, there's still gonna be some transformation in terms of turning, let's say data, that's, that's formed in a document into something that's represented by columns. There is a form of transformation, you know, so that said, and Mongo is already, you know, it has some NA you know, nascent capability there, but it's all, but this is still like at a rev 1.0 level, you know, I expect a lot more >>Of so refin you, how Amazon says in the fullness of time, all workloads will be in the cloud. And we could certainly debate that. What do we mean by cloud? So, but there's a sort of analog for Mongo that I'll ask you in the fullness of time, will Mongo be in a position to replace data warehouses or data lakes? No. Or, or, or, and we know the answer is no. So that's of course, yeah. But are these two worlds on a quasi collision course? I think they >>More on a convergence course or the collision course, because number one is I said, the first principle and operational database is the last thing you wanna do is slow it down. And to do all this complex modeling that let's say that you would do in a data bricks, or very complex analytics that you would do in a snowflake that is going to get, you know, you know, no matter how much you partition the load, you know, in Atlas, and yes, you can have separate nodes. The fact is you really do not wanna burden the operational database with that. And that's not what it's meant for, but what it is meant for is, you know, can I make a smart decision on the spot? In other words, kinda like close the loop on that. And so therefore there's a, a form of lightweight analytic that you can perform in there. And actually that's also the same principle, you know, on which let's say for instance, you know, my SQL heat wave and Allo DBR based on, they're not, they're predicated on, they're not meant to replace, you know, whether it be exit data or big query, the idea there is to do more of the lightweight stuff, you know, and keep the database, you know, keep the operations, you know, >>Operating. And, but from a practitioner's standpoint, I, I, I can and should isolate you're saying that node, right. That's what they'll do. Sure. How does that affect cuz my understanding is that that the Mon Mongo specifically, but I think document databases generally will have a primary node. Right? And then you can set up secondary nodes, which then you have to think about availability, but, but would that analytic node be sort of fenced off? Is that part of the >>Well, that's actually what they're, they've already, I mean, they already laid the groundwork for it last year, by saying that you can set up separate nodes and dedicate them to analytics and what they've >>As, as a primary, >>Right? Yes, yes. For analytics and what they've added, what they're a, what they are adding this year is the fact to say like that separate node does not have to be the same instance class, you know, as, as, as, as the, >>What, what does that mean? Explain >>That in other words, it's a, you know, you could have BA you know, for instance, you could have a node for operations, that's basically very eye ops intensive, whereas you could have a node let's say for analytics that might be more compute intensive or, or more he, or, or more heavily, you know, configured with, with memory per se. And so the idea here is you can tailor in a node to the workload. So that's, you know what they're saying with, you know, and I forget what they're calling it, but the idea that you can have a different type, you can specify a different type of node, a different type of instance for the analytic node, I think is, you know, is a major step forward >>And that, and that that's enabled by the cloud and architecture. >>Of course. Yes. I mean, we're separating, compute from data is, is, is the starter. And so yeah. Then at that point you can then start to, you know, you know, to go less vanilla. I think, you know, the re you know, the, you know, the, I guess the fruition of this is going to be when they say, okay, you can run your, let's say your operational nodes, you know, dedicated, but we'll let you run your analytic nodes serverless. Can't do it yet, but I've gotta believe that's on the roadmap. >>Yeah. So seq brings a lot of overhead. So you get MQL, but now square this circle for me, cuz now you got Mago talking sequel. >>They had to start doing that some time. I mean, and I it's been a court take I've had from them from the, from the get go, which I said, I understand that you're looking at this as an alternative to SQL and that's perfectly valid, but don't deny the validity of SQL or the reason why we, you know, we need it. The fact is that you have, okay, the number, you know, according to Ty index, JavaScript is the seventh, most popular language. Most SQL follows closely behind at the ninth, most popular language you don't want to cl. And the fact is those people exist in the enterprise and they're, and they're disproportionately concentrated in analytics. I mean, you know, it's getting a little less, so now we're seeing like, you know, basically, you know, Python, the programmatic, but still, you know, a lot of sequel expertise there. It does not make, it makes no sense for Mongo to, to, to ignore or to overlook that audience. I think now they're, you know, you know, they're taking baby steps to start, you know, reaching out to them. >>It's interesting. You see it going both ways. See Oracle announces a Mongo, DB, Mongo. I mean, it's just convergence. You called it not, I love collisions, you know, >>I know it's like, because you thrive on drama and I thrive on can't. We all love each other, but you know, act. But the thing is actually, I've been, I wrote about this. I forget when I think it was like 2014 or 2016. It's when we, I was noticed I was noting basically the, you know, the rise of all these specialized databases and probably Amazon, you know, AWS is probably the best exemplar of that. I've got 15 or 16 or however, number of databases and they're all dedicated purpose. Right. But I also was, you know, basically saw that inevitably there was gonna be some overlap. It's not that all databases were gonna become one and the same we're gonna be, we're gonna become back into like the, you know, into a pan G continent or something like that. But that you're gonna have a relational database that can do JSON and, and a, and a document database that can do relational. I mean, you know, it's, to me, that's a no brainer. >>So I asked Andy Ja one time, I'd love to get your take on this, about those, you know, multiple data stores at the time. They probably had a thousand. I think they're probably up to 15 now, right? Different APIs, different S et cetera. And his response. I said, why don't you make it easier for, for customers and maybe build an abstraction or converge these? And he said, well, it's by design. What if you buy this? And, and what your thoughts are, cuz I, you know, he's a pretty straight shooter. Yeah. It's by design because it allows us as the market moves, we can move with it. And if we, if we give developers access to those low level primitives and APIs, then they can move with, with at market speed. Right. And so that again, by design, now we heard certainly Mongo poo pooing that today they didn't mention, they didn't call out Amazon. Yeah. Oracle has no compunction about specifically calling out Amazon. They do it all the time. What do you make of that? Can't Amazon have its cake and eat it too. In other words, extend some of the functionality of those specific databases without going to the Swiss army. >>I I'll put it this way. You, you kind of tapped in you're, you're sort of like, you know, killing me softly with your song there, which is that, you know, I was actually kind of went on a rant about this, actually know in, you know, come, you know, you know, my year ahead sort of out predictions. And I said, look, cloud folks, it's great that you're making individual SAS, you know, products easy to use. But now that I have to mix and match SAS products, you know, the burden of integration is on my shoulders. Start making my life easier. I think a good, you know, a good example of this would be, you know, for instance, you could take something like, you know, let's say like a Google big query. There's no reason why I can't have a piece of that that might, you know, might be paired, say, you know, say with span or something like that. >>The idea being is that if we're all working off a common, you know, common storage, we, you know, it's in cloud native, we can separate the computer engines. It means that we can use the right engine for the right part of the task. And the thing is that maybe, you know, myself as a consumer, I should not have to be choosing between big query and span. But the thing is, I should be able to say, look, I want to, you know, globally distribute database, but I also wanna do some analytics and therefore behind the scenes, you know, new microservices, it could connect the two wouldn't >>Microsoft synapse be an example of doing that. >>It should be an example. I wish I, I would love to hear more from Microsoft about this. They've been radio silent for about the past two or three years in data. You hardly hear about it, but synapse is actually those actually one of the ideas I had in mind now keep in mind that with synapse, you're not talking about, let's say, you know, I mean, it's, it's obviously a sequel data warehouse. It's not pure spark. It's basically their, it was their curated version of spark, but that's fine. But again, I would love to hear Microsoft talk more about that. They've been very quiet. >>Yeah. You, you, the intent is there to >>Simplify >>It exactly. And create an abstraction. Exactly. Yeah. They have been quiet about it. Yeah. Yeah. You would expect that, that maybe they're still trying to figure it out. So what's your prognosis from Mongo? I mean, since this company IP, you know, usually I, I tell and I tell everybody this, especially my kids, like don't buy a stock at IPO. You'll always get a better chance at a cheaper price to buy it. Yeah. And even though that was true with Mongo, you didn't have a big window. No. Like you did, for instance, with, with Facebook, certainly that's been the case with snowflake and sure. Alibaba, I mean, I name a zillion style was almost universal. Yeah. But, but since that, that, that first, you know, few months, period, this, this company has been on a roll. Right. And it, it obviously has been some volatility, but the execution has been outstanding. >>No question about that. I mean, the thing is, look what I, what I, and I'm just gonna talk on the product side on the sales side. Yeah. But on the product side, from the get go, they made a product that was easy for developers. Whereas let's say someone's giving an example, for instance, Cosmo CB, where to do certain operations. They had to go through multiple services in, you know, including Azure portal with Atlas, it's all within Atlas. So they've really, it's been kinda like design thinking from the start initially with, with the core Mongo DB, you know, you, the on premise, both this predates Atlas, I mean, part of it was that they were coming with a language that developers knew was just Javas script. The construct that they knew, which was JS on. So they started with that home core advantage, but they weren't the only ones doing that. But they did it with tooling that was very intuitive to developers that met developers, where they lived and what I give them, you know, then additional credit for is that when they went to the cloud and it wasn't an immediate thing, Atlas was not an overnight success, but they employed that same design thinking to Atlas, they made Atlas a good cloud experience. They didn't just do a lift and shift the cloud. And so that's why today basically like five or six years later, Atlas's most of their business. >>Yeah. It's what, 60% of the business now. Yeah. And then Dave, on the, on the earning scholar, maybe it wasn't Dave and somebody else in response to question said, yeah, ultimately this is the future will be be 90% of the business. I'm not gonna predict when. So my, my question is, okay, so let's call that the midterm midterm ATLA is gonna be 90% of the business with some exceptions that people just won't move to the cloud. What's next is the edge. A new opportunity is Mongo architecturally suited for the, I mean, it's certainly suited for the right, the home Depot store. Sure. You know, at the edge. Yeah. If you, if you consider that edge, which I guess it is form of edge, but how about the far edge EVs cell towers, you know, far side, real time, AI inferencing, what's the requirement there, can Mongo fit there? Any thoughts >>On that? I think the AI and the inferencing stuff is interesting. It's something which really Mongo has not tackled yet. I think we take the same principle, which is the lightweight stuff. In other words, you'll say, do let's say a classification or a prediction or some sort of prescriptive action in other words, where you're not doing some convolution, neural networking and trying to do like, you know, text, text to voice or, or, or vice versa. Well, you're not trying to do all that really fancy stuff. I think that's, you know, if you're keeping it SIM you know, kinda like the kiss principle, I think that's very much within Mongo's future. I think with the realm they have, they basically have the infrastructure to go out to the edge. I think with the fact that they've embraced GraphQL has also made them a lot more extensible. So I think they certainly do have, you know, I, I do see the edge as being, you know, you know, in, in, you know, in their, in their pathway. I do see basically lightweight analytics and lightweight, let's say machine learning definitely in their >>Future. And, but, and they would, would you agree that they're in a better position to tap that opportunity than say a snowflake or an Oracle now maybe M and a can change that. R D can maybe change that, but fundamentally from an architectural standpoint yeah. Are they in a better position? >>Good question. I think that that Mongo snowflake by virtual fact, I mean that they've been all, you know, all cloud start off with, I think makes it more difficult, not impossible to move out to the edge, but it means that, and I, and know, and I, and I said, they're really starting to making some tentative moves in that direction. I'm looking forward to next week to, you know, seeing what, you know, hearing what we're gonna, what they're gonna be saying about that. But I do think, right. You know, you know, to answer your question directly, I'd say like right now, I'd say Mongo probably has a, you know, has a head start there. >>I'm losing track of time. I could go forever with you. Tony bear DB insight with tons of insights. Thanks so much for coming back with. >>It's only one insight insight, Dave. Good to see you again. All >>Right. Good to see you. Thank you. Okay. Keep it right there. Right back at the Java center, Mongo DB world 2022, you're watching the cube.