>>Hello everyone. Welcome to the Super Cloud Event preview. I'm John Forry, host of the Cube, and with Dave Valante, host of the popular Super cloud events. This is Super Cloud two preview. I'm joined by industry leader and Cube alumni, Victoria Vigo, vice president of klos Cross Cloud Services at VMware. Vittorio. Great to see you. We're here for the preview of Super Cloud two on January 17th, virtual event, live stage performance, but streamed out to the audience virtually. We're gonna do a preview. Thanks for coming in. >>My pleasure. Always glad to be here. >>It's holiday time. We had the first super cloud on in August prior to VMware, explore North America prior to VMware, explore Europe prior to reinvent. We've been through that, but right now, super Cloud has got momentum. Super Cloud two has got some success. Before we dig into it, let's take a step back and set the table. What is Super Cloud and why is important? Why are people buzzing about it? Why is it a thing? >>Look, we have been in the cloud now for like 10, 15 years and the cloud is going strong and I, I would say that going cloud first was deliberate and strategic in most cases. In some cases the, the developer was going for the path of risk resistance, but in any sizable company, this caused the companies to end up in a multi-cloud world where 85% of the companies out there use two or multiple clouds. And with that comes what we call cloud chaos, because each cloud brings their own management tools, development tools, security. And so that increase the complexity and cost. And so we believe that it's time to usher a new era in cloud computing, which we, you call the super cloud. We call it cross cloud services, which allows our customers to have a single way to build, manage, secure, and access any application across any cloud. Lowering the cost and simplifying the environment. Since >>Dave Ante and I introduced and rift on the concept of Supercloud, as we talked about at reinvent last year, a lot has happened. Supercloud one, it was in August, but prior to that, great momentum in the industry. Great conversation. People are loving it, they're hating it, which means it's got some traction. Berkeley has come on board as with a position paper. They're kind of endorsing it. They call it something different. You call it cross cloud services, whatever it is. It's kind of the same theme we're seeing. And so the industry has recognized something is happening that's different than what Cloud one was or the first generation of cloud. Now we have something different. This Super Cloud two in January. This event has traction with practitioners, customers, big name brands, Sachs, fifth Avenue, Warner, media Financial, mercury Financial, other big names are here. They're leaning in. They're excited. Why the traction in the customer's industry converts over to, to the customer traction. Why is it happening? You, you get a lot of data. >>Well, in, in Super Cloud one, it was a vendor fest, right? But these vendors are smart people that get their vision from where, from the customers. This, this stuff doesn't happen in a vacuum. We all talk to customers and we tend to lean on the early adopters and the early adopters of the cloud are the ones that are telling us, we now are in a place where the complexity is too much. The cost is ballooning. We're going towards slow down potentially in the economy. We need to get better economics out of, of our cloud. And so every single customers I talked to today, or any sizable company as this problem, the developers have gone off, built all these applications, and now the business is coming to the operators and asking, where are my applications? Are they performing? What is the security posture? And how do we do compliance? And so now they're realizing we need to do something about this or it is gonna be unmanageable. >>I wanna go to a clip I pulled out from the, our video data lake and the cube. If we can go to that clip, it's Chuck Whitten Dell at a keynote. He was talking about what he calls multi-cloud by default, not by design. This is a state of the, of the industry. If we're gonna roll that clip, and I wanna get your reaction to that. >>Well, look, customers have woken up with multiple clouds, you know, multiple public clouds. On-premise clouds increasingly as the edge becomes much more a reality for customers clouds at the edge. And so that's what we mean by multi-cloud by default. It's not yet been designed strategically. I think our argument yesterday was it can be, and it should be, it is a very logical place for architecture to land because ultimately customers want the innovation across all of the hyperscale public clouds. They will see workloads and use cases where they wanna maintain an on-premise cloud. On-premise clouds are not going away. I mentioned edge Cloud, so it should be strategic. It's just not today. It doesn't work particularly well today. So when we say multi-cloud, by default we mean that's the state of the world. Today, our goal is to bring multi-cloud by design, as you heard. Yeah, I >>Mean, I, okay, Vittorio, that's, that's the head of Dell Technologies president. He obvious he runs it. Michael Dell's still around, but you know, he's the leader. This is a interesting observation. You know, he's not a customer. We have some customer equips we'll go to as well, but by default it kind of happened not by design. So we're now kind of in a zoom out issue where, okay, I got this environment just landed on me. What, what is the, what's your reaction to that clip of how multi-cloud has become present in, in everyone's on everyone's plate right now to deal with? Yeah, >>I it is, it is multi-cloud by default, I would call it by accident. We, we really got there by accident. I think now it's time to make it a strategic asset because look, we're using multiple cloud for a reason, because all these hyperscaler bring tremendous innovation that we want to leverage. But I strongly believe that in it, especially history repeat itself, right? And so if you look at the history of it, as was always when a new level of obstruction that simplify things, that we got the next level of innovation at the lower cost, you know, from going from c plus plus to Visual basic, going from integrating application at the bits of by layer to SOA and then web services. It's, it's only when we simplify the environment that we can go faster and lower cost. And the multi-cloud is ready for that level of obstruction today. >>You know, you've made some good points. You know, developers went crazy building great apps. Now they got, they gotta roll it out and operationalize it globally. A lot of compliance issues going on. The costs are going up. We got an economic challenge, but also agility with the cloud. So using cloud and or hybrid, you can get better agility. And also moving to the cloud, it's kind of still slow. Okay, so I get that at reinvent this year and at VMware explorer we were observing and we reported that you're seeing a transition to a new kind of ecosystem partner. Ones that aren't just ISVs anymore. You have ISVs, independent software vendors, but you got the emergence of bigger players that just, they got platforms, they have their own ecosystems. So you're seeing ecosystems on top of ecosystems where, you know, MongoDB CEO and the Databricks CEO both told me, we're not an isv, we're a platform built on a cloud. So this new kind of super cloudlike thing is going on. Why should someone pay attention to the super cloud movement? We're on two, we're gonna continue to do these out in the open. Anyone can participate. Why should people pay attention to this? Why should they come to the event? Why is this important? Is this truly an inflection point? And if they do pay attention, what should they pay attention to? >>I would pay attention to two things. If you are customers that are now starting to realize that you have a multi-cloud problem and the costs are getting outta control, look at what the leading vendors are saying, connect the dots with the early adopters and some of the customers that we are gonna have at Super Cloud two, and use those learning to not fall into the same trap. So I, I'll give you an example. I was talking to a Fortune 50 in Europe in my latest trip, and this is an a CIO that is telling me >>We build all these applications and now for compliance reason, the business is coming to me, I don't even know where they are, right? And so what I was telling him, so look, there are other customers that are already there. What did they do? They built a platform engineering team. What is the platform? Engineering team is a, is an operation team that understands how developers build modern applications and lays down the foundation across multiple clouds. So the developers can be developers and do their thing, which is writing code. But now you as a cio, as a, as a, as a governing body, as a security team can have the guardrail. So do you know that these applications are performing at a lower cost and are secure and compliant? >>Patura, you know, it's really encouraging and, and love to get your thoughts on this is one is the general consensus of industry leaders. I talked to like yourself in the round is the old way was soft complexity with more complexity. The cloud demand simplicity, you mentioned abstraction layer. This is our next inflection point. It's gotta be simpler and it's gotta be easy and it's gotta be performant. That's the table stakes of the cloud. What's your thoughts on this next wave of simplicity versus complexity? Because again, abstraction layers take away complexity, they should make it simpler. What's your thoughts? >>Yeah, so I'll give you few examples. One, on the development side and runtime. You, you one would think that Kubernetes will solve all the problems you have Kubernetes everywhere, just look at, but every cloud has a different distribution of Kubernetes, right? So for example, at VMware with tansu, we create a single place that allows you to deploy that any Kubernetes environment. But now you have one place to set your policies. We take care of the differences between this, this system. The second area is management, right? So once you have all everything deployed, how do you get a single object model that tells you where your stuff is and how it's performing, and then apply policies to it as well. So these are two areas and security and so on and so forth. So the idea is that figure out what you can abstract and make common across cloud. Make that simple and put it in one place while always allowing the developers to go underneath and use the differentiated features for innovation. >>Yeah, one of the areas I'm excited, I want to get your thoughts of too is, we haven't talked about this in the past, but it, I'll throw it out there. I think the, the new AI coming out chat, G P T and other things like lens, you see it and see new kinds of AI coming that's gonna be right in the heavy lifting opportunity to make things easier with AI and automation. I think AI will be a big factor in super cloud and, and cross cloud. What's your thoughts? >>Well, the one way to look at AI is, is one of the main, main services that you would want out of a multi-cloud, right? You want eventually, right now Google seems to have an edge, but you know, the competition creates, you know, innovation. So later on you wanna use something from Azure or from or from Oracle or something that, so you want at some point that is gonna be prone every single service in in the cloud is gonna be prone to obstruction and simplification. And I, I'm just excited about to see >>What book, I can't wait for the chat services to write code automatically for us. Well, >>They >>Do, they do. They're doing it now. They do. >>Oh, the other day, somebody, you know that I do this song par this for. So for fun sometimes. And somebody the other day said, ask the AI to write a parody song for multi-cloud. And so I have the lyrics stay >>Tuned. I should do that from my blog post. Hey, write a blog post on this January 17th, Victoria, thanks for coming in, sharing the preview bottom line. Why should people come? Why is it important? What's your final kind of takeaway? Billboard message >>History is repeat itself. It goes to three major inflection points, right? We had the inflection point with the cloud and the people that got left behind, they were not as competitive as the people that got on top o of this wave. The new wave is the super cloud, what we call cross cloud services. So if you are a customer that is experiencing this problem today, tune in to to hear from other customers in, in your same space. If you are behind, tune in to avoid the, the, the, the mistakes and the, the shortfalls of this new wave. And so that you can use multi-cloud to accelerate your business and kick butt in the future. >>All right. Kicking kick your names and kicking butt. Okay, we're here on J January 17th. Super Cloud two. Momentum continues. We'll be super cloud three. There'll be super cloud floor. More and more open conversations. Join the community, join the conversation. It's open. We want more voices. We want more, more industry. We want more customers. It's happening. A lot of momentum. Victoria, thank you for your time. Thank you. Okay. I'm John Farer, host of the Cube. Thanks for watching.

