(light music) >> Announcer: TheCUBE's live coverage is made possible by funding from Dell Technologies. Creating technologies that drive human progress. (upbeat music) >> Welcome back to the Fira in Barcelona. Dave Vellante with Dave Nicholson. Lisa Martin's been here all week. John Furrier is in our Palo Alto studio, banging out all the news. Don't forget to check out siliconangle.com, thecube.net. This is day four, our last segment, winding down. MWC23, super excited to be here. Wayne Duso, friend of theCUBE, VP of engineering from products at AWS is here with Iyad Tarazi, who's the CEO of Federated Wireless. Gents, welcome. >> Good to be here. >> Nice to see you. >> I'm so stoked, Wayne, that we connected before the show. We texted, I'm like, "You're going to be there. I'm going to be there. You got to come on theCUBE." So thank you so much for making time, and thank you for bringing a customer partner, Federated Wireless. Everybody knows AWS. Iyad, tell us about Federated Wireless. >> We're a software and services company out of Arlington, Virginia, right outside of Washington, DC, and we're really focused on this new technology called Shared Spectrum and private wireless for 5G. Think of it as enterprises consuming 5G, the way they used to consume WiFi. >> Is that unrestricted spectrum, or? >> It is managed, organized, interference free, all through cloud platforms. That's how we got to know AWS. We went and got maybe about 300 products from AWS to make it work. Quite sophisticated, highly available, and pristine spectrum worth billions of dollars, but available for people like you and I, that want to build enterprises, that want to make things work. Also carriers, cable companies everybody else that needs it. It's really a new revolution for everyone. >> And that's how you, it got introduced to AWS. Was that through public sector, or just the coincidence that you're in DC >> No, I, well, yes. The center of gravity in the world for spectrum is literally Arlington. You have the DOD spectrum people, you have spectrum people from National Science Foundation, DARPA, and then you have commercial sector, and you have the FCC just an Uber ride away. So we went and found the scientists that are doing all this work, four or five of them, Virginia Tech has an office there too, for spectrum research for the Navy. Come together, let's have a party and make a new model. >> So I asked this, I'm super excited to have you on theCUBE. I sat through the keynotes on Monday. I saw Satya Nadella was in there, Thomas Kurian there was no AWS. I'm like, where's AWS? AWS is everywhere. I mean, you guys are all over the show. I'm like, "Hey, where's the number one cloud?" So you guys have made a bunch of announcements at the show. Everybody's talking about the cloud. What's going on for you guys? >> So we are everywhere, and you know, we've been coming to this show for years. But this is really a year that we can demonstrate that what we've been doing for the IT enterprise, IT people for 17 years, we're now bringing for telcos, you know? For years, we've been, 17 years to be exact, we've been bringing the cloud value proposition, whether it's, you know, cost efficiencies or innovation or scale, reliability, security and so on, to these enterprise IT folks. Now we're doing the same thing for telcos. And so whether they want to build in region, in a local zone, metro area, on-prem with an outpost, at the edge with Snow Family, or with our IoT devices. And no matter where they want to start, if they start in the cloud and they want to move to the edge, or they start in the edge and they want to bring the cloud value proposition, like, we're demonstrating all of that is happening this week. And, and very much so, we're also demonstrating that we're bringing the same type of ecosystem that we've built for enterprise IT. We're bringing that type of ecosystem to the telco companies, with CSPs, with the ISP vendors. We've seen plenty of announcements this week. You know, so on and so forth. >> So what's different, is it, the names are different? Is it really that simple, that you're just basically taking the cloud model into telco, and saying, "Hey, why do all this undifferentiated heavy lifting when we can do it for you? Don't worry about all the plumbing." Is it really that simple? I mean, that straightforward. >> Well, simple is probably not what I'd say, but we can make it straightforward. >> Conceptually. >> Conceptually, yes. Conceptually it is the same. Because if you think about, firstly, we'll just take 5G for a moment, right? The 5G folks, if you look at the architecture for 5G, it was designed to run on a cloud architecture. It was designed to be a set of services that you could partition, and run in different places, whether it's in the region or at the edge. So in many ways it is sort of that simple. And let me give you an example. Two things, the first one is we announced integrated private wireless on AWS, which allows enterprise customers to come to a portal and look at the industry solutions. They're not worried about their network, they're worried about solving a problem, right? And they can come to that portal, they can find a solution, they can find a service provider that will help them with that solution. And what they end up with is a fully validated offering that AWS telco SAS have actually put to its paces to make sure this is a real thing. And whether they get it from a telco, and, and quite frankly in that space, it's SIs such as Federated that actually help our customers deploy those in private environments. So that's an example. And then added to that, we had a second announcement, which was AWS telco network builder, which allows telcos to plan, deploy, and operate at scale telco network capabilities on the cloud, think about it this way- >> As a managed service? >> As a managed service. So think about it this way. And the same way that enterprise IT has been deploying, you know, infrastructure as code for years. Telco network builder allows the telco folks to deploy telco networks and their capabilities as code. So it's not simple, but it is pretty straightforward. We're making it more straightforward as we go. >> Jump in Dave, by the way. He can geek out if you want. >> Yeah, no, no, no, that's good, that's good, that's good. But actually, I'm going to ask an AWS question, but I'm going to ask Iyad the AWS question. So when we, when I hear the word cloud from Wayne, cloud, AWS, typically in people's minds that denotes off-premises. Out there, AWS data center. In the telecom space, yes, of course, in the private 5G space, we're talking about a little bit of a different dynamic than in the public 5G space, in terms of the physical infrastructure. But regardless at the edge, there are things that need to be physically at the edge. Do you feel that AWS is sufficiently, have they removed the H word, hybrid, from the list of bad words you're not allowed to say? 'Cause there was a point in time- >> Yeah, of course. >> Where AWS felt that their growth- >> They'll even say multicloud today, (indistinct). >> No, no, no, no, no. But there was a period of time where, rightfully so, AWS felt that the growth trajectory would be supported solely by net new things off premises. Now though, in this space, it seems like that hybrid model is critical. Do you see AWS being open to the hybrid nature of things? >> Yeah, they're, absolutely. I mean, just to explain from- we're a services company and a solutions company. So we put together solutions at the edge, a smart campus, smart agriculture, a deployment. One of our biggest deployment is a million square feet warehouse automation project with the Marine Corps. >> That's bigger than the Fira. >> Oh yeah, it's bigger, definitely bigger than, you know, a small section of here. It's actually three massive warehouses. So yes, that is the edge. What the cloud is about is that massive amount of efficiency has happened by concentrating applications in data centers. And that is programmability, that is APIs that is solutions, that is applications that can run on it, where people know how to do it. And so all that efficiency now is being ported in a box called the edge. What AWS is doing for us is bringing all the business and technical solutions they had into the edge. Some of the data may send back and forth, but that's actually a smaller piece of the value for us. By being able to bring an AWS package at the edge, we're bringing IoT applications, we're bringing high speed cameras, we're able to integrate with the 5G public network. We're able to bring in identity and devices, we're able to bring in solutions for students, embedded laptops. All of these things that you can do much much faster and cheaper if you are able to tap in the 4,000, 5,000 partners and all the applications and all the development and all the models that AWS team did. By being able to bring that efficiency to the edge why reinvent that? And then along with that, there are partners that you, that help do integration. There are development done to make it hardened, to make the data more secure, more isolated. All of these things will contribute to an edge that truly is a carbon copy of the data center. >> So Wayne, it's AWS, Regardless of where the compute, networking and storage physically live, it's AWS. Do you think that the term cloud will sort of drift away from usage? Because if, look, it's all IT, in this case it's AWS and federated IT working together. How, what's your, it's sort of a obscure question about cloud, because cloud is so integrated. >> You Got this thing about cloud, it's just IT. >> I got thing about cloud too, because- >> You and Larry Ellison. >> Because it's no, no, no, I'm, yeah, well actually there's- >> There's a lot of IT that's not cloud, just say that okay. >> Now, a lot of IT that isn't cloud, but I would say- >> But I'll (indistinct) cloud is an IT tool, and you see AWS obviously with the Snow fill in the blank line of products and outpost type stuff. Fair to say that you're, doesn't matter where it is, it could be AWS if it's on the edge, right? >> Well, you know, everybody wants to define the cloud as what it may have been when it started. But if you look at what it was when it started and what it is today, it is different. But the ability to bring the experience, the AWS experience, the services, the operational experience and all the things that Iyad had been talking about from the region all to all the way to, you know, the IoT device, if you would, that entire continuum. And it doesn't matter where you start. Like if you start in region and you need to bring your value to other places because your customers are asking you to do so, we're enabling that experience where you need to bring it. If you started at the edge, and- but you want to build cloud value, you know, whether it's again, cost efficiency, scalability, AI, ML or analytics into those capabilities, you can start at the edge with the same APIs, with the same service, the same capabilities, and you can build that value in right from the get go. You don't build this bifurcation or many separations and try to figure out how do I glue them together? There is no gluing together. So if you think of cloud as being elastic, scalable flexible, where you can drive innovation, it's the same exact model on the continuum. And you can start at either end, it's up to you as a customer. >> And I think if, the key to me is the ecosystem. I mean, if you can do for this industry what you've done for the technology- enterprise technology business from an ecosystem standpoint, you know everybody talks about flywheel, but that gives you like the massive flywheel. I don't know what the ratio is, but it used to be for every dollar spent on a VMware license, $15 is spent in the ecosystem. I've never heard similar ratios in the AWS ecosystem, but it's, I go to reinvent and I'm like, there's some dollars being- >> That's a massive ecosystem. >> (indistinct). >> And then, and another thing I'll add is Jose Maria Alvarez, who's the chairman of Telefonica, said there's three pillars of the future-ready telco, low latency, programmable networks, and he said cloud and edge. So they recognizing cloud and edge, you know, low latency means you got to put the compute and the data, the programmable infrastructure was invented by Amazon. So what's the strategy around the telco edge? >> So, you know, at the end, so those are all great points. And in fact, the programmability of the network was a big theme in the show. It was a huge theme. And if you think about the cloud, what is the cloud? It's a set of APIs against a set of resources that you use in whatever way is appropriate for what you're trying to accomplish. The network, the telco network becomes a resource. And it could be described as a resource. We, I talked about, you know, network as in code, right? It's same infrastructure in code, it's telco infrastructure as code. And that code, that infrastructure, is programmable. So this is really, really important. And in how you build the ecosystem around that is no different than how we built the ecosystem around traditional IT abstractions. In fact, we feel that really the ecosystem is the killer app for 5G. You know, the killer app for 4G, data of sorts, right? We started using data beyond simple SMS messages. So what's the killer app for 5G? It's building this ecosystem, which includes the CSPs, the ISVs, all of the partners that we bring to the table that can drive greater value. It's not just about cost efficiency. You know, you can't save your way to success, right? At some point you need to generate greater value for your customers, which gives you better business outcomes, 'cause you can monetize them, right? The ecosystem is going to allow everybody to monetize 5G. >> 5G is like the dot connector of all that. And then developers come in on top and create new capabilities >> And how different is that than, you know, the original smartphones? >> Yeah, you're right. So what do you guys think of ChatGPT? (indistinct) to Amazon? Amazon turned the data center into an API. It's like we're visioning this world, and I want to ask that technologist, like, where it's turning resources into human language interfaces. You know, when you see that, you play with ChatGPT at all, or I know you guys got your own. >> So I won't speak directly to ChatGPT. >> No, don't speak from- >> But if you think about- >> Generative AI. >> Yeah generative AI is important. And, and we are, and we have been for years, in this space. Now you've been talking to AWS for a long time, and we often don't talk about things we don't have yet. We don't talk about things that we haven't brought to market yet. And so, you know, you'll often hear us talk about something, you know, a year from now where others may have been talking about it three years earlier, right? We will be talking about this space when we feel it's appropriate for our customers and our partners. >> You have talked about it a little bit, Adam Selipsky went on an interview with myself and John Furrier in October said you watch, you know, large language models are going to be enormous and I know you guys have some stuff that you're working on there. >> It's, I'll say it's exciting. >> Yeah, I mean- >> Well proof point is, Siri is an idiot compared to Alexa. (group laughs) So I trust one entity to come up with something smart. >> I have conversations with Alexa and Siri, and I won't judge either one. >> You don't need, you could be objective on that one. I definitely have a preference. >> Are the problems you guys solving in this space, you know, what's unique about 'em? What are they, can we, sort of, take some examples here (indistinct). >> Sure, the main theme is that the enterprise is taking control. They want to have their own networks. They want to focus on specific applications, and they want to build them with a skeleton crew. The one IT person in a warehouse want to be able to do it all. So what's unique about them is that they're now are a lot of automation on robotics, especially in warehousing environment agriculture. There simply aren't enough people in these industries, and that required precision. And so you need all that integration to make it work. People also want to build these networks as they want to control it. They want to figure out how do we actually pick this team and migrate it. Maybe just do the front of the house first. Maybe it's a security team that monitor the building, maybe later on upgrade things that use to open doors and close doors and collect maintenance data. So that ability to pick what you want to do from a new processors is really important. And then you're also seeing a lot of public-private network interconnection. That's probably the undercurrent of this show that haven't been talked about. When people say private networks, they're also talking about something called neutral host, which means I'm going to build my own network, but I want it to work, my Verizon (indistinct) need to work. There's been so much progress, it's not done yet. So much progress about this bring my own network concept, and then make sure that I'm now interoperating with the public network, but it's my domain. I can create air gaps, I can create whatever security and policy around it. That is probably the power of 5G. Now take all of these tiny networks, big networks, put them all in one ecosystem. Call it the Amazon marketplace, call it the Amazon ecosystem, that's 5G. It's going to be tremendous future. >> What does the future look like? We're going to, we just determined we're going to be orchestrating the network through human language, okay? (group laughs) But seriously, what's your vision for the future here? You know, both connectivity and cloud are on on a continuum. It's, they've been on a continuum forever. They're going to continue to be on a continuum. That being said, those continuums are coming together, right? They're coming together to bring greater value to a greater set of customers, and frankly all of us. So, you know, the future is now like, you know, this conference is the future, and if you look at what's going on, it's about the acceleration of the future, right? What we announced this week is really the acceleration of listening to customers for the last handful of years. And, we're going to continue to do that. We're going to continue to bring greater value in the form of solutions. And that's what I want to pick up on from the prior question. It's not about the network, it's not about the cloud, it's about the solutions that we can provide the customers where they are, right? And if they're on their mobile phone or they're in their factory floor, you know, they're looking to accelerate their business. They're looking to accelerate their value. They're looking to create greater safety for their employees. That's what we can do with these technologies. So in fact, when we came out with, you know, our announcement for integrated private wireless, right? It really was about industry solutions. It really isn't about, you know, the cloud or the network. It's about how you can leverage those technologies, that continuum, to deliver you value. >> You know, it's interesting you say that, 'cause again, when we were interviewing Adam Selipsky, everybody, you know, all journalists analysts want to know, how's Adam Selipsky going to be different from Andy Jassy, what's the, what's he going to do to Amazon to change? And he said, listen, the real answer is Amazon has changed. If Andy Jassy were here, we'd be doing all, you know, pretty much the same things. Your point about 17 years ago, the cloud was S3, right, and EC2. Now it's got to evolve to be solutions. 'Cause if that's all you're selling, is the bespoke services, then you know, the future is not as bright as the past has been. And so I think it's key to look for what are those outcomes or solutions that customers require and how you're going to meet 'em. And there's a lot of challenges. >> You continue to build value on the value that you've brought, and you don't lose sight of why that value is important. You carry that value proposition up the stack, but the- what you're delivering, as you said, becomes maybe a bigger or or different. >> And you are getting more solution oriented. I mean, you're not hardcore solutions yet, but we're seeing more and more of that. And that seems to be a trend. We've even seen in the database world, making things easier, connecting things. Not really an abstraction layer, which is sort of antithetical to your philosophy, but it creates a similar outcome in terms of simplicity. Yeah, you're smiling 'cause you guys always have a different angle, you know? >> Yeah, we've had this conversation. >> It's right, it's, Jassy used to say it's okay to be misunderstood. >> That's Right. For a long time. >> Yeah, right, guys, thanks so much for coming to theCUBE. I'm so glad we could make this happen. >> It's always good. Thank you. >> Thank you so much. >> All right, Dave Nicholson, for Lisa Martin, Dave Vellante, John Furrier in the Palo Alto studio. We're here at the Fira, wrapping out MWC23. Keep it right there, thanks for watching. (upbeat music)

>> Narrator: theCUBE's live coverage is made possible by funding from Dell Technologies, creating technologies that drive human progress. (upbeat music) >> Welcome back to the Fira in Barcelona. This is Dave Vellante with David Nicholson. Lisa Martin is also here. This is day two of our coverage of MWC 23 on theCUBE. We're super excited. We're in between hall four and five. Stop by if you're here. Dennis Hoffman is here. He's the senior vice president and general manager of the Telecom systems business at Dell Technologies, and he's joined by Yousef Khalidi, who's the corporate vice president of Azure for Operators from Microsoft. Gents, Welcome. >> Thanks, Dave. >> Thank you. >> So we saw Satya in the keynote. He wired in. We saw T.K. came in. No AWS. I don't know. They're maybe not part of the show, but maybe next year they'll figure it out. >> Indeed, indeed. >> Lots of stuff happened in the Telecom, but the Azure operator distributed service is the big news, you guys got here. What's that all about? >> Oh, first of all, we changed the name. >> Oh, you did? >> You did? >> Oh, yeah. We have a real name now. It's called the Azure Operator Nexus. >> Oh, I like Nexus better than that. >> David: That's much better, much better. >> Dave: The engineers named it first time around. >> I wish, long story, but thank you for our marketing team. But seriously, not only did we rename the platform, we expanded the platform. >> Dave: Yeah. >> So it now covers the whole spectrum from the far-edge to the public cloud as well, including the near-edge as well. So essentially, it's a hybrid platform that can also run network functions. So all these operators around you, they now have a platform which combines cloud technologies with the choice where they want to run, optimized for the network. >> Okay and so, you know, we've talked about the disaggregation of the network and how you're bringing kind of engineered systems to the table. We've seen this movie before, but Dennis, there are differences, right? I mean, you didn't really have engineered systems in the 90s. You didn't have those integration points. You really didn't have the public cloud, you didn't have AI. >> Right. >> So you have all those new powers that you can tap, so give us the update from your perspective, having now spent a day and a half here. What's the vibe, what's the buzz, and what's your take on everything? >> Yeah, I think to build on what Yousef said, there's a lot going on with people still trying to figure out exactly how to architect the Telecom network of the future. They know it's got to have a lot to do with cloud. It does have some pretty significant differences, one of those being, there's definitely got to be a hybrid component because there are pieces of the Telecom network that even when modernized will not end up centralized, right? They're going to be highly distributed. I would say though, you know, we took away two things, yesterday, from all the meetings. One, people are done, I think the network operators are done, questioning technology readiness. They're now beginning to wrestle with operationalization of it all, right? So it's like, okay, it's here. I can in fact build a modern network in a very cloud native way, but I've got to figure out how to do that all. And another big part of it is the ecosystem and certainly the partnership long standing between Dell and Microsoft which we're extending into this space is part of that, making it easier on people to actually acquire, deploy, and importantly, support these new technologies. >> So a lot of the traditional carriers, like you said, they're sort of beyond the technology readiness. Jose Maria Alvarez in the keynote said there are three pillars to the future Telecom network. He said low latency, programmable networks, and then cloud and edge, kind of threw that in. You agree with that, Yousef? (Dave and Yousef speaking altogether) >> I mean, we've been for years talking about the cloud and edge. >> Yeah. >> Satya for years had the same graphic. We still have it. Today, we have expanded the graphic a bit to include the network as one, because you can have a cloud without connectivity as well but this is very, very, very, very much true. >> And so the question then, Dennis, is okay, you've got disruptors, we had Dish on yesterday. >> Oh, did you? Good. >> Yeah, yeah, and they're talking about what they're doing with, you know, ORAN and all the applications, really taking account of it. What I see is a developer friendly, you know, environment. You got the carriers talking about how they're going to charge developers for APIs. I think they've published eight APIs which is nowhere near enough. So you've got that sort of, you know, inertia and yet, you have the disruptors that are going to potentially be a catalyst to, you know, cross the chasm, if you will. So, you know, put on your strategy hat. >> Yeah. >> Dave: How do you see that playing out? >> Well, they're trying to tap into three things, the disruptors. You know, I think the thesis is, "If I get to a truly cloud native, communications network first, I ought to have greater agility so that I can launch more services and create more revenue streams. I ought to be lower cost in terms of both acquisition cost and operating cost, right, and I ought to be able to create scale between my IT organization, everything I know how to do there and my Telecom network." You know, classic, right? Better, faster, cheaper if I embrace cloud early on. And people like Dish, you know, they have a clean sheet of paper with which to do that. So innovation and rate of innovation is huge for them. >> So what would you do? We put your Clay Christensen hat on, now. What if you were at a traditional Telco who's like, complaining about- >> You're going to get me in trouble. >> Dave: Come on, come on. >> Don't do it. >> Dave: Help him out. Help him out, help him out. So if, you know, they're complaining about CapEx, they're highly regulated, right, they want net neutrality but they want to be able to sort of dial up the cost of those using the network. So what would you do? Would you try to disrupt yourself? Would you create a skunkworks? Would you kind of spin off a disruptor? That's a real dilemma for those guys. >> Well for mobile network operators, the beauty of 5G is it's the first cloud native cellular standard. So I don't know if anybody's throwing these terms around, but 5G SA is standalone, right? >> Dave: Yeah, yeah. >> So a lot of 'em, it's not a skunkworks. They're just literally saying, "I've got to have a 5G network." And some of 'em are deciding, "I'm going to stand it up all by itself." Now, that's duplicative expense in a lot of ways, but it creates isolation from the two networks. Others are saying, "No, it's got to be NSA. I've got to be able to combine 4G and 5G." And then you're into the brownfield thing. >> That's the hybrid. >> Not hybrid as in cloud, but hybrid as in, you know. >> Yeah, yeah. >> It's a converge network. >> Dave: Yeah, yeah. >> So, you know, I would say for a lot of them, they're adopting, probably rightly so, a wait and see attitude. One thing we haven't talked about and you got to get on the table, their high order bit is resilience. >> Dave: Yeah, totally. >> David: Yeah. >> Right? Can't go down. It's national, secure infrastructure, first responder. >> Indeed. >> Anytime you ask them to embrace any new technology, the first thing that they have to work through in their minds is, you know, "Is the juice worth the squeeze? Like, can I handle the risk?" >> But you're saying they're not questioning the technology. Aren't they questioning ORAN in terms of the quality of service, or are they beyond that? >> Dennis: They're questioning the timing, not the inevitability. >> Okay, so they agree that ORAN is going to be open over time. >> At some point, RAN will be cloud native, whether it's ORAN the spec, open RAN the concept, (Yousef speaking indistinctly) >> Yeah. >> Virtual RAN. But yeah, I mean I think it seems pretty evident at this point that the mainframe will give way to open systems once again. >> Dave: Yeah, yeah, yeah. >> ERAN, ecosystem RAN. >> Any RAN. (Dave laughing) >> You don't have to start with the ORAN where they're inside the house. So as you probably know, our partner AT&T started with the core. >> Dennis: They almost all have. >> And they've been on the virtualization path since 2014 and 15. And what we are working with them on is the hybrid cloud model to expand all the way, if you will, as I mentioned to the far-edge or the public cloud. So there's a way to be in the brownfield environment, yet jump on the new bandwagon of technology without necessarily taking too much risk, because you're quite right. I mean, resiliency, security, service assurance, I mean, for example, AT&T runs the first responder network for the US on their network, on our platform, and I'm personally very familiar of how high the bar is. So it's doable, but you need to go in stages, of course. >> And they've got to do that integration. >> Yes. >> They do. >> And Yousef made a great point. Like, out of the top 30 largest Telcos by CapEx outside of China, three quarters of them have virtualized their core. So the cloudification, if you will, software definition run on industry standard hardware, embraced cloud native principles, containerized apps, that's happened in the core. It's well accepted. Now it's just a ripple-down through the network which will happen as and when things are faster, better, cheaper. >> Right. >> So as implemented, what does this look like? Is it essentially what we used to loosely refer to as Azure stacked software, running with Dell optimized Telecom infrastructure together, sometimes within a BBU, out in a hybrid cloud model communicating back to Azure locations in some cases? Is that what we're looking at? >> Approximately. So you start with the near-edge, okay? So the near-edge lives in the operator's data centers, edges, whatever the case may be, built out of off the shelf hardware. Dell is our great partner there but in principle, it could be different mix and match. So once you have that true near-edge, then you can think of, "Okay, how can I make sure this environment is as uniform, same APIs, same everything, regardless what the physical location is?" And this is key, key for the network function providers and the NEPs because they need to be able to port once, run everywhere, and it's key for the operator to reduce their costs. You want to teach your workforce, your operations folks, if you will, how to manage this system one time, to automation and so forth. So, and that is actually an expansion of the Azure capabilities that people are familiar with in a public cloud, projected into different locations. And we have technology called Arc which basically models everything. >> Yeah, yeah. >> So if you have trained your IT side, you are halfway there, how to manage your new network. Even though of course the network is carrier graded, there's different gear. So yes, what you said, a lot of it is true but the actual components, whatever they might be running, are carrier grade, highly optimized, the next images and our solution is not a DIY solution, okay? I know you cater to a wide spectrum here but for us, we don't believe in the TCO. The proper TCO can be achieved by just putting stuff by yourself. We just published a report with Analysys Mason that shows that our approach will save 36 percent of the cost compared to a DIY approach. >> Dave: What percent? >> 36 percent. >> Dave: Of the cost? >> Of, compared to DIY, which is already cheaper than classical models. >> And there's a long history of fairly failed DIY, right, >> Yeah. >> That preceded this. As in the early days of public cloud, the network operators wrestled with, "Do I have to become one to survive?" >> Dave: Yeah. Right. >> So they all ended up having cloud projects and by and large, they've all dematerialized in favor of this. >> Yeah, and it's hard for them to really invest at scale. Let me give you an example. So, your biggest tier one operator, without naming anybody, okay, how many developers do they have that can build and maintain an OS image, or can keep track of container technology, or build monitoring at scale? In our company, we have literally thousands of developers doing it already for the cloud and all we're doing for the operator segment is customizing it and focusing it at the carrier grade aspects of it. But so, I don't have half a dozen exterior experts. I literally have a building of developers who can do that and I'm being literal, here. So it's a scale thing. Once you have a product that you can give to multiple people, everybody benefits. >> Dave: Yeah, and the carriers are largely, they're equipment engineers in a large setting. >> Oh, they have a tough job. I always have total respect what they do. >> Oh totally, and a lot of the work happens, you know, kind of underground and here they are. >> They are network operators. >> They don't touch. >> It's their business. >> Right, absolutely, and they're good at it. They're really good at it. That's right. You know, you think about it, we love to, you know, poke fun at the big carriers, but think about what happened during the pandemic. When they had us shift everything to remote work, >> Dennis: Yes. >> Landline traffic went through the roof. You didn't even notice. >> Yep. That's very true. >> I mean, that's the example. >> That's very true. >> However, in the future where there's innovation and it's going to be driven by developers, right, that's where the open ecosystem comes in. >> Yousef: Indeed. >> And that's the hard transition for a lot of these folks because the developers are going to win that with new workloads, new applications that we can't even think of. >> Dennis: Right. And a lot of it is because if you look at it, there's the fundamental back strategy hat back on, fundamental dynamics of the industry, forced investment, flat revenues. >> Dave: Yeah. Right. >> Very true. >> Right? Every few years, a new G comes out. "Man, I got to retool this massive thing and where I can't do towers, I'm dropping fiber or vice a versa." And meanwhile, most diversification efforts into media have failed. They've had to unwind them and resell them. There's a lot of debt in the industry. >> Yousef: Yeah. >> Dennis: And so, they're looking for that next big, adjacent revenue stream and increasingly deciding, "If I don't modernize my network, I can't get it." >> Can't do it. >> Right, and again, what I heard from some of the carriers in the keynote was, "We're going to charge for API access 'cause we have data in the network." Okay, but I feel like there's a lot more innovation beyond that that's going to come from the disruptors. >> Dennis: Oh yeah. >> Yousef: Yes. >> You know, that's going to blow that away, right? And then that may not be the right model. We'll see, you know? I mean, what would Microsoft do? They would say, "Here, here's a platform. Go develop." >> No, I'll tell you. We are actually working with CAMARA and GSMA on the whole API layer. We actually announced a service as well as (indistinct). >> Dave: Yeah, yeah, right. >> And the key there, frankly, in my opinion, are not the disruptors as in operators. It's the ISV community. You want to get developers that can write to a global set of APIs, not per Telco APIs, such that they can do the innovation. I mean, this is what we've seen in other industries, >> Absolutely. >> That I critically can think of. >> This is the way they get a slice of that pie, right? The recent history of this industry is one where 4G LTE begot the smartphone and app store era, a bevy of consumer services, and almost every single profit stream went somewhere other than the operator, right? >> Yousef: Someone else. So they're looking at this saying, "Okay, 5G is the enterprise G and there's going to be a bevy of applications that are business service related, based on 5G capability and I can't let the OTT, over the top, thing happen again." >> Right. >> They'll say that. "We cannot let this happen." >> "We can't let this happen again." >> Okay, but how do they, >> Yeah, how do they make that not happen? >> Not let it happen again? >> Eight APIs, Dave. The answer is eight APIs. No, I mean, it's this approach. They need to make it easy to work with people like Yousef and more importantly, the developer community that people like Yousef and his company have found a way to harness. And by the way, they need to be part of that developer community themselves. >> And they're not, today. They're not speaking that developer language. >> Right. >> It's hard. You know, hey. >> Dennis: Hey, what's the fastest way to sell an enterprise, a business service? Resell Azure, Teams, something, right? But that's a resale. >> Yeah, that's a resale thing. >> See, >> That's not their service. >> They also need to free their resources from all the plumbing they do and leave it to us. We are plumbers, okay? >> Dennis: We are proud plumbers. >> We are proud plumbers. I'm a plumber. I keep telling people this thing. We had the same discussion with banks and enterprises 10 years ago, by the way. Don't do the plumbing. Go add value on the top. Retool your workforce to do applications and work with ISVs to the verticals, as opposed to either reselling, which many do, or do the plumbing. You'd be surprised. Traditionally, many operators do around, "I want to plumb this thing to get this small interrupt per second." Like, who cares? >> Well, 'cause they made money on connectivity. >> Yes. >> And we've seen this before. >> And in a world without telephone poles and your cables- >> Hey, if what you have is a hammer, everything's a nail, right? And we sell connectivity services and that's what we know how to do, and that both build and sell. And if that's no longer driving a revenue stream sufficient to cover this forced investment march, not to mention Huawei rip and government initiatives to pull infrastructure out and accelerate investment, they got to find new ways. >> I mean, the regulations have been tough, right? They don't go forward and ask for permission. They really can't, right? They have to be much more careful. >> Dennis: It is tough. >> So, we don't mean to sound like it's easy for these guys. >> Dennis: No, it's not. >> But it does require a new mindset, new skillsets, and I think some of 'em are going to figure it out and then pff, the wave, and you guys are going to be riding that wave. >> We're going to try. >> Definitely. Definitely. >> As a veteran of working with both Dell and Microsoft, specifically Azure on things, I am struck by how you're very well positioned in this with Microsoft in particular. Because of Azure's history, coming out of the on-premises world that Microsoft knows so well, there's a natural affinity to the hybrid nature of Telecom. We talk about edge, we talk about hybrid, this is it, absolutely the center of it. So it seems like a- >> Yousef: Indeed. Actually, if you look at the history of Azure, from day one, and I was there from day one, we always spoke of the hybrid model. >> Yeah. >> The third point, we came from the on-premises world. >> David: Right. >> And don't get me wrong, I want people to use the public cloud, but I also know due to physics, regulation, geopolitical boundaries, there's something called on-prem, something called an edge here. I want to add something else. Remember our deal on how we are partner-centric? We're applying the same playbook, here. So, you know, for every dollar we make, so many of it's been done by the ecosystem. Same applies here. So we have announced partnerships with Ericson, Nokia, (indistinct), all the names, and of course with Dell and many others. The ecosystem has to come together and customers must retain their optionality to drum up whatever they are on. So it's the same playbook, with this. >> And enterprise technology companies are, actually, really good at, you know, decoding the customer, figuring out specific requirements, making some mistakes the first time through and then eventually getting it right. And as these trends unfold, you know, you're in a good position, I think, as are others and it's an exciting time for enterprise tech in this industry, you know? >> It really is. >> Indeed. >> Dave: Guys, thanks so much for coming on. >> Thank you. >> Dave: It's great to see you. Have a great rest of the show. >> Thank you. >> Thanks, Dave. Thank you, Dave. >> All right, keep it right there. John Furrier is live in our studio. He's breaking down all the news. Go to siliconangle.com to go to theCUBE.net. Dave Vellante, David Nicholson and Lisa Martin, we'll be right back from the theater in Barcelona, MWC 23 right after this short break. (relaxing music)

