>>Hello, and welcome back to the live cube coverage here in San Francisco, California, the cube live coverage. Two days, day two of a summit 2022, a summit New York city coming up in the summer. We'll be there as well. Events are back. I'm the host, John fur, the cube got great guest here, Johnny Dallas with Ze. Um, here's on the cube. We're gonna talk about his background. Uh, little trivia here. He was the youngest engineer ever worked at Amazon at the age. 17 had to get escorted into reinvent in Vegas cause he was underage <laugh> with security, all good stories. Now the CEO of gonna called Ze know DevOps kind of focus, managed service, a lot of cool stuff, John, welcome to the cube. >>Thanks John. Great. >>So tell a story. You were the youngest engineer at AWS. >>I was, yes. So I used to work at a company called Bebo. I got started very young. I started working when I was about 14, um, kind of as a software engineer. And when I, uh, was about 16, I graduated out of high school early. Um, worked at this company, Bebo running all of the DevOps at that company. Um, I went to reinvent in about 2018 to give a talk about some of the DevOps software I wrote at that company. Um, but you know, as many of those things are probably familiar with reinvent happens in a casino and I was 16, so I was not able to actually go into the casino on my own <laugh> um, so I'd have <inaudible> security as well as C security escort me in to give my talk. >>Did Andy jazzy, was he aware of this? >>Um, you know, that's a great question. I don't know. <laugh> >>I'll ask him great story. So obviously you started a young age. I mean, it's so cool to see you jump right in. I mean, I mean, you never grew up with the old school that I used to grew up in loading package software, loading it onto the server, deploying it, plugging the cables in, I mean you just rocking and rolling with DevOps as you look back now what's the big generational shift because now you got the Z generation coming in, millennials are in the workforce. It's changing. Like no one's putting package software on servers. >>Yeah, no, I mean the tools keep getting better, right? We, we keep creating more abstractions that make it easier and easier. When I, when I started doing DevOps, I could go straight into E two APIs. I had APIs from the get go and you know, my background was, I was a software engineer. I never went through like the CIS admin stack. I, I never had to, like you said, rack servers, myself. I was immediately able to scale to I, I was managing, I think 2,500 concurrent servers across every Ables region through software. It was a fundamental shift. >>Did you know what an SRE was at that time? Uh, you were kind of an SRE on >>Yeah, I was basically our first SRE, um, familiar with the, with the phrasing, but really thought of myself as a software engineer who knows cloud APIs, not a SRE. >>All right. So let's talk about what's what's going on now, as you look at the landscape today, what's the coolest thing that's going on in your mind and cloud? >>Yeah, I think the, I think the coolest thing is, you know, we're seeing the next layer of those abstraction tools exist and that's what we're doing with Ze is we've basically gone and we've, we're building an app platform that deploys onto your cloud. So if you're familiar with something like Carku, um, where you just click a GitHub repo, uh, we actually make it that easy. You click a GI hub repo and it'll deploy on a AWS using Al AWS tools. >>So, right. So this is Z. This is the company. Yes. How old's the company >>About a year and a half old now. >>Right. So explain what it does. >>Yeah. So we make it really easy for any software engineer to deploy on a AWS. Um, that's not SREs. These are the actual application engineers doing the business logic. Mm-hmm <affirmative> they don't really want to think about Yamo. They don't really want to configure everything super deeply. Um, they want to say, run this API on a AWS in the best way possible. We've encoded all the best practices into software and we set it up for you. >>Yeah. So I think the problem you're solving is, is that there's a lot of want to be DevOps engineers. And then they realize, oh shit, I don't wanna do this. Yeah. And the people want to do it. They loved under the hood. Right. People love that infrastructure, but the average developer needs to actually be as agile on scale. So that seems to be the problem you solve. Right? Yeah. >>We, we, we give way more productivity to each individual engineer, you know? >>All right. So let me ask you a question. So let me just say, I'm a developer. Cool. I built this new app. It's a streaming app or whatever. I'm making it up cube here, but let's just say I deploy it. I need your service. But what happens about when my customers say, Hey, what's your SLA? The CDN went down from this it's flaky. Does Amazon have? So how do you handle all that SLA reporting that Amazon provides? Cause they do a good job with sock reports all through the console. But as you start getting into DevOps and sell your app, mm-hmm <affirmative> you have customer issues. You, how do you view that? Yeah, >>Well, I, I think you make a great point of AWS has all this stuff already. AWS has SLAs. AWS has contract. Aw, has a lot of the tools that are expected. Um, so we don't have to reinvent the wheel here. What we do is we help people get to those SLAs more easily. So, Hey, this is a AWS SLA as a default. Um, Hey, we'll configure your services. This is what you can expect here. Um, but we can really leverage AWS reli ability of you don't have to trust us. You have to trust S and trust that the setup is good there. >>Do you handle all the recovery or mitigation between, uh, identification say downtime for instance, oh, the servers not 99% downtime, uh, went down for an hour, say something's going on? And is there a service dashboard? How does it get what's the remedy? Do you have, how does all that work? >>Yeah, so we have some built in remediation. You know, we, we basically say we're gonna do as much as we can to keep your endpoint up 24 7 mm-hmm <affirmative>. If it's something in our control, we'll do it. If it's a disc failure, that's on us. If you push bad code, we won't put out that new version until it's working. Um, so we do a lot to make sure that your endpoint stays up, um, and then alert you if there's a problem that we can't fix. So cool. Hey, S has some downtime, this thing's going on. You need to do this action. Um, we'll let you know. >>All right. So what do you do for fun? >>Yeah, so, uh, for, for fun, um, a lot of side projects. <laugh>, uh, >>What's your side hustle right now. You got going on >>The, uh, it's a lot of schools playing >>With serverless. >>Yeah. Playing with a lot of serverless stuff. Um, I think there's a lot of really cool Lam stuff as well, going on right now. Um, I love tools is, is the truest answer is I love building something that I can give to somebody else. And they're suddenly twice as productive because of it. Um, >>That's a good feeling, isn't it? Oh >>Yeah. There's nothing >>Like that. Tools versus platforms. Mm-hmm, <affirmative>, you know, the expression, too many tools in the tool, she becomes, you know, tools for all. And then ultimately tools become platforms. What's your view on that? Because if a good tool works and starts to get traction, you need to either add more tools or start building a platform platform versus tool. What's your, what's your view on our reaction to that kind of concept debate? >>Yeah, it's a good question. Uh, we we've basically started as like a, a platform. First of we've really focused on these, uh, developers who don't wanna get deep into the DevOps. And so we've done all of the piece of the stacks. We do C I C D management. We do container orchestration, we do monitoring. Um, and now we're, spliting those up into individual tools so they can be used awesome in conjunction more. >>Right. So what are some of the use cases that you see for your service? It's DevOps basically nano service DevOps for people on a DevOps team. Do clients have a DevOps person and then one person, two people what's the requirements to run >>Z? Yeah. So we we've got teams, um, from no DevOps is kind of when they start and then we've had teams grow up to about, uh, five, 10 man DevOps teams. Mm-hmm <affirmative> um, so, you know, as more structured people come in, because we're in your cloud, you're able to go in and configure it on top you're we can't block you. Uh, you wanna use some new AOL service. You're welcome to use that alongside the stack that we deploy for >>You. How many customers do you have now? >>So we've got about 40 companies that are using us for all of their infrastructure, um, kind of across the board, um, as well as >>What's the pricing model. >>Uh, so our pricing model is we, we charge basically similar to an engineer salary. So we charge, uh, a monthly rate. We have plans at 300 bucks a month, a thousand bucks a month, and then enterprise plan for based >>On the requirement scale. Yeah. You know, so back into the people cost, you must offer her discounts, not a fully loaded thing, is it? >>Yeah. There's a discounts kind of at scale, >>Then you pass through the Amazon bill. >>Yeah. So our customers actually pay for the Amazon bill themselves. Oh. So >>They have their own >>Account. There's no margin on top. You're linking your Aless account in, um, it, which is huge because we can, we are now able to help our customers get better deals with Amazon. Um, got it. We're incentivized on their team to drive your cost down. >>And what's your unit main unit of economics software scale. >>Yeah. Um, yeah, so we, we think of things as projects. How many services do you have to deploy as that scales up? Um, awesome. >>All right. You're 20 years old now you not even can't even drink legally. <laugh> what are you gonna do when you're 30? We're gonna be there. >>Well, we're, uh, we're making it better. And >>The better, the old guy on the cube here. >><laugh> I think, uh, I think we're seeing a big shift of, um, you know, we've got these major clouds. AWS is obviously the biggest cloud. Um, and it's constantly coming out with new services. Yeah. But we're starting to see other clouds have built many of the common services. So Kubernetes is a great example. It exists across all the clouds. Um, and we're starting to see new platforms come up on top that allow you to leverage tools from multiple clouds. At the same time. Many of our customers actually have AWS as their primary cloud and they'll have secondary clouds or they'll pull features from other clouds into AWS, um, through our software. I think that I'm very excited by that. And I, uh, expect to be working on that when I'm 30. Awesome. >>Well, you gonna have a good future. I gotta ask you this question cuz uh, you know, I've always, I was a computer science undergraduate in the, in the eighties and um, computer science back then was hardcore, mostly systems OS stuff, uh, database compiler. Um, now there's so much compi, right? So mm-hmm <affirmative> how do you look at the high school college curriculum experience slash folks who are nerding out on computer science? It's not one or two things much. You've got a lot of, a lot of things. I mean, look at Python, data engineering, merging as a huge skill. What's it? What's it like for college kids now and high school kids? What, what do you think they should be doing if you had to give advice to your 16 year old self back a few years ago now in college? Um, I mean Python's not a great language, but it's super effective for coding and the data's really relevant, but it's you got other language opportunities, you got tools to build. So you got a whole culture of young builders out there. What should, what should people gravitate to in your opinion stay away from yeah. Or >>Stay away from that's a good question. I, I think that first of all, you're very right of the, the amount of developers is increasing so quickly. Um, and so we see more specialization. That's why we also see, you know, these SREs that are different than typical application engineering. You get more specialization in job roles. Um, I think if, what I'd say to my 16 year old self is do projects, um, the, I learned most of my, what I've learned just on the job or online trying things, playing with different technologies, actually getting stuff out into the world, um, way more useful than what you'll learn in kind of a college classroom. I think classrooms great to, uh, get a basis, but you need to go out and experiment actually try things. >>You know? I think that's great advice. In fact, I would just say from my experience of doing all the hard stuff and cloud is so great for just saying, okay, I'm done, I'm abandoning the project. Move on. Yeah. Because you know, it's not gonna work in the old days. You have to build this data center. I bought all this certain, you know, people hang on to the old, you know, project and try to force it out there. >>You can launch a project, >>Can see gratification, it ain't working <laugh> or this is shut it down and then move on to something new. >>Yeah, exactly. Instantly you should be able to do that much more quickly. Right. >>So you're saying get those projects and don't be afraid to shut it down. Mm-hmm <affirmative> that? Do you agree with that? >>Yeah. I think it's ex experiment. Um, you're probably not gonna hit it rich on the first one. It's probably not gonna be that idea is DJing me this idea. So don't be afraid to get rid of things and just try over and over again. It's it's number of reps that a win. >>I was commenting online. Elon Musk was gonna buy Twitter, that whole Twitter thing. And, and, and someone said, Hey, you know, what's the, I go look at the product group at Twitter's been so messed up because they actually did get it right on the first time <laugh> and, and became such a great product. They could never change it because people would freak out and the utility of Twitter. I mean, they gotta add some things, the added button and we all know what they need to add, but the product, it was just like this internal dysfunction, the product team, what are we gonna work on? Don't change the product so that you kind of have there's opportunities out there where you might get the lucky strike, right. Outta the gate. Yeah. Right. You don't know, >>It's almost a curse too. It's you're not gonna Twitter. You're not gonna hit a rich second time too. So yeah. >><laugh> Johnny Dallas. Thanks for coming on the cube. Really appreciate it. Give a plug for your company. Um, take a minute to explain what you're working on, what you're looking for. You're hiring funding. Customers. Just give a plug, uh, last minute and have the last word. >>Yeah. So, um, John Dallas from Ze, if you, uh, need any help with your DevOps, if you're a early startup, you don't have DevOps team, um, or you're trying to deploy across clouds, check us out ze.com. Um, we are actively hiring. So if you are a software engineer excited about tools and cloud, or you're interested in helping getting this message out there, hit me up. Um, find a Z. >>Yeah. LinkedIn Twitter handle GitHub handle. >>Yeah. I'm the only Johnny on a LinkedIn and GitHub and underscore Johnny Dallas underscore on Twitter. Right? Um, >>Johnny Dallas, the youngest engineer working at Amazon. Um, now 20 we're on great new project here. The cube builders are all young. They're growing in to the business. They got cloud at their, at their back it's, uh, tailwind. I wish I was 20. Again, this is a cue. I'm John for your host. Thanks for watching. >>Thanks.