>>Hello everyone and welcome back to Las Vegas. I've got my jazz hands because I am very jazzed to be here at AWS Reinvent Live from the show floor all week. My name is Savannah Peterson, joined with the infamous John Farer. John, how you feeling >>After feeling great? Love? What's going on here? The vibe is a cloud, cloud native. Lot of security conversation, data, stuff we love Cloud Native, >>M I >>A L, I mean big news. Security, security, data lake. I mean, who would've thought Amazon have a security data lake? You know, e k s, I mean >>You might have with that tweet you had out >>Inside outside the containers. Reminds me, it feels like coan here. >>It honestly, and there's a lot of overlap and it's interesting that you mention CubeCon because we talked to the next company when we were in Detroit just a couple weeks ago. Teleport E is the CEO and founder F Welcome to the show. How you doing? >>I'm doing well. Thank you for having me today. >>We feel very lucky to have you. We hosted Drew who works on the product marketing side of Teleport. Yeah, we got to talk caddies and golf last time on the show. We'll talk about some of your hobbies a little bit later, but just in case someone's tuning in, unfamiliar with Teleport, you're all about identity. Give us a little bit of a pitch, >>Little bit of our pitch. Teleport is the first identity native infrastructure access platform. It's used by engineers and it's used by machines. So notice that I used very specific choice of words first identity native, what does it mean? Identity native? It consists of three things and we're writing a book about those, but I'll let you know. Stay >>Tuned on that front. >>Exactly, yes, but I can talk about 'em today. So the first component of identity, native access is moving away from secrets towards true identity. The secrets, I mean things like passwords, private keys, browser cookies, session tokens, API keys, all of these things is secrets and they make you vulnerable. The point is, as you scale, it's absolutely impossible to protect all of the seekers because they keep growing and multiplying. So the probability of you getting hacked over time is high. So you need to get rid of secrets altogether that that's the first thing that we do. We use something called True Identity. It's a combination of your biometrics as well as identity of your machines. That's tpms, HSMs, Ubikes and so on, so forth. >>Go >>Ahead. The second component is Zero Trust. Like Teleport is built to not trust the network. So every resource inside of your data center automatically gets configured as if there is no perimeter it, it's as safe as it was on the public network. So that's the second thing. Don't trust the network. And the third one is that we keep access policy in one place. So Kubernetes clusters, databases on stage, rdp, all of these protocols, the access policy will be in one place. That's identity. Okay, >>So I'm, I'm a hacker. Pretend I'm a hacker. >>Easy. That sounds, >>That sounds really good to me. Yeah, I'm supposed to tell 'em you're hacker. Okay. I can go to one place and hack that. >>I get this question a lot. The thing is, you want centralization when it comes to security, think about your house being your AWS account. Okay? Everything inside your furniture, your valuable, like you'll watch collection, like that's your data, that's your servers, paper clusters, so and so forth. Right Now I have a choice and your house is in a really bad neighborhood. Okay, that's the bad internet. Do you wanna have 20 different doors or do you want to have one? But like amazing one, extremely secure, very modern. So it's very easy for you to actually maintain it and enforce policy. So the answer is, oh, you probably need to have >>One. And so you're designing security identity from a perspective of what's best for the security posture. Exactly. Sounds like, okay, so now that's not against the conventional wisdom of the perimeter's dead, the cloud's everywhere. So in a way kind of brings perimeter concepts into the posture because you know, the old model of the firewall, the moat >>It Yeah. Just doesn't scale. >>It doesn't scale. You guys bring the different solution. How do you fit into the new perimeters dead cloud paradigm? >>So the, the way it works that if you are, if you are using Teleport to access your infrastructure, let's just use for example, like a server access perspective. Like that machine that you're accessing doesn't listen on a network if it runs in Teleport. So instead Teleport creates this trusted outbound tunnels to the proxy. So essentially you are managing devices using out going connection. It's kind of like how your phone runs. Yeah. Like your phone is actually ultimate, it's like a teleport like, like I It's >>Like teleporting into your environment. >>Yeah, well play >>Journal. But >>Think about actually like one example of an amazing company that's true Zero trust that we're all familiar with would be Apple. Because every time you get a new iOS on your phone, the how is it different from Apple running massive software deployment into enormous cloud with billions of servers sprinkle all over the world without perimeter. How is it possible That's exactly the kind of technology that Teleports >>Gives you. I'm glad you clarified. I really wanted to get that out on the table. Cuz Savannah, this is, this is the paradigm shift around what an environment is Exactly. Did the Apple example, so, okay, tell 'em about customer traction. Are people like getting it right away? Are their teams ready? Are they go, oh my god this is >>Great. Pretty much you see we kinda lucky like in a, in a, like in this business and I'm walking around looking at all these successful startups, like every single one of them has a story about launching the right thing at just the right like moment. Like in technology, like the window to launch something is extremely short. Like months. I'm literally talking months. So we built Teleport started to work on it in like 2015. It was internal project, I believe it or not, also a famous example. It's really popular like internal project, put it on GitHub and it sat there relatively unnoticed for a while and then it just like took off around 2000 >>Because people start to feel the pain. They needed it. Exactly, >>Exactly. >>Yeah. The timing. Well and And what a great way to figure out when the timing is right? When you do something like that, put it on GitHub. Yeah. >>People >>Tell you what's up >>Yeah's Like a basketball player who can just like be suspended in the air over the hoop for like half the game and then finally his score and wins >>The game. Or video gamer who's lagged, everyone else is lagging and they got the latency thing. Exactly. Thing air. Okay. Talk about the engineering side. Cause I, I like this at co con, you mentioned it at the opening of this segment that you guys are for engineers, not it >>Business people. That's right. >>Explain that. Interesting. This is super important. Explain why and why that's resonating. >>So there is this ongoing shift on more and more responsibilities going to engineers. Like remember back in the day before we even had clouds, we had people actually racking servers, sticking cables into them, cutting their fingers, like trying to get 'em in. So those were not engineers, they were different teams. Yeah. But then you had system administrators who would maintain these machines for you. Now all of these things are done with code. And when these things are done with code and with APIs, that shifts to engineers. That is what Teleport does with policy. So if you want to have a set of rules that govern who or what and when under what circumstances can access what data like on Kubernetes, on databases, on, on servers wouldn't be nice to use code for it. So then you could use like a version control and you can keep track of changes. That's what teleport enables. Traditionally it preferred more kind of clicky graphical things like clicking buttons. And so it's just a different world, different way of doing it. So essentially if you want security as code, that's what Teleport provides and naturally this language resonates with this persona. >>Love that. Security is coding. It's >>A great term. Yeah. Love it. I wanna, I wanna, >>Okay. We coined it, someone else uses it on the show. >>We borrow it >>To use credit. When did you, when did you coin that? Just now? >>No, >>I think I coined it before >>You wanted it to be a scoop. I love that. >>I wish I had this story when I, I was like a, like a poor little 14 year old kid was dreaming about security code but >>Well Dave Ante will testify that I coined data as code before anyone else but it got 10 years ago. You >>Didn't hear it this morning. Jimmy actually brought it back up. Aws, you're about startups and he's >>Whoever came up with lisp programming language that had this concept that data and code are exact same thing, >>Right? We could debate nerd lexicon all day on the cube. In fact, that could even be a segment first >>Of we do. First of all, the fact that Lisp came up on the cube is actually a milestone because Lisp is a very popular language for object-oriented >>Grandfather of everything. >>Yes, yes, grandfather. Good, good. Good catch there. Yeah, well done. >>All right. I'm gonna bring us back. I wanna ask you a question >>Talking about nerd this LIS is really >>No, I think it's great. You know how nerdy we can get here though. I mean we can just hang out in the weeds the whole time. All right. I wanna ask you a question that I asked Drew when we were in Detroit just because I think for some folks and especially the audience, they may not have as distinctive a definition as y'all do. How do you define identity? >>Oh, that's a great question. So identity as a term was, it was always used for security purposes. But most people probably use identity in the context of single signon sso. Meaning that if your company uses identity for access, which instead of having each application have an account for you, like a data entry with your first name, last name emails and your role. Yeah. You instead have a central database, let's say Okta or something like that. Yep. And then you, you use that to access everything that's kind of identity based access because there is a single source of identity. What we say is that we, that needs to be extended because it it no longer enough because that identity can be stolen. So if someone gets access to your Okta account using your credentials, then they can become you. So in order for identity to be attached to you and become your true identity, you have to rely on physical world objects. That's biometrics your facial fingerprint, like your facial print, your fingerprints as well as biometric of your machine. Like your laptops have PPM modules on it. They're absolutely unique. They cannot be cloned stolen. So that is your identity as well. So if you combine whatever is in Octa with the biker chip in this laptop and with your finger that collectively is your true identity, which cannot be stolen. So it's can't be hacked. >>And someone can take my finger like they did in the movies. >>So they would have to do that. And they would also have to They'd >>Steal your match. Exactly, exactly. Yeah. And they'd have to have your eyes >>And they have to, and you have >>Whatever the figure that far, they meant what >>They want. So that is what Drew identity is from telecom and >>Biometric. I mean it's, we're so there right now it's, it's really not an issue. It's only getting faster and better to >>Market. There is one important thing I said earlier that I want to go back to that I said that teleport is not just for engineers, it's also for machines. Cuz machines they also need the identity. So when we talk about access silos and that there are many different doors into your apartment, there are many different ways to access your data. So on the infrastructure side, machines are doing more and more. So we are offloading more and more tasks to them. That's a really good, what do machines use to access each other? Biome? They use API keys, they use private keys, they use basically passwords. Yeah. Like they're secrets and we already know that that's bad, right? Yeah. So how do you extend biometrics to machines? So this is why AWS offers cloud HSM service. HSM is secure hardware security module. That's a unique private key for the machine that is not accessible by anyone. And Teleport uses that to give identities to machines. Does do >>Customers have to enable that themselves or they have that part of a Amazon, the that >>Special. So it's available on aws. It's available actually in good old, like old bare metal machines that have HSMs on them on the motherboard. And it's optional by the way Teleport can work even if you don't have that capability. But the point is that we tried, you >>Have a biometric equivalent for the machines with >>Take advantage of it. Yeah. It's a hardware thing that you have to have and we all have it. Amazon sells it. AWS sells it to us. Yeah. And Teleport allows you to leverage that to enhance security of the infrastructure. >>So that classic hardware software play on that we're always talking about here on the cube. It's all, it's all important. I think this is really fascinating though. So I had an on the way to the show, I just enrolled in Clear and I had used a different email. I enrolled for the second time and my eyes wouldn't let me have two accounts. And this was the first time I had tried to sort of hack my own digital identity. And the girl, I think she was humoring me that was, was kindly helping me, the clear employee. But I think she could tell I was trying to mess with it and I wanted to see what would happen. I wanted to see if I could have two different accounts linked to my biometric data and I couldn't it, it picked it up right away. >>That's your true >>Identity. Yeah, my true identity. So, and forgive me cuz this is kind of just a personal question. It might be a little bit finger finger to the wind, but how, just how much more secure if you could, if you could give us a, a rating or a percentage or a a number. How much more secure is leveraging biometric data for identity than the secrets we've been using historically? >>Look, I could, I played this game with you and I can answer like infinitely more secure, right? Like but you know how security works that it all depends on implementation. So let's say you, you can deploy teleport, you can put us on your infrastructure, but if you're running, let's say like a compromised old copy of WordPress that has vulnerability, you're gonna get a hack through that angle. But >>Happens happens to my personal website all the time. You just touched Yeah, >>But the fact is that we, I I don't see how your credentials will be stolen in this system simply because your TPM on your laptop and your fingerprint, they cannot be downloaded. They like a lot of people actually ask us a slightly different question. It's almost the opposite of it. Like how can I trust you with my biometrics? When I use my fingerprint? That's my information. I don't want the company I work at to get my fingerprint people. I think it's a legit question to ask. >>Yeah. And it's >>What you, the answer to that question is your fingerprint doesn't really leave your laptop teleport doesn't see your fingerprint. What happens is when your fingerprint gets validated, it's it's your laptop is matching what's on the tpm. Basically Apple does it and then Apple simply tells teleport, yep that's F or whoever. And that's what we are really using. So when you are using this form authentication, you're not sharing your biometric with the company you work at. >>It's a machine to human confirmation first and >>Then it's it. It's basically you and the laptop agreeing that my fingerprint matches your TPM and if your laptop agrees, it's basically hardware does validation. So, and teleport simply gets that signal. >>So Ed, my final question for you is here at the show coupon, great conversations there for your company. What's your conversations here like at reinvent? Are you meeting with Amazon people, customers? What are some of the conversations? Because this is a much broader, I mean it's still technical. Yep. But you know, a lot of business kind of discussions, architectural refactoring of organizations. What are some of the things that you're talking about here with Telepo? What are, >>So I will mention maybe two trends I observed. The first one is not even security related. It's basically how like as a cloud becomes more mature, people now actually at different organizations develop their own internal ways of doing cloud properly. And they're not the same. Because when cloud was earlier, like there were this like best practices that everyone was trying to follow and there was like, there was just a maybe lack of expertise in the world and and now finding that different organizations just do things completely different. Like one, like for example, yeah, like some companies love having handful, ideally just one enormous Kubernetes cluster with a bunch of applications on it. And the other companies, they create Kubernetes clusters for different workloads and it's just like all over the map and both of them are believed that they're doing it properly. >>Great example of bringing in, that's Kubernetes with the complexity. And >>That's kind of one trend I'm noticing. And the second one is security related. Is that everyone is struggling with the access silos is that ideally every organization is dreaming about a day, but they have like one place which is which with great user experience that simply spells out this is what policy is to access this particular data. And it gets a automatically enforced by every single cloud provider, but every single application, but every single protocol, but every single resource. But we don't have that unfortunately Teleport is slowly becoming that, of course. Excuse me for plugging >>TelePro. No, no worries. >>But it is this ongoing theme that everyone is can't wait to have that single source of truth for accessing their data. >>The second person to say single source of truth on this stage in the last 24 >>Hours or nerds will love that. I >>Know I feel well, but it's all, it all comes back to that. I keep using this tab analogy, but we all want everything in one place. We don't wanna, we don't wanna have to be going all over the place and to look for >>Both. Because if it's and everything else places, it means that different teams are responsible for it. Yeah. So it becomes this kind of internal information silo as well. So you not even, >>And the risks and liabilities there, depending on who's overseeing everything. That's awesome. Right? So we have a new challenge on the cube specific to this show thing of this as your 30 minute or 30 minute that would be bold. 32nd sizzle reel, Instagram highlight. What is your hot take? Most important thing, biggest theme of the show this year. >>This year. Okay, so here's my thing. Like I want cloud to become something I want it to be. And every time I come here and I'm like, are we closer? Are we closer? So here's what I want. I want all cloud providers collectively to kind of merge. So then when we use them, it feels like we are programming one giant machine. Kind of like in the matrix, right? The movie. So like I want cloud to feel like a computer, like to have this almost intimate experience you have with your laptop. Like you can like, like do this and the laptop like performs the instructions. So, and it feels to me that we are getting closer. So like walking around here and seeing how everything works now, like on the single signon on from a security perspective, there is so that consolidation is finally happening. So it's >>The software mainframe we used to call it back in 2010. >>Yeah, yeah. Just kind of planetary scale thing. Yes. It's not the Zuckerberg that who's building metaverse, it's people here at reinvent. >>Unlimited resource for developers. Just call in. Yeah, yeah. Give me some resource, spin me up some, some compute. >>I would like alter that slightly. I would just basically go and do this and you shouldn't even worry about how it gets done. Just put instructions into this planetary mainframe and mainframe will go and figure this out. Okay. >>We gotta take blue or blue or red pill. I >>Know. I was just gonna say y'all, we are this, this, this, this segment is lit. >>We got made tricks. We got brilliant. We didn't get super cloud in here but we, we can weave that in. We got >>List. We just said it. So >>We got lisp. Oh great con, great conversation. Cloud native. >>Outstanding conversation. And thank you so much for being here. We love having teleport on the show. Obviously we hope to see you back again soon and and Drew as well. And thank all of you for tuning in this afternoon. Live from Las Vegas, Nevada, where we are hanging out at AWS Reinvent with John Furrier. I'm Savannah Peterson. This is the Cube. We are the source for high tech coverage.