(gentle music) >> Announcer: "theCube's" live coverage is made possible by funding from Dell Technologies, creating technologies that drive human progress. (upbeat music) (logo whooshing) >> Hey, everyone, welcome back to "theCube's" coverage of day one, MWC23 live from Barcelona, Lisa Martin here with Dave Vellante. Dave, we've got some great conversations so far This is the biggest, most packed show I've been to in years. About 80,000 people here so far. >> Yeah, down from its peak of 108, but still pretty good. You know, a lot of folks from China come to this show, but with the COVID situation in China, that's impacted the attendance, but still quite amazing. >> Amazing for sure. We're going to be talking about trends and mobility, and all sorts of great things. We have a couple of guests joining us for the first time on "theCUBE." Please welcome Dr. Srinivas Mukkamala or Sri, chief product officer at Ivanti. And Dave Shepherd, VP Ivanti. Guys, welcome to "theCUBE." Great to have you here. >> Thank you. >> So, day one of the conference, Sri, we'll go to you first. Talk about some of the trends that you're seeing in mobility. Obviously, the conference renamed from Mobile World Congress to MWC mobility being part of it, but what are some of the big trends? >> It's interesting, right? I mean, I was catching up with Dave. The first thing is from the keynotes, it took 45 minutes to talk about security. I mean, it's quite interesting when you look at the shore floor. We're talking about Edge, we're talking about 5G, the whole evolution. And there's also the concept of are we going into the Cloud? Are we coming back from the Cloud, back to the Edge? They're really two different things. Edge is all decentralized while you recompute. And one thing I observed here is they're talking about near real-time reality. When you look at automobiles, when you look at medical, when you look at robotics, you can't have things processed in the Cloud. It'll be too late. Because you got to make millisecond-based stations. That's a big trend for me. When I look at staff... Okay, the compute it takes to process in the Cloud versus what needs to happen on-prem, on device, is going to revolutionize the way we think about mobility. >> Revolutionize. David, what are some of the things that you're saying? Do you concur? >> Yeah, 100%. I mean, look, just reading some of the press recently, they're predicting 22 billion IoT devices by 2024. Everything Sri just talked about there. It's growing exponentially. You know, problems we have today are a snapshot. We're probably in the slowest place we are today. Everything's just going to get faster and faster and faster. So it's a, yeah, 100% concur with that. >> You know, Sri, on your point, so Jose Maria Alvarez, the CEO of Telefonica, said there are three pillars of the future of telco, low latency, programmable networks, and Cloud and Edge. So, as to your point, Cloud and low latency haven't gone hand in hand. But the Cloud guys are saying, "All right, we're going to bring the Cloud to the Edge." That's sort of an interesting dynamic. We're going to bypass them. We heard somebody, another speaker say, "You know, Cloud can't do it alone." You know? (chuckles) And so, it's like these worlds need each other in a way, don't they? >> Definitely right. So that's a fantastic way to look at it. The Cloud guys can say, "We're going to come closer to where the computer is." And if you really take a look at it with data localization, where are we going to put the Cloud in, right? I mean, so the data sovereignty becomes a very interesting thing. The localization becomes a very interesting thing. And when it comes to security, it gets completely different. I mean, we talked about moving everything to a centralized compute, really have massive processing, and give you the addition back wherever you are. Whereas when you're localized, I have to process everything within the local environment. So there's already a conflict right there. How are we going to address that? >> Yeah. So another statement, I think, it was the CEO of Ericsson, he was kind of talking about how the OTT guys have heard, "We can't let that happen again. And we're going to find new ways to charge for the network." Basically, he's talking about monetizing the API access. But I'm interested in what you're hearing from customers, right? 'Cause our mindset is, what value you're going to give to customers that they're going to pay for, versus, "I got this data I'm going to charge developers for." But what are you hearing from customers? >> It's amazing, Dave, the way you're looking at it, right? So if we take a look at what we were used to perpetual, and we said we're going to move to a subscription, right? I mean, everybody talks about subscription economy. Telcos on the other hand, had subscription economy for a long time, right? They were always based on usage, right? It's a usage economy. But today, we are basically realizing on compute. We haven't even started charging for compute. If you go to AWS, go to Azure, go to GCP, they still don't quite charge you for actual compute, right? It's kind of, they're still leaning on it. So think about API-based, we're going to break the bank. What people don't realize is, we do millions of API calls for any high transaction environment. A consumer can't afford that. What people don't realize is... I don't know how you're going to monetize. Even if you charge a cent a call, that is still going to be hundreds and thousands of dollars a day. And that's where, if you look at what you call low-code no-code motion? You see a plethora of companies being built on that. They're saying, "Hey, you don't have to write code. I'll give you authentication as a service. What that means is, Every single time you call my API to authenticate a user, I'm going to charge you." So just imagine how many times we authenticate on a single day. You're talking a few dozen times. And if I have to pay every single time I authenticate... >> Real friction in the marketplace, David. >> Yeah, and I tell you what. It's a big topic, right? And it's a topic that we haven't had to deal with at the Edge before, and we hear it probably daily really, complexity. The complexity's growing all the time. That means that we need to start to get insight, visibility. You know? I think a part of... Something that came out of the EU actually this week, stated, you know, there's a cyber attack every 11 seconds. That's fast, right? 2016, that was 40 seconds. So actually that speed I talked about earlier, everything Sri says that's coming down to the Edge, we want to embrace the Edge and that is the way we're going to move. But customers are mindful of the complexity that's involved in that. And that, you know, lens thought to how are we going to deal with those complexities. >> I was just going to ask you, how are you planning to deal with those complexities? You mentioned one ransomware attack every 11 seconds. That's down considerably from just a few years ago. Ransomware is a household word. It's no longer, "Are we going to get attacked?" It's when, it's to what extent, it's how much. So how is Ivanti helping customers deal with some of the complexities, and the changes in the security landscape? >> Yeah. Shall I start on that one first? Yeah, look, we want to give all our customers and perspective customers full visibility of their environment. You know, devices that are attached to the environment. Where are they? What are they doing? How often are we going to look for those devices? Not only when we find those devices. What applications are they running? Are those applications secure? How are we going to manage those applications moving forward? And overall, wrapping it round, what kind of service are we going to do? What processes are we going to put in place? To Sri's point, the low-code no-code angle. How do we build processes that protect our organization? But probably a point where I'll pass to Sri in a moment is how do we add a level of automation to that? How do we add a level of intelligence that doesn't always require a human to be fixing or remediating a problem? >> To Sri, you mentioned... You're right, the keynote, it took 45 minutes before it even mentioned security. And I suppose it's because they've historically, had this hardened stack. Everything's controlled and it's a safe environment. And now that's changing. So what would you add? >> You know, great point, right? If you look at telcos, they're used to a perimeter-based network. >> Yep. >> I mean, that's what we are. Boxed, we knew our perimeter. Today, our perimeter is extended to our home, everywhere work, right? >> Yeah- >> We don't have a definition of a perimeter. Your browser is the new perimeter. And a good example, segueing to that, what we have seen is horizontal-based security. What we haven't seen is verticalization, especially in mobile. We haven't seen vertical mobile security solutions, right? Yes, you hear a little bit about automobile, you hear a little bit about healthcare, but what we haven't seen is, what about food sector? What about the frontline in food? What about supply chain? What security are we really doing? And I'll give you a simple example. You brought up ransomware. Last night, Dole was attacked with ransomware. We have seen the beef producer colonial pipeline. Now, if we have seen agritech being hit, what does it mean? We are starting to hit humanity. If you can't really put food on the table, you're starting to really disrupt the supply chain, right? In a massive way. So you got to start thinking about that. Why is Dole related to mobility? Think about that. They don't carry service and computers. What they carry is mobile devices. that's where the supply chain works. And then that's where you have to start thinking about it. And the evolution of ransomware, rather than a single-trick pony, you see them using multiple vulnerabilities. And Pegasus was the best example. Spyware across all politicians, right? And CEOs. It is six or seven vulnerabilities put together that actually was constructed to do an attack. >> Yeah. How does AI kind of change this? Where does it fit in? The attackers are going to have AI, but we could use AI to defend. But attackers are always ahead, right? (chuckles) So what's your... Do you have a point of view on that? 'Cause everybody's crazy about ChatGPT, right? The banks have all banned it. Certain universities in the United States have banned it. Another one's forcing his students to learn how to use ChatGPT to prompt it. It's all over the place. You have a point of view on this? >> So definitely, Dave, it's a great point. First, we all have to have our own generative AI. I mean, I look at it as your digital assistant, right? So when you had calculators, you can't function without a calculator today. It's not harmful. It's not going to take you away from doing multiplication, right? So we'll still teach arithmetic in school. You'll still use your calculator. So to me, AI will become an integral part. That's one beautiful thing I've seen on the short floor. Every little thing there is a AI-based solution I've seen, right? So ChatGPT is well played from multiple perspective. I would rather up level it and say, generated AI is the way to go. So there are three things. There is human intense triaging, where humans keep doing easy work, minimal work. You can use ML and AI to do that. There is human designing that you need to do. That's when you need to use AI. >> But, I would say this, in the Enterprise, that the quality of the AI has to be better than what we've seen so far out of ChatGPT, even though I love ChatGPT, it's amazing. But what we've seen from being... It's got to be... Is it true that... Don't you think it has to be cleaner, more accurate? It can't make up stuff. If I'm going to be automating my network with AI. >> I'll answer that question. It comes down to three fundamentals. The reason ChatGPT is giving addresses, it's not trained on the latest data. So for any AI and ML method, you got to look at three things. It's your data, it's your domain expertise, who is training it, and your data model. In ChatGPT, it's older data, it's biased to the people that trained it, right? >> Mm-hmm. >> And then, the data model is it's going to spit out what it's trained on. That's a precursor of any GPT, right? It's pre-trained transformation. >> So if we narrow that, right? Train it better for the specific use case, that AI has huge potential. >> You flip that to what the Enterprise customers talk about to us is, insight is invaluable. >> Right. >> But then too much insight too quickly all the time means we go remediation crazy. So we haven't got enough humans to be fixing all the problems. Sri's point with the ChatGPT data, some of that data we are looking at there could be old. So we're trying to triage something that may still be an issue, but it might have been superseded by something else as well. So that's my overriding when I'm talking to customers and we talk ChatGPT, it's in the news all the time. It's very topical. >> It's fun. >> It is. I even said to my 13-year-old son yesterday, your homework's out a date. 'Cause I knew he was doing some summary stuff on ChatGPT. So a little wind up that's out of date just to make that emphasis around the model. And that's where we, with our Neurons platform Ivanti, that's what we want to give the customers all the time, which is the real-time snapshot. So they can make a priority or a decision based on what that information is telling them. >> And we've kind of learned, I think, over the last couple of years, that access to real-time data, real-time AI, is no longer nice to have. It's a massive competitive advantage for organizations, but it's going to enable the on-demand, everything that we expect in our consumer lives, in our business lives. This is going to be table stakes for organizations, I think, in every industry going forward. >> Yeah. >> But assumes 5G, right? Is going to actually happen and somebody's going to- >> Going to absolutely. >> Somebody's going to make some money off it at some point. When are they going to make money off of 5G, do you think? (all laughing) >> No. And then you asked a very good question, Dave. I want to answer that question. Will bad guys use AI? >> Yeah. Yeah. >> Offensive AI is a very big thing. We have to pay attention to it. It's got to create an asymmetric war. If you look at the president of the United States, he said, "If somebody's going to attack us on cyber, we are going to retaliate." For the first time, US is willing to launch a cyber war. What that really means is, we're going to use AI for offensive reasons as well. And we as citizens have to pay attention to that. And that's where I'm worried about, right? AI bias, whether it's data, or domain expertise, or algorithmic bias, is going to be a big thing. And offensive AI is something everybody have to pay attention to. >> To your point, Sri, earlier about critical infrastructure getting hacked, I had this conversation with Dr. Robert Gates several years ago, and I said, "Yeah, but don't we have the best offensive, you know, technology in cyber?" And he said, "Yeah, but we got the most to lose too." >> Yeah, 100%. >> We're the wealthiest nation of the United States. The wealthiest is. So you got to be careful. But to your point, the president of the United States saying, "We'll retaliate," right? Not necessarily start the war, but who started it? >> But that's the thing, right? Attribution is the hardest part. And then you talked about a very interesting thing, rich nations, right? There's emerging nations. There are nations left behind. One thing I've seen on the show floor today is, digital inequality. Digital poverty is a big thing. While we have this amazing technology, 90% of the world doesn't have access to this. >> Right. >> What we have done is we have created an inequality across, and especially in mobility and cyber, if this technology doesn't reach to the last mile, which is emerging nations, I think we are creating a crater back again and putting societies a few miles back. >> And at much greater risk. >> 100%, right? >> Yeah. >> Because those are the guys. In cyber, all you need is a laptop and a brain to attack. >> Yeah. Yeah. >> If I don't have it, that's where the civil war is going to start again. >> Yeah. What are some of the things in our last minute or so, guys, David, we'll start with you and then Sri go to you, that you're looking forward to at this MWC? The theme is velocity. We're talking about so much transformation and evolution in the telecom industry. What are you excited to hear and learn in the next couple of days? >> Just getting a complete picture. One is actually being out after the last couple of years, so you learn a lot. But just walking around and seeing, from my perspective, some vendor names that I haven't seen before, but seeing what they're doing and bringing to the market. But I think goes back to the point made earlier around APIs and integration. Everybody's talking about how can we kind of do this together in a way. So integrations, those smart things is what I'm kind of looking for as well, and how we plug into that as well. >> Excellent, and Sri? >> So for us, there is a lot to offer, right? So while I'm enjoying what I'm seeing here, I'm seeing at an opportunity. We have an amazing portfolio of what we can do. We are into mobile device management. We are the last (indistinct) company. When people find problems, somebody has to go remediators. We are the world's largest patch management company. And what I'm finding is, yes, all these people are embedding software, pumping it like nobody's business. As you find one ability, somebody has to go fix them, and we want to be the (indistinct) company. We had the last smile. And I find an amazing opportunity, not only we can do device management, but do mobile threat defense and give them a risk prioritization on what needs to be remediated, and manage all that in our ITSM. So I look at this as an amazing, amazing opportunity. >> Right. >> Which is exponential than what I've seen before. >> So last question then. Speaking of opportunities, Sri, for you, what are some of the things that customers can go to? Obviously, you guys talk to customers all the time. In terms of learning what Ivanti is going to enable them to do, to take advantage of these opportunities. Any webinars, any events coming up that we want people to know about? >> Absolutely, ivanti.com is the best place to go because we keep everything there. Of course, "theCUBE" interview. >> Of course. >> You should definitely watch that. (all laughing) No. So we have quite a few industry events we do. And especially there's a lot of learning. And we just raised the ransomware report that actually talks about ransomware from a global index perspective. So one thing what we have done is, rather than just looking at vulnerabilities, we showed them the weaknesses that led to the vulnerabilities, and how attackers are using them. And we even talked about DHS, how behind they are in disseminating the information and how it's actually being used by nation states. >> Wow. >> And we did cover mobility as a part of that as well. So there's a quite a bit we did in our report and it actually came out very well. >> I have to check that out. Ransomware is such a fascinating topic. Guys, thank you so much for joining Dave and me on the program today, sharing what's going on at Ivanti, the changes that you're seeing in mobile, and the opportunities that are there for your customers. We appreciate your time. >> Thank you >> Thank you. >> Yes. Thanks, guys. >> Thanks, guys. >> For our guests and for Dave Vellante, I'm Lisa Martin. You're watching "theCUBE" live from MWC23 in Barcelona. As you know, "theCUBE" is the leader in live tech coverage. Dave and I will be right back with our next guest. (gentle upbeat music)

>>Well, hello everybody at John Wallace here on the Cube, and glad to have you along here for day two of our coverage here at AWS Reinvent 22. We're up in the global startup program, which is part of AWS's Startup Showcase, and I've got Kevin Farley with me. He is the director of Strategic Alliances with Maria Day db. And Kevin, good to see you this morning. Good to see you, John. Thanks for joining us. Thank >>You. >>Appreciate it. Yeah. First off, tell us about Maria db. Sure. Obviously data's your thing. Yep. But to share that with some folks at home who might not be familiar with your offering. >>Yeah. So Maria DB's been around as a corporate entity for 10 plus years, and we have a massive customer base. You know, there's a billion downloads from Docker Hub, 75% of the Fortune 500. We have an enormous sea of really happy users. But what we realize is that all of these users are really thinking about what do we, what does it mean to transform it? What does cloud modernization mean? And how do we build a strategy on something we really love to drive it into the cloud and take it to the future. So what we launched about two years ago, two and a half years ago, is Skye. It's our database as a service. It leverages all the best elements, what we provide on the enterprise platform. It marries to the AWS cloud, and it really provides the best of both worlds for our >>Customers. So in your thought then, what, what problem is that solving? >>I think what you see in the overall database market is that many people have been using what we would call legacy technology. There's been lots of sort of stratification and mixes of different database solutions. All of them come with some promise, and all of 'em come with a lot of compromise. So I think what the market is really looking for is something that can take what they know and love, can bring it to the cloud and can survive the port drive the performance and scale. That completely changes the landscape, especially as you think about what modern data needs look like, right? What people did 10 years ago with the exponential scale of data no longer works. And what they need is something that not only can really deliver against their core business values and their core business deliverables, but gets 'em to the future. How do we drive something new? How do we innovate? How do we change the game? And I think what we built with AWS really delivers what we call cloud scale. It's taking something that is the best technology, and I as a V can build, marrying it to, you know, Kubernetes layer, marrying it to global availability, thinking about having true global high availability across all of your environments and really delivering that to customers through an integrated partnership. >>Could we see this coming? I mean, because you know data, right? I mean, yeah, we, we, everybody talked about the tsunami of growth, you know, >>Back 10 >>Sure. 11 years ago. But, but maybe the headlights didn't go far enough or, or, but, but you could see that there was going to be crunch time. >>There's no doubt. And I think that this has been a, there's, there's been these sort of pocket solutions, right? So if you think at the entire no sequel world, right? People said, oh, I need scale, I can get it, but what do I have to give up asset compliance? So I have to change the way I think about what data is and how I, I can govern it. So there's been these things that deliver on half the promise, but there's never been something that comes together and really drives what we deliver through CIQ is something called expand. So distributed SQL really tied to the SQL Query language, having that asset data. So having everything you need without the compromise built on the cloud allows you to scale out and allows you to think about, I can actually do exponential layers of, of data, data modeling, data querying, complete read, write, driving that forward. And I think it gives us a whole nother dynamic that we can deliver on in a way that hasn't been before. And I think that's kind of the holy grail of what people are looking for is how am I building modern applications and how do I have a database in the cloud that's really gonna support >>It? You know, you talk about distributed, you know, sequel and, and I mean, there's a little mystery behind it, isn't there? Or at least maybe not mystery. There's a little, I guess, confusion or, or just misunderstanding. I mean, I, how, nail that down a little bit. I >>Would say the best way to say it, honestly, this is the great thing, is it people believe it's too good to be true. And I think what we see over and over >>Again, you know, what they say about that. >>But this is the great part is, you know, you know, we've just had two taste studies recently with aws, with HIT labs and Certified power, both on expand, both proof in the pudding. They did the POCs, they're like, oh my God, this works. If you watch the keynote yesterday, you know, Adam had a slide that was, you know, as big as the entire room and it highlighted Samsung and they said, you know, we're doing 80,000 requests per second. So the, you know, the story there is that AWS is able as, as an entity with their scale and their breadth to handle that kind of workload. But guess what that is? That's MariaDB expand underneath there driving all of that utilization. So it's already there, it's already married, it's already in the cloud, and now we're taking it to a completely different level with a fully managed database solution. Right? >>How impressive is that? Right? I mean, you would think that somebody out there who, I mean that that volume, that kind of capacity is, is mind blowing. >>I mean, to your kind of previous point, it's like one of those things, do I see what's coming and it's here, right? You know, it's, is it actually ever gonna be possible? And now we're showing that it really is on a daily basis for some of the biggest brands in the world. We're also seeing companies moving off not only transitioning from, you know, MariaDB or myse, but all of the big licensed, you know, conversions as well. So you think about Oracle DBS Bank is one of our biggest customers, one of the largest Oracle conversions in the world onto MariaDB. And now thinking about what is the promise of connecting that to the cloud? How do you take things that you're currently doing, OnPrem delivering a hybrid model that also then starts to say, Hey, here's my path to cloud modernization. Skye gives me that bridge. And then you take it one layer farther and you think about multi-cloud, right? That's one of the things that's critical that ISVs can really only deliver in a meaningful way, is how can we have a solution for a customer that we can take to any availability zone. We can have performance, proximity, cost, proximity. We're always able to have that total data dexterity across any environment we need and we can build on that for the future. >>So if, if we're talking about cloud database and there's so many good things going forward here. You're talking about easy use and scalability and all that. But as with ever have you talked about this, there's some push and there's some pull. Yeah. So, so what's the, what's the other side that's still, you know, you that you think has to be >>Addressed? And I think that's a great question. So there's, we see that there's poll, right? We've seen these deals, this pipeline growth, this, there's great adoption. But what I think we're still not at the point of massive hockey stick adoption is that customers still don't fully understand the capabilities distributed SQL and the power they can actually deliver. So the more we drive case studies, the more we drive POCs, the more we prove the model, I think you're gonna see just a massive adoption scale. And I also think customers are tired of doing lots of different things in lots of different pockets. So neither one of the key elements of Sky SQL is we can do both transactional and analytical data out of the same database driven by the same proxy. So what, instead of having DBAs and developers try to figure out, okay, I'm gonna pull from this database here. >>Yeah. That there, it's, it's this big spaghetti wire concept that is super expensive and super time intensive. So the ability to write modern applications and pull data from both pockets and really be able to have that as a seamless entity and deliver that to customers is massive. I mean, another part of the keynote yesterday was a new deliverable, like kind of no etl. Adam talked about Aurora and Redshift and the massive complexity of what used to exist for getting data back and forth. You also have to pay for two different databases. It's super expensive. So I think the idea that you can take the real focus of AWS and US is customer value. How do you deliver that next thing that changes the game? Always utilizes AWS delivers on that promise, but then takes a net new technology that really starts to think about how do we bring things together? How do we make it more simple? How do we make it more powerful? And how do we deliver more customer value as we go forward? >>But you know, if, if I'm, I'm still an on-prim guy, just pretend I'm not saying I am. Just pretend I just for the sake of the discussion here, it's like I just can't let it go. Yeah. Right. I, I still, you know, there's control, there's the known versus the unknown. The uncertain. Yeah. So twist my arm just a little bit more and get me over the hum. >>Well, first of all, you don't have to, right? And there's gonna be some industries and some verticals that will always have elements of their business that will be OnPrem. Guess what? We make the best based in the world. It can be MariaDB, but there's those that then say, these, these elements of our business are gonna be far more effective moving to the cloud. So we give you Skye, there's a natural symbiotic bridge between everything we do and how we deliver it. Where you can be hybrid and it's great. You can adopt the cloud as your business needs grow. And you can have multi-cloud. This is that, that idea that you can, can have your cake and eat it too, right? You can literally have all these elements of your business met without these big pressure to say, you gotta throw that away. You gotta move to this. It's really, how do you kind of gracefully adopt the cloud in a way that makes sense for your business? Where are you trying to drive your business? Is it time to value, right? Is it governance? Is it is there's different elements of what matters the most to individual businesses. You know, we wanna address those and we can address >>Those. So you're saying you don't have to dive >>In, you don't have to dive >>In. You, you can, you can go ankle deep, knee deep, whatever you wanna >>Do. Absolutely. And you know, some of the largest MariaDB users still have massive, massive on-prem implementations. And that's okay. But there's elements that are starting to fall behind. There's cost savings, there's things that they need to do in the cloud that they can't do. OnPrem. And that's where expand Skye really says, okay, here is your platform. Grow as you want to, migrate as you want to. And we're there every step along the way. We, we also provide a whole Sky DBA team. Some guys just say, I wanna get outta the database world at all. This is, this is expensive, it's costly and it's difficult to be an expert. So you can bring in our DBA team and they'll man and run, they'll, they'll run your entire environment. They'll optimize it, you know, they'll troubleshoot it, they'll bug fix, they'll do everything for you. So you can just say, I just wanna focus on building phenomenal applications for my customers. And the database game as we knew it is not something that I know I want to invest in anymore. Right. I wanna make that transition >>That makes that really, yeah. You know, I mean really attractive to a lot of people because you are, you talk about a lot of headache there. Yeah. So let's talk about AWS before Sure. I let you go just about that relationship. Okay. You've talked about the platform that it provides you and, and obviously the benefits, but just talk about how you've worked with AWS over the years Yep. And, and how you see that relationship allowing you to expand your services, no pun intended. >>For sure. So, I mean, I would start with the way we even contemplated architecture. You know, we worked with the satisfactory team. We made sure that the things that we built were optimized in their environment. You know, I think it was a lot of collaboration on how does this combined entity really make the most value for our customers? How does it make the most sense for our developers as we build it out? Then we work in the, in the global startup team. So the strategic element of who we are, not all startups are created equal, right? We have, right, we have 75% of the Fortune 100, we've got over a billion downloads. So, you know, we come in with promise. And the reason this partnership is so valuable and the reason there's so much investment going forward is cuz what really, what do the cloud guys care about? >>The very, very most, they want all of these mission critical, big workloads that are on prem to land in their cloud. What do we have a massive, massive TAM sitting out there, these customers that could go to aws. So we both see, like if we can deliver incredible value to that customer base, these big workloads will end up in aws. They'll use other AWS services. And as we scale and grow, you know, we have that platform that's already built for it. So I think that when you go back to like the tenants, the core principles of aws, the one that always stands out, the one that we always kind of lean back on is, are we delivering customer value? Is this the best thing for the customer? Because we do have some competition just like many other, other partners do, right? So there is Aurora and there is rds and there is times when that's a great service for a customer. But when people are really thinking about where do I need my database to go? Where do I really need to be set for the future growth? Where am I gonna get the kind of ROI I need going forward? That's where you can go, Hey, sky sql, expand distributed sql. This is the best game in town. It's built on aws and collectively, you know, we're gonna present that to a customer. I'm >>Sold. Done. >>I love it. Right? >>Maria db, check 'em out, they're on the show floor. Great traffic. I know at at the, at the booth. They're here at AWS Reinvent. So check 'em out. Maria db. Thanks >>Kevin. Hey, thanks John. Appreciate your >>Time. Appreciate Great. That was great. Right back with more, you're watching the cube, the leader in high tech coverage.