>>live from Copenhagen, Denmark. It's the Q covering Nutanix dot next 2019. Brought to you by Nutanix >>Welcome back, everyone to the cubes. Live coverage of Nutanix dot Next here at the Bella Centre in the Copenhagen. I'm your host, Rebecca Knight, coasting along side of stew, Minutemen were joined by Bala Coochie bottler >>Bhola. He is the VP GM Nutanix era and business critical lapse at Nutanix. Thanks so much for coming on the island. >>It's an honor to come here and talk to guys. >>So you were up on the main stage this morning. You did a fantastic job doing some demos for us. But up there you talked about your data, your days gold. And you said there are four p's thio the challenges of mining the burning process you want >>you want to go through >>those for our viewers? >>Definitely. So for every business, critical lab data is gold likely anam bigness for a lot of people are anyone. Now the question is like similar to how the gore gets processed and there's a lot of hazardous mining that happens and process finally get this processed gold. To me, the data is also very similar for business could collapse. Little database systems will be processed in a way to get the most efficient, elegant way of getting the database back data back. No. The four pains that I see for managing data businesses started provisioning even today. Some of his biggest companies that I talkto they take about 3 to 5 weeks toe provisions. A database. It goes from Infrastructure team. The ticket passes from infrastructure team, computer, networking stories, toe database team and the database administration team. That's number one silo. Number two is like proliferation, and it's very consistent, pretty much every big company I talkto there. How about 8 to 10 copies of the data for other analytics que year development staging Whatever it is, it's like over you take a photo and put it on. What Step and your friends download it. They're basically doing a coffee data. Essentially, that Fordham be becomes 40 and in no time in our what's up. It's the same thing that happens for databases, data bits gets cloned or if it's all the time. But this seemingly simple, simple operation off over Clone Copy copy paste operation becomes the most dreaded, complex long running error prone process. And I see that dedicated Devi is just doing Tony. That's another thing. And then lineage problem that someone is cloning the data to somewhere. I don't know where the data is coming from. Canister in The third pain that we talk about is the protection. Actually, to me it's like a number one and number two problem, but I was just putting it in the third. If you're running daily basis, and if you're running it for Mission critical data basis, your ability to restore the rhythm is to any point in time. It's an absolute must write like otherwise, you're not even calling The database. Question is, Are the technologies don't have this kind of production technology? Are they already taken care? They did already, but the question is on our new town expert from Are on Cloud platform. Can they be efficient and elegant? Can we can we take out some of the pain in this whole process? That's what we're talking about. And the last one is, ah, big company problem. Anyone who has dozens of databases can empathize with me how painful it is to patch how painful it is to get up get your complaints going to it. Holy Manager instead driven database service, this kind of stuff. So these are the four things that we actually think that if you solve them, your databases are one step. Are much a lot steps closer to database service. That's what I see >>Bala. It's interesting. You know, you spent a lot of time working for, you know, the big database company out there. There is no shortage of options out there for databases. When I talked to most enterprises, it's not one database they now have, you know, often dozens of databases that they have. Um so explain line. Now you know, there's still an unmet need in the marketplace that Nutanix is looking to help fill there. >>So you're absolutely right on the dark that there are lots of date of this technology is actually that compounds the problem because all these big enterprise companies that are specially Steadman stations for Oracle Post Grace may really be my sequel sequel administrator. Now they're new breed of databases in no sequel monger leave. You know, it's it's like Hardy Man is among really be somebody manage the Marta logics and stuff like that so no, we I personally eating their databases need to become seemed like Alex City. Right? So >>most of >>these banks and telcos all the company that we talk about data this is just a means to an end for them. So there should focus on the business logic. Creating those business value applications and databases are more like okay, I can just manage them with almost no touch Aghanistan. But whether these technologies that were created around 20 years back are there, there it kind of stopped. So that is what we're trying to talk about when you have a powerful platform like Nutanix that actually abstracts the stories and solve some of the fundamental problems for database upstream technologies to take advantage of. We combine the date of this FBI's the render A P s as well as the strength of the new tenants platform to give their simplicity. Essentially. So that's what I see. We're not inventing. New databases were trying to simplify the database. If that's what >>you and help make sure we understand that you know, Nutanix isn't just building the next great lock in, you know, from top to bottom. You know, Nutanix can provide it. But Optionality is a word that Nutanix way >>live and time by choice and freedom for the customers. In fact, I make this as one of the fundamental design principles, even for era we use. AP is provided with the database vendors, for example, for our men, we just use our men. AP is. We start the database in the backup, using our many years where we take that one day. It is the platform. Once the database in the backup more we're taking snapshots of the latest visit is pretty much like our men. Regan back up with a Miss based backup, essentially alchemist, so the customer is not locked in the 2nd 1 is if the customer wants to go to the other clothes are even other technologies kind of stuff? We will probably appear just kind of migrate. So that's one of the thing that I want to kind of emphasize that we're not here to lock in any customer. In fact, your choice is to work. In fact, I emphasize, if the customer has the the computer environment on the year six were more than happy weaken. Some 40 year six are his feet both are equal for us. All we need is the air weighs on era because it was is something that we leverage a lot off platform patent, uh, repentance of Nutanix technology that we're passing on the benefits canister down the road where we're trying to see is we'll have cyclists and AWS and DCP. And as you and customers can move databases from unpromising private cloud platform through hybrid cloud to other clusters and then they can bring back the data business. That's what we can to protect the customers. Investment. >>Yeah. I mean, I'm curious. Your commentary. When you go listen, toe the big cloud player out there. It's, you know, they tell you how many hundreds of thousands of databases they've migrated. When I talk to customers and they think about their workload, migrations are gonna come even more often, and it's not a one way thing. It's often it's moving around and things change. So can we get there for the database? Because usually it's like, Well, it isn't it easier for me to move my computer to my data. You know, data has gravity. You know, there's a lot of, you know, physics. Tell General today. >>See what what is happening with hyper killers is. They're asking the applications. Toby return against clothed native databases, obviously by if you are writing an application again, it's chlorinated. Databases say there are Are are are even DCP big table. You're pretty much locked technical because further obligation to come back down from there is no view. There's no big table on and there's no one around. Where is what we're trying to say is the more one APS, the oracles the sequels were trying to clarify? We're trying to bring the simplicity of them, so if they can run in the clover, they condone an art crime. So that's how we protect the investment, that there is not much new engineering that needs to be done for your rafts as is, we can move them. Only thing is, we're taking or the pain off mobility leveraging all platform. So obviously we can run your APS, as is Oracle applications on the public lower like oracle, and if you feel like you want to do it on on from, we can do it on the impromptu canister so and to protect the investment for the customers, we do have grown feeling this man, That means that you can How did a bee is running on your ex editor and you can do capacity. Mediation means tier two tier three environments on Nutanix using our time mission technology. So we give the choicest customers >>So thinking about this truly virtualized d be what is what some of the things you're hearing from customers here a dot next Copenhagen. What are the things that you were they there, There there Pain points. I mean, in addition to those four peas. But what are some of the next generation problems that you're trying to solve here? >>So that first awful for the customers come in acknowledges way that this is a true database. Which letters? I don't know what happened is what tradition is all aboard compute. And when when he saw the computer watch logician problem you threw in database server and then try to run the databases. You're not really solving the problem of the data? No, With Nutanix, our DNA is in data. So we have started our pioneered the storage, which location and then extended to the files and objects. Now we're extending into database making that application Native Watch Ladies database for dilation, leveraging the story published Combining that with Computer. What's litigation? We think that we have made an honest effort to watch less data basis. Know the trend that I see is Everyone is moving. Our everyone wants cloudlike experience. It's not like they want to go to club, but they want the cloud like agility, that one click simplicity, consumer, great experience for the data basis, I would liketo kind of manage my data basis in self service matter. So we took both these dimensions. We made a great we made an honest effort to make. The databases are truly watch list. That's the copy data management and olive stuff and then coupled with how cloud works able to tow provisions. Self service way ability to manage your backups in self service. Weigh heavily to do patch self service fair and customers love it, and they want to take us tow new engines. One of the other thing that we see beget Bronte's with ERA is Chloe's. Olive or new databases generally are the post press and the cancer, but there's a lot of data on site because there's a lot of data on Mississippi. Honey, there's a lot of data on TV, too. Why don't we enjoy the same kind of experience for those databases? What? What did they do wrong? So can we >>give >>those experience the cloud like experience and then true? Watch allegation for those databases on the platform. That's what customers ask What kind of stuff. Obviously, they will have asked for more and more, um, br kind of facilities and other stuff that way there in the road map that we will be able to take it off. One >>of the questions we've had this week as Nutanix build out some of these application software not just infrastructure software pieces, go to market tends to be a little bit different. We had an interesting conversation with the Pro. They're wrapping the service for a row so that that seems like a really good way to be able to reach customers that might not even knew no Nutanix tell us, you know, how is that going? Is there an overlay? Salesforce's it? Some of the strategic channel and partnership engagements, you know, because this is not the traditional Nutanix, >>So obviously Nutanix is known. Andi made its name and fame for infrastructure as service. So it's really a challenge to talk about database language for our salespeople. But country that I heard the doubt when I kind of started my journey It Nutanix Okay, we will build a product. But how are you going to the city? And we get off this kind of sales for But believe me, we're making multimillion dollar deals mainly led by the application Native Miss our application centric nous so I could talk about federal governments. And yes, she made perches because it was a different station for them. We're talking about big telco company in Europe trying to replace their big Internet appliances because era makes the difference vanished. We're providing almost two X value almost half the price. So the pain point is real. Question is, can we translate their token reconnect with the right kind of customer? So we do have a cell so early for my division. They speak database language. Obviously we're very early in the game, so we will have selected few people in highly dense are important geographic regions who after that, but I also work with channels, work with apartments like geniuses like we prove head steal another kind of stuff and down the best people to leverage and take this holding and practice. This is the solution. In fact, companies like GE S D s is like people take an offer. Managed database seven. Right. So we have a product. People can build a cloud with it. But with the pro they can offer in a word, why do you want to go to public Lower? I can provide the same cloud. Man is database service more on our picks, Mortal kind of stuff. So we're kind of off fighting on all cylinders in this sense, but very selectively very focused. And I really believe that customers fill understand this, Mrs, that Nutanix is not just the infrastructure, but it's a cloud. It's a It's a club platform where I considered arise like Microsoft Office Suite on Microsoft's operating system. Think about that. That's the part off full power that we think that I can make make it happen >>and who are you know, you said you're going in very tight. Who are these Target customers without naming names? But what kinds of businesses are they? You know? How big are they? What kinds of challenges. Are >>they looking at all? The early customers were hardly in the third quarter of the business, but five. Financial sector is big. The pain point of data mismanagement is so acute there capacity limitation is a huge thing. They are spending hundreds of millions of dollars on this big. When that kind of stuff on can they run in the can extract efficiencies out of this hole all their investment. Second thing is manufacturing and tell Cole, and obviously federal is one of the biggest friend of Nutanix and I happened to pitch in and religions is loaded. And they said, Israel, let's do it real demo. And then let's make it happen. They actually tested the product and there are taking it. So the e r piece, where are they? Run Oracle, Where the run big sequence kind of stuff. This is what we're seeing. It >>followed. Wanna make sure there was a bunch of announcements about era tudo Otto, Just walk us through real quick kind of where we are today. And what should we be looking for? Directionally in the future. >>So we started out with four are five engines. Basically, Andi, you know that Oracle sequel and my sequel post this kind of stuff, and we attacked on four problems this provisioning patching copy, data management and then production. But when we talked to all these customers on, I talked to see Ables and City Walls. They love it. They wanted to say that Hey, Kanna, how around more engines? Right? So that's one will live. But more importantly, they do have practices. They have their closest vehicles that they want to have single pane of management, off era managing data basis across. So the multi cluster capability, what we call that's like equal and a prison central which manage multiple excesses. They weren't error to manage multiple clusters that manage daily basis, right? That's number one. That's big for a product with in one year that we regard to that stage. Second thing was, obviously, people and press customers expect rule rule based access control. But this is data, so it's not a simple privilege, and, uh, you would define the roles and religious and then get it over kind of stuff. You do want to know who is accessing the data, whether they can access the data and where they can accident. We want to give them freedom to create clones and data kind of act. Give the access to data, but in a country manor so they can clone on their cure. Clusters there need to file a huge big ticket with Wait for two weeks. They can have that flexibility, but they can manage the data at that particular fear class. So this is what we call D a M Data access management. It's like a dam on the like construct on the river, control flow of the water and then channel is it to the right place and right. But since Canister, so that's what we're trying to do for data. That's the second big thing that we look for in the attitude. Otto. Obviously, there's a lot off interest on engines. Expand both relation in Cecil has no sequel are We are seeing huge interest in recipe. Hannah. We're going to do it in a couple of months. You'll have take review monger. Dubious. The big big guy in no sequel space will expand that from long. Would it be to march logic and other stuff, But even D B two insiders There's a lot of interest. I'm just looking for committed Customers were, weren't They are willing to put the dollars on the table, and we're going to rule it out. That's the beauty of fair that we're not just talking about. Cloud native databases Just force Chris and kind of stuff. What? All this innovation that happened in 30 40 years, we can we can renew them to the New Age. Afghanistan. >>Great. Well, Bala, thank you so much for coming on. The Cuba was >>Thank you. >>I'm Rebecca Knight for stew minimum. Stay tuned. For more of the cubes. Live coverage of Nutanix dot next.