>>Good afternoon and welcome back to the Classiest Show in Technology. This is the Cube we are at AWS Reinvent 2022 in Fabulous Sin City. That's why I've got my sequence on. We love a little Vegas, don't we? I'm joined by John Farer, another, another Vegas >>Fan. I don't have my sequence, I left it in my room. We're >>Gonna have to figure out how to get us 20 as soon as possible. What's been your biggest shock for you at the show so far? >>Well, I think the data story and security is so awesome. I love how that's front and center. If you look at the minutes of the keynote of Adamski, the CEO on day one, it's all bulked into data and security. All worked hand in hand. That's on top of already the innovation of their infrastructure. So I think you're gonna see a lot of interplay going on in this next segment. It's gonna tell a lot of that innovation story that's coming next. It's pretty awesome. >>It is pretty awesome, and I'm super excited. It's not only what we do here on the Cube, it's also in my show notes. We are gonna be geeking out for the next segment. Please welcome Paul and Puja. Wonderful to have you both here. Paul from Amazon, s3, glacier, and Pujan, CEO of kuo. I wanna turn to you Pujan, to start us off, just in case the audience isn't familiar, give us the Kuo pitch. >>Yeah, so basically Kuo is a, a backup as a service offering, right? Built in AWS four aws, right? And effectively going after, you know, any service that a customer uses on top of aws, right? And so a lot of the data sitting on s3, right? So that's been like our, our big use case going and basically building backup and air gap protection for, for s3. But we basically go to every other service, e c two, ebs, dynamo, you know, you name it, right? So basically do the whole thing >>And the relationship with aws. Can you guys share, I mean, you got you here together. You guys are a great partnership. Born in the cloud, operation in the cloud. Absolutely. I think talk about the partnership with aws. >>Absolutely. I think the last five years of building on AWS has been phenomenal, right? And I love the platform. It's, it's a very pure platform for us. You know, the APIs and, and the access you get and access you get to the service teams like Paul sitting here and the other teams you have gotten access to, I think has been phenomenal. But we also have, I would say, pushed the envelope in terms of how innovative we have been and how aggressive we have been in utilizing all the innovation that AWS has built in over the last few years. But it would not have happened without the fantastic partnership with the service teams. >>Paul, talk about the, AM the S3 part of this. What's the story there? >>Well, it's been great working with the CUO team over the course of the last few years. We were just upstairs diving deep into the, to the features that they're taking advantage of. They really push us hard on behalf of customers, and it's been a, it's just been a great relationship over the last years. >>That's awesome. And the ecosystem at such a, we're gonna hear tomorrow, the keynote on the, from Aruba who's gonna tend over the ecosystem. You guys are working together. There's a lot of strategic partnerships, so much collaboration between you guys that makes it very, this is the next gen cloud of cloud environment we're seeing. And you heard the, the economies around the corner. It's still gonna be challenging, but still there's more growth in the cloud. This is not stopping. This is impacts the customers. What are the customers saying to you guys when you work backwards from their needs? They want it faster, easier, cheaper. They want it more integrated. What are some of the things, all those you guys hearing from customers? >>So for us, you know, if you think about it, like, you know, as people are moving to the cloud, especially like take a use case like s3, right? So much of critical data sitting on top of S3 today. And so what folks have realized that as they're, you know, putting all of those, you know, what, over two 50 trillion objects, you know, sitting on s3, a lot of them need backup and data protection because there could be accidental deletions, there could be software bugs, there could be a ransomware type event due to which you need a second copy of the data that is outside of your security domain, right? But again, that needs to get be done at the, at the right price point, right? And that's where like a technology like Columbia comes in because since we've been built on the cloud, we've optimized it correctly. So especially for folks who are very cost conscious, given the macroeconomic conditions, we are heading into a technology that's built correctly so that, you know, you get the right architecture and the right solution at the right price point and the scale, right? Talking about trillions of objects, billions of objects within a single customer, within a single bucket sometimes. And that's where Columbia comes in. Cause we basically do that at scale without, again, impacting the, the customer's wallet more than it needs to. >>The porridge has to be the right temperature and the right size bowl. With the right spoon. You've got a lot of complexity when it comes to solving those customer challenges. You have a couple customer story examples you're allowed to share with us. Correct? Paul, do you want to kick one off? Go ahead. Oh, puja. All right. >>No, absolutely. I think there's a ton of them. I, I'll talk about, you know, want to begin with like Cox Automotive, right? A phenomenal customer that we, all of us have worked together with them. And again, looking for a solution to backup S3 to essentially go air gap protection outside of their account, right? They looked at doing it themselves, right? They thought they'll go and basically do it themselves. And then they fortunately bumped into Columbia, they looked at our architecture, looked at what it would really go and take to build it. And guess what, sitting in 2022, getting 23 right now, nobody wants to go and build this themselves. They actually want a turnkey solution that just does it, right? And so, again, we are a phenomenal joint customer of ours doing this at a pretty massive scale, right? And there are many more like that. There's Warner Brothers that are essentially going into the cloud from on premises, right? And they're going really fast accelerating the usage on aws again, looking at, you know, backup and data protection and using clum because of our extreme simplicity that we provide. >>Yeah, I think it's, you've got a, a lot of different people solving different problems that you're working with all the time. Millions of customers. Well, how do you prioritize? >>Well, for us, it really all comes down to fundamentals, right? So Amazon, s3 s unique distributed architecture delivers industry leading durability, availability, performance and security at virtually unlimited scale, right? And it's really been delivering on the fundamentals that has earned the trust of so many customers of all sizes and industries over the course of over 16 years. Now, in terms of how we prioritize on behalf of those customers, we always say that 90% of our roadmap comes directly from what customers are telling us is important. And a large number of our customers now are using S3 through lumino, which is why the relationship is so important. We're here talking about customer use cases here at the show, and we do that regularly throughout the year as well. And that's, that's how we land on a road. >>And what are the, what are the top stories from customers? What, what are they telling you? What's the number one top three things you're hearing? >>I tell you, like, again, it just comes down to the fundamentals, right? Of security, availability, durability and performance at virtually unlimited scale. Like that is the first customer first discussions that we have with customers talking about durable storage, for >>Sure. What I find interesting in, you mentioned scale, right? That comes up a lot scale with data. Yeah. That we heard data. The big theme here, security, what's in my S3 bucket? Can you find out what's in there? Is it backed up properly? How do I get it back? Where's the ransomware? Why not just target the ransomware? So how do you navigate the, the security challenges, the, the need to store all that scale data? What's the secret sauce? >>Yeah, so I think the, the big thing is we'll start with the, you know, how we have architected the product, right? If you think about it, this, you're dealing with a lot of scale, right? You get to a hundred million, a billion and billions very fast on S3 few, especially on a cloud native application. So it starts with the visibility, right? It's basically about, like we have things where you do, where you create a subset of your buckets called protection groups that you can essentially, you know, do it based on prefixes. So now you can essentially figure out what prefix you want to back up and what you don't want to back up. Maybe there's log data that you don't care about, so you don't back that up, right? And it all starts with that visibility that you give. And the prefix level data protection then comes the scale, which is where I was telling you, right? We have basically built an orchestration engine, right? It's like we call the ES for Lambdas, right? So we have a internal orchestration engine and essentially what what we have done is we have our own language internally that spawns off these lambdas, right? And they go after these S3 partitions do the right things and then you basically reel them back. So things like that that we do that are not possible if you're not built on the >>Clock. Well also, I mean, just mind blowing and go back 10 years. Yeah. I mean you got Lambda. What you're talking about here is the gift of the cloud innovation. Yeah. So the benefit of S3 is now accelerated. This is the story this year. Yeah. I mean they're highlighting it at scale, not just in the data, but like what we knew when Lambda came out and what S3 could do. But now mainstream solutions are coming in. Does that change your backup plans? Because we're gonna see a lot more end to end, lot more solutions. We heard that on the keynote. Some are saying it's more complexity. Of course it might, but you can abstract another way with the cloud that's the best part of the cloud. So these abstraction leads. So what's your view on that? But I wanna get your thoughts because you guys are perfectly positioned for this scale, but there's more coming. Yes. Yes. Exactly. What, how are you looking at that? >>So again, I think the, you know, obviously the, the S3 teams and every team in AWS is basically pushing the envelope in terms of innovation. But the key for a partner like us is to go and take that innovation. A lot of complex architectures behind the scene. But what you deliver to the customer is simple. I'll give you one more example. One of the things we launched that, you know, Paul and others are very excited about, is this ability to do instant access on the backup, right? So you could have billions of objects that you backed up. Maybe you need just 10,000 of them for a DR test. And we can basically create like an instant virtual bucket on top of that backup that you can instantly restore >>Spinning up a sandbox of temporary data to go check it >>Out. Exactly. Offer an inte application. >>Think we're geeking out right now. >>Yeah, I know. Brought that part of the segment, John. Don't worry, we're safely there. But, >>But that's the thing, right? That all that is possible because of all the, the scale and innovation and all the APIs and everything that, you know, Paul and the team gives us that we go and build on top of >>Paul, geek out on with us on this. We >>Are super excited for instant restore >>For store. I mean, automation programmability. >>It is, I mean it's the logical next step for backup in the cloud. Exactly. Yeah. But it's a super hard engineering problem to go solve for customers. I mean, the RTO benefits alone are super compelling, but then there's a cost element as well of not having to bring back all that stuff for a test restore, for example. And so it's, it's been really great to, to work with the team on that. We have some ideas on how we may help solve it from our side, and we're looking forward to collaborating on it. >>This is a great illustration of what I was writing about this week around the classic cloud, which is great. And as Adam said, and used like to use the word and, and you got this new functionality we're seeing emerge from the growth. Yes. From the companies that are built on Amazon web services that are growing. You're a partner, they have a lot of other partners and people are taking over restaurant here off action. I mean, there's real growth and new functionality on top of aws. You guys are no different. What's, are you prepared for that? Are you ready to go? >>Yeah, no, absolutely. And I think if you think about, if you think about it, right, I think it's also about doing this without impacting the primary application. Like if the customer is running a primary application at scale on s3, a backup application like ours can't come in and really mess with that. So I think being able to do things where, and this is where you solve really hard computer science problems, right? Where you're bottling yourself. If you are essentially seeing any kind of, you know, interfering with the primary, you're going to cut yourself down. You're gonna go after a different partition. So there are a lot of things you need to do behind the scenes, which is again, all the complexity, all of that, but deliver the, to the customer a very, very simple thing. >>You know, Paul, I wanna get your thoughts and I want you to chime in. Yeah. In 2014, I interviewed Steven Schmidt, my first interview with the, he was the CISO then, and now he's a CSO and, and former ciso, he's back at that time, the word was the cloud's not secure. Now we're talking about security. Just in the complexity of how you're partitioning and managing your sub portions, how you explained it, it's harder for the attackers. The cloud in its in its architecture has become a more secure environment. Yeah. Well, and getting more secure as you have laying out this, this is a new dynamic. This is good. Can you explain the, >>I mean, I, I can just tell you that at AWS security is job zero and that it will always be our number one priority, right? We have a, an infrastructure with under AWS that is vetted and approved to run even top secret workloads, which benefits all customers in all regions. >>And your, your security posture is embedded on top of that. And you got your own stuff. >>Yeah. And if you think of it as a shared responsibility model, so security of the cloud is the responsibility of the cloud provider, but then security of the data on top of it. Like you, you go and delete stuff, your software goes and does something that resiliency, the integrity of the data is your responsibility as a customer. And that's where, you know, we come in. Who >>Shared responsibility has been such a hot topic all week. Yeah. >>I gotta ask him one more question. Cause this is fascinating. And we are talking about on the cube all day today after we saw the announcement and Adam's comment on the cube, Adams LE's comment on the keynote. I mean, he said, if you're gonna tighten your belt, meaning economic cost recovery, re right sizing. If you want to tighten your belt, come to the cloud. So I have to ask you guys, Puja, if you can comment, that'd be great. There's a lot of other competitors out there that aren't born on aws. What is the customer gonna do when they tighten the build? What does that mean? They're gonna go to, to the individual contracts. They're gonna work in the marketplace. I mean this, there's a new dynamic in town. It's called AWS 2022. They weren't really around much in the recession of 2008. They were just starting to grow. Now they're an economic force. People like yourselves have embedded in there. There's a lot of competition. What's gonna happen? >>I think people are gonna just go to a place like, you know, AWS marketplace. You're going to essentially look for solutions and essentially like, and, and the right solutions built in are going to be self-service like aws. It's a very self-service thing. A hundred percent. So you go and do self-service, you figure out what's working, what's not working. Also, the model has to be consumption oriented. No longer can you expect the customer to go and pay a bunch of money for shelfware, right? It's like, like how we charge how AWS charges, which is you pay for what you consume. That and all has to be front and center, >>Right? I think that's a really, I think that's a really important >>Point. It's time >>And I think it's time. So we have a new challenge on the cube. We give you 30 seconds roughly to give us your extraordinarily hot take your shining thought leadership moment and, and highlight what you think is the most important takeaway from the show. The biggest soundbite, the juiciest announcement. Paul, I'll >>Start with an Instagram. Real basically. Yeah. Okay. >>Yeah. Hi. Go. I would just say from an S3 perspective, over the course of the last several years, we've really seen workloads shift from just backup and recovery and static images on websites to data lake analytics applications. And you continue to see that here. And I can tell you that some of these scaled applications are running at enormous mind blowing scale, right? And so, so every year we come here, we talk to customers, and it's just every year it sort of blows me away. And I've been in the storage industry for a long time and it's just is, it blows me away. Just the scale at customers are running in >>And >>Blowing scale. And when it comes to backup, let me just say that it's easy to back up and recover a single object, but doing an easy thing, a billion or 10 billion times over, that's actually quite hard. >>And just to, just to bold that a little bit, just pull out my highlighter. S3 now has over 280 trillion objects. That's a lot. >>That's a lot of objects. >>Yeah. You are not, you are not kidding. When you talk about scale, I mean, this is the most scalable. >>That's not solution's not there. Yeah. That, that's right. And we wake up every, we have a culture of durability and we wake up every single day to raise the bar on the fundamentals and make sure that every single one of those objects is protected and safe. >>Okay. You, I, >>I can't imagine worrying about two, two 80 trillion different things. >>Let's go. You're Instagram real >>For me again, you know, between S3 and us, we are two players out there that are really, you know, processing the data at the end of the day, right? And so I'm very excited about, you know, what we are going to do more and more with the instant restore capability where we can integrate third party services on top of it that can do more things with the data that is not, not passively sitting, but now becomes active data that you can analyze and do things with. So that's something where we take this to the next level is something that I'm super excited about. >>There's a lot to be excited about and, and we're excited to have you. We're excited to hear what happens next. Excited to see more collaboration like this. Paul Pon, thank you so much for joining us here on the show. Thank all of you from for tuning into our continuous wall to wall super thrilling live coverage of AWS reinvent here in fabulous Las Vegas, Nevada, with John Furrier. I'm Savannah Peterson. We're the cube, the leading source for high tech coverage.