>>When Oracle acquired my SQL via the Sun acquisition, nobody really thought the company would put much effort into the platform preferring to focus all the wood behind its leading Oracle database, Arrow pun intended. But two years ago, Oracle surprised many folks by announcing my SQL Heatwave a new database as a service with a massively parallel hybrid Columbia in Mary Mary architecture that brings together transactional and analytic data in a single platform. Welcome to our latest database, power panel on the cube. My name is Dave Ante, and today we're gonna discuss Oracle's MySQL Heat Wave with a who's who of cloud database industry analysts. Holgar Mueller is with Constellation Research. Mark Stammer is the Dragon Slayer and Wikibon contributor. And Ron Westfall is with Fu Chim Research. Gentlemen, welcome back to the Cube. Always a pleasure to have you on. Thanks for having us. Great to be here. >>So we've had a number of of deep dive interviews on the Cube with Nip and Aggarwal. You guys know him? He's a senior vice president of MySQL, Heatwave Development at Oracle. I think you just saw him at Oracle Cloud World and he's come on to describe this is gonna, I'll call it a shock and awe feature additions to to heatwave. You know, the company's clearly putting r and d into the platform and I think at at cloud world we saw like the fifth major release since 2020 when they first announced MySQL heat wave. So just listing a few, they, they got, they taken, brought in analytics machine learning, they got autopilot for machine learning, which is automation onto the basic o l TP functionality of the database. And it's been interesting to watch Oracle's converge database strategy. We've contrasted that amongst ourselves. Love to get your thoughts on Amazon's get the right tool for the right job approach. >>Are they gonna have to change that? You know, Amazon's got the specialized databases, it's just, you know, the both companies are doing well. It just shows there are a lot of ways to, to skin a cat cuz you see some traction in the market in, in both approaches. So today we're gonna focus on the latest heat wave announcements and we're gonna talk about multi-cloud with a native MySQL heat wave implementation, which is available on aws MySQL heat wave for Azure via the Oracle Microsoft interconnect. This kind of cool hybrid action that they got going. Sometimes we call it super cloud. And then we're gonna dive into my SQL Heatwave Lake house, which allows users to process and query data across MyQ databases as heatwave databases, as well as object stores. So, and then we've got, heatwave has been announced on AWS and, and, and Azure, they're available now and Lake House I believe is in beta and I think it's coming out the second half of next year. So again, all of our guests are fresh off of Oracle Cloud world in Las Vegas. So they got the latest scoop. Guys, I'm done talking. Let's get into it. Mark, maybe you could start us off, what's your opinion of my SQL Heatwaves competitive position? When you think about what AWS is doing, you know, Google is, you know, we heard Google Cloud next recently, we heard about all their data innovations. You got, obviously Azure's got a big portfolio, snowflakes doing well in the market. What's your take? >>Well, first let's look at it from the point of view that AWS is the market leader in cloud and cloud services. They own somewhere between 30 to 50% depending on who you read of the market. And then you have Azure as number two and after that it falls off. There's gcp, Google Cloud platform, which is further way down the list and then Oracle and IBM and Alibaba. So when you look at AWS and you and Azure saying, hey, these are the market leaders in the cloud, then you start looking at it and saying, if I am going to provide a service that competes with the service they have, if I can make it available in their cloud, it means that I can be more competitive. And if I'm compelling and compelling means at least twice the performance or functionality or both at half the price, I should be able to gain market share. >>And that's what Oracle's done. They've taken a superior product in my SQL heat wave, which is faster, lower cost does more for a lot less at the end of the day and they make it available to the users of those clouds. You avoid this little thing called egress fees, you avoid the issue of having to migrate from one cloud to another and suddenly you have a very compelling offer. So I look at what Oracle's doing with MyQ and it feels like, I'm gonna use a word term, a flanking maneuver to their competition. They're offering a better service on their platforms. >>All right, so thank you for that. Holger, we've seen this sort of cadence, I sort of referenced it up front a little bit and they sat on MySQL for a decade, then all of a sudden we see this rush of announcements. Why did it take so long? And and more importantly is Oracle, are they developing the right features that cloud database customers are looking for in your view? >>Yeah, great question, but first of all, in your interview you said it's the edit analytics, right? Analytics is kind of like a marketing buzzword. Reports can be analytics, right? The interesting thing, which they did, the first thing they, they, they crossed the chasm between OTP and all up, right? In the same database, right? So major engineering feed very much what customers want and it's all about creating Bellevue for customers, which, which I think is the part why they go into the multi-cloud and why they add these capabilities. And they certainly with the AI capabilities, it's kind of like getting it into an autonomous field, self-driving field now with the lake cost capabilities and meeting customers where they are, like Mark has talked about the e risk costs in the cloud. So that that's a significant advantage, creating value for customers and that's what at the end of the day matters. >>And I believe strongly that long term it's gonna be ones who create better value for customers who will get more of their money From that perspective, why then take them so long? I think it's a great question. I think largely he mentioned the gentleman Nial, it's largely to who leads a product. I used to build products too, so maybe I'm a little fooling myself here, but that made the difference in my view, right? So since he's been charged, he's been building things faster than the rest of the competition, than my SQL space, which in hindsight we thought was a hot and smoking innovation phase. It kind of like was a little self complacent when it comes to the traditional borders of where, where people think, where things are separated between OTP and ola or as an example of adjacent support, right? Structured documents, whereas unstructured documents or databases and all of that has been collapsed and brought together for building a more powerful database for customers. >>So I mean it's certainly, you know, when, when Oracle talks about the competitors, you know, the competitors are in the, I always say they're, if the Oracle talks about you and knows you're doing well, so they talk a lot about aws, talk a little bit about Snowflake, you know, sort of Google, they have partnerships with Azure, but, but in, so I'm presuming that the response in MySQL heatwave was really in, in response to what they were seeing from those big competitors. But then you had Maria DB coming out, you know, the day that that Oracle acquired Sun and, and launching and going after the MySQL base. So it's, I'm, I'm interested and we'll talk about this later and what you guys think AWS and Google and Azure and Snowflake and how they're gonna respond. But, but before I do that, Ron, I want to ask you, you, you, you can get, you know, pretty technical and you've probably seen the benchmarks. >>I know you have Oracle makes a big deal out of it, publishes its benchmarks, makes some transparent on on GI GitHub. Larry Ellison talked about this in his keynote at Cloud World. What are the benchmarks show in general? I mean, when you, when you're new to the market, you gotta have a story like Mark was saying, you gotta be two x you know, the performance at half the cost or you better be or you're not gonna get any market share. So, and, and you know, oftentimes companies don't publish market benchmarks when they're leading. They do it when they, they need to gain share. So what do you make of the benchmarks? Have their, any results that were surprising to you? Have, you know, they been challenged by the competitors. Is it just a bunch of kind of desperate bench marketing to make some noise in the market or you know, are they real? What's your view? >>Well, from my perspective, I think they have the validity. And to your point, I believe that when it comes to competitor responses, that has not really happened. Nobody has like pulled down the information that's on GitHub and said, Oh, here are our price performance results. And they counter oracles. In fact, I think part of the reason why that hasn't happened is that there's the risk if Oracle's coming out and saying, Hey, we can deliver 17 times better query performance using our capabilities versus say, Snowflake when it comes to, you know, the Lakehouse platform and Snowflake turns around and says it's actually only 15 times better during performance, that's not exactly an effective maneuver. And so I think this is really to oracle's credit and I think it's refreshing because these differentiators are significant. We're not talking, you know, like 1.2% differences. We're talking 17 fold differences, we're talking six fold differences depending on, you know, where the spotlight is being shined and so forth. >>And so I think this is actually something that is actually too good to believe initially at first blush. If I'm a cloud database decision maker, I really have to prioritize this. I really would know, pay a lot more attention to this. And that's why I posed the question to Oracle and others like, okay, if these differentiators are so significant, why isn't the needle moving a bit more? And it's for, you know, some of the usual reasons. One is really deep discounting coming from, you know, the other players that's really kind of, you know, marketing 1 0 1, this is something you need to do when there's a real competitive threat to keep, you know, a customer in your own customer base. Plus there is the usual fear and uncertainty about moving from one platform to another. But I think, you know, the traction, the momentum is, is shifting an Oracle's favor. I think we saw that in the Q1 efforts, for example, where Oracle cloud grew 44% and that it generated, you know, 4.8 billion and revenue if I recall correctly. And so, so all these are demonstrating that's Oracle is making, I think many of the right moves, publishing these figures for anybody to look at from their own perspective is something that is, I think, good for the market and I think it's just gonna continue to pay dividends for Oracle down the horizon as you know, competition intens plots. So if I were in, >>Dave, can I, Dave, can I interject something and, and what Ron just said there? Yeah, please go ahead. A couple things here, one discounting, which is a common practice when you have a real threat, as Ron pointed out, isn't going to help much in this situation simply because you can't discount to the point where you improve your performance and the performance is a huge differentiator. You may be able to get your price down, but the problem that most of them have is they don't have an integrated product service. They don't have an integrated O L T P O L A P M L N data lake. Even if you cut out two of them, they don't have any of them integrated. They have multiple services that are required separate integration and that can't be overcome with discounting. And the, they, you have to pay for each one of these. And oh, by the way, as you grow, the discounts go away. So that's a, it's a minor important detail. >>So, so that's a TCO question mark, right? And I know you look at this a lot, if I had that kind of price performance advantage, I would be pounding tco, especially if I need two separate databases to do the job. That one can do, that's gonna be, the TCO numbers are gonna be off the chart or maybe down the chart, which you want. Have you looked at this and how does it compare with, you know, the big cloud guys, for example, >>I've looked at it in depth, in fact, I'm working on another TCO on this arena, but you can find it on Wiki bod in which I compared TCO for MySEQ Heat wave versus Aurora plus Redshift plus ML plus Blue. I've compared it against gcps services, Azure services, Snowflake with other services. And there's just no comparison. The, the TCO differences are huge. More importantly, thefor, the, the TCO per performance is huge. We're talking in some cases multiple orders of magnitude, but at least an order of magnitude difference. So discounting isn't gonna help you much at the end of the day, it's only going to lower your cost a little, but it doesn't improve the automation, it doesn't improve the performance, it doesn't improve the time to insight, it doesn't improve all those things that you want out of a database or multiple databases because you >>Can't discount yourself to a higher value proposition. >>So what about, I wonder ho if you could chime in on the developer angle. You, you followed that, that market. How do these innovations from heatwave, I think you used the term developer velocity. I've heard you used that before. Yeah, I mean, look, Oracle owns Java, okay, so it, it's, you know, most popular, you know, programming language in the world, blah, blah blah. But it does it have the, the minds and hearts of, of developers and does, where does heatwave fit into that equation? >>I think heatwave is gaining quickly mindshare on the developer side, right? It's not the traditional no sequel database which grew up, there's a traditional mistrust of oracles to developers to what was happening to open source when gets acquired. Like in the case of Oracle versus Java and where my sql, right? And, but we know it's not a good competitive strategy to, to bank on Oracle screwing up because it hasn't worked not on Java known my sequel, right? And for developers, it's, once you get to know a technology product and you can do more, it becomes kind of like a Swiss army knife and you can build more use case, you can build more powerful applications. That's super, super important because you don't have to get certified in multiple databases. You, you are fast at getting things done, you achieve fire, develop velocity, and the managers are happy because they don't have to license more things, send you to more trainings, have more risk of something not being delivered, right? >>So it's really the, we see the suite where this best of breed play happening here, which in general was happening before already with Oracle's flagship database. Whereas those Amazon as an example, right? And now the interesting thing is every step away Oracle was always a one database company that can be only one and they're now generally talking about heat web and that two database company with different market spaces, but same value proposition of integrating more things very, very quickly to have a universal database that I call, they call the converge database for all the needs of an enterprise to run certain application use cases. And that's what's attractive to developers. >>It's, it's ironic isn't it? I mean I, you know, the rumor was the TK Thomas Curian left Oracle cuz he wanted to put Oracle database on other clouds and other places. And maybe that was the rift. Maybe there was, I'm sure there was other things, but, but Oracle clearly is now trying to expand its Tam Ron with, with heatwave into aws, into Azure. How do you think Oracle's gonna do, you were at a cloud world, what was the sentiment from customers and the independent analyst? Is this just Oracle trying to screw with the competition, create a little diversion? Or is this, you know, serious business for Oracle? What do you think? >>No, I think it has lakes. I think it's definitely, again, attriting to Oracle's overall ability to differentiate not only my SQL heat wave, but its overall portfolio. And I think the fact that they do have the alliance with the Azure in place, that this is definitely demonstrating their commitment to meeting the multi-cloud needs of its customers as well as what we pointed to in terms of the fact that they're now offering, you know, MySQL capabilities within AWS natively and that it can now perform AWS's own offering. And I think this is all demonstrating that Oracle is, you know, not letting up, they're not resting on its laurels. That's clearly we are living in a multi-cloud world, so why not just make it more easy for customers to be able to use cloud databases according to their own specific, specific needs. And I think, you know, to holder's point, I think that definitely lines with being able to bring on more application developers to leverage these capabilities. >>I think one important announcement that's related to all this was the JSON relational duality capabilities where now it's a lot easier for application developers to use a language that they're very familiar with a JS O and not have to worry about going into relational databases to store their J S O N application coding. So this is, I think an example of the innovation that's enhancing the overall Oracle portfolio and certainly all the work with machine learning is definitely paying dividends as well. And as a result, I see Oracle continue to make these inroads that we pointed to. But I agree with Mark, you know, the short term discounting is just a stall tag. This is not denying the fact that Oracle is being able to not only deliver price performance differentiators that are dramatic, but also meeting a wide range of needs for customers out there that aren't just limited device performance consideration. >>Being able to support multi-cloud according to customer needs. Being able to reach out to the application developer community and address a very specific challenge that has plagued them for many years now. So bring it all together. Yeah, I see this as just enabling Oracles who ring true with customers. That the customers that were there were basically all of them, even though not all of them are going to be saying the same things, they're all basically saying positive feedback. And likewise, I think the analyst community is seeing this. It's always refreshing to be able to talk to customers directly and at Oracle cloud there was a litany of them and so this is just a difference maker as well as being able to talk to strategic partners. The nvidia, I think partnerships also testament to Oracle's ongoing ability to, you know, make the ecosystem more user friendly for the customers out there. >>Yeah, it's interesting when you get these all in one tools, you know, the Swiss Army knife, you expect that it's not able to be best of breed. That's the kind of surprising thing that I'm hearing about, about heatwave. I want to, I want to talk about Lake House because when I think of Lake House, I think data bricks, and to my knowledge data bricks hasn't been in the sites of Oracle yet. Maybe they're next, but, but Oracle claims that MySQL, heatwave, Lakehouse is a breakthrough in terms of capacity and performance. Mark, what are your thoughts on that? Can you double click on, on Lakehouse Oracle's claims for things like query performance and data loading? What does it mean for the market? Is Oracle really leading in, in the lake house competitive landscape? What are your thoughts? >>Well, but name in the game is what are the problems you're solving for the customer? More importantly, are those problems urgent or important? If they're urgent, customers wanna solve 'em. Now if they're important, they might get around to them. So you look at what they're doing with Lake House or previous to that machine learning or previous to that automation or previous to that O L A with O ltp and they're merging all this capability together. If you look at Snowflake or data bricks, they're tacking one problem. You look at MyQ heat wave, they're tacking multiple problems. So when you say, yeah, their queries are much better against the lake house in combination with other analytics in combination with O ltp and the fact that there are no ETLs. So you're getting all this done in real time. So it's, it's doing the query cross, cross everything in real time. >>You're solving multiple user and developer problems, you're increasing their ability to get insight faster, you're having shorter response times. So yeah, they really are solving urgent problems for customers. And by putting it where the customer lives, this is the brilliance of actually being multicloud. And I know I'm backing up here a second, but by making it work in AWS and Azure where people already live, where they already have applications, what they're saying is, we're bringing it to you. You don't have to come to us to get these, these benefits, this value overall, I think it's a brilliant strategy. I give Nip and Argo wallet a huge, huge kudos for what he's doing there. So yes, what they're doing with the lake house is going to put notice on data bricks and Snowflake and everyone else for that matter. Well >>Those are guys that whole ago you, you and I have talked about this. Those are, those are the guys that are doing sort of the best of breed. You know, they're really focused and they, you know, tend to do well at least out of the gate. Now you got Oracle's converged philosophy, obviously with Oracle database. We've seen that now it's kicking in gear with, with heatwave, you know, this whole thing of sweets versus best of breed. I mean the long term, you know, customers tend to migrate towards suite, but the new shiny toy tends to get the growth. How do you think this is gonna play out in cloud database? >>Well, it's the forever never ending story, right? And in software right suite, whereas best of breed and so far in the long run suites have always won, right? So, and sometimes they struggle again because the inherent problem of sweets is you build something larger, it has more complexity and that means your cycles to get everything working together to integrate the test that roll it out, certify whatever it is, takes you longer, right? And that's not the case. It's a fascinating part of what the effort around my SQL heat wave is that the team is out executing the previous best of breed data, bringing us something together. Now if they can maintain that pace, that's something to to, to be seen. But it, the strategy, like what Mark was saying, bring the software to the data is of course interesting and unique and totally an Oracle issue in the past, right? >>Yeah. But it had to be in your database on oci. And but at, that's an interesting part. The interesting thing on the Lake health side is, right, there's three key benefits of a lakehouse. The first one is better reporting analytics, bring more rich information together, like make the, the, the case for silicon angle, right? We want to see engagements for this video, we want to know what's happening. That's a mixed transactional video media use case, right? Typical Lakehouse use case. The next one is to build more rich applications, transactional applications which have video and these elements in there, which are the engaging one. And the third one, and that's where I'm a little critical and concerned, is it's really the base platform for artificial intelligence, right? To run deep learning to run things automatically because they have all the data in one place can create in one way. >>And that's where Oracle, I know that Ron talked about Invidia for a moment, but that's where Oracle doesn't have the strongest best story. Nonetheless, the two other main use cases of the lake house are very strong, very well only concern is four 50 terabyte sounds long. It's an arbitrary limitation. Yeah, sounds as big. So for the start, and it's the first word, they can make that bigger. You don't want your lake house to be limited and the terabyte sizes or any even petabyte size because you want to have the certainty. I can put everything in there that I think it might be relevant without knowing what questions to ask and query those questions. >>Yeah. And you know, in the early days of no schema on right, it just became a mess. But now technology has evolved to allow us to actually get more value out of that data. Data lake. Data swamp is, you know, not much more, more, more, more logical. But, and I want to get in, in a moment, I want to come back to how you think the competitors are gonna respond. Are they gonna have to sort of do a more of a converged approach? AWS in particular? But before I do, Ron, I want to ask you a question about autopilot because I heard Larry Ellison's keynote and he was talking about how, you know, most security issues are human errors with autonomy and autonomous database and things like autopilot. We take care of that. It's like autonomous vehicles, they're gonna be safer. And I went, well maybe, maybe someday. So Oracle really tries to emphasize this, that every time you see an announcement from Oracle, they talk about new, you know, autonomous capabilities. It, how legit is it? Do people care? What about, you know, what's new for heatwave Lakehouse? How much of a differentiator, Ron, do you really think autopilot is in this cloud database space? >>Yeah, I think it will definitely enhance the overall proposition. I don't think people are gonna buy, you know, lake house exclusively cause of autopilot capabilities, but when they look at the overall picture, I think it will be an added capability bonus to Oracle's benefit. And yeah, I think it's kind of one of these age old questions, how much do you automate and what is the bounce to strike? And I think we all understand with the automatic car, autonomous car analogy that there are limitations to being able to use that. However, I think it's a tool that basically every organization out there needs to at least have or at least evaluate because it goes to the point of it helps with ease of use, it helps make automation more balanced in terms of, you know, being able to test, all right, let's automate this process and see if it works well, then we can go on and switch on on autopilot for other processes. >>And then, you know, that allows, for example, the specialists to spend more time on business use cases versus, you know, manual maintenance of, of the cloud database and so forth. So I think that actually is a, a legitimate value proposition. I think it's just gonna be a case by case basis. Some organizations are gonna be more aggressive with putting automation throughout their processes throughout their organization. Others are gonna be more cautious. But it's gonna be, again, something that will help the overall Oracle proposition. And something that I think will be used with caution by many organizations, but other organizations are gonna like, hey, great, this is something that is really answering a real problem. And that is just easing the use of these databases, but also being able to better handle the automation capabilities and benefits that come with it without having, you know, a major screwup happened and the process of transitioning to more automated capabilities. >>Now, I didn't attend cloud world, it's just too many red eyes, you know, recently, so I passed. But one of the things I like to do at those events is talk to customers, you know, in the spirit of the truth, you know, they, you know, you'd have the hallway, you know, track and to talk to customers and they say, Hey, you know, here's the good, the bad and the ugly. So did you guys, did you talk to any customers my SQL Heatwave customers at, at cloud world? And and what did you learn? I don't know, Mark, did you, did you have any luck and, and having some, some private conversations? >>Yeah, I had quite a few private conversations. The one thing before I get to that, I want disagree with one point Ron made, I do believe there are customers out there buying the heat wave service, the MySEQ heat wave server service because of autopilot. Because autopilot is really revolutionary in many ways in the sense for the MySEQ developer in that it, it auto provisions, it auto parallel loads, IT auto data places it auto shape predictions. It can tell you what machine learning models are going to tell you, gonna give you your best results. And, and candidly, I've yet to meet a DBA who didn't wanna give up pedantic tasks that are pain in the kahoo, which they'd rather not do and if it's long as it was done right for them. So yes, I do think people are buying it because of autopilot and that's based on some of the conversations I had with customers at Oracle Cloud World. >>In fact, it was like, yeah, that's great, yeah, we get fantastic performance, but this really makes my life easier and I've yet to meet a DBA who didn't want to make their life easier. And it does. So yeah, I've talked to a few of them. They were excited. I asked them if they ran into any bugs, were there any difficulties in moving to it? And the answer was no. In both cases, it's interesting to note, my sequel is the most popular database on the planet. Well, some will argue that it's neck and neck with SQL Server, but if you add in Mariah DB and ProCon db, which are forks of MySQL, then yeah, by far and away it's the most popular. And as a result of that, everybody for the most part has typically a my sequel database somewhere in their organization. So this is a brilliant situation for anybody going after MyQ, but especially for heat wave. And the customers I talk to love it. I didn't find anybody complaining about it. And >>What about the migration? We talked about TCO earlier. Did your t does your TCO analysis include the migration cost or do you kind of conveniently leave that out or what? >>Well, when you look at migration costs, there are different kinds of migration costs. By the way, the worst job in the data center is the data migration manager. Forget it, no other job is as bad as that one. You get no attaboys for doing it. Right? And then when you screw up, oh boy. So in real terms, anything that can limit data migration is a good thing. And when you look at Data Lake, that limits data migration. So if you're already a MySEQ user, this is a pure MySQL as far as you're concerned. It's just a, a simple transition from one to the other. You may wanna make sure nothing broke and every you, all your tables are correct and your schema's, okay, but it's all the same. So it's a simple migration. So it's pretty much a non-event, right? When you migrate data from an O LTP to an O L A P, that's an ETL and that's gonna take time. >>But you don't have to do that with my SQL heat wave. So that's gone when you start talking about machine learning, again, you may have an etl, you may not, depending on the circumstances, but again, with my SQL heat wave, you don't, and you don't have duplicate storage, you don't have to copy it from one storage container to another to be able to be used in a different database, which by the way, ultimately adds much more cost than just the other service. So yeah, I looked at the migration and again, the users I talked to said it was a non-event. It was literally moving from one physical machine to another. If they had a new version of MySEQ running on something else and just wanted to migrate it over or just hook it up or just connect it to the data, it worked just fine. >>Okay, so every day it sounds like you guys feel, and we've certainly heard this, my colleague David Foyer, the semi-retired David Foyer was always very high on heatwave. So I think you knows got some real legitimacy here coming from a standing start, but I wanna talk about the competition, how they're likely to respond. I mean, if your AWS and you got heatwave is now in your cloud, so there's some good aspects of that. The database guys might not like that, but the infrastructure guys probably love it. Hey, more ways to sell, you know, EC two and graviton, but you're gonna, the database guys in AWS are gonna respond. They're gonna say, Hey, we got Redshift, we got aqua. What's your thoughts on, on not only how that's gonna resonate with customers, but I'm interested in what you guys think will a, I never say never about aws, you know, and are they gonna try to build, in your view a converged Oola and o LTP database? You know, Snowflake is taking an ecosystem approach. They've added in transactional capabilities to the portfolio so they're not standing still. What do you guys see in the competitive landscape in that regard going forward? Maybe Holger, you could start us off and anybody else who wants to can chime in, >>Happy to, you mentioned Snowflake last, we'll start there. I think Snowflake is imitating that strategy, right? That building out original data warehouse and the clouds tasking project to really proposition to have other data available there because AI is relevant for everybody. Ultimately people keep data in the cloud for ultimately running ai. So you see the same suite kind of like level strategy, it's gonna be a little harder because of the original positioning. How much would people know that you're doing other stuff? And I just, as a former developer manager of developers, I just don't see the speed at the moment happening at Snowflake to become really competitive to Oracle. On the flip side, putting my Oracle hat on for a moment back to you, Mark and Iran, right? What could Oracle still add? Because the, the big big things, right? The traditional chasms in the database world, they have built everything, right? >>So I, I really scratched my hat and gave Nipon a hard time at Cloud world say like, what could you be building? Destiny was very conservative. Let's get the Lakehouse thing done, it's gonna spring next year, right? And the AWS is really hard because AWS value proposition is these small innovation teams, right? That they build two pizza teams, which can be fit by two pizzas, not large teams, right? And you need suites to large teams to build these suites with lots of functionalities to make sure they work together. They're consistent, they have the same UX on the administration side, they can consume the same way, they have the same API registry, can't even stop going where the synergy comes to play over suite. So, so it's gonna be really, really hard for them to change that. But AWS super pragmatic. They're always by themselves that they'll listen to customers if they learn from customers suite as a proposition. I would not be surprised if AWS trying to bring things closer together, being morely together. >>Yeah. Well how about, can we talk about multicloud if, if, again, Oracle is very on on Oracle as you said before, but let's look forward, you know, half a year or a year. What do you think about Oracle's moves in, in multicloud in terms of what kind of penetration they're gonna have in the marketplace? You saw a lot of presentations at at cloud world, you know, we've looked pretty closely at the, the Microsoft Azure deal. I think that's really interesting. I've, I've called it a little bit of early days of a super cloud. What impact do you think this is gonna have on, on the marketplace? But, but both. And think about it within Oracle's customer base, I have no doubt they'll do great there. But what about beyond its existing install base? What do you guys think? >>Ryan, do you wanna jump on that? Go ahead. Go ahead Ryan. No, no, no, >>That's an excellent point. I think it aligns with what we've been talking about in terms of Lakehouse. I think Lake House will enable Oracle to pull more customers, more bicycle customers onto the Oracle platforms. And I think we're seeing all the signs pointing toward Oracle being able to make more inroads into the overall market. And that includes garnishing customers from the leaders in, in other words, because they are, you know, coming in as a innovator, a an alternative to, you know, the AWS proposition, the Google cloud proposition that they have less to lose and there's a result they can really drive the multi-cloud messaging to resonate with not only their existing customers, but also to be able to, to that question, Dave's posing actually garnish customers onto their platform. And, and that includes naturally my sequel but also OCI and so forth. So that's how I'm seeing this playing out. I think, you know, again, Oracle's reporting is indicating that, and I think what we saw, Oracle Cloud world is definitely validating the idea that Oracle can make more waves in the overall market in this regard. >>You know, I, I've floated this idea of Super cloud, it's kind of tongue in cheek, but, but there, I think there is some merit to it in terms of building on top of hyperscale infrastructure and abstracting some of the, that complexity. And one of the things that I'm most interested in is industry clouds and an Oracle acquisition of Cerner. I was struck by Larry Ellison's keynote, it was like, I don't know, an hour and a half and an hour and 15 minutes was focused on healthcare transformation. Well, >>So vertical, >>Right? And so, yeah, so you got Oracle's, you know, got some industry chops and you, and then you think about what they're building with, with not only oci, but then you got, you know, MyQ, you can now run in dedicated regions. You got ADB on on Exadata cloud to customer, you can put that OnPrem in in your data center and you look at what the other hyperscalers are, are doing. I I say other hyperscalers, I've always said Oracle's not really a hyperscaler, but they got a cloud so they're in the game. But you can't get, you know, big query OnPrem, you look at outposts, it's very limited in terms of, you know, the database support and again, that that will will evolve. But now you got Oracle's got, they announced Alloy, we can white label their cloud. So I'm interested in what you guys think about these moves, especially the industry cloud. We see, you know, Walmart is doing sort of their own cloud. You got Goldman Sachs doing a cloud. Do you, you guys, what do you think about that and what role does Oracle play? Any thoughts? >>Yeah, let me lemme jump on that for a moment. Now, especially with the MyQ, by making that available in multiple clouds, what they're doing is this follows the philosophy they've had the past with doing cloud, a customer taking the application and the data and putting it where the customer lives. If it's on premise, it's on premise. If it's in the cloud, it's in the cloud. By making the mice equal heat wave, essentially a plug compatible with any other mice equal as far as your, your database is concern and then giving you that integration with O L A P and ML and Data Lake and everything else, then what you've got is a compelling offering. You're making it easier for the customer to use. So I look the difference between MyQ and the Oracle database, MyQ is going to capture market more market share for them. >>You're not gonna find a lot of new users for the Oracle debate database. Yeah, there are always gonna be new users, don't get me wrong, but it's not gonna be a huge growth. Whereas my SQL heatwave is probably gonna be a major growth engine for Oracle going forward. Not just in their own cloud, but in AWS and in Azure and on premise over time that eventually it'll get there. It's not there now, but it will, they're doing the right thing on that basis. They're taking the services and when you talk about multicloud and making them available where the customer wants them, not forcing them to go where you want them, if that makes sense. And as far as where they're going in the future, I think they're gonna take a page outta what they've done with the Oracle database. They'll add things like JSON and XML and time series and spatial over time they'll make it a, a complete converged database like they did with the Oracle database. The difference being Oracle database will scale bigger and will have more transactions and be somewhat faster. And my SQL will be, for anyone who's not on the Oracle database, they're, they're not stupid, that's for sure. >>They've done Jason already. Right. But I give you that they could add graph and time series, right. Since eat with, Right, Right. Yeah, that's something absolutely right. That's, that's >>A sort of a logical move, right? >>Right. But that's, that's some kid ourselves, right? I mean has worked in Oracle's favor, right? 10 x 20 x, the amount of r and d, which is in the MyQ space, has been poured at trying to snatch workloads away from Oracle by starting with IBM 30 years ago, 20 years ago, Microsoft and, and, and, and didn't work, right? Database applications are extremely sticky when they run, you don't want to touch SIM and grow them, right? So that doesn't mean that heat phase is not an attractive offering, but it will be net new things, right? And what works in my SQL heat wave heat phases favor a little bit is it's not the massive enterprise applications which have like we the nails like, like you might be only running 30% or Oracle, but the connections and the interfaces into that is, is like 70, 80% of your enterprise. >>You take it out and it's like the spaghetti ball where you say, ah, no I really don't, don't want to do all that. Right? You don't, don't have that massive part with the equals heat phase sequel kind of like database which are more smaller tactical in comparison, but still I, I don't see them taking so much share. They will be growing because of a attractive value proposition quickly on the, the multi-cloud, right? I think it's not really multi-cloud. If you give people the chance to run your offering on different clouds, right? You can run it there. The multi-cloud advantages when the Uber offering comes out, which allows you to do things across those installations, right? I can migrate data, I can create data across something like Google has done with B query Omni, I can run predictive models or even make iron models in different place and distribute them, right? And Oracle is paving the road for that, but being available on these clouds. But the multi-cloud capability of database which knows I'm running on different clouds that is still yet to be built there. >>Yeah. And >>That the problem with >>That, that's the super cloud concept that I flowed and I I've always said kinda snowflake with a single global instance is sort of, you know, headed in that direction and maybe has a league. What's the issue with that mark? >>Yeah, the problem with the, with that version, the multi-cloud is clouds to charge egress fees. As long as they charge egress fees to move data between clouds, it's gonna make it very difficult to do a real multi-cloud implementation. Even Snowflake, which runs multi-cloud, has to pass out on the egress fees of their customer when data moves between clouds. And that's really expensive. I mean there, there is one customer I talked to who is beta testing for them, the MySQL heatwave and aws. The only reason they didn't want to do that until it was running on AWS is the egress fees were so great to move it to OCI that they couldn't afford it. Yeah. Egress fees are the big issue but, >>But Mark the, the point might be you might wanna root query and only get the results set back, right was much more tinier, which been the answer before for low latency between the class A problem, which we sometimes still have but mostly don't have. Right? And I think in general this with fees coming down based on the Oracle general E with fee move and it's very hard to justify those, right? But, but it's, it's not about moving data as a multi-cloud high value use case. It's about doing intelligent things with that data, right? Putting into other places, replicating it, what I'm saying the same thing what you said before, running remote queries on that, analyzing it, running AI on it, running AI models on that. That's the interesting thing. Cross administered in the same way. Taking things out, making sure compliance happens. Making sure when Ron says I don't want to be American anymore, I want to be in the European cloud that is gets migrated, right? So tho those are the interesting value use case which are really, really hard for enterprise to program hand by hand by developers and they would love to have out of the box and that's yet the innovation to come to, we have to come to see. But the first step to get there is that your software runs in multiple clouds and that's what Oracle's doing so well with my SQL >>Guys. Amazing. >>Go ahead. Yeah. >>Yeah. >>For example, >>Amazing amount of data knowledge and, and brain power in this market. Guys, I really want to thank you for coming on to the cube. Ron Holger. Mark, always a pleasure to have you on. Really appreciate your time. >>Well all the last names we're very happy for Romanic last and moderator. Thanks Dave for moderating us. All right, >>We'll see. We'll see you guys around. Safe travels to all and thank you for watching this power panel, The Truth About My SQL Heat Wave on the cube. Your leader in enterprise and emerging tech coverage.