>>Hello, wonderful humans and welcome back to The Cube's Thrilling live coverage of AWS Reinvent here in Las Vegas, Nevada. I'm joined by my fantastic co-host, John Farer. John, things are really ramping up in here. Day one. >>Yep, it's packed already. I heard 70,000 maybe attendees really this year. I just saw that on Twitter. Again, it continues to show that over the past 10 years we've been here, you're seeing some of the players that were here from the beginning growing up and getting bigger and stronger, becoming more platforms, not just point solutions. You're seeing new entrants coming in, new startups, and the innovation you start to see happening, it's really compelling to fun to watch. And our next segment, we have multi 10 time Cube alumni coming on and a first timer, so it should be great. We'll get into some of the innovation, >>Not only as this guest went on the cube 10 times, he also spoke at the first AWS reinvent, just like you were covering it here with Cube. But without further ado, please welcome Ronan and Kevin from NetApp. Thank you gentlemen, both for being here and for matching in your dark blue. How's the show going for you? Ronan, I'm gonna ask you first, you've been here since the beginning. How does it feel in 2022? >>First, it's amazing to see so many people, right? So many humans in one place, flesh and blood. And it's also amazing to see, it's such a celebration for people in the cloud, right? Like this is our, this is our event, the people in the cloud. I'm really, really happy to be here and be in the cube as well. >>Fantastic. It, it is a party, it's a cloud party. Yes. How are you feeling being here, Kevin? I'm >>Feeling great. I mean, going all the way back to the early days of Spot T, which was the start that eventually got acquired as Spot by NetApp. I mean this was, this was our big event. This is what we lived for. We've gone, I've gone from everything, one of the smaller booths out here on the floor all the way up to the, the huge booth that we have today. So we've kind of grown along with the AWS ecosystem and it's just a lot of fun to get here, see all the customers and talk to everybody. >>That's a lot of fun. Fun. That's the theme that we've been talking about. And we wrote a story about on, on Silicon Angle, more that growth from that getting in and getting bigger, not just an ISV or part of the startup showcase or ecosystem. The progression of the investment on how cloud has changed deliverables. You've been part of that wave. What's the biggest walk away, what's, and what's the most important thing going on now cuz it's not stopping. You got new interests coming in and the folks are rising with the tide and getting platforms built around their products. >>Yeah, I would say, you know, years ago is, is cloud in my decision path and now it's cloud is in my decision path. How much is it and how am I going to use it? And I think especially coming up over the next year, macroeconomic events and everything going on is how do I make my next dollar in the cloud go further than my last dollar? Because I know I'm gonna be there, I know I'm gonna be growing in the cloud, so how do I effectively use it to run my business going forward? >>All right, take a minute to explain Spot now part of NetApp. What's the story? What take us through for the folks that aren't familiar with the journey, where it's come from, where it's today? >>Sure. So SPOT is all about cloud optimization. We help all of our customers deploy scale and optimize their applications in the cloud. And what we do is everything from VMs to containers to any type of custom application you want to deploy, we analyze those applications, we find the best price point to run them, we right size them, we do the automation so your DevOps team doesn't have to do it. And we basically make the whole cloud serverless for you at the end of the day. So whatever you're doing in the cloud, we'll manage that for you from the lowest level of the stack all the way up to the highest level financials. >>Is this what you call the evolved cloud state? >>It is in the evolve clouds a little bit more, and Ronan can touch on that a little bit too. The Evolve clouds not only the public cloud but also the cloud that you're building OnPrem, right? A lot of big companies, it's not necessarily a hundred percent one way or the other. The Evolve cloud is which cloud am I on? Am I on an OnPrem cloud and a public cloud or am I on multiple public clouds in an OnPrem cloud? And I think Ronan, you probably have an opinion on that too. >>Yeah, and and I think what we are hearing from our customers is that many of them are in a situation where a lot of their data has been built for years on premises. They're accelerating their move to the cloud, some of them are accelerating, they're moving into multiple cloud and that situation of an on-prem that is becoming cloudy and cloudy all the time. And then accelerated cloud adoption. This is what the customers are calling the Evolve cloud and that's what we're trying to support them in that journey. >>How many customers are you supporting in this Evolve cloud? You made it seem like you can just turnkey this for everyone, which I am here >>For it. Yeah, just to be clear, I mean we have thousands of customers, right? Everything from your small startups, people just getting going with a few VMs all the way to people scaling to tens and thousands of VMs in the cloud or even beyond VM services and you know, tens of millions of spend a month. You know, people are putting a lot of investment into the cloud and we have all walks of life under our, you know, customer portfolio. >>You know, multi-cloud has been a big topic in the industry. We call it super cloud. Cause we think super cloud kind of more represents the destination to multi-cloud. I mean everyone has multiple clouds, but they're best of breed defaults. They're not by design in most cases, but we're starting to see traction towards that potential common level services fix to late. See, I still think we're on the performance game now, so I have to ask, ask you guys. Performance has becoming back in VO speeds and feeds back during the data center days. Well, I wouldn't wanna talk speeds and feeds of solutions and then cloud comes in. Now we're at the era of cloud where people are moving their workloads there. There's a lot more automation going on, A lot more, as you said, part of the decision. It is the path. Yeah. So they say, now I wanna run my workloads on the better, faster infrastructure. No developer wants to run their apps on the slower hardware. >>I think that's a tall up for you. Ronan go. >>I mean, I put out my story, no developer ever said, give me the slower software performance and and pay more fast, >>Fastest find too fastest. >>Speed feeds your back, >>Right? And and performance comes in different, in different parameters, right? They think it is come throughput, it comes through latency. And I think even a stronger word today is price performance, right? How much am I paying for the performance that that I need? NetApp is actually offering a very, very big advantage for customers on both the high end performance as well as in the dollar per performance. That is, that is needed. This is actually one of the key differentiator that Fsx for NetApp on top is an AWS storage based on the NetApp on top storage operating system. This is one of the biggest advantages it is offering. It is SAP certified, for example, where latency is the key, is the key item. It is offering new and fastest throughput available, but also leveraging some advanced features like tiering and so on, is offering unique competitive advantage in the dollar for performance specifically. >>And why, why is performance important now, in your opinion? Obviously besides the obvious of no one wants to run their stuff on the slower infrastructure, but why are some people so into it now? >>I think performance as a single parameter is, is definitely a key influencer of the user experience. None, none of us will, will compromise our our experience. The second part is performance is critical when scale is happening, right? And especially with the scale of data performance to handle massive amounts of data is is becoming more and more critical. The last thing that I'll emphasize is again is the dollar for performance. The more data you have, the more you need to handle, the more critical for you is to handle it in a cost effective way. This is kind of, that's kind of in the, in the, in the secret sauce of the success of every workload. >>There isn't a company or person here who's not thinking about doing more faster for cheaper. So you're certainly got your finger on the pulse With that, I wanna talk about a, a customer case study. A little birdie told me that a major US airline recently just had a mass of when we're where according to my notes response time and customer experience was improved by 17 x. Now that's the type of thing that cuts cost big time. Can one of you tell me a little bit more about that? >>Yeah, so I think we all flew here somehow, right? >>Exactly. It's airlines matter. Probably most folks listening, they're >>Doing very well right now. Yes, the >>Airlines and I think we all also needed to deal with changes in the flights with, with really enormous amount of complexity in managing a business like that. We actually rank and choose what, what airline to use among other things based on the level of service that they give us. And especially at the time of crunch, a lot of users are looking through a lot of data to try to optimize, >>Plus all of them who just work this holiday weekend sidebar >>E Exactly right. Can't even, and Thanksgiving is one of these crunch times that are in the middle of this. So 70 x improvement in performance means a loss seven >>Zero or >>17 1 7 1 7 x Right? >>Well, and especially when we're talking about it looks like 50,000, 50,000 messages per minute that this customer was processing. Yes. That that's a lot. That's almost a thousand messages a second. Wow. I think my math tees up there. Yeah. >>It does allow them to operate in the next level of scale and really increase their support for the customer. It also allows them to be more efficient when it comes to cost. Now they need less infrastructure to give better service across the board. The nice thing is that it didn't require them for a lot of work. Sometimes when the customers are doing their journey to the cloud, one of the things that kind of hold them back is like, is either the fear or, or maybe is the, the concern of how much effort will it take me to achieve the same performance or even a better performance in the cloud? They are a live example that not only can you achieve, you can actually exceed the performance that I have on premises and really give customer a better service >>Customer a better service. And reliability is extremely important there. 99.9%. 99% >>99. Yes. >>Yes. That second nine obviously being very important, especially when we're talking about the order of magnitude of, of data and, and actions being taken place. How much of a priority is, is reliability and security for y'all as a team? >>So reliability is a key item for, for everybody, especially in crunch times. But reliability goes beyond the nines. Specifically reliability goes into how simple it is for you to enable backup n dr, how protected are you against ransomware? This is where netup and, and including the fsx for NETUP on top richness of data management makes a huge difference. If you are able to make your copy undeletable, that is actually a game changer when it comes to, to data protection. And this is, this is something that in the past requires a lot of work, opening vaults and other things. Yeah. Now it becomes a very simple configuration that is attached to every net up on top storage, no matter where it is. >>We heard some news at VMware explorer this past fall. Early fall. You guys were there. We saw the Broadcom acquisition. Looks like it's gonna get finalized maybe sooner than later. Lot of, so a lot of speculation around VMware. Someone called the VMware like where is VMware as in where they now, nice pun it was, it was actually Nutanix people, they go at each other all the time. But Broadcom's gonna keep vse and that's where the bread and butter, that's the, that's the goose that lays the Golden eggs. Customers are there. How do you guys see your piece there with VMware cloud on AWS that integrates solution? You guys have a big part of that ecosystem. We've covered it for years. I mean we've been to every VM world now called explorer. You guys have a huge customer base with VMware customers. What's the, what's the outlook? >>Yeah, and, and I think the important part is that a big part of the enterprise workloads are running on VMware and they will continue to run on VMware in, in, in the future. And most of them will try to run in a hybrid mode if not moving completely to the cloud. The cloud give them unparallel scale, it give them DR and backup opportunities. It does a lot of goodness to that. The partnership that NetApp brings with both VMware as well ass as well as other cloud vendors is actually a game changer. Because the minute that you go to the cloud, things like DR and backup have a different economics connected to them. Suddenly you can do compute less dr definitely on backup you can actually achieve massive savings. NetApp is the only data store that is certified to run with VMware cloud. And that actually opens to the customer's huge opportunity for unparalleled data protection as well as real, real savings, hard savings. And customers that look today and they say, I'm gonna shrink my data center, I'm gonna focus on, on moving certain things to the cloud, DR and backup and especially DR and backup VMware might be one of the easiest, fastest things to take into the cloud. And the partnership betweens VMware and NetApp might actually give you >>And the ONAP is great solution. Fsx there? Yes. I think you guys got a real advantage here and I want to get into something that's kind of a gloom and doom. I don't have to go negative on this one, Savannah, but they me nervous John. But you know, if you look at the economic realities you got a lot of companies like that are in the back of a Druva, Netta, Druva, cohesive rub. Others, you know, they, you know, there's a, their generational cloud who breaks through. What's the unique thing? Because you know there's gonna be challenges in the economy and customers are gonna vote with their wallets and they start to see as they make these architectural decisions, you guys are in the middle of it. There's not, there may not be enough to go around and the musical chairs might stop or, or not, I'm not sure. But I feel like if there's gonna be a consolidation, what does that look like? What are customers thinking? Backup recovery, cloud. That's a unique thing. You mentioned economics, it's not, you can't take the old strategy and put it there from five, 10 years ago. What's different now? >>Yeah, I think when it comes to data protection, there is a real change in, in the technology landscape that opened the door for a lot of new vendors to come and offer. Should we expect consolidation? I think microeconomic outside and other things will probably drive some of that to happen. I think there is one more parameter, John, that I wanna mention in this context, which is simplicity. Many of the storage vendors, including us, including aws, you wanna make as much of the backup NDR at basically a simple checkbox that you choose together with your main workload. This is another key capabilities that is, that is being, bringing and changing the market, >>But it also needs to move up. So it's not only simplicity, it's also about moving to the applications that you use, use, and just having it baked in. It's not about you going out and finding a replication. It's like what Ronan said, we gotta make it simple and then we gotta bake it into what they use. So one of our most recent acquisitions of Insta Cluster allows us to provide our customers with open source databases and data streaming services. When those sit on top of on tap and they sit on top of spots, infrastructure optimization, you get all that for free through the database that you use. So you don't worry about it. Your database is replicated, it's highly available, and it's running at the best cost. That's where it's going. >>Awesome. >>You also recently purchased Cloud Checker as well. Yes. Do you just purchase wonderful things all the time? We >>Do. We do. We, >>I'm not >>The, if he walk and act around and then we find the best thing and then we, we break out the checkbook, no, but more seriously, it, it rounds out what customers need for the cloud. So a lot of our customers come from storage, but they need to operate the entire cloud around the storage that they have. Cloud Checker gives us that financial visibility across every single dollar that you spend in the cloud and also gives us a better go to market motion with our MSPs and our distributors than we had in the past. So we're really excited about what cloud checker can unlock for us in >>The future. Makes a lot of sense and congratulations on all the extremely exciting things going on. Our final and closing question for our guests on this year's show is we would love your, your Instagram hot take your 32nd hot take on the most important stories, messages, themes of AWS reinvent 2022. Ronan, I'm gonna start with you cause you have a smirk >>And you do it one day ahead of the keynotes, one day ahead with you. >>You can give us a little tease a little from you. >>I think that pandemic or no pandemic face to face or no face to face, the innovation in the cloud is, is actually breaking all records. And I think this year specifically, you will see a lot of focus on data and scale. I think that's, these are two amazing things that you'll see, I think doubling down. But I'm also anxious to see tomorrow, so I'll learn more about it. >>All right. We might have to chat with you a little bit after tomorrow. Is keynotes and whatnot coming up? What >>About you? I think you're gonna hear a lot about cost. How much are you spending? How far are your dollars going? How are you using the cloud to the best of your abilities? How, how efficient are you being with your dollars in the cloud? I think that's gonna be a huge topic. It's on everybody's mind. It's the macro economics situation right now. I think it's gonna be in every session of the keynote tomorrow. All >>Right, so every >>Session. Every session, >>A bulk thing. John, we're gonna have >>That. >>I'm with him. You know, all S in general, you >>Guys have, and go look up what I said. >>Yeah, >>We'll go back and look at, >>I'm gonna check on you >>On that. The record now states. There you go, Kevin. Thank both. Put it down so much. We hope that it's a stellar show for Spotify, my NetApp. Thank you. And that we have you 10 more times and more than just this once and yeah, I, I can't wait to see, well, I can't wait to hear when your predictions are accurate tomorrow and we get to learn a lot more. >>No, you gotta go to all the sessions down just to check his >>Math on that. Yeah, no, exactly. Now we have to do our homework just to call him out. Not that we're competitive or those types of people at all. John. No. On that note, thank you both for being here with us. John, thank you so much. Thank you all for tuning in from home. We are live from Las Vegas, Nevada here at AWS Reinvent with John Furrier. My name is Savannah Peterson. You're watching the Cube, the leader in high tech coverage.