>>Everyone, welcome to the cube here in Palo Alto, California for a special presentation on Cloud native at scale, enabling super cloud modern applications with Platform nine. I'm John Furry, your host of The Cube. We've got a great lineup of three interviews we're streaming today. Mattor Makki, who's the co-founder and VP of Product of Platform nine. She's gonna go into detail around Arlon, the open source products, and also the value of what this means for infrastructure as code and for cloud native at scale. Bickley the chief architect of Platform nine Cube alumni. Going back to the OpenStack days. He's gonna go into why Arlon, why this infrastructure as code implication, what it means for customers and the implications in the open source community and where that value is. Really great wide ranging conversation there. And of course, Vascar, Gort, the CEO of Platform nine, is gonna talk with me about his views on Super Cloud and why Platform nine has a scalable solutions to bring cloud native at scale. So enjoy the program, see you soon. Hello and welcome to the cube here in Palo Alto, California for a special program on cloud native at scale, enabling next generation cloud or super cloud for modern application cloud native developers. I'm John Forry, host of the Cube. Pleasure to have here me Makowski, co-founder and VP of product at Platform nine. Thanks for coming in today for this Cloudnative at scale conversation. >>Thank you for having >>Me. So Cloudnative at scale, something that we're talking about because we're seeing the, the next level of mainstream success of containers Kubernetes and cloud native develop, basically DevOps in the C I C D pipeline. It's changing the landscape of infrastructure as code, it's accelerating the value proposition and the super cloud as we call it, has been getting a lot of traction because this next generation cloud is looking a lot different, but kind of the same as the first generation. What's your view on Super cloud as it fits to cloud native as scales up? >>Yeah, you know, I think what's interesting, and I think the reason why Super Cloud is a really good and a really fit term for this, and I think, I know my CEO was chatting with you as well, and he was mentioning this as well, but I think there needs to be a different term than just multi-cloud or cloud. And the reason is because as cloud native and cloud deployments have scaled, I think we've reached a point now where instead of having the traditional data center style model, where you have a few large distributors of infrastructure and workload at a few locations, I think the model is kind of flipped around, right? Where you have a large number of micro sites. These micro sites could be your public cloud deployment, your private on-prem infrastructure deployments, or it could be your edge environment, right? And every single enterprise, every single industry is moving in that direction. And so you gotta rougher that with a terminology that, that, that indicates the scale and complexity of it. And so I think super cloud is a, is an appropriate term for >>That. So you brought a couple things I want to dig into. You mentioned Edge Notes. We're seeing not only edge nodes being the next kind of area of innovation, mainly because it's just popping up everywhere. And that's just the beginning. Wouldn't even know what's around the corner. You got buildings, you got iot, o ot, and it kind of coming together, but you also got this idea of regions, global infrastructures, big part of it. I just saw some news around cloud flare shutting down a site here, there's policies being made at scale. These new challenges there. Can you share because you can have edge. So hybrid cloud is a winning formula. Everybody knows that it's a steady state. Yeah. But across multiple clouds brings in this new un engineered area, yet it hasn't been done yet. Spanning clouds. People say they're doing it, but you start to see the toe in the water, it's happening, it's gonna happen. It's only gonna get accelerated with the edge and beyond globally. So I have to ask you, what is the technical challenges in doing this? Because it's something business consequences as well, but there are technical challenge. Can you share your view on what the technical challenges are for the super cloud across multiple edges and >>Regions? Yeah, absolutely. So I think, you know, in in the context of this, the, this, this term of super cloud, I think it's sometimes easier to visualize things in terms of two access, right? I think on one end you can think of the scale in terms of just pure number of nodes that you have, deploy number of clusters in the Kubernetes space. And then on the other access you would have your distribution factor, right? Which is, do you have these tens of thousands of nodes in one site or do you have them distributed across tens of thousands of sites with one node at each site? Right? And if you have just one flavor of this, there is enough complexity, but potentially manageable. But when you are expanding on both these access, you really get to a point where that skill really needs some well thought out, well-structured solutions to address it, right? A combination of homegrown tooling along with your, you know, favorite distribution of Kubernetes is not a strategy that can help you in this environment. It may help you when you have one of this or when you, when you scale, is not at the level. >>Can you scope the complexity? Because I mean, I hear a lot of moving parts going on there, the technology's also getting better. We we're seeing cloud native become successful. There's a lot to configure, there's a lot to install. Can you scope the scale of the problem? Because we're talking about at scale Yep. Challenges here. >>Yeah, absolutely. And I think, you know, I I like to call it, you know, the, the, the problem that the scale creates, you know, there's various problems, but I think one, one problem, one way to think about it is, is, you know, it works on my cluster problem, right? So, you know, I come from engineering background and there's a, you know, there's a famous saying between engineers and QA and the support folks, right? Which is, it works on my laptop, which is I tested this change, everything was fantastic, it worked flawlessly on my machine, on production, It's not working. The exact same problem now happens and these distributed environments, but at massive scale, right? Which is that, you know, developers test their applications, et cetera within the sanctity of their sandbox environments. But once you expose that change in the wild world of your production deployment, right? >>And the production deployment could be going at the radio cell tower at the edge location where a cluster is running there, or it could be sending, you know, these applications and having them run at my customer's site where they might not have configured that cluster exactly the same way as I configured it, or they configured the cluster, right? But maybe they didn't deploy the security policies or they didn't deploy the other infrastructure plugins that my app relies on all of these various factors at their own layer of complexity. And there really isn't a simple way to solve that today. And that is just, you know, one example of an issue that happens. I think another, you know, whole new ball game of issues come in the context of security, right? Because when you are deploying applications at scale in a distributed manner, you gotta make sure someone's job is on the line to ensure that the right security policies are enforced regardless of that scale factor. So I think that's another example of problems that occur. >>Okay. So I have to ask about scale because there are a lot of multiple steps involved when you see the success cloud native, you know, you see some, you know, some experimentation. They set up a cluster, say it's containers and Kubernetes, and then you say, Okay, we got this, we can configure it. And then they do it again and again, they call it day two. Some people call it day one, day two operation, whatever you call it. Once you get past the first initial thing, then you gotta scale it. Then you're seeing security breaches, you're seeing configuration errors. This seems to be where the hotpot is. And when companies transition from, I got this to, Oh no, it's harder than I thought at scale. Can you share your reaction to that and how you see this playing out? >>Yeah, so, you know, I think it's interesting. There's multiple problems that occur when, you know, the, the two factors of scale is we talked about start expanding. I think one of them is what I like to call the, you know, it, it works fine on my cluster problem, which is back in, when I was a developer, we used to call this, it works on my laptop problem, which is, you know, you have your perfectly written code that is operating just fine on your machine, your sandbox environment. But the moment it runs production, it comes back with p zeros and POS from support teams, et cetera. And those issues can be really difficult to try us, right? And so in the Kubernetes environment, this problem kind of multi folds, it goes, you know, escalates to a higher degree because yeah, you have your sandbox developer environments, they have their clusters and things work perfectly fine in those clusters because these clusters are typically handcrafted or a combination of some scripting and handcrafting. >>And so as you give that change to then run at your production edge location, like say you radio sell tower site, or you hand it over to a customer to run it on their cluster, they might not have not have configured that cluster exactly how you did it, or they might not have configured some of the infrastructure plugins. And so the things don't work. And when things don't work, triaging them becomes like ishly hard, right? It's just one of the examples of the problem. Another whole bucket of issues is security, which is, is you have these distributed clusters at scale, you gotta ensure someone's job is on the line to make sure that these security policies are configured properly. >>So this is a huge problem. I love that comment. That's not not happening on my system. It's the classic, you know, debugging mentality. Yeah. But at scale it's hard to do that with error prone. I can see that being a problem. And you guys have a solution you're launching, Can you share what our lawn is, this new product, What is it all about? Talk about this new introduction. >>Yeah, absolutely. I'm very, very excited. You know, it's one of the projects that we've been working on for some time now because we are very passionate about this problem and just solving problems at scale in on-prem or at in the cloud or at edge environments. And what arwan is, it's an open source project and it is a tool, it's a Kubernetes native tool for complete end to end management of not just your clusters, but your clusters. All of the infrastructure that goes within and along the sites of those clusters, security policies, your middleware plugins, and finally your applications. So what alarm lets you do in a nutshell is in a declarative way, it lets you handle the configuration and management of all of these components in at scale. >>So what's the elevator pitch simply put for what this solves in, in terms of the chaos you guys are reigning in. What's the, what's the bumper sticker? Yeah, >>What would it do? There's a perfect analogy that I love to reference in this context, which is think of your assembly line, you know, in a traditional, let's say, you know, an auto manufacturing factory or et cetera, and the level of efficiency at scale that that assembly line brings, right online. And if you look at the logo we've designed, it's this funny little robot. And it's because when we think of online, we, we think of these enterprise large scale environments, you know, sprawling at scale creating chaos because there isn't necessarily a well thought through, well structured solution that's similar to an assembly line, which is taking each components, you know, addressing them, manufacturing, processing them in a standardized way, then handing to the next stage. But again, it gets, you know, processed in a standardized way. And that's what Arlon really does. That's like the I pitch. If you have problems of scale of managing your infrastructure, you know, that is distributed. Arlon brings the assembly line level of efficiency and consistency >>For those. So keeping it smooth, the assembly on things are flowing. C C I CD pipelining. Exactly. So that's what you're trying to simplify that ops piece for the developer. I mean, it's not really ops, it's their ops, it's coding. >>Yeah. Not just developer, the ops, the operations folks as well, right? Because developers, you know, there is, the developers are responsible for one picture of that layer, which is my apps, and then maybe that middleware of application that they interface with, but then they hand it over to someone else who's then responsible to ensure that these apps are secure properly, that they are logging, logs are being collected properly, monitoring and observability integrated. And so it solves problems for both those >>Teams. Yeah. It's DevOps. So the DevOps is the cloud native developer. The OP teams have to kind of set policies. Is that where the declarative piece comes in? Is that why that's important? >>Absolutely. Yeah. And, and, and, and you know, Kubernetes really in introduced or elevated this declarative management, right? Because, you know, c communities clusters are Yeah. Or your, yeah, you know, specifications of components that go in Kubernetes are defined in a declarative way. And Kubernetes always keeps that state consistent with your defined state. But when you go outside of that world of a single cluster, and when you actually talk about defining the clusters or defining everything that's around it, there really isn't a solution that does that today. And so online addresses that problem at the heart of it, and it does that using existing open source well known solutions. >>Ed, do I wanna get into the benefits? What's in it for me as the customer developer? But I want to finish this out real quick and get your thoughts. You mentioned open source. Why open source? What's the, what's the current state of the product? You run the product group over at platform nine, is it open source? And you guys have a product that's commercial? Can you explain the open source dynamic? And first of all, why open source? Yeah. And what is the consumption? I mean, open source is great, People want open source, they can download it, look up the code, but maybe wanna buy the commercial. So I'm assuming you have that thought through, can you share open source and commercial relationship? >>Yeah, I think, you know, starting with why open source? I think it's, you know, we as a company, we have, you know, one of the things that's absolutely critical to us is that we take mainstream open source technologies components and then we, you know, make them available to our customers at scale through either a SaaS model on from model, right? But, so as we are a company or startup or a company that benefits, you know, in a massive way by this open source economy, it's only right, I think in my mind that we do our part of the duty, right? And contribute back to the community that feeds us. And so, you know, we have always held that strongly as one of our principles. And we have, you know, created and built independent products starting all the way with fi, which was a serverless product, you know, that we had built to various other, you know, examples that I can give. But that's one of the main reasons why opensource and also opensource because we want the community to really firsthand engage with us on this problem, which is very difficult to achieve if your product is behind a wall, you know, behind, behind a block box. >>Well, and that's, that's what the developers want too. I mean, what we're seeing in reporting with Super Cloud is the new model of consumption is I wanna look at the code and see what's in there. That's right. And then also, if I want to use it, I, I'll do it. Great. That's open source, that's the value. But then at the end of the day, if I wanna move fast, that's when people buy in. So it's a new kind of freemium, I guess, business model. I guess that's the way that, Well, but that's, that's the benefit. Open source. This is why standards and open source is growing so fast. You have that confluence of, you know, a way for helpers to try before they buy, but also actually kind of date the application, if you will. We, you know, Adrian Karo uses the dating me metaphor, you know, Hey, you know, I wanna check it out first before I get married. Right? And that's what open source, So this is the new, this is how people are selling. This is not just open source, this is how companies are selling. >>Absolutely. Yeah. Yeah. You know, I think, and you know, two things. I think one is just, you know, this, this, this cloud native space is so vast that if you, if you're building a close flow solution, sometimes there's also a risk that it may not apply to every single enterprises use cases. And so having it open source gives them an opportunity to extend it, expand it, to make it proper to their use case if they choose to do so, right? But at the same time, what's also critical to us is we are able to provide a supported version of it with an SLA that we, you know, that's backed by us, a SAS hosted version of it as well, for those customers who choose to go that route, you know, once they have used the open source version and loved it and want to take it at scale and in production and need, need, need a partner to collaborate with, who can, you know, support them for that production >>Environment. I have to ask you now, let's get into what's in it for the customer. I'm a customer, why should I be enthused about Arlo? What's in it for me? You know? Cause if I'm not enthused about it, I'm not gonna be confident and it's gonna be hard for me to get behind this. Can you share your enthusiastic view of, you know, why I should be enthused about Arlo customer? >>Yeah, absolutely. And so, and there's multiple, you know, enterprises that we talk to, many of them, you know, our customers, where this is a very kind of typical story that you hear, which is we have, you know, a Kubernetes distribution. It could be on premise, it could be public clouds, native es, and then we have our C I CD pipelines that are automating the deployment of applications, et cetera. And then there's this gray zone. And the gray zone is well before you can you, your CS CD pipelines can deploy the apps. Somebody needs to do all of their groundwork of, you know, defining those clusters and yeah. You know, properly configuring them. And as these things, these things start by being done hand grown. And then as the, as you scale, what typically enterprises would do today is they will have their home homegrown DIY solutions for this. >>I mean, the number of folks that I talk to that have built Terra from automation, and then, you know, some of those key developers leave. So it's a typical open source or typical, you know, DIY challenge. And the reason that they're writing it themselves is not because they want to. I mean, of course technology is always interesting to everybody, but it's because they can't find a solution that's out there that perfectly fits the problem. And so that's that pitch. I think Spico would be delighted. The folks that we've talked, you know, spoken with, have been absolutely excited and have, you know, shared that this is a major challenge we have today because we have, you know, few hundreds of clusters on s Amazon and we wanna scale them to few thousands, but we don't think we are ready to do that. And this will give us >>Stability. Yeah, I think people are scared, not sc I won't say scare, that's a bad word. Maybe I should say that they feel nervous because, you know, at scale small mistakes can become large mistakes. This is something that is concerning to enterprises. And, and I think this is gonna come up at co con this year where enterprises are gonna say, Okay, I need to see SLAs. I wanna see track record, I wanna see other companies that have used it. Yeah. How would you answer that question to, or, or challenge, you know, Hey, I love this, but is there any guarantees? Is there any, what's the SLAs? I'm an enterprise, I got tight, you know, I love the open source trying to free fast and loose, but I need hardened code. >>Yeah, absolutely. So, so two parts to that, right? One is Arlan leverages existing open source components, products that are extremely popular. Two specifically. One is Lon uses Argo cd, which is probably one of the highest rated and used CD open source tools that's out there, right? It's created by folks that are as part of Intuit team now, you know, really brilliant team. And it's used at scale across enterprises. That's one. Second is arlon also makes use of cluster api capi, which is a ES sub-component, right? For lifecycle management of clusters. So there is enough of, you know, community users, et cetera, around these two products, right? Or, or, or open source projects that will find Arlan to be right up in their alley because they're already comfortable, familiar with algo cd. Now Arlan just extends the scope of what Algo CD can do. And so that's one. And then the second part is going back to a point of the comfort. And that's where, you know, Platform nine has a role to play, which is when you are ready to deploy Alon at scale, because you've been, you know, playing with it in your DEF test environments, you're happy with what you get with it, then Platform nine will stand behind it and provide that sla. >>And what's been the reaction from customers you've talked to Platform nine customers with, with, that are familiar with, with Argo and then Arlo? What's been some of the feedback? >>Yeah, I, I, I think the feedback's been fantastic. I mean, I can give you examples of customers where, you know, initially, you know, when you are, when you're telling them about your entire portfolio of solutions, it might not strike a card right away. But then we start talking about Arlan and, and we talk about the fact that it uses Argo CD and they start opening up, they say, We have standardized on Argo and we have built these components, homegrown, we would be very interested. Can we co-develop? Does it support these use cases? So we've had that kind of validation. We've had validation all the way at the beginning of our line before we even wrote a single line of code saying this is something we plan on doing. And the customer said, If you had it today, I would've purchased it. So it's been really great validation. >>All right. So next question is, what is the solution to the customer? If I asked you, Look it, I have, I'm so busy, my team's overworked. I got a skills gap. I don't need another project that's, I'm so tied up right now and I'm just chasing my tail. How does Platform nine help me? >>Yeah, absolutely. So I think, you know, one of the core tenets of Platform nine has always been that we try to bring that public cloud like simplicity by hosting, you know, this in a lot of such similar tools in a SaaS hosted manner for our customers, right? So our goal behind doing that is taking away or trying to take away all of that complexity from customer's hands and offloading it to our hands, right? And giving them that full white glove treatment as we call it. And so from a customer's perspective, one, something like arlon will integrate with what they have so they don't have to rip and replace anything. In fact, it will, even in the next versions, it may even discover your clusters that you have today and, you know, give you an inventory and that, >>So customers have clusters that are growing, that's a sign correct call you guys. >>Absolutely. Either they're, they have massive large clusters, right? That they wanna split into smaller clusters, but they're not comfortable doing that today, or they've done that already on say, public cloud or otherwise. And now they have management challenges. So >>Especially operationalizing the clusters, whether they want to kind of reset everything and remove things around and reconfigure Yeah. And or scale out. >>That's right. Exactly. >>And you provide that layer of policy. >>Absolutely. >>Yes. That's the key value >>Here. That's right. >>So policy based configuration for cluster scale up >>Profile and policy based declarative configuration and life cycle management for clusters. >>If I asked you how this enables Super club, what would you say to that? >>I think this is one of the key ingredients to super cloud, right? If you think about a super cloud environment, there's at least few key ingredients that that come to my mind that are really critical. Like they are, you know, life saving ingredients at that scale. One is having a really good strategy for managing that scale, you know, in a, going back to assembly line in a very consistent, predictable way so that our lot solves then you, you need to compliment that with the right kind of observability and monitoring tools at scale, right? Because ultimately issues are gonna happen and you're gonna have to figure out, you know, how to solve them fast. And alon by the way, also helps in that direction, but you also need observability tools. And then especially if you're running it on the public cloud, you need some cost management tools. In my mind, these three things are like the most necessary ingredients to make Super Cloud successful. And, you know, alarm flows >>In one. Okay, so now the next level is, Okay, that makes sense. There's under the covers kind of speak under the hood. Yeah. How does that impact the app developers and the cloud native modern application workflows? Because the impact to me, seems the apps are gonna be impacted. Are they gonna be faster, stronger? I mean, what's the impact if you do all those things, as you mentioned, what's the impact of the apps? >>Yeah, the impact is that your apps are more likely to operate in production the way you expect them to, because the right checks and balances have gone through, and any discrepancies have been identified prior to those apps, prior to your customer running into them, right? Because developers run into this challenge to their, where there's a split responsibility, right? I'm responsible for my code, I'm responsible for some of these other plugins, but I don't own the stack end to end. I have to rely on my ops counterpart to do their part, right? And so this really gives them, you know, the right tooling for >>That. So this is actually a great kind of relevant point, you know, as cloud becomes more scalable, you're starting to see this fragmentation gone of the days of the full stack developer to the more specialized role. But this is a key point, and I have to ask you because if this Arlo solution takes place, as you say, and the apps are gonna be stupid, there's designed to do, the question is, what did, does the current pain look like of the apps breaking? What does the signals to the customer Yeah. That they should be calling you guys up into implementing Arlo, Argo, and, and, and on all the other goodness to automate, What are some of the signals? Is it downtime? Is it, is it failed apps, Is it latency? What are some of the things that Yeah, absolutely would be in indications of things are effed up a little bit. >>Yeah. More frequent down times, down times that are, that take longer to triage. And so you are, you know, the, you know, your mean times on resolution, et cetera, are escalating or growing larger, right? Like we have environments of customers where they, they have a number of folks on in the field that have to take these apps and run them at customer sites. And that's one of our partners. And they're extremely interested in this because the, the rate of failures they're encountering for this, you know, the field when they're running these apps on site, because the field is automating their clusters that are running on sites using their own script. So these are the kinds of challenges, and those are the pain points, which is, you know, if you're looking to reduce your, your meantime to resolution, if you're looking to reduce the number of failures that occur on your production site, that's one. And second, if you are looking to manage these at scale environments with a relatively small, focused, nimble ops team, which has an immediate impact on your, So those are, those are the >>Signals. This is the cloud native at scale situation, the innovation going on. Final thought is your reaction to the idea that if the world goes digital, which it is, and the confluence of physical and digital coming together, and cloud continues to do its thing, the company becomes the application, not where it used to be supporting the business, you know, the back office and the IIA terminals and some PCs and handhelds. Now if technology's running, the business is the business. Yeah. The company's the application. Yeah. So it can't be down. So there's a lot of pressure on, on CSOs and CIOs now and see, and boards is saying, how is technology driving the top line revenue? That's the number one conversation. Yeah. Do you see that same thing? >>Yeah. It's interesting. I think there's multiple pressures at the CXO CIO level, right? One is that there needs to be that visibility and clarity and guarantee almost that, you know, that the, the technology that's, you know, that's gonna drive your top line is gonna drive that in a consistent, reliable, predictable manner. And then second, there is the constant pressure to do that while always lowering your costs of doing it, right? Especially when you're talking about, let's say retailers or those kinds of large scale vendors, they many times make money by lowering the amount that they spend on, you know, providing those goods to their end customers. So I think those, both those factors kind of come into play and the solution to all of them is usually in a very structured strategy around automation. >>Final question. What does cloudnative at scale look like to you? If all the things happen the way we want 'em to happen, The magic wand, the magic dust, what does it look like? >>What that looks like to me is a CIO sipping at his desk on coffee production is running absolutely smooth. And his, he's running that at a nimble, nimble team size of at the most, a handful of folks that are just looking after things with things. So just >>Taking care of, and the CIO doesn't exist. There's no CSO there at the beach. >>Yeah. >>Thank you for coming on, sharing the cloud native at scale here on the cube. Thank you for your time. >>Fantastic. Thanks for having >>Me. Okay. I'm John Fur here for special program presentation, special programming cloud native at scale, enabling super cloud modern applications with Platform nine. Thanks for watching. Welcome back everyone to the special presentation of cloud native at scale, the cube and platform nine special presentation going in and digging into the next generation super cloud infrastructure as code and the future of application development. We're here at Bickley, who's the chief architect and co-founder of Platform nine b. Great to see you Cube alumni. We, we met at an OpenStack event in about eight years ago, or well later, earlier when opens Stack was going. Great to see you and great to see congratulations on the success of platform nine. >>Thank you very much. >>Yeah. You guys have been at this for a while and this is really the, the, the year we're seeing the, the crossover of Kubernetes because of what happens with containers. Everyone now was realized, and you've seen what Docker's doing with the new docker, the open source Docker now just a success Exactly. Of containerization, right? And now the Kubernetes layer that we've been working on for years is coming, bearing fruit. This is huge. >>Exactly. Yes. >>And so as infrastructure's code comes in, we talked to Bacar talking about Super Cloud, I met her about, you know, the new Arlon, our R lawn you guys just launched, the infrastructure's code is going to another level. And then it's always been DevOps infrastructure is code. That's been the ethos that's been like from day one, developers just code. Then you saw the rise of serverless and you see now multi-cloud or on the horizon, connect the dots for us. What is the state of infrastructures code today? >>So I think, I think I'm, I'm glad you mentioned it, everybody or most people know about infrastructures code. But with Kubernetes, I think that project has evolved at the concept even further. And these dates, it's infrastructure as configuration, right? So, which is an evolution of infrastructure as code. So instead of telling the system, here's how I want my infrastructure by telling it, you know, do step A, B, C, and D instead with Kubernetes, you can describe your desired state declaratively using things called manifest resources. And then the system kind of magically figures it out and tries to converge the state towards the one that you specify. So I think it's, it's a even better version of infrastructures code. >>Yeah, yeah. And, and that really means it's developer just accessing resources. Okay. Not declaring, Okay, give me some compute, stand me up some, turn the lights on, turn 'em off, turn 'em on. That's kind of where we see this going. And I like the configuration piece. Some people say composability, I mean now with open source, so popular, you don't have to have to write a lot of code. It's code being developed. And so it's into integration, it's configuration. These are areas that we're starting to see computer science principles around automation, machine learning, assisting open source. Cuz you got a lot of code that's right in hearing software, supply chain issues. So infrastructure as code has to factor in these new, new dynamics. Can you share your opinion on these new dynamics of, as open source grows, the glue layers, the configurations, the integration, what are the core issues? >>I think one of the major core issues is with all that power comes complexity, right? So, you know, despite its expressive power systems like Kubernetes and declarative APIs let you express a lot of complicated and complex stacks, right? But you're dealing with hundreds if not thousands of these yamo files or resources. And so I think, you know, the emergence of systems and layers to help you manage that complexity is becoming a key challenge and opportunity in, in this space that, >>That's, I wrote a LinkedIn post today was comments about, you know, hey, enterprise is the new breed, the trend of SaaS companies moving our consumer comp consumer-like thinking into the enterprise has been happening for a long time, but now more than ever, you're seeing it the old way used to be solve complexity with more complexity and then lock the customer in. Now with open source, it's speed, simplification and integration, right? These are the new dynamic power dynamics for developers. Yeah. So as companies are starting to now deploy and look at Kubernetes, what are the things that need to be in place? Because you have some, I won't say technical debt, but maybe some shortcuts, some scripts here that make it look like infrastructure is code. People have done some things to simulate or or make infrastructure as code happen. Yes. But to do it at scale Yes. Is harder. What's your take on this? What's your >>View? It's hard because there's a per proliferation of methods, tools, technologies. So for example, today it's very common for DevOps and platform engineering tools, I mean, sorry, teams to have to deploy a large number of Kubernetes clusters, but then apply the applications and configurations on top of those clusters. And they're using a wide range of tools to do this, right? For example, maybe Ansible or Terraform or bash scripts to bring up the infrastructure and then the clusters. And then they may use a different set of tools such as Argo CD or other tools to apply configurations and applications on top of the clusters. So you have this sprawl of tools. You, you also have this sprawl of configurations and files because the more objects you're dealing with, the more resources you have to manage. And there's a risk of drift that people call that where, you know, you think you have things under control, but some people from various teams will make changes here and there and then before the end of the day systems break and you have no idea of tracking them. So I think there's real need to kind of unify, simplify, and try to solve these problems using a smaller, more unified set of tools and methodologies. And that's something that we try to do with this new project. Arlon. >>Yeah. So, so we're gonna get into Arlan in a second. I wanna get into the why Arlon. You guys announced that at our GoCon, which was put on here in Silicon Valley at the, at the by intu. They had their own little day over there at their headquarters. But before we get there, Vascar, your CEO came on and he talked about Super Cloud at our inaugural event. What's your definition of super cloud? If you had to kind of explain that to someone at a cocktail party or someone in the industry technical, how would you look at the super cloud trend that's emerging? It's become a thing. What's your, what would be your contribution to that definition or the narrative? >>Well, it's, it's, it's funny because I've actually heard of the term for the first time today, speaking to you earlier today. But I think based on what you said, I I already get kind of some of the, the gist and the, the main concepts. It seems like super cloud, the way I interpret that is, you know, clouds and infrastructure, programmable infrastructure, all of those things are becoming commodity in a way. And everyone's got their own flavor, but there's a real opportunity for people to solve real business problems by perhaps trying to abstract away, you know, all of those various implementations and then building better abstractions that are perhaps business or application specific to help companies and businesses solve real business problems. >>Yeah, I remember that's a great, great definition. I remember, not to date myself, but back in the old days, you know, IBM had a proprietary network operating system, so to deck for the mini computer vendors, deck net and SNA respectively. But T C P I P came out of the osi, the open systems interconnect and remember, ethernet beat token ring out. So not to get all nerdy for all the young kids out there, look, just look up token ring, you'll see, you've probably never heard of it. It's IBM's, you know, connection for the internet at the, the layer too is Amazon, the ethernet, right? So if T C P I P could be the Kubernetes and the container abstraction that made the industry completely change at that point in history. So at every major inflection point where there's been serious industry change and wealth creation and business value, there's been an abstraction Yes. Somewhere. Yes. What's your reaction to that? >>I think this is, I think a saying that's been heard many times in this industry and, and I forgot who originated it, but I think the saying goes like, there's no problem that can't be solved with another layer of indirection, right? And we've seen this over and over and over again where Amazon and its peers have inserted this layer that has simplified, you know, computing and, and infrastructure management. And I believe this trend is going to continue, right? The next set of problems are going to be solved with these insertions of additional abstraction layers. I think that that's really a, yeah, it's gonna continue. >>It's interesting. I just really wrote another post today on LinkedIn called the Silicon Wars AMD Stock is down arm has been on rise, we've remember pointing for many years now, that arm's gonna be hugely, it has become true. If you look at the success of the infrastructure as a service layer across the clouds, Azure, aws, Amazon's clearly way ahead of everybody. The stuff that they're doing with the silicon and the physics and the, the atoms, the pro, you know, this is where the innovation, they're going so deep and so strong at ISAs, the more that they get that gets come on, they have more performance. So if you're an app developer, wouldn't you want the best performance and you'd wanna have the best abstraction layer that gives you the most ability to do infrastructures, code or infrastructure for configuration, for provisioning, for managing services. And you're seeing that today with service MeSHs, a lot of action going on in the service mesh area in, in this community of co con, which will be a covering. So that brings up the whole what's next? You guys just announced our lawn at ar GoCon, which came out of Intuit. We've had Maria Teel at our super cloud event, She's a cto, you know, they're all in the cloud. So they contributed that project. Where did Arlon come from? What was the origination? What's the purpose? Why our lawn, why this announcement? Yeah, >>So the, the inception of the project, this was the result of us realizing that problem that we spoke about earlier, which is complexity, right? With all of this, these clouds, these infrastructure, all the variations around and you know, compute storage networks and the proliferation of tools we talked about the Ansibles and Terraforms and Kubernetes itself, you can think of that as another tool, right? We saw a need to solve that complexity problem, and especially for people and users who use Kubernetes at scale. So when you have, you know, hundreds of clusters, thousands of applications, thousands of users spread out over many, many locations, there, there needs to be a system that helps simplify that management, right? So that means fewer tools, more expressive ways of describing the state that you want and more consistency. And, and that's why, you know, we built AR lawn and we built it recognizing that many of these problems or sub problems have already been solved. So Arlon doesn't try to reinvent the wheel, it instead rests on the shoulders of several giants, right? So for example, Kubernetes is one building block, GI ops, and Argo CD is another one, which provides a very structured way of applying configuration. And then we have projects like cluster API and cross plane, which provide APIs for describing infrastructure. So arlon takes all of those building blocks and builds a thin layer, which gives users a very expressive way of defining configuration and desired state. So that's, that's kind of the inception of, And >>What's the benefit of that? What does that give the, what does that give the developer, the user, in this case, >>The developers, the, the platform engineer, team members, the DevOps engineers, they get a a ways to provision not just infrastructure and clusters, but also applications and configurations. They get a way, a system for provisioning, configuring, deploying, and doing life cycle management in a, in a much simpler way. Okay. Especially as I said, if you're dealing with a large number of applications. >>So it's like an operating fabric, if you will. Yes. For them. Okay, so let's get into what that means for up above and below the, the, this abstraction or thin layer below the infrastructure. We talked a lot about what's going on below that. Yeah. Above our workloads at the end of the day, and I talk to CXOs and IT folks that, that are now DevOps engineers. They care about the workloads and they want the infrastructure's code to work. They wanna spend their time getting in the weeds, figuring out what happened when someone made a push that that happened or something happened. They need observability and they need to, to know that it's working. That's right. And here's my workloads running effectively. So how do you guys look at the workload side of it? Cuz now you have multiple workloads on these fabric, right? >>So workloads, so Kubernetes has defined kind of a standard way to describe workloads and you can, you know, tell Kubernetes, I want to run this container this particular way, or you can use other projects that are in the Kubernetes cloud native ecosystem, like K native, where you can express your application in more at a higher level, right? But what's also happening is in addition to the workloads, DevOps and platform engineering teams, they need to very often deploy the applications with the clusters themselves. Clusters are becoming this commodity. It's, it's becoming this host for the application and it kind of comes bundled with it. In many cases it is like an appliance, right? So DevOps teams have to provision clusters at a really incredible rate and they need to tear them down. Clusters are becoming more, >>It's coming like an EC two instance, spin up a cluster. We've heard people used words like that. That's >>Right. And before arlon you kind of had to do all of that using a different set of tools as, as I explained. So with AR loan you can kind of express everything together. You can say I want a cluster with a health monitoring stack and a logging stack and this ingress controller and I want these applications and these security policies. You can describe all of that using something we call the profile. And then you can stamp out your app, your applications and your clusters and manage them in a very, So >>It's essentially standard, like creates a mechanism. Exactly. Standardized, declarative kind of configurations. And it's like a playbook, just deploy it. Now what there is between say a script like I'm, I have scripts, I can just automate scripts >>Or yes, this is where that declarative API and infrastructure as configuration comes in, right? Because scripts, yes you can automate scripts, but the order in which they run matters, right? They can break, things can break in the middle and, and sometimes you need to debug them. Whereas the declarative way is much more expressive and powerful. You just tell the system what you want and then the system kind of figures it out. And there are these things are controllers which will in the background reconcile all the state to converge towards your desire. It's a much more powerful, expressive and reliable way of getting things done. >>So infrastructure as configuration is built kind of on, it's a super set of infrastructures code because it's >>An evolution. >>You need edge's code, but then you can configure the code by just saying do it. You basically declaring saying Go, go do that. That's right. Okay, so, alright, so cloud native at scale, take me through your vision of what that means. Someone says, Hey, what does cloud native at scale mean? What's success look like? How does it roll out in the future as you, not future next couple years. I mean people are now starting to figure out, okay, it's not as easy as it sounds. Kubernetes has value. We're gonna hear this year at CubeCon a lot of this, what does cloud native at scale >>Mean? Yeah, there are different interpretations, but if you ask me, when people think of scale, they think of a large number of deployments, right? Geographies, many, you know, supporting thousands or tens or millions of, of users there, there's that aspect to scale. There's also an equally important a aspect of scale, which is also something that we try to address with Arran. And that is just complexity for the people operating this or configuring this, right? So in order to describe that desired state, and in order to perform things like maybe upgrades or updates on a very large scale, you want the humans behind that to be able to express and direct the system to do that in, in relatively simple terms, right? And so we want the tools and the abstractions and the mechanisms available to the user to be as powerful but as simple as possible. So there's, I think there's gonna be a number and there have been a number of CNCF and cloud native projects that are trying to attack that complexity problem as well. And Arlon kind of falls in in that >>Category. Okay, so I'll put you on the spot rogue, that CubeCon coming up and now this'll be shipping this segment series out before. What do you expect to see at this year? It's the big story this year. What's the, what's the most important thing happening? Is it in the open source community and also within a lot of the, the people jockeying for leadership. I know there's a lot of projects and still there's some white space in the overall systems map about the different areas get run time and there's ability in all these different areas. What's the, where's the action? Where, where's the smoke? Where's the fire? Where's the piece? Where's the tension? >>Yeah, so I think one thing that has been happening over the past couple of coupon and I expect to continue and, and that is the, the word on the street is Kubernetes is getting boring, right? Which is good, right? >>Boring means simple. >>Well, well >>Maybe, >>Yeah, >>Invisible, >>No drama, right? So, so the, the rate of change of the Kubernetes features and, and all that has slowed but in, in a, in a positive way. But there's still a general sentiment and feeling that there's just too much stuff. If you look at a stack necessary for hosting applications based on Kubernetes, there are just still too many moving parts, too many components, right? Too much complexity. I go, I keep going back to the complexity problem. So I expect Cube Con and all the vendors and the players and the startups and the people there to continue to focus on that complexity problem and introduce further simplifications to, to the stack. >>Yeah. Vic, you've had an storied career VMware over decades with them within 12 years with 14 years or something like that. Big number co-founder here a platform. I you's been around for a while at this game, man. We talked about OpenStack, that project we interviewed at one of their events. So OpenStack was the beginning of that, this new revolution. I remember the early days it was, it wasn't supposed to be an alternative to Amazon, but it was a way to do more cloud cloud native. I think we had a Cloud Aati team at that time. We would joke we, you know, about, about the dream. It's happening now, now at Platform nine. You guys have been doing this for a while. What's the, what are you most excited about as the chief architect? What did you guys double down on? What did you guys pivot from or two, did you do any pivots? Did you extend out certain areas? Cuz you guys are in a good position right now, a lot of DNA in Cloud native. What are you most excited about and what does Platform Nine bring to the table for customers and for people in the industry watching this? >>Yeah, so I think our mission really hasn't changed over the years, right? It's been always about taking complex open source software because open source software, it's powerful. It solves new problems, you know, every year and you have new things coming out all the time, right? Opens Stack was an example and then Kubernetes took the world by storm. But there's always that complexity of, you know, just configuring it, deploying it, running it, operating it. And our mission has always been that we will take all that complexity and just make it, you know, easy for users to consume regardless of the technology, right? So the successor to Kubernetes, you know, I don't have a crystal ball, but you know, you have some indications that people are coming up of new and simpler ways of running applications. There are many projects around there who knows what's coming next year or the year after that. But platform will a, platform nine will be there and we will, you know, take the innovations from the the community. We will contribute our own innovations and make all of those things very consumable to customers. >>Simpler, faster, cheaper. Exactly. Always a good business model technically to make that happen. Yes. Yeah, I think the, the reigning in the chaos is key, you know, Now we have now visibility into the scale. Final question before we depart this segment. What is at scale, how many clusters do you see that would be a watermark for an at scale conversation around an enterprise? Is it workloads we're looking at or, or clusters? How would you, Yeah, how would you describe that? When people try to squint through and evaluate what's a scale, what's the at scale kind of threshold? >>Yeah. And, and the number of clusters doesn't tell the whole story because clusters can be small in terms of the number of nodes or they can be large. But roughly speaking when we say, you know, large scale cluster deployments, we're talking about maybe hundreds, two thousands. >>Yeah. And final final question, what's the role of the hyperscalers? You got AWS continuing to do well, but they got their core ias, they got a PAs, they're not too too much putting a SaaS out there. They have some SaaS apps, but mostly it's the ecosystem. They have marketplaces doing, doing over $2 billion billions of transactions a year and, and it's just like, just sitting there. It hasn't really, they're now innovating on it, but that's gonna change ecosystems. What's the role the cloud play in the cloud need of its scale? >>The, the hyper squares? >>Yeah, yeah. A's Azure Google, >>You mean from a business perspective, they're, they have their own interests that, you know, that they're, they will keep catering to, they, they will continue to find ways to lock their users into their ecosystem of services and, and APIs. So I don't think that's gonna change, right? They're just gonna keep well, >>They got great performance. I mean, from a, from a hardware standpoint, yes. That's gonna be key, >>Right? Yes. I think the, the move from X 86 being the dominant way and platform to run workloads is changing, right? That, that, that, that, and I think the, the hyper skaters really want to be in the game in terms of, you know, the, the new risk and arm ecosystems, the platforms. >>Yeah. Not joking aside, Paul Morritz, when he was the CEO of VMware, when he took over once said, I remember our first year doing the cube. Oh the cloud is one big distributed computer. It's, it's hardware and you got software and you got middleware and he kinda over, well he's kind of tongue in cheek, but really you're talking about large compute and sets of services that is essentially a distributed computer. Yes, >>Exactly. >>It's, we're back in the same game. Thank you for coming on the segment. Appreciate your time. This is cloud native at scale special presentation with Platform nine. Really unpacking super cloud Arlon open source and how to run large scale applications on the cloud, cloud native develop for developers. And John Furrier with the cube. Thanks for Washington. We'll stay tuned for another great segment coming right up. Hey, welcome back everyone to Super Cloud 22. I'm John Fur, host of the Cuba here all day talking about the future of cloud. Where's it all going? Making it super multi-cloud is around the corner and public cloud is winning. Got the private cloud on premise and Edge. Got a great guest here, Vascar Gorde, CEO of Platform nine, just on the panel on Kubernetes. An enabler blocker. Welcome back. Great to have you on. >>Good to see you >>Again. So Kubernetes is a blocker enabler by, with a question mark I put on on there. Panel was really to discuss the role of Kubernetes. Now great conversation operations is impacted. What's just thing about what you guys are doing at Platform nine? Is your role there as CEO and the company's position, kind of like the world spun into the direction of Platform nine while you're at the helm, right? >>Absolutely. In fact, things are moving very well and since they came to us, it was an insight to call ourselves the platform company eight years ago, right? So absolutely whether you are doing it in public clouds or private clouds, you know, the application world is moving very fast in trying to become digital and cloud native. There are many options for you to run the infrastructure. The biggest blocking factor now is having a unified platform. And that's what where we come into >>Patrick, we were talking before we came on stage here about your background and we were kind of talking about the glory days in 2000, 2001 when the first ASPs application service providers came out. Kind of a SaaS vibe, but that was kind of all kind of cloud-like >>It wasn't, >>And web services started then too. So you saw that whole growth. Now, fast forward 20 years later, 22 years later, where we are now, when you look back then to here and all the different cycles, >>In fact, you know, as we were talking offline, I was in one of those ASPs in the year 2000 where it was a novel concept of saying we are providing a software and a capability as a service, right? You sign up and start using it. I think a lot has changed since then. The tooling, the tools, the technology has really skyrocketed. The app development environment has really taken off exceptionally well. There are many, many choices of infrastructure now, right? So I think things are in a way the same but also extremely different. But more importantly now for any company, regardless of size, to be a digital native, to become a digital company is extremely mission critical. It's no longer a nice to have everybody's in the journey somewhere. >>Everyone is going digital transformation here. Even on a so-called downturn recession that's upcoming inflations sea year. It's interesting. This is the first downturn, the history of the world where the hyperscale clouds have been pumping on all cylinders as an economic input. And if you look at the tech trends, GDPs down, but not tech. Nope. Cause pandemic showed everyone digital transformation is here and more spend and more growth is coming even in, in tech. So this is a unique factor which proves that that digital transformation's happening and company, every company will need a super cloud. >>Everyone, every company, regardless of size, regardless of location, has to become modernize their infrastructure. And modernizing infrastructure is not just some, you know, new servers and new application tools. It's your approach, how you're serving your customers, how you're bringing agility in your organization. I think that is becoming a necessity for every enterprise to survive. >>I wanna get your thoughts on Super Cloud because one of the things Dave Alon and I want to do with Super Cloud and calling it that was we, I, I personally, and I know Dave as well, he can, I'll speak from, he can speak for himself. We didn't like multi-cloud. I mean not because Amazon said don't call things multi-cloud, it just didn't feel right. I mean everyone has multiple clouds by default. If you're running productivity software, you have Azure and Office 365. But it wasn't truly distributed. It wasn't truly decentralized, it wasn't truly cloud enabled. It didn't, it felt like they're not ready for a market yet. Yet public clouds booming on premise. Private cloud and Edge is much more on, you know, more, More dynamic, more unreal. >>Yeah. I think the reason why we think Super cloud is a better term than multi-cloud. Multi-cloud are more than one cloud, but they're disconnected. Okay, you have a productivity cloud, you have a Salesforce cloud, you may have, everyone has an internal cloud, right? So, but they're not connected. So you can say, okay, it's more than one cloud. So it's, you know, multi-cloud. But super cloud is where you are actually trying to look at this holistically. Whether it is on-prem, whether it is public, whether it's at the edge, it's a store at the branch. You are looking at this as one unit. And that's where we see the term super cloud is more applicable because what are the qualities that you require if you're in a super cloud, right? You need choice of infrastructure, you need, but at the same time you need a single pan or a single platform for you to build your innovations on, regardless of which cloud you're doing it on, right? So I think Super Cloud is actually a more tightly integrated orchestrated management philosophy we think. >>So let's get into some of the super cloud type trends that we've been reporting on. Again, the purpose of this event is as a pilot to get the conversations flowing with, with the influencers like yourselves who are running companies and building products and the builders, Amazon and Azure are doing extremely well. Google's coming up in third Cloudworks in public cloud. We see the use cases on premises use cases. Kubernetes has been an interesting phenomenon because it's become from the developer side a little bit, but a lot of ops people love Kubernetes. It's really more of an ops thing. You mentioned OpenStack earlier. Kubernetes kind of came out of that open stack. We need an orchestration. And then containers had a good shot with, with Docker. They re pivoted the company. Now they're all in an open source. So you got containers booming and Kubernetes as a new layer there. >>What's, >>What's the take on that? What does that really mean? Is that a new defacto enabler? It >>Is here. It's for here for sure. Every enterprise somewhere in the journey is going on. And you know, most companies are, 70 plus percent of them have 1, 2, 3 container based, Kubernetes based applications now being rolled out. So it's very much here. It is in production at scale by many customers. And it, the beauty of it is yes, open source, but the biggest gating factor is the skill set. And that's where we have a phenomenal engineering team, right? So it's, it's one thing to buy a tool and >>Just be clear, you're a managed service for Kubernetes. >>We provide, provide a software platform for cloud acceleration as a service and it can run anywhere. It can run in public private. We have customers who do it in truly multi-cloud environments. It runs on the edge, it runs at this in stores about thousands of stores in a retailer. So we provide that and also for specific segments where data sovereignty and data residency are key regulatory reasons. We also un on-prem as an air gap version. Can >>You give an example on how you guys are deploying your platform to enable a super cloud experience for your customer? Right. >>So I'll give you two different examples. One is a very large networking company, public networking company. They have hundreds of products, hundreds of r and d teams that are building different, different products. And if you look at few years back, each one was doing it on a different platforms, but they really needed to bring the agility. And they worked with us now over three years where we are their build test dev pro platform where all their products are built on, right? And it has dramatically increased their agility to release new products. Number two, it actually is a light out operation. In fact, the customer says like, like the Maytag service person, cuz we provide it as a service and it barely takes one or two people to maintain it for them. >>So it's kinda like an SRE vibe. One person managing a >>Large 4,000 engineers building infrastructure >>On their tools, >>Whatever they want on their tools. They're using whatever app development tools they use, but they use our platform. What >>Benefits are they seeing? Are they seeing speed? >>Speed, definitely. Okay. Definitely they're speeding. Speed uniformity because now they're building able to build, so their customers who are using product A and product B are seeing a similar set of tools that are being used. >>So a big problem that's coming outta this super cloud event that we're, we're seeing and we heard it all here, ops and security teams. Cause they're kind of part of one thing, but option security specifically need to catch up speed wise. Are you delivering that value to ops and security? Right? >>So we, we work with ops and security teams and infrastructure teams and we layer on top of that. We have like a platform team. If you think about it, depending on where you have data centers, where you have infrastructure, you have multiple teams, okay, but you need a unified platform. Who's your buyer? Our buyer is usually, you know, the product divisions of companies that are looking at or the CTO would be a buyer for us functionally cio definitely. So it it's, it's somewhere in the DevOps to infrastructure. But the ideal one we are beginning to see now many large corporations are really looking at it as a platform and saying we have a platform group on which any app can be developed and it is run on any infrastructure. So the platform engineering teams. So >>You working two sides to that coin. You've got the dev side and then >>And then infrastructure >>Side. >>Okay. Another customer that I give an example, which I would say is kind of the edge of the store. So they have thousands of stores. Retail, retail, you know food retailer, right? They have thousands of stores that are on the globe, 50,000, 60,000. And they really want to enhance the customer experience that happens when you either order the product or go into the store and pick up your product or buy or browse or sit there. They have applications that were written in the nineties and then they have very modern AIML applications today. They want something that will not have to send an IT person to install a rack in the store or they can't move everything to the cloud because the store operations has to be local. The menu changes based on it's classic edge. It's classic edge, yeah. Right? They can't send it people to go install rack access servers then they can't sell software people to go install the software and any change you wanna put through that, you know, truck roll. So they've been working with us where all they do is they ship, depending on the size of the store, one or two or three little servers with instructions that >>You, you say little servers like how big one like a box, like a small little box, >>Right? And all the person in the store has to do like what you and I do at home and we get a, you know, a router is connect the power, connect the internet and turn the switch on. And from there we pick it up. >>Yep. >>We provide the operating system, everything and then the applications are put on it. And so that dramatically brings the velocity for them. They manage thousands of >>Them. True plug and play >>Two, plug and play thousands of stores. They manage it centrally. We do it for them, right? So, so that's another example where on the edge then we have some customers who have both a large private presence and one of the public clouds. Okay. But they want to have the same platform layer of orchestration and management that they can use regardless of the locations. >>So you guys got some success. Congratulations. Got some traction there. It's awesome. The question I want to ask you is that's come up is what is truly cloud native? Cuz there's lift and shift of the cloud >>That's not cloud native. >>Then there's cloud native. Cloud native seems to be the driver for the super cloud. How do you talk to customers? How do you explain when someone says what's cloud native, what isn't cloud native? >>Right. Look, I think first of all, the best place to look at what is the definition and what are the attributes and characteristics of what is truly a cloud native, is CNC foundation. And I think it's very well documented, very well. >>Tucan, of course Detroit's >>Coming so, so it's already there, right? So we follow that very closely, right? I think just lifting and shifting your 20 year old application onto a data center somewhere is not cloud native. Okay? You can't put to cloud, not you have to rewrite and redevelop your application in business logic using modern tools. Hopefully more open source and, and I think that's what Cloudnative is and we are seeing a lot of our customers in that journey. Now everybody wants to be cloudnative, but it's not that easy, okay? Because it's, I think it's first of all, skill set is very important. Uniformity of tools that there's so many tools there. Thousands and thousands of tools you could spend your time figuring out which tool to use. Okay? So I think the complexity is there, but the business benefits of agility and uniformity and customer experience are truly being done. >>And I'll give you an example, I don't know how clear native they are, right? And they're not a customer of ours, but you order pizzas, you do, right? If you just watch the pizza industry, how dominoes actually increase their share and mind share and wallet share was not because they were making better pizzas or not, I don't know anything about that, but the whole experience of how you order, how you watch what's happening, how it's delivered. There were a pioneer in it. To me, those are the kinds of customer experiences that cloud native can provide. >>Being agility and having that flow to the application changes what the expectations >>Are >>For the customer. Customer, >>The customer's expectations change, right? Once you get used to a better customer experience, you learn. >>That's to wrap it up. I wanna just get your perspective again. One of the benefits of chatting with you here and having you part of the Super Cloud 22 is you've seen many cycles, you have a lot of insights. I want to ask you, given your career where you've been and what you've done and now let's CEO platform nine, how would you compare what's happening now with other inflection points in the industry? And you've been, again, you've been an entrepreneur, you sold your company to Oracle, you've been seeing the big companies, you've seen the different waves. What's going on right now put into context this moment in time around Super Cloud. >>Sure. I think as you said, a lot of battles. CARSs being been in an asb, being in a real time software company, being in large enterprise software houses and a transformation. I've been on the app side, I did the infrastructure right and then tried to build our own platforms. I've gone through all of this myself with lot of lessons learned in there. I think this is an event which is happening now for companies to go through to become cloud native and digitalize. If I were to look back and look at some parallels of the tsunami that's going on is a couple of paddles come to me. One is, think of it, which was forced to honors like y2k. Everybody around the world had to have a plan, a strategy, and an execution for y2k. I would say the next big thing was e-commerce. I think e-commerce has been pervasive right across all industries. >>And disruptive. >>And disruptive, extremely disruptive. If you did not adapt and adapt and accelerate your e-commerce initiative, you were, it was an existence question. Yeah. I think we are at that pivotal moment now in companies trying to become digital and cloudnative. You know, that is what I see >>Happening there. I think that that e-commerce is interesting and I think just to riff with you on that is that it's disrupting and refactoring the business models. I think that is something that's coming out of this is that it's not just completely changing the gain, it's just changing how you operate, >>How you think and how you operate. See, if you think about the early days of e-commerce, just putting up a shopping cart that made you an e-commerce or e retailer or an e e e customer, right? Or so. I think it's the same thing now is I think this is a fundamental shift on how you're thinking about your business. How are you gonna operate? How are you gonna service your customers? I think it requires that just lift and shift is not gonna work. >>Nascar, thank you for coming on, spending the time to come in and share with our community and being part of Super Cloud 22. We really appreciate, we're gonna keep this open. We're gonna keep this conversation going even after the event, to open up and look at the structural changes happening now and continue to look at it in the open in the community. And we're gonna keep this going for, for a long, long time as we get answers to the problems that customers are looking for with cloud cloud computing. I'm Sean Fur with Super Cloud 22 in the Cube. Thanks for watching. >>Thank you. Thank you. >>Hello and welcome back. This is the end of our program, our special presentation with Platform nine on cloud native at scale, enabling the super cloud. We're continuing the theme here. You heard the interviews Super Cloud and its challenges, new opportunities around solutions around like Platform nine and others with Arlon. This is really about the edge situations on the internet and managing the edge multiple regions, avoiding vendor lock in. This is what this new super cloud is all about. The business consequences we heard and and the wide ranging conversations around what it means for open source and the complexity problem all being solved. I hope you enjoyed this program. There's a lot of moving pieces and things to configure with cloud native install, all making it easier for you here with Super Cloud and of course Platform nine contributing to that. Thank you for watching.