>>Good morning and welcome back to Detroit, Michigan. My name is Savannah Peterson and I'm here on set of the cube, my co-host John Farer. How you doing this morning, John? >>Doing great. Feeling fresh. Day two of three days of coverage, feeling >>Fresh. That is that for being in the heat of the conference. I love that attitude. It's gonna >>Be a great day today. We'll see you at the end of the day. Yeah, >>Well, we'll hold him to it. All right, everyone hold 'em accountable. Very excited to start the day off with an internet, a legend as well as a cube og. We are joined this morning by Matt Klein. Matt, welcome to the show. >>Thanks for having me. Good to see you. Yep. >>It's so, what's the vibe? Day two, Everyone's buzzing. What's got you excited at the show? You've been here before, but it's been three years you >>Mentioned. I, I was saying it's been three years since I've been to a conference, so it's been interesting for me to see what is, what is the same and what is different pre and post covid. But just really great to see everyone here again and nice to not be sitting in my home by myself. >>You know, Savannah said you're an OG and we were referring before we came on camera that you were your first came on the Cub in 2017, second Cuban event. But you were, I think, on the first wave of what I call the contributor momentum, where CNCF really got the traction. Yeah. You were at Lift, Envoy was contributed and that was really hyped up and I remember that vividly. It was day zero they called it back then. Yeah. And you got so much traction. People are totally into it. Yeah. Now we've got a lot of that going on now. Right. A lot of, lot of day Zero events. They call 'em co, co-located events. You got web assembly, a lot of other hype out there. What do you see out there that you like? How would you look at some of these other Sure. Communities that are developing, What's the landscape look like as you look out? Because Envoy set the table, what is now a standard >>Practice. Yeah. What's been so interesting for me just to come here to the conference is, you know, we open source Envoy in 2016. We donated in 2017. And as you mentioned at that time, Envoy was, you know, everyone wanted to talk about Envoy. And you know, much to my amazement, Envoy is now pervasive. I mean, it's used everywhere around the world. It's like, never in my wildest dreams would I have imagined that it would be so widely used. And it's almost gotten to the point where it's become boring. You know, It's just assumed that Envoy is, is everywhere. And now we're hearing a lot about Eeb p f and Web assembly and GI ops and you know, AI and a bunch of other things. So it's, it's actually great. It's made me very happy that it's become so pervasive, but it's also fun. Yeah. We mention to, to look around all other stuff >>Like congratulate. It's just a huge accomplishment really. I think it's gonna be historic, historical moment for the industry too. But I like how it progressed. I mean, I don't mind hype cycles as long as it's some vetting. Sure. Of course. You know, use cases that are clearly defined, but you gotta get that momentum in the community, but then you start gotta get down to, to business. Yep. So, so to speak and get it deployed, get traction. Yep. What should projects look like? And, and give us the update on Envoy. Cause you guys have a, a great use case of how you got traction. Right. Take us through some of the early days of what made Envoy successful in your opinion. Great question. >>Yeah. You know, I, I think Envoy is fairly unique around this conference in the sense that Envoy was developed by Lyft, which is an end user company. And many of the projects in this ecosystem, you know, no judgment, for better or worse, they are vendor backed. And I think that's a different delivery mechanism when it's coming from an end user where you're solving a, a particular business case. So Envoy was really developed for Lyft in a, you know, very early scaling days and just, you know, trying to help Lyft solve its business problems. So I think when Envoy was developed, we were, you know, scaling, we were falling over and actually many other companies were having similar problems. So I think Envoy became very widely deployed because many companies were having similar issues. So Envoy just became pervasive among lift peer companies. And then we saw a lot of vendor uptake in the service mesh space in the API gateway space among large internet providers. So, I I I, I think it's just, it's an interesting case because I think when you're solving real problems on the ground, in some ways it's easier to actually get adoption than if you're trying to develop it from a commercial backing. >>And that's the class, I mean, almost, It's almost like open source product market fit. It is in its own way. Cause you have a problem. Absolutely. Other people have the same problem finding >>Too. I mean, it's, it's designed thinking from >>A different, When, when I talk to people about open source, I like to tell people that I do not think it's any different than starting a company. I actually think it's all the same problems finding pro product, market fit, hiring, like finding contributors and maintainers, like doing PR and marketing. Yeah. Getting team together, traction, getting, getting funding. I mean, you have to have money to do all these things. Yeah. So I think a lot of people think of open source as I, I don't know, you know, this fantastic collaborative effort and, and it is that, but there's a lot more to it. Yeah. And it is much more akin to starting a >>Company. Let's, let's just look at that for a second. Cause I think that's a good point. And I was having a conversation in the hallway two nights ago on this exact point. If the power dynamics of a startup in the open source, as you point out, is just different, it's community based. So there are things you just gotta be mindful of. It's not top down. >>Exactly. It's not like, >>Right. You know, go take that hill. It's really consensus based, but it is a startup. All those elements are in place. Absolutely. You need leadership, you gotta have debates, alignment, commit, You gotta commit to a vision. Yep. You gotta make adjustments. Build the trajectory. So based on that, I mean, do you see more end user traction? Cause I was, we were talking also about Intuit, they donated some of their tow code R goes out there. Yep. R go see the CDR goes a service. Where's the end user contributions to these days? Do you feel like it's good, still healthy? >>I, I mean, I, I'm, I'm biased. I would like to see more. I think backstage outta Spotify is absolutely fantastic. That's an area just in terms of developer portals and developer efficiency that I think has been very underserved. So seeing Backstage come outta Spotify where they've used it for years, and I think we've already seen they had a huge date, you know, day one event. And I, I think we're gonna see a lot more out of that >>Coming from, I'm an end user, pretend I'm an end user, so pretend I have some code. I want to, Oh man, I'm scared. I don't am I'm gonna lose my competitive edge. What's the, how do you talk to the enterprise out there that might be thinking about putting their project out there for whether it's the benefit of the community, developing talent, developing the product? >>Sure. Yeah. I would say that I, I would ask everyone to think through all of the pros and cons of doing that because it's not for free. I mean, doing open source is costly. It takes developer time, you know, it takes management time, it takes budgeting dollars. But the benefits if successful can be huge, right? I mean, it can be just in terms of, you know, getting people into your company, getting users, getting more features, all of that. So I would always encourage everyone to take a very pragmatic and realistic view of, of what is required to make that happen. >>What was that decision like at Lyft >>When you I I'm gonna be honest, it was very naive. I I think we've, of that we think we need to know. No, just didn't know. Yeah. I think a lot of us, myself included, had very minimal open source experience. And had we known, or had I known what would've happened, I, I still would've done it. But I, I'm gonna be honest, the last seven years have aged me what I feel like is like 70 or a hundred. It's been a >>But you say you look out in the landscape, you gotta take pride, look at what's happened. Oh, it's, I mean, it's like you said, it >>Matured fantastic. I would not trade it for anything, but it has, it has been a journey. What >>Was the biggest surprise? What was the most eye opening thing about the journey for you? >>I, I think actually just the recognition of all of the non-technical things that go into making these things a success. I think at a conference like this, people think a lot about technology. It is a technology conference, but open source is business. It really is. I mean, it, it takes money to keep it going. It takes people to keep >>It going. You gotta sell people on the concepts. >>It takes leadership to keep it going. It takes internal, it takes marketing. Yeah. So for me, what was most eyeopening is over the last five to seven years, I feel like I actually have not developed very many, if any technical skills. But my general leadership skills, you know, that would be applicable again, to running a business have applied so well to, to >>Growing off, Hey, you put it out there, you hear driving the ship. It's good to do that. They need that. It really needs it. And the results speak for itself and congratulations. Yeah. Thank you. What's the update on the project? Give us an update because you're seeing, seeing a lot of infrastructure people having the same problem. Sure. But it's also, the environments are a little bit different. Some people have different architectures. Absolutely different, more cloud, less cloud edges exploding. Yeah. Where does Envoy fit into the landscape they've seen and what's the updates? You've got some new things going on. Give the updates on what's going on with the project Sure. And then how it sits in the ecosystem vis-a-vis what people may use it for. >>Yeah. So I'm, from a core project perspective, honestly, things have matured. Things have stabilized a bit. So a lot of what we focus on now are less Big bang features, but more table stakes. We spend a lot of time on security. We spend a lot of time on software supply chain. A topic that you're probably hearing a lot about at this conference. We have a lot of software supply chain issues. We have shipped Quicken HTB three over the last year. That's generally available. That's a new internet protocol still work happening on web assembly where ha doing a lot of work on our build and release pipeline. Again, you would think that's boring. Yeah. But a lot of people want, you know, packages for their fedora or their ADU or their Docker images. And that takes a lot of effort. So a lot of what we're doing now is more table stakes, just realizing that the project is used around the world very widely. >>Yeah. The thing that I'm most interested in is, we announced in the last six months a project called Envoy Gateway, which is layered on top of Envoy. And the goal of Envoy Gateway is to make it easier for people to run Envoy within Kubernetes. So essentially as an, as an ingress controller. And Envoy is a project historically, it is a very sophisticated piece of software, very complicated piece of software. It's not for everyone. And we want to provide Envoy Gateway as a way of onboarding more users into the Envoy ecosystem and making Envoy the, the default API gateway or edge proxy within Kubernetes. But in terms of use cases, we see Envoy pervasively with service mesh, API gateway, other types of low balancing cases. I mean, honestly, it's, it's all over the place at >>This point. I'm curious because you mentioned it's expanded beyond your wildest dreams. Yeah. And how could you have even imagined what Envoy was gonna do? Is there a use case or an application that really surprised you? >>You know, I've been asked that before and I, it's hard for me to answer that. It's, it's more that, I mean, for example, Envoy is used by basically every major internet company in China. I mean, like, wow. Everyone in China uses Envoy, like TikTok, like Alibaba. I mean like everyone, all >>The large sale, >>Everyone. You know, and it's used, it's used in the, I'm just, it's not just even the us. So I, I think the thing that has surprised me more than individual use cases is just the, the worldwide adoption. You know, that something could be be everywhere. And that I think, you know, when I open my phone and I'm opening all of these apps on my phone, 80 or 90% of them are going through Envoy in some form. Yeah. You know, it's, it's just that pervasive, I blow your mind a little bit sometimes >>That does, that's why you say plumber on your Twitter handle as your title. Cause you're working on all these things that are like really important substrate issues, Right. For scale, stability, growth. >>And, you know, to, I, I guess the only thing that I would add is, my goal for Envoy has always been that it is that boring, transparent piece of technology. Kind of similar to Linux. Linux is everywhere. Right? But no one really knows that they're using Linux. It's, it's justs like Intel inside, we're not paying attention. It's just there, there's >>A core group working on, if they have pride, they understand the mission, the importance of it, and they make their job is to make it invisible. >>Right. Exactly. >>And that's really ease of use. What's some of the ease of use sways and, and simplicity that you're working on, if you can talk about that. Because to be boring, you gotta be simpler and easier. All boring complex is unique is not boring. Complex is stressful. No, >>I I think we approach it in a couple different ways. One of them is that because we view Envoy as a, as a base technology in the ecosystem, we're starting to see, you know, not only vendors, but other open source projects that are being built on top of Envoy. So things like API Gateway, sorry, Envoy Gateway or you know, projects like Istio or all the other projects that are out there. They use Envoy as a component, but in some sense Envoy is a, as a transparent piece of that system. Yeah. So I'm a big believer in the ecosystem that we need to continue to make cloud native easier for, for end users. I still think it's too complicated. And so I think we're there, we're, we're pushing up the stack a bit. >>Yeah. And that brings up a good point. When you start seeing people building on top of things, right? That's enabling. So as you look at the enablement of Envoy, what are some of the things you see out on the horizon if you got the 20 mile stare out as you check these boring boxes, make it more plumbing, Right? Stable. You'll have a disruptive enabling platform. Yeah. What do you see out there? >>I am, you know, I, again, I'm not a big buzzword person, but, so some people call it serverless functions as a service, whatever. I'm a big believer in platforms in the sense that I really believe in the next 10 to 15 years, developers, they want to provide code. You know, they want to call APIs, they want to use pub subsystems, they want to use cas and databases. And honestly, they don't care about container scheduling or networking or load balancing or any of >>These things. It's handled in the os >>They just want it to be part of the operating system. Yeah, exactly. So I, I really believe that whether it's an open source or in cloud provider, you know, package solutions, that we're going to be just moving increasingly towards systems likes Lambda and Fargate and Google Cloud Run and Azure functions and all those kinds of things. And I think that when you do that much of the functionality that has historically powered this conference like Kubernetes and Onvoy, these become critical but transparent components that people don't, they're not really aware of >>At that point. Yeah. And I think that's a great call out because one of the things we're seeing is the market forces of, of this evolution, what you just said is what has to happen Yep. For digital transformation to, to get to its conclusion. Yep. Which means that everything doesn't have to serve the business, it is the business. Right. You know it in the old days. Yep. Engineers, they serve the business. Like what does that even mean? Yep. Now, right. Developers are the business, so they need that coding environment. So for your statement to happen, that simplicity in visibility calling is invisible os has to happen. So it brings up the question in open source, the trend is things always work itself out on the wash, as we say. So when you start having these debates and the alignment has to come at some point, you can't get to those that stay without some sort of defacto or consensus. Yep. And even standards, I'm not a big be around hardcore standards, but we can all agree and have consensus Sure. That will align behind, say Kubernetes, It's Kubernetes a standard. It's not like an i e you know, but this next, what, what's your reaction to this? Because this alignment has to come after debate. So all the process contending for I am the this of that. >>Yeah. I'm a look, I mean, I totally see the value in like i e e standards and, and there's a place for that. At the same time, for me personally as a technologist, as an engineer, I prefer to let the, the market as it were sort out what are the defacto standards. So for example, at least with Envoy, Envoy has an API that we call Xds. Xds is now used beyond Envoy. It's used by gc, it's used by proprietary systems. And I'm a big believer that actually Envoy in its form is probably gonna go away before Xds goes away. So in some ways Xds has become a defacto standard. It's not an i e e standard. Yeah. We, we, we have been asked about whether we should do that. Yeah. But I just, I I think the >>It becomes a component. >>It becomes a component. Yeah. And then I think people gravitate towards these things that become de facto standards. And I guess I would rather let the people on the show floor decide what are the standards than have, you know, 10 people sitting in a room figure out >>The community define standards versus organizational institutional defined standards. >>And they both have places a >>Hundred percent. Yeah, sure. And, and there's social proof in both of them. Yep. >>Frankly, >>And we were saying on the cube that we believe that the developers will decide the standard. Sure. Because that's what you're basically saying. They're deciding what they do with their code. Right. And over time, as people realize the trade of, hey, if everyone's coding this right. And makes my life easier to get to that state of nirvana and enlightenment, as we would say. Yeah. Yeah. >>Starting strong this morning. John, I I love this. I'm curious, you mentioned Backstage by Spotify wonderful example. Do you think that this is a trend we're gonna see with more end users >>Creating open source projects? Like I, you know, I hope so. The flip side of that, and as we all know, we're entering an uncertain economic time and it can be hard to justify the effort that it takes to do it well. And what I typically counsel people when they are about to open source something is don't do it unless you're ready to commit the resources. Because opensourcing something and not supporting it. Yeah. I actually can be think, I think it'd be worse. >>It's an, it's insult that people, you're asking to commit to something. Exactly. Needs of time, need the money investment, you gotta go all in and push. >>So I, so I very much want to see it and, and I want to encourage that here, but it's hard for me to look into the crystal ball and know, you know, whether it's gonna happen more >>Or less at what point there were, are there too many projects? You know, I mean, but I'm not, I mean this in, in a, in a negative way. I mean it more in the way of, you know, you mentioned supply chain. We were riffing on the cube about at some point there's gonna be so much code open source continuing thundering away with, with the value that you're just gluing things. Right. I don't need the code, this code there. Okay. What's in the code? Okay. Maybe automation can help out on supply chain. Yeah. But ultimately composability is the new >>Right? It is. Yeah. And, and I think that's always going to be the case. Case. Good thing. It is good thing. And I, I think that's just, that's just the way of things for sure. >>So no code will be, >>I think, I think we're seeing a lot of no code situations that are working great for people. And, and, but this is actually really no different than my, than my serverless arguing from before. Just as a, as a, a slight digression. I'm building something new right now and you know, we're using cloud native technologies and all this stuff and it's still, >>What are you building? >>Even as a I'm, I'm gonna keep that, I'm gonna keep that secret. I know I'm, but >>We'll find out on Twitter. We're gonna find out now that we know it. Okay. Keep on mystery. You open that door. We're going down see in a couple weeks. >>Front >>Page is still an angle. >>But I, I was just gonna say that, you know, and I consider myself, you know, you're building something, I'm, I see myself an expert in the cloud native space. It's still difficult, It's difficult to, to pull together these technologies and I think that we will continue to make it easier for people. >>What's the biggest difficulties? Can you give us some examples? >>Well, just, I mean, we still live in a big mess of yammel, right? Is a, there's a, there's a lot of yaml out there. And I think just wrangling all of that in these systems, there's still a lot of cobbling together where I think that there can be unified platforms that make it easier for us to focus on our application logic. >>Yeah. I gotta ask you a question cuz I've talked to college kids all the time. My son's a junior in CS and he's, you know, he's coding away. What would you, how does a student or someone who's learning figure out where, who they are? Because there's now, you know, you're either into the infrastructure under the hood Yeah. Or you're, cuz that's coding there option now coding the way your infrastructure people are working on say the boring stuff so everyone else can have ease of use. And then what is just, I wanna just code, there's two types of personas. How does someone know who they are? >>My, when I give people career advice, my biggest piece of advice to them is in the first five to seven to 10 years of their career, I encourage people to do different things like every say one to two to three years. And that doesn't mean like quitting companies and changing companies, it could mean, you know, within a company that they join doing different teams, you know, working on front end versus back end. Because honestly I think people don't know. I think it's actually very, Yeah. Our industry is so broad. Yeah. That I think it's almost impossible to >>Know. You gotta get your hands dirty to jump >>In order to know what you like. And for me, in my career, you know, I've dabbled in different areas, but I've always come back to infrastructure, you know, that that's what I enjoy >>The most. Okay. You gotta, you gotta taste everything. See what you, what >>You like. Exactly. >>Right. Last question for you, Matt. It's been three years since you were here. Yep. What do you hope that we're able to say next year? That we can't say this year? Hmm. Beyond the secrets of your project, which hopefully we will definitely be discussing then. >>You know, I I, I don't have anything in particular. I would just say that I would like to see more movement towards projects that are synthesizing and making it easier to use a lot of the existing projects that we have today. So for example, I'm, I'm very bullish on backstage. Like I, I've, I've always said that we need better developer UIs that are not CLIs. Like I know it's a general perception among many people. Totally agree with you. Frankly, you're not a real systems engineer unless you type on the command line. I, I think better user interfaces are better for humans. Yep. So just for a project like Backstage to be more integrated with the rest of the projects, whether that be Envo or Kubernete or Argo or Flagger. I, I just, I think there's tremendous potential for further integration of some >>Of these projects. It just composability That makes total sense. Yep. Yep. You're, you're op you're operating and composing. >>Yep. And there's no reason that user experience can't be better. And then more people can create and build. So I think it's awesome. Matt, thank you so much. Thank you. Yeah, this has been fantastic. Be sure and check out Matt on Twitter to find out what that next secret project is. John, thank you for joining me this morning. My name is Savannah Peterson and we'll be here all day live from the cube. We hope you'll be joining us throughout the evening until a happy hour today. Thanks for coming. Thanks for coming. Thanks for watching.