>>Welcome back to super cloud 22, our inaugural event. It's a pilot event here in the cube studios we're live and streaming virtually until we do it in person. Maybe next year. I'm John fury, host of the cube with Dave Lon two great guests, distinguished engineers managers, CTOs investors. Mariana Tessel is a CTO of Intuit ins Ray founder of vertex ventures. Both have a lot of DNA. Founder allow cloud here with mark Andre and Ben Horowitz, a variety of other great ventures you've done. And now you're an investor. Yep. Maria, you've been a seasoned CTO, VP of engineering, VMware Docker Intuit. Now thanks for joining us. >>Absolutely. >>So super cloud is a, is a thing. And apparently it's got a lot of momentum and you guys got stats over there at, at Intuit in, so you're investing and we were challenged on super cloud. Our initial thesis was you build on the clouds, get all that leverage like snowflake, you get a good differentiation and then you compete and then move to other clouds. Now it's becoming a thing where I can do this. Every enterprise could possibly do it. So I want to get your guys thoughts on what you think of super cloud concept and where are the holes in it, what needs to be defined. And so we'll start with you. You've done a lot of cloud things in your day. What >>Do you think? Yeah, it's the whole cloud journey started with a desire to consolidate and desire to actually provide uniformity and, and standards driven ways of doing things. And I think Amazon was a leader there. They helped kind of teach everybody else. You know, when I was in loud cloud, we were trying to do it with proprietary stacks just wouldn't work. But once everyone standardized upon Unix and you know, the chip sets no longer became as relevant. They did a lot of good things there, but what's happened since then is now you've got competing standards at the API layer at the interface layer no longer at the chip set layer, no longer at the operating system layer. Right? So the evolution of the, the, the battles are still there. When you talk about multicloud and super cloud, though, like one of the big things you have to keep in mind is latency is not free. Latency is very expensive and it's getting even more expensive now with, with multi-cloud. So you have to really understand where the separations of boundaries are between your data, your compute, and, and the network is just there as a facilitator to help binding compute and data. Right? And I think there's a lot of bets being made across different vendors like CloudFlare Akamai, as well as Amazon Google Microsoft in terms of how they think we should take computing either to the edge, from the core or back and forth. >>These, this is structural change. I mean, this is structural, >>It's desired by incumbents, but it's not something that I'm seeing from the consumption. I'd love to hear, hear from our end's per perspective, from a consumption point of view, like how much edge computing really matters. Right. >>Mario. >>So I think there's like, there's kind of a, a story of like two, like it's kind of, you can cut it for both edges. No, no pun intended on one end. It is really simplifying to actually go into like a single cloud and standardize on it and just have everything there. But I think what over time companies find is that they end up in multiple clouds, whether like, you know, through acquisitions or through like needing to use a service in another cloud. So you do find yourself in a situation where you have multi multi-cloud and you have to kind of work through it and understand how to make it all like work and latency is an issue, but also for many, many workloads, you can work around it and you can make it work where you have workloads that actually span multiple vendors and clouds. You know, again, having said that, I would say the world is such, that is still a simplifying assumption. When if you go to a single cloud, it's much easier to just go and, and bet on that >>Easier in terms of everything's integrated, IAS works with SAS, they solve a lot of problems. >>Correct. And you can do like for your developers, you can actually provide an environment that's super homogenous, simple. You can use services easily up and down the stack. And, you know, we, we actually made that deliberate decision. When we started migrating to the cloud at the beginning, it was like, oh, let's do like hybrid we'll, you know, make it, so it work anywhere. It was so complicated. It was not worth it. >>When was the, when did you give up, what was the moment? Was there a flash point where you said, oh, this is terrible. This is >>Dead. Yeah. When, when we started to try to make it interoperable and you just see what it requires to do that and the complexity of the architecture that it just became not worth it for the gains you have. >>So speaking obviously as a SAS provider, right. So it just doesn't, it didn't make business case sense for you guys to do that. So it was super cloud. Then an infrastructure thing we just heard from Ben wa deja VI that they're not, they're going beyond instantiating their, their data cloud. They're actually running, you know, their own little snow grid. They called it. And, and then when I asked him, well, what about latency? He said, well, we copied data over, you know, so, okay. That's you have to do, but that's a singular experience with the same governance or the same security. Just wasn't worth it for you guys is what I'm hearing. >>Correct. But again, like for some workload or for some services that we want to use, we are gonna go there and we are gonna then figure out what is the work around the latency issue, whether it's like copy or, you know, redundancy. >>Well, the question I have Dave on snowflake is maybe the question for you and in the panel is snowflake a tan expansion opportunity, or is there a technical reason to go to other clouds? >>I think they wanted to leverage the hyperscale infrastructure globally. And they said that they're out there, it's a free gift. We're gonna go take it. I, I think it started with we're on AWS. Do you think? And then we're on Azure and then we're on Google. And then they said, why don't we just connect all these and make it a singular experience? And yeah, I guess it's a TA expansion as a differentiator and it's, it adds value. Right. If I can share data across that global network, >>We have customers on Azure now, >>Right? Yeah. Yeah. Of course. >>You guys don't need to go CP. What do you think about that? >>Well, I think Snowflake's in a good position cuz they work mostly with analytical workloads and you have capacity. That's always gonna increase like no one subtracts, their analytical workload like ever, right. So there was just compounded growth is like 50% or 80% for, you know, many enterprises despite their best intentions, not to collect more data, they just can't stop doing it. So it's different than if you're like an Oracle or a transactional database where you don't have those, you know, like kind of infinite growth paths. So Snowflake's gonna continue to expand footprint their customers. They don't mind as long as you, they can figure out the, the lowest cost on denominator for, for that. >>Yeah. So it makes sense to be in all the clouds >>For them, for, for them, for sure. Yeah. >>But, but, but Oracle just announced with Microsoft what I would call super cloud, a, a cross cloud database service running on OCI and Azure with very low latency and a database that looks like a, the singular experience. Yeah. With, with a PAs layers >>That lost me after OCI that's >>Okay. You know, but that's the, that's the, the BS answer for all U VCs. The do nobody develops on Oracle? Well, it's a 240 billion market cap company. Show me who you all want be. >>We're gonna talk about SRDF and em C next, you >>All want Oracle. So there we go. You throw that into, you all want Oracle to buy your companies, your funding, you know, cause, cause we all wanna be like Oracle with that kinda cash flow. But, but anyway, >>Here's, here's one thing that I'm noticing that is gonna be really practical. I think for companies that do run SA is because like, you know, you have all these solutions, whether it's like analytics or like monitoring or logging or whatever. And each one of them is very data hungry and all of them have like SAS solutions that end up copy the data, moving data to their cloud, and then they might charge you by the size of your data. It does become kind of overwhelming for companies to use that many tools and basically maybe have that data kind of charge for it, multiple places because you use it for different purposes or just in general, if you have a lot of data, you know, that that is becoming an issue. So that's something that I've noticed in our, in our own kind of, you know, a world, but it's just something that I think companies need to think about how they solve because eventually a lot of companies will say, I cannot have all these solutions, so there's no way I'm gonna be willing to have so many copies of the data and actually pay for that. >>So many times, just something to think about. >>But one of the criticisms of the super cloud concept is that it's just SAS. If I'm running workload on prem and I, and I've got, you know, a connection to the cloud, which you probably do, that's, that's SAS, what's, what's the big deal and that's not anything new or different. So I'd love to get your thoughts on that. But Goldman Sachs, for instance, just announced the service last reinvent with AWS, connecting their tools, their data, and their software from on-prem to AWS, they're offering it as a service. I'm like, Hmm. Kind of looking like Supercloud, but maybe it's just SAS. >>It could be. And like, what I'm talking about is not so much like, you know, like what you wanna connect your data. But the idea is like a lot of the providers of different services, like in the past and, and like higher layer, they're actually COPI the data. They need the data in their cloud or their solution. And it just becomes complicated and expensive is, is kind of like my point. So yes, connecting it like for you to have the data in one place and then be able to connect to it. I think that is a valid, if, if that's kinda what you think about as a super cloud, that is a valid need, I think that companies will >>Have where developers actually want access to tools that might exist. >>Also the key is developers, right? Yeah. Developers decide all decisions, not database on administrators, not, you know, a hundred percent security engineers, not admins. So what's really interesting is where are the developers going next? If you look at the current winners in the current ecosystem, companies like MongoDB, I mean, they capture the minds of yeah. The JavaScript, you know, no JS developers absolutely very early on. And I started catch base and I could tell you like the difference was that capture motion was so important. So developers are basically used to this game-like experience now where they want to see tools that are free, whether it's open source or not, they actually don't care. They just want, and they want it SAS. They want it SAS delivered on demand. Right. And pay as you go. And so there's a lot of these different frameworks coming out next generation, no code, low code, whether it's Java, JavaScript, rust, you know, whatever, you know, go Lang. And there's a lot of people fighting religious wars about how to develop the next kind of modern pattern design pattern. Okay. And that's where a lot of excitement is how we look at like investment opportunities. Like where are those big bets who are, you know, frustrated developers, who are they frustrated, what's wrong with their current environment? You know, do they really enjoy using Kubernetes or trying to use Kubernetes? Yeah. Right. Like developers have a very different view than operator, >>But you mentioned couch base. I mean, I look at couch base what they're doing with Capellas as a form of Supercloud. I mean, I think that's an excellent, they're bringing that out to the edge. We're gonna hear later on from someone from couch base. That's gonna talk about that now. It's kind of a lightweight, you know, sort of, it's gonna be a, a synchronization, but it's the beginning >>A cool new venture deal that I'm not in, but was like duck DB. I'm like, what's duck DB like, well, it's an Emory database that has like this like remote store thing. I'm like, okay, that sounds interesting. Like let's call Mike Olson cuz that sounds like sleepy cat redone red distributed world. But like it's, it's like there's a lot of people refactoring design patterns that we're all grew up with since the popup days of, you know, typical round. Right? >>Yeah. That's the refactory I think that's the big pattern. So I have to ask you guys, what are you guys investing in? We've got a couple minutes left to chat about that. What are you investing at into it from a, from a, a CTO engineering perspective and what are you investing in that feels super cloud like to you? >>Well, the, the thing that like I'm focused on is to make sure that we have absolutely best in the world development environment for our engineers, where it's modern, it's easy to use and it incorporates as many things as we can into that environment. So the engineers don't have to think about it. Like one big example would be security and how we incorporated that into development environment. So again, the engineers don't have to bother with trying to think through how they secure their workloads and every step of the way their other things that we incorporated, whether it's like rollbacks or monitoring or, you know, like baly enough other things. But I think that's really an investment that has panned off for us. We actually started investing in development environment several years ago. We started measure our development velocity and we, it actually went up by six X justly investing. So >>User experience, developer experience and productivity pretty much right. >>Yeah. AB absolutely. Yeah. That's like a big investment area for us that, you know, cloud cloud >>Sounds like super cloudlike factor and I'm assuming it's you're on AWS. >>We are mostly on AWS. Yes. >>And so what are you investing in that from a VC money doling out standpoint? That feels super cloudlike >>So very similar to what we just touched on a lot of developer tool experiences. We have a company that we've invested in called ops level that the service catalogs it's, it's helping, you know, understand your, where your services live and how they could be accessed and, and you know, enterprise kind of that come with that. And then we have a company called Lugo that helps you do serverless debugging container debugging, cuz it turns out debugging distributed, you know, applications is a real problem right now just you can only do so much by log tracing, right? We have a company haven't announced yet that's in the web assembly space. So we're looking at modernizing the next generation past stack and throwing everything out the window, including Java and all of the, you know, current prebuilt components because turns out 90% of enterprise workloads are actually not used. They're they're just policy code. You compiled with they're sitting there as vulnerabilities that no one's actually accessing, but you still have to compile with all of it. So we have a lot of bloatware happening in the enterprise. So we're thinking about how do you skinny that up with the next generation paths that's enterprise capable with security context and frameworks >>Super pass. >>Well, yeah, super pass. That's a kind of good way to, well, is >>It, is it a consistent developer experience across clouds? >>It is. And, and, and, and web assembly is a very raw standard if you can call it that. I mean it's, but it's supported by every modern browser, every major platform, vendor cloud, and Adobe and others, and are using it for their uses. And it's not just about your edge browser compute. It's really, you can take the same framework and compile it down to server side as well as client site, just like JavaScript was a client side tool before it became node. Right. Right. So we're looking at that as a very interesting opportunity. It's very nascent. Yeah. >>Great patterns. Yeah. Well, thanks so much for spending the time outta your busy day. Ariana. Thanks for your commentary. Appreciate your coming on the cubes first in IGUR super cloud event, pilot. Thanks for, for sharing. Thanks for having, thanks for having us. Okay. More coverage here. Super cloud 2022. I'm Jeff David Alane stay with us. We got our cloud ARA panel coming up next.

>>Hey, welcome back everyone. Through the cubes coverage of VMware Explorer, 22, I'm John Fett, Dave ante, formerly world, our 12th year extracting the signal from the noise. A lot of great guests. It's very vibrant right here. The floor's great. The expo halls booming, the keynotes went great. We just had a keynote announce. So our next first guest here on day one is car Capor C co-founder and COO min IO. Welcome to the cube. Thanks for joining us. >>Thank you for having >>Me. You're also angel investor of variety of companies of Q alumnis and been in the valley for a long time. Thanks for coming on sharing. What's going on. So, first of all, obviously VMware still on the wave. They've always been relevant and they've always been part of it. Yes. But as that's changing a lot's going on security data's big conversation. Yeah. And now with their multi-cloud we call super cloud. But their multi-cloud it's it's about hyperscaler participation. Yes. Yes. Cloud universal. Yes. It's clear that VMware has to be successful in every cloud. Okay. And that's really important. And storage is one of it. You guys do that? So talk about how you guys relate with min IO, the vision, how that connects with what's happening here. >>Yeah. So like you already said, right? Most of the enterprises are become data enterprises in itself and storage is a foundation layer of how, and you do need a system that is simple, scalable, and high perform it at scale. Right? So that's where min IO fits into the picture. And we are software defined, open source. So, you know, like VMware has traditionally been focused on enterprise it, but that world is fast changing. They are making a move in terms, developer first approach and min IO, because it's open source. It's simple enough to start, get, start deploying object storage and cloud native applications on top. So that's where we come in. We have around 1.3 million DACA downloads a day. So we own the developer market overall. And that is where I feel the partnership with VMware as they are coming into multi-cloud on their own min IO is a foundational layer. >>So just to elaborate on it, whenever you talk about multi-cloud, there are two pieces to it. One is the compute side and one is on the storage side. So compute Kubernetes takes care of the compute sites. Once you containerize an application, you can deploy it any cloud, but the data has gravity and all the clouds that you see AWS, your Google cloud, they're inherently incompatible with each other. So you need a consistent storage layer with industry standard APIs that you can just deploy it around with your application without a single line of code change. So that's what we >>Do. Oh, so you got a great value proposition, love the story. So just kind of connect on something. So we heard the keynote today. We gotta win the developers. They didn't say that, but they said, they said that they have the ops lockdown, but DevOps is now the new developer. Yes. We've been covering a lot of the poop coupon as you know, and shifting left everyone's in the C I C D pipeline. So developers are driving all the action and it has to be self-service. Absolutely. It has to be high velocity. Can't be slow. Yes. Gotta be fast. So that sounds like you're winning that piece. >>Yes. Yes. And I think more than that, what is most important is it needs to be simple. It needs to get your job done in a very simple and efficient way. And I think that is very important to the developers overall. They don't like complex appliances or complex piece of software. They just want to get their job done and move on the next thing in order to build their application and deploy it successfully. So whatever you do, it needs to be very simple. And of course, you know, it needs to be feature rich and high performant and whatnot that comes with the, with the flow in itself. But I think simplicity is what wins, the developers, hearts and minds overall. >>So object storage always been simple, get put right. Pretty simple, you know, paradigm. Yes. But it was sort of the backwater before, you know, Amazon, you know, launched. Yes. You know, it's cloud. How have you seen object evolve? You mentioned performance. So I presume yes. Yes. You're not just for cheap and deep you're for cheap bin performance. So you could describe that a little bit if you would, >>For, for sure. Like you mentioned, right. When AWS was launched, S3 was the foundation layer. They launched S3 first and then came everything else around it. So object storage is the foundation of any cloud that you go with. And over a period of time, when we started the company back in 20 end of 2014, beginning 2015, it was all about cheap and deep storage. You know, you just get, put it into one basket, but over years, if you see, because the scale of data has increased quite a bit, new applications have emerged as well. That require high performance. That is where we partnered very closely with Intel early on. And I have to give it to them. Intel was the one who convinced us that you need to do high performance. You need to optimize your software with all the AVX five, 12 instruction set and so on. >>So we partnered very closely with them and we were the first one to come up with, you know, you need high performance, object storage and that in collaboration with Intel. So that's something that we take a lot of pride in, in terms of being the leader in that direction of bringing high performance object storage to the market, especially for big data workloads, AI ML, workloads, they're all object first, like even, you know, new age applications like snowflake and data bricks, they are not built on sand or file system. Right. They're all built on object storage rates. So that's where the, you need >>Performance. And I think the, I think the data bricks, snowflake examples. Good. And then you mentioned in 2014, when you started yes. At that time, big data was Hudu and you know, data, legs, data swamp. Yes. Yes. But the ones that were successful, the ones who optimize had the right bets, like you guys. Yeah. Now we're in an era. Okay. I gotta deploy this. So you got great downloads and update from developers. Now we see ops struggling to keep up yes. With the velocity of the development cycle. Yes. And with DevOps driving the cloud native yeah. Security data ops becomes important. Okay. Exactly. Security and data. A lot with storage going on there. Yes. How do you guys see that emerging? Cuz that becomes a lot of the conversations now in the architecture of the ops teams. I want to be supportive in enablement of dev. Yes. Yes. Do you guys target that world too? Or >>Yeah, we, we do target that. So the good thing about object storage is that if you look at the architecture in itself, it's very granular in terms of the controls that it can give to the end user. Right? So you can really customize in terms of, you know, what objects need to be accessible to whom what kind of policies you need to implement on the bucket level, what kind of access controls and provisions that you need to do. And especially like with ransomware attacks and what not, you can enable immutability and so on, so forth. So that's an important part of it. Especially I think the ransomware threats have increased quite a bit, especially with, you know, the macro, you know, situation with war and stuff. So we see that come up quite a bit. And that's where I think, you know, the data IU immutability, the data governance and compliance becomes extremely, extremely important for organizations. So we, we are partnering very closely with a lot of big organizations just for this use case itself. >>So how's it work if I want to build some kind of multi-cloud whatever X, right. Okay. I, I can use S three APIs or Azure blah. Okay. And I, and are all different. Yes. But if I want to use min IO, what's the experience like describe how I go about doing >>So if you've had any experience working with AWS, you don't need to even change a single line of code with us. You can just bring your applications directly onto min IO and it just behaves and act same way transparently what you would've experienced in AWS. Now you can just lift and shift that application and deploy it wherever you need it to be. Whether it is Azure, blah, whether it is Google cloud or even on edge. Like what we are seeing is that data is getting generated outside of public cloud. And most of the data that, you know, the emerging trend is that we see that data gets generated on edge quite a bit, whether it is autonomous cars, whether it is IOT, manufacturing units and so on. And you cannot push all that data back in the central cloud, it's extremely expensive for bandwidth and latency reasons. >>So you need to have an environment that looks and feels exactly what you have experienced at the central cloud on the edge itself. So a lot of our use cases are also getting deployed with Mani on the edge itself, whether it is on top of VMware because of the footprint of that VMware has within all these organizations itself. So we see that emerging quite a bit as well. And then you can tier the data off to any cloud, whether it is mid IO cloud, whether it is AWS, Azure, Google cloud, and so on. So you can have like a true multi-cloud environment. >>So you would follow VMware to the edge and be the object store there, or not necessarily if it's not VMware Kubernetes or whatever. >>Exactly. Exactly. Depending on the skill set that the organization has within, within their setup, if their DevOps savvy Kubernetes is becomes a very natural choice. If they are traditional enterprise, it, VMware is an ideal choice. So yeah. >>So you're seeing a lot of edge action you're saying, and we, >>We, we have seen starting it increasing yes. And >>Are customers. So they're persisting data at the edge. Yes. Yes they >>Are. Okay. >>It's not just the femoral and >>No, they are not because what the cost of putting all the data through bandwidth is extremely expansive to push all the data in central cloud and then process it and then store it. So we see that the data gets persisted on edge cloud as well in terms of processing and only the data that you need for, for the processing through whatever application systems that you, whether it is snowflake or data, bricks and whatnot, you know, you choose what applications from compute side, you want to bring on top of storage. And that can just seamlessly and transparently work. Yeah. >>Maria, you were saying that multi-cloud yeah. Games around Kubernetes. You, yes. That Kubernetes is all about multi-cloud that's the game. >>Yes. >>Yes. Can you explain what you mean by that? Why is multi-cloud a Kubernetes game? >>So multi-cloud has two foundations to it. One is the compute side. Another one is the storage side. Compute Kubernetes makes it extremely simple to deploy any application that is containerized. Once you containerize an application, it's no longer tied to the underlying infrastructure. You can actually deploy it no matter where you go. So Kubernetes makes that task extremely easy. And from storage standpoint, you know, the state of applications need to be held somewhere. You know, it's it, people say it's cloud, but it's computer somewhere. Right? So >>Exactly it's the >>Container. It needs, it needs to be stored somewhere. So that's where, you know, storage systems like man IO come into play where you can just take the storage and deploy it wherever you go. So it gets tightly bound with application itself, just like Kubernetes is for compute. Mano is for storage. >>I saw Scott Johnson, the CEO of Docker in Palo Alto last week did yeah. The spring to his step. So to speak Dockers doing pretty well as a result, they got, you know, starting to see certifications. Yes. So people are really rallying around containers in a more open way. Yes. But that's open source, but it's the Kubernetes, that's the action. Absolutely. That the container's really there now Docker's got a great business. Yes. Right now going yes. With how they're handling. I thought they did a great job. Yeah. But the Docker's now lingua Franco, right? Yes. That's the standard. It >>Is. It is. And I think where Kubernetes really makes it easy is in terms of when the scale is involved. Right. If there are, if the scale is small, it's okay. You can, you can work around it. But Kubernetes makes it extremely simple. If you have the right Kubernetes skill, I just need to put a disclaimer around there because not lot of people are Kubernetes expert, at least not yet. So if you have the expertise, Kubernetes makes the task extremely simple, predictable and automate and automated scale. I think that is what is >>The, so take me through a use case, cuz I've talked to a lot of enterprises, multiple versions, we're lifting and shifting to the cloud, that's kind of the, you know, get started, get your feet wet. Yes. Then there's like, okay, now we're refactoring really doing some native development and they're like, we don't have a staff on Kubernetes. We do a managed service. Yeah. So how does, how do you see that evolution piece taking place? Cause that's a critical adoption component as they start figuring out their Kubernetes relationship yes. To compute yes. How they roll it out. Yes. How do you see that playing out as a big part of this growth for a customer? >>Yeah. So we see a mix, you know, we see organizations that are born within cloud. Like they have just been in mono cloud like AWS. Now they are thinking about two things, right. With the economy being, you know, and the state that it is, they're getting hurt on the margin. Some of the SaaS companies that were born in cloud. So they are now actively thinking in terms of what mode they can do to bring the cost down. So they are partnering with min IO either to, you know, be in a colocation at Equinix, like data centers or go to other clouds to optimize for the compute modes and so on. So that's one thing that we see increasingly amongst enterprise. Second thing that we see is that because you know of that whole multi-cloud and cloud does go down, it's not like it, you know, and it's been evident over the last year or so that, you know, we've seen instances where Amazon was down or Google cloud was down. So they want to make sure that the data is available across the clouds in a consistent way. So with man IO, with the active, active application and so on, you can make the data available across the cloud. So your applications, even if one cloud is down for Dr. Purposes and so on, you can, you know, transparently, move the applications to another cloud and make sure that your business is not affected. So from business continuity reasons as well, the customers are partnering with us. So like I said, it's a mix. >>So the Tansu, you know, 1.3, the application development platform that we heard in the keynotes this morning, critical, you have to have that for cross cloud services. If you don't have a consistent experience, absolutely forget it. I mean it's table stake. Absolutely. But there's a lot of chatter on Twitter. A lot of skepticism that VMware can appeal to developers, some folk John as well chimed in saying, well, you know, it's, don't forget about the op side of the equation as well. They need security and consistency. Yes. What are you seeing in the marketplace in terms of VMware, specifically their customers and, and what do you, what do you, how do you rate their chances in terms of them being able to track the developer crowd, your, your peeps? >>Yeah. So VMware has a very strong hold on enterprise. It, you know, you have to give it to them. I don't come across any organization that does not have VMware, you know, for, with 500,000 customers. Right. Right. So they have done something really right for themselves. And if you have such a strong hold on the customers, it's not that hard to make the transition over to the developer mindset as well. And that is where with VMware partnership with partners like us, they can make, make that jump happen. So we partnered with them very closely for the data persistence layer and they wanted to bring Kubernetes the VMware tan natively to the VSAN interface itself. So we partnered with them, you know, we were their design partner and in, I think, 2020 or something, and we were their launch partner for that platform service. So now through the vCenter itself, you can provision object storage as a service for the developers. So I think they are working in terms of bridging the gap and they have the right mindset. It's all about execution like this. Right. >>They gotta get it >>Justed >>And it's the execution and timing. Exactly. And if they overshoot and the, it shifts over here, you know, this comes up a lot in our conversations. I want to get your reaction to this because I think that's a really great point. You guys are a nice foundational element. Yes. For VMware that plugs into them. That makes everything kind of float for them. Yes. Now we would, we were comparing OpenStack back in the day, how that had so much promise. Yes it did. If you remember, and storage was a big part of that conversation. It, it did. But the one thing that a lot of people didn't factor in on those industry discussions was Amazon was just ramping. Yes. So assuming that the hyper scales aren't stopping, innovating. Yeah. How does the multi-cloud fit with the constant struggles? Cuz abs is not rah multi-cloud cause they're there for the cloud, but customers are using Azure for yeah. Say office productivity teams or whatever, and then they have apps over here and then I'll see on private, private. Right. So hybrids there we get hybrid. Yeah. The clouds aren't changing. Yes. How does that change the dynamics in the market? Because it's a moving train. Some say, >>You know, it is, I would not characterize it like that because you know, AWS strength is that it is AWS, but also that it is not outside of AWS. Right. So it comes with the strengths and weaknesses and same goes for Azure. And same goes for Google cloud where VMware strength lies is the enterprise customers that it has. And I think if they can bridge the gap between the developers, enterprise customers and also the cloud, I think they have a really fair shot at, you know, making sure that the organizations and enterprise have the right experiences in terms of, you know, everyone needs to innovate. There is just no nothing that you can just sit back and relax. Everyone needs to innovate. And I think the good part about VMware is the partnership ecosystem that they have developed over the years and also making sure that their partners are successful along with them. And I think that is, that is going to be a key determining factor in terms of how well and how fast they can execute because nobody can do it alone in, in the enterprise world. So I think that that would be the >>Key, well, gua you're a great guest. Thanks for coming on and sharing you for having perspective on the cube. And obviously you've been on a, this from day 1, 20 15. Yes. I mean that's early and you guys made some great moves. Thank you. In a great position with VMware. Thank you. I like how you're the connective tissue and bridge to developers without a lot of disruption. Right? Real enablement. I think the question is can the VMware customers get there? So congratulations. No, thank you. And we got a couple minutes left. Take a minute to explain what's going on with the company that you co-founded, the team what's going on. Any updates funding very well, well funded. Yeah. How many people do you have? What's new. Are you gonna hire where take a minute to give the plug, give the commercial real quick >>For sure. So we started in 24 15, so it has been like seven, eight years now that we are at it. And I think we've been just very focused with the S3 compatible object storage, being AWS S3 for rest of the world. Like we get characterized at and over the years we've been like now we, we are used 60% in fortune 500 companies in some shape or format. So in terms of the scale and growth, we couldn't be more happier. We are about to touch a billion dollar billion Docker downloads in September. So that's something that we, we are very excited about. And in terms of the funding, we closed the, our series B sometime I think end of December last year and it's a billion dollar valuation and we have great partners in Intel capital and Dell ventures and soft bank. So we couldn't be in a more happier >>Spot. You're a unicorn soon to be decor. Right. >>What's next? Yes. I think, I think what is exciting for us is that the market, we could not be more happier with how the market is coming together with our vision, what we saw in 2015 and how everything is coming together nicely with, from the, the organization, realizing that multi-cloud is the core foundation and strategy of whatever they do next and lot has been accelerated due to COVID as well. Yeah. So in those terms, I think from market and product alignment, we just couldn't be more happier. >>Yeah. We think multi-cloud hybrids here. Steady state multi-cloud is gonna be a reality. Yeah. It becomes super cloud with the new dynamics. And again, David and I were talking last night, storage, networking, compute never goes away, never goes the operating. System's still gonna be out there. Just gonna be looked different and that >>Differently. Yes. I mean, yeah. And like, you know, in 10 years from now, Kubernetes might or might not be there as the foundation for, you know, compute, but storage is something that is always going to be there. People still need to persist the data. People still need a performance data store. People still need something that can scale to hundreds and hundreds of petabytes. So we are here. You bet against data >>As indie gross head once, you know, let chaos rain, rain in the chaos. There you go. Chaos cloud is gonna be simplified. Yeah. That's what innovation looks like. That's, >>That's what it is. >>Thanks for coming on the queue. Appreciate thank you for having me more coverage here. I'm John furrier with Dave Alane. Thanks for watching. More coverage. Three days just getting started. We'll be right back.

>>Hello, everyone. Welcome to the cubes coverage here. New York city for AWS Amazon web services summit 2022. I'm John furrier, host of the cube with Dave ante. My co-host. We are breaking it down, getting an update on the ecosystem. As the GDP drops, inflations up gas prices up the enterprise continues to grow. We're seeing exceptional growth. We're here on the ground floor. Live at the Summit's packed house, 10,000 people. Eric Bradley's here. Chief STR at ETR, one of the premier enterprise research firms out there, partners with the cube and powers are breaking analysis that Dave does check that out as the hottest podcast in enterprise. Eric. Great to have you on the cube. Thanks for coming on. >>Thank you so much, John. I really appreciate the collaboration always. >>Yeah. Great stuff. Your data's amazing ETR folks watching check out ETR. They have a unique formula, very accurate. We love it. It's been moving the market. Congratulations. Let's talk about the market right now. This market is booming. Enterprise is the hottest thing, consumers kind of in the toilet. Okay. I said that all right, back out devices and, and, and consumer enterprise is still growing. And by the way, this first downturn, the history of the world where hyperscalers are on full pumping on all cylinders, which means they're still powering the revolution. >>Yeah, it's true. The hyperscalers were basically at this two sun system when Microsoft and an AWS first came around and everything was orbiting around it. And we're starting to see that sun cool off a little bit, but we're talking about a gradient here, right? When we say cool off, we're not talking to shutdown, it's still burning hot. That's for sure. And I can get it to some of the macro data in a minute, if that's all right. Or do you want me to go right? No, go go. Right. Yeah. So right now we just closed our most recent survey and that's macro and vendor specific. We had 1200 people talk to us on the macro side. And what we're seeing here is a cool down in spending. We originally had about 8.5% increase in budgets. That's cool down is 6.5 now, but I'll say with the doom and gloom and the headlines that we're seeing every day, 6.5% growth coming off of what we just did the last couple of years is still pretty fantastic as a backdrop. >>Okay. So you, you started to see John mentioned consumer. We saw that in Snowflake's earnings. For example, we, we certainly saw, you know, Walmart, other retailers, the FA Facebooks of the world where consumption was being dialed down, certain snowflake customers. Not necessarily, they didn't have mentioned any customers, but they were able to say, all right, we're gonna dial down, consumption this quarter, hold on until we saw some of that in snowflake results and other results. But at the same time, the rest of the industry is booming. But your data is showing softness within the fortune 500 for AWS, >>Not only AWS, but fortune 500 across the board. Okay. So going back to that larger macro data, the biggest drop in spending that we captured is fortune 500, which is surprising. But at the same time, these companies have a better purview into the economy. In general, they tend to see things further in advance. And we often remember they spend a lot of money, so they don't need to play catch up. They'll easily more easily be able to pump the brakes a little bit in the fortune 500. But to your point, when we get into the AWS data, the fortune 500 decrease seems to be hitting them a little bit more than it is Azure and GCP. I >>Mean, we're still talking about a huge business, right? >>I mean, they're catching up. I mean, Amazon has been transforming from owning the developer cloud startup cloud decade ago to really putting a dent on the enterprise as being number one cloud. And I still contest that they're number one by a long ways, but Azure kicking ass and catching up. Okay. You seeing people move to Azure, you got Charlie bell over there, Sean, by former Amazonians, Theresa Carlson, people are going over there, there there's lift over at Azure. >>There certainly is. >>Is there kinks in the arm or for AWS? There's >>A couple of kinks, but I think your point is really good. We need to take a second there. If you're talking about true pass or infrastructure is a service true cloud compute. I think AWS still is the powerhouse. And a lot of times the, the data gets a little muddied because Azure is really a hosted platform for applications. And you're not really sure where that line is drawn. And I think that's an important caveat to make, but based on the data, yes, we are seeing some kinks in the armor for AWS. Yes. Explain. So right now, a first of all caveat, 40% net score, which is our proprietary spending metric across the board. So we're not like raising any alarms here. It's still strong that said there are declines and there are declines pretty much across the board. The only spot we're not seeing a decline at all is in container, spend everything else is coming down specifically. We're seeing it come down in data analytics, data warehousing, and M I, which is a little bit of a concern because that, that rate of decline is not the same with Azure. >>Okay. So I gotta ask macro, I see the headwinds on the macro side, you pointed that out. Is there any insight into any underlying conditions that might be there on AWS or just a chronic kind of situational thing >>Right now? It seems situational. Other than that correlation between their big fortune 500, you know, audience and that being our biggest decline. The other aspect of the macro survey is we ask people, if you are planning to decline spend, how do you plan on doing it? And the number two answer is taking a look at our cloud spend and auditing it. So they're kind say, all right, you know, for the last 10 years it's been drunken, sail or spend, I >>Was gonna use that same line, you know, >>Cloud spend, just spend and we'll figure it out later, who cares? And then right now it's time to tighten the belts a little bit, >>But this is part of the allure of cloud at some point. Yeah. You, you could say, I'm gonna, I'm gonna dial it down. I'm gonna rein it in. So that's part of the reason why people go to the cloud. I want to, I wanna focus in on the data side of things and specifically the database. Let, just to give some context if, and correct me if I'm, I'm a little off here, but snowflake, which hot company, you know, on the planet, their net score was up around 80% consistently. It it's dropped down the last, you know, quarter, last survey to 60%. Yeah. So still highly, highly elevated, but that's relative to where Amazon is much larger, but you're saying they're coming down to the 40% level. Is that right? >>Yeah, they are. And I remember, you know, when I first started doing this 10 years ago, AWS at a 70%, you know, net score as well. So what's gonna happen over time is those adoptions are gonna get less and you're gonna see more flattening of spend, which ultimately is going to lower the score because we're looking for expansion rates. We wanna see adoption and increase. And when you see flattening a spend, it starts to contract a little bit. And you're right. Snowflake also was in the stratosphere that cooled off a little bit, but still, you know, very strong and AWS is coming down. I think the reason why it's so concerning is because a it's within the fortune 500 and their rate of decline is more than Azure right >>Now. Well, and, and one of the big trends you're seeing in database is this idea of converging function. In other words, bringing transaction and analytics right together at snowflake summit, they added the capability to handle transaction data, Mongo DB, which is largely mostly transactions added the capability in June to bring in analytic data. You see data bricks going from data engineering and data science now getting into snowflake space and analytics. So you're seeing that convergence Oracle is converging with my SQL heat wave and their core databases, couch base couch base is doing the same. Maria do virtually all these database companies are, are converging their platforms with the exception of AWS. AWS is still the right tool for the right job. So they've got Aurora, they've got RDS, they've got, you know, a dynamo DV, they've got red, they've got, you know, going on and on and on. And so the question everybody's asking is will that change? Will they start to sort of cross those swim lanes? We haven't seen it thus far. How is that affecting the data >>Performance? I mean, that's fantastic analysis. I think that's why we're seeing it because you have to be in the AWS ecosystem and they're really not playing nicely with others in the sandbox right now that now I will say, oh, Amazon's not playing nicely. Well, no, no. Simply to your point though, that there, the other ones are actually bringing in others at consolidating other different vendor types. And they're really not. You know, if you're in AWS, you need to stay within AWS. Now I will say their tools are fantastic. So if you do stay within AWS, they have a tool for every job they're advanced. And they're incredible. I think sometimes the complexity of their tools hurts them a little bit. Cause to your point earlier, AWS started as a developer-centric type of cloud. They have moved on to enterprise cloud and it's a little bit more business oriented, but their still roots are still DevOps friendly. And unless you're truly trained, AWS can be a little scary. >>So a common use case is I'm gonna be using Aurora for my transaction system and then I'm gonna ETL it into Redshift. Right. And, and I, now I have two data stores and I have two different sets of APIs and primitives two different teams of skills. And so that is probably causing some friction and complexity in the customer base that again, the question is, will they begin to expand some of those platforms to minimize some of that friction? >>Well, yeah, this is the question I wanted to ask on that point. So I've heard from people inside Amazon don't count out Redshift, we're making, we're catching up. I think that's my word, but they were kind of saying that right. Cuz Redshift is good, good database, but they're adding a lot more. So you got snowflake success. I think it's a little bit of a jealousy factor going on there within Redshift team, but then you got Azure synapse with the Synap product synapse. Yep. And then you got big query from Google big >>Query. Yep. >>What's the differentiation. What are you seeing for the data for the data warehouse or the data clouds that are out there for the customers? What's the data say, say to us? >>Yeah, unfortunately the data's showing that they're dropping a little bit whose day AWS is dropping a little bit now of their data products, Redshift and RDS are still the two highest of them, but they are starting to decline. Now I think one of the great data points that we have, we just closed the survey is we took a comparison of the legacy data. Now please forgive me for the word legacy. We're gonna anger a few people, but we Gotter data Oracle on-prem, we've got IBM. Some of those more legacy data warehouse type of names. When we look at our art survey takers that have them where their spend is going, that spends going to snowflake first, and then it's going to Google and then it's going to Microsoft Azure and, and AWS is actually declining in there. So when you talk about who's taking that legacy market share, it's not AWS right now. >>So legacy goes to legacy. So Microsoft, >>So, so let's work through in a little context because Redshift really was the first to take, you know, take the database to the cloud. And they did that by doing a one time license deal with par XL, which was an on-prem database. And then they re-engineered it, they did a fantastic job, but it was still engineered for on-prem. Then you along comes snowflake a couple years later and true cloud native, same thing with big query. Yep. True cloud native architecture. So they get a lot of props. Now what, what Amazon did, they took a page outta of the snowflake, for example, separating compute from storage. Now of course what's what, what Amazon did is actually not really completely separating like snowflake did they couldn't because of the architecture, they created a tearing system that you could dial down the compute. So little nuances like that. I understand. But at the end of the day, what we're seeing from snowflake is the gathering of an ecosystem in this true data cloud, bringing in different data types, they got to the public markets, data bricks was not able to get to the public markets. Yeah. And think is, is struggling >>And a 25 billion evaluation. >>Right. And so that's, that's gonna be dialed down, struggling somewhat from a go to market standpoint where snowflake has no troubles from a go to market. They are the masters at go to market. And so now they've got momentum. We talked to Frank sluman at the snowflake. He basically said, I'm not taking the foot off the gas, no way. Yeah. We, few of our large, you know, consumer customers dialed things down, but we're going balls to the >>Wall. Well, if you look at their show before you get in the numbers, you look at the two shows. Snowflake had their summit in person in Vegas. Data bricks has had their show in San Francisco. And if you compare the two shows, it's clear, who's winning snowflake is blew away from a, from a market standpoint. And we were at snowflake, but we weren't at data bricks, but there was really nothing online. I heard from sources that it was like less than 3000 people. So >>Snowflake was 1900 people in 2019, nearly 10,000. Yeah. In 2020, >>It's gonna be fun to sort of track that as a, as an odd caveat to say, okay, let's see what that growth is. Because in fairness, data, bricks, you know, a little bit younger, Snowflake's had a couple more years. So I'd be curious to see where they are. Their, their Lakehouse paradigm is interesting. >>Yeah. And I think it's >>And their product first company, yes. Their go to market might be a little bit weak from our analysis, but that, but they'll figure it out. >>CEO's pretty smart. But I think it's worth pointing out. It's like two different philosophies, right? It is. Snowflake is come into our data cloud. That's their proprietary environment. They're the, they think of the iPhone, right? End to end. We, we guarantee it's all gonna work. And we're in control. Snowflake is like, Hey, open source, no, bring in data bricks. I mean data bricks, open source, bring in this tool that too, now you are seeing snowflake capitulate a little bit. They announce, for instance, Apache iceberg support at their, at the snowflake summit. So they're tipping their cap to open source. But at the end of the day, they're gonna market and sell the fact that it's gonna run better in native snowflake. Whereas data bricks, they're coming at it from much more of an open source, a mantra. So that's gonna, you know, we'll see who look at, you had windows and you had apple, >>You got, they both want, you got Cal and you got Stanford. >>They both >>Consider, I don't think it's actually there yet. I, I find the more interesting dynamic right now is between AWS and snowflake. It's really a fun tit for tat, right? I mean, AWS has the S three and then, you know, snowflake comes right on top of it and announces R two, we're gonna do one letter, one number better than you. They just seem to have this really interesting dynamic. And I, and it is SLT and no one's betting against him. I mean, this guy's fantastic. So, and he hasn't used his war chest yet. He's still sitting on all that money that he raised to your point, that data bricks five, their timing just was a little off >>5 billion in >>Capital when Slootman hasn't used that money yet. So what's he gonna do? What can he do when he turns that on? He finds the right. >>They're making some acquisitions. They did the stream lit acquisitions stream. >>Fantastic >>Problem. With data bricks, their valuation is underwater. Yes. So they're recruiting and their MNAs. Yes. In the toilet, they cannot make the moves because they don't have the currency until they refactor the multiple, let the, this market settle. I I'm, I'm really nervous that they have to over factor the >>Valuation. Having said that to your point, Eric, the lake house architecture is definitely gaining traction. When you talk to practitioners, they're all saying, yeah, we're building data lakes, we're building lake houses. You know, it's a much, much smaller market than the enterprise data warehouse. But nonetheless, when you talk to practitioners that are actually doing things like self serve data, they're building data lakes and you know, snow. I mean, data bricks is right there. And as a clear leader in, in ML and AI and they're ahead of snowflake, right. >>And I was gonna say, that's the thing with data bricks. You know, you're getting that analytics at M I built into it. >>You know, what's ironic is I remember talking to Matt Carroll, who's CEO of auDA like four or five years ago. He came into the office in ma bro. And we were in temporary space and we were talking about how there's this new workload emerging, which combines AWS for cloud infrastructure, snowflake for the simple data warehouse and data bricks for the ML AI, and then all now all of a sudden you see data bricks yeah. And snowflake going at it. I think, you know, to your point about the competition between AWS and snowflake, here's what I think, I think the Redshift team is, you know, doesn't like snowflake, right. But I think the EC two team loves it. Loves it. Exactly. So, so I think snowflake is driving a lot of, >>Yeah. To John's point, there is plenty to go around. And I think I saw just the other day, I saw somebody say less than 40% of true global 2000 organizations believe that they're at real time data analytics right now. They're not really there yet. Yeah. Think about how much runway is left and how many tools you need to get to real time streaming use cases. It's complex. It's not easy. >>It's gonna be a product value market to me, snowflake in data bricks. They're not going away. Right. They're winning architectures. Yeah. In the cloud, what data bricks did would spark and took over the Haddo market. Yeah. To your point. Now that big data, market's got two players, in my opinion, snow flicking data, bricks converging. Well, Redshift is sitting there behind the curtain, their wild card. Yeah. They're wild card, Dave. >>Okay. I'm gonna give one more wild card, which is the edge. Sure. Okay. And that's something that when you talk about real time analytics and AI referencing at the edge, there aren't a lot of database companies in a position to do that. You know, Amazon trying to put outposts out there. I think it runs RDS. I don't think it runs any other database. Right. Snowflake really doesn't have a strong edge strategy when I'm talking the far edge, the tiny edge. >>I think, I think that's gonna be HPE or Dell's gonna own the outpost market. >>I think you're right. I'll come back to that. Couch base is an interesting company to watch with Capella Mongo. DB really doesn't have a far edge strategy at this point, but couch base does. And that's one to watch. They're doing some really interesting things there. And I think >>That, but they have to leapfrog bongo in my >>Opinion. Yeah. But there's a new architecture emerging at the edge and it's gonna take a number of years to develop, but it could eventually from an economic standpoint, seep back into the enterprise arm base, low end, take a look at what couch base is >>Doing. They hired an Amazon guard system. They have to leapfrog though. They need to, they can't incrementally who's they who >>Couch >>Base needs to needs to make a big move in >>Leap frog. Well, think they're trying to, that's what Capella is all about was not only, you know, their version of Atlas bringing to the cloud couch base, but it's also stretching it out to the edge and bringing converged database analytics >>Real quick on the numbers. Any data on CloudFlare, >>I was, I've been sitting here trying to get the word CloudFlare out my mouth the whole time you guys were talking, >>Is this another that's innovated in the ecosystem. So >>Platform, it was really simple for them early on, right? They're gonna get that edge network out there and they're gonna steal share from Akamai. Then they started doing exactly what Akamai did. We're gonna start rolling out some security. Their security is fantastic. Maybe some practitioners are saying a little bit too much, cuz they're not focused on one thing or another, but they are doing extremely well. And now they're out there in the cloud as well. You >>Got S3 compare. They got two, they got an S3 competitor. >>Exactly. So when I'm listening to you guys talk about, you know, a, a couch base I'm like, wow, those two would just be an absolute fantastic, you know, combination between the two of them. You mean >>CloudFlare >>Couch base. Yeah. >>I mean you got S3 alternative, right? You got a Mongo alternative basically in my >>Opinion. And you're going and you got the edge and you got the edge >>Network with security security, interesting dynamic. This brings up the super cloud date. I wanna talk about Supercloud because we're seeing a trend on we're reporting this since last year that basically people don't have to spend the CapEx to be cloud scale. And you're seeing Amazon enable that, but snowflake has become a super cloud. They're on AWS. Now they're on Azure. Why not tan expansion expand the market? Why not get that? And then it'll be on Google next, all these marketplaces. So the emergence of this super cloud, and then the ability to make that across a substrate across multiple clouds is a strategy we're seeing. What do you, what do you think? >>Well, honestly, I'm gonna be really Frank here. The, everything I know about the super cloud I know from this guy. So I've been following his lead on this and I'm looking forward to you guys doing that conference and that summit coming up from a data perspective. I think what you're saying is spot on though, cuz those are the areas we're seeing expansion in without a doubt. >>I think, you know, when you talk about things like super cloud and you talk about things like metaverse, there's, there's a, there, there look every 15 or 20 years or so this industry reinvents itself and a new disruption comes out and you've got the internet, you've got the cloud, you've got an AI and VR layer. You've got, you've got machine intelligence. You've got now gaming. There's a new matrix, emerging, super cloud. Metaverse there's something happening out there here. That's not just your, your father's SAS or is or pass. Well, >>No, it's also the spend too. Right? So if I'm a company like say capital one or Goldman Sachs, my it spend has traditionally been massive every year. Yes. It's basically like tons of CapEx comes the cloud. It's an operating expense. Wait a minute, Amazon has all the CapEx. So I'm not gonna dial down my budget. I want a competitive advantage. So next thing they know they have a super cloud by default because they just pivoted their, it spend into new capabilities that they then can sell to the market in FinTech makes total sense. >>Right? They're building out a digital platform >>That would, that was not possible. Pre-cloud >>No, it wasn't cause you weren't gonna go put all that money into CapEx expenditure to build that out. Not knowing whether or not the market was there, but the scalability, the ability to spend, reduce and be flexible with it really changes that paradigm entire. >>So we're looking at this market now thinking about, okay, it might be Greenfield in every vertical. It might have a power law where you have a head of the long tail. That's a player like a capital one, an insurance. It could be Liberty mutual or mass mutual that has so much it and capital that they're now gonna scale it into a super cloud >>And they have data >>And they have the data tools >>And the tools. And they're gonna bring that to their constituents. Yes, yes. And scale it using >>Cloud. So that means they can then service the entire vertical as a service provider. >>And the industry cloud is becoming bigger and bigger and bigger. I mean, that's really a way that people are delivering to market. So >>Remember in the early days of cloud, all the banks thought they could build their own cloud. Yeah. Yep. Well actually it's come full circle. They're like, we can actually build a cloud on top of the cloud. >>Right. And by the way, they can have a private cloud in their super cloud. Exactly. >>And you know, it's interesting cause we're talking about financial services insurance, all the people we know spend money in our macro survey. Do you know the, the sector that's spending the most right now? It's gonna shock you energy utilities. Oh yeah. I was gonna, the energy utilities industry right now is the one spending the most money I saw largely cuz they're playing ketchup. But also because they don't have these type of things for their consumers, they need the consumer app. They need to be able to do that delivery. They need to be able to do metrics. And they're the they're, they're the one spending right >>Now it's an arms race, but the, the vector shifts to value creation. So >>It's it just goes back to your post when it was a 2012, the trillion dollar baby. Yeah. It's a multi-trillion dollar baby that they, >>The world was going my chassis post on Forbes, headline trillion dollar baby 2012. You know, I should add it's happening. That's >>On the end. Yeah, exactly. >>Trillions of babies, Eric. Great to have you on the key. >>Thank you so much guys. >>Great to bring the data. Thanks for sharing. Check out ETR. If you're into the enterprise, want to know what's going on. They have a unique approach, very accurate in their survey data. They got a great market basket of, of, of, of, of data questions and people and community. Check it out. Thanks for coming on and sharing with. >>Thank you guys. Always enjoy. >>We'll be back with more coverage here in the cube in New York city live at summit 22. I'm John fur with Dave ante. We'll be right back.

>>Good morning from New York city, Lisa Martin and John furrier with the cube. We are at AWS summit NYC. This is a series of summits this year, about 15 summit globally. And we're excited to be here, John, with about 10,000 folks. >>It's crowded. New York is packed big showing here at 80 of us summit. So it's super exciting, >>Super exciting. Just a little bit before the keynote. And we have our first guest, Kevin Farley joins us the director of strategic alliances at Maria DB. Kevin, welcome to >>The program. Thank you very much. Appreciate you guys having us. >>So all of us out from California to NYC. Yeah, lots of eyes. We got keynote with Warner Vogels coming up. We should be some good news, hopefully. Yep. But talk to us about Maria DB Skys cloud native version released a couple years ago. What's going on? >>Yeah, well, it's, you know, Skys SQL for us is really a be on the future. I think when we think about like the company's real mission is it's just creating a database for everyone. It's it's any cloud, any scale, um, any size of performance and really making sure that we're able to deliver on something that really kind of takes advantage of everything we've done in the market to date. If you think about it, there's not very many startups that have a billion downloads and 75% of the fortune 500 already using our service. So what we're really thinking about is how do we bridge that gap? How do we create a natural path for all of these customers? And if you think about not just Maria DB, but anyone else using the sequel query language, all the, my people, what I think most Andy jazzy TK, anyone says, you know, it's about 10% of the market currently is in the clouds. That's 90% of a total addressable market that hasn't done it yet. So creating cloud modernization for us, I think is just a huge opportunity. Do >>You guys have a great history with AWS? I want to just step back, you mentioned some stats on, on success. Can you scope the size and track record of Maria DB for us real quick and set the table? Because I think there's a bigger picture going on that we've been tracking for the past 13 years we address is the role of the database has always been one of those things where they didn't believe a one database fits all things, right. You guys have been part of that track record scope, the size and scale of Maria DB, the usage, the use cases and some of the successes. >>Yeah. I mean, like I said, some of the stats are already threw out there. So, you know, it is pervasive, I think is the best way to put it. I think what you look at what the database market really became is very siloed. Right? I think there was a lot of unique solutions that were built and delivered that had promise, but they also had compromise. And I think once you look at the landscape of a lot of fortune 500 companies, they have probably 10 to 15 different database solutions, right? And they're all doing unique things. They're difficult to manage. They're very costly. So what Marie DB is always kind of focused on is how do we continue to build more and more functionality into the database itself and allow that to be a single source of truth where application developers can seamlessly integrate applications. >>So then the theme of this event in New York city, which is scale dot, dot, dot, anything must align quite well with Maria and your >>Objectives. I mean, honestly, I think when I think of the problems that most database, um, companies, um, face customers, I should say it, it really comes down to performance and scale. Most of them like Maria DB, like you said, they it's like the car, you know, and love you've been driving it for years. You're an expert at it. It works great, but it doesn't have enough range. It doesn't go fast enough. It's hitting walls. That modern data requirements are just breaking. So scale for me is the favorite thing to talk about because what we launched as MariaDB expand, which is a plugable storage engine that is integrated into Skye, and it really gives you dynamic scale. So you can scale in, you can scale out, it's not costly compute to try to get for seasonality. So you can make your black Friday numbers. It's really about the dexterity to be able to come in and out as you need in a share, nothing architecture with full failover sale healing, high availability, married to the cloud for full cloud scale. And that's really the beauty of the AWS partnership. >>Can you elaborate a bit more on the partnership? How long have you guys been partners? Where is it now anything exciting coming out? >>Yeah, it it's, it's actually been a wonderful ride. They've really invested from the very beginning we went for the satisfactory. So they really brought a lot of resources to bear. And I think if you're looking at why it works, um, it's probably two things. I think the number one thing is that we share one of the core tenants and it's customer obsession in a, in a, in an environment where there is co-opetition right. You have to find paths for how do you get the best thing for the customer? And the second is pretty obvious, but if you look at any major cloud, their number one priority is getting large mission critical workloads into their cloud because the revenue is exponential on the backside. So what do we own? Large mission critical workloads. So if you marry that objective with AWS, the partnership is absolutely perfect for driving true revenue, growth scale, and, and revenue across, across both entities in the partner ecosystem. >>So Kevin talk about the, um, the hybrid strategy, cuz you're seeing cloud operations. Yep. Go hybrid. Amazon announced AWS announced outpost like four years ago. Right now edge is super hot. Yeah. So you're seeing like most of the enterprise is saying mm-hmm <affirmative> okay. Love cloud love the cloud database, but I got the on-prem hybrid cloud operations. Right. So it's not just proprietary operations. It's cloud ops. Yeah. How do you guys fit into that? What's the story. >>We, we actually it's. I mean, there's, there's all these new deliverables outposts, you know, come out with a promise. What we have is a reality right now, um, one of the largest, um, networking companies, which I can't mention yet publicly, um, we want a really big sky SQL deal, but what they had manufacturing plants, they needed to have on-prem deployments. So Maria DB naturally syncs with sky SQL. It's the same technology. It works in perfect harmony. So we really already deliver on the promise of hybrid, but of course there's a lot more we can grow in that area. And certainly thinking about app posts and other solutions, um, is definitely on the, the longer term roadmap of what could make sense for in our customer. What, >>What are some of the latest things that, that you guys are doing now that you weren't doing a few years ago that customers should know about the audience should know about? >>I mean, I think the game changer, we're always innovating. I mean, when you're the company that writes the code owns the code, you know, we can do hot fixes, we can do security patches, we can always do the things that give you real time access to what you need. But I think the game changer is what I mentioned a little bit earlier. And I think it's really the, the holy grail of the cloud. It's like, how can we take the, the SQL query language, which is well over 50% of the open source market. Right. And how do we convert that seamlessly into the cloud? How do we help you modernize on that journey? And expand gives you the ability to say, I can be the small, I can be a small startup. I got my C round. I don't wanna manage databases. I can use the exact same service as the largest fortune 100 company that has massive global scale and needs to be able to drive that across globe. Yeah. So I think that's the beauty is that it's really a democratization of the database, >>At least that, you know, we've been covering the big data space for 10 years. Remember all those different conversations had do those days and oh, they have big data and right. But then it's like too hard to set up. Then you had that kind of period where you saw a spark and data lakes emerge. Yeah. Then you, now it almost seems, seems like now more than ever, there's a data revolutions back. Right. It was almost like a lull in the, in, in the, in the market a little bit. Yeah. I'm gonna democratize data science right now. You got data. So now it just seems to be an explosion at that level. What's your analysis on that? Because you you've been in, in, in the weeds and in the, in the, in this market for 10 years. Yeah. And nothing really changed. It's just now it's more ready. Yeah. I think what's your observation. Why >>Is that? I think that's a really good question. And I love it cuz I mean, what the promise of things like could do and net new technologies sort of, it was always out there, but it required this whole net new lift and how do I do it? How do I manage it? How do I optimize it? The beauty of what we can do with Maria DB is that sky SQLs, which you already know and love. Right? And now we can Del you can deliver a data lake on S3, right? You can pull that data. And we also have the ability to do both analytical data and transactional data from the same database. So you can write applications that can pull column, store data up into, um, your application, but you can also have all of your asset transactions, which are absolutely required for all of your mission critical business. So I think that we're seeing more and more adoption. You've seen other companies start to talk about bringing the different elements in, but we're the only ones that really >>Do it and SQL standardizing that front end. Yeah. Even better than ever before. All the stuff under the covers is all being connected. >>That's the awesome part is right. Is you're literally doing what you already know how to do, but you blow it out on the back end, married to the cloud. And that I think is the real revolution of what makes usability real in the data space. And I think that's what was always the problem before >>When you're in partner conversations, you mentioned co-opetition. Yeah. <laugh> so I think when you're in partner conversations and customer conversations, there is a lot of the, the there's a lot of competition out there. Absolutely. Everyone's got their own key messages. What are the key differentiators that you're saying AWS Marie to be together better? And here's why, >>Yeah. I, I think that certainly you, you start with the global footprint of AWS, right? So what we rely on the most is having the ability to truly deal with global customers in availability zones, they're gonna optimize performance from them. But then when we look at what we do that really changes the game, it comes down to scale and performance. We actually just ran, um, a suspense test against cockroach that also does distributed sequel. Absolutely. You know, the results were off the chart. So we went public and said, we have an open challenge. Anyone that wants to try to beat, um, expand and Skye will we'll if you can, we'll put $25,000 towards charity. So we really are putting our money where our mouth is on that challenge. So we believe the performance cuz we've seen it and we know it's real, but then it's really always about data scale. Modern data requirements are breaking the mold of charting. They're breaking the mold of all these bandaids that people have put in these traditional services. And we give them future. We, we feature proof their investments, so they can say, Hey, I can start here. But if I end up being a startup that becomes Airbnb, I'm already built to blow it out on the back end. I can already use what I have. >>Speaking of startups, being the next Airbnb. If you look at behind us here, you can see, this is a really packed event in New York city events are back, but the ecosystem here is even flourishing. So Dave and I and Lisa were observing that we're still kind of in a growth mode, big time. So yeah, there's some market forces headwinds for the big unicorns, overfunded, you know, public companies, maybe the valuations are a little bit off, but there's still a surge of new innovations, new companies coming out of this. Um, and it's all around data and scale. It's all around new names. We've never heard of. Absolutely. What's your take on >>Reaction? Well, actually another awesome segues cuz in addition to the public clouds, I manage the ecosystem. And one of the things that we've really been focused on with Skys SQL is making it accessible API accessible. So if you're a company that has a huge Marine DB footprint change data capture might be the most important thing for you to say, we wanna do this, but we want you to stay in sync with our environments. Um, things like monitoring, things like BI, all of these are ecosystem plays and current partners that we have, um, that we really think about how do you holistically look at not only the database and what it can do, but how does it deliver value to different segments of your customer base or just your employee base that are using that stuff? So I think that's huge for us. >>Well, you know, one of the things that we talk often about is that every company, these days, regardless of industry, has to be a data company. Yep. You've gotta be able to access the data glean insights from an act on it quickly, whether it's manufacturing, retail, healthcare, are there any verticals in where Maria DB really excels? >>Um, so certainly we Excel in areas like financial services is huge DBS bank. Um, in APAC, one of our biggest customers, also one of the largest Oracle migrations, probably the, that we've ever done. A lot of people trying to get off Oracle, we make it seamless to get into Maria DB. Um, you can think about Samsung cloud and another, their entire consumer cloud is built on Maria DB, why it's integrated with expand right seasonality. So there's customers like that that really bring it home for us as far as ServiceNow tech sector. Right? So these are all different ones, but I think we're really strong in those >>Areas. So this brings up a good point. Dave and I a coined a term called super cloud at reinvent and Lisa and Dave were at multiple events we're together at events. And so a lot of people are getting behind this cuz it's multi-cloud sounds like something's broken. Yes. But so we call it super cloud because customers are building on top of ecosystems like Maria DB and others. Yeah. Not just AWS SOS does all the CapEx absolutely provide the value. So now people are having this new super cloud moment. We' saying we can get all the benefits of cloud scale mm-hmm <affirmative> without actually being a cloud. Right. So this is where the next gen layer comes. What's your reaction to, to super cloud. Do you think it's a thing? >>Well, I think it's a thing in the sense, from our perspective as an ISV, we're, we're laser focused on making sure that we support any cloud and we have a truly multicloud cloud platform. But the beauty of that as well is from a single UI, you're able to deploy databases in different clouds underneath that you're not looking at so you can have performance proximity, but you're still driving it through the same Skys UI. So for us it's, it's unequivocally true. Got it. And I think it's only ISVs like Maria DB that can deliver on that value because >>You're enabling, >>We're enabling it. Right. We partner, we build on top of everything. Right. So we can access everything underneath >>And they can then build on top of you. >>Sure, exactly. And that's exactly where it goes. Right? Yeah. So that, I think in that sense, the super cloud is actually already somewhat real. >>It's interesting. You look at the old, it spend, you take a big company. I won't say a name, but a leader in a, a vertical, they have such a big spend. Now they can leverage that spend in with the super cloud model. They then could become a service provider in the vertical. Absolutely capital one S doing it. Yeah. You're seeing, um, Goldman Sachs doing it. They have the power on the spend that they're leveraging in for their business and servicing their vertical and the smaller players. Do you see that trend? >>Well, I think that's the reality is that everyone is getting this place where if you're talking about sort of this broader super concept, you're talking about global scale, right? That's if in order to deliver a backbone that can service that model, you have to have the right data structure and the right database footprint to be able to scale. And I think that's what they all need to be able to do. And that's what we're really well positioned with Skys >>To enable companies, as we talked about a minute ago to truly become data companies. Yeah. And to be competitive and to scale on their own, where are your customer conversations? Are they at the C-suite level? Has that changed in the last couple of years? >>Uh, that's actually a really great way to state that question because I think you would've traditionally probably talked more to, um, the DBAs, right? They're the people that are having headaches. They're having problems. They're, they're trying to solve. We see a lot of developers now tons, right? They're thinking about, I have this, I have this new thing that I need to do to deliver this new application. And here's the requirements and the current model's broken. It doesn't optimize that it's a lot of work and it's hard to manage. So I think that we're in a great position to be able to take that to that next phase and deliver. And then of course, as you get deeper in with AWS, you're talking about, you know, CIO level, CISO level, they're they need to understand how do you fit into our larger paradigm. And many of these guys have, you know, hundreds of million dollar commits with AWS. So they think of their investment in the sense of the cloud stack. And we're part of that cloud stack, just like AWS services. So those conversations continue to happen certainly with our larger customers, cuz it truly is married. >>It is. And they continue to evolve. Kevin, thank you so much >>For joining. You're welcome. Great, >>John and me talking about what's going on with Maria >>D. Thank you, John. Thank you, Lisa. On behalf of Maria B, it was wonderful. Really >>Appreciate it. Fantastic as well for John furrier. I'm Lisa Martin. You're watching the cube live from New York city at AWS summit NYC, John and I we're back with our next guest in a minute.

from the cube studios in palo alto in boston bringing you data driven insights from the cube and etr this is breaking analysis with dave vellante earnings season has shown a conflicting mix of signals for software companies well virtually all firms are expressing caution over so-called macro headwinds we're talking about ukraine inflation interest rates europe fx headwinds supply chain just overall i.t spend mongodb along with a few other names appeared more sanguine thanks to a beat in the recent quarter and a cautious but upbeat outlook for the near term hello and welcome to this week's wikibon cube insights powered by etr in this breaking analysis ahead of mongodb world 2022 we drill into mongo's business and what etr survey data tells us in the context of overall demand and the patterns that we're seeing from other software companies and we're seeing some distinctly different results from major firms these days we'll talk more about [ __ ] in this session which beat eps by 30 cents in revenue by more than 18 million dollars salesforce had a great quarter and its diversified portfolio is paying off as seen by the stocks noticeable uptick post earnings uipath which had been really beaten down prior to this quarter it's brought in a new co-ceo and it's business is showing a nice rebound with a small three cent eps beat and a nearly 20 million dollar top line beat crowdstrike is showing strength as well meanwhile managements at microsoft workday and snowflake expressed greater caution about the macroeconomic climate and especially on investors minds his concern about consumption pricing models snowflake in particular which had a small top-line beat cited softness and effects from reduced consumption especially from certain consumer-facing customers which has analysts digging more deeply into the predictability of their models in fact barclays analyst ramo lenchow published an especially thoughtful piece on this topic concluding that [ __ ] was less susceptible to consumption headwinds than for example snowflake essentially for a few reasons one because atlas mongo's cloud managed service which is the consumption model comprises only about 60 percent of mongo's revenue second is the premise that [ __ ] is supporting core operational applications that can't be easily dialed down or turned off and three that snowflake customers it sounds like has a more concentrated customer base and due to that fact there's a preponderance of its revenue is consumption driven and would be more sensitive to swings in these consumption patterns now i'll say this first consumption pricing models are here to stay and the much preferred model for customers is consumption the appeal of consumption is i can actually dial down turn off if i need to and stop spending for a while which happened or at least happened to a certain extent this quarter for certain companies but to the point about [ __ ] supporting core applications i do believe that over time you're going to see the increased emergence of data products that will become core monetization drivers in snowflake along with other data platforms is going to feed those data products and services and become over time maybe less susceptible and less sensitive to these consumption patterns it'll always be there but i think increasingly it's going to be tied to operational revenue last two points here in this slide software evaluations have reverted to their historical mean which is a good thing in our view we've taken some air out of the bubble and returned to more normalized valuations was really predicted and looked forward to look we're still in a lousy market for stocks it's really a bear market for tech the market tends to be at least six months ahead of the economy and often not always but often is a good predictor we've had some tough compares relative to the pandemic days in tech and we'll be watching next quarter very closely because the macro headwinds have now been firmly inserted into the guidance of software companies okay let's have a look at how certain names have performed relative to a software index benchmark so far this year here's a year-to-date chart comparing microsoft salesforce [ __ ] and snowflake to the igv software heavy etf which is shown in the darker blue line which by the way it does not own the ctf does not own snowflake or [ __ ] you can see that these big super caps have fared pretty well whereas [ __ ] and especially snowflake those higher growth companies have been much more negatively impacted year to date from a stock price standpoint now let's move on let's take a financial snapshot of [ __ ] and put it next to snowflake so we can compare these two higher growth names what we've done here in this chart has taken the most recent quarters revenue and multiplied it by 4x to get a revenue run rate and we've parenthetically added a projection for the full year revenue [ __ ] as you see will do north of a billion dollars in revenue while snowflake will begin to approach three billion dollars 2.7 and run right through that that four quarter run rate that they just had last quarter and you can see snowflake is growing faster than [ __ ] at 85 percent this past quarter and we took now these most of these profit of these next profitability ratios off the current quarter with one exception both companies have high gross margins of course you'd expect that but as we've discussed not as high as some traditional software companies in part because of their cloud costs but also you know their maturity or lack thereof both [ __ ] and snowflake because they are in high growth mode have thin operating margins they spend nearly half or more than half of their revenue on growth that's the sg a line mostly the s the sales and marketing is really where they're spending money uh and and they're specialists so they spend a fair amount of their revenue on r d but maybe not as high as you might think but a pretty hefty percentage the free cash flow as a percentage of revenue line we calculated off the full year projections because there was a kind of an anomaly this quarter in the in the snowflake numbers and you can see snowflakes free cash flow uh which again was abnormally high this quarter is going to settle in around 16 this year versus mongo's six percent so strong focus by snowflake on free cash flow and its management snowflake is about four billion dollars in cash and marketable securities on its balance sheet with little or no debt whereas [ __ ] has about two billion dollars on its balance sheet with a little bit of longer term debt and you can see snowflakes market cap is about double that of mongos so you're paying for higher growth with snowflake you're paying for the slootman scarpelli execution engine the expectation there a stronger balance sheet etc but snowflake is well off its roughly 100 billion evaluation which it touched during the peak days of tech during the pandemic and just that as an aside [ __ ] has around 33 000 customers about five times the number of customers snowflake has so a bit of a different customer mix and concentration but both companies in our view have no lack of market in terms of tam okay now let's dig a little deeper into mongo's business and bring in some etr data this colorful chart shows the breakdown of mongo's net score net score is etr's proprietary methodology that measures the percent of customers in the etr survey that are adding the platform new that's the lime green at nine percent existing customers that are spending six percent or more on the platform that's the forest green at 37 spending flat that's the gray at 46 percent decreasing spend that's the pinkish at around 5 and churning that's only 3 that's the bright red for [ __ ] subtract the red from the greens and you net out to a 38 which is a very solid net score figure note this is a survey of 1500 or so organizations and it includes 150 mongodb customers which includes by the way 68 global 2000 customers and they show a spending velocity or a net score of 44 so notably higher among the larger clients and while it's a smaller sample only 27 emea's net score for [ __ ] is 33 now that's down from 60 last quarter note that [ __ ] cited softness in its european business on its earning calls so that aligns to the gtr data okay now let's plot [ __ ] relative to some other data platforms these don't all necessarily compete head to head with [ __ ] but they are in data and database platforms in the etr data set and that's what this chart shows it's an xy graph with net score or as we say spending momentum on the vertical axis and overlap or presence or pervasiveness in the data set on the horizontal axis see that red dotted line there at 40 that indicates an elevated level of spending anything above that is highly elevated we've highlighted [ __ ] in that red box which is very close to that 40 percent line it has a pretty strong presence on the x-axis right there with gcp snowflake as we've reported has come down to earth but still well elevated again that aligns with the earnings releases uh aws and microsoft they have many data platforms especially aws so their plot position reflects their broad portfolio massive size on the x-axis um that's the presence and and very impressive on the vertical axis so despite that size they have strong spending momentum and you can see the pack of others including cockroach small on the verdict on the horizontal but elevated on the vertical couch base is creeping up since its ipo redis maria db which was launched the day that oracle bought sun and and got my sequel and some legacy platforms including the leader in database oracle as well as ibm and teradata's both cloud and on-prem platforms now one interesting side note here is on mongo's earning call it clearly cited the advantages of its increasingly all-in-one approach relative to others that offer a portfolio of bespoke or what we some sometimes call horses for courses databases [ __ ] cited the advantages of its simplicity and lower costs as it adds more and more functionality this is an argument often made by oracle and they often target aws as the company with too many databases and of course [ __ ] makes that argument uh as well but they also make the argument that oracle they don't necessarily call them out but they talk about traditional relational databases of course they're talking about oracle and others they say that's more complex less flexible and less appealing to developers than is [ __ ] now oracle of course would retur we retort saying hey we now support a mongodb api so why go anywhere else we're the most robust and the best for mission critical but this gives credence to the fact that if oracle is trying to capture business by offering a [ __ ] api for example that [ __ ] must be doing something right okay let's look at why they buy [ __ ] here's an etr chart that addresses that question it's it's mongo's feature breadth is the number one reason lower cost or better roi is number two integrations and stack alignment is third and mongo's technology lead is fourth those four kind of stand out with notice on the right hand side security and vision much lower there in the right that doesn't necessarily mean that [ __ ] doesn't have good security and and good vision although it has been cited uh security concerns um and and so we keep an eye on that but look [ __ ] has a document database it's become a viable alternative to traditional relational databases meaning you have much more flexibility over your schema um and in fact you know it's kind of schema-less you can pretty much put anything into a document database uh developers seem to love it generally it's fair to say mongo's architecture would favor consistency over availability because it uses a single master architecture as a primary and you can create secondary nodes in the event of a primary failure but you got to think about that and how to architect availability into the platform and got to consider recovery more carefully now now no schema means it's not a tables and rows structure and you can again shove anything you want into the database but you got to think about how to optimize performance um on queries now [ __ ] has been hard at work evolving the platform from the early days when you go back and look at its roadmap it's been you know started as a document database purely it added graph processing time series it's made search you know much much easier and more fundamental it's added atlas that fully managed cloud database uh service which we said now comprises 60 of its revenue it's you know kubernetes integrations and kind of the modern microservices stack and dozens and dozens and dozens of other features mongo's done a really fine job we think of creating a leading database platform today that is loved by customers loved by developers and is highly functional and next week the cube will be at mongodb world and we'll be looking for some of these items that we're showing here and this this chart this always going to be main focus on developers [ __ ] prides itself on being a developer friendly platform we're going to look for new features especially around security and governance and simplification of configurations and cluster management [ __ ] is likely going to continue to advance its all-in-one appeal and add more capabilities that reduce the need to to spin up bespoke platforms and we would expect enhance enhancements to atlas further enhancements there is atlas really is the future you know maybe adding you know more cloud native features and integrations and perhaps simplified ways to migrate to the cloud to atlas and improve access to data sources generally making the lives of developers and data analysts easier that's going to be we think a big theme at the event so these are the main things that we'll be scoping out at the event so please stop by if you're in new york city new york city at mongodb world or tune in to thecube.net okay that's it for today thanks to my colleagues stephanie chan who helps research breaking analysis from time to time alex meyerson is on production as today is as is andrew frick sarah kenney steve conte conte anderson hill and the entire team in palo alto thank you kristen martin and cheryl knight helped get the word out and rob hof is our editor-in-chief over there at siliconangle remember all these episodes are available as podcasts wherever you listen just search breaking analysis podcast we do publish each week on wikibon.com and siliconangle.com want to reach me email me david.velante siliconangle.com or dm me at divalante or a comment on my linkedin post and please do check out etr.ai for the best survey data in the enterprise tech business this is dave vellante for the cube insights powered by etr thanks for watching see you next time [Music] you