>>Good afternoon everyone, and welcome back to Cuan where my cohost John Farer and I are broadcasting live, along with Lisa Martin from Cuan Detroit, Michigan. We are joined this afternoon by two very interesting gentlemen who also happen to be legends on the cube. John, how long have you known the next few? They've, >>They've made their mark on the cube with Jerry Chen from Greylock was one of our most attended cube guests. He's a VC partner at Greylock and an investor and this company that just launched their new cloud observability platform should be a great segment. >>Well, I'm excited. I are. Are you excited? Should I string this out just a little bit longer? No, I won't. I won't do that to you. Please welcome Martin and Jeff from Chronosphere Martin. Jeff, thank you so much for being >>Here. Thank you for having us. Thank you. >>I noticed right away that you have raised a mammoth series C. Yeah. 200 million if I'm not mistaken. >>That is correct. >>Where's the company at? >>Yeah, so we raised that series C a year ago. In fact, we were just talking about it a year ago at Cub Con. Since then, at the time we're about 80 employees or so. Since then, we've tripled the headcount, so we're over 200 people. Casual, triple casual, triple of the headcount. Yeah. Luckily it was the support of business, which is also tripled in the last year. So we're very lucky from that perspective as well. And a couple of other things we're pretty proud of last year. We've had a hundred percent customer retention, which is always a great thing to have as a SaaS platform there. >>Real metric if you've had a hundred percent. I'm >>Kidding. It's a good metric to, to put out there if you had a hundred percent. I would say for sure. It's an A for sure and exactly welcome to meet >>Anyone else who's had a hundred percent >>Customer attention here at coupon this week and 90% of our customers are using more of the service and, and you know, therefore paying more for the service as well. So those are great science for us and I think it shows that we're clearly doing something right on the product side. I would say. And >>Last and last time you're on the cube. We're talking about about the right data. Not so much a lot of data, if I remember correctly. Yeah, a hundred percent. And that was a unique approach. Yeah, it's a data world on relative observability. And you guys just launched a new release of your platform, cloud native platform. What's new in the platform? Can you share an update on what you guys release? >>Yeah, well we did and, and you, you bring up a great point. You know, like it's not just in observably but overall data is exploding. Alright, so three things there. It's like, hey, can your platform even handle the explosion of data? Can it control it over time and make sure that as your business grows, the data doesn't continue explode at the same time. And then for the end users, can they make sense of all this data? Cuz what's the point of having it if the end users can't make sense of it? So actually our product announcement this time is a pretty big refresh of, of a lot of features in our, in our platform. And it actually tackles all three of these particular components. And I'll let Jeff, our head of product, Doug, >>You, you run product, you get the keys to the kingdom, I do product roadmap. People saying, Hey this, take this out. You're under a lot of pressure. What makes the platform platform a great observability product? >>So the keystone of what we do that's different is helping you control the data, right? As we're talking about there's an infinite amount of data. These systems are getting more and more and more complicated. A lot of what we do is help you understand the utility of the telemetry so that you can optimize for keeping and storing and paying for the data that's actually helpful as opposed to the stuff that isn't. >>What's the benefit now with observability, with all the noise out in the marketplace, there's been a shift over the past couple years. Cloud native at scale, you're seeing a lot more automation, almost a set to support the growth for more application development. We had a Docker CEO on earlier today, he said there are more applications being deployed in the past year than in the history of open source. So more and more apps are being deployed, more data's being generated. What's the key to observability right now that's gonna separate the winners from the losers? >>Yeah, I think, you know, not only are there more applications being deployed, but there are smaller and small applications being deployed mostly on containers these days more than if they, hence this conference gets larger and larger every year. Right? So, you know, I think the key is a can your system handle this data explosion is, is the first thing. Not only can it handle the data explosion, but you know, APM solutions have been around for a very long time and those were really introspecting into an application. Whereas these days what's more important is, well how is your application interfacing with every other application in your distributed architecture there, right? So the use case is slightly different there. And then to what Jeff was saying is like once the data is there, not only making use of what is actually useful to you, but then having the end user make sense of it. >>Because we, we, we always think about the technology changes. We forget that the end users are different now we used to have IT operations team operating everything and the developers would write the application, just throw it over the wall. These days the developers have to actually operate this thing in production. So the end users of these systems are very different as well. And you can imagine these are folks, your average developer as maybe not operated things for many years in production before. So they need to, that they need to pick up a new skill set, they need to use new tooling in order to, to do that. So yeah, it's, it's, >>And you got the developer persona, you got a developer that's building products for builders and developers that are building products to be consumed. So they're not, they're not really infrastructure builders, they're just app developers. >>Exactly. Exactly. That's right. And that's what a lot of the new functionality that we're introducing here at the show is all about is helping developers who build software by day and are on call by night, actually get in context. There's so much data chances of when that, when one of those pages goes off and your number comes up, that the problem happens to be in the part of the system that you know a lot about are pretty low, chances are you're gonna get bothered about something else. So we've built a feature, we call it collections that's about putting you in the right context and connecting you into the piece of the system where the problem is to orient you and to get you started. So instead of waiting through, through hundreds of millions of things, you're waiting through the stuff that's in the immediate neighborhood of where the >>Problem is. Yeah. To your point about data, you can't let it go unchecked. That's right. You gotta gotta understand that. And we were talking about containers again with, again with docker, you know, nuance point, but oh, scan your container. But not everyone's scanning the containers security nightmare, right? I mean, >>Well I think one of the things that I, I loved in reading the notes in preparation for you coming up is you've actually created cloud native observability with the goal of eliminating engineering burnout. And what you're talking about there is actually the cognitive burden of when things happen. Yeah, for sure. We we're, you know, we're not just designing for when everything goes right, You need to be prepared for when everything goes wrong and that poor lonely individual in the middle of the night has, it's >>A tough job. >>Has to navigate that >>And, and observability is just one thing you gotta mean like security is another thing. So, so many more things have been piled on top of the developer in addition to actually creating the application. Right? It is. There is a lot. And you know, observably is one of those key things you need to do your job. So as much as, as much as we can make that easier, that's a better bit. Like there are so many things being piled on right now. >>That's the holy grail right there. Because they don't want to be doing exactly >>The work. Exactly. They're not observability experts. >>Exactly. And automating that in. So where do you guys weigh in on the automation wave? Everything's automation. Yeah. Is that kind of a hand waving or what's going on? What's the reality? What's actually happening? >>Yeah, I think automation I think is key. You hear a lot of ai ml ops there. I, I don't know if I really believe in that or having a machine self heal itself or anything like that. But I think automation is key because there are a lot of repeatable tasks in a lot of what you're doing. So once you detect that something goes wrong, generally if you've seen it before, you know what the fix is. So I think automation plays a key on the sense that once it's detected again the second time, the third time, okay, I know what I did the previous time, let, let's make sure we can do that again. So automation I think is key. I think it helps a lot with the burnout. I dunno if I'd go as far as the >>Same burnout's a big deal. >>Well there's an example again in the, in the stuff we're releasing this week, a new feature we call query accelerator. That's a form of automation. Problem is you got all this data, mountain of data, put you in the right context so you're at least in the right neighborhood, but now you need to query it. You gotta get the data to actually inform the specific problem you're trying to solve. And the burden on the developer in that situation is really high. You have to know what you're looking for and you have to know how to efficiently ask for it. So you're not waiting for a long time and >>We >>Built a feature, you tell us what you want, we will figure out how to get it for you efficiently. That's the kind of automation that we're focused on. That's actually a good service. How can we, it >>Sounds >>Blissful. How can we accelerate and optimize what you were gonna do anyway, rather than trying to read your mind or predict the future. >>Yes, >>Savannah, some community forward. Yeah, I, I'm, so I'm curious, you, you clearly lead with a lot of empathy, both of you and, and putting your, well you probably have experience with this as well, but putting your mind or putting yourself in the mind to the developer are, what's that like for you from a product development standpoint? Are you doing a lot of community engagement? Are you talking to developers to try and anticipate what they're gonna be needing next in terms of, of your offering? Or how has that work >>For you? Oh, for sure. So, so I run product, I have a lot of product managers who work for me. Somebody that I used to work with, she was accusing me, but what she called, she called me an anthropologist of a product manager. I >>Get these kind of you, the very good design school vibes from you both of you, which >>Is, and the reason why she said the way you do this, you go and you live with them in order to figure out what a day in their life is really like, what the job is really like, what's easy, what's hard. And that's what we try to aim at and try to optimize for. So that's very much the way that we do all of >>Our work. And that's really also highlights the fact that we're in a market that requires acute realtime data from the customer. Cause it's, and it's all new data. Well >>Yeah, it's all changing. The tools change every day. I mean if we're not watching how, and >>So to your point, you need it in real time as well. The whole point of moving to cloud native is you have a reliable product or service there. And like if you need to wait a few minutes to even know that something's wrong, like you've already lost at that point, you've already lost a ton of customers, potentially. You've already lost a ton of business. You know, to your point about the, the community earlier, one other thing we're trying to do is also give back to the community a little bit. So actually two days ago we just announced the open source of a tool that we've been using in our product for a very long time. But of course our product is, is a paid product, right? But actually open source a part of that tool thus that the broader community can benefit as well. And that tool which, which tool is that? It's, it's called Prom lens. And it's actually the Prometheus project is the open sourced metrics project that everybody uses. So this is a query builder that helps developers understand how to create queries in a much more efficient way. We've had in our product for a long time, but we're like, let's give that back to the community so that the broader community of developers out there can have a much easier time creating these queries as well. What's >>Been the feedback? >>We only now it's two days ago so I'm not, I'm not exactly sure. I imagine >>It's great. They're probably playing with it right now. >>Exactly. Exactly. Exactly. For sure. I imagine. Great. >>Yeah, you guys mentioned burnout before and we heard this a lot now you mentioned in terms of data we've been hearing and reporting about Insta security world, which is also data specific observability ties right into security. Yep. How does a company figure out, first of all, burnout's a big problem. It's more and more data coming. It's like, it's like doesn't stop and the breaches are coming too. How does a company know when they need that their observability strategy is broken? Is there sig signs of you know, burnout? Is there signs of breaches? I mean, what are some of the tell signs that if I'm a CSO I go, you know what, maybe I should check out promisee. When do, when do you guys match in and go we're a perfect fit to solve that problem? >>Yeah, I, I would say, you know, because we're focused on the observability side, less so on the security side, some of those signals are like how many incidents do you have? How many outages do you have? What's the occurrence of these things and how long does it take to recover from from from these particular incidents? How >>Upsetting are we finding customers? >>Upsetting are >>Customer. Exactly. >>And and one trend was seeing >>Not churn happening. Exactly. >>And one trend we're seeing in the industry is that 68% of companies are saying that they're having more incidents over time. Right. And if you have more incidents, you can imagine more engineers are being paid, are being woken up and they're being put under more stress. And one thing you said that very interesting is, you know, I think generally in the observability world, you ideally actually don't want to figure out the problem when it goes wrong. Ideally what you want to do these days is figure out how do I remediate this and get the business back to a running state as quickly as I can. And then when the business isn't burning, let me go and figure out what the underlying root cause is. So the strategy there is changed as well from the APM days where like I don't want to figure out the problem in real time. I wanna make sure my business and my service is running as it should be. And then separately from that, once it is then I wanna go >>Under understand that assume it's gonna happen, be ready to close that isolate >>The >>Fire. Exactly. Exactly. And, and you know, you can imagine, you know the whole movement towards C I C D, like generally when you don't touch a system, nothing goes wrong. You deploy change, first thing you do is not figure out why you change break thing. Get that back like underplay that change roll that change back, get your business back to a estate and then take the time where you're not under pressure, you're not gonna be burnt out to figure out what was it about my change that that broke everything. So, yeah. Got >>It. >>Well it's not surprising that you've added some new exciting customers to the roster. We have. We have. You want to tell the audience who they might >>Be? Yes. It's been a few big names in the last year we're pretty excited about. One is Snapchat, I think everybody knows, knows that application And one is Robin Hood. So you know, you can imagine very large, I'll say tech forward companies that have completed their migrations to, to cloud native or a wallet on their way to Cloudnative and, and we like helping those customers for sure. We also like helping a lot of startups out there cause they start off in the cloud native world. Like if you're gonna build a business today, you're gonna use Kubernetes from day one. Right? But we're actually interestingly seeing more and more of is traditional enterprises who are just early, pretty early on in their cloudnative migration then now starting to adopt cloud native at scale and now they're running to the same problems. As well >>Said, the Gartner data last year was something like 85% of companies had not made that transformation. Right. So, and that, I mean that's looking at larger scale companies, obviously >>A hundred, you're >>Right on the pulse. They >>Have finished it, but a lot of them are starting it now. So we're seeing pilot >>Projects, testing and cadence. And I imagine it's a bit of a different pace when you're working with some of those transforming companies versus those startups that are, are just getting rolling. I >>Love and you know, you have a lot of legacy use case you have to, like, if you're a startup, you can imagine there's no baggage, there's no legacy. You're just starting brand new, right? If you're a large enterprise, you have to really think about, okay, well how do I get my active business moved over? But yeah. >>Yeah. And how do you guys see the whole cloud native scale moving with the hyper scales? Like aws? You've got a lot of multi-cloud conversation. We call it super cloud in our narrative, but there's now this new, we're gonna get some of common services being identified. We're seeing a, we're seeing a lot more people recognize and with Kubernetes that hey, you know what, you could get some common services maybe across clouds with SOS doing storage. We got Min iOS doing some storage. Yeah. Cloud flare, I mean starting to see a lot more non-hyper scale systems. >>Yeah, I mean I, and I think that's the pattern there and I think it, it's, especially for enterprise at the top end, right? You see a, a lot of companies are trying to de-risk by saying, Hey, I, I don't want to bet maybe on one cloud provider, I sort of need to hedge my bets a little bit. And Kubernetes is a great tool to go do that. You can imagine some of these other tools you mentioned is a great way to do that. Observability is another great way to do that. Or the cloud providers have their observability or monitoring tooling, but it's really optimized just for that cloud provider, just for those services there. So if you're really trying to run either your custom applications or a multi-cloud approach, you really can't use one cloud providers solution to go solve that problem. Do you >>Guys see yourselves with that unifying >>Layer? We, we, we are a little bit as that lay because it's agnostic to each of the cloud providers. And the other thing is we actually like to understand where our customers run and then try to run their observability stack on a different cloud provider. Cuz we use the cloud ourselves. We're not running our own data centers of course, but it's an interesting thing where everybody has a common dependency on the cloud provider. So when us e one ofs hate to call them out, but when us E one ofs goes down, imagine half the internet goes down, right? And that's the time that you actually need observability. Right? Seriously. And every other tooling there. So we try to find out where do you run and then we try to actually run you elsewhere. But yeah, >>I like that. And nobody wants to see the ugly bits anyway. Exactly. And we all know who when we're all using someone when everything >>Exactly. Exactly, exactly. >>People off the internet. So it's very, I, I really love that. Martin, Jeff, thank you so much for being here with us. Thank you. What's next? What, how do people find out, how do they get one of the jobs since three Xing your >>Employee growth? We're hiring a lot. I think the best thing is to go check out our website chronosphere.io. You'll find out a lot about our, our, our careers, our job openings, the culture we're trying to build here. Find out a lot about the product as well. If you do have an observability problem, like that's the best place to go to find out about that as well. Right. >>Fantastic. Well if you want to join a quarter billion, a quarter of a billion dollar rocket ship over here and certainly a unicorn, get in touch with Martin and Jeff. John, thank you so much for joining me for this very special edition and thank all of you for tuning in to the Cube live here from Motor City. My name's Savannah Peterson and we'll see you in a little bit. >>Robert Herbeck. People obviously know you from Shark Tanks, but the Herbeck group has been really laser focused on cyber security. So I actually helped to bring my.

>>Hello everyone. My name is Savannah Peterson, coming to you live from the Kim Con Show floor on the cube here in Detroit, Michigan. The energy is pulsing big event for the Cloud Native Foundation, and I'm joined by John Furrier on my left. John. Hello. >>Great, great, great to have you on the cube. Thanks for being our new host. You look great, Great segment coming up. I'm looking forward to this. Savannah, this is a great segment. A cube alumni, an OG in the cloud, native world or cloud aati. I, as I call it, been there, done that. A lot of respect, a lot of doing some really amazing, I call it the super cloud holy grail. But we'll see >>Your favorite word, >>This favorite word, It's a really strong segment. Looking forward to hearing from this guest. >>Yes, I am very excited and I'm gonna let him tee it up a little bit. But our guest and his project were actually mentioned in the opening keynote this morning, which is very, very exciting. Ladies and gentlemen, please welcome Baam Tobar Baam, thanks for being here with >>Us. Thank you guys. So good to be back here on the show and, and this exciting energy around us. So it was super, super awesome to be here. >>Yeah, it feels great. So let's start with the opening keynote. Did you know you were gonna get that shout out? >>No, not at all. I, it was, it was really cool to see, you know, I think Cruz was up there talking about how they were building their own platform for autonomous cars and what's running behind it. And they mentioned all these projects and you know, we were like, Wow, that sounds super familiar. And then, then, and then they said, Okay, yeah, we we're, you know, cross plane. They mentioned cross plane, they mentioned, Upbound mentioned the work that we're doing in this space to help folks effectively run, you know, their own layer on top of cloud computing. >>And then Tom, we've known each other, >>We're gonna do a bingo super cloud. So how many times is this Super cloud? So >>Super Cloud is super services, super apps around us. He enables a lot of great things that Brian Grace had a great podcast this week on super services. So it's super, super exciting, >>Super great time on the queue. Super, >>Super >>Cloud conversation. All seriously. Now we've known each other for a long time. You've been to every cub com, you've been in open source, you've seen the seen where it's been, where it is now. Super exciting that in mainstream conversations we're talking about super cloud extractions and around interoperability. Things that were once like really hard to do back, even back on the opens stack days. Now we're at a primetime spot where the control plane, the data planes are in play as a viable architectural component of all the biggest conversations. Yeah, you're in the middle of it. What's your take on it? Give some perspective of why this is so important. >>I mean, look, the key here is to standardize, right? Get to standardization, right? And, and what we saw, like early days of cloud native, it was mostly around Kubernetes, but it was Kubernetes as a, you know, essentially a container orchestrator, the container of wars, Docker, Mesos, et cetera. And then Kubernetes emerged as a, a, the winner in containers, right? But containers is a workload, one kind of workload. It's, I run containers on it, not everything's containers, right? And the, you know, what we're seeing now is the Kubernetes API is emerging as a way to standardize on literally everything in cloud. Not just containers, but you know, VMs, serverless, Lambda, et cetera, storage databases that all using a common approach, a common API layer, a common way to do access control, a common way to do policy, all built around open source projects and you know, the cloud data of ecosystem that you were seeing around here. And that's exciting cuz we've, for the first time we're arriving at some kind of standardization. >>Every major inflection point has this defacto standard evolution, then it becomes kind of commonplace. Great. I agree with Kubernetes. The question I wanted to ask you is what's the impact to the DevOps community? DevSecOps absolutely dominated the playbook, if you will. Developers we're saying we'll run companies cuz they'll be running the applications. It's not a department anymore. Yes, it is the business. If you believe the digital transformation finds its final conclusion, which it will at some point. So more developers doing more, ask more stuff. >>Look, if you, I'd be hard pressed to find somebody that's has a title of DevOps or SRE that can't at least spell Kubernetes, if not running in production, right? And so from that perspective, I think this is a welcome change. Standardize on something that's already familiar to everyone is actually really powerful. They don't have to go, Okay, we learned Kubernetes, now you guys are taking us down a different path of standardization. Or something else has emerged. It's the same thing. It's like we have what, eight years now of cloud native roughly. And, and people in the DevOps space welcome a change where they are basically standardizing on things that are working right? They're actually working right? And they could be used in more use cases, in more scenarios than they're actually, you know, become versatile. They become, you know, ubiquitous as >>You will take a minute to just explain what you guys are selling and doing. What's the product, what's the traction, why are people using you? What's the big, big mo position value statement you guys think? >>Yeah, so, so, so the, my company's called Upbound and where the, where the folks behind the, the cross plane project and cross plane is effective, takes Kubernetes and extends it to beyond containers and to ev managing everything in cloud, right? So if you think about that, if you love the model where you're like, I, I go to Kubernetes cluster and I tell it to run a bunch of containers and it does it for me and I walk away, you can do that for the rest of the surface area of cloud, including your VMs and your storage and across cloud vendors, hybrid models, All of it works in a consistent standardized way, you know, using crossline, right? And I found >>What do you solve? What do you solve or eliminate? What happens? Why does this work? Are you replacing something? Are you extracting away something? Are you changing >>Something? I think we're layering on top of things that people have, right? So, so you'll see people are organized differently. We see a common pattern now where there's shared services teams or platform teams as you hear within enterprises that are responsible for basically managing infrastructure and offering a self-service experience to developers, right? Those teams are all about standardization. They're all about creating things that help them reduce the toil, manage things in a common way, and then offer self-service abstractions to their, you know, developers and customers. So they don't have to be in the middle of every request. Things can go faster. We're seeing a pattern now where the, these teams are standardizing on the Kubernetes API or standardizing on cross plane and standardizing on things that make their life easier, right? They don't have to replace what they're doing, they just have to layer and use it. And I layer it's probably a, an opening for you that makes it sound >>More complex, I think, than what you're actually trying to do. I mean, you as a company are all about velocity as an ethos, which I think is great. Do you think that standardization is the key in increasing velocity for teams leveraging both cross claim, Kubernetes? Anyone here? >>Look, I mean, everybody's trying to achieve the same thing. Everybody wants to go faster, they want to innovate faster. They don't want tech to be the friction to innovation, right? Right. They want, they wanna go from feature to production in minutes, right? And so, or less to that extent, standardization is a way to achieve that. It's not the only way to achieve that. It's, it's means to achieve that. And if you've standardized, that means that less people are involved. You can automate more, you can st you can centralize. And by doing that, that means you can innovate faster. And if you don't innovate these days, you're in trouble. Yeah. You're outta business. >>Do you think that, so Kubernetes has a bit of a reputation for complexity. You're obviously creating a tool that makes things easier as you apply Kubernetes outside just an orchestration and container environment. Do you, what do you see those advantages being across the spectrum of tools that people are leveraging you >>For? Yeah, I mean, look, if Kubernetes is a platform, right? To build other things on top of, and as a, as a result, it's something that's used to kind of on the back end. Like you would never, you should put something in front of Kubernetes as an application model or consumption interface of portals or Right, Yeah. To give zero teams. But you should still capture all your policies, you know, automation and compliance governance at the Kubernetes layer, right? At the, or with cross plane at that layer as well, right? Right. And so if you follow that model, you can get the best of world both worlds. You standardize, you centralize, you are able to have, you know, common controls and policies and everything else, but you can expose something that's a dev friendly experience on top of as well. So you get the both, both the best of both worlds. >>So the problem with infrastructure is code you're saying is, is that it's not this new layer to go across environments. Does that? No, >>Infrastructure is code works slightly differently. I mean, you, you can, you can write, you know, infrastructures, codes using whatever tooling you like to go across environments. The problem with is that everybody has to learn a specific language or has to work with understanding the constructs. There's the beauty of the Kubernetes based approach and the cross playing best approach is that it puts APIs first, right? It's basically saying, look, kind of like the API meant that it, that led to AWS being created, right? Teams should interact with APIs. They're super strong contracts, right? They're visionable. Yeah. And if you, if you do that and that's kind of the power of this approach, then you can actually reach a really high level of automation and a really high level of >>Innovation. And this also just not to bring in the clouds here, but this might bring up the idea that common services create interoperability, but yet the hyper scale clouds could still differentiate on value very much faster processors if it's silicon to better functions if glam, right? I mean, so there's still, it's not killing innovation. >>It is not, And in fact I, you know, this idea of building something that looks like the lowest common denominator across clouds, we don't actually see that in practice, right? People want, people want to use the best services available to them because they don't have time to go, you know, build portability layers and everything else. But they still, even in that model want to standardize on how to call these services, how to set policy on them, how to set access control, how to actually invoke them. If you can standardize on that, you can still, you get the, you get to use these services and you get the benefits of standardization. >>Well Savannah, we were talking about this, about the Berkeley paper that came out in May, which is kind of a super cloud version they call sky computing. Their argument is that if you try to standardize too much like the old kind of OSI model back in the day, you actually gonna, the work innovations gonna stunt the growth. Do you agree with that? And how do you see, because standardization is not so much a spec and it it, it e f thing. It's not an i e committee. Yeah. It's not like that's kind of standard. It's more of defacto, >>I mean look, we've had standards emerge like, you know, if you look at my S SQL for example, and the Postgres movement, like there are now lots of vendors that offer interfaces that support Postgres even though they're differentiated completely on how it's implement. So you see that if you can stick to open interfaces and use services that offer them that tons of differentiation yet still, you know, some kind of open interface if you will. But there are also differentiated services that are, don't have open interfaces and that's okay too. As long as you're able to kind of find a way to manage them in a consistent way. I think you sh and it makes sense to your business, you should use >>Them. So enterprises like this and just not to get into the business model side real quick, but like how you guys making money? You got the project, you get the cross playing project, that's community. You guys charging what's, what's the business model? >>We we're in the business of helping people adopt and run controlled lanes that do all this management service managed service services and customer support and services, the, the plethora of things that people need where we're >>Keeping the project while >>Keeping the project. >>Correct. So that's >>The key. That's correct. Yeah. You have to balance both >>And you're all over the show. I mean, outside of the keynote mention looking here, you have four events on where can people find you if they're tuning in. We're just at the beginning and there's a lot of looks here. >>Upbound at IO is the place to find Upbound and where I have a lot of talks, you'll see Crossline mention and lots of talks and a number of talks today. We have a happy hour later today we've got a booth set up. So >>I'll be there folks. Just fyi >>And everyone will be there now. Yeah. Quick update. What's up? What's new with the cross plane project? Can you share a little commercial? What's the most important stories going on there? >>So cross plane is growing obviously, and we're seeing a ton of adoption of cross plane, especially actually in large enterprise, which is really exciting cuz they're usually the slow to move and cross plane is so central, so it's now in hundreds and thousands of deployments in woohoo, which is amazing to see. And so the, the project itself is adding a ton of features, reducing friction in terms of adoption, how people ride these control planes and alter them coverage of the space. As you know, controls are only useful when you connect them to things. And the space is like the amount of things you can connect control planes to is increasing on a day to day basis and the maturity is increasing. So it's just super exciting to see all of this right >>Now. How would you categorize the landscape? We were just talking earlier in another segment, we're in Detroit Motor City, you know, it's like teaching someone how to drive a car. Kubernetes pluss, okay, switch the gears like, you know, don't hit the other guy. You know? Now once you learn how to drive, they want a sports car. How do you keep them that progression going? How do you keep people to grow continuously? Where do you see the DevOps and or folks that are doing cross playing that are API hardcore? Cause that's a good IQ that shows 'em that they're advancing. Where's the IQ level of advancement relative to the industry? Is the adoption just like, you know, getting going? Are people advancing? Yeah. Sounds like your customers are heavily down the road on >>Yeah, the way I would describe it is there's a progression happening, right? It, it DevOps was make, initially it was like how do I keep things running right? And it transitioned to how do I automate things so that I don't have to be involved when things are running, running. Right now we're seeing a next turn, which is how do I build what looks like a product that offers shared services or a platform so that people consume it like a product, right? Yeah. And now I'm now transition becomes, well I'm an, I'm a developer on a product in operations building something that looks like a product and thinking about it as a, as a has a user interface. >>Ops of the new devs. >>That's correct. Yeah. There we go. >>Talk about layers. Talk about layers on layers on >>Layers. It's not confusing at all John. >>Well, you know, when they have the architecture architectural list product that's coming. Yeah. But this is what's, I mean the Debs are got so much DevOps in the front and the C I C D pipeline, the ops teams are now retrofitting themselves to be data and security mainly. And that's just guardrails, automation policy, seeing a lot of that kind of network. Like exactly. >>Function. >>Yep. And they're, they're composing, not maybe coding a little bit, but they not, they're not >>Very much. They're in the composition, you know that as a daily thing. They're, they're writing compositions, they're building things, they're putting them together and making them work. >>How new is this in your mind? Cause you, you've watching this progress, you're in the middle of it, you're in the front wave of this. Is it adopting faster now than ever before? I mean, if we talked five years ago, we were kind of saying this might happen, but it wasn't happening today. It kind, it is, >>It's kind of, it's kind of amazing. Like, like everybody's writing these cloud services now. Everybody's authoring things that look like API services that do things on top of the structure. That move is very much, has a ton of momentum right now and it's happening mainstream. It, it's becoming mainstream. >>Speaking of momentum, but some I saw both on your LinkedIn as well as on your badge today that you are hiring. This is your opportunity to shamelessly plug. What are you looking for? What can people expect in terms of your company culture? >>Yeah, so we're obviously hiring, we're hiring both on the go to market side or we're hiring on the product and engineering side. If you want to build, well a new cloud platform, I won't say the word super cloud again, but if you want to, if you're excited about building a cloud platform that literally sits on top of, you know, the other cloud platforms and offers services on top of this, come talk to us. We're building something amazing. >>You're creating a super cloud tool kit. I'll say it >>On that note, think John Farer has now managed to get seven uses of the word super cloud into this broadcast. We sawm tomorrow. Thank you so much for joining us today. It's been a pleasure. I can't wait to see more of you throughout the course of Cuban. My name is Savannah Peterson, everyone, and thank you so much for joining us here on the Cube where we'll be live from Detroit, Michigan all week.