(upbeat music) >> When Oracle acquired Sun in 2009, it paid $5.6 billion net of Sun's cash and debt. Now I argued at the time that Oracle got one of the best deals in the history of enterprise tech, and I got a lot of grief for saying that because Sun had a declining business, it was losing money, and its revenue was under serious pressure as it tried to hang on for dear life. But Safra Catz understood that Oracle could pay Sun's lower profit and lagging businesses, like its low index 86 product lines, and even if Sun's revenue was cut in half, because Oracle has such a high revenue multiple as a software company, it could almost instantly generate $25 to $30 billion in shareholder value on paper. In addition, it was a catalyst for Oracle to initiate its highly differentiated engineering systems business, and was actually the precursor to Oracle's Cloud. Oracle saw that it could capture high margin dollars that used to go to partners like HP, it's original exit data partner, and get paid for the full stack across infrastructure, middleware, database, and application software, when eventually got really serious about cloud. Now there was also a major technology angle to this story. Remember Sun's tagline, "the network is the computer"? Well, they should have just called it cloud. Through the Sun acquisition. Oracle also got a couple of key technologies, Java, the number one programming language in the world, and MySQL, a key ingredient of the LAMP stack, that's Linux, Apache, MySQL and PHP, Perl or Python, on which the internet is basically built, and is used by many cloud services like Facebook, Twitter, WordPress, Flicker, Amazon, Aurora, and many other examples, including, by the way, Maria DB, which is a fork of MySQL created by MySQL's creator, basically in protest to Oracle's acquisition; the drama is Oscar worthy. It gets even better. In 2020, Oracle began introducing a new version of MySQL called MySQL HeatWave, and since late 2020 it's been in sort of a super cycle rolling, out three new releases in less than a year and a half in an attempt to expand its Tam and compete in new markets. Now we covered the release of MySQL Autopilot, which uses machine learning to automate management functions. And we also covered the bench marketing that Oracle produced against Snowflake, AWS, Azure, and Google. And Oracle's at it again with HeatWave, adding machine learning into its database capabilities, along with previously available integrations of OLAP and OLTP. This, of course, is in line with Oracle's converged database philosophy, which, as we've reported, is different from other cloud database providers, most notably Amazon, which takes the right tool for the right job approach and chooses database specialization over a one size fits all strategy. Now we've asked Oracle to come on theCUBE and explain these moves, and I'm pleased to welcome back Nipun Agarwal, who's the senior vice president for MySQL Database and HeatWave at Oracle. And today, in this video exclusive, we'll discuss machine learning, other new capabilities around elasticity and compression, and then any benchmark data that Nipun wants to share. Nipun's been a leading advocate of the HeatWave program. He's led engineering in that team for over 10 years, and he has over 185 patents in database technologies. Welcome back to the show Nipun. Great to see you again. Thanks for coming on. >> Thank you, Dave. Very happy to be back. >> Yeah, now for those who may not have kept up with the news, maybe to kick things off you could give us an overview of what MySQL HeatWave actually is so that we're all on the same page. >> Sure, Dave, MySQL HeatWave is a fully managed MySQL database service from Oracle, and it has a builtin query accelerator called HeatWave, and that's the part which is unique. So with MySQL HeatWave, customers of MySQL get a single database which they can use for transactional processing, for analytics, and for mixed workloads because traditionally MySQL has been designed and optimized for transaction processing. So in the past, when customers had to run analytics with the MySQL based service, they would need to move the data out of MySQL into some other database for running analytics. So they would end up with two different databases and it would take some time to move the data out of MySQL into this other system. With MySQL HeatWave, we have solved this problem and customers now have a single MySQL database for all their applications, and they can get the good performance of analytics without any changes to their MySQL application. >> Now it's no secret that a lot of times, you know, queries are not, you know, most efficiently written, and critics of MySQL HeatWave will claim that this product is very memory and cluster intensive, it has a heavy footprint that adds to cost. How do you answer that, Nipun? >> Right, so for offering any database service in the cloud there are two dimensions, performance and cost, and we have been very cognizant of both of them. So it is indeed the case that HeatWave is a, in-memory query accelerator, which is why we get very good performance, but it is also the case that we have optimized HeatWave for commodity cloud services. So for instance, we use the least expensive compute. We use the least expensive storage. So what I would suggest is for the customers who kind of would like to know what is the price performance advantage of HeatWave compared to any database we have benchmark against, Redshift, Snowflake, Google BigQuery, Azure Synapse, HeatWave is significantly faster and significantly lower price on a multitude of workloads. So not only is it in-memory database and optimized for that, but we have also optimized it for commodity cloud services, which makes it much lower price than the competition. >> Well, at the end of the day, it's customers that sort of decide what the truth is. So to date, what's been the customer reaction? Are they moving from other clouds from on-prem environments? Both why, you know, what are you seeing? >> Right, so we are definitely a whole bunch of migrations of customers who are running MySQL on-premise to the cloud, to MySQL HeatWave. That's definitely happening. What is also very interesting is we are seeing that a very large percentage of customers, more than half the customers who are coming to MySQL HeatWave, are migrating from other clouds. We have a lot of migrations coming from AWS Aurora, migrations from RedShift, migrations from RDS MySQL, TerriData, SAP HANA, right. So we are seeing migrations from a whole bunch of other databases and other cloud services to MySQL HeatWave. And the main reason we are told why customers are migrating from other databases to MySQL HeatWave are lower cost, better performance, and no change to their application because many of these services, like AWS Aurora are ETL compatible with MySQL. So when customers try MySQL HeatWave, not only do they get better performance at a lower cost, but they find that they can migrate their application without any changes, and that's a big incentive for them. >> Great, thank you, Nipun. So can you give us some names? Are there some real world examples of these customers that have migrated to MySQL HeatWave that you can share? >> Oh, absolutely, I'll give you a few names. Stutor.com, this is an educational SaaS provider raised out of Brazil. They were using Google BigQuery, and when they migrated to MySQL HeatWave, they found a 300X, right, 300 times improvement in performance, and it lowered their cost by 85 (audio cut out). Another example is Neovera. They offer cybersecurity solutions and they were running their application on an on-premise version of MySQL when they migrated to MySQL HeatWave, their application improved in performance by 300 times and their cost reduced by 80%, right. So by going from on-premise to MySQL HeatWave, they reduced the cost by 80%, improved performance by 300 times. We are Glass, another customer based out of Brazil. They were running on AWS EC2, and when they migrated, within hours they found that there was a significant improvement, like, you know, over 5X improvement in database performance, and they were able to accommodate a very large virtual event, which had more than a million visitors. Another example, Genius Senority. They are a game designer in Japan, and when they moved to MySQL HeatWave, they found a 90 times percent improvement in performance. And there many, many more like a lot of migrations, again, from like, you know, Aurora, RedShift and many other databases as well. And consistently what we hear is (audio cut out) getting much better performance at a much lower cost without any change to their application. >> Great, thank you. You know, when I ask that question, a lot of times I get, "Well, I can't name the customer name," but I got to give Oracle credit, a lot of times you guys have at your fingertips. So you're not the only one, but it's somewhat rare in this industry. So, okay, so you got some good feedback from those customers that did migrate to MySQL HeatWave. What else did they tell you that they wanted? Did they, you know, kind of share a wishlist and some of the white space that you guys should be working on? What'd they tell you? >> Right, so as customers are moving more data into MySQL HeatWave, as they're consolidating more data into MySQL HeatWave, customers want to run other kinds of processing with this data. A very popular one is (audio cut out) So we have had multiple customers who told us that they wanted to run machine learning with data which is stored in MySQL HeatWave, and for that they have to extract the data out of MySQL (audio cut out). So that was the first feedback we got. Second thing is MySQL HeatWave is a highly scalable system. What that means is that as you add more nodes to a HeatWave cluster, the performance of the system improves almost linearly. But currently customers need to perform some manual steps to add most to a cluster or to reduce the cluster size. So that was other feedback we got that people wanted this thing to be automated. Third thing is that we have shown in the previous results, that HeatWave is significantly faster and significantly lower price compared to competitive services. So we got feedback from customers that can we trade off some performance to get even lower cost, and that's what we have looked at. And then finally, like we have some results on various data sizes with TPC-H. Customers wanted to see if we can offer some more data points as to how does HeatWave perform on other kinds of workloads. And that's what we've been working on for the several months. >> Okay, Nipun, we're going to get into some of that, but, so how did you go about addressing these requirements? >> Right, so the first thing is we are announcing support for in-database machine learning, meaning that customers who have their data inside MySQL HeatWave can now run training, inference, and prediction all inside the database without the data or the model ever having to leave the database. So that's how we address the first one. Second thing is we are offering support for real time elasticity, meaning that customers can scale up or scale down to any number of nodes. This requires no manual intervention on part of the user, and for the entire duration of the resize operation, the system is fully available. The third, in terms of the costs, we have double the amount of data that can be processed per node. So if you look at a HeatWave cluster, the size of the cluster determines the cost. So by doubling the amount of data that can be processed per node, we have effectively reduced the cluster size which is required for planning a given workload to have, which means it reduces the cost to the customer by half. And finally, we have also run the TPC-DS workload on HeatWave and compared it with other vendors. So now customers can have another data point in terms of the performance and the cost comparison of HeatWave with other services. >> All right, and I promise, I'm going to ask you about the benchmarks, but I want to come back and drill into these a bit. How is HeatWave ML different from competitive offerings? Take for instance, Redshift ML, for example. >> Sure, okay, so this is a good comparison. Let's start with, let's say RedShift ML, like there are some systems like, you know, Snowflake, which don't even offer any, like, processing of machine learning inside the database, and they expect customers to write a whole bunch of code, in say Python or Java, to do machine learning. RedShift ML does have integration with SQL. That's a good start. However, when customers of Redshift need to run machine learning, and they invoke Redshift ML, it makes a call to another service, SageMaker, right, where so the data needs to be exported to a different service. The model is generated, and the model is also outside RedShift. With HeatWave ML, the data resides always inside the MySQL database service. We are able to generate models. We are able to train the models, run inference, run explanations, all inside the MySQL HeatWave service. So the data, or the model, never have to leave the database, which means that both the data and the models can now be secured by the same access control mechanisms as the rest of the data. So that's the first part, that there is no need for any ETL. The second aspect is the automation. Training is a very important part of machine learning, right, and it impacts the quality of the predictions and such. So traditionally, customers would employ data scientists to influence the training process so that it's done right. And even in the case of Redshift ML, the users are expected to provide a lot of parameters to the training process. So the second thing which we have worked on with HeatWave ML is that it is fully automated. There is absolutely no user intervention required for training. Third is in terms of performance. So one of the things we are very, very sensitive to is performance because performance determines the eventual cost to the customer. So again, in some benchmarks, which we have published, and these are all available on GitHub, we are showing how HeatWave ML is 25 times faster than Redshift ML, and here's the kicker, at 1% of the cost. So four benefits, the data all remain secure inside the database service, it's fully automated, much faster, much lower cost than the competition. >> All right, thank you Nipun. Now, so there's a lot of talk these days about explainability and AI. You know, the system can very accurately tell you that it's a cat, you know, or for you Silicon Valley fans, it's a hot dog or not a hot dog, but they can't tell you how the system got there. So what is explainability, and why should people care about it? >> Right, so when we were talking to customers about what they would like from a machine learning based solution, one of the feedbacks we got is that enterprise is a little slow or averse to uptaking machine learning, because it seems to be, you know, like magic, right? And enterprises have the obligation to be able to explain, or to provide a answer to their customers as to why did the database make a certain choice. With a rule based solution it's simple, it's a rule based thing, and you know what the logic was. So the reason explanations are important is because customers want to know why did the system make a certain prediction? One of the important characteristics of HeatWave ML is that any model which is generated by HeatWave ML can be explained, and we can do both global explanations or model explanations as well as we can also do local explanations. So when the system makes a specific prediction using HeatWave ML, the user can find out why did the system make such a prediction? So for instance, if someone is being denied a loan, the user can figure out what were the attribute, what were the features which led to that decision? So this ensures, like, you know, fairness, and many of the times there is also like a need for regulatory compliance where users have a right to know. So we feel that explanations are very important for enterprise workload, and that's why every model which is generated by HeatWave ML can be explained. >> Now I got to give Snowflakes some props, you know, this whole idea of separating compute from storage, but also bringing the database to the cloud and driving elasticity. So that's been a key enabler and has solved a lot of problems, in particular the snake swallowing the basketball problem, as I often say. But what about elasticity and elasticity in real time? How is your version, and there's a lot of companies chasing this, how is your approach to an elastic cloud database service different from what others are promoting these days? >> Right, so a couple of characteristics. One is that we have now fully automated the process of elasticity, meaning that if a user wants to scale up or scale down, the only thing they need to specify is the eventual size of the cluster and the system completely takes care of it transparently. But then there are a few characteristics which are very unique. So for instance, we can scale up or scale down to any number of nodes. Whereas in the case of Snowflake, the number of nodes someone can scale up or scale down to are the powers of two. So if a user needs 70 CPUs, well, their choice is either 64 or 128. So by providing this flexibly with MySQL HeatWave, customers get a custom fit. So they can get a cluster which is optimized for their specific portal. So that's the first thing, flexibility of scaling up or down to any number of nodes. The second thing is that after the operation is completed, the system is fully balanced, meaning the data across the various nodes is fully balanced. That is not the case with many solutions. So for instance, in the case of Redshift, after the resize operation is done, the user is expected to manually balance the data, which can be very cumbersome. And the third aspect is that while the resize operation is going on, the HeatWave cluster is completely available for queries, for DMLS, for loading more data. That is, again, not the case with Redshift. Redshift, suppose the operation takes 10 to 15 minutes, during that window of time, the system is not available for writes, and for a big part of that chunk of time, the system is not even available for queries, which is very limiting. So the advantages we have are fully flexible, the system is in a balanced state, and the system is completely available for the entire duration operation. >> Yeah, I guess you got that hypergranularity, which, you know, sometimes they say, "Well, t-shirt sizes are good enough," but then I think of myself, some t-shirts fit me better than others, so. Okay, I saw on the announcement that you have this lower price point for customers. How did you actually achieve this? Could you give us some details around that please? >> Sure, so there are two things for announcing this service, which lower the cost for the customers. The first thing is that we have doubled the amount of data that can be processed by a HeatWave node. So if we have doubled the amount of data, which can be a process by a node, the cluster size which is required by customers reduces to half, and that's why the cost drops to half. The way we have managed to do this is by two things. One is support for Bloom filters, which reduces the amount of intermediate memory. And second is we compress the base data. So these are the two techniques we have used to process more data per node. The second way by which we are lowering the cost for the customers is by supporting pause and resume of HeatWave. And many times you find customers of like HeatWave and other services that they want to run some other queries or some other workloads for some duration of time, but then they don't need the cluster for a few hours. Now with the support for pause and resume, customers can pause the cluster and the HeatWave cluster instantaneously stops. And when they resume, not only do we fetch the data, in a very, like, you know, a quick pace from the object store, but we also preserve all the statistics, which are used by Autopilot. So both the data and the metadata are fetched, extremely fast from the object store. So with these two capabilities we feel that it'll drive down the cost to our customers even more. >> Got it, thank you. Okay, I promised I was going to get to the benchmarks. Let's have it. How do you compare with others but specifically cloud databases? I mean, and how do we know these benchmarks are real? My friends at EMC, they were back in the day, they were brilliant at doing benchmarks. They would produce these beautiful PowerPoints charts, but it was kind of opaque, but what do you say to that? >> Right, so there are multiple things I would say. The first thing is that this time we have published two benchmarks, one is for machine learning and other is for SQL analytics. All the benchmarks, including the scripts which we have used are available on GitHub. So we have full transparency, and we invite and encourage customers or other service providers to download the scripts, to download the benchmarks and see if they get any different results, right. So what we are seeing, we have published it for other people to try and validate. That's the first part. Now for machine learning, there hasn't been a precedence for enterprise benchmarks so we talk about aiding open data sets and we have published benchmarks for those, right? So both for classification, as well as for aggression, we have run the training times, and that's where we find that HeatWave MLS is 25 times faster than RedShift ML at one percent of the cost. So fully transparent, available. For SQL analytics, in the past we have shown comparisons with TPC-H. So we would show TPC-H across various databases, across various data sizes. This time we decided to use TPC-DS. the advantage of TPC-DS over TPC-H is that it has more number of queries, the queries are more complex, the schema is more complex, and there is a lot more data skew. So it represents a different class of workloads, and which is very interesting. So these are queries derived from the TPC-DS benchmark. So the numbers we have are published this time are for 10 terabyte TPC-DS, and we are comparing with all the four majors services, Redshift, Snowflake, Google BigQuery, Azure Synapse. And in all the cases, HeatWave is significantly faster and significantly lower priced. Now one of the things I want to point out is that when we are doing the cost comparison with other vendors, we are being overly fair. For instance, the cost of HeatWave includes the cost of both the MySQL node as well as the HeatWave node, and with this setup, customers can run transaction processing analytics as well as machine learning. So the price captures all of it. Whereas with the other vendors, the comparison is only for the analytic queries, right? So if customers wanted to run RDP, you would need to add the cost of that database. Or if customers wanted to run machine learning, you would need to add the cost of that service. Furthermore, with the case of HeatWave, we are quoting pay as you go price, whereas for other vendors like, you know, RedShift, and like, you know, where applicable, we are quoting one year, fully paid upfront cost rate. So it's like, you know, very fair comparison. So in terms of the numbers though, price performance for TPC-DS, we are about 4.8 times better price performance compared to RedShift We are 14.4 times better price performance compared to Snowflake, 13 times better than Google BigQuery, and 15 times better than Synapse. So across the board, we are significantly faster and significantly lower price. And as I said, all of these scripts are available in GitHub for people to drive for themselves. >> Okay, all right, I get it. So I think what you're saying is, you could have said this is what it's going to cost for you to do both analytics and transaction processing on a competitive platform versus what it takes to do that on Oracle MySQL HeatWave, but you're not doing that. You're saying, let's take them head on in their sweet spot of analytics, or OLTP separately and you're saying you still beat them. Okay, so you got this one database service in your cloud that supports transactions and analytics and machine learning. How much do you estimate your saving companies with this integrated approach versus the alternative of kind of what I called upfront, the right tool for the right job, and admittedly having to ETL tools. How can you quantify that? >> Right, so, okay. The numbers I call it, right, at the end of the day in a cloud service price performance is the metric which gives a sense as to how much the customers are going to save. So for instance, for like a TPC-DS workload, if we are 14 times better price performance than Snowflake, it means that our cost is going to be 1/14th for what customers would pay for Snowflake. Now, in addition, in other costs, in terms of migrating the data, having to manage two different databases, having to pay for other service for like, you know, machine learning, that's all extra and that depends upon what tools customers are using or what other services they're using for transaction processing or for machine learning. But these numbers themselves, right, like they're very, very compelling. If we are 1/5th the cost of Redshift, right, or 1/14th of Snowflake, these numbers, like, themselves are very, very compelling. And that's the reason we are seeing so many of these migrations from these databases to MySQL HeatWave. >> Okay, great, thank you. Our last question, in the Q3 earnings call for fiscal 22, Larry Ellison said that "MySQL HeatWave is coming soon on AWS," and that caught a lot of people's attention. That's not like Oracle. I mean, people might say maybe that's an indication that you're not having success moving customers to OCI. So you got to go to other clouds, which by the way I applaud, but any comments on that? >> Yep, this is very much like Oracle. So if you look at one of the big reasons for success of the Oracle database and why Oracle database is the most popular database is because Oracle database runs on all the platforms, and that has been the case from day one. So very akin to that, the idea is that there's a lot of value in MySQL HeatWave, and we want to make sure that we can offer same value to the customers of MySQL running on any cloud, whether it's OCI, whether it's the AWS, or any other cloud. So this shows how confident we are in our offering, and we believe that in other clouds as well, customers will find significant advantage by having a single database, which is much faster and much lower price then what alternatives they currently have. So this shows how confident we are about our products and services. >> Well, that's great, I mean, obviously for you, you're in MySQL group. You love that, right? The more places you can run, the better it is for you, of course, and your customers. Okay, Nipun, we got to leave it there. As always it's great to have you on theCUBE, really appreciate your time. Thanks for coming on and sharing the new innovations. Congratulations on all the progress you're making here. You're doing a great job. >> Thank you, Dave, and thank you for the opportunity. >> All right, and thank you for watching this CUBE conversation with Dave Vellante for theCUBE, your leader in enterprise tech coverage. We'll see you next time. (upbeat music)

(upbeat music) >> Welcome to theCUBE coverage of women in tech. International Women's Day 2022. I'm your host, Lisa Martin. Karla Wong joins me next. Country Sales Leader for the Commercial Sector in Peru at AWS. Karla, welcome to theCUBE. >> Thank you so much Lisa and thank you for having me. It's a pleasure to be with you today. >> I'm looking forward to chatting with you. You've been in the tech industry for more than 20 years, you've been a leader in tech and sales and customer service, partners, organizations. Talk to me a little bit about your background. >> I am a system engineer. I have some studies from enterprise direction with a university in Savannah, Columbia and I have a digital transformation certified with MIT in Boston. >> Fantastic, were you always interested in technology or STEM or was it something that you pivoted into somewhere during your career? >> Yes, you know what? Since I was little, I was just fascinated with the technology and all the time I was just trying to figure out how to do things and how to build that things and I remember once I was just, of course many time long ago, I was with this BHS, right? An equipment and I tried to do and tried to understand how this works and just figure out I was with many parts of that equipment and then I didn't realize how to join that parts but it was really funny because all the time I was trying to understand what is behind that kind of equipment, how this works and all the time I was asking and my dad said, I was just feeling so curiosity about that and asking many questions and I have uncles that they are engineers. So I was just all the time asking about that and they said, you know what? You are good in math, maybe you can just decide for an engineering career. They were encouraged me for doing that. So I guess that was my first clue that I'm interested in technology. >> Well, you sounds like you have a natural curiosity that you had great role models in your parents and probably others along your educational route and your career route that kind of encouraged that curiosity and being curious is one of the things that's important to being at AWS. Am I right? >> Yes, it's really important because we promote, you know, our, one of the main leadership principles that you read is learn to be curious and they promote that one, right? They're encouraging you to innovate, to learn more, to try to understand more about our solutions, our customers, how to make the things better and you have the space to propose new things, to do the things better. So they encourage you and they empower you to do that and you feel like your curiosity that you have very natural here's improved and they just promote that you continue to do that. >> That curiosity is so important. I mean, when we think about women in technology and we think about bringing in more thought diversity and DEI, it's important to be curious, to be able to bring different thoughts in so that the organization can be more well rounded, it can learn, you also not only do you lead the sales organization, but you are someone that's very active in volunteering. Tell me a little bit about that and how do you balance leading a sales organization and volunteering at the same time? >> You know, when you talk about this is more like work life balance, right? And when we talk about that you can feel like you need it, right? You need to work on that. It's more like an attitude of it's extremely important to think about mental health for everyone because that of course have impact in your physical health and when you talk about this, it not only matters in terms of attitude, it's action and disciplines as well and you have to keep in mind that. The first thing I believe and all the time I do it give the right value for this balance because it's something that a lot of people want more than anything and I have more than some professional decision thinking about this precisely and I have to thinking of me as a person, my family, how to help the community and you cannot imagine the impact when you decide to go for a volunteering activities how can benefit you and not in only the personal way, in your professional way. Even though you didn't start a volunteering, trying to figure out how this help you in your professional life, you receive a lot of benefits from the volunteering activities and it's amazing how that one's impacting your professional life also. When you are a volunteer, you'll receive new and meaningful experiences. Volunteering can be an excellent getaway to find unique and valuable experiences that you are very difficult to find in a day to day basis, right? And you develop your real life skills, openness to criticism, responsibility, humility, commitment, service, attitude, many things that you can proactively include in your job with your team and you can join with them in teamwork and try to figure out how to engage with them in your activities. This is another way to motivate your team, to build your team, right? Talking with this very valuable experiences and also I find out that that improves your health and mood. >> Sounds very-- >> We talk having-- >> Sorry. >> I'm sorry, no don't worry. >> That's very complimentary, that the volunteer work with leading the sales organization that there's so much value that you're bringing into your sales leadership role from the volunteering that you do. I'm just curious, can you describe some of the volunteer organizations that you work with? I think it's pretty impressive. >> Yes, I started my volunteering 14 years ago I guess but I was in the volunteering activities from the school and my dad was a really strong influence for that because I joined, I remember joining with him and go to do some volunteering activities that he led and I start 14 years I went with Operation and Smile group and then in the last two or three years I start with Project of Love. We are focused on kids with cancer and try to help them to build the last wishes they have because they pass away and at the end of this, this two years ago, I start with local activity that we do for patients with rare diseases and we just try to join two great passion that I have. One is the dance that we have here. The name of our national dance is Marinera Norteña and we are just doing this with a group that they are passion at the same time with this volunteering activities and the dance and we just trying to be the ambassador for and the voice for these patients, try to share with the community, the hard health journey that they have trying to obtain a fair treatment, a fair diagnostic, because they are rare disease and here is very difficult that they investigate about that. So that's why we are just doing this using dance as a way to broadcast our voice and just share happiness and hope and health. >> Happiness and hope. Those are two great things. So as the female leader in the tech industry, what are some of the main challenges that you have found regarding cultural aspects, regarding geographical aspects and LATAM? Talk to me about some of those challenges. >> Let me share with you my personal journey. My challenges started with the moment I decided to start engineering. A career that is traditional considered for men only, although this changes over the time, you will realize that the stereotype remains in many people minds right? It happens not only in Peru I can see it in Latin America. Someone once asked me if I wouldn't like to study something easier for a woman, right? And I just, when I received that question, that helping me to reaffirm that it was taking the right decision and I have the fortune to work with companies that believe in female leadership and the importance of our contribution and empower me to do things differently. Although I must confess that this was not always like this. I experienced the situation when I have to show that I'm so much and more capable and prepared than a man to take a major challenge. So despite the fact in the recent years you have had the great advances in integration of women in the field of science and technology, the gap in equality in equality in this sector still continues and many times the attitude towards women is discriminatory considering that we don't have enough knowledge and we don't have enough strength to overcome challenge without the ability to give the extra mile that is often required, or simply because of a gender issue. And generally speaking, opportunities that they're not equal. Neither in salaries. Several studies have revealed that in the same position since at position level within company, men's salary or benefits are higher than the woman. In addition, sometimes the position for a woman is not necessarily for merit it's just to feel fulfill a gender quota and when it's fulfilled, there's no more opportunities. So it's still a long way to go. We are working in that, we are trying to inspire more women to be part of this world. This is an amazing world and this world needs our leadership, judgment, ambition, as a woman. So that's why we try to inspire and try to be a role model for some young ladies that they are thinking about this career in technology. >> Right, you bring up a great point though about one of the things in terms of hiring for quotas. And as we think about this International Women's Day, this year's theme is Breaking the Bias. Where do you think we are with that? >> I think we have a lot long, long way to go to. Today we don't see that we have more women in some leadership roles in technology. We see more young ladies studying engineering but you know what, when you talk about stereotypes we need to understand, or the bias, the bias is not only what the society it's giving you, it's also your own bias because we need to understand that technology careers is not only for men it's also for a woman. And we need to understand and change the perspective that we see the challenges that we have in our life because sometimes that could be a really stopper in your professional life. And for me, we don't, we really need to understand that it's important. We cannot stop believing in ourself and we can achieve whatever we want. So we never stop pursuing our goals and achieve what you really need to achieve and as I said all the time, get inspired by women with great achievements who have changed this world technology. We have many examples of that for many years. We have Eva Maria Kiesler, the core inventor of Wi-Fi, Radia Joy Perlman, known as the the mother of the internet and Ada Lovelace who became the first female computer programmer. So we have many examples in this story to understand that the limit is on you. So the bias we need to break the first one is the bias that you have of yourself. >> That's a good point. That's a really good point there. I'm curious, what would your recommendation be? You obviously had, you had that natural curiosity that we talked about. You also seems like you had great parents who were very encouraging of all of the different things that you were interested in. What do you recommend for women maybe starting out in the STEM area or in tech in particular? How do they get that courage to just try? >> You know what, the main thing I guess as I mentioned before, is to put aside the stereotypes, right? And get out of your head, the standing out career like science, technology and engineering is only for a man. All the time I have this list for me, that is lesson learned. And my lesson learned is please don't think that you cannot do it. Try it. If you go and the things do not work well, try it again and try it again. So don't feel stopped because you face your first challenge and the challenge it's very difficult, because we have the courage to do that and you know what? It is very and interesting to understand that women has resilience, we have the courage to do anything, we are multi tasking all the time they say women can do many things at the same time and we have this particular way to communicate. We are very inclusive. We make empathy. We're just leading with a cohesion concept of a team. So we need to explore more about our strengths and try to encourage from them. And one of the main things for me is don't feel afraid and transform, you know, when you feel like that, transfer that as your power, you're encouraged to continue. So we need to transform our fears in our, I always said our gasoline to continue and then your motive to be successful. So transform your fears. >> I love that. >> That's my main focus. >> Transform your fear. That's great advice there is. And I will say no, don't be afraid to raise your hand and ask a question 'cause I guarantee you, many people in the room whether it's a physical room these days or it's a virtual video conferencing room, probably have the same question. Be the one to raise your hand and ask. But I love how you're saying transform that fear 'cause it's there. Don't be afraid to fail but also we need to have those female role models, mentors and sponsors that we can see that can have help us kind of in that transformation process, that mentorship is really critical to help guide that along. >> Yes, yes, yes, that's correct and I will, I am, I was really fortunate because I have real role models in my life not only, as I mentioned my dad and also one of the things that I recognize in this company that I work for that empower leadership from women and I identify some role models I want to follow and I ask her in each particular company to be my coach and to be my mentor, because of course you are starting in the technology side and you need more from others that they can share with you her wisdom, right? And try to give you advice, how to work on that. And I always said, and I will always repeat because I sometimes I have the opportunity to mentor young ladies that they are very curious about the technology side and I share with them my experience, my lesson learned so they can build their own story to do this and I share all the time don't compete in a male environment in a gray suit. You have your own personality, you have your own strengths, you're a woman and you have your strength as a woman. Show that, be, you know, the black point in the middle of the white environment because you're different, your leadership is different. You have to understand that, value that and explore more about that so you can inspire others and you can inspire yourself and it's fair to say, please identify your achievements and value them because you deserve that, you fight for them and you have to be celebrate for that. >> Right. >> So that's the main, you know, the main idea when I share with these ladies but it's right, it's fair to be recognized for that. It's your effort, it's your way to do the things differently and it's very appreciated. >> Very appreciated and very inspiring. Thank you so much Karla for sharing your story, how you are balancing work life volunteerism, how it's complimentary. I found this conversation very inspiring so thank you so much for joining me today. >> Thank you. No, thank you so much Lisa. It was really a pleasure for me to be with you today. >> Excellent, likewise. For Karla Wong, I'm Lisa Martin. You're watching theCUBE's coverage of women in tech, International Women's Day 2022. (upbeat music)

(upbeat music) >> Oracle continues to pursue a multi-mode converged database strategy. The premise of this all in one approach is to make life easier for practitioners and developers. And the most recent example is the Oracle database API for MongoDB, which was announced today. Now, Oracle, they're not the first to come out with a MongoDB compatible API, but Oracle hopes to use its autonomous database as a differentiator and further build a moat around OCI, Oracle Cloud Infrastructure. And with us to talk about Oracle's MongoDB compatible API is Gerald Venzl, who's a distinguished Product Manager at Oracle. Gerald was a guest along with Maria Colgan on the CUBE a while back, and we talked about Oracle's converge database and the kind of Swiss army knife strategy, I called it, of databases. This is dramatically different. It's an approach that we see at the opposite end of the the spectrum, for instance, from AWS, who, for example, goes after the world of developers with a different database for every use case. So, kind of picking up from there, Gerald, I wonder if you could talk about how this new MongoDB API adds to your converged model and the whole strategy there. Where does it fit? >> Yeah, thank you very much, Dave and, by the way, thanks for having me on the CUBE again. A pleasure to be here. So, essentially the MongoDB API to build the compatibility that we used with this API is a continuation of the converge database story, as you said before. Which is essentially bringing the many features of the many single purpose databases that people often like and use, together into one technology so that everybody can benefit from it. So as such, this is just a continuation that we have from so many other APIs or standards that we support. Since a long time, we already, of course to SQL because we are relational database from the get go. Also other standard like GraphQL, Sparkle, et cetera that we have. And the MongoDB API, is now essentially just the next step forward to give the developers this API that they've gotten to love and use. >> I wonder if you could talk about from the developer angle, what do they get out of it? Obviously you're appealing to the Mongo developers out there, but you've got this Mongo compatible API you're pouting the autonomous database on OCI. Why aren't they just going to use MongoDB Atlas on whatever cloud, Azure or AWS or Google Cloud platform? >> That's a very good question. We believe that the majority of developers want to just worry about their application, writing the application, and not so much about the database backend that they're using. And especially in cloud with cloud services, the reason why developers choose these services is so that they don't have to manage them. Now, autonomous database brings many topnotch advanced capabilities to database cloud services. We firmly believe that autonomous database is essentially the next generation of cloud services with all the self-driving features built in, and MongoDB developers writing applications against the MongoDB API, should not have to hold out on these capabilities either. It's like no developer likes to tune the database. No developer likes to take a downtime when they have to rescale their database to accommodate a bigger workload. And this is really where we see the benefit here, so for the developer, ideally nothing will change. You have MongoDB compatible API so they can keep on using their tools. They can build the applications the way that they do, but the benefit from the best cloud database service out there not having to worry about any of these package things anymore, that even MongoDB Atlas has a lot of shortcomings still today, as we find. >> Of cos, this is always a moving target The technology business, that's why we love it. So everybody's moving fast and investing and shaking and jiving. But, I want to ask you about, well, by the way, that's so you're hiding the underlying complexity, That's really the big takeaway there. So that's you huge for developers. But take, I was talking before about, the Amazon's approach, right tool for the right job. You got document DB, you got Microsoft with Cosmos, they compete with Mongo and they've been doing so for some time. How does Oracle's API for Mongo different from those offerings and how you going to attract their users to your JSON offering. >> So, you know, for first of all we have to kind of separate slightly document DB and AWS and Cosmos DB in Azure, they have slightly different approaches there. Document DB essentially is, a document store owned by and built by AWS, nothing different to Mongo DB, it's a head to head comparison. It's like use my document store versus the other document store. So you don't get any of the benefits of a converge database. If you ever want to do a different data model, run analytics over, etc. You still have to use the many other services that AWS provides you to. You cannot all do it into one database. Now Cosmos DB it's more in interesting because they claim to be a multi-model database. And I say claim because what we understand as multi-model database is different to what they understand as multimodel database. And also one of the reasons why we start differentiating with converge database. So what we mean is you should be able to regardless what data format you want to store in the database leverage all the functionality of the database over that data format, with no trade offs. Cosmos DB when you look at it, it essentially gives you mode of operation. When you connect as the application or the user, you have to decide at connection time, how you want, how this database should be treated. Should it be a document store? Should it be a graph store? Should it be a relational store? Once you make that choice, you are locked into that. As long as you establish that connection. So it's like, if you say, I want a document store, all you get is a document store. There's no way for you to crossly analyze with the relational data sitting in the same service. There's no for you to break these boundaries. If you ever want to add some graph data and graph analytics, you essentially have to disconnect and now treat it as a graph store. So you get multiple data models in it, but really you still get, one trick pony the moment you connect to it that you have to choose to. And that is where we see a huge differentiation again with our converge database, because we essentially say, look, one database cloud service on Oracle cloud, where it allows you to do anything, if you wish to do so. You can start as a document store if you wish to do so. If you want to write some SQL queries on top, you can do so. If you want to add some graph data, you can do so. But there's no way for you to have to rewrite your application, use different libraries and frameworks now to connect et cetera, et cetera. >> Got it. Thank you for that. Do you have any data when you talk to customers? Like I'm interested in the diversity of deployments, like for instance, how many customers are using more than one data model? Do for instance, do JSON users need support for other data types or are they happy to stay kind of in their own little sandbox? Do you have any data on that? >> So what we see from the majority of our customers, there is no such thing as one data model fits everything. So, and it's like, there again we have to differentiate the developer that builds a certain microservice, that makes happy to stay in the JSON world or relational world, or the company that's trying to derive value from the data. So it's like the relational model has not gone away since 40 years of it existence. It's still kicking strong. It's still really good at what it does. The JSON data model is really good in what it does. The graph model is really good at what it does. But all these models have been built for different purposes. Try to do graph analytics on relational or JSON data. It's like, it's really tricky, but that's why you use a graph model to begin with. Try to shield yourself from the organization of the data, how it's structured, that's really easy in the relational world, not so much when you get into a document store world. And so what we see about our customers is like as they accumulate more data, is they have many different applications to run their enterprises. The question always comes back, as we have predicted since about six, seven years now, where they say, hey, we have all this different data and different data formats. We want to bring it all together, analyze it together, get value out of the data together. We have seen a whole trend of big data emerge and disappear to answer the question and didn't quite do the trick. And we are basically now back to where we were in the early 2000's when XML databases have faded away, because everybody just allowed you to store XML in the database. >> Got it. So let's make this real for people. So maybe you could give us some examples. You got this new API from Mongo, you have your multi model database. How, take a, paint a picture of how customers are going to benefit in real world use cases. How does it kind of change the customer's world before and after if you will? >> Yeah, absolutely. So, you know the API essentially we are going to use it to accept before, you know, make the lives of the developers easier, but also of course to assist our customers with migrations from Mongo DB over to Oracle Autonomous Database. One customer that we have, for example, that would've benefited of the API several a couple of years ago, two, three years ago, it's one of the largest logistics company on the planet. They track every package that is being sent in JSON documents. So every track package is entries resembled in a JSON document, and they very early on came in with the next question of like, hey, we track all these packages and document in JSON documents. It will be really nice to know actually which packages are stuck, or anywhere where we have to intervene. It's like, can we do this? Can we analyze just how many packages get stuck, didn't get delivered on, the end of a day or whatever. And they found this struggle with this question a lot, they found this was really tricky to do back then, in that case in MongoDB. So they actually approached Oracle, they came over, they migrated over and they rewrote their applications to accommodate that. And there are happy JSON users in Oracle database, but if we were having this API already for them then they wouldn't have had to rewrite their applications or would we often see like worry about the rewriting the application later on. Usually migration use cases, we want to get kind of the migration done, get the data over be running, and then worry about everything else. So this would be one where they would've greatly benefited to shorten this migration time window. If we had already demo the Mongo API back then or this compatibility layer. >> That's a good use case. I mean, it's, one of the most prominent and painful, so anything you could do to help that is key. I remember like the early days of big data, NoSQL, of course was the big thing. There was a lot of confusion. No, people thought was none or not only SQL, which is kind of the more widely accepted interpretation today. But really, it's talking about data that's stored in a non-relational format. So, some people, again they thought that SQL was going to fade away, some people probably still believe that. And, we saw the rise of NoSQL and document databases, but if I understand it correctly, a premise for your Mongo DB API is you really see SQL as a main contributor over Mongo DB's document collections for analytics for example. Can you make, add some color here? Are you seeing, what are you seeing in terms of resurgence of SQL or the momentum in SQL? Has it ever really waned? What's your take? >> Yeah, no, it's a very good point. So I think there as well, we see to some extent history repeating itself from, this all has been tried beforehand with object databases, XML database, et cetera. But if we stay with the NoSQL databases, I think it speaks at length that every NoSQL database that as you write for the sensor you started with NoSQL, and then while actually we always meant, not only SQL, everybody has introduced a SQL like engine or interface. The last two actually join this family is MongoDB. Now they have just recently introduced a SQL compatibility for the aggregation pipelines, something where you can put in a SQL statement and that essentially will then work with aggregation pipeline. So they all acknowledge that SQL is powerful, for us this was always clear. SQL is a declarative language. Some argue it's the only true 4GL language out there. You don't have to code how to get the data, but you just ask the question and the rest is done for you. And, we think that as we, basically, has SQL ever diminished as you said before, if you look out there? SQL has always been a demand. Look at the various developer surveys, etc. The various top skills that are asked for SQL has never gone away. Everybody loves and likes and you wants to use SQL. And so, yeah, we don't think this has ever been, going away. It has maybe just been, put in the shadow by some hypes. But again, we had the same discussion in the 2000's with XML databases, with the same discussions in the 90's with object databases. And we have just frankly, all forgotten about it. >> I love when you guys come on and and let me do my thing and I can pretty much ask any question I want, because, I got to say, when Oracle starts talking about another company I know that company's doing well. So I like, I see Mongo in the marketplace and I love that you guys are calling it out and making some moves there. So here's the thing, you guys have a large install base and that can be an advantage, but it can also be a weight in your shoulder. These specialized cloud databases they don't have that legacy. So they can just kind of move freely about, less friction. Now, all the cloud database services they're going to have more and more automation. I mean, I think that's pretty clear and inevitable. And most if not all of the database vendors they're going to provide support for these kind of converged data models. However they choose to do that. They might do it through the ecosystem, like what Snowflake's trying to do, or bring it in the house themselves, like a watch maker that brings an in-house movement, if you will. But it's like death and taxes, you can't avoid it. It's got to happen. That's what customers want. So with all that being said, how do you see the capabilities that you have today with automation and converge capabilities, How do you see that, that playing out? What's, do you think it gives you enough of an advantage? And obviously it's an advantage, but is it enough of an advantage over the specialized cloud database vendors, where there's clearly a lot of momentum today? >> I mean, honestly yes, absolutely. I mean, we are with some of these databases 20 years ahead. And I give you concrete examples. It's like Oracle had transaction support asset transactions since forever. NoSQL players all said, oh, we don't need assets transactions, base transactions is fine. Yada, yada, yada. Mongo DB started introducing some transaction support. It comes with some limits, cannot be longer than 60 seconds, cannot touch more than a thousand documents as well, et cetera. They still will have to do some catching up there. I mean, it took us a while to get there, let's be honest. Glad We have been around for a long time. Same thing, now that happened with version five, is like we started some simple version of multi version concurrency control that comes along with asset transactions. The interesting part here is like, we've introduced this also an Oracle five, which was somewhere in the 80's before I even started using Oracle Database. So there's a lot of catching up to do. And then you look at the cloud services as well, there's actually certain, a lot of things that we kind of gotten take, we've kind of, we Oracle people have taken for granted and we kind of keep forgetting. For example, our elastic scale, you want to add one CPU, you add one CPU. Should you take downtime for that? Absolutely not. It's like, this is ridiculous. Why would you, you cannot take it downtime in a 24/7 backend system that runs the world. Take any of our customers. If you look at most of these cloud services or you want to reshape, you want to scale your cloud service, that's fine. It's just the VM under the covers, we just shut everything down, give you a VM with more CPU, and you boot it up again, downtown right there. So it's like, there's a lot of these things where we go like, well, we solved this frankly decades ago, that these cloud vendors will run into. And just to add one more point here, so it's like one thing that we see with all these migrations happening is exactly in that field. It's like people essentially started building on whether it's Mongo DB or other of these NoSQL databases or cloud databases. And eventually as these systems grow, as they ask more difficult questions, their use cases expand, they find shortcomings. Whether it's the scalability, whether it's the security aspects, the functionalities that we have, and this is essentially what drives them back to Oracle. And this is why we see essentially this popularity now of pendulum swimming towards our direction again, where people actually happily come over back and they come over to us, to get their workloads enterprise grade if you like. >> Well, It's true. I mean, I just reported on this recently, the momentum that you guys have in cloud because it is, 'cause you got the best mission critical database. You're all about maps. I got to tell you a quick story. I was at a vertical conference one time, I was on stage with Kurt Monash. I don't know if you know Kurt, but he knows this space really well. He's probably forgot and more about database than I'll ever know. But, and I was kind of busting his chops. He was talking about asset transactions. I'm like, well with NoSQL, who needs asset transactions, just to poke him. And he was like, "Are you out of your mind?" And, and he said, look it's everybody is going to head in this direction. It turned out, it's true. So I got to give him props for that. And so, my last question, if you had a message for, let's say there's a skeptical developer out there that's using Mongo DB and Atlas, what would you say to them? >> I would say go try it for yourself. If you don't believe us, we have an always free cloud tier out there. You just go to oracle.com/cloud/free. You sign up for an always free tier, spin up an autonomous database, go try it for yourself. See what's actually possible today. Don't just follow your trends on Hackernews and use a set study here or there. Go try it for yourself and see what's capable of >> All right, Gerald. Hey, thanks for coming into my firing line today. I really appreciate your time. >> Thank you for having me again. >> Good luck with the announcement. You're very welcome, and thank you for watching this CUBE conversation. This is Dave Vellante, We'll see you next time. (gentle music)