>>Welcome back everyone to the cubes live coverage here in San Francisco for VMware Explorer. I'm John farer, Dave LAN two days of Wal three days of Wal Walker. Two sets live events got PERA, had Metabo, senior vice president and general manager of cloud management at VMware. I got it. Right. Thanks for coming on the queue. >>You got it right. Good to >>Be here. We're all smiles. Cause we were talking about your history. You once worked at loud cloud and we were reminiscent about how cloud was before cloud was even cloud. Exactly. And how, how hard it was. >>And >>It's still hard. Complexity is a big deal. And one of the segments we want to talk to you about is the announcement around aria and you see cloud manage a big part of this direction to multi-cloud yes. To tame the complexity. And you know, we were quoting Andy Grove on the cube, let chaos rain, and then rain in the chaos. Exactly. Okay. A very famous quote in tech and the theme here is cloud chaos. Yes. And so we're starting to see signs of raining in that chaos or solving complexity. And every major inflection point has this moment where yes, it gets so hard and then it kicks up to the right and grows and link gets solved. So we feel like we're in that moment. >>I couldn't agree more. And in fact, the way I say is our, our, our tagline is we make the complexity of managing cloud invisible so that you can focus on building your business apps. And you're right about the inflection point. Every time a new technology hits, you have some point of adoption and then it becomes insanely successful. And that's when the complexity hits, then you go and tame the complexity till the next technology hits. Right? That's what happens. It's happened with virtualization. Then it has happened with cloud then with containerization and now the next one will hit. And so with aria, we said, we have to fundamentally change the problem, right? We are constantly running a race of TAing, this complexity. So very excited about this announcement with which we're doing with aria. And we said, imagine if I could have a view of my environment and all the dependencies, I don't need to know everything, just the environment and its dependencies. Then I can now start solving problems and answering questions that I was unable to before. And newer technologies can keep coming and piling on, but I'll always be able to answer that, help >>Our audience understand Ari, a great name and, and what's new. Your Heka what's new from, you know, it's not just V V realize with a new name what's what's new specifically. >>Yeah. Please. No. >>Explain some people. Well, >>There's some commentary on snarky comments, but it's a product it's not a rebrand of something >>Else. It's right. It's not explain that. It's not a, yeah. So what we did is let, let me start off. Why, why we started aria? So we said, okay, native public managing environments, native public cloud environments and cloud native applications is a different ballgame, more Emeral workloads, very large scale, highly fragmented data. So we looked at that problem rounds up and said, we need to have a management solution that solves that problem focused on native public cloud and cloud native apps and the core to solving that problem was you can't just solve it for one cloud or you can't solve it for one discipline. When I say discipline, when you think about management, what do you manage? You're managing to optimize cost. You're managing to optimize performance. You're managing to optimize your security and you're managing to speed up the delivery. That is it. And so we said, we'll have a new look to this management. And what we have done with aria is we have introduced a brand new platform, which we call aria hub powered by aria graph, which allows you to deliver this man on this management challenges, by creating a map of your environment, a near real time map of your environment. And then we are able to, once we know what an application looks like and how it maps to the infrastructure, we can go and query other subsystems to tell you, what is the cost of an application? What is the performance of an application? Creating a common understanding >>This now it's a new architecture. >>I just wanted to get that out there. It's federated >>New graph database. >>Yes. It's a new architecture federated, a platform that not only gives you a map of your environment, but it federates into other sources to pull that data together. Right now, one of the data sources that it federates into is of course also we realize, yeah, yeah. Cloud health, >>You plug and >>Cloud observability. You plug everything into it. Yeah. And as part of the announcement, we didn't just announce a platform. We also announced a set of crosscutting solutions cuz we said, okay, what is the power of the platform? The big thing is it removes the swivel share management. It allows you to answer questions you couldn't answer before. And so >>Swivel share meaning going from one app to another one app logging in exactly >>Credentials in credentials. And you don't have a common understanding of app across those. So now you hire people who do integration buses, right? All kinds of cloud. So the three new end to end solutions we are announcing also in, along with the platform, these are brand new. One is something called aria guardrails. So when I have development environments today, for example, my, I do development on public cloud as well as private cloud. I have thousands of accounts, each one with its own security rules, each one with its own policies. After I initially deploy the account, it becomes a nightmare to manage that. So what aria guardrails allows you to do is set up these multi-cloud environments with the right policies. And not only is it about one time provisioning, but it is maintaining them on >>A run basis. And those credentials are also risk. Cuz you have a password on the dark web, that's exposed on one and you've got to change it. And, and there's so many things going on exactly on security, which brings me up to the point of, you know, we were talking, we're gonna see Tom later on security. We heard earlier, why wasn't security in the keynote? Oh, it's table stakes. That's what Z has said. But we're like, okay, I get that. So let's just say that security is table stakes. There's a big trend towards security as a state of something at a, at a given time. And that CSOs and CSOs are going to defensible. Yes. Meaning being defensible all the time. Yes. As an ongoing thing, which is not just running a pen test once a week. Yes. Like multiple testing, real testing. Not simulation. Yes. To be secure. Yes. So it's not about being secure. It's about having security, but defense ability is the action now not yeah. Yeah. >>Can >>You does that, how does that fit into this? Because this seems to like be in this wheelhouse of management. >>No, I think you're bringing a very important point, which is the security as a post. The fact item is no longer. Right? Right. You want to bake in security. This is a shift left of security that we talk about when you're building an application and you are deploying code in your test, you wanna say, Hey, what is the security? Is it secure? Is it meeting my guardrail? Then when you deploy it from an operations perspective, also it is a security concern. It's not just a security team's concern now. So is my configuration right? Is my configuration secure? Has, is it drifting? It's never a snapshot in time. It's constantly, you have to look at it. Is it drifting? And that is exactly what we are doing also with aria. So >>That's part of the solution you're talking about in the guardrails within being >>Able to maintain the secure configuration right now, as I said, there's always a security discipline. Yeah. Which is you are done by security teams, but you also want operations teams and development teams to enforce security in their respective practices. And that's what Ari allows you to do. >>So the question on multi-cloud comes in, okay. So this is all good. By the way, we love that shift left again, very developer. And I would argue actually we are argue on the cube. That dev ops is the development environment for cloud native. So the it operational once called ops is now in dev just saying he is, and then data ops and security ops are now the new it because that's where the hard problems are. So how do you look at the data side of it as well as security in your view of multi-cloud because you know, hybrid cloud, I can see the steady state between, you know, on premises and cloud, if it's operating cloudlike but now you're starting to look at spanning clouds. Yes. Yes. Not full spanning workloads. That's not there yet, but certainly people have multiple clouds. Yeah. But when you data seems to be the first thing spanning not necessarily the app itself, but how do you guys view that multi-cloud aspect of what you're managing? I mean, how you look at that? >>I think there are different angles to it. Right? You can look at it from the data angle and you look at it on how the, how protected a data is for us. When you look at management discipline, it is all from the perspective of configurations. Okay. If I have configured my environment correctly, then you should not be able to do something that destroys or the data. Right. So getting the configuration right. When you're developing that, getting the configuration right. When you're provisioning the app and then getting the configuration, right. Even when you're doing day two and ongoing operations, that is what we bring to the table. And to some extent, that aria visibility, that I was talking about an Ary graph, a near real time view of the configuration state and its dependencies is very critical. So now I can ask questions. Is there a misconfiguration, by the way, the answer is yes, they, yeah. >>That is a lot by the way, too, right? Yeah. >>Which, which exposes me. And then you can say, Hey, is there user activity associated with that misconfigured? Good object. Now suddenly you have go, go to a red alert. So not only something misconfigured, but there is user activity associated with the misconfigured data. You know, this is something that I have. This >>Is where AI sings beautifully because beautifully, once you have the configuration baseline done, yes. It's like securing the S3 bucket, which is like a knee has to be a like brushing your teeth. It's gotta be a habit. Exactly. It's like, you just don't even think about, you just don't leave an S3 bucket. >>It's gotta be simplified because you're, we're asking the devs now to be security pros, correct. Secure the run time, secure the paths, you know, secure the containers. And so they need help. This is not what they wake up in the morning passionate about. Right. >>But that is where the guardrails comes in. Totally. Yeah. So a a developer, why should they care? They should just say, look, I'm developing for the credit card industry. I need a PCI compliant environment. And then let us take care of defining that environment, deploying that environment, managing that environment on an ongoing basis, they should be building code. Yeah. Right. But there is a change also, which is in the past, these were like two different islands and two different views with aria graft. We also have created this unified API that a developer could query or an ops could query to create a common understanding of the environment. So you're not looking at, you know, the elephant won the trunk and the other one, the tail you're looking at it in a common way. >>Can you talk about the collaboration between tan zoo and aria portfolios? Because obviously the VMware customers are investing in tan zoo. A lot of stuff's coming outta the oven. We heard some Dave heard some stuff from Chris Wolf and he's gonna come on tomorrow. And Raghu was hinting at some other stuff. That's not yet public, but you know, this things happening, >>Things happening, lot of >>Things, you know, you know, announcements happened years ago last year. Now some fruit's coming off the tree, this is a hot product aria. It makes a lot of sense for the customers. Where's the cloud native stuff, kicking, connecting in. What's the give us the overview what's connection >>Is lots and lots of connections. So you have a beautiful Kubernetes environment and a cloud native platform. You have accelerated app development. Now you're building more apps, more microservices based apps, more fragmented data, more information. So think of aria as an envelope around all of this. So wherever you are, whether you are building an application, deploying an application, managing an application, retiring an application through that life cycle, we can bring that management. So what we are doing with Tansu is with the platform, develop and platform. Now we can hook in management with a common perspective earlier in the life cycle. I don't have to wait for it to go to production to start saying, is it secure? Is it configured? How is it performing? What is my cost trade off as a developer, I've decided to, to fix a latency issue, I'm gonna add a new region or I'm gonna scale out a particular tier. Do I know how much it'll cost me? Can I give you that right at your fingertips, potentially even within the development platform and within the ID, that's the power, right? So bringing Ary, >>Not a lot of heavy lifting on the develop. So it's pretty much almost like a query to a database or >>As simple API that they can just query as part of their development process. Yeah. So by bringing aria and Tansu and really aria en developing Tansu right. You're able to bring that power >>Developer. I just always smile because you, I remember we, we have a group called the cloud. AATI the early OG found cloud. >>AATI >>The early days of cloud. When we were talking about infrastructure as code yes. Way back when, and finally it's actually happening. So what you're describing is infrastructure's code because now there's more complexity happening under the hard and top and you know, service are being turned on and off automatically. Yes. And sometimes you might not even know what's going on. Exactly. If you have guard rail, >>But you have to discover the state, know something has turned on, understand the implication and then synthesize, synthesize it down to the insight for the user. >>You know, a lot of people have been complaining about other older companies. Like Splunks the world who have great logging technology for gen one cloud, but now these new logging logging becomes a problem. Can you talk about how you guys are handling that? Give confidence or yeah. Explain that there's everything's gonna be logged properly. Yeah. >>So, so really look, there are three disciplines that we have management. Discipl like, ultimately there are thousands of names, but it boils down to you're managing the cost. You're managing the security, you're managing the performance of your applications. That is it. Right. So what we found is when you think of these disciplines as siloed load solutions, you can't ask a simple question as what is my cost performance trade off. You can't ask a simple question as, Hey, I'm improving performance. How, what is the implication of security? And that's when you start building complex solutions that say, okay, let me collect log from here. Let me collect this from here. Then let me correlate and normalize an application definition and tell you something and then put it in a spreadsheet and put it in a spreadsheet finally for manual work. Exactly. So one of the pillars is about managing performance. >>We have very powerful capabilities today in our portfolio. Tansu observability, which is part of aria portfolio. We realize log, which is part of aria portfolio, networks, insights, and operations. So with the common, when you, when you have a common language, we have a common language. We understand each other. Similarly with Ary graph and aria hub, we have creating this common language. So once we create a common language, all the various observability and log solutions have a meaning. They have relevance. And so we are able to take the noise from all these systems and synthesize it down to what we call business insights. And that's what is one of the big announcement as part of aria, awesome take data, which we have lots of and convert it to information. >>Give us the bumper sticker on why VMware. >>Well, I I'll tell you, when you talk about various public clouds, each public cloud has their native solutions. I've got control tower, I've got cloud wash, cloud trail, different solutions, and some of the hyperscalers are also expanding their solutions to other cloud. I think VMware in a way, from a multi-cloud perspective, we are in a wonderfully neutral position. Not only do we have a wealth of technology and assets that we can bring to the game, but we can also do it evenly across all clouds. So, so look at something like cost. Do you trust one of the hyperscalers to tell you that what is the cost comparison between them and another hyperscaler? That is where the VMware value comes in? >>I think people just try to hear what the cost of one cloud. Exactly, exactly. That is often people make money doing that is a job. No, >>No, definitely. Even a single cloud. What is the cost? >>It's a cloud economist out there and we know who he is. Corey Corey, a friend of the cube. He does it for his living. So help people figure out their bill. Exactly. Just on one cloud. >>Exactly. It's one cloud. So being able, we have the unique position where, and the right sets of technologies and experiences to bring that solution to bear across multicloud. Right. Great. >>What's your vision real quick. One minute left. What's your vision for the group? What are you investing in? What's your goals? What are you trying to do? Ask you the products. New. Gonna roll that out. What's what's the plan. I >>Really, again, the biggest one, the, the, the tagline I talked about, right. I, I, I want to, you know, I'm telling customers, managing stuff is boring. Don't waste your time on it. Let us take care of it. Right? So make the cloud complexity invisible so that you can focus on building your applications and everything that we do in the business unit is targeted towards that one goal. It is not about doing more features, more capabilities. It's are you solving customers questions? And we start from question down, >>Be thank you for spending your valuable time here in the cube, explaining the new news. Appreciate it. All right. Get lunch. After the short breaks, stay more with the cube live here in San Francisco for VMware Explorer, 22. I'm John that's. Dave. >>Thank you.