(gentle music) >> Welcome back to theCUBE's continuous coverage of AWS re:Invent 2021. I'm your host, Lisa Martin. We are running one of the industry's most important and largest hybrid tech events of the year with AWS and its ecosystem partners. We have two live sets, two remote sites, and over a hundred guests on the program talking about the next decade in cloud innovation. I'm pleased to welcome Jon Bakke, Chief Revenue Officer from Maria DB as my next guest. Jon, welcome to the program. >> Thanks for having me, Lisa. >> Talk to me a little bit about MariaDB. What makes it unique? What differentiates it? What gaps in the market does it address? >> Yeah, so we have a lot of passion here at MariaDB because we are, at the end of the day, we're the backbone of services used by people everyday, all over the world. In fact, you might not realize that, but you've probably hit a MariaDB database in the past 60 minutes. It's true. For example, if you're using a Samsung mobile phone, we provide data services for the Samsung cloud. In fact, we've provided services for 5G networks all over the globe. And so at the end of the day, we actually process trillions of transactions per day. And I think that's really cool. >> Awesome. Talk to me a little bit about the key problems. You mentioned Samsung. Big fan, lots of Samsung devices in the house. Talk to me about some of the key problems that MariaDB SkySQL specifically solves for customers. What are they coming to you, looking for them, looking for help for? >> Yeah, so we launched SkySQL and AWS earlier this year. It's become wildly popular. And so SkySQL overcome some of the limitations of the cloud. 1.0, 2.0 era. In fact, we went from having zero customers to a slew of customers in just a short period of time. There are a ton of pent up demand from MariaDB and distributed SQL in particular, and that's our Xpand product. And where Samsung uses Xpand is, they use it to store data for the phones, just like, you might if you're an iPhone user on the iCloud, they have the Samsung cloud. So what we do is we provide expanding database services for them, for a large user base across the globe. And they do that because they just can't get the scale out of some of the community databases that are offered by the major CSPs. >> And obviously that scale is critical. We've seen so much change in the last year and a half, two years with growth, with acceleration to cloud acceleration of digital. Talk to me about what you seen as the CRO of the company from a customer lens perspective. How has the last 20 months really affected acceleration, adoption, of Maria's technologies? >> Yeah, so, I'm a geek at heart. I grew up in the database business. In fact, I've been in the database business for 30 years and during the last 20 months during the pandemic, and even before that, companies like MariaDB strive to create a beautiful database and what it really is a beautiful database. It's a database that is flushed with features that make applications work. Lightweight, portable, and fast for the cloud, but still reliable and familiar so that application developers can use it for multiple workloads. So when it comes to the database industry, we're still going after those characteristics and we provide world-class support. My team just rocks it for our customers. And it's really important to them to get that. And at the end of the day, our costs while at the end of the day, we're the least expensive. So it really is a beautiful database and we're very proud of it. >> Beautiful database that's the least expensive. That sounds like music to probably a lot of companies ears. Talk to me about where it went. Obviously AWS, you mentioned SkySQL was launched earlier this year on AWS? >> That's correct. Yep. >> Talk to me a little bit more about the capabilities there, the partnership that Maria and AWS have, what you bring to your customers. >> Yeah, so we have a great partnership with AWS. They provide a tremendous levels of support to help startups like MariaDB get going satisfactory and everything about their go-to market strategy to make enabled partners like us. But we have a customer that is, well, they're a major trading application on the internet and they were an AWS customer, right? So they were an existing AWS customer, but they were struggling with some of the community databases in AWS to find that scale and that elasticity that they were looking for on their platform. So enter MariaDB Xpand, where we can scale a relational database out far and wide to make it possible for a customer like that. Who's really pushing the limits of what a database needs to do to remain an AWS customer. So in this particular case, we worked with AWS to land them on SkySQL and use Xpand, a distributed database technology. So we went together and that's a really great story for everybody. >> Talk to me about some of the technical requirements, as we've seen so much change in the last 20 months, as I said, but so much growth and scale and needs are changing so dynamically. What are some of the key technical requirements of the database to keep up with that? And how does MariaDB exhibit those? >> Yeah, that's a great question. So in distributed SQL, in particular, which I see as sort of the next wave of database, particularly in the cloud, right? The database needs to leverage familiar application paradigms like relational and document databases do and connection protocols so that existing applications connect to those. But at the end, they have to be highly scalable for the cloud by design and highly available in the cloud by design. Xpand just screams. It's really fast. It's really reliable. And transactional integrity is inherent to the architecture. So our customers love it. And so really, what's not to love about a database that does all of those things? >> What's not to love about a beautiful database? That speed. I mean, the speed is critical. I think one of the many things that we've learned in the last interesting couple of years of our lives is that real time is no longer a nice to have, right? Nobody wants a less data, slower. That ability to deliver real-time data, real-time analytics is critical for businesses in any company as we're seeing. And you're probably seeing this as a CRO, every company becoming a software company, or leaning to. >> Absolutely, yeah. Some of our biggest customers are major SAS providers. So if you work for a business that is using ServiceNow, one of the largest SAS companies in the world, you're using MariaDB every day, billions and billions of transactions by service, now on an hourly basis and it's all in the cloud. So when we look at how we've evolved to this point, we're offering services to companies big and small, we're being tested by companies like ServiceNow and their infrastructure on a regular basis. >> What are some of the trends that you're seeing as we... And 22 months or so in this pandemic, what are some of the market trends that you're seeing from a scalability perspective? And what is it that a distributed SQL database can deliver to help customers meet those trends? >> Well, certainly, I think when you look at what is a good database for the cloud in the future, it really does need to have the features that make applications work. So you had mentioned analytical databases and transactional databases. One thing that is inherent to our strategy, is the ability to use hybrid approach to transactional and analytical because a lot of applications are both at the end of the day. And why use two different databases in order to get there? Right? Our database is lightweight and fast. It's portable. It's reliable and familiar to the customer and versatile in the workload. So those are the things that are trending at the conclusion of sort of this year going into next year, as we roll out more technology in subsequent versions, we'll just enhance those capabilities, make it possible for even more and more workloads to find their way into SkySQL. >> And talk about the adoption of cloud, the acceleration. We've been talking about that a lot in the last year and a half about the acceleration of digital transformation, the acceleration to cloud. It was so critical for so many businesses, especially if you think of the SAS adoption, the collaboration tools, but what are some of the things that you're seeing? How are you helping customers on that migration journey? >> Yeah. So migration is a key element there. there are customers leading older proprietary database technology. There are customers trying to enhance their cloud experience and go from the early cloud databases up to more modern architectures. And so migration is a constant activity that we work with our customers on. And so over the years, just as a matter of course, we've become better and better at getting database workloads from proprietary, older databases, even other open source databases onto MariaDB, so that we can consume those workloads and get those in the cloud and make them work for customers better than they ever have before. >> And I'm curious as the Chief Revenue Officer, how your customer conversations have evolved in the last year or so, where is cloud database security? Where are those things with respect to the level of conversations that you're having with customers? And is that conversation going up the stack? >> Yeah, so the security has always been a key cornerstone of the database industry, really, when you think about it, database is information assurance and confidentiality is a key tenant to information security and information assurance in general. So it's always an ever present in the discussion. MariaDB is enhancing its list of compliance that we've gone through, like SOC 2, we're on the precipice of that. We've got ISO certifications and we have US Department of Defense install guys that are secure for a MariaDB. All sorts of activity around that, to make it possible for customers to standardize on MariaDB. We have customers that have taken out every ounce of their legacy, relational database, the older incumbents, and replace that with lighter weight MariaDB, because we have the security qualifications, but we also meet their functional needs and their information assurance needs. And so that's whats made us really successful. >> In addition to compliance, you talked about this database being beautiful. You described what you meant by that, but also you said least expensive. So I'm wondering from a business outcome perspective, are customers all across the board, reducing TCO, leveraging MariaDB? >> Absolutely. And in cases where we displace a proprietary database, the TCO can reduce by as much as 90%. And so it's very attractive to customers that are looking for the next wave. Not only do we take them to a lower cost, but we bring them to a more modern multi-cloud architecture. So AWS is our primary focus for certain in this conversation but also just generally because there's such a huge install base. But they do like the option of being able to say, "Hey, I can use this database on any cloud. It works everywhere. And the vendor that makes it is supporting it in all environments." So for us, that's a huge strong point in terms of what makes our business run. >> And we're seeing so much, we're talking so much about Hybrid, Hybrid IT, Hybrid Cloud, Hybrid work from anywhere environments. So I imagine MariaDB runs on, obviously AWS, but Azure, Google cloud platform, so that customers that are in that multi-cloud world and those that will be can take advantage of the services. >> That's correct. So Azure is in our near term pipeline or roadmap for the cloud, but we're already present in GCP and we're available in other clouds as well. >> Excellent. So talk to me a little bit about what customers can do. Can they test out MariaDB? Can they test out SkySQL, Xpand? If so, where do they go? How do they get their hands on it? >> Right, so existing AWS customers, they can get to SkySQL on the AWS marketplace, right? It's incredibly easy. AWS customers go to the marketplace. They can find us by doing a search. But not to be outdone, there are customers that aren't on AWS and they can come to MariaDB.com. You can start SkySQL there and select AWS as the deployment cloud and try it for free. It's super cool. It's really easy. >> I'm just curious. What's the typical deployment time from the free trial POC to deployment? What do you normally see from a time distinct band perspective? >> Oh yeah, customers are up and running with a live database in just a few minutes. >> Minutes? >> Yep. >> Minutes up to 90% TCO. Big business outcomes there that affect every business in every industry. John, we appreciate you coming on, talking to us about MariaDB, the solutions that you offer, and how you're partnering with AWS and where folks can go to get started. >> Thank you. >> He's Jon Bakke. I'm Lisa Martin. You're watching theCUBE's continuous coverage of AWS re:Invent 2021. Stick around, more coverage coming up next. (peaceful music)

(upbeat music) Developers have become the new king makers in the world of digital and cloud. The rise of containers and microservices has accelerated the transition to cloud native applications. A lot of people will talk about application architecture and the related paradigms and the benefits they bring for the process of writing and delivering new apps. But a major challenge continues to be, the how and the what when it comes to accessing, processing and getting insights from the massive amounts of data that we have to deal with in today's world. And with me are two experts from the data management world who will share with us how they think about the best techniques and practices based on what they see at large organizations who are working with data and developing so-called data-driven apps. Please welcome Maria Colgan and Gerald Venzl, two distinguish product managers from Oracle. Folks, welcome, thanks so much for coming on. >> Thanks for having us Dave. >> Thank you very much for having us. >> Okay, Maria let's start with you. So, we throw around this term data-driven, data-driven applications. What are we really talking about there? >> So data-driven applications are applications that work on a diverse set of data. So anything from spatial to sensor data, document data as well as your usual transaction processing data. And what they're going to do is they'll generate value from that data in very different ways to a traditional application. So for example, they may use machine learning, they are able to do product recommendations in the middle of a transaction. Or we could use graph to be able to identify an influencer within the community so we can target them with a specific promotion. It could also use spatial data to be able to help find the nearest stores to a particular customer. And because these apps are deployed on multiple platforms, everything from mobile devices as well as standard browsers, they need a data platform that's going to be both secure, reliable and scalable. >> Well, so when you think about how the workloads are shifting I mean, we're not talking about, you know it's not anymore a world of just your ERP or your HCM or your CRM, you know kind of the traditional operational systems. You really are seeing an explosion of these new data oriented apps. You're seeing, you know, modeling in the cloud, you are going to see more and more inferencing, inferencing at the edge. But Maria maybe you could talk a little bit about sort of the benefits that customers are seeing from developing these types of applications. I mean, why should people care about data-driven apps? >> Oh, for sure, there's massive benefits to them. I mean, probably the most obvious one for any business regardless of the industry, is that they not only allow you to understand what your customers are up to, but they allow you to be able to anticipate those customer's needs. So that helps businesses maintain that competitive edge and retain their customers. But it also helps them make data-driven decisions in real time based on actual data rather than on somebody's gut feeling or basing those decisions on historical data. So for example, you can do real-time price adjustments on products based on demand and so forth, that kind of thing. So it really changes the way people do business today. >> So Gerald, you think about the narrative in the industry everybody wants to be a platform player all your customers they are becoming software companies, they are becoming platform players. Everybody wants to be like, you know name a company that is huge trillion dollar market cap or whatever, and those are data-driven companies. And so it would seem to me that data-driven applications, there's nobody, no company really shouldn't be data-driven. Do you buy that? >> Yeah, absolutely. I mean, data-driven, and that naturally the whole industry is data-driven, right? It's like we all have information technologies about processing data and deriving information out of it. But when it comes to app development I think there is a big push to kind of like we have to do machine learning in our applications, we have to get insights from data. And when you actually look back a bit and take a step back, you see that there's of course many different kinds of applications out there as well that's not to be forgotten, right? So there is a usual front end user interfaces where really the application all it does is just entering some piece of information that's stored somewhere or perhaps a microservice that's not attached to a data to you at all but just receives or asks calls (indistinct). So I think it's not necessarily so important for every developer to kind of go on a bandwagon that they have to be data-driven. But I think it's equally important for those applications and those developers that build applications, that drive the business, that make business critical decisions as Maria mentioned before. Those guys should take really a close look into what data-driven apps means and what the data to you can actually give to them. Because what we see also happening a lot is that a lot of the things that are well known and out there just ready to use are being reimplemented in the applications. And for those applications, they essentially just ended up spending more time writing codes that will be already there and then have to maintain and debug the code as well rather than just going to market faster. >> Gerald can you talk to the prevailing approaches that developers take to build data-driven applications? What are the ones that you see? Let's dig into that a little bit more and maybe differentiate the different approaches and talk about that? >> Yeah, absolutely. I think right now the industry is like in two camps, it's like sort of a religious war going on that you'll see often happening with different architectures and so forth going on. So we have single purpose databases or data management technologies. Which are technologies that are as the name suggests build around a single purpose. So it's like, you know a typical example would be your ordinary key-value store. And a key-value store all it does is it allows you to store and retrieve a piece of data whatever that may be really, really fast but it doesn't really go beyond that. And then the other side of the house or the other camp would be multimodal databases, multimodal data management technologies. Those are technologies that allow you to store different types of data, different formats of data in the same technology in the same system alongside. And, you know, when you look at the geographics out there of what we have from technology, is pretty much any relational database or any database really has evolved into such a multimodal database. Whether that's MySQL that allows you to store or chase them alongside relational or even a MongoDB that allows you to do or gives you native graph support since (mumbles) and as well alongside the adjacent support. >> Well, it's clearly a trend in the industry. We've talked about this a lot in The Cube. We know where Oracle stands on this. I mean, you just mentioned MySQL but I mean, Oracle Databases you've been extending, you've mentioned JSON, we've got blockchain now in there you're infusing, you know ML and AI into the database, graph database capabilities, you know on and on and on. We talked a lot about we compared that to Amazon which is kind of the right tool, the right job approach. So maybe you could talk about, you know, your point of view, the benefits for developers of using that converged database if I can use that word approach being able to store multiple data formats? Why do you feel like that's a better approach? >> Yeah, I think on a high level it comes down to complexity. You are actually avoiding additional complexity, right? So not every use case that you have necessarily warrants to have yet another data management technology or yet the special build technology for managing that data, right? It's like many use cases that we see out there happily want to just store a piece of a chase and document, a piece of chase in a database and then perhaps retrieve it again afterwards so write some simple queries over it. And you really don't have to get a new database technology or a NoSQL database into the mix if you already have some to just fulfill that exact use case. You could just happily store that information as well in the database you already have. And what it really comes down to is the learning curve for developers, right? So it's like, as you use the same technology to store other types of data, you don't have to learn a new technology, you don't have to associate yourself with new and learn new drivers. You don't have to find new frameworks and you don't have to know how to necessarily operate or best model your data for that database. You can essentially just reuse your knowledge of the technology as well as the libraries and code you have already built in house perhaps in another application, perhaps, you know framework that you used against the same technology because it is still the same technology. So, kind of all comes down again to avoiding complexity rather than not fragmenting you know, the many different technologies we have. If you were to look at the different data formats that are out there today it's like, you know, you would end up with many different databases just to store them if you were to fully religiously follow the single purpose best built technology for every use case paradigm, right? And then you would just end up having to manage many different databases more than actually focusing on your app and getting value to your business or to your user. >> Okay, so I get that and I buy that by the way. I mean, especially if you're a larger organization and you've got all these projects going on but before we go back to Maria, Gerald, I want to just, I want to push on that a little bit. Because the counter to that argument would be in the analogy. And I wonder if you, I'd love for you to, you know knock this analogy off the blocks. The counter would be okay, Oracle is the Swiss Army knife and it's got, you know, all in one. But sometimes I need that specialized long screwdriver and I go into my toolbox and I grab that. It's better than the screwdriver in my Swiss Army knife. Why, are you the Swiss Army knife of databases? Or are you the all-in-one have that best of breed screwdriver for me? How do you think about that? >> Yeah, that's a fantastic question, right? And I think it's first of all, you have to separate between Oracle the company that has actually multiple data management technologies and databases out there as you said before, right? And Oracle Database. And I think Oracle Database is definitely a Swiss Army knife has many capabilities of since the last 40 years, you know that we've seen object support coming that's still in the Oracle Database today. We have seen XML coming, it's still in the Oracle Database, graph, spatial, et cetera. And so you have many different ways of managing your data and then on top of that going into the converge, not only do we allow you to store the different data model in there but we actually allow you also to, you apply all the security policies and so forth on top of it something Maria can talk more about the mission around converged database. I would also argue though that for some aspects, we do actually have to or add a screwdriver that you talked about as well. So especially in the relational world people get very quickly hung up on this idea that, oh, if you only do rows and columns, well, that's kind of what you put down on disk. And that was never true, it's the relational model is actually a logical model. What's probably being put down on disk is blocks that align themselves nice with block storage and always has been. So that allows you to actually model and process the data sort of differently. And one common example or one good example that we have that we introduced a couple of years ago was when, column and databases were very strong and you know, the competition came it's like, yeah, we have In-Memory column that stores now they're so much better. And we were like, well, orienting the data role-based or column-based really doesn't matter in the sense that we store them as blocks on disks. And so we introduced the in memory technology which gives you an In-Memory column, a representation of your data as well alongside your relational. So there is an example where you go like, well, actually you know, if you have this use case of the column or analytics all In-Memory, I would argue Oracle Database is also that screwdriver you want to go down to and gives you that capability. Because not only gives you representation in columnar, but also which many people then forget all the analytic power on top of SQL. It's one thing to store your data columnar, it's a completely different story to actually be able to run analytics on top of that and having all the built-in functionalities and stuff that you want to do with the data on top of it as you analyze it. >> You know, that's a great example, the kilometer 'cause I remember there was like a lot of hype around it. Oh, it's the Oracle killer, you know, at Vertica. Vertica is still around but, you know it never really hit escape velocity. But you know, good product, good company, whatever. Natezza, it kind of got buried inside of IBM. ParXL kind of became, you know, red shift with that deal so that kind of went away. Teradata bought a company, I forget which company it bought but. So that hype kind of disapated and now it's like, oh yeah, columnar. It's kind of like In-Memory, we've had a In-Memory databases ever since we've had databases you know, it's a kind of a feature not a sector. But anyway, Maria, let's come back to you. You've got a lot of customer experience. And you speak with a lot of companies, you know during your time at Oracle. What else are you seeing in terms of the benefits to this approach that might not be so intuitive and obvious right away? >> I think one of the biggest benefits to having a multimodel multiworkload or as we call it a converged database, is the fact that you can get greater data synergy from it. In other words, you can utilize all these different techniques and data models to get better value out of that data. So things like being able to do real-time machine learning, fraud detection inside a transaction or being able to do a product recommendation by accessing three different data models. So for example, if I'm trying to recommend a product for you Dave, I might use graph analytics to be able to figure out your community. Not just your friends, but other people on our system who look and behave just like you. Once I know that community then I can go over and see what products they bought by looking up our product catalog which may be stored as JSON. And then on top of that I can then see using the key-value what products inside that catalog those community members gave a five star rating to. So that way I can really pinpoint the right product for you. And I can do all of that in one transaction inside the database without having to transform that data into different models or God forbid, access different systems to be able to get all of that information. So it really simplifies how we can generate that value from the data. And of course, the other thing our customers love is when it comes to deploying data-driven apps, when you do it on a converged database it's much simpler because it is that standard data platform. So you're not having to manage multiple independent single purpose databases. You're not having to implement the security and the high availability policies, you know across a bunch of different diverse platforms. All of that can be done much simpler with a converged database 'cause the DBA team of course, is going to just use that standard set of tools to manage, monitor and secure those systems. >> Thank you for that. And you know, it's interesting, you talk about simplification and you are in Juan's organization so you've big focus on mission critical. And so one of the things that I think is often overlooked well, we talk about all the time is recovery. And if things are simpler, recovery is faster and easier. And so it's kind of the hallmark of Oracle is like the gold standard of the toughest apps, the most mission critical apps. But I wanted to get to the cloud Maria. So because everything is going to the cloud, right? Not all workloads are going to the cloud but everybody is talking about the cloud. Everybody has cloud first mentality and so yes, it's a hybrid world. But the natural next question is how do you think the cloud fits into this world of data-driven apps? >> I think just like any app that you're developing, the cloud helps to accelerate that development. And of course the deployment of these data-driven applications. 'Cause if you think about it, the developer is instantly able to provision a converged database that Oracle will automatically manage and look after for them. But what's great about doing something like that if you use like our autonomous database service is that it comes in different flavors. So you can get autonomous transaction processing, data warehousing or autonomous JSON so that the developer is going to get a database that's been optimized for their specific use case, whatever they are trying to solve. And it's also going to contain all of that great functionality and capabilities that we've been talking about. So what that really means to the developer though is as the project evolves and inevitably the business needs change a little, there's no need to panic when one of those changes comes in because your converged database or your autonomous database has all of those additional capabilities. So you can simply utilize those to able to address those evolving changes in the project. 'Cause let's face it, none of us normally know exactly what we need to build right at the very beginning. And on top of that they also kind of get a built-in buddy in the cloud, especially in the autonomous database. And that buddy comes in the form of built-in workload optimizations. So with the autonomous database we do things like automatic indexing where we're using machine learning to be that buddy for the developer. So what it'll do is it'll monitor the workload and see what kind of queries are being run on that system. And then it will actually determine if there are indexes that should be built to help improve the performance of that application. And not only does it bill those indexes but it verifies that they help improve the performance before publishing it to the application. So by the time the developer is finished with that app and it's ready to be deployed, it's actually also been optimized by the developers buddy, the Oracle autonomous database. So, you know, it's a really nice helping hand for developers when they're building any app especially data-driven apps. >> I like how you sort of gave us, you know the truth here is you don't always know where you're going when you're building an app. It's like it goes from you are trying to build it and they will come to start building it and we'll figure out where it's going to go. With Agile that's kind of how it works. But so I wonder, can you give some examples of maybe customers or maybe genericize them if you need to. Data-driven apps in the cloud where customers were able to drive more efficiency, where the cloud buddy allowed the customers to do more with less? >> No, we have tons of these but I'll try and keep it to just a couple. One that comes to mind straight away is retrace. These folks built a blockchain app in the Oracle Cloud that allows manufacturers to actually share the supply chain with the consumer. So the consumer can see exactly, who made their product? Using what raw materials? Where they were sourced from? How it was done? All of that is visible to the consumer. And in order to be able to share that they had to work on a very diverse set of data. So they had everything from JSON documents to images as well as your traditional transactions in there. And they store all of that information inside the Oracle autonomous database, they were able to build their app and deploy it on the cloud. And they were able to do all of that very, very quickly. So, you know, that ability to work on multiple different data types in a single database really helped them build that product and get it to market in a very short amount of time. Another customer that's doing something really, really interesting is MindSense. So these guys operate the largest mines in Canada, Chile, and Peru. But what they do is they put these x-ray devices on the massive mechanical shovels that are at the cove or at the mine face. And what that does is it senses the contents of the buckets inside these mining machines. And it's looking to see at that content, to see how it can optimize the processing of the ore inside in that bucket. So they're looking to minimize the amount of power and water that it's going to take to process that. And also of course, minimize the amount of waste that's going to come out of that project. So all of that sensor data is sent into an autonomous database where it's going to be processed by a whole host of different users. So everything from the mine engineers to the geo scientists, to even their own data scientists utilize that data to drive their business forward. And what I love about these guys is they're not happy with building just one app. MindSense actually use our built-in low core development environment, APEX that comes as part of the autonomous database and they actually produce applications constantly for different aspects of their business using that technology. And it's actually able to accelerate those new apps to the business. It takes them now just a couple of days or weeks to produce an app instead of months or years to build those new apps. >> Great, thank you for that Maria. Gerald, I'm going to push you again. So, I said upfront and talked about microservices and the cloud and containers and you know, anybody in the developer space follows that very closely. But some of the things that we've been talking about here people might look at that and say, well, they're kind of antithetical to microservices. This is our Oracles monolithic approach. But when you think about the benefits of microservices, people want freedom of choice, technology choice, seen as a big advantage of microservices and containers. How do you address such an argument? >> Yeah, that's an excellent question and I get that quite often. The microservices architecture in general as I said before had architectures, Linux distributions, et cetera. It's kind of always a bit of like there's an academic approach and there's a pragmatic approach. And when you look at the microservices the original definitions that came out at the early 2010s. They actually never said that each microservice has to have a database. And they also never said that if a microservice has a database, you have to use a different technology for each microservice. Just like they never said, you have to write a microservice in a different programming language, right? So where I'm going with this is like, yes you know, sometimes when you look at some vendors out there, some niche players, they push this message or they jump on this academic approach of like each microservice has the best tool at hand or I'd use a different database for your purpose, et cetera. Which almost often comes across like us. You know, we want to stay part of the conversation. Nothing stops a developer from, you know using a multimodal database for the microservice and just using that as a document store, right? Or just using that as a relational database. And, you know, sometimes I mean, it was actually something that happened that was really interesting yesterday I don't know whether you follow Dave or not. But Facebook had an outage yesterday, right? And Facebook is one of those companies that are seen as the Silicon Valley, you know know how to do microservices companies. And when you add through the outage, well, what happened, right? Some unfortunate logical error with configuration as a force that took a database cluster down. So, you know, there you have it where you go like, well, maybe not every microservice is actually in fact talking to its own database or its own special purpose database. I think there, you know, well, what we should, the industry should be focusing much more on this argument of which technology to use? What's the right tool for a job? Is more to ask themselves, what business problem actually are we trying to solve? And therefore what's the right approach and the right technology for this. And so therefore, just as I said before, you know multimodal databases they do have strong benefits. They have many built-in functionalities that are already there and they allow you to reduce this complexity of having to know many different technologies, right? And so it's not only to store different data models either you know, treat a multimodal database as a chasing documents store or a relational database but most databases are multimodal since 20 plus years. But it's also actually being able to perhaps if you store that data together, you can perhaps actually derive additional value for somebody else but perhaps not for your application. But like for example, if you were to use Oracle Database you can actually write queries on top of all of that data. It doesn't really matter for our query engine whether it's the data is format that then chase or the data is formatted in rows and columns you can just rather than query over it. And that's actually very powerful for those guys that have to, you know get the reporting done the end of the day, the end of the week. And for those guys that are the data scientists that they want to figure out, you know which product performed really well or can we tweak something here and there. When you look into that space you still see a huge divergence between the guys to put data in kind of the altarpiece style and guys that try to derive new insights. And there's still a lot of ETL going around and, you know we have big data technologies that some of them come and went and some of them came in that are still around like Apache Spark which is still like a SQL engine on top of any of your data kind of going back to the same concept. And so I will say that, you know, for developers when we look at microservices it's like, first of all, is the argument you were making because the vendor or the technology you want to use tells you this argument or, you know, you kind of want to have an argument to use a specific technology? Or is it really more because it is the best technology, to best use for this given use case for this given application that you have? And if so there's of course, also nothing wrong to use a single purpose technology either, right? >> Yeah, I mean, whenever I talk about Oracle I always come back to the most important applications, the mission critical. It's very difficult to architect databases with microservices and containers. You have to be really, really careful. And so and again, it comes back to what we were talking before about with Maria that the complexity and the recovery. But Gerald I want to stay with you for a minute. So there's other data management technologies popping out there. I mean, I've seen some people saying, okay just leave the data in an S3 bucket. We can query that, then we've got some magic sauce to do that. And so why are you optimistic about you know, traditional database technology going forward? >> I would say because of the history of databases. So one thing that once struck me when I came to Oracle and then got to meet great people like Juan Luis and Andy Mendelsohn who had been here for a long, long time. I come to realization that relational databases are around for about 45 years now. And, you know, I was like, I'm too young to have been around then, right? So I was like, what else was around 45 years? It's like just the tech stack that we have today. It's like, how does this look like? Well, Linux only came out in 93. Well, databases pre-date Linux a lot rather than as I started digging I saw a lot of technologies come and go, right? And you mentioned before like the technologies that data management systems that we had that came and went like the columnar databases or XML databases, object databases. And even before relational databases before Cot gave us the relational model there were apparently these networks stores network databases which to some extent look very similar to adjacent documents. There wasn't a harder storing data and a hierarchy to format. And, you know when you then start actually reading the Cot paper and diving a little bit more into the relation model, that's I think one important crux in there that most of the industry keeps forgetting or it hasn't been around to even know. And that is that when Cot created the relational model, he actually focused not so much on the application putting the data in, but on future users and applications still being able to making sense out of the data, right? And that's kind of like I said before we had those network models, we had XML databases you have adjacent documents stores. And the one thing that they all have along with it is like the application that puts the data in decides the structure of the data. And that's all well and good if you had an application of the developer writing an application. It can become really tricky when 10 years later you still want to look at that data and the application that the developer is no longer around then you go like, what does this all mean? Where is the structure defined? What is this attribute? What does it mean? How does it correlate to others? And the one thing that people tend to forget is that it's actually the data that's here to stay not someone who does the applications where it is. Ideally, every company wants to store every single byte of data that they have because there might be future value in it. Economically may not make sense that's now much more feasible than just years ago. But if you could, why wouldn't you want to store all your data, right? And sometimes you actually have to store the data for seven years or whatever because the laws require you to. And so coming back then and you know, like 10 years from now and looking at the data and going like making sense of that data can actually become a lot more difficult and a lot more challenging than having to first figure out and how we store this data for general use. And that kind of was what the relational model was all about. We decompose the data structures into tables and columns with relationships amongst each other so therefore between each other. So that therefore if somebody wants to, you know typical example would be well you store some purchases from your web store, right? There's a customer attribute in it. There's some credit card payment information in it, just some product information on what the customer bought. Well, in the relational model if you just want to figure out which products were sold on a given day or week, you just would query the payment and products table to get the sense out of it. You don't need to touch the customer and so forth. And with the hierarchical model you have to first sit down and understand how is the structure, what is the customer? Where is the payment? You know, does the document start with the payment or does it start with the customer? Where do I find this information? And then in the very early days those databases even struggled to then not having to scan all the documents to get the data out. So coming back to your question a bit, I apologize for going on here. But you know, it's like relational databases have been around for 45 years. I actually argue it's one of the most successful software technologies that we have out there when you look in the overall industry, right? 45 years is like, in IT terms it's like from a star being the ones who are going supernova. You have said it before that many technologies coming and went, right? And just want to add a more really interesting example by the way is Hadoop and HDFS, right? They kind of gave us this additional promise of like, you know, the 2010s like 2012, 2013 the hype of Hadoop and so forth and (mumbles) and HDFS. And people are just like, just put everything into HDFS and worry about the data later, right? And we can query it and map reduce it and whatever. And we had customers actually coming to us they were like, great we have half a petabyte of data on an HDFS cluster and we have no clue what's stored in there. How do we figure this out? What are we going to do now? Now you had a big data cleansing problem. And so I think that is why databases and also data modeling is something that will not go away anytime soon. And I think databases and database technologies are here for quite a while to stay. Because many of those are people they don't think about what's happening to the data five years from now. And many of the niche players also and also frankly even Amazon you know, following with this single purpose thing is like, just use the right tool for the job for your application, right? Just pull in the data there the way you wanted. And it's like, okay, so you use technologies all over the place and then five years from now you have your data fragmented everywhere in different formats and, you know inconsistencies, and, and, and. And those are usually when you come back to this data-driven business critical business decision applications the worst case scenario you can have, right? Because now you need an army of people to actually do data cleansing. And there's not a coincidence that data science has become very, very popular the last recent years as we kind of went on with this proliferation of different database or data management technologies some of those are not even database. But I think I leave it at that. >> It's an interesting talk track because you're right. I mean, no schema on right was alluring, but it definitely created some problems. It also created an entire, you know you referenced the hyper specialized roles and did the data cleansing component. I mean, maybe technology will eventually solve that problem but it hasn't up at least up tonight. Okay, last question, Maria maybe you could start off and Gerald if you want to chime in as well it'd be great. I mean, it's interesting to watch this industry when Oracle sort of won the top database mantle. I mean, I watched it, I saw it. It was, remember it was Informix and it was (indistinct) too and of course, Microsoft you got to give them credit with SQL server, but Oracle won the database wars. And then everything got kind of quiet for awhile database was sort of boring. And then it exploded, you know, all the, you know not only SQL and the key-value stores and the cloud databases and this is really a hot area now. And when we looked at Oracle we said, okay, Oracle it's all about Oracle Database, but we've seen the kind of resurgence in MySQL which everybody thought, you know once Oracle bought Sun they were going to kill MySQL. But now we see you investing in HeatWave, TimesTen, we talked about In-Memory databases before. So where do those fit in Maria in the grand scheme? How should we think about Oracle's database portfolio? >> So there's lots of places where you'd use those different things. 'Cause just like any other industry there are going to be new and boutique use cases that are going to benefit from a more specialized product or single purpose product. So good examples off the top of my head of the kind of systems that would benefit from that would be things like a stock exchange system or a telephone exchange system. Both of those are latency critical transaction processing applications where they need microsecond response times. And that's going to exceed perhaps what you might normally get or deploy with a converged database. And so Oracle's TimesTen database our In-Memory database is perfect for those kinds of applications. But there's also a host of MySQL applications out there today and you said it yourself there Dave, HeatWave is a great place to provision and deploy those kinds of applications because it's going to run 100 times faster than AWS (mumbles). So, you know, there really is a place in the market and in our customer's systems and the needs they have for all of these different members of our database family here at Oracle. >> Yeah, well, the internet is basically running in the lamp stack so I see MySQL going away. All right Gerald, will give you the final word, bring us home. >> Oh, thank you very much. Yeah, I mean, as Maria said, I think it comes back to what we discussed before. There is obviously still needs for special technologies or different technologies than a relational database or multimodal database. Oracle has actually many more databases that people may first think of. Not only the three that we have already mentioned but there's even SP so the Oracle's NoSQL database. And, you know, on a high level Oracle is a data management company, right? And we want to give our customers the best tools and the best technology to manage all of their data. Rather than therefore there has to be a need or there should be a part of the business that also focuses on this highly specialized systems and this highly specialized technologies that address those use cases. And I think it makes perfect sense. It's like, you know, when the customer comes to Oracle they're not only getting this, take this one product you know, and if you don't like it your problem but actually you have choice, right? And choice allows you to make a decision based on what's best for you and not necessarily best for the vendor you're talking to. >> Well guys, really appreciate your time today and your insights. Maria, Gerald, thanks so much for coming on The Cube. >> Thank you very much for having us. >> And thanks for watching this Cube conversation this is Dave Vellante and we'll see you next time. (upbeat music)