>>The Cube is live with three different stages here at AW S Reinvent in fabulous Las Vegas, Nevada. My name's Savannah Peterson, and I gotta tell you, even though the cube has been at AW w s reinvent for over a decade, this is my first year and wow, is it just buzzing in here? >>It's >>Busy, it's crowd, it's loud. >>So exciting to be here with you all. >>We're hearing north of 50,000 people, and I'm hearing hundreds of thousands online. >>No, it's going great. There's lots of buzz, lots of excitement this year, of course, three times a number of people, but it's fantastic. >>Everyone at the same place at the same time. Energy is just pretty special. So it's >>Fun. >>I mean, AWS is a friendly place for security companies and I'm excited to talk about that. >>Let's be here. We have a lot coming for you. We're super excited and if you think about it, it's price, performance, it's data, it's security, and it's solutions for purpose-built use cases. >>Great job. Congratulations. I love the mess. I love how you guys had the theme. I thought his keynote was great and it's great to see Amazon continue to innovate. >>My name is Savannah Peterson. We are the Cube and we are the leading source for high tech coverage.

(upbeat music) >> Hello, brilliant humans and welcome back to theCUBE. We're live from Detroit, Michigan. My name is Savannah Peterson. Joined here with John Furrier, John, so exciting, day three. >> Day three, cranking along, doing great, final day of KubeCon, it wraps up. This next segment's going to be great. It's about WebAssembly, the hottest trend here, at KubeCon that nobody knows about cause they just got some funding and it's got some great traction. Multiple players in here. People are really interested in this and they're really discovering it. They're digging into it. So, we're going to hear from one of the founders of the company that's involved. So, it'll be great. >> Yeah, I think we're right at the tip of the iceberg really. We started off the show with Scott from Docker talking about this, but we have a thought leader in this space. Please welcome Matt Butcher the CEO and co-founder of Fermyon Thank you for being here. Welcome. >> Yeah, thanks so much for having me. Favorite thing to talk about is WebAssembly after that is coffee but WebAssembly first. >> Hey, it's the morning. We can talk about both those on the show. (all chuckles) >> It might get confusing, but I'm willing to try. >> If you can use coffee as a metaphor to teach everyone about WebAssembly throughout the rest of the show. >> All right. That would be awesome. >> All right I'll keep that in mind. >> So when we were talking before we got on here I thought it was really fun because I think the hype is just starting in the WebAssembly space. Very excited about it. Where do you think we're at, set the stage? >> Honestly, we were really excited to come here and see that kind of first wave of hype. We came here expecting to have to answer the question you know, what is WebAssembly and why is anybody looking at it in the cloud space, and instead people have been coming up to us and saying, you know this WebAssembly thing, we're hearing about it. What are the problems it's solving? >> Savannah: Yeah. >> We're really excited to hear about it. So, people literally have been stopping us in restaurants and walking down the street, hey, "You're at KubeCon, you're the WebAssembly people. Tell us more about what's going on." >> You're like awesome celeb. I love this. >> Yeah, and I, >> This is great >> You know the, the description I used was I expected to come here shouting into the void. Hey, you know anybody, somebody, let me tell you about WebAssembly. Instead it's been people coming to us and saying "We've heard about it. Get us excited about it," and I think that's a great place to be. >> You know, one of the things that's exciting too is that this kind of big trend with this whole extraction layer conversation, multicloud, it reminds me of the old app server days where, you know there was a separation between the back end and front end, and then we're kind of seeing that now with this WebAssembly Wasm trend where the developers just want to have the apps run everywhere and the coding to kind of fall in, take a minute to explain what this is, why it's important, why are people jazzed about there's other companies like Cosmonic is in there. There's a lot of open source movement behind it. You guys are out there, >> Savannah: Docker. >> 20 million in fresh funding. Why is this important? What is it and why is it relevant right now? Why are people talking about it? >> I mean, we can't... There is no penasia in the tech world much for the good of all of us, right? To keep us employed. But WebAssembly seems to be that technology that just sort of arose at the right time to solve a number of problems that were really feeling intractable not very long ago. You know, at the core of what is WebAssembly? Well it's a binary format, right? But there's, you know, built on the same, strain of development that Java was built on in the 90's and then the .net run time. But with a couple of little fundamental changes that are what have made it compelling today. So when we think about the cloud world, we think about, okay well security's a big deal to us. Virtual machines are a way for us to run other people's untrusted operating systems on our hardware. Containers come along, they're a... The virtual machine is really the heavyweight class. This is the big thing. The workhorse of the cloud. Then along come Containers, they're a little slimmer. They're kind of the middleweight class. They provide us this great way to sort of package up just the application, not the entire operating system just the application and the bits we care about and then be able to execute those in a trusted environment. Well you know, serverless was the buzzword a few years ago. But one thing that serverless really identified for us is that we didn't actually have the kind of cloud side architecture that was the compute layer that was going to be able to fulfill the promise of serverless. >> Yeah. >> And you know, at that time I was at Microsoft we got to see behind the curtain and see how Azure operates and see the frustration with going, okay how do we get this faster? How do we get this startup time down from seconds to hundreds of milliseconds, WebAssembly comes along and we're able to execute these things in sub one millisecond, which means there is almost no cost to starting up one of these. >> Sub one millisecond. I just want to let everyone rest on that for a second. We've talked a lot about velocity and scale on the show. I mean everyone here is trying to do things faster >> Yep >> Obviously, but that is a real linchpin that makes a very big difference when we're talking about deploying things. Yeah. >> Yeah, and I mean when you think about the ecological and the cost impact of what we're building with the cloud. When we leave a bunch of things running in idle we're consuming electricity if nothing else. The electricity bill keeps going up and we're paying for it via cloud service charges. If you can start something in sub one millisecond then there's no reason you have to leave it running when nobody's using it. >> Savannah: Doesn't need to be in the background. >> That's right. >> So the lightweight is awesome. So, this new class comes up. So, like Java was a great metaphor there. This is kind of like that for the modern era of apps. >> Yeah. >> Where is this going to apply most, do you think? Where's it going to impact most? >> Well, you know, I think there are really four big categories. I think there's the kind of thing I was just talking about I think serverless and edge computing and kind of the server class of problem space. I think IOT is going to benefit, Amazon, Disney Plus, >> Savannah: Yes, edge. >> And PBS, sorry BBC, they all use WebAssembly for the players because they need to run the same player on thousands of different devices. >> I didn't even think about that use case. What a good example. >> It's a brilliant way to apply it. IOT is a hard space period and to be able to have that kind of layer of abstraction. So, that's another good use case >> Savannah: Yeah. >> And then I think this kind of plugin model is another one. You see it was Envoy proxy using this as a way to extend the core features. And I think that one's going to be very, very promising as well. I'm forgetting one, but you know. (all chuckles) I think you end up with these kind of discreet compartments where you can easily fit WebAssembly in here and it's solving a problem that we didn't have the technology that was really adequately solving it before. >> No, I love that. One of the things I thought was interesting we were all at dinner, we were together on Tuesday. I was chatting with Paris who runs Deliveroo at Apple and I can't say I've heard this about too many tools but when we were talking about WebAssembly she said "This is good for everybody" And, it's really nice when technologies come along that will raise the water level across the board. And I love that you're leading this. Speaking of you just announced a huge series aid, 20 million dollars just a few days ago. What does that mean for you and the team? >> I mean there's a little bit of economic uncertainty and it's always nice, >> Savannah: Just a little bit. >> Little bit. >> Savannah: It's come up on the show a little bit this week >> Just smidge. and it's nice to know that we're at a critical time developing this kind of infrastructure layer developing this kind of developer experience where they can go from, you know, blinking cursor to deployed application in two minutes or less. It would be a tragedy if that got forestalled merely because you can't achieve the velocity you need to carry it out. So, what's very exciting about being able to raise around like that at this critical time is that gives us the ability to grow strategically, be able to continue releasing products, building a community around WebAssembly as a whole and of course around our products at Fermyon is a little smaller circle in the bigger circle, and that's why we are so excited about having closed around, that's the perfect one to extend a runway like that. >> Well I'm super excited by this because one I love the concept. I think it's very relevant, like how you progress heavyweight, middleweight, maybe this is lightweight class. >> I know, I'm here for the analogy. No, it's great, its great. >> Maybe it's a lightweight class. >> And we're slimming, which not many of us can say in these times so that's awesome. >> Maybe it's more like the tractor trailer, the van, now you got the sports car. >> Matt: Yeah, I can go.. >> Now you're getting Detroit on us. >> I was trying for a coffee, when I just couldn't figure it out. (all chuckles) >> So, you got 20 million. I noticed the investors amplify very good technical VC and early stage firm. >> Amazing, yeah. >> Insight, they do early stage, big early stage like this. Also they're on the board of Docker. Docker was intent to put a tool out there. There's other competition out there. Cosmonic is out there. They're funded. So you got VC funded companies like yourselves and Cosmonic and others. What's that mean? Different tool chains, is it going to create fragmentation? Is there a common mission? How do you look at the competition as you get into the market >> When you see an ecosystem form. So, here we are at KubeCon, the cloud native ecosystem at this point I like to think of them as like concentric rings. You have the kind of core and then networking and storage and you build these rings out and the farther out you get then the easier it is to begin talking about competition and differentiation. But, when you're looking at that core piece everybody's got to be in there together working on the same stuff, because we want interoperability, we want standards based solutions. We want common ways of building things. More than anything, we want the developers and operators and users who come into the ecosystem to be able to like instantly feel like, okay I don't have to learn. Like you said, you know, 50 different tools for 50 different companies. "I see how this works", and they're doing this and they're doing this. >> Are you guys all contributing into the same open source? >> Yep, yeah, so... >> All the funding happens. >> Both CNCF and the ByteCode Alliance are organizations that are really kind of pushing forward that core technology. You know, you mentioned Cosmonic, Microsoft, SOSA, Red Hat, VMware, they're all in here too. All contributing and again, with all of us knowing this is that nascent stage where we got to execute it. >> How? >> Do it together. >> How are you guys differentiating? Because you know, open source is a great thing. Rising Tide floats all boats. This is a hot area. Is there a differentiation discussion or is it more let's see how it goes, kind of thing? >> Well for us, we came into it knowing very specifically what the problem was we wanted to solve. We wanted this serverless architecture that executed in sub one millisecond to solve, to really create a new wave of microservices. >> KubeCon loves performance. They want to run their stuff on the fastest platform possible. >> Yeah, and it shouldn't be a roadblock, you know, yeah. >> And you look at someone like SingleStore who's a database company and they're in it because they want to be able to run web assemblies close to the data. Instead of doing a sequel select and pulling it way out here and munging it and then pushing it back in. They move the code in there and it's executing in there. So everybody's kind of finding a neat little niche. You know, Cosmonic has really gone more for an enterprise play where they're able to provide a lot of high level security guarantees. Whereas we've been more interested in saying, "Hey, this your first foray into WebAssembly and you're interested in serverless we'll get you going in like a couple of minutes". >> I want to ask you because we had Scott Johnston on earlier opening keynote so we kind of chatted one-on-one and I went off form cause I really wanted to talk to him because Docker is one of the most important companies since their pivot, when they did their little reset after the first Docker kind of then they sold the enterprise off to Mirantis they've been doing really, really well. What's your relationship to Docker? He was very bullish with you guys. Insights, joint investor. Is there a relationship? You guys talk, what's going on there? >> I mean, I'm going to have to admit a little bit of hero worship on my part. I think Scott is brilliant. I just do, and having come from the Kubernetes world the Fermyon team, we've always kind of kept an eye on Docker communicated with a lot of them. We've known Justin Cormack for years. Chris Cornett. (indistinct) I mean yeah, and so it has been a very natural >> Probably have been accused of every Docker Con and we've did the last three years on the virtual side with them. So, we know them really well. >> You've always got your finger on the pulse for them. >> Do you have a relationship besides a formal relationship or is it more of pass shoot score together in the industry? >> Yeah. No, I think it is kind of the multi-level one. You come in knowing people. You've worked together before and you like working with each other and then it sort of naturally extends onto saying, "Hey, what can we do together?" And also how do we start building this ecosystem around us with Docker? They've done an excellent job of articulating why WebAssembly is a complimentary technology with Containers. Which is something I believe very wholeheartedly. You need all three of the heavyweight, middleweight, lightweight. You can't do all the with just one, and to have someone like that sort of with a voice profoundly be able to express, look we're going to start integrating it to show you how it works this way and prevent this sort of like needless drama where people are going, oh Dockers dead, now everything's WebAssembly, and that's been a great.. >> This fight that's been going on. I mean, Docker, Kubernetes, WebAssembly, Containers. >> Yeah. >> We've seen on the show and we both know this hybrid is the future. We're all going to be using a variety of different tools to achieve our goals and I think that you are obviously one of them. I'm curious because just as we were going on you mentioned that you have a PhD in philosophy. (Matt chuckles) >> Matt: Yeah. >> Which is a wild card. You're actually our second PhD in philosophy working in a very technical role on the show this week, which is kind of cool. So, how does that translate into the culture at Fermyon? What's it like on the team? >> Well, you know, a philosophy degree if nothing else teaches you to think in systems and both human systems and formal systems. So that helps and when you approach the process of building a company, you need to be thinking both in terms of how are we organizing this? How are we organizing the product? How do we organize the team? We have really learned that culture is a major deal and culture philosophy, >> Savannah: Why I'm bringing it up. >> We like that, you know, we've been very forward. We have our chip values, curiosity, humility inclusivity and passion, and those are kind of the four things that we feel like that each of us every day should strive to be exhibiting these kinds of things. Curiosity, because you can't push the envelope if you don't ask the hard questions. Humility, because you know, it's easy to get cocky and talk about things as if you knew all the answers. We know we don't and that means we can learn from Docker and Microsoft >> Savannah: That's why you're curious. >> And the person who stops by the booth that we've never met before and says, "hey" and inclusivity, of course, building a community if you don't execute on that well you can't build a good community. The diversity of the community is what makes it stronger than a singular.. >> You have to come in and be cohesive with the community. >> Matt: Yeah. >> The app focus is a really, I think, relevant right now. The timing of this is right online. I think Scott had a good answer I thought on the relationship and how he sees it. I think it's going to be a nice extension to not a extension that way, but like. >> It probably will be as well. >> Almost a pun there John, almost a pun. >> There actually might be an extension, but evolution what we're going to get to which I think is going to be pure application server, like. >> Yep, yep. Like performance for new class of developer. Then now the question comes up and we've been watching developer productivity. That is a big theme and our belief is that if you take digital transformation to its conclusion IT and developers aren't a department serving the business they are the business. That means the developer workflows will have to be radically rebuilt to handle the velocity and new tech for just coding. I call it architectural list. >> I like that. I might steal that. >> It's a pun, but it's also brings up the provocative question. You shouldn't have to need an architecture to code. I mean, Java was great for that reason in many ways. So, if that happens if the developers are running the business that means more apps. The apps is the business. You got to have tool chains and productivity. You can't have fragmentation. Some people are saying WebAssembly might, fork tool chains, might challenge the developer productivity. what's your answer to that? How would you address that objection? >> I mean the threat of forking is always lurking in the corner in open source. In a way it's probably a positive threat because it keeps us honest it keeps us wanting to be inclusive again and keep people involved. Honestly though, I'm not particularly worried about it. I know that the W-3 as a standards body, of course, one of the most respected standards bodies on the planet. They do html, they do cascading style sheets. WebAssembly is in that camp and those of us in the core are really very interested in saying, you know, come on in, let's build something that's going to be where the core is solid and you know what you got and then you can go into the resurgence of the application server. I mean, I wholeheartedly agree with you on that, and we can only get there if we say, all right, here are the common paradigms that we're all going to agree to use, now let's go build stuff. >> And as we've been saying, developers are setting, I think are going to set the standards and they're going to vote with their code and their feet, if you will. >> Savannah: A hundred percent. >> They will decide if you're not aligning with what they want to do. okay. On how they want to self-serve and or work, you'll figure that out. >> Yep, yep. >> You'll get instant feedback. >> Yeah. >> Well, you know, again, I tell you a huge fan of Docker. One of the things that Docker understood at the very outset, is that they had an infrastructure tool and developers were the way to get adoption, and if you look at how fast they got adoption versus many, many other technologies that are profoundly impacted. >> Savannah: Wild. >> Yeah. >> Savannah: It's a cool story. >> It's because they got the developers to go, "This is amazing, hey infrastructure folks, here's an infrastructure tool that we like" and the infrastructure folks are used to code being tossed over the wall are going, "Are you for real?" I mean, and that was a brilliant way to do it and I think that what.. >> John: Yeah, yeah. >> We want to replay in the WebAssembly world is making it developer friendly and you know the kind of infrastructure that we can actually operate. >> Well congratulations to the entire community. We're huge fans of the concept. I kind of see where it's going with connect the dots. You guys getting a lot of buzz. I have to ask you, my final question is the hype is beyond all recognition at this point. People are super pumped and enthusiastic about it and people are looking at it maybe some challenging it, but that's all good things. How do you get to the next level where people are confident that this is actually going to go the next step? Hype to confidence. We've seen great hype. Envoy was hyped up big time before it came in, then it became great. That was one of my favorite examples. Hype is okay, but now you got to put some meat on the bone. The sizzle on the stake so to speak. So what's going to be the stake for you guys as you see this going forward? What's the need? >> Yeah, you know, I talk about our first guiding story was, you know, blinking cursor to deployed application in two minutes. That's what you need to win developers initially. So, what's the next story after that? It's got to be, Fermyon can run real world applications that solve real world problems. That's where hype often fails. If you can build something that's neat but nobody's quite sure what to do with it, to use it, maybe somebody will discover a good use. But, if you take that gambling asset, >> Savannah: It's that ending answer that makes the difference. >> Yeah, yeah. So we say, all right, what are developers trying to build with our platform and then relentlessly focus on making that easier and solving the real world problem that way. That's the crucial thing that's going to drive us out of that sort of early hype stage into a well adopted technology and I talk from Fermyon point of view but really that's for all of us in the WebAssembly. >> John: Absolutely. >> Very well stated Matt, just to wrap us up when we're interviewing you here on theCUBE next year, what do you hope to be able to say then that you can't say today? >> All this stuff about coffee we didn't cover today, but also.. (all chuckles) >> Savannah: Here for the coffee show. Only analogies, that's a great analogy. >> I want to walk here and say, you know last time we talked about being able to achieve density in servers that was, you know, 10 times Kubernetes. Next year I want to say no, we're actually thousands of times beyond Kubernetes that we're lowering people's electricity bill by making these servers more efficient and the developers love it. >> That your commitment to the environment is something I want to do an entirely different show on. We learned that 7-8% of all the world's powers actually used on data centers through the show this week which is jarring quite frankly. >> Yeah, yeah. Tragic would be a better way of saying that. >> Yeah, I'm holding back so that we don't go over time here quite frankly. But anyways, Matt Butcher thank you so much for being here with us. >> Thank you so much for having me it was pleasure.. >> You are worth the hype you are getting. I am grateful to have you as our WebAssembly thought leader. In addition to Scott today from Docker earlier in the show. John Furrier, thanks for being my co-host and thank all of you for tuning into theCUBE here, live from Detroit. I'm Savannah Peterson and we'll be back with more soon. (ambient music)

(energizing music) >> Welcome back, everyone to the Cube and Druva special presentation of why ransomware isn't your only problem. I'm John Furrier, host of The Cube. We're here with W. Curtis Preston, Curtis Preston as he is known in the industry, Chief Technical Cult Evangelist at Druva. Curtis, great to see you. We're here at why ransomware isn't your only problem. Great to see you. Thanks for coming on. >> Happy to be here. >> So we always see each other events now. Events are back, so it's great to have you here for this special presentation. The white paper from IDC really talks about this in detail. I can get your thoughts, and I'd like you to reflect on the analysis that we've been covering here and the survey data, how it lines up with the real world that you're seeing out there. >> Yeah, I think it's the survey results really, I'd like to say that they surprised me, but unfortunately they didn't. The data protection world has been this way or a while where there's this difference in belief or difference between the belief and the reality. And what we see is that there are a number of organizations that have been successfully hit by ransomware, paid the ransom and or lost data. And yet the same people that were surveyed, they had the high degrees of confidence in their backup system and you know, I could probably go on for an hour as to the various reasons why that would be the case, but I think that this long running problem that as long as I've been associated with backups, which, you know has been a while, it's that problem of, you know nobody wants to be the backup person. And people often just, they don't want to have anything to do with the backup system. And so it sort of exists in this vacuum. And so then management is like, oh the backup system's great, because the backup person often, you know, might say that it's great because maybe it's their job to say so. But the reality has always been very, very different. >> It's funny, you know, we're good boss, we got this covered. >> Good, it's all good, it's all good. >> Yeah, the fingers crossed, right? So again, this is the reality and as it becomes backup and recovery, which we've talked about many times on The Cube, certainly we have with you before, but now with ransomware also, the other thing is people get ransomware hit multiple times. So it's not only like to get hit once. So you know, this is a constant chasing the tail on some ends, but there are some tools out there that you guys have a solution. And so let's get into that. You know, you have had hands on backup experience. What are the points that surprise you the most about what's going on in this world and the realities of how people should be going forward? What's your take? >> Well, I would say that the one part in the survey that surprised me the most was people that had a huge, you know, that there was a huge percentage of people that said that they had a you know, a ransomware response, you know in readiness program. And you look at that and how could you be, that higher percentage of people be comfortable with their ransomware readiness program and you know which includes a number of things, right? There's the cyber attack aspect of responding to a ransomware attack, and then there's the recovery aspect. And so you believe that your company was ready for that, and then you go, and I think it was 67% of the people in the survey paid the ransom, which as as a person who, you know, has spent my entire career trying to help people successfully recover their data that number I think just hurt me the most is that, because you talked about reinfections. The surest way to guarantee that you get re-attacked and reinfected, is to pay the ransom. This goes back all the way, ransom since the beginning of time, right? Everyone knows if you pay the blackmail all you're telling people is that you pay blackmail. >> And you're in business, you're a good customer. ARR, (indistinct) >> Yeah, exactly. So the fact that, you know 60 what, two thirds, of the people that were attacked by ransomware paid the ransom, that one statistic just hurt my heart. >> Yeah, and I think this is the reality. I mean, we go back and even the psychology of the practitioners was, you know, it's super important to get back in recovery, and that's been around for a long time, but now that's an attack vector, okay? And there's dollars involved, like I said the ARR, I'm joking, but there's recurring revenue for the bad guys if they know you're paying up and if you're stupid enough not to change, you're tooling, right? So again, it works both ways. So I got to ask you, why do you think so many owners are unable to successfully respond after an attack? Is it because, they know it's coming, I mean, they're not that dumb. I mean, they have to know it's coming. Why aren't they responding successfully to this? >> I think it's a litany of things starting with the aspect that I mentioned before that nobody wants to have anything to do with the backup system, right? So nobody wants to be the one to raise their hand because if you're the one that raises their hand you know what, that's a good idea, Curtis why don't you look into that? Right, nobody wants to be-- >> Where's that guy now? He doesn't work here anymore. Yeah, but I hear where you come from. >> Exactly. >> Psychology. >> Yeah, so there's that. But then the second is that because of that no one's looking at the fact that backups are the attack vector, they become the attack vector. And so because they're the attack vector they have to be protected as much if not more than the rest of the environment. The rest of the environment can live off of active directory and you know, things like Okta so that you can have SSO and things like that. The backup environment has to be segregated in a very special way. Backups have to be stored completely separate from your environment. The login and authentication and authorization system needs to be completely separate from your typical environment, why? Because if that production environment is compromised now knowing that the attacks or that the backup systems are a significant portion of the attack vector, then if the production system is compromised then the backup system is compromised. So you've got to segregate all of that. And I just don't think that people are thinking about that. You know and they're using the same backup techniques that they've used for many, many years. >> So what you're saying is that the attack vectors and the attackers are getting smarter. They're saying, hey, we'll just take out the backup first so they can't backup, so we got the ransomware. It makes sense. >> Yeah, exactly. The largest ransomware group out there the Conti Ransomware Group, they are specifically targeting specific backup vendors. They know how to recognize the backup servers. They know how to recognize where the backups are stored and they are exfiltrating the backups first and then deleting them, and then letting you know you have ransom. >> Okay, so you guys have a lot of customers. They all kind of have the same problem. What's the patterns that you're seeing? How are they evolving? What are some of the things that they're implementing? What is the best practice? >> Well again, you've got to fully segregate that data. There are, and everything about how that data is stored and everything about how that data's created and accessed, there are ways to do that with other, you know with other commercial products. You can take a standard product and put a number of layers of defense on top of it or you can switch to the way Druva does things which is a SAS offering that stores your data completely in the cloud in our account, right? So your account could be completely compromised. That has nothing to do with our account. And the, it's a completely different authentication and authorization system. You've got multiple layers of defense between your computing environment and where we store your backups. So basically what you get by default with the way Druva stores your backups is the best you can get after doing many, many layers of defense on the other side and having to do all that work. With us, you just log in and you get all of that. >> I guess, how do you break the laws of physics? I guess that's the question here. >> Well, that's the other thing, is that by storing the data in the cloud, we do and I've said this a few times, that you get to break the laws of physics. And the only way to do that is time travel. And that's what... (chuckles) so yeah, so Druva has time travel. This isn't a criticism, by the way. I don't think this is our official position, but the idea is that the only way to restore data as fast as possible is to restore it before you actually need it. And that's what kind of, what I mean by time travel in that you basically, you configure your DR, your disaster recovery environment in Druva one time, and then we are pre restoring your data as often as you tell us to do to bring your DR environment up to the current environment as quickly as we can. So that in a disaster recovery scenario which is part of your ransomware response, right? Again, there are many different parts but when you get to actually restoring the data you should be able to just push a button and go. The data should already be restored. And that's the way that you break the laws of physics, is you break the laws of time. >> Well, everyone wants to know the next question, and this is the real big question is, are you from the future? >> Yeah. Very much the future. >> What's it like in the future? Back at recovery as a restorer, air gaping everything? >> Yeah. It, well it's a world where people don't have to worry about their backups. I like to use the phrase, get out of the backup business. Just get into the restore business. You know, I'm a grandfather now, and I love having a granddaughter and I often make the joke that if I've known how great grandkids were I would've skipped straight to them, right? Not possible. Just like this. Recoveries are great. Backups are really hard. So in the future, if you use a SAS data protection system and data resiliency system, you can just do recoveries and not have to worry about backups. >> Yeah. And what's great about your background is you've got a lot of historical perspective. I've seen that in the ways of innovation. Now it really is about the recovery and real time. So a lot of good stuff going on and got things automated things got to be rocking and rolling. >> Absolutely. Yeah, I do remember again, having worked so hard with many clients over the years, back then we worked so hard just to get the backup done. There was very little time to work on the recovery. And I really, I kid you not that our customers don't have to do all of those things that all of our competitors have to do to you know, to try to break the laws of physics. I've been fighting the laws of physics my entire career to get the backup done in the first place. Then to secure all the data, right, to air gap it and make sure that a ransomware attack isn't going to attack it. Our customers get to get straight to a fully automated disaster recovery environment that they get to test as often as possible and they get to do a full test by simply pressing a single button. And you know, I wish everybody had that ability. >> Yeah, I mean security's a big part of it. Data's in the middle of it. All this is now mainstream, front lines, great stuff. Curtis, great to have you on, bring that perspective, and thanks for the insight. Really appreciate it. >> Always happy to talk about my favorite subject. (bright music)

>> The past 2 1/2 years have seen a dramatic change in the security posture of virtually all organizations. By accelerating the digital business mandate, the isolation economy catalyzed a move toward cloud computing to support remote workers. This we know. This had several ripple effects on CSO and CIO strategies that were highly visible at the Board of Directors' level. Now, the first major change was to recognize that the perimeter had suddenly been vaporized. Protection, as a result, moved away from things like perimeter-based firewalls toward more distributed endpoints, cloud security, and modern identity management. The second major change was a heightened awareness of the realities of ransomware. Ransomware as a service, for example, emerged as a major threat where virtually anyone with access to critical data and criminal intentions could monetize corporate security exposures. The third major change was a much more acute understanding of how data protection needed to become a fundamental component of cybersecurity strategies, and more specifically, CIOs quickly realized that their business resilience strategies were too narrowly DR-focused, that their DR approach was not cost efficient and needed to be modernized, and that new approaches to operational resilience were needed to reflect the architectural and business realities of this new environment. Hello, and welcome to "Why Ransomware isn't Your Only Problem," a service of theCUBE made possible by Druva, and in collaboration with IDC. I'm your host, Dave Vellante, and today, we're presenting a three-part program. We'll start with the data. IDC recently conducted a global survey of 500 business technology practitioners across 20 industries to understand the degree to which organizations are aware of and prepared for the threats they face in today's new world. IDC Research Vice President Phil Goodwin is here to share the highlights of the study and to summarize the findings from a recent research report on the topic. After that, we're going to hear from Curtis Preston, who's the Chief Technical Evangelist at Druva. I've known Curtis for decades. He's one of the world's foremost experts on backup and recovery, specifically, and data protection, generally. Curtis will help us understand how the survey data presented by IDC aligns with the real world findings from the field from his point of view. And he'll discuss why so many organizations have failed to successfully recover from an attack without major pains and big costs, and how to avoid such operational disruptions and disasters. And then finally, we'll hear from the technical experts at Druva, Stephen Manley and Anjan Srinivas. Stephen is a 10-time CUBE alum and Chief Technology Officer at Druva, and Anjan is Vice President and General Manager of Product Management at the company. And these individuals will specifically address how Druva is closing the gaps presented in the IDC survey through their product innovation. But right now I'm going to toss it to Lisa Martin, another one of the hosts for today's program. Lisa, over to you. (upbeat music) >> Bill Goodwin joins me next, the VP of Research at IDC. We're going to be breaking down what's going on in the threat landscape. Phil, welcome to the program. It's great to have you back on theCUBE. >> Hey, Lisa, it's great to be here with you. >> So talk to me about the state of the global IT landscape as we see cyberattacks massively increasing, the threat landscape changing so much. What is IDC seeing? >> You know, you really hit the top topic that we find from IT organizations as well as business organizations. And really, it's that digital resilience, that ransomware that has everybody's attention, and it has the attention, not just of the IT people, but of the business people alike, because it really does have profound effects across the organization. The other thing that we're seeing, Lisa, is really a move towards cloud. And I think part of that is driven by the economics of cloud, which fundamentally changed the way that we can approach disaster recovery, but also has accelerated during the pandemic for all the reasons that people have talked about in terms of work from home and so on. And then really the third thing is the economic uncertainty, and this is relatively new for 2022, but within IDC we've been doing a lot of research around what are those impacts going to be? And what we find people doing is they want greater flexibility, they want more cost certainty, and they really want to be able to leverage those cloud economics to have the scale up or scale down on demand nature of cloud. So those are, in a nutshell, kind of the three things that people are looking at. >> You mentioned ransomware. It's a topic we've been talking about a lot. It's a household word these days. It's now, Phil, no longer if we're going to get attacked, it's when, it's how often, it's the severity. Talk about ransomware as a priority all the way up the stack to the C-suite, and what are they trying to do to become resilient against it? >> Well, what some of the research that we did is we found that about 77% of organizations have digital resilience as a top priority within their organization. And so what you're seeing is organizations trying to leverage things to become more resilient, more digitally resilient, and to be able to really hone in on those kinds of issues that are keeping them awake at night, quite honestly. If you think about digital resilience, it really is foundational to the organization, whether it's through digital transformation or whether it's simply data availability, whatever it might happen to be. Digital resilience is really a large umbrella term that we use to describe that function that is aimed at avoiding data loss, assuring data availability, and helping the organization to extract value from their data. >> And digital resilience, data resilience, as every company these days has to be a data company to be competitive. Digital resilience, data resilience, are you using those terms interchangeably or is data resilience defined as something a little bit different? >> Well, sometimes yeah, we do get caught using them when one is the other. But data resilience is really a part of digital resilience, if you think about the data itself in the context of IT computing. So it really is a subset of that, but it is foundational to IT resilience. You can't have IT resilience without data resilience. So that's where we're coming from on it. >> Inextricably linked, and it's becoming a corporate initiative, but there's some factors that can complicate digital resilience, data resilience for organizations. What are some of those complications that organizations need to be aware of? >> Well, one of the biggest is what you mentioned at the top of the segment, and that is the area of ransomware. The research that we found is about 46% of organizations have been hit within the last three years. You know, it's kind of interesting how it's changed over the years. Originally, being hit by ransomware had a real stigma attached to it. Organizations didn't want to admit it, and they really avoided confronting that. Nowadays, so many people have been hit by it that that stigma has gone. And so really it is becoming more of a community kind of effort as people try to defend against these ransomers. The other thing about it is it's really a lot like Whac-A-Mole, you know. They attack us in one area and we defend against it so they attack us in another area, and we defend against it. And in fact, I had an individual come up to me at a show not long ago and said, "You know, one of these days we're going to get pretty well defended against ransomware and it's going to go away." And I responded I don't think so because we're constantly introducing new systems, new software, and introducing new vulnerabilities. And the fact is ransomware is so profitable, the bad guys aren't going to just fade into the night without giving it a a lot of fight. So I really think that ransomware is one of those things that is here for the long term and something that we have to address and have to get proactive about. >> You mentioned some stats there, and recently IDC and Druva did a white paper together that really revealed some quite shocking results. Talk to me about some of the things. Let's talk a little bit about the demographics of the survey and then talk about what was the biggest finding there, especially where it's concerning ransomware? >> Yeah, this was a worldwide study. It was sponsored by Druva and conducted by IDC as an independent study. And what we did, we surveyed 500, it was a little over 500 different individuals across the globe in North America, select countries in Western Europe, as well as several in Asia Pacific. And we did it across industries there were 20 different industries represented, they're all evenly represented. We had surveys that included IT practitioners, primarily CIOs, CTOs, VP of infrastructure, you know, managers of data centers, things like that. And the biggest finding that we had in this, Lisa, was really finding that there is a huge disconnect, I believe, between how people think they are ready and what the actual results are when they get attacked. Some of the statistics that we learned from this, Lisa, include 83% of organizations believe, or told us that they have a playbook that they have for ransomware. I think 93% said that they have a high degree, or a high or very high degree of confidence in their recovery tools and are fully automated. And yet, when you look at the actual results, you know, I told you a moment ago, 46% have been attacked successfully. I can also tell you that in separate research, fewer than 1/3 of organizations were able to fully recover their data without paying the ransom, and some 2/3 actually had to pay the ransom. And even when they did, they didn't necessarily achieve their full recovery. You know, the bad guys aren't necessarily to be trusted, and so the software that they provide sometimes is fully recovered, sometimes it's not. So you look at that and you go, wow. On the one hand, people think they're really, really prepared, and on the other hand, the results are absolutely horrible. You know, 2/3 of people having to pay the ransom. So you start to ask yourself, well, what's going on there? And I believe that a lot of it comes down to, kind of reminds me of the old quote from Mike Tyson. "Everybody has a plan until they get punched in the mouth." And I think that's kind of what happens with ransomware. You think you know what you're doing. You think you're ready, based on the information you have. And these people are smart people, and they're professionals, but oftentimes, you don't know what you don't know. And like I said, the bad guys are always dreaming up new ways to attack us. And so, I think, for that reason, a lot of these have been successful. So that was kind of the key finding to me and kind of the aha moment really in this whole thing, Lisa. >> That's a massive disconnect with the vast majority saying, "We have a cyber recovery playbook," yet nearly 1/2 being the victims of ransomware in the last three years, and then 1/2 of them experiencing data loss. What is it then that organizations in this situation across any industry can do to truly enable cyber resilience, data resilience? As we said, this is a matter of this is going to happen, just a matter of when and how often. >> It is a matter, yeah, as you said, it's not if, when, or how often, it's really how badly. So I think what organizations are really doing now is starting to turn more to cloud-based services, you know, finding professionals who know what they're doing, who have that breadth of experience and who have seen the kinds of necessary steps that it takes to do a recovery. And the fact of the matter is a disaster recovery and a cyber recovery are really not the same thing. And so organizations need to be able to plan the kinds of recovery associated with cyber recovery in terms of forensics, in terms of scanning, in terms of analysis, and so forth. So they're turning to professionals in the cloud much more, in order to get that breadth of experience, and to take advantage of cloud-based services that are out there. >> Talk to me about some of the key advantages of cloud-based services for data resilience versus traditional legacy on-prem equipment. What are some of the advantages? Why is IDC seeing this big shift to cloud where data resilience is concerned? >> Well, the first and foremost is the economics of it. You know, you can have on-demand resources. In the old days, when we had disaster recoveries where we had two different data centers and a failover and so forth, you know, you had double the infrastructure. If you're financial services, it might even be triple the infrastructure. It was very complicated, very difficult. By going to the cloud, organizations can subscribe to disaster recovery as a service. And increasingly what we see is a new market of cyber recovery as a service. So being able to leverage those resources, to be able to have the forensic analysis available to them, to be able to have the other resources available that are on demand, and to have that plan in place to have those resources in place. I think what happens in a number of situations, Lisa, is that organizations think they're ready, but then all of a sudden they get hit, and all of a sudden they have to engage with outside consultants, or they have to bring in other experts, and that extends the time to recover that they have and it also complicates it. So if they have those resources in place, then they can simply turn them on, engage them, and get that recovery going as quickly as possible. >> So what do you think the big issue here is? Is it that these IPT practitioners, over 500 that you surveyed across 20 industries, this a global survey, do they they not know what they don't know? What's the overlying issue here? >> Yeah, I think that's right. You don't know what you don't know, and until you get into a specific attack, you know, there are so many different ways that organizations can be attacked. And, in fact, from this research that we found is that, in many cases, data exfiltration exceeds data corruption by about 50%. But when you think about that, the issue is, once I have your data, what are you going to do? I mean, there's no amount of recovery that is going to help. So organizations are either faced with paying the ransom to keep the data from perhaps being used on the dark web, or whatever, or simply saying no, and taking their chances. So best practice things like encryption, immutability, things like that that organizations can put into place. Certainly air gaps, having a solid backup foundation to where data is, you have a high recovery, high probability of recovery, things like that. Those are the kinds of things that organizations have to put into place, really as a baseline to assure that they can recover as fast as possible and not lose data in the event of a ransomware attack. >> Given some of the disconnect that you articulated, the stats that show so many think we are prepared, we've got a playbook, yet so many are being attacked, the vulnerabilities as the landscape, threat landscape, just gets more and more amorphous. What do you recommend organizations do? You talked to the IT practitioners, but does this go all the way up to the board level in terms of, hey guys, across every industry, we are vulnerable, this is going to happen. We've got to make sure that we are truly resilient and proactive? >> Yes, and in fact, what we found from this research is in more than 1/2 of cases, the CEO is directly involved in the recovery. So this is very much a C-suite issue. And if you look at the consequences of ransomware, it's not just the ransom, it's the lost productivity, it's the loss of revenue. It's the loss of customer faith and goodwill, and organizations that have been attacked have suffered those consequences, and many of them are permanent. So people at the board level, whether it's the CEO, the CFO, the CIO, the CSO, you know, whoever it is, they're extremely concerned about these. And I can tell you, they are fully engaged in addressing those issues within their organization. >> So all the way at the top, and critically important, business critical for any industry. I imagine some industries may be a little bit more vulnerable than others, financial services, healthcare, education. We've just seen a big attack in Los Angeles County. But in terms of establishing data resilience, you mentioned ransomware isn't going anywhere, it's a big business, it's very profitable. But what is IDC's prediction where ransomware is concerned? Do you think that organizations, if they truly adopt cloud and SaaS-based technologies, can they get to a place where the C-suite doesn't have to be involved to the point where they really actually have a functioning playbook? >> I don't know if we'll ever get to the point where the C-suite is not involved. It's probably very important to have that level of executive sponsorship. But what we are seeing is, in fact, we predict that by 2025, 55% of organizations will have shifted to a cloud-centric strategy for their data resilience. And the reason we say that is, you know, workloads on premises aren't going away. So that's the core. We have an increasing number of workloads in the cloud and at the edge, and that's really where the growth is. So being able to take that cloud-centric model and take advantage of cloud resources like immutable storage, being able to move data from region to region inexpensively and easily, and to be able to take that cloud-centric perspective and apply it on premises as well as in the cloud and at the edge is really where we believe that organizations are shifting their focus. >> Got it, we're just cracking the surface here, Phil. I wish we had more time, but I had a chance to read the Druva-sponsored IDC white paper. Fascinating finds. I encourage all of you to download that, take a read. You're going to learn some very interesting statistics and recommendations for how you can really truly deploy data resilience in your organization. Phil, it's been a pleasure to have you on the program. Thank you for joining me. >> No problem. Thank you, Lisa. >> In a moment, John Furrier will be here with his next guest. For right now, I'm Lisa Martin, and you are watching theCUBE, the leader in live tech coverage. >> We live in a world of infinite data. Sprawling, dispersed, valuable, but also vulnerable. So how do organizations achieve data resiliency when faced with ever expanding workloads, increasing security threats, and intensified regulations? Unfortunately, the answer often boils down to what flavor of complexity do you like best? The common patchwork approaches are expensive, convoluted, and difficult to manage. There's multiple software and hardware vendors to worry about, different deployments for workloads running on-premises or in the cloud. And an inconsistent security framework resulting in enterprises maintaining four to five copies of the same data, increasing costs and risk, building to an incoherent mess of complications. Now, imagine a world free from these complexities. Welcome to the the Druva Data Resiliency Cloud, where full data protection and beautiful simplicity converge. No hardware, no upgrades, no management, just total data resilience. With just a few clicks, you can get started integrating all of your data resiliency workflows in minutes. Through a true cloud experience built on Amazon Web Services, the Druva platform automates and manages critical daily tasks, giving you time to focus on your business. In other words, get simplicity, scalability, and security instantly. With the Druva Data Resiliency Cloud, your data isn't just backed up, it's ready to be used 24/7 to meet compliance needs and to extract critical insights. You can archive data for long-term retention, be protected against device failure and natural disasters, and recover from ransomware lightning fast. Druva is trusted with billions of backups annually by thousands of enterprises, including more than 60 of the Fortune 500, costing up to 50% less than the convoluted hardware, software, and appliance solutions. As data grows and becomes more critical to your business advantage, a data resiliency plan is vital, but it shouldn't be complicated. Druva makes it simple. (upbeat music) (mouse clicks) >> Welcome back, everyone, to theCUBE and the Druva special presentation of "Why Ransomware isn't Your Only Problem." I'm John Furrier, host of theCUBE. We're here with W Curtis Preston, Curtis Preston, as he's known in the industry, Chief Technical Evangelist at Druva. Curtis, great to see you. We're here at "Why Ransomware isn't Your Only Problem." Great to see you, thanks for coming on. >> Happy to be here. >> So we always see each other at events now events are back. So it's great to have you here for this special presentation. The white paper from IDC really talks about this in detail. I'd like to get your thoughts, and I'd like you to reflect on the analysis that we've been covering here in this survey data, how it lines up with the real world that you're seeing out there. >> Yeah, I think it's, the survey results really, I'd like to say, I'd like to say that they surprised me, but unfortunately, they didn't. The data protection world has been this way for a while where there's this difference in belief, or difference between the belief and the reality. And what we see is that there are a number of organizations that have been hit, successfully hit by ransomware, paid the ransom and/or lost data, and yet the same people that were surveyed, they had high degrees of confidence in their backup system. And, you know, I could probably go on for an hour as to the various reasons why that would be the case, but I think that this long running problem that as long as I've been associated with backups, which, you know, has been a while, it's that problem of, you know, nobody wants to be the backup person. And people often just, they don't want to have anything to do with the backup system, and so it sort of exists in this vacuum. And so then management is like, "Oh, the backup system's great," because the backup person often, you know, might say that it's great because maybe it's their job to say so. But the reality has always been very, very different. >> It's funny, you know. "We're good, boss, we got this covered." >> Yeah, it's all good, it's all good. >> And the fingers crossed, right? So again, this is the reality, and as it becomes backup and recovery, which we've talked about many times on theCUBE, certainly we have with you before, but now with ransomware, also, the other thing is people get ransomware hit multiple times. So it's not only like they get hit once, so, you know, this is a constant chasing the tail on some ends, but there are some tools out there, You guys have a solution, and so let's get into that. You know, you have had hands-on backup experience. What are the points that surprise you the most about what's going on in this world and the realities of how people should be going forward? What's your take? >> Well, I would say that the one part in the survey that surprised me the most was people that had a huge, you know, there was a huge percentage of people that said that they had, you know, a ransomware response, you know, and readiness program. And you look at that, and how could you be, you know, that high a percentage of people be comfortable with their ransomware readiness program, which includes a number of things, right? There's the cyberattack aspect of responding to a ransomware attack, and then there's the recovery aspect. And so you believe that your company was ready for that, and then you go, and I think it was 67% of the people in the survey paid the ransom, which as a person who, you know, has spent my entire career trying to help people successfully recover their data, that number, I think, just hurt me the most is that because, you talked about re-infections. The surest way to guarantee that you get re-attacked and reinfected is to pay the ransom. This goes back all the way to ransom since the beginning of time, right? Everyone knows if you pay the blackmail, all you're telling people is that you pay blackmail. >> You're in business, you're a good customer >> Yeah, yeah, exactly. >> for ransomware. >> Yeah, so the fact that, you know, 60, what, 2/3 of the people that were attacked by ransomware paid the ransom. That one statistic just hurt my heart. >> Yeah, and I think this is the reality. I mean, we go back, and even the psychology of the practitioners was, you know, it's super important to get backup and recovery, and that's been around for a long time, but now that's an attack vector, okay? And there's dollars involved, like I said, I'm joking, but there's recurring revenue for the bad guys if they know you're paying up and if you're stupid enough not to change your tooling. So again, it works both ways. So I got to ask you, why do you think so many owners are unable to successfully respond after an attack? Is it because, they know it's coming, I mean, they're not that dumb. I mean, they have to know it's coming. Why aren't they responding successfully to this? >> I think it's a litany of things, starting with that aspect that I mentioned before, that nobody wants to have anything to do with the backup system, right? So nobody wants to be the one to raise their hand because if you're the one that raises their hand, "You know, that's a good idea, Curtis, why don't you look into that?" Nobody wants to be- >> Where's that guy now? He doesn't work here anymore. Yeah, I hear where you coming from. >> Exactly. >> It's psychology (indistinct) >> Yeah, so there's that. But then the second is that because of that, no one's looking at the fact that backups are the attack vector. They become the attack vector. And so because they're the attack vector, they have to be protected as much, if not more than the rest of the environment. The rest of the environment can live off of Active Directory and, you know, and things like Okta, so that you can have SSO and things like that. The backup environment has to be segregated in a very special way. Backups have to be stored completely separate from your environment. The login and authentication and authorization system needs to be completely separate from your typical environment. Why? Because if that production environment is compromised, now knowing that the attacks or that the backup systems are a significant portion of the attack vector, then if the production system is compromised, then the backup system is compromised. So you've got to segregate all of that. And I just don't think that people are thinking about that. You know, and they're using the same backup techniques that they've used for many, many years. >> So what you're saying is that the attack vectors and the attackers are getting smarter. They're saying, "Hey, we'll just take out the backup first so they can't backup. So we got the ransomware." It makes sense. >> Yeah, exactly. The largest ransomware group out there, the Conti ransomware group, they are specifically targeting specific backup vendors. They know how to recognize the backup servers. They know how to recognize where the backups are stored, and they are exfiltrating the backups first, and then deleting them, and then letting you know you have ransom. >> Okay, so you guys have a lot of customers. They all kind of have the same problem. What's the patterns that you're seeing? How are they evolving? What are some of the things that they're implementing? What is the best practice? >> Well, again, you've got to fully segregate that data, and everything about how that data is stored and everything about how that data's created and accessed, there are ways to do that with other, you know, with other commercial products. You can take a standard product and put a number of layers of defense on top of it, or you can switch to the way Druva does things, which is a SaaS offering that stores your data completely in the cloud in our account, right? So your account could be completely compromised. That has nothing to do with our account. It's a completely different authentication and authorization system. You've got multiple layers of defense between your computing environment and where we store your backups. So basically, what you get by default with the way Druva stores your backups is the best you can get after doing many, many layers of defense on the other side and having to do all that work. With us, you just log in and you get all of that. >> I guess, how do you break the laws of physics? I guess that's the question here. >> Well, because that's the other thing is that by storing the data in the cloud, and I've said this a few times, you get to break the laws of physics, and the only way to do that is time travel. (both laughing) So yes, so Druva has time travel. And this is a Curtisism, by the way, I don't think this is our official position, but the idea is that the only way to restore data as fast as possible is to restore it before you actually need it, and that's kind of what I mean by time travel, in that you, basically, you configure your DR, your disaster recovery environment in Druva one time, and then we are pre-restoring your data as often as you tell us to do, to bring your DR environment up to the, you know, the current environment as quickly as we can so that in a disaster recovery scenario, which is part of your ransomware response, right? Again, there are many different parts, but when you get to actually restoring the data, you should be able to just push a button and go. The data should already be restored. And that's the way that you break the laws of physics is you break the laws of time. >> (laughs) Well, all right, everyone wants to know the next question, and this is a real big question is, are you from the future? >> (laughs) Yeah. Very much the future. >> What's it like in the future, backup, recovery? How does it restore? Is it air gapping everything? >> Yeah, well, it's a world where people don't have to worry about their backups. I like to use the phrase get out of the backup business, just get into the restore business. You know, I'm a grandfather now, and I love having a granddaughter, and I often make the joke that if I'd have known how great grandkids were, I would've skipped straight to them, right? Not possible. Just like this. Recoveries are great. Backups are really hard. So in the future, if you use a SaaS data protection system and data resiliency system, you can just do recoveries and not have to worry about backups. >> Yeah, and what's great about your background is you've got a lot of historical perspective. You've seen that, the waves of innovation. Now it really is about the recovery and real time. So a lot of good stuff going on. And got to think automated, things got to be rocking and rolling. >> Absolutely. Yeah. I do remember, again, having worked so hard with many clients over the years, back then, we worked so hard just to get the backup done. There was very little time to work on the recovery. And I really, I kid you not, that our customers don't have to do all of those things that all of our competitors have to do to, you know, to break, to try to break the laws of physics, I've been fighting the laws of physics my entire career, to get the backup done in the first place, then to secure all the data, and to air gap it and make sure that a ransomware attack isn't going to attack it. Our customers get to get straight to a fully automated disaster recovery environment that they get to test as often as possible and they get to do a full test by simply pressing a single button. And you know, I wish everybody had that ability. >> Yeah, I mean, security's a big part of it. Data's in the middle of it all. This is now mainstream, front lines, great stuff. Curtis, great to have you on, bring that perspective, and thanks for the insight. Really appreciate it. >> Always happy to talk about my favorite subject. >> All right, we'll be back in a moment. We'll have Stephen Manley, the CTO, and Anjan Srinivas, the GM and VP of Product Management will join me. You're watching theCUBE, the leader in high tech enterprise coverage. >> Ransomware is top of mind for everyone. Attacks are becoming more frequent and more sophisticated. It's a problem you can't solve alone anymore. Ransomware is built to exploit weaknesses in your backup solution, destroying data, and your last line of defense. With many vendors, it can take a lot of effort and configuration to ensure your backup environment is secure. Criminals also know that it's easy to fall behind on best practices like vulnerability scans, patches, and updates. In fact, 42% of vulnerabilities are exploited after a patch has been released. After an attack, recovery can be a long and manual process that still may not restore clean or complete data. The good news is that you can keep your data safe and recover faster with the Druva Data Resiliency Cloud on your side. The Druva platform functions completely in the cloud with no hardware, software, operating system, or complex configurations, which means there are none of the weaknesses that ransomware commonly uses to attack backups. Our software as a service model delivers 24/7/365 fully managed security operations for your backup environment. We handle all the vulnerability scans, patches, and upgrades for you. Druva also makes zero trust security easy with built-in multifactor authentication, single sign-on, and role-based access controls. In the event of an attack, Druva helps you stop the spread of ransomware and quickly understand what went wrong with built-in access insights and anomaly detection. Then you can use industry first tools and services to automate the recovery of clean, unencrypted data from the entire timeframe of the attack. Cyberattacks are a major threat, but you can make protection and recovery easy with Druva. (electronic music) (upbeat music) (mouse clicks) >> Welcome back, everyone, to theCUBE's special presentation with Druva on "Why Ransomware isn't Your Only Problem." I'm John Furrier, host of theCUBE. Our next guests are Stephen Manley, Chief Technology Officer of Druva, and Anjan Srinivas, who is the General Manager and Vice President of Product Management at Druva. Gentlemen, you got the keys to the kingdom, the technology, ransomware, data resilience. This is the topic. The IDC white paper that you guys put together with IDC really kind of nails it out. I want to get into it right away. Welcome to this segment. I really appreciate it. Thanks for coming on. >> Great to be here, John. >> So what's your thoughts on the survey's conclusion? Obviously, the resilience is huge. Ransomware continues to thunder away at businesses and causes a lot of problems, disruption. I mean, it's endless ransomware problems. What's your thoughts on the conclusion? >> So I'll say the thing that pops out to me is, on the one hand, everybody who sees the survey and reads it is going to say, "Well, that's obvious." Of course, ransomware continues to be a problem. Cyber resilience is an issue that's plaguing everybody. But I think when you dig deeper and there's a lot of subtleties to look into, but one of the things that I hear on a daily basis from the customers is, it's because the problem keeps evolving. It's not as if the threat was a static thing to just be solved and you're done. Because the threat keeps evolving, it remains top of mind for everybody because it's so hard to keep up with what's happening in terms of the attacks. >> And I think the other important thing to note, John, is that people are grappling with this ransomware attack all of a sudden where they were still grappling with a lot of legacy in their own environment. So they were not prepared for the advanced techniques that these ransomware attackers were bringing to market. It's almost like these ransomware attackers had a huge leg up in terms of technology that they had in their favor while keeping the lights on was keeping IT away from all the tooling that they needed to do. A lot of people are even still wondering, when that happens next time, what do I even do? So clearly not very surprising. Clearly, I think it's here to stay, and I think as long as people don't retool for a modern era of data management, this is going to to stay this way. >> Yeah, I hear this all the time in our CUBE conversations with practitioners. It's kind of like the security pro, give me more tools, I'll buy anything that comes in the market, I'm desperate. There's definitely attention, but it doesn't seem like people are satisfied with the tooling that they have. Can you guys share kind of your insights into what's going on in the product side? Because, you know, people claim that they have tools at crime points of recovery opportunities, but they can't get there. So it seems to be that there's a confidence problem here in the market. How do you guys see that? 'cause I think this is where the rubber meets the road with ransomware 'cause it is a moving train, it's always changing, but it doesn't seem there's confidence. Can you guys talk about that? What's your reaction? >> Yeah, let me jump in first, and Stephen can add to it. What happens is, I think this is a panic buying and they have accumulated this tooling now just because somebody said they could solve your problem, but they haven't had a chance to take a real look from a ground up perspective to see where are the bottlenecks? Where are the vulnerabilities? And which tooling set needs to lie where? Where does the logic need to reside? And what, in Druva, we are watching people do and people do it successfully, is that as they have adopted Druva technology, which is ground up built for the cloud, and really built in a way which is, you know, driven at a data insight level where we have people even monitoring our service for anomalies and activities that are suspicious. We know where we need to play a role in really kind of mitigating this ransomware, and then there's a whole plethora of ecosystem players that kind of combine to really finish the story, so to say, right? So I think this has been a panic buying situation. This is like, "Get me any help you can give me." And I think as this settles down and people really understand that longer term as they really build out a true defense mechanism, they need to think really ground up. They will start to really see the value of technologies like Druva, and try to identify the right set of ecosystem to really bring together to solve it meaningfully. >> Yes, Stephen? >> I was going to say, I mean, one of the the really interesting things in the survey for me, and for a moment, a little more than a moment, it made me think was that the large number of respondents who said, "I've got a really efficient, well-run back environment," who, then, on basically the next question said, "And I have no confidence that I can recover from a ransomware attack." And you scratch your head and you think, "Well, if your backup environment is so good, why do you have such low confidence?" And I think that's the moment when we dug deeper and we realized, if you've got a traditional architecture, and let's face it, the disk-based architecture's been around for almost two decades now, in terms of disk-based backup, you can have that tuned to the hilt. That can be running as efficiently as you want it, but it was built before the ransomware attacks, before all these cyber issues, you know, really start hitting companies. And so I have this really well-run traditional backup environment that is not at all built for these modern threat vectors. And so that's really why customers are saying, "I'm doing the best I can," but as Anjan pointed out, the architecture, the tooling isn't there to support what problems I need to solve today. >> Yeah, great point. >> And so, yeah. >> Well, that's a great point. Before we get into the customer side I want to get to in second, you know, I interviewed Jaspreet, the founder and CEO many years ago, even before the pandemic, and you mentioned modern. You guys have always had the cloud with Druva. This is huge. Now that you're past the pandemic, what is that modern cloud edge that you guys have? 'Cause that's a great point. A lot of stuff was built kind of backup and recovery bolted on, not really kind of designed into the current state of the infrastructure and the cloud native application modern environment we're seeing right now. It's a huge issue. >> I think, to me there's three things that come up over and over and over again as we talk to people in terms of, you know, being built in cloud, being cloud native, why is it an advantage? The first one is security and ransomware. And we can go deeper, but the most obvious one that always comes up is every single backup you do with Druva is air gapped, offsite, managed under a separate administrative domain so that you're not retrofitting any sort of air gap network and buying another appliance or setting up your own cloud environment to manage this. Every backup is ransomware protected, guaranteed. The second advantage is the scalability. And you know, this certainly plays into account as your business grows, or, in some cases, as you shrink or repurpose workloads, you're only paying for what you use. But it also plays a big role, again, when you start thinking of ransomware recoveries because we can scale your recovery in cloud, on premises as much or as little as you want. And then I think the third one is we're seeing, basically, things evolving, new workloads, data sprawl, new threat vectors. And one of the nice parts of being a SaaS service in the cloud is we're able to roll out new functionality every two weeks and there's no upgrade cycle, there's no waiting. The customer doesn't have to say, "Wow, I needed six months in the lab before I upgrade it and it's an 18-month, 24-month cycle before the functionality releases. You're getting it every two weeks, and it's backed by Druva to make sure it works. >> Anjan, you know, you got the product side, you know, it's a challenging job 'cause you have so many customers asking for things, probably on the roadmap, you probably can go an hour for that one, but I want to get your thoughts on what you're hearing and seeing from customers. We just reviewed the IDC with Phil. How are you guys responding to your customer's needs? Because it seems that it's highly accelerated, probably on the feature requests, but also structurally as ransomware continues to evolve. What are you hearing? What's the key customer need? How are you guys responding? >> Yeah, actually, I have two things that I hear very clearly when I talk to customers. One, I think, after listening to their security problems and their vulnerability challenges, because we see customers and help customers who are getting challenged by ransomware on a weekly basis. And what I find that this problem is not just a technology problem, it's an operating model problem. So in order to really secure themselves, they need a security operating model and a lot of them haven't figured out that security operating model in totality. Now where we come in, as Druva, is that we are providing them the cloud operating model and a data protection operating model, combined with a data insights operating model which all fit into their overall security operating model that they are really owning and they need to manage and operate, because this is not just about a piece of technology. On top of that, I think our customers are getting challenged by all the same challenges of not just spending time on keeping the lights on, but innovating faster with less. And that has been this age old problem, do more with less. But in this whole, they're like trying to innovate in the middle of the war, so to say. The war is happening, they're getting attacked, but there's also net new shadow IT challenges that's forcing them to make sure that they can manage all the new applications that are getting developed in the cloud. There is thousands of SaaS applications that they're consuming, not knowing which data is critical to their success and which ones to protect and govern and secure. So all of these things are coming at them at 100 miles per hour, while they're just trying to live one day at a time. And unless they really develop this overall security operating model, helped by cloud native technologies like Druva that really providing them a true cloud native model of really giving like a touchless and an invisible protection infrastructure. Not just beyond backups, beyond just the data protection that we all know of into this mindset of kind of being able to look at where each of those functionalities need to lie. That's where I think they're grappling with. Now Druva is clearly helping them with keep up to pace with the public cloud innovations that they need to do and how to protect data. We just launched our EC2 offering to protect EC2 virtual machines back in AWS, and we are going to be continuing to evolve that to further the many services that public cloud software 'cause our customers are really kind of consuming them at breakneck speed. >> So new workloads, new security capabilities. Love that. Good call out there. Stephen, there's still the issue of the disruption side of it. You guys have a guarantee. There's a cost of ownership as you get more tools. Can you talk about that angle of it? You got new workloads, you got the new security needs, what's the disruption impact? 'Cause you want to avoid that. How much is it going to cost you? And you guys have this guarantee, can you explain that? >> Yeah, absolutely. So Druva launched our $10 million data resiliency guarantee. And for us, there were really two key parts to this. The first obviously is $10 million means that, you know, again, we're willing to put our money where our mouth is, and that's a big deal, right? That we're willing to back this with the guarantee. But then the second part, and this is the part that I think reflects that sort of model that Anjan was talking about. We sort of look at this and we say the goal of Druva is to do the job of protecting and securing your data for you so that you, as a customer, don't have to do it anymore. And so the guarantee actually protects you against multiple types of risks, all with SLAs. So everything from your data's going to be recoverable in the case of a ransomware attack. Okay, that's good. Of course, for it to be recoverable, we're also guaranteeing your backup success rate. We're also guaranteeing the availability of the service. We're guaranteeing that the data that we're storing for you can't be compromised or leaked externally, and we're guaranteeing the long-term durability of the data so that if you backup with us today and you need to recover 30 years from now, that data's going to be recovered. So we wanted to really attack the end-to-end risks that affect our customers. Cybersecurity is a big deal, but it is not the only problem out there, and the only way for this to work is to have a service that can provide you SLAs across all of the risks, because that means, as a SaaS vendor, we're doing the job for you so you're buying results as opposed to technology. >> That's great. Great point. Ransomware isn't the only problem. That's the title of this presentation, but it's a big one. (laughs) People are concerned about it, so great stuff. In the last five minutes, guys, if you don't mind, I'd love to have you share what's on the horizon for Druva? You mentioned the new workloads, Anjan. You mentioned this new security. You're going to shift left. DevOps is now the developer model. They're running IT. Get data and security teams now stepping in and trying to be as high velocity as possible for the developers and enterprises. What's on the horizon for Druva? What trends is the company watching, and how are you guys putting that together to stay ahead in the marketplace and the competition? >> Yeah, I think, listening to our customers, what we realize is they need help with the public cloud, number one. I think that's a big wave of consumption. People are consolidating their data centers, moving to the public cloud. They need help in expanding data protection, which becomes the basis of a lot of the security operating model that I talked about. They need that first, from Druva, before they can start to get into much more advanced level of insights and analytics around that data to protect themselves and secure themselves and do interesting things with that data. So we are expanding our coverage on multiple fronts there. The second key thing is to really bring together a very insightful presentation layer, which, I think, is very unique to Druva because only we can look at multiple tenants, multiple customers because we are a SaaS vendor, and look at insights and give them best practices and guidances and analytics that nobody else can give. There's no silo anymore because we are able to take a good big vision view and now help our customers with insights that otherwise that information map is completely missing. So we are able to guide them down a path where they can optimize which workloads need what kind of protection, and then how to secure them. So that is the second level of insights and analytics that we are building. And there's a whole plethora of security offerings that we are going to build, all the way from a feature level where we have things like (audio distorts) that's already available to our customers today to prevent any anomalous behavior and attacks that would delete their backups and then they still have a way to recover from it, but also things to curate and get back to that point in time where it is safe to recover and help them with a sandbox which they can recover confidently knowing it's not going to jeopardize them again and reinfect the whole environment again. So there's a whole bunch of things coming, but the key themes are public cloud, data insights, and security, and that's where my focus is, to go and get those features delivered, and Stephen can add a few more things around services that Stephen is looking to build and launch. >> Sure, so, yeah, so John, I think one of the other areas that we see just an enormous groundswell of interest. So public cloud is important, but there are more and more organizations that are running hundreds, if not thousands of SaaS applications, and a lot of those SaaS applications have data. So there's the obvious things, like Microsoft 365, Google Workspace, but we're also seeing a lot of interest in protecting Salesforce because, if you think about it, if someone you know deletes some really important records in Salesforce, that's actually kind of the record of your business. And so, we're looking at more and more SaaS application protection, and really getting deep in that application awareness. It's not just about backup and recovery when you look at something like a Salesforce, or something like Microsoft 365. You do want to look into sandboxing, you want to look into long-term archival, because this is the new record of the business. What used to be in your on-premises databases, that all lives in cloud and SaaS applications now. So that's a really big area of investment for us. The second one, just to echo what Anjan said is, one of the great things of being a SaaS provider is I have metadata that spans across thousands of customers and tens of billions of backups a year. I'm tracking all sorts of interesting information that is going to enable us to do things like make backups more autonomous so that customers, again, I want to do the job for them. We'll do all the tuning, we'll do all the management for them to be able to better detect ransomware attacks, better respond to ransomware attacks, because we're seeing across the globe. And then, of course, being able to give them more insight into what's happening in their data environment so they can get a better security posture before any attack happens. Because, let's face it, if you can set your data up more cleanly, you're going to be a lot less worried and a lot less exposed when that attack happens. So we want to be able to, again, cover those SaaS applications in addition to the public cloud, and then we want to be able to use our metadata and use our analytics and use this massive pipeline we've got to deliver value to our customers. Not just charts and graphs, but actual services that enable them to focus their attention on other parts of the business. >> That's great stuff. >> And remember, John, I think all this while keeping things really easy to consume, consumer grade UI, APIs, and then really the power of SaaS as a service, simplicity to kind of continue on, amongst kind of keeping these complex technologies together. >> Anjan, that's a great callout. I was going to mention ease of use and self-service. Big part of the developer and IT experience. Expected. It's the table stakes. Love the analytic angle, I think that brings the scale to the table, and faster time to value to get to learn best practices. But at the end of the day, automation, cross-cloud protection and security to protect and recover. This is huge, and this is a big part of not only just protecting against ransomware and other things, but really being fast and being agile. So really appreciate the insights. Thanks for sharing on this segment, really under the hood and really kind of the value of the product. Thanks for coming on, appreciate it. >> Thank you very much. >> Okay, there it is. You have the experts talk about under the hood, the product, the value, the future of what's going on with Druva, and the future of cloud native protecting and recovering. This is what it's all about. It's not just ransomware they have to worry about. In a moment, Dave Vellante will give you some closing thoughts on the subject here. You're watching theCUBE, the leader in high tech enterprise coverage. >> As organizations migrate their business processes to multi-cloud environments, they still face numerous threats and risks of data loss. With a growing number of cloud platforms and fragmented applications, it leads to an increase in data silos, sprawl, and management complexity. As workloads become more diverse, it's challenging to effectively manage data growth, infrastructure, and resource costs across multiple cloud deployments. Using numerous backup vendor solutions for multiple cloud platforms can lead to management complexity. More importantly, the lack of centralized visibility and control can leave you exposed to security vulnerabilities, including ransomware that can cripple your business. The Druva Data Resiliency Cloud is the only 100% SaaS data resiliency platform that provides centralized, secure, air gapped, and immutable backup and recovery. With Druva, your data is safe with multiple layers of protection and is ready for fast recovery from cyberattacks, data corruption, or accidental data loss. Through a simple, easy to manage platform, you can seamlessly protect fragmented, diverse data at scale, across public clouds, and your business critical SaaS applications. Druva is the only 100% SaaS vendor that can manage, govern, and protect data across multiple clouds and business critical SaaS applications. It supports not just backup and recovery, but also data resiliency across high value use cases, such as e-discovery, sensitive data governance, ransomware, and security. No other vendor can match Druva for customer experience, infinite scale, storage optimization, data immutability, and ransomware protection. The Druva Data Resiliency Cloud, your data, always safe, always ready. Visit druva.com today to schedule a free demo. (upbeat music) >> One of the big takeaways from today's program is that in the scramble to keep business flowing over the past 2+ years, a lot of good technology practices have been put into place, but there's much more work to be done, specifically, because the frequency of attacks is on the rise and the severity of lost, stolen, or inaccessible data is so much higher today, business resilience must be designed into architectures and solutions from the start. It cannot be an afterthought. Well, actually it can be, but you won't be happy with the results. Now, part of the answer is finding the right partners, of course, but it also means taking a system's view of your business, understanding the vulnerabilities and deploying solutions that can balance cost efficiency with appropriately high levels of protection, flexibility, and speed slash accuracy of recovery. Here we hope you found today's program useful and informative. Remember, this session is available on demand in both its full format and the individual guest segments. All you got to do is go to thecube.net, and you'll see all the content, or you can go to druva.com. There are tons of resources available, including analyst reports, customer stories. There's this cool TCO calculator. You can find out what pricing looks like and lots more. Thanks for watching "Why Ransomware isn't Your Only Problem," made possible by Druva, in collaboration with IDC and presented by theCUBE, your leader in enterprise and emerging tech coverage. (upbeat music)

(bright inspirational music) >> Welcome back everyone to theCUBE and the Druva special presentation of, "Why Ransomware Isn't Your Only Problem." I'm John Furrier, host of theCUBE. We're here with W. Curtis Preston. Curtis Preston, as you know in the industry, Chief Technical Evangelist at Druva. Curtis, great to see you. We're here at, "Why Ransomware Isn't Your Only Problem." Great to see you. Thanks for coming on. >> Happy to be here. >> So we always see each other events, now events are back. So it's great to have you here for this special presentation. The White Paper from IDC really talks about this in detail. Like to get your thoughts, and I'd like you to reflect on the analysis that we've been covering here and the survey data, how it lines up with the real world that you're seeing out there. >> Yeah, I think it's... The survey results really I'd like to say that they surprised me, but unfortunately they didn't. The data protection world has been this way for a while where there's this difference in belief, or difference between the belief and the reality. And what we see is that there are a number of organizations that have been hit- successfully hit by ransomware, paid the ransom and/or lost data. And yet the same people that were surveyed they had high degrees of confidence in their backup system. And, you know, I could probably go on for an hour as to the various reasons why that would be the case, but I think that this long running problem that as long as I've been associated with backups, which, you know, has been a while, it's that problem of, you know, nobody wants to be the backup person. And people often just they don't want to have anything to do with the backup system. And so it sort of exists in this vacuum. And so then management is like, "Oh, the backup system's great," because the backup person often, you know, might say that it's great because maybe it's their job to say so. But the reality has always been very, very different. >> It's funny, you know, "We're good boss, we got this covered." >> Good. All good. It's all good. >> Fingers crossed, right? So again, this is the reality, and as it becomes backup and recovery, which we've talked about many times on theCUBE, certainly we have with you before, but now with ransomware, also, the other thing is people get ransomware hit multiple times. So it's not only like they get hit once. So, you know, this is a constant chasing the tail on some ends, but there are some tools out there. You guys have a solution. And so let's get into that. You know, you have had hands-on backup experience. What are the points that surprise you the most about what's going on in this world and the realities of how people should be going forward? What's your take? >> Well, I would say that the one part in the survey that surprised me the most was people that had a huge, you know, that there was a huge percentage of people that said that they had a, you know, a ransomware response, you know, and readiness program. And you look at that and how could you be, you know, that high a percentage of people be comfortable with their ransomware readiness program and a, you know, which includes a number of things, right? There's the cyber attack aspect of responding to a ransomware attack, and then there's the recovery aspect. And so you believe that your company was ready for that, and then you go, and I think it was 67% of the people in the survey paid the ransom, which as a person who, you know, has spent my entire career trying to help people successfully recover their data, that number I think just hurt me the most is that because you talked about re-infections the surest way to guarantee that you get re-attacked and reinfected is to pay the ransom. This goes back all the way to ransom since the beginning of time, right? Everyone knows if you pay the blackmail all you're telling people is that you pay blackmail. >> You're in business, you're a good customer. ALR for ransomware. >> Yeah. So, the fact that, you know, 60, what, two-thirds of the people that were attacked by ransomware paid the ransom. That one statistic just, just hurt my heart. >> Yeah. And I think this is the reality. I mean, we go back and even the psychology of the practitioners was, you know, super important to get back in recovery. And that's been around for a long time. But now that's an attack vector, okay? And there's dollars involved, like I said, ALR, I'm joking but there's recurring revenue for the for the bad guys if they know you're paying up and if you're stupid enough not to change you're tooling. Right? So again, it works both ways. So, I got to ask you, why do you think so many organizations are unable to successfully respond after an attack? Is it because- they know it's coming. I mean, they're not that dumb. I mean, they have to know it's coming. Why aren't they responding successfully to this? >> I think it's a litany of things starting with that aspect that I mentioned before that nobody wants to have anything to do with the backup system, right? So, nobody wants to be the one to raise their hand because if you're the one that raises their hand "You know what, that's a good idea, Curtis, why don't you look into that?" Right? Nobody wants to be responsible- >> Where's that guy now? He doesn't work here anymore. Yeah, but I hear where you coming from. Psychology (indistinct). >> Yeah. So there's that. But then the second is that because of that no one's looking at the fact that backups are the attack vector. They become the attack vector. And so because they're the attack vector they have to be protected as much, if not more, than the rest of the environment. The rest of the environment can live off of active directory and, you know, and things like Okta so that you can have SSO and things like that. The backup environment has to be segregated in a very special way. Backups have to be stored completely separate from your environment. The login and authentication and authorization system needs to be completely separate from your typical environment. Why? Because if you, if that production environment is compromised now knowing that the attacks or that the backup systems are a significant portion of the attack vector, if the production system is compromised then the backup system is compromised. So you've got to segregate all of that. And I just don't think that people are thinking about that. You know, and they're using the same backup techniques that they've used for many, many years. >> So what you're saying is that the attack vectors and the attackers are getting smarter. They're saying, "Hey, we'll just take out the backup first so they can't back-up. So we got the ransomware." >> Yeah, exactly. The largest ransomware group out there, the Conti ransomware group, they are specifically targeting specific backup vendors. They know how to recognize the backup servers. They know how to recognize where the backups are stored and they are exfiltrating the backups first and then deleting them and then letting you know you have ransom. Right? >> Okay, so you guys have a lot of customers They all kind of have the same- this problem. What's the patterns that you're seeing? How are they evolving? What are some of the things that they're implementing? What is the best practice? >> Well, again, you've got to fully segregate that data, There are, and everything about how that data is stored and everything about how that data is created and accessed. There are ways to do that with other, you know, with other commercial products. You can take a standard product and put a number of layers of defense on top of it or you can switch to the way Druva does things which is a SaaS offering that stores your data completely in the cloud in our account, right? So your account could be completely compromised. That has nothing to do with our account. And the- it's a completely different authentication and authorization system. You've got multiple layers of defense between your computing environment and where we store your backups. So basically what you get by default with the way Druva stores your backups is the best you can get after doing many, many layers of defense on the other side and having to do all that work with us. You just login and you get all of that. >> I guess how do you break the laws of physics? I guess that's the question here. >> Well, when, because that's the other thing is that by storing the data in the cloud, we do it, and I've said this a few times, that you get to break the laws of physics. And the only way to do that is to, is time travel. And that's what, so yeah. So Druva has time travel. What, and this is a courtisism by the way, I don't think this is our official position, but the idea is that the only way to restore data as fast as possible is to restore it before you actually need it. And that's what kind of what I mean by time travel. In that you, basically, you configure your DR, your disaster recovery environment in Druva one time. And then we are pre-restoring your data as often as you tell us to do, to bring your DR environment up to the, you know, the current environment as quickly as we can so that in a disaster recovery scenario which is part of your ransomware response, right? Again, there are many different parts but when you get to actually restoring the data you should be able to just push a button and go. The data should already be restored. And that's the, that's the way that you of physics is you break the laws of time. >> Well, I and everyone wants to know the next question, and this is the real big question is, are you from the future? (light chuckling) >> Yeah. Very much the future. >> What's it like in the future, back-up recovery, how's it restored? Is it air gapping everything? >> Yeah, it, well, it's a world where people don't have to worry about their backups. I like to use the phrase, "get out of the backup business. Just get into the restore business." I, you know, I'm a grandfather now and I love having a granddaughter and I often make the joke that if I'd have known how great grandkids were I would've skipped straight to them. Right? Not possible. Just like this. Recoveries are great. Backups are really hard. So, in the future, if you use a SaaS data protection system and data resiliency system, you can just do recoveries and not have to worry about backups. >> Yeah. And what's great about your background is you've got a lot of historical perspective. I've seen that in the ways of innovation now it's really is about the recovery and real time. So a lot of good stuff going on and got to think automated. Things got to be rocking and rolling. >> Absolutely. Yeah. I do remember, again, having worked so hard with many clients over the years, back then we worked so hard just to get the backup done. There was very little time to work on the recovery. And I really, I kid you not that our customers don't have to do all of those things that all of our competitors have to do to, you know, to try to break the laws of physics. I've been fighting the laws of physics my entire career to get the backup done in the first place. Then to secure all the data, right? To air gap it and make sure that a ransomware attack isn't going to attack it. Our customers get to get straight to a fully automated disaster recovery environment that they get to test as often as possible and they get to do a full test by simply pressing a single button. And you know, I wish that, I wish everybody had that ability. >> Yeah, I mean, security's a big part of it. Data's in the middle of it. All this is now mainstream front lines. Great stuff. Curtis, great to have you on, bring that perspective and thanks for the insight. Really appreciate it. >> Always happy to talk about my favorite subject. >> Alright. We'll be back in a moment. We'll have Stephen Manley, the CTO, and Anjan Srinivas, the GM and VP of Product Management will join me. You're watching theCUBE, the leader in high tech enterprise coverage. (gentle scientific music)

>>Oracle continues to enhance my sequel Heatwave at a very rapid pace. The company is now in its fourth major release since the original announcement in December 2020. 1 of the main criticisms of my sequel, Heatwave, is that it only runs on O. C I. Oracle Cloud Infrastructure and as a lock in to Oracle's Cloud. Oracle recently announced that heat wave is now going to be available in AWS Cloud and it announced its intent to bring my sequel Heatwave to Azure. So my secret heatwave on AWS is a significant TAM expansion move for Oracle because of the momentum AWS Cloud continues to show. And evidently the Heatwave Engineering team has taken the development effort from O. C I. And is bringing that to A W S with a number of enhancements that we're gonna dig into today is senior vice president. My sequel Heatwave at Oracle is back with me on a cube conversation to discuss the latest heatwave news, and we're eager to hear any benchmarks relative to a W S or any others. Nippon has been leading the Heatwave engineering team for over 10 years and there's over 100 and 85 patents and database technology. Welcome back to the show and good to see you. >>Thank you. Very happy to be back. >>Now for those who might not have kept up with the news, uh, to kick things off, give us an overview of my sequel, Heatwave and its evolution. So far, >>so my sequel, Heat Wave, is a fully managed my secret database service offering from Oracle. Traditionally, my secret has been designed and optimised for transaction processing. So customers of my sequel then they had to run analytics or when they had to run machine learning, they would extract the data out of my sequel into some other database for doing. Unlike processing or machine learning processing my sequel, Heat provides all these capabilities built in to a single database service, which is my sequel. He'd fake So customers of my sequel don't need to move the data out with the same database. They can run transaction processing and predicts mixed workloads, machine learning, all with a very, very good performance in very good price performance. Furthermore, one of the design points of heat wave is is a scale out architecture, so the system continues to scale and performed very well, even when customers have very large late assignments. >>So we've seen some interesting moves by Oracle lately. The collaboration with Azure we've we've covered that pretty extensively. What was the impetus here for bringing my sequel Heatwave onto the AWS cloud? What were the drivers that you considered? >>So one of the observations is that a very large percentage of users of my sequel Heatwave, our AWS users who are migrating of Aurora or so already we see that a good percentage of my secret history of customers are migrating from GWS. However, there are some AWS customers who are still not able to migrate the O. C. I to my secret heat wave. And the reason is because of, um, exorbitant cost, which was charges. So in order to migrate the workload from AWS to go see, I digress. Charges are very high fees which becomes prohibitive for the customer or the second example we have seen is that the latency of practising a database which is outside of AWS is very high. So there's a class of customers who would like to get the benefits of my secret heatwave but were unable to do so and with this support of my secret trip inside of AWS, these customers can now get all the grease of the benefits of my secret he trip without having to pay the high fees or without having to suffer with the poorly agency, which is because of the ws architecture. >>Okay, so you're basically meeting the customer's where they are. So was this a straightforward lifted shift from from Oracle Cloud Infrastructure to AWS? >>No, it is not because one of the design girls we have with my sequel, Heatwave is that we want to provide our customers with the best price performance regardless of the cloud. So when we decided to offer my sequel, he headed west. Um, we have optimised my sequel Heatwave on it as well. So one of the things to point out is that this is a service with the data plane control plane and the console are natively running on AWS. And the benefits of doing so is that now we can optimise my sequel Heatwave for the E. W s architecture. In addition to that, we have also announced a bunch of new capabilities as a part of the service which will also be available to the my secret history of customers and our CI, But we just announced them and we're offering them as a part of my secret history of offering on AWS. >>So I just want to make sure I understand that it's not like you just wrapped your stack in a container and stuck it into a W s to be hosted. You're saying you're actually taking advantage of the capabilities of the AWS cloud natively? And I think you've made some other enhancements as well that you're alluding to. Can you maybe, uh, elucidate on those? Sure. >>So for status, um, we have taken the mind sequel Heatwave code and we have optimised for the It was infrastructure with its computer network. And as a result, customers get very good performance and price performance. Uh, with my secret he trade in AWS. That's one performance. Second thing is, we have designed new interactive counsel for the service, which means that customers can now provision there instances with the council. But in addition, they can also manage their schemas. They can. Then court is directly from the council. Autopilot is integrated. The council we have introduced performance monitoring, so a lot of capabilities which we have introduced as a part of the new counsel. The third thing is that we have added a bunch of new security features, uh, expose some of the security features which were part of the My Secret Enterprise edition as a part of the service, which gives customers now a choice of using these features to build more secure applications. And finally, we have extended my secret autopilot for a number of old gpus cases. In the past, my secret autopilot had a lot of capabilities for Benedict, and now we have augmented my secret autopilot to offer capabilities for elderly people. Includes as well. >>But there was something in your press release called Auto thread. Pooling says it provides higher and sustained throughput. High concerns concerns concurrency by determining Apple number of transactions, which should be executed. Uh, what is that all about? The auto thread pool? It seems pretty interesting. How does it affect performance? Can you help us understand that? >>Yes, and this is one of the capabilities of alluding to which we have added in my secret autopilot for transaction processing. So here is the basic idea. If you have a system where there's a large number of old EP transactions coming into it at a high degrees of concurrency in many of the existing systems of my sequel based systems, it can lead to a state where there are few transactions executing, but a bunch of them can get blocked with or a pilot tried pulling. What we basically do is we do workload aware admission control and what this does is it figures out, what's the right scheduling or all of these algorithms, so that either the transactions are executing or as soon as something frees up, they can start executing, so there's no transaction which is blocked. The advantage to the customer of this capability is twofold. A get significantly better throughput compared to service like Aurora at high levels of concurrency. So at high concurrency, for instance, uh, my secret because of this capability Uh oh, thread pulling offers up to 10 times higher compared to Aurora, that's one first benefit better throughput. The second advantage is that the true part of the system never drops, even at high levels of concurrency, whereas in the case of Aurora, the trooper goes up, but then, at high concurrency is, let's say, starting, uh, level of 500 or something. It depends upon the underlying shit they're using the troopers just dropping where it's with my secret heatwave. The truth will never drops. Now, the ramification for the customer is that if the truth is not gonna drop, the user can start off with a small shape, get the performance and be a show that even the workload increases. They will never get a performance, which is worse than what they're getting with lower levels of concurrency. So this let's leads to customers provisioning a shape which is just right for them. And if they need, they can, uh, go with the largest shape. But they don't like, you know, over pay. So those are the two benefits. Better performance and sustain, uh, regardless of the level of concurrency. >>So how do we quantify that? I know you've got some benchmarks. How can you share comparisons with other cloud databases especially interested in in Amazon's own databases are obviously very popular, and and are you publishing those again and get hub, as you have done in the past? Take us through the benchmarks. >>Sure, So benchmarks are important because that gives customers a sense of what performance to expect and what price performance to expect. So we have run a number of benchmarks. And yes, all these benchmarks are available on guitar for customers to take a look at. So we have performance results on all the three castle workloads, ol DB Analytics and Machine Learning. So let's start with the Rdp for Rdp and primarily because of the auto thread pulling feature. We show that for the IPCC for attended dataset at high levels of concurrency, heatwave offers up to 10 times better throughput and this performance is sustained, whereas in the case of Aurora, the performance really drops. So that's the first thing that, uh, tend to alibi. Sorry, 10 gigabytes. B B C c. I can come and see the performance are the throughput is 10 times better than Aurora for analytics. We have done a comparison of my secret heatwave in AWS and compared with Red Ship Snowflake Googled inquiry, we find that the price performance of my secret heatwave compared to read ship is seven times better. So my sequel, Heat Wave in AWS, provides seven times better price performance than red ship. That's a very, uh, interesting results to us. Which means that customers of Red Shift are really going to take the service seriously because they're gonna get seven times better price performance. And this is all running in a W s so compared. >>Okay, carry on. >>And then I was gonna say, compared to like, Snowflake, uh, in AWS offers 10 times better price performance. And compared to Google, ubiquity offers 12 times better price performance. And this is based on a four terabyte p PCH workload. Results are available on guitar, and then the third category is machine learning and for machine learning, uh, for training, the performance of my secret heatwave is 25 times faster compared to that shit. So all the three workloads we have benchmark's results, and all of these scripts are available on YouTube. >>Okay, so you're comparing, uh, my sequel Heatwave on AWS to Red Shift and snowflake on AWS. And you're comparing my sequel Heatwave on a W s too big query. Obviously running on on Google. Um, you know, one of the things Oracle is done in the past when you get the price performance and I've always tried to call fouls you're, like, double your price for running the oracle database. Uh, not Heatwave, but Oracle Database on a W s. And then you'll show how it's it's so much cheaper on on Oracle will be like Okay, come on. But they're not doing that here. You're basically taking my sequel Heatwave on a W s. I presume you're using the same pricing for whatever you see to whatever else you're using. Storage, um, reserved instances. That's apples to apples on A W s. And you have to obviously do some kind of mapping for for Google, for big query. Can you just verify that for me, >>we are being more than fair on two dimensions. The first thing is, when I'm talking about the price performance for analytics, right for, uh, with my secret heat rape, the cost I'm talking about from my secret heat rape is the cost of running transaction processing, analytics and machine learning. So it's a fully loaded cost for the case of my secret heatwave. There has been I'm talking about red ship when I'm talking about Snowflake. I'm just talking about the cost of these databases for running, and it's only it's not, including the source database, which may be more or some other database, right? So that's the first aspect that far, uh, trip. It's the cost for running all three kinds of workloads, whereas for the competition, it's only for running analytics. The second thing is that for these are those services whether it's like shit or snowflakes, That's right. We're talking about one year, fully paid up front cost, right? So that's what most of the customers would pay for. Many of the customers would pay that they will sign a one year contract and pay all the costs ahead of time because they get a discount. So we're using that price and the case of Snowflake. The costs were using is their standard edition of price, not the Enterprise edition price. So yes, uh, more than in this competitive. >>Yeah, I think that's an important point. I saw an analysis by Marx Tamer on Wiki Bond, where he was doing the TCO comparisons. And I mean, if you have to use two separate databases in two separate licences and you have to do et yelling and all the labour associated with that, that that's that's a big deal and you're not even including that aspect in in your comparison. So that's pretty impressive. To what do you attribute that? You know, given that unlike, oh, ci within the AWS cloud, you don't have as much control over the underlying hardware. >>So look hard, but is one aspect. Okay, so there are three things which give us this advantage. The first thing is, uh, we have designed hateful foreign scale out architecture. So we came up with new algorithms we have come up with, like, uh, one of the design points for heat wave is a massively partitioned architecture, which leads to a very high degree of parallelism. So that's a lot of hype. Each were built, So that's the first part. The second thing is that although we don't have control over the hardware, but the second design point for heat wave is that it is optimised for commodity cloud and the commodity infrastructure so we can have another guys, what to say? The computer we get, how much network bandwidth do we get? How much of, like objects to a brand that we get in here? W s. And we have tuned heat for that. That's the second point And the third thing is my secret autopilot, which provides machine learning based automation. So what it does is that has the users workload is running. It learns from it, it improves, uh, various premieres in the system. So the system keeps getting better as you learn more and more questions. And this is the third thing, uh, as a result of which we get a significant edge over the competition. >>Interesting. I mean, look, any I SV can go on any cloud and take advantage of it. And that's, uh I love it. We live in a new world. How about machine learning workloads? What? What did you see there in terms of performance and benchmarks? >>Right. So machine learning. We offer three capabilities training, which is fully automated, running in France and explanations. So one of the things which many of our customers told us coming from the enterprise is that explanations are very important to them because, uh, customers want to know that. Why did the the system, uh, choose a certain prediction? So we offer explanations for all models which have been derailed by. That's the first thing. Now, one of the interesting things about training is that training is usually the most expensive phase of machine learning. So we have spent a lot of time improving the performance of training. So we have a bunch of techniques which we have developed inside of Oracle to improve the training process. For instance, we have, uh, metal and proxy models, which really give us an advantage. We use adaptive sampling. We have, uh, invented in techniques for paralysing the hyper parameter search. So as a result of a lot of this work, our training is about 25 times faster than that ship them health and all the data is, uh, inside the database. All this processing is being done inside the database, so it's much faster. It is inside the database. And I want to point out that there is no additional charge for the history of customers because we're using the same cluster. You're not working in your service. So all of these machine learning capabilities are being offered at no additional charge inside the database and as a performance, which is significantly faster than that, >>are you taking advantage of or is there any, uh, need not need, but any advantage that you can get if two by exploiting things like gravity. John, we've talked about that a little bit in the past. Or trainee. Um, you just mentioned training so custom silicon that AWS is doing, you're taking advantage of that. Do you need to? Can you give us some insight >>there? So there are two things, right? We're always evaluating What are the choices we have from hybrid perspective? Obviously, for us to leverage is right and like all the things you mention about like we have considered them. But there are two things to consider. One is he is a memory system. So he favours a big is the dominant cost. The processor is a person of the cost, but memory is the dominant cost. So what we have evaluated and found is that the current shape which we are using is going to provide our customers with the best price performance. That's the first thing. The second thing is that there are opportunities at times when we can use a specialised processor for vaccinating the world for a bit. But then it becomes a matter of the cost of the customer. Advantage of our current architecture is on the same hardware. Customers are getting very good performance. Very good, energetic performance in a very good machine learning performance. If you will go with the specialised processor, it may. Actually, it's a machine learning, but then it's an additional cost with the customers we need to pay. So we are very sensitive to the customer's request, which is usually to provide very good performance at a very low cost. And we feel is that the current design we have as providing customers very good performance and very good price performance. >>So part of that is architectural. The memory intensive nature of of heat wave. The other is A W s pricing. If AWS pricing were to flip, it might make more sense for you to take advantage of something like like cranium. Okay, great. Thank you. And welcome back to the benchmarks benchmarks. Sometimes they're artificial right there. A car can go from 0 to 60 in two seconds. But I might not be able to experience that level of performance. Do you? Do you have any real world numbers from customers that have used my sequel Heatwave on A W s. And how they look at performance? >>Yes, absolutely so the my Secret service on the AWS. This has been in Vera for, like, since November, right? So we have a lot of customers who have tried the service. And what actually we have found is that many of these customers, um, planning to migrate from Aurora to my secret heat rape. And what they find is that the performance difference is actually much more pronounced than what I was talking about. Because with Aurora, the performance is actually much poorer compared to uh, like what I've talked about. So in some of these cases, the customers found improvement from 60 times, 240 times, right? So he travels 100 for 240 times faster. It was much less expensive. And the third thing, which is you know, a noteworthy is that customers don't need to change their applications. So if you ask the top three reasons why customers are migrating, it's because of this. No change to the application much faster, and it is cheaper. So in some cases, like Johnny Bites, what they found is that the performance of their applications for the complex storeys was about 60 to 90 times faster. Then we had 60 technologies. What they found is that the performance of heat we have compared to Aurora was 100 and 39 times faster. So, yes, we do have many such examples from real workloads from customers who have tried it. And all across what we find is if it offers better performance, lower cost and a single database such that it is compatible with all existing by sequel based applications and workloads. >>Really impressive. The analysts I talked to, they're all gaga over heatwave, and I can see why. Okay, last question. Maybe maybe two and one. Uh, what's next? In terms of new capabilities that customers are going to be able to leverage and any other clouds that you're thinking about? We talked about that upfront, but >>so in terms of the capabilities you have seen, like they have been, you know, non stop attending to the feedback from the customers in reacting to it. And also, we have been in a wedding like organically. So that's something which is gonna continue. So, yes, you can fully expect that people not dressed and continue to in a way and with respect to the other clouds. Yes, we are planning to support my sequel. He tripped on a show, and this is something that will be announced in the near future. Great. >>All right, Thank you. Really appreciate the the overview. Congratulations on the work. Really exciting news that you're moving my sequel Heatwave into other clouds. It's something that we've been expecting for some time. So it's great to see you guys, uh, making that move, and as always, great to have you on the Cube. >>Thank you for the opportunity. >>All right. And thank you for watching this special cube conversation. I'm Dave Volonte, and we'll see you next time.

(digital music) >> And we're back live in New York. It's theCUBE. It's not SNL, it's better than SNL. Lisa Martin and John Furrier here with about 10,000 to 12,000 folks. (John chuckles) There is a ton of energy here. There's a ton of interest in what's going on. But one of the things that we know that AWS is really well-known for is its massive ecosystem. And one of its ecosystem partners is joining us. Please welcome Domenic Ravita, the VP of Product Marketing from SingleStore. Dominic, great to have you on the program. >> Well, thank you. Glad to be here. >> It's a nice opening, wasn't it? (Lisa and John laughing) >> I love SNL. Who doesn't? >> Right? I know. So some big news came out today. >> Yes. >> Funding. Good number. Talk to us a little bit about that before we dig in to SingleStore and what you guys are doing with AWS. >> Right, yeah. Thank you. We announced this morning our latest round, 116 million. We're really grateful to our customers and our investors and the partners and employees and making SingleStore a success to go on this journey of, really, to fulfill our mission to unify and simplify modern, real time data. >> So talk to us about SingleStore. Give us the value prop, the key differentiators, 'cause obviously customers have choice. Help us understand where you're nailing it. >> SingleStore is all about, what we like to say, the moments that matter. When you have an analytical question about what's happening in the moment, SingleStore is your best way to solve that cost-effectively. So that is for, in the case of Thorn, where they're helping to protect and save children from online trafficking or in the case of True Digital, which early in the pandemic, was a company in Southeast Asia that used anonymized phone pings to identify real time population density changes and movements across Thailand to have a proactive response. So really real time data in the moment can help to save lives quite literally. But also it does things that are just good commercially that gives you an advantage like what we do with Uber to help real time pricing and things like this. >> It's interesting this data intensity happening right now. We were talking earlier on theCUBE with another guest and we said, "Why is it happening now?" The big data has been around since the dupe days. That was hard to work with, then data lakes kicked in. But we seem to be, in the past year, everyone's now aware like, "Wow, I got a lot of data." Is it the pandemic? Now we're seeing customers understand the consequences. So how do you look at that? Because is it just timing, evolution? Are they now getting it or is the technology better? Is machine learning better? What's the forces driving the massive data growth acceleration in terms of implementing and getting stuff out, done? (chuckles) >> We think it's the confluence of a lot of those things you mentioned there. First of all, we just celebrate the 15-year anniversary of the iPhone, so that is like wallpaper now. It's just faded into our daily lives. We don't even think of that as a separate thing. So there's an expectation that we all have instant information and not just for the consumer interactions, for the business interactions. That permeates everything. I think COVID with the pandemic forced everyone, every business to try to move to digital first and so that put pressure on the digital service economy to mature even faster and to be digital first. That is what drives what we call data intensity. And more generally, the economic phenomenon is the data intensive era. It's a continuous competition and game for customers. In every moment in every location, in every dimension, the more data hat you have, the better value prop you can give. And so SingleStore is uniquely positioned to and focused on solving this problem of data intensity by bringing and unifying data together. >> What's the big customer success story? Can you share any examples that highlight that? What are some cool things that are happening that can illustrate this new, I won't say bit that's been flipped, that's been happening for a while, but can you share some cutting edge customer successes? >> It's happening across a lot of industries. So I would say first in financial services, FinTech. FinTech is always at the leading edge of these kind of technology adaptions for speeds and things like that. So we have a customer named IEX Cloud and they're focused on providing real time financial data as an API. So it's a data product, API-first. They're providing a lot of historical information on instruments and that sort of thing, as well as real time trending information. So they have customers like Seeking Alpha, for instance, who are providing real time updates on massive, massive data sets. They looked at lots of different ways to do this and there's the traditional, transactionals, LTP database and then maybe if you want to scale an API like theirs, you might have a separate end-memory cache and then yet another database for analytics. And so we bring all that together and simplify that and the benefit of simplification, but it's also this unification and lower latency. Another example is GE who basically uses us to bring together lots of financial information to provide quicker close to the end-of-month process across many different systems. >> So we think about special purpose databases, you mentioned one of the customers having those. We were in the keynote this morning where AWS is like, "We have the broadest set of special purpose databases," but you're saying the industry can't afford them anymore. Why and would it make SingleStore unique in terms of what you deliver? >> It goes back to this data intensity, in that the new business models that are coming out now are all about giving you this instant context and that's all data-driven and it's digital and it's also analytical. And so the reason that's you can't afford to do this, otherwise, is data's getting so big. Moving that data gets expensive, 'cause in the cloud you pay for every byte you store, every byte you process, every byte you move. So data movement is a cost in dollars and cents. It's a cost in time. It's also a cost in skill sets. So when you have many different specialized data sets or data-based technologies, you need skilled people to manage those. So that's why we think the industry needs to be simplified and then that's why you're seeing this unification trend across the database industry and other parts of the stack happening. With AWS, I mean, they've been a great partner of ours for years since we launched our first cloud database product and their perspective is a little bit different. They're offering choice of the specialty, 'cause many people build this way. But if you're going after real time data, you need to bring it. They also offer a SingleStore as a service on AWS. We offer it that way. It's in the AWS Marketplace. So it's easily consumable that way. >> Access to real time data is no longer a nice-to-have for any company, it's table stakes. We saw that especially in the last 20 months or so with companies that needed to pivot so quickly. What is it about SingleStore that delivers, that you talked about moments that matter? Talk about the access to real time data. How that's a differentiator as well? >> I think businesses need to be where their customers are and in the moments their customers are interacting. So that is the real time business-driver. As far as technology wise, it's not easy to do this. And you think about what makes a database fast? A major way of what makes it fast is how you store the data. And so since 2014, when we first released this, what Gartner called at the time, hybrid transaction/analytical processing or HTAP, where we brought transactional data and analytical data together. Fast forward five years to 2019, we released this innovation called Universal Storage, which does that in a single unified table type. Why that matters is because, I would say, basically cost efficiency and better speed. Again, because you pay for the storage and you pay for the movement. If you're not duplicating that data, moving it across different stores, you're going to have a better experience. >> One of the things you guys pioneered is unifying workloads. You mentioned some of the things you've done. Others are now doing it. Snowflake, Google and others. What does that mean for you guys? I mean, 'cause are they copying you? Are they trying to meet the functionality? >> I think. >> I mean, unification. I mean, people want to just store things and make it, get all the table stakes, check boxes, compliance, security and just keep coding and keep building. >> We think it's actually great 'cause they're validating what we've been seeing in the market for years. And obviously, they see that it's needed by customers. And so we welcome them to the party in terms of bringing these unified workloads together. >> Is it easy or hard? >> It's a difficult thing. We started this in 2014. And we've now have lots of production workloads on this. So we know where all the production edge cases are and that capability is also a building block towards a broader, expansive set of capabilities that we've moved onto that next phase and tomorrow actually we have an event called, The Real Time Data Revolution, excuse me, where we're announcing what's in that new product of ours. >> Is that a physical event or virtual? >> It's a virtual event. >> So we'll get the URL on the show notes, or if you know, just go to the new site. >> Absolutely. SingleStore Real Time Data Revolution, you'll find it. >> Can you tease us with the top three takeaways from Revolution tomorrow? >> So like I said, what makes a database fast? It's the storage and we completed that functionality three years ago with Universal Storage. What we're now doing for this next phase of the evolution is making enterprise features available and Workspaces is one of the foundational capabilities there. What SingleStore Workspaces does is it allows you to have this isolation of compute between your different workloads. So that's often a concern to new users to SingleStore. How can I combine transactions and analytics together? That seems like something that might be not a good thing. Well, there are multiple ways we've been doing that with resource governance, workload management. Workspaces offers another management capability and it's also flexible in that you can scale those workloads independently, or if you have a multi-tenant application, you can segment your application, your customer tenant workloads by each workspace. Another capability we're releasing is called Wasm, which is W-A-S-M, Web Assembly. This is something that's really growing in the open source community and SingleStore's contributing to that open source scene, CF project with WASI and Wasm. Where it's been mentioned mostly in the last few years has been in the browser as a more efficient way to run code in the browser. We're adapting that technology to allow you to run any language of your choice in the database and why that's important, again, it's for data movement. As data gets large in petabyte sizes, you can't move it in and out of Pandas in Python. >> Great innovation. That's real valuable. >> So we call this Code Engine with Wasm and- >> What do you call it? >> Code Engine Powered by Wasm. >> Wow. Wow. And that's open source? >> We contribute to the Wasm open source community. >> But you guys have a service that you- >> Yes. It's our implementation and our database. But Wasm allows you to have code that's portable, so any sort of runtime, which is... At release- >> You move the code, not the data. >> Exactly. >> With the compute. (chuckles) >> That's right, bring the compute to the data is what we say. >> You mentioned a whole bunch of great customer examples, GE, Uber, Thorn, you talked about IEX Cloud. When you're in customer conversations, are you dealing mostly with customers that are looking to you to help replace an existing database that was struggling from a performance perspective? Or are you working with startups who are looking to build a product on SingleStore? Is it both? >> It is a mix of both. I would say among SaaS scale up companies, their API, for instance, is their product or their SaaS application is their product. So quite literally, we're the data engine and the database powering their scale to be able to sign that next big customer or to at least sleep at night to know that it's not going to crash if they sign that next big costumer. So in those cases, we're mainly replacing a lot of databases like MySQL, Postgre, where they're typically starting, but more and more we're finding, it's free to start with SingleStore. You can run it in production for free. And in our developer community, we see a lot of customers running in that way. We have a really interesting community member who has a Minecraft server analytics that he's building based on that SingleStore free tier. In the enterprise, it's different, because there are many incumbent databases there. So it typically is a case where there is a, maybe a new product offering, they're maybe delivering a FinTech API or a new SaaS digital offering, again, to better participate in this digital service economy and they're looking for a better price performance for that real time experience in the app. That's typically the starting point, but there are replacements of traditional incumbent databases as well. >> How has the customer conversation evolved the last couple of years? As we talked about, one of the things we learned in the pandemic was access to real time data and those moments that matter isn't a nice-to-have anymore for businesses. There was that force march to digital. We saw the survivors, we're seeing the thrivers, but want to get your perspective on that. From the customers, how has the conversation evolved or elevated, escalated within an organization as every company has to be a data company? >> It really depends on their business strategy, how they are adapting or how they have adapted to this new digital first orientation and what does that mean for them in the direct interaction with their customers and partners. Often, what it means is they realize that they need to take advantage of using more data in the customer and partner interaction and when they come to those new ideas for new product introductions, they find that it's complicated and expensive to build in the old way. And if you're going to have these real time interactions, interactive applications, APIs, with all this context, you're going to have to find a better, more cost-effective approach to get that to market faster, but also not to have a big sprawling data-based technology infrastructure. We find that in those situations, we're replacing four or five different database technologies. A specialized database for key value, a specialized database for search- >> Because there's no unification before? Is that one of the reasons? >> I think it's an awareness thing. I think technology awareness takes a little bit of time, that there's a new way to do things. I think the old saying about, "Don't pave cow paths when the car..." You could build a straight road and pave it. You don't have to pave along the cow path. I think that's the natural course of technology adaption and so as more- >> And the- pandemic, too, highlighted a lot of the things, like, "Do we really need that?" (chuckles) "Who's going to service that?" >> That's right. >> So it's an awakening moment there where it's like, "Hey, let's look at what's working." >> That's right. >> Double down on it. >> Absolutely. >> What are you excited about new round of funding? We talked about, obviously, probably investments in key growth areas, but what excites you about being part of SingleStore and being a partner of AWS? >> SingleStore is super exciting. I've been in this industry a long time as an engineer and an engineering leader. At the time, we were MemSQL, came into SingleStore. And just that unification and simplification, the systems that I had built as a system engineer and helped architect did the job. They could get the speed and scale you needed to do track and trace kinds of use cases in real time, but it was a big trade off you had to make in terms of the complexity, the skill sets you needed and the cost and just hard to maintain. What excites me most about SingleStore is that it really feels like the iPhone moment for databases because it's not something you asked for, but once your friend has it and shows it to you, why would you have three different devices in your pocket with a flip phone, a calculator? (Lisa and Domenic chuckles) Remember these days? >> Yes. >> And a Blackberry pager. (all chuckling) You just suddenly- >> Or a computer. That's in there. >> That's right. So you just suddenly started using iPhone and that is sort of the moment. It feels like we're at it in the database market where there's a growing awareness and those announcements you mentioned show that others are seeing the same. >> And your point earlier about the iPhone throwing off a lot of data. So now you have data explosions at levels that unprecedented, we've never seen before and the fact that you want to have that iPhone moment, too, as a database. >> Absolutely. >> Great stuff. >> The other part of your question, what excites us about AWS. AWS has been a great partner since the beginning. I mean, when we first released our database, it was the cloud database. It was on AWS by customer demand. That's where our customers were. That's where they were building other applications. And now we have integrations with other native services like AWS Glue and we're in the Marketplace. We've expanded, that said we are a multi-cloud system. We are available in any cloud of your choice and on premise and in hybrid. So we're multi-cloud, hybrid and SaaS distribution. >> Got it. All right. >> Got it. So the event is tomorrow, Revolution. Where can folks go to register? What time does it start? >> 1:00 PM Eastern and- >> 1:00 PM. Eastern. >> Just Google SingleStore Real Time Data Revolution and you'll find it. Love for everyone to join us. >> All right. We look forward to it. Domenic, thank you so much for joining us, talking about SingleStore, the value prop, the differentiators, the validation that's happening in the market and what you guys are doing with AWS. We appreciate it. >> Thanks so much for having me. >> Our pleasure. For Domenic Ravita and John Furrier, I'm Lisa Martin. You're watching theCUBE, live from New York at AWS Summit 22. John and I are going to be back after a short break, so come back. (digital pulsing music)

>>Hey, everyone, welcome to the Cubes Coverage of the International Women's Showcase for 2022. I'm your host, Lisa Martin. Pleased to be here with an agreement ahead of small medium business SMB for Asia Pacific and Japan at Amazon Web services. Anna. It's great to have you on the programme, >>Lisa. I am delighted to be here and really excited to be talking about what we're gonna be talking about today, which is diversity and women in technology. >>One of the great things about International Women's Day Tuesday, March 8th, is there's always a campaign of theme. This year's theme is breaking the bias. What does that mean to you? And are we on our way to actually accomplish that? >>Look, Breaking the bias really is about all of us being more self aware in our workplaces. Really. What it means to me is understanding that the communities and the employment, the employee population, that all of us working is diverse. Um, and this is a great example of that, right? We are a global organisation and our employees come from across the world. I am representing people from across Asia Pacific and Japan. They look, feel and think differently to people in other parts of the world. So, really, what breaking the biases about is understanding our unconscious biases and thinking differently about how we approach conversations in the workplace to make sure that we're including everyone in the conversation. And honestly, Lisa, when you do that, you get much better. Business outcomes. I've seen that for sure. >>Definitely. There's some stats we can talk about later that I think really articulate that point incredibly well. But I want to talk about your background. You pivoted many times from lawyer to the CEO of ANZ Bank in the Philippines to now a leader at Amazon Web services. Talk to you about your career path with all those different pivots. How did you get to where you are tonight? >>Yeah, I mean, honestly, I recognise that I don't have a traditional Orthodox career plan, but that's my intention. I'm somebody who has always been really interested in the world around me, and I would say that my biggest driver is learning and being curious, which, as you know, is an Amazon leadership principles. So it's probably not a surprise that I ended up here at Ws, but really for me when I thought about my career and I have thought about it intentionally. I've been willing to put my hand up and take risks where I think probably others around me were not feeling as safe, and that's that's a function of who I am. But it's also a function of what I see women wanting to and needing to do more in order to bring their career forward. So as you say, I started my I had a pure technical lens when I started my career, which was being a lawyer, and there's been a lot of time just learning that and holding that skill set, I knew Lisa even then that that was not what I wanted to do forever. I wanted to do more than simply sit in an office and negotiate documents. Um, even though that was an exciting career, there was more that I wanted to do. So off the back of that, I moved into banking and was able to to learn and build some really important skill sets in terms of thinking about being a leader. And those skill sets include things like running a balance sheet, managing people thinking differently about risking compliance, which then allowed me to guess, run a bank and run the business. And then finally, how did I then pivot into technology? Well, it was a long conversation. If I'm honest with you, you know, there were there were conversations back and forth and I thought to myself and doing the right thing here. But what I could see for sure was that the world was moving to a technological context and for me not to take an opportunity to do it. A job like running a technology business across Asia, particularly Japan, just It just wasn't a possibility for me. I had to take the opportunity. So here I am, >>And that's one of the most exciting things I think is that these days every company has to be a tech company. Every company has to be a data company, a digital company with one of the lessons we've learned in the last couple of years. But another thing that we've learned is you mentioned skill sets. But it isn't just about those hard skill sets. What are some of those key soft skill sets that you think are really outstanding and really help to break down the bias. >>Yeah, again, Really interesting. So as I'm talking to women, when they hear about my career journey, a lot of them are surprised. How could you move into technology? And I think the challenge is that a lot of women view technology simply as a coding context. They view it as something that only someone with technical skills can do, and that is simply not the case. So if you look at a recent study by Deloitte Access Economics in Australia, for instance, the soft, skill intensive occupations are going to account for two thirds of all jobs by 2030. So if you think about that having a pure technical skill set, so certainly if you're going to do something like be a solutions architect or be a coda, it's really important that you must have those skills. But technology businesses are building and growing like no other, so we need all of those soft skills, like project management like P and L. Accountability and responsibility, like learning how to manage teams. These are caused fuels that have nothing to do with kind of fundamental technology, understanding that business contacts is important, but there are a lot of women out there who could be working in technology now but are a little bit scared to do so because they're thinking maybe they don't have the skills and I would encourage them to think differently. >>I think your your background with your pivots is a great articulation of you can take so many different backgrounds law banking into tech There's probably a fair amount of overlap there, but you also have you have in and of yourself thought diversity because of your background. I think that's another important thing for women to learn how important that thought diversity can be in any sort of job that they do, whether they are in a technical field. Or maybe they're in finance or operations or sales for a technology company. You guys talk about builders at A. W S. Talk to me about what a builder is, what's that definition and one of some of those key skill sets hard and soft that those builders exemplify. >>Yeah, so we are very build focused at AWS because we're building on behalf of our customers. But what that means is that the trays that make you a builder are exemplified by our leadership principles. So things like being curious. As you just pointed out, Lisa, these are the tenants of being a good builder, um, pursuing continuous learning. So whilst you you may know that you're good at something, you're not scared of trying something else. You're not scared of training and learning about something else. Being able to look around corners, um, and take calculated risks. I mean, whilst it may sound like my career journey has been pivot, pivot, pivot. Actually, if we're honest that these have been very intentional moves that I've made with my career to try to learn, as I said, to try to grow, um, and I've been fortunate and have been intentional also about building that leadership profile, But that's because I'm really fundamentally interested in how business and how people are connecting across the world. And as I said to you in a building context, really, that's about learning about how to build and run digital businesses. And at the end of the day is I guess the key message that I would send to everyone out there getting involved in a career in technology is not a bad move. >>No, it's definitely not a bad movie. I love the curiosity angle. That's one of those things that I'd love to hear. How do you encourage that? One of the biggest challenges. If we look at the stats of girls in stem programmes, from primary school to high school to university, as we see the numbers going down, we see them going up in university. And then, of course, when we're in, we're looking at the raw tech numbers. The number of women in technical positions is quite low to your point. There's many other opportunities besides technical positions. How do you encourage women to not be afraid to raise their hand and ask a question, even if they think maybe this is a dumb question? >>Uh, it's such a I think, you know, honestly, we need to see more women in leadership roles. Um, and, uh, and I think it's incumbent upon the organisations that are are running our businesses, that they make this a priority because you can't see I'm sorry. You can't be what you can't see Lisa, Um, and so it's great for us to talk about it. But once we start seeing women having active business, led conversations. That's where we're really going to see the dial shift. I have a 13 year old daughter, Um, and she's deeply interested in everything on her computer. Um, and what I try to do is encourage her to think differently about the type of roles that she could have if she was interested in, say, for instance, graphic design. She loves drawing, Um, singing. There are so many ways you can do all those YouTube videos. Maybe not, but you know, ways in which you can engage with technology to pursue a career that's interesting to you, regardless of your gender. So maybe the first part is making sure that we are talking about female leaders and what they're doing. I think also what we can do is start building programmes where we're involving women in building skills and certification skills. So here we've got this amazing event which we've built called She builds and I'm an active mentor for that. And what that's all about is kind of connecting women in the tech community and those who are interested with programmes that really speak to the way that women are thinking about their roles. So we have like minded peers. We have senior leaders, We have certification skills, programmes, always part of that, and we also have male allies. It's really important to include our male allies in that conversation, and you will have heard about things like male champions of change. These are very important conversations because again, what we know from statistics is that women are not as likely to build networks and sponsors as men are. And that's not statement of Miss Mala intense. What it means is that they just learn differently and think differently as they're building their careers. So if we're starting to get a man involved in the conversation in a more meaningful way, it's a conversation that's inclusive, and that's really what I want to drive. So I'm not sure I answered your question, but I certainly got to a couple of points that I was interested in highlighting, which is it's a conversation that has to happen at a grassroots level at a leadership level and across the organisation in terms of metrics, data understanding where women are and how to build and grow them >>right. But one of the things that you said that I was about to say was, We can't be what we can't see. We need to be able to elevate those female leaders like yourself so that more younger women and even women who maybe have been in the field for a while, can see the opportunities, the leadership. But you also brought up another great point. And that is, and something I was going to ask you about who are who are some of your mentors. And I imagine it's not just all females. It's got to be men as well. As you point out, it's incredibly important to have the men as allies. >>Yeah, absolutely. And certainly I wouldn't even be having this conversation with you now if I didn't have some amazing allies, both men and women, by my side as I've tracked this leadership journey. Certainly, um, Phil Davis, who is the head of our commercial organisation, Greg Pearson. These are people who have taken time out of their careers to talk with me about how we can help to build and grow women leaders, and to me, that's impactful. And I feel that that's an authentic engagement because there is a recognition in technology that we need to do more around this issue, and I see senior leaders like Matt Garman leading into the conversation. So for me, that's that's very inspiring. But I can't I couldn't have answered that question without telling you that the people who probably inspired me most in the organisation and within my network are those young women out there who are female founders. Now you know, I'm going to have to say a couple of names because I get the opportunity. Lisa, I've got a part of the networking, a women's networking, um, and mentoring organisation. And we have women here in Singapore like Ping Ping Han, who is building out an environmental education and sustainability digital business. We've got Francesco Cuccia, who is building Go get. She's already built it, which is an on demand workforce platform, which has over 250,000 people online that are helping people in Malaysia to work and has helped immensely during Covid. So what we're seeing with these young women is that they're actually building the digital businesses of the future, and it's not about, I mean, what I'm seeing them do is invest their time and energy in building. As I said, kind of programmes and models that are sustainable. So they're building businesses not just for the bottom line, but also to help the communities in which we operate, which to me is deeply inspirational. >>Absolutely. And the female founders need much more visibility than they're getting and obviously much more funding. One last point that I want to bring up because this is really important is that there is some data that I know that you have about performance company performance. When there are females at the helm, talk to me a little bit about that, and how can we help get that word out there more? Some more organisations understand the potential they have when they got that thought. Diversity. >>Yeah, it's such a wonderful point, and it's so well made now across the across media. But I feel like we need to double down on it because this is not a piecemeal conversation about doing the right thing. Um, sometimes we view it that way, and of course it is the right thing to have equity and diversity in our workplace. But in fact, there's so much data around how a diverse workforce creates better outcomes for business So in 2020 we had a McKenzie survey that found that companies with more than 30% of women executives were more likely to outperform companies with this percentage. So there is now a huge amount of data that's starting to show us what a diverse. And this is not just about gender. This is also about diversity across various lenses culture, ethnicity, minority groups, etcetera. So and for me, Lisa, it's just common sense. So if you're building a business that is trying to reach the most number of customers, it really is intuitive that you need to have all of those customers represented around the table. If you only have a single point of view, you're not going to represent all of those customers out there. And increasingly, those customers are expecting to be represented as part of your conversation in your business. So it totally makes sense from a business lens to build and recruit a diverse workforce. >>I couldn't agree more. One. I like to have one more question. Talk to me really quickly, briefly about how how are you building your teams to promote effectiveness through that diversity that, as you just described, can be so leading edge. >>Yeah, So what I'm doing is being intentional in my hiring practises. So this is something that all leaders can do. >>And that is really >>carefully about filling the roles in my organisation, where I'm given a role to fulfil, making sure that I'm looking at that diverse candidates, not just the same candidates who might have applied before. And that means sometimes throwing the net a bit wider than what you might usually have and thinking differently about the candidates that are applying. So, for instance, in my team, we have 50 50 men and women. Um, and we all come from very diverse backgrounds. We've got Indian, we've got Singaporean, we've got Australian talent, which means we've got a gender and cultural mix, which is actually, as I said, bringing a very different lens to the conversation when we're trying to solve customer problems. And what I would say is collaboration and respect is the cornerstone of the way that we should be. Building teams and diverse perspectives mean that our teams and the outcomes that we build are going to reflect the complexity of both the cross cultural and the divers, gender lens within which all of our customers are doing business today. >>Anna, thank you so much for joining me today, talking about the intentional pivots that you've made in your career, how inspiring those are two others and also how we're making progress on breaking the bias. My pleasure. >>Lisa. It's wonderful to join you. And thank you always think you for bringing us so much interesting data >>for Anna Greene. I'm Lisa Martin. You're watching the Cubes. Coverage of International Women's Showcase 2022.

>>Mm. >>Okay. Hello, and welcome to the Cubes Coverage of the International Women in Tech Showcase featuring National Women's Day. I'm John for a host of the Cube. We have a great guest here of any theory a PJ head of aerospace and satellite for A W S A P J s Asia Pacific in Japan. Great to have you on many thanks for joining us. Talk about Space and International Women's Day. Thanks for coming on. >>Thanks, John. It's such a pleasure to be here with you. >>So obviously, aerospace space satellite is an area that's growing. It's changing. AWS has made a lot of strides closure, and I had a conversation last year about this. Remember when Andy Jassy told me about this initiative to 2.5 years or so ago? It was like, Wow, that makes a lot of sense Ground station, etcetera. So it just makes a lot of sense, a lot of heavy lifting, as they say in the satellite aerospace business. So you're leading the charge over there in a p J. And you're leading women in space and beyond. Tell us what's the Storey? How did you get there? What's going on. >>Thanks, John. Uh, yes. So I need the Asia Pacific business for Clint, um, as part of Amazon Web services, you know, that we have in industry business vertical that's dedicated to looking after our space and space customers. Uh, my journey began really? Three or four years ago when I started with a W s. I was based out of Australia. Uh, and Australia had a space agency that was being literally being born. Um, and I had the great privilege of meeting the country's chief scientist. At that point. That was Dr Alan Finkel. Uh, and we're having a conversation. It was really actually an education conference. And it was focused on youth and inspiring the next generation of students. Uh, and we hit upon space. Um, and we had this conversation, and at that stage, we didn't have a dedicated industry business vertical at A W s well supported space customers as much as we did many other customers in the sector, innovative customers. And after the conversation with Dr Finkel, um, he offered to introduce me, uh, to Megan Clark, who was back back then the first CEO of the Australian Space Agency. So that's literally how my journey into space started. We had a conversation. We worked out how we could possibly support the Australian Space Agency's remit and roadmap as they started growing the industry. Uh, and then a whole industry whole vertical was set up, clinic came on board. I have now a global team of experts around me. Um, you know, they've pretty much got experience from everything creating building a satellite, launching a satellite, working out how to down link process all those amazing imagery that we see because, you know, um, contrary to what a lot of people think, Uh, space is not just technology for a galaxy far, far away. It is very much tackling complex issues on earth. Um, and transforming lives with information. Um, you know, arranges for everything from wildfire detection to saving lives. Um, smart, smart agriculture for for farmers. So the time of different things that we're doing, Um, and as part of the Asia Pacific sector, uh, my task here is really just to grow the ecosystem. Women are an important part of that. We've got some stellar women out here in region, both within the AWS team, but also in our customer and partner sectors. So it's a really interesting space to be. There's a lot of challenges. There's a lot of opportunities and there's an incredible amount of growth so specific, exciting space to be >>Well, I gotta say I'm super inspired by that. One of the things that we've been talking about the Cuban I was talking to my co host for many, many years has been the democratisation of digital transformation. Cloud computing and cloud scale has democratised and change and level the playing field for many. And now space, which was it's a very complex area is being I want kind of democratised. It's easier to get access. You can launch a satellite for very low cost compared to what it was before getting access to some of the technology and with open source and with software, you now have more space computing things going on that's not out of reach. So for the people watching, share your thoughts on on that dynamic and also how people can get involved because there are real world problems to solve that can be solved now. That might have been out of reach, but now it's cloud. Can you share your thoughts. >>That's right. So you're right, John. Satellites orbiting There's more and more satellites being launched every day. The sensors are becoming more sophisticated. So we're collecting huge amounts of data. Um, one of our customers to cut lab tell us that we're collecting today three million square kilometres a day. That's gonna increase to about three billion over the next five years. So we're already reaching a point where it's impossible to store, analyse and make sense of such massive amounts of data without cloud computing. So we have services which play a very critical role. You know, technologies like artificial intelligence machine learning. Help us help these customers build up products and solutions, which then allows us to generate intelligence that's serving a lot of other sectors. So it could be agriculture. It could be disaster response and recovery. Um, it could be military intelligence. I'll give you an example of something that's very relevant, and that's happening in the last couple of weeks. So we have some amazing customers. We have Max our technologies. They use a W S to store their 100 petabytes imagery library, and they have daily collection, so they're using our ground station to gather insight about a lot of changing conditions on Earth. Usually Earth observation. That's, you know, tracking water pollution, water levels of air pollution. But they're also just tracking, um, intelligence of things like military build up in certain areas. Capella space is another one of our customers who do that. So over the last couple of weeks, maybe a couple of months, uh, we've been watching, uh, images that have been collected by these commercial satellites, and they've been chronicling the build up, for instance, of Russian forces on Ukraine's borders and the ongoing invasion. They're providing intelligence that was previously only available from government sources. So when you talk about the democratisation of space, high resolution satellite images are becoming more and more ridiculous. Um, I saw the other day there was, uh, Anderson Cooper, CNN and then behind him, a screenshot from Capella, which is satellite imagery, which is very visible, high resolution transparency, which gives, um, respected journalists and media organisations regular contact with intelligence, direct intelligence which can help support media storytelling and help with the general public understanding of the crisis like what's happening in Ukraine. And >>I think on that point is, people can relate to it. And if you think about other things with computer vision, technology is getting so much stronger. Also, there's also metadata involved. So one of the things that's coming out of this Ukraine situation not only is tracking movements with the satellites in real time, but also misinformation and disinformation. Um, that's another big area because you can, uh, it's not just the pictures, it's what they mean. So it's well beyond just satellite >>well, beyond just satellite. Yeah, and you know, not to focus on just a crisis that's happening at the moment. There's 100 other use cases which were helping with customers around the globe. I want to give you a couple of other examples because I really want people to be inspired by what we're doing with space technology. So right here in Singapore, I have a company called Hero Factory. Um, now they use AI based on Earth observation. They have an analytics platform that basically help authorities around the region make key decisions to drive sustainable practises. So change detection for shipping Singapore is, you know, it's lots of traffic. And so if there's oil spills, that can be detected and remedy from space. Um, crop productivity, fruit picking, um, even just crop cover around urban areas. You know, climate change is an increasing and another increasing, uh, challenges global challenge that we need to tackle and space space technology actually makes it possible 15 50% of what they call e CVS. Essential climate variables can only be measured from space. So we have companies like satellite through, uh, one of our UK customers who are measuring, um, uh, carbon emissions. And so the you know, the range of opportunities that are out there, like you said previously untouched. We've just opened up doors for all sorts of innovations to become possible. >>It totally is intoxicating. Some of the fun things you can discuss with not only the future but solving today's problems. So it's definitely next level kind of things happening with space and space talent. So this is where you start to get into the conversation like I know some people in these major technical instance here in the US as sophomore second year is getting job offers. So there's a There's a there's a space race for talent if you will, um and women talent in particular is there on the table to So how How can you share that discussion? Because inspiration is one thing. But then people want to know what to do to get in. So how do you, um how do you handle the recruiting and motivating and or working with organisations to just pipeline interest? Because space is one of the things you get addicted to. >>Yeah. So I'm a huge advocate for science, technology, engineering, math. We you know, we highlights them as a pathway into space into technology. And I truly believe the next generation of talent will contribute to the grand challenges of our time. Whether that climate change or sustainability, Um, it's gonna come from them. I think I think that now we at Amazon Web services. We have several programmes that we're working on to engage kids and especially girls to be equipped with the latest cloud skills. So one of the programmes that we're delivering this year across Singapore Australia uh, we're partnering with an organisation called the Institute for Space Science, Exploration and Technology and we're launching a programme called Mission Discovery. It's basically students get together with an astronaut, NASA researcher, technology experts and they get an opportunity to work with these amazing characters, too. Create and design their own project and then the winning project will be launched will be taken up to the International space station. So it's a combination of technology skills, problem solving, confidence building. It's a it's a whole range and that's you know, we that's for kids from 14 to about 18. But actually it, in fact, because the pipeline build is so important not just for Amazon Web services but for industry sector for the growth of the overall industry sector. Uh, there's several programmes that were involved in and they range from sophomore is like you said all the way to to high school college a number of different programmes. So in Singapore, specifically, we have something called cloud Ready with Amazon Web services. It's a very holistic clouds killing programme that's curated for students from primary school, high school fresh graduates and then even earlier careers. So we're really determined to work together closely and it the lines really well with the Singapore government's economic national agenda, um so that that's one way and and then we have a tonne of other programmes specifically designed for women. So last year we launched a programme called She Does It's a Free online training learning programme, and the idea is really to inspire professional women to consider a career in the technology industry and show them pathways, support them through that learning process, bring them on board, help drive a community spirit. And, you know, we have a lot of affinity groups within Amazon, whether that's women in tech or a lot of affinity groups catering for a very specific niches. And all of those we find, uh, really working well to encourage that pipeline development that you talk about and bring me people that I can work with to develop and build these amazing solutions. >>Well, you've got so much passion. And by the way, if you have, if you're interested in a track on women in space, would be happy to to support that on our site, send us storeys, we'll we'll get We'll get them documented so super important to get the voices out there. Um and we really believe in it. So we love that. I have to ask you as the head of a PJ for a W S uh aerospace and satellite. You've you've seen You've been on a bunch of missions in the space programmes of the technologies. Are you seeing how that's trajectory coming to today and now you mentioned new generation. What problems do you see that need to be solved for this next generation? What opportunities are out there that are new? Because you've got the lens of the past? You're managing a big part of this new growing emerging business for us. But you clearly see the future. And you know, the younger generation is going to solve these problems and take the opportunities. What? What are they? >>Yes, Sometimes I think we're leaving a lot, uh, to solve. And then other times, I think, Well, we started some of those conversations. We started those discussions and it's a combination of policy technology. We do a lot of business coaching, so it's not just it's not just about the technology. We do think about the broader picture. Um, technology is transferring. We know that technology is transforming economies. We know that the future is digital and that diverse backgrounds, perspective, skills and experiences, particularly those of women minority, the youth must be part of the design creation and the management of the future roadmaps. Um, in terms of how do I see this going? Well, it's been sort of we've had under representation of women and perhaps youth. We we just haven't taken that into consideration for for a long time now. Now that gap is slowly becoming. It's getting closer and closer to being closed. Overall, we're still underrepresented. But I take heart from the fact that if we look at an agency like the US Mohammed bin Rashid Space Centre, that's a relatively young space agency in your A. I think they've got about three or 400 people working for them at this point in time, and the average age of that cohort John, is 28. Some 40% of its engineers and scientists are women. Um, this year, NASA is looking to recruit more female astronauts. Um, they're looking to recruit more people with disabilities. So in terms of changing in terms of solving those problems, whatever those problems are, we started the I guess we started the right representation mix, so it doesn't matter. Bring it on, you know, whether it is climate change or this ongoing crisis, productive. Um, global crisis around the world is going to require a lot more than just a single shot answer. And I think having diversity and having that representation, we know that it makes a difference to innovation outputs. We know that it makes a difference to productivity, growth, profit. But it's also just the right thing to do for so long. We haven't got it right, and I think if we can get this right, we will be able to solve the majority of some of the biggest things that we're looking at today. >>And the diversity of problems in the diversity of talent are two different things. But they come together because you're right. It's not about technology. It's about all fields of study sociology. It could be political science. Obviously you mentioned from the situation we have now. It could be cybersecurity. Space is highly contested. We dated long chat about that on the Last Cube interview with AWS. There's all these new new problems and so problem solving skills. You don't need to have a pedigree from Ivy League school to get into space. This is a great opportunity for anyone who can solve problems because their new No one's seen them before. >>That's exactly right. And you know, every time we go out, we have sessions with students or we're at universities. We tell them, Raise your voices. Don't be afraid to use your voice. It doesn't matter what you're studying. If you think you have something of value to say, say it. You know, by pushing your own limits, you push other people's limits, and you may just introduce something that simply hasn't been part of before. So your voice is important, and we do a lot of lot of coaching encouraging, getting people just to >>talk. >>And that in itself is a great start. I think >>you're in a very complex sector, your senior leader at AWS Amazon Web services in a really fun, exciting area, aerospace and satellite. And for the young people watching out there or who may see this video, what advice would you have for the young people who are trying to navigate through the complexities of now? Third year covid. You know, seeing all the global changes, um, seeing that massive technology acceleration with digital transformation, digitisation it's here, digital world we're in. >>It could >>be confusing. It could be weird. And so how would you talk to that person and say, Hey, it's gonna be okay? And what advice would you give? >>It is absolutely going to be okay. Look, from what I know, the next general are far more fluent in digital than I am. I mean, they speak nerd. They were born speaking nerd, so I don't have any. I can't possibly tell them what to do as far as technology is concerned because they're so gung ho about it. But I would advise them to spend time with people, explore new perspectives, understand what the other is trying to do or achieve, and investing times in a time in new relationships, people with different backgrounds and experience, they almost always have something to teach you. I mean, I am constantly learning Space tech is, um it's so complicated. Um, I can't possibly learn everything I have to buy myself just by researching and studying. I am totally reliant on my community of experts to help me learn. So my advice to the next generation kids is always always in this time in relationships. And the second thing is, don't be disheartened, You know, Um this has happened for millennia. Yes, we go up, then we come down. But there's always hope. You know, there there is always that we shape the future that we want. So there's no failure. We just have to learn to be resilient. Um, yeah, it's all a learning experience. So stay positive and chin up, because we can. We can do it. >>That's awesome. You know, when you mentioned the Ukraine in the Russian situation, you know, one of the things they did they cut the Internet off and all telecommunications and Elon Musk launched a star linked and gives them access, sending them terminals again. Just another illustration. That space can help. Um, and these in any situation, whether it's conflict or peace and so Well, I have you here, I have to ask you, what is the most important? Uh uh, storeys that are being talked about or not being talked about are both that people should pay attention to. And they look at the future of what aerospace satellite these emerging technologies can do for the world. What's your How would you kind of what are the most important things to pay attention to that either known or maybe not being talked about. >>They have been talked about John, but I'd love to see more prominent. I'd love to see more conversations about stirring the amazing work that's being done in our research communities. The research communities, you know, they work in a vast area of areas and using satellite imagery, for instance, to look at climate change across the world is efforts that are going into understanding how we tackle such a global issue. But the commercialisation that comes from the research community that's pretty slow. And and the reason it's loads because one is academics, academics churning out research papers. The linkage back into industry and industry is very, um, I guess we're always looking for how fast can it be done? And what sort of marginal profit am I gonna make for it? So there's not a lot of patients there for research that has to mature, generate outputs that you get that have a meaningful value for both sides. So, um, supporting our research communities to output some of these essential pieces of research that can Dr Impact for society as a whole, Um, maybe for industry to partner even more, I mean, and we and we do that all the time. But even more focus even more. Focus on. And I'll give you a small example last last year and it culminated this earlier this month, we signed an agreement with the ministry of With the Space Office in Singapore. Uh, so it's an MOU between AWS and the Singapore government, and we are determined to help them aligned to their national agenda around space around building an ecosystem. How do we support their space builders? What can we do to create more training pathways? What credits can we give? How do we use open datasets to support Singaporeans issues? And that could be claimed? That could be kind of change. It could be, um, productivity. Farming could be a whole range of things, but there's a lot that's happening that is not highlighted because it's not sexy specific, right? It's not the Mars mission, and it's not the next lunar mission, But these things are just as important. They're just focused more on earth rather than out there. >>Yeah, and I just said everyone speaking nerd these days are born with it, the next generations here, A lot of use cases. A lot of exciting areas. You get the big headlines, you know, the space launches, but also a lot of great research. As you mentioned, that's, uh, that people are doing amazing work, and it's now available open source. Cloud computing. All this is bringing to bear great conversation. Great inspiration. Great chatting with you. Love your enthusiasm for for the opportunity. And thanks for sharing your storey. Appreciate it. >>It's a pleasure to be with you, John. Thank you for the opportunity. Okay. >>Thanks, Manny. The women in tech showcase here, the Cube is presenting International Women's Day celebration. I'm John Ferrier, host of the Cube. Thanks for watching. Mm mm.

(upbeat music) >> Welcome everyone to theCUBE's presentation of the AWS Startup Showcase Open Cloud Innovations. This is season two of the ongoing series. We're covering exciting start startups in the AWS ecosystem to talk about open source community stuff. I'm your host, Dave Nicholson. And I'm delighted today to have two guests from Weaveworks. Steve George, COO of Weaveworks, and Steve Waterworth, technical marketing engineer from Weaveworks. Welcome, gentlemen, how are you? >> Very well, thanks. >> Very well, thanks very much. >> So, Steve G., what's the relationship with AWS? This is the AWS Startup Showcase. How do Weaveworks and AWS interact? >> Yeah sure. So, AWS is a investor in Weaveworks. And we, actually, collaborate really closely around EKS and some specific EKS tooling. So, in the early days of Kubernetes when AWS was working on EKS, the Elastic Kubernetes Service, we started working on the command line interface for EKS itself. And due to that partnership, we've been working closely with the EKS team for a long period of time, helping them to build the CLI and make sure that users in the community find EKS really easy to use. And so that brought us together with the AWS team, working on GitOps and thinking about how to deploy applications and clusters using this GitOps approach. And we've built that into the EKS CLI, which is an open source tool, is a project on GitHub. So, everybody can get involved with that, use it, contribute to it. We love hearing user feedback about how to help teams take advantage of the elastic nature of Kubernetes as simply and easily as possible. >> Well, it's great to have you. Before we get into the specifics around what Weaveworks is doing in this area that we're about to discuss, let's talk about this concept of GitOps. Some of us may have gotten too deep into a Netflix series, and we didn't realize that we've moved on from the world of DevOps or DevSecOps and the like. Explain where GitOps fits into this evolution. >> Yeah, sure. So, really GitOps is an instantiation, a version of DevOps. And it fits within the idea that, particularly in the Kubernetes world, we have a model in Kubernetes, which tells us exactly what we want to deploy. And so what we're talking about is using Git as a way of recording what we want to be in the runtime environment, and then telling Kubernetes from the configuration that is stored in Git exactly what we want to deploy. So, in a sense, it's very much aligned with DevOps, because we know we want to bring teams together, help them to deploy their applications, their clusters, their environments. And really with GitOps, we have a specific set of tools that we can use. And obviously what's nice about Git is it's a very developer tool, or lots and lots of developers use it, the vast majority. And so what we're trying to do is bring those operational processes into the way that developers work. So, really bringing DevOps to that generation through that specific tooling. >> So Steve G., let's continue down this thread a little bit. Why is it necessary then this sort of added wrinkle? If right now in my organization we have developers, who consider themselves to be DevOps folks, and we give them Amazon gift cards each month. And we say, "Hey, it's a world of serverless, "no code, low code lights out data centers. "Go out and deploy your code. "Everything should be fine." What's the problem with that model, and how does GitOps come in and address that? >> Right. I think there's a couple of things. So, for individual developers, one of the big challenges is that, when you watch development teams, like deploying applications and running them, you watch them switching between all those different tabs, and services, and systems that they're using. So, GitOps has a real advantage to developers, because they're already sat in Git, they're already using their familiar tooling. And so by bringing operations within that developer tooling, you're giving them that familiarity. So, it's one advantage for developers. And then for operations staff, one of the things that it does is it centralizes where all of this configuration is kept. And then you can use things like templating and some other things that we're going to be talking about today to make sure that you automate and go quickly, but you also do that in a way which is reliable, and secure, and stable. So, it's really helping to bring that run fast, but don't break things kind of ethos to how we can deploy and run applications in the cloud. >> So, Steve W., let's start talking about where Weaveworks comes into the picture, and what's your perspective. >> So, yeah, Weaveworks has an engine, a set of software, that enables this to happen. So, think of it as a constant reconciliation engine. So, you've got your declared state, your desired state is declared in Git. So, this is where all your YAML for all your Kubernetes hangs out. And then you have an agent that's running inside Kubernetes, that's the Weaveworks GitOps agent. And it's constantly comparing the desired state in Git with the actual state, which is what's running in Kubernetes. So, then as a developer, you want to make a change, or an operator, you want to make a change. You push a change into Git. The reconciliation loop runs and says, "All right, what we've got in Git does not match "what we've got in Kubernetes. "Therefore, I will create story resource, whatever." But it also works the other way. So, if someone does directly access Kubernetes and make a change, then the next time that reconciliation loop runs, it's automatically reverted back to that single source of truth in Git. So, your Kubernetes cluster, you don't get any configuration drift. It's always configured as you desire it to be configured. And as Steve George has already said, from a developer or engineer point of view, it's easy to use. They're just using Git just as they always have done and continue to do. There's nothing new to learn. No change to working practices. I just push code into Git, magic happens. >> So, Steve W., little deeper dive on that. When we hear Ops, a lot of us start thinking about, specifically in terms of infrastructure, and especially since infrastructure when deployed and left out there, even though it's really idle, you're paying for it. So, anytime there's an Ops component to the discussion, cost and resource management come into play. You mentioned this idea of not letting things drift from a template. What are those templates based on? Are they based on... Is this primarily an infrastructure discussion, or are we talking about the code itself that is outside of the infrastructure discussion? >> It's predominantly around the infrastructure. So, what you're managing in Git, as far as Kubernetes is concerned, is always deployment files, and services, and horizontal pod autoscalers, all those Kubernetes entities. Typically, the source code for your application, be it in Java, Node.js, whatever it is you happen to be writing it in, that's, typically, in a separate repository. You, typically, don't combine the two. So, you've got one set of repository, basically, for building your containers, and your CLI will run off that, and ultimately push a container into a registry somewhere. Then you have a separate repo, which is your config. repo, which declares what version of the containers you're going to run, how many you're going to run, how the services are bound to those containers, et cetera. >> Yeah, that makes sense. Steve G., talk to us about this concept of trusted application delivery with GitOps, and frankly, it's what led to the sort of prior question. When you think about trusted application delivery, where is that intertwinement between what we think of as the application code versus the code that is creating the infrastructure? So, what is trusted application delivery? >> Sure, so, with GitOps, we have the ability to deploy the infrastructure components. And then we also define what the application containers are, that would go to be deployed into that environment. And so, this is a really interesting question, because some teams will associate all of the services that an application needs within an application team. And sometimes teams will deploy sort of horizontal infrastructure, which then all application teams services take advantage of. Either way, you can define that within your configuration, within your GitOps configuration. Now, when you start deploying speed, particularly when you have multiple different teams doing these sorts of deployments, one of the questions that starts to come up will be from the security team, or someone who's thinking about, well, what happens if we make a deployment, which is accidentally incorrect, or if there is a security issue in one of those dependencies, and we need to get a new version deployed as quickly as possible? And so, in the GitOps pipeline, one of the things that we can do is to put in various checkpoints to check that the policy is being followed correctly. So, are we deploying the right number of applications, the right configuration of an application? Does that application follow certain standards that the enterprise has set down? And that's what we talk about when we talk about trusted policy and trusted delivery. Because really what we're thinking about here is enabling the development teams to go as quickly as possible with their new deployments, but protecting them with automated guard rails. So, making sure that they can go fast, but they are not going to do anything which destroys the reliability of the application platform. >> Yeah, you've mentioned reliability and kind of alluded to scalability in the application environment. What about looking at this from the security perspective? There've been some recently, pretty well publicized breaches. Not a lot of senior executives in enterprises understand that a very high percentage of code that their businesses are running on is coming out of the open source community, where developers and maintainers are, to a certain degree, what they would consider to be volunteers. That can be a scary thing. So, talk about why an enterprise struggles today with security, policy, and governance. And I toss this out to Steve W. Or Steve George. Answer appropriately. >> I'll try that in a high level, and Steve W. can give more of the technical detail. I mean, I'll say that when I talk to enterprise customers, there's two areas of concern. One area of concern is that, we're in an environment with DevOps where we started this conversation of trying to help teams to go as quickly as possible. But there's many instances where teams accidentally do things, but, nonetheless, that is a security issue. They deploy something manually into an environment, they forget about it, and that's something which is wrong. So, helping with this kind of policy as code pipeline, ensuring that everything goes through a set of standards could really help teams. And that's why we call it developer guard rails, because this is about helping the development team by providing automation around the outside, that helps them to go faster and relieves them from that mental concern of have they made any mistakes or errors. So, that's one form. And then the other form is the form, where you are going, David, which is really around security dependencies within software, a whole supply chain of concern. And what we can do there, by, again, having a set of standard scanners and policy checking, which ensures that everything is checked before it goes into the environment. That really helps to make sure that there are no security issues in the runtime deployment. Steve W., anything that I missed there? >> Yeah, well, I'll just say, I'll just go a little deeper on the technology bit. So, essentially, we have a library of policies, which get you started. Of course, you can modify those policies, write your own. The library is there just to get you going. So, as a change is made, typically, via, say, a GitHub action, the policy engine then kicks in and checks all those deployment files, all those YAML for Kubernetes, and looks for things that then are outside of policy. And if that's the case, then the action will fail, and that'll show up on the pull request. So, things like, are your containers coming from trusted sources? You're not just pulling in some random container from a public registry. You're actually using a trusted registry. Things like, are containers running as route, or are they running in privileged mode, which, again, it could be a security? But it's not just about security, it can also be about coding standards. Are the containers correctly annotated? Is the deployment correctly annotated? Does it have the annotation fields that we require for our coding standards? And it can also be about reliability. Does the deployment script have the health checks defined? Does it have a suitable replica account? So, a rolling update. We'll actually do a rolling update. You can't do a rolling update with only one replica. So, you can have all these sorts of checks and guards in there. And then finally, there's an admission controller that runs inside Kubernetes. So, if someone does try and squeeze through, and do something a little naughty, and go directly to the cluster, it's not going to happen, 'cause that admission controller is going to say, "Hey, no, that's a policy violation. "I'm not letting that in." So, it really just stops. It stops developers making mistakes. I know, I know, I've done development, and I've deployed things into Kubernetes, and haven't got the conflict quite right, and then it falls flat on its face. And you're sitting there scratching your head. And with the policy checks, then that wouldn't happen. 'Cause you would try and put something in that has a slightly iffy configuration, and it would spit it straight back out at you. >> So, obviously you have some sort of policy engine that you're you're relying on. But what is the user experience like? I mean, is this a screen that is reminiscent of the matrix with non-readable characters streaming down that only another machine can understand? What does this look like to the operator? >> Yeah, sure, so, we have a console, a web console, where developers and operators can use a set of predefined policies. And so that's the starting point. And we have a set of recommendations there and policies that you can just attach to your deployments. So, set of recommendations about different AWS resources, deployment types, EKS deployment types, different sets of standards that your enterprise might be following along with. So, that's one way of doing it. And then you can take those policies and start customizing them to your needs. And by using GitOps, what we're aiming for here is to bring both the application configuration, the environment configuration. We talked about this earlier, all of this being within Git. We're adding these policies within Git as well. So, for advanced users, they'll have everything that they need together in a single unit of change, your application, your definitions of how you want to run this application service, and the policies that you want it to follow, all together in Git. And then when there is some sort of policy violation on the other end of the pipeline, people can see where this policy is being violated, how it was violated. And then for a set of those, we try and automate by showing a pull request for the user about how they can fix this policy violation. So, try and make it as simple as possible. Because in many of these sorts of violations, if you're a busy developer, there'll be minor configuration details going against the configuration, and you just want to fix those really quickly. >> So Steve W., is that what the Mega Leaks policy engine is? >> Yes, that's the Mega Leaks policy engine. So, yes, it's a SaaS-based service that holds the actual policy engine and your library of policies. So, when your GitHub action runs, it goes and essentially makes a call across with the configuration and does the check and spits out any violation errors, if there are any. >> So, folks in this community really like to try things before they deploy them. Is there an opportunity for people to get a demo of this, get their hands on it? what's the best way to do that? >> The best way to do it is have a play with it. As an engineer, I just love getting my hands dirty with these sorts of things. So, yeah, you can go to the Mega Leaks website and get a 30-day free trial. You can spin yourself up a little, test cluster, and have a play. >> So, what's coming next? We had DevOps, and then DevSecOps, and now GitOps. What's next? Are we going to go back to all infrastructure on premises all the time, back to waterfall? Back to waterfall, "Hot Tub Time Machine?" What's the prediction? >> Well, I think the thing that you set out right at the start, actually, is the prediction. The difference between infrastructure and applications is steadily going away, as we try and be more dynamic in the way that we deploy. And for us with GitOps, I think we're... When we talk about operations, there's a lots of depth to what we mean about operations. So, I think there's lots of areas to explore how to bring operations into developer tooling with GitOps. So, that's, I think, certainly where Weaveworks will be focusing. >> Well, as an old infrastructure guy myself, I see this as vindication. Because infrastructure still matters, kids. And we need sophisticated ways to make sure that the proper infrastructure is applied. People are shocked to learn that even serverless application environments involve servers. So, I tell my 14-year-old son this regularly, he doesn't believe it, but it is what it is. Steve W., any final thoughts on this whole move towards GitOps and, specifically, the Weaveworks secret sauce and superpower. >> Yeah. It's all about (indistinct)... It's all about going as quickly as possible, but without tripping up. Being able to run fast, but without tripping over your shoe laces, which you forgot to tie up. And that's what the automation brings. It allows you to go quickly, does lots of things for you, and yeah, we try and stop you shooting yourself in the foot as you're going. >> Well, it's been fantastic talking to both of you today. For the audience's sake, I'm in California, and we have a gentleman in France, and a gentlemen in the UK. It's just the wonders of modern technology never cease. Thanks, again, Steve Waterworth, Steve George from Weaveworks. Thanks for coming on theCUBE for the AWS Startup Showcase. And to the rest of us, keep it right here for more action on theCUBE, your leader in tech coverage. (upbeat music)

>>Yeah, yeah. Okay. Welcome back, everyone to the cubes. Coverage of reinvent 20 twenty-one Jon, your host of the Cube. We're here. Live in person for a real event. It's a hybrid event is a live stream of action to cube sets here, wall to wall coverage dot com. And, of course, you don't need to check the coverage out. And Amazon has got their own live event site. Go check out all the action. Stewart, See two of Micro Focus, the company That was part of the big announcement involving the mainframe modernization that Adam announced on stage and his first keynote CEO. And under the covers Micro Focus powering a lot of that functionality. Stuart, thanks for coming on. The break it down with >>Thanks. >>So what does the announcement? I mean that that Adam gave the i b. M. I mean the mainframe announcement that I've known for the main frame, but he had the mainframe modernization program. What's that all about? >>I think I'd like to think of this is the next evolution of the main frame for those customers that have been running on the main thing for 40 years. They had their business on it. Where do they go next? What does the future? What does the future hold? And this is all part of the announcement yesterday is this is the journey that many, many customers are going to decide to go on. >>So it's all about the relationship between A. W S and micro Focus. Obviously, Um, yeah. I was talking about migration for the Oracle, and a lot of our customers have these main friends that are in the classic data centers. And he told me personally when I interviewed him that the main part of that data center mindset that people are chipping away at now they want to move them out and keep some functionality, but for the most part, migrated out eventually. Yeah, This is where you guys are involved. Take us through why that's important. >>I think it's the next level of agility that it is actually delivered for many customers. They need to move a hell of a lot faster than they currently are. Let's face it, the world is changing at pace. The applications support these customers need to also a change of pace. What a W s does give this market and momentum which is, Where do we go next? Where do we take customers where workloads have been running the business? Where? How are they going to run the business in five years time? How they're gonna run their business in 10. >>Well, congratulations on microphone. Big part of the announcement. Specifically explained to me, Micro focuses role in the announcement with a W S. What's the relationship? >>I think they're too old to call it out. Actually, we've been working with A W S for many, many years. This isn't something that radically new. We've been engaging with them for literally 10 years, at least. But the key elements Microphone provides technology That's an enabler to facilitate delivering the service as well as the competency partner to help customers actually accelerate their journey to take advantage of it. >>So we're bundling micro focus into that capability. Is it software that you guys have? What's going on the covers? >>I think it's software. It's capability. It's expertise. It's everything that a customer might need to help and be successful. Our job is to a W S H A W s job to make sure the customer is absolutely satisfied. >>Give me an example of a customer mainframe. I'm a bank. I've been using the main frame and just squeaked Time to get my back up before I turned the light in the morning. It's just working. It's coming. It's pumping it all cylinders, my cobalt program or just quit. What do I do? How do you help me? >>Well, I think there are two reasons why you can give us a call Is number one? Yeah, You need to move your business of pace. So what's going to run your business going forward? So you need to understand your applications. Number two, the cost profile of your existing infrastructure is going to be incredibly expensive. So what you wanna do is essentially make the change accelerate the change delivered at a much lower cost. >>So it looks like the application. So the software Okay, what's the app? And then create a replica of digital twin? I'm just trying to visualized. Now I see what you mean. What happens because, I mean, you know what? That is A big deal with that animal for a long time. What happens next is a container eyes. That application, >>the customer determines how far they want to go if they would like the application to run in the cloud exactly as is so it supports their customers exactly as they expect today. We can do that. On the other hand, if they need to enhance the experience for their customers if they need to take it into a completely different environment. If they do want to contain, arise if they want to take it into new levels of service. If they do want to leverage artificial intelligence and machine learning, then again they can determine the journey. Micro focus is that essentially support them. Do that first step, which is get the applications ready to be delivered into cloud as fast as possible. >>Congratulations. Relationship. I guess I've got to ask you a question. Which on my mind is that Okay? It's the death of the mainframe. Long live the mainframe. You know the expression, uh, mainframe dying. I'm gonna hang around for a while. The dinosaurs are out there. >>I think it is. We like to position there is an evolution. We don't think the main friends gonna die. There will be customers who want to stay there, and we respect their choices. But on the other hand, this is a way to truly accelerate the future of mainstream applications. >>You know, student, I talked to a lot of success and C E O. S. And they tell me the same thing when they moved into the cloud. White hardcore is pretty much the main or critical laps to get the edges first moved into the cloud. And then they come and they start chipping away at the main, the main core and then slowly move it out because they don't want to get in there and disrupt so disruptions. A huge concerns. How does this new, um, modernization Tranz, uh, migration program for the mainframe ensure that disruption doesn't happen? What? I'm sure that's on their mind >>as well. I think what you're describing is what's the cut over when you're running on the main street today? You wanna run on the main from tomorrow, You know, if that's the case, or do you want to run the main from today and you want to run the cloud tomorrow? Essentially, the cut over is the same. The process is fairly separate from the mainframe itself. You obviously bringing applications off. We're getting them ready to go tested, you know, regulated. So it's been approved securities all in place, and then essentially, it's literally a switch cut. We literally have customers that turn off the main frame and, you know, they're already running in the cloud, and then we don't even have some that photographs of them shipping mainframe out the door. >>So I've got to ask, Is there a party at that point? You know, some people do >>that. It's certainly true. Remember that people are also going along for this journey, and they're not, You know, it's a big moment for them. >>You know, I hate the sound of today's my birthday. So I have to say this, Um, I remember when I was breaking into the business in my twenties. I never I never program punch cards, But remember pointing at the mainstream guys are seeing those old relics. I guess that's what I would be today. But the young guns coming into the industry, they want containers. They want micro services. They want cloud and see what's going on here. I mean, some really cool stuff happening. >>Uh, they want to take advantage of all the stuff that is there and every single announcement has been made today and yesterday on the days ahead. All of those great capabilities if you can get them into the core of your business. And so the key is to actually take us running your business today, enhance it and improve it and take it forward. I >>think I think the key points great insight on your part about this cut over because people know what that means. It's a project plan. Cut it over, get set up. And I think that's the hard part. How hard is that? On the cloud side, In terms of staging, can you share some timetables with me? Just kind of Give me a feel for order of magnitude Mainframe. Assuming, pumping it snap I'm using. I really can't shut it down, but I want to put it on. How much time to prepare to get into the cloud? Um, roughly just order of magnitude. Most >>customers, they tend to face these things they're not trying to. If you're a really big bank, you are not gonna do that overnight. That isn't gonna come as a surprise. But what we're gonna do is we're gonna take it in chunks and typically 12 to 15 months, which is the biggest step of the journey, which is going from mainframe to cloud. The next generation is going to be modernizing those applications, and it's going to be much short timeframes. Then you're getting into months, weeks, days >>after that. Is there any category that you see that are more susceptible to migration? You mentioned banks. I know some banks that they will never going to touch the mainstream because it's just so critical that the migration longer is there. Other areas of your insurance is a big market mainframe. Is the verticals that kind of like a more converting than others? >>Well, yes. But actually, I take it back. One of the reasons are these applications absolutely critical to these businesses. If they are, that's the reason why they're still running where they are, because they're really truly valuable. They are the business, so you're you're taking the business into new framework. So in that context actually tends to be financial services insurance, as you say, but also government, For example, the federal government, state and local as well as you move into retail. And it's surprising how often as you go into some of the other verticals where some of these mainframe applications are still existing. >>I hate to ask a question, because I don't know. So I want to ask, Um, and you can see it's a dumb question. If you think it is. Just tell me, Are there still cobalt programmers out there? >>There are to be clear. Actually, it's not a problem. You can train a new guy and literally weeks. If the issue is, yeah, actually use the mainstream itself, the mainstream experience about how it works as getting rarer. And so the key element is, how can how can you take the new young guns, give them, give them the application and see what they can do? This is a mechanism to do that. >>Great, Great announcement. Congratulations. I was really impressed at the moment. I'm actually surprised to see Adam kind of focus on that. But again, in the spirit of the traditional, uh, reinvent jazzy before Adam and he did the same thing with Oracle and all the other kind of big the legacy old guard they call them Technologies maintains one. You guys are part of that. So congratulations. Final word. Your take on the event so far. What's been the feedback on the announcement? Share some color commentary on what the feedback for you guys >>were. Actually, since the announcement, we've had some great customer conversations. I mean, there are a lot of businesses that really do want to make this change. We're kind of there to help them. And that's really the next step, which is what needs to happen to make that a reality. >>Amazon may not like me saying it, but I think there's some cases where you keep them in there and you don't touch. It works there. You keep it unless you wanna move. But if you want to move it, people, sometimes we want to move faster. And just there >>even a W s respects customer choice. The purpose is to meet the demand for the customer. And if the customer to sounds great, if they want to move off, we're there to help >>with the mainframe. Long live the main friends. The Cube coverage here in Las Vegas. I'm John. I love the mainframe Thirty-seven terminal. When I worked at the back in the eighties getting myself, um, thanks for coming in. And I appreciate it. Okay. Coverage here in Las Vegas. The Cube. You're watching the leader in global tech event coverage? I'm your host. Thanks for watching. Yeah, Yeah, yeah, yeah, yeah. Uh, mhm, yeah.

>>Yeah. Hey, everyone, Welcome to the cubes. Continuous coverage of AWS Re invent 2021. I'm Lisa Martin with John Furrier were running one of the industry's largest and most important hybrid tech events with AWS and massive ecosystem of partners. Right now there are two live cube sets to remote sets over 100 guests on the programme and we're pleased to welcome back one of our alum I to talk about the next generation and cloud innovation. Georgia Lisa is joins John to me, the director of product management for EC two edge at A. W S George. Welcome to the programme. >>Glad to be here in person. Thanks Great to be here in person. Awesome to be here in person. Finally, >>one of the things that is very clear is the US flywheel of innovation and there was no slowdown with what's happened in the last 22 months. Amazing announcements, new leadership. We talked a little bit about five g yesterday, but let's talk more about that. Everyone is excited about five g consumers businesses. What's going on? >>So, yeah, I wanted to talk to you today about the new service that we launched called AWS Private. Five g. Essentially, it's a service that allows any AWS customer to build their own private five g network and what we try to do with the services make it that simple and cost effective for anyone without any telco experience or expertise, really, to build their own private five g network. So you just have to go to your AWS console. Um, describe the parameters for network simple stuff like, Where do you want it to be located? The throughput, the number of devices and AWS will build a plan for your network and seep you everything that you need. Just plug it together. Uh, turn it on and the network automatically configures itself. All you got to do is popular sim cards that we send you into your mobile devices and you have a private five g network working in your your premise is >>one of the things that we know and love about AWS is its customer obsession. It's focused on the customer's that whole flywheel of all the innovation that comes out as Adam was saying yesterday to the customers, we deliver this, but but you wanted more. We said we deliver this, but you wanted more. Talk to me a little bit about some of the customer catalysts for private five G. >>Actually, one of the good examples is where we are right now. More and more AWS customers need to connect an increased number of devices, and these devices become more data hungry. You know they need to push data around. They also become more and more wireless, right? Uh, so when you are trying to connect devices in the manufacturing floor, bit sensors, you know, connect the tracks, forklifts or in a convention centre. You look at how many devices there are around us. When you're trying to connect these devices with a wired network, you quickly run into physical problems like it's. It's hard to lay cable anywhere, and customers try to use for many of these use cases. But as a number of devices grows into the thousands and you know you need to put more and more data around, you quickly reach the limitations of what the WiFi technology and also WiFi is not really great at covering really open, large space. So that's where these customers, you know, think of college campuses, convention centres, manufacturing floors, all of these customers. Really? What they need to be able to do is to level the power of the mobile networks. However, doing that by yourself is pretty hard. So that's what we aim to to enable here we are waiting to enable these customers to build very easily and cost effectively their own. Uh, >>Okay, George. So I have to ask. I'm truly curious. I love this announcement. Um, because it brings together kind of the edge story. But also, I'm a band with love. I love more broad. Give me more broadband. Faster, cheaper and more broadband. How does it work? So take me through the use case of what do I need to deploy? Do I need to have a back haul connection? What does that look like? Is there a certain band with requirements? How big is the footprint? What's the radius? Just walk me through. How do I roll this out? >>Yeah, sure. Some of that stuff actually depends on your requirements, right. How How big? How much of a space do you want to cover? Basically, what we see, if you were in preview right now, so we're sipping you. The simplest configuration, which is basically these things called small cells there, you know, radio units and antennas. And all you have to do is connect them to your local. The network has Internet access. These things connect and automatically had, you know, connect home to the cloud and basically integrate and build up your whole network. All all you need is that Internet connection, and I don't know what to do. Now, how big is the network? You can You can make it pretty big. You can cover hundreds of thousands of square feet with with cellular networks with mobile networks. Um, you know, the bigger you they especially want to cover the more of these radio units. We're gonna stop you, uh, >>classic wireless radios. >>Yes. You >>light up the area with five g connected to the network. That's your choke point. The big of the pipe >>took the bigger pipe. That toxic. I mean, well, there, there's two. There's two things to consider here. There is local connectivity. So devices talking to each other, and there was connectivity back to somewhere else, like the Internet or the cloud. There are use cases, for example. Let's say data video feeds that you want to push up to do some inference in the cloud. In these use cases, you're basically pushing all of the data up. There is no left. There's no East West connectivity locally, and that's where our simplest configuration works best. There are other, uh, use cases where there is a lot of connectivity and devices talk to each other locally, like in this place, for example, right in this. In these cases, we can sip you that second configuration where we actually see Pew, a managed hardware WS managed hardware on premises, and that runs the smart of the network and allows all of your data traffic to remain local. That's >>wavelength Outpost, or both. >>A different configuration of A. W s private five G. It's a managed service. We take. We take care of it. You basically it's very It has a pricing model, which is very customer friendly because you like multi W services. You can start with no upfront fees. You can scale and pay as you scale because >>it's designed to deploy easily. >>Yep, deploys the >>footprint. Just I'm just curious if the poll is it like, it's like an antenna. Is it like so and >>yeah, well, the antenna is, you know, the small cell. They call them small cells in, you know, in in cellular land there, this big. And you can you can hide this. There is actually a demo in the Venetian of the private service. So you can you can actually see it in action, but yeah, that thing can cover 10,000 square feet, just one of them. So you can >>go out and put a five g network downtown and be like the king. >>You could Yes. You could have your own private network. You can monetise that next >>on the Q. >>Great stuff. >>So in terms of industries adopting this, you gave us some examples. Obviously. Convention centres, campuses, universities. I'm just curious, given the amount of acceleration that we've seen in every industry the last 22 months where organisations must become digital. They depend on that for their livelihood. And we saw this all these pivots, right? 22 months ago. How do we survive this? How do we thrive? Are consumers now are whether it's an injury or consumer or enterprise. Have this expectation that we're gonna be able to communicate no matter where we are 24 by seven. Whether it's health care, financial services. I'm just curious if you're seeing any industries in particular that you think are really prime for this private five >>G. Yeah. So manufacturing is a is a really great example because you have to cover large spaces. You have thousands of devices, sensors, etcetera and using other solutions like WiFi does not provide you the depth of capabilities like, for example, you know, advanced security capabilities or even capabilities to prioritise traffic from some devices over others, which is what a five G network can do for you. But also, you know, it involves large spaces both indoors and outdoors. We, you know, actually, Amazon is a really great example of you know of using this. We're working with Amazon fulfilment centres. These are the warehouses that fulfil your orders when you order online. Um, and they are a mix of indoor space and outer space, and you can think of, you know, I don't know if you've seen pictures or videos. There's robots running around their sensors everywhere. There is packing lines, etcetera, all of these things in order to operate performantly, but also securely and safely for the people that are around. You need to be well connected at a very high reliability rate. Right? So, uh, Amazon for two networks is actually using private A W s private five G to connect all of these devices. The really key thing here is you don't have to go drop 1000 of these access points we're talking about you. Can you can. You can probably cover your space with 5 10 of these. So your operational expenses, your maintenance goes down and there is less interruption of your normal operations like you can't. You don't have to stop your manufacturing line for someone to come in and fix your WiFi access. >>It's great for campuses like college campuses, college >>campuses, a great one. We you know, we've worked with college campuses, including the CME University in the past two, you know, with some of our partners to, uh, to to deploy. So >>that's how close you have these distribution, gas systems, distribution, whatever they call it accelerate whatever amplifies into get extra coverage, this seems to be a good fit. Um, for that how you mentioned in the preview? How do people get involved? Is there like a criteria. How was it going to >>be available to get priority? Don't get you >>tell them ready to jump in. Take us through the programme. What's the plants? >>So currently we're you know, we're in that preview mode. So we're keeping you this small configuration, the simpler configuration. You can sign up on the AWS website and you know, we, as we scale our operations are supply chain. Because this involves also, you know, hardware, etcetera. We're gonna go to general availability g A over the next few months and we have both configurations open. So I I encourage everyone who is interested go to the W s website and sign up. We're asking to get that in customers' hands because we're getting overwhelmingly positive feedback on what we built. >>This is transformative. I mean, clearly what you're talking about here is going to transform industry and help organisations transform themselves and outpaced the competitors that are in the rear view mirror Aren't going to be able to take advantage of this were on the show floor. We've got lots of people here. Where can people actually go and see this preview tested up? >>There is an actual demo in the Venetian. I can't remember. Sorry, I can't remember the room. I think it's on the Yes, actually, it's on the floor on the third floor where the meeting rooms are on outside 35 or one. If anyone wants to go, we're >>going to start buying lunch time. >>Yes. Yeah, you can see it in action. And, you know, you could You could see a future where everything, You know, you look around. There's thousands of devices here. You could power all of these devices with a single cell and, you know, really scaled throughput >>in the five G. Just curious, um on the range is better than wifi >>ranges. Better outdoors, >>obviously, or factories. What's the throughput on the >>depending on the spectrum that you choose? And that's actually a really good save way. The device, the service that we built, its spectrum agnostic so it can be used on right now. We're using it on what we call C BRS spectrum, which is the free for all you can. You know, you can you can use it yourself. But also, customers can bring their own spectrum. And we're working with a batch of, uh, CSP operators to build advanced bundles where you can work this on licence spectrum. So if you're going up the spectrum in what they called millimetre wave >>spectrum owner to bring your own licence, >>you could So telco right? You could be a telco, bring your, you know, and work with us as a partner or some actually, actually, manufacturing customers have purchased rights to small spectrum bands so they can use those in combination with this service to deploy. So to your original question, as you're going back up the spectrum, you can drive more and more throughput. You it's not. It's not unheard of to drive one gig. You know what's so >>The low hanging fruit is the the use cases that have critical need for edge connectivity manufacturing? Um, certainly the retail or whatever that they help do the deployment >>we can. We can. We can see this being applicable because because you can start super small. You can see this being applicable even to branch offices, right? Like, uh, let's say I was talking to a customer yesterday. They were thinking or have all these branch offices. I don't even I don't even want to have I thought either he just wants something that's very quickly and easily. You know, I can manage centrally and it just connects. >>Can I should have fixed wireless shot to the wavelength order to have back all with wire >>too. Oh, they actually we are planning to. You know, I talked about where the smarts of the network live in the they can live in a region, they can live in the locals, and they can live in a wave election. So we're combining more and more of these products as well. And it's computing, obviously, is a is an obvious thing that, you know, we should be working on >>incredible work, George, that you and the team have done transforming industries. And I don't know if a feeling there might be a cube to Is it? Would it be too dot >>Oh, John, >>he's ready. Big George, Thank you so much for joining joining me today. It's great >>to be here. Thanks for having that >>for John Ferrier. I'm Lisa Martin. You're watching the Cube, the global leader in live coverage. Mhm

>>Mhm. Hey, everyone, welcome back to the cubes. Continuous coverage of AWS Re Invent 2021. Live from Las Vegas. Lisa Martin with John Ferrier We have to live sets to remote studios over 100 guests on the Cube at this year's show and we're really excited to get to the next decade in cloud innovation and welcome from the keynote stage. Mark Ruin the Chief Network Officer Andy VPs Dish Network Mark, Welcome to the Cube. >>Thank you. >>Enjoyed your keynote this morning. So big news coming from AWS and dish you guys announced in the spring telecom industry First dish in AWS have formed a strategic collaboration to reinvent, reinvent five G connectivity and innovation. Let's let's really kind of dig into the AWS dish partnership. >>Yeah, you know, we're putting our network in the cloud, which allows us to have a different speed of innovation and a much more corroborative way of bringing new technology. And then we have access to all the developer ecosystem of AWS. So that's but as you say, it's a world first to put the telco in the cloud. >>And so the first time the five g network is going to be in the cloud, and it was also announced I'm curious, uh, that Las Vegas is going to be the first city live here. We are sitting in Las Vegas. What's the any status you can give us on >>that? So we're building across the US and Las Vegas is a place that we've built and we better testing. So that's where we have all run and we're testing all sorts of traffic and capability with our people and partners live here at the same time that we have the reinvent and, uh, Bianco around. We're also starting to test new capabilities like orchestration, slicing things that we've never seen any industry. So that's pretty exciting, I >>have to ask you. In the telecom industry, there has been an inflexion point around cloud and cloud Impact Ran is opening up new opportunities. What is the telecom industry getting and missing at the same time? Because it seems to be two schools of thought cloud pro cloud ran and then hold onto the old way. >>I think everybody would like to go to Iran and the cloud, but it's not as easy if you have a big installed base. So for us. You know, we all knew it. It's easy so we can adopt the best technology and the newest. But of course, if you have a big instal base, there is going to be a transformation, if you wish. So you know, people are starting trying to set the expectation of how much time it will take. But for us, you know we are. We're moving ahead because we're building a completely new network. >>It's a lot easier than well, it's a relative term. It's >>really much more fun. And we can We don't have to make compromises, right? So but it's still a lot of work, you know, we're discovering we're learning a lot of things. We're partners. >>What if you have a clean sheet of paper or Greenfield? What's the playbook to roll this out across the campus for a large geographic area? >>Yeah, so pretty much You have the same capability in terms of coverage and capabilities than anybody else, but we can do it in an automated manner. We can do it with much thinner and efficient hardware, pretty much hardware with a few accelerators, so a bit of jargon. But, you know, we just have access to a larger ecosystem and much more silicon and all the good things that are coming with the cloud >>talk to us about some of the unique challenges of five G that make running it in the cloud so much more helpful. And then also, why did you decide to partner with AWS? Clearly you have choice, but I'd love to know the backstory on that. >>Yeah, I've been in the telco industry forever, and I've always seen that our speed of innovation was to slow. The telco is very good at reliability. You know, your phone always works. Um, it's very reliable. You can have massive traffic, but the speed of innovation is not fast enough. And the the applications that are coming on the clouds are much faster. So what we wanted to marry is the reliability of the telco and and all the knowledge that exists with the speed of the cloud. And that's what we're doing with bringing their ecosystem into our ecosystem to get the best of two worlds. >>Lots of transformation in the vertical industries. We heard from Adam today on stage vertical with ai machine learning. How does that apply in the telco world because it's an edge you got. See, sports stadiums, for instance. You're seeing all kinds of home impact. How is vertical specialisation? >>Yeah. So what is unique about the cloud is that you can observe a lot of things, you know, in the cloud you have access to data, so you see what's happening, and then you use a lot of algorithms. We call it Machine Learning Analytics to make decisions. Now, for us, it means if you're a stadium, you're going to have a much better visibility of what's happening. Where is the traffic? You know, people moving in and moving out? Are they going to buy some food awards? So you see the traffic and you can adapt the way you steal the traffic the way you distribute video, the way you distribute entertainment to how people are moving because you can observe what is happening in the network, which you can't do in a classic or legacy five g network. So once you observe, you can have plenty of ideas, right? And you can start innovation again, mix a lot of things and offer new services. >>In this last 22 months, when we saw this rapid pivot to work from home. And now it's work from anywhere, right? We talk about hybrid cloud hybrid events here, but this hybrid work environment talk to me about the impact that that decision A W s are going to have on all of those companies and people who are going to be remote and working from the edge for maybe permanently. >>Yes, you say, You know what is important is that people want to have access to the to the cloud to the services, the enterprise from wherever they are. So as a software architect, I need to make sure that we can follow them and offer that service from wherever they are in a similar manner today. If you're making a phone call, you don't have to think if you're connecting to the Web, you know, through WiFi through this and that, you have to think we want to make it as simple as making a phone call. In the past, where you always connected, you always secured. You always have access to your data. So that's really the ambition we have. And, of course, with the new remote abbots, the video conferencing that's the perfect time to come with a new offer. >>And the Strand also is moving towards policy based. You mentioned understanding video and patterns. Having that differentiated services capability in real time is a big deal. >>Yeah, that's a big deal. Actually, what enterprise want? They want to manage their policy, so they want to decide what traffic gets, a premium access and what traffic can be put in the background. You want to update your computers? Maybe that's not a premium price for that. You can do it at any time, but you want to have real time, customer service and support. You want premium? And who am I to decide for an enterprise? Enterprises want to decide. So what we offer them is the tools to create their policy, and their policy will be a competitive advantage for them when they can different change. >>And this brings up another point. I want to ask you. You brought this up earlier about this. The ideas, the creativity that enables with cloud you mentioned ideas will come out. These are this is where the developers now can really encode. This is the whole theme of this Pathfinders keynote. You were up on stage. This is a real opportunity to add value. Doing all the heavy lifting in the top of the stack and enabling new use cases, new applications, new expectations. >>You know what I tell to my engineers? My dream as an engineer is to be, uh, developer friendly. I want people to come to us because it's fun to work in our environment and try things. And a lot of the ideas that developers will have won't work. But if they can spin it off very fast, they will move to that killer application of killer service very fast. So my job is to bring that to them so that it's very easy to consume and and trying to live And, you know, just like bringing >>candy to a baby here. >>Yeah, cause right And have fun and, uh, and discover it for yourself and decide for yourself. >>I gotta ask your questions in the Telecom for a while. We've been seeing on the Cube earlier in our intro keynote analysis that we're now living in an era with SAS applications. No more shelf where now, with purpose built applications that you're seeing now and horizontally scalable, vertically integrated machine learning. You can't hide the ball anymore around what's working. You can't put a project out there and say no, you can't justify. You can't put you can put lipstick on that. You can't know you're seeing on >>that bad cake. Yeah, it's all the point of beta testing and market adoption. You try, you put it there. It works. You say the brake doesn't work. You try again, right? That's the way it works. And and in Telco, you're right. We were cooking for a year or two years, Three years and saying, Oh, you know what? That's what you need. It doesn't work like this faster now. Yeah, Yeah. And people want to be able to influence and they want to say, I like it. I don't like it. And the market is deciding. >>Speaking of influence, one of the things we know we talk a lot about with A W S and their guests is their customer. First customer obsession focused. You know, the whole reason we're here is that is to serve the customer, talk to me about how customers and joint customers are influencing some of the design choices that you guys are making as you're bringing five due to the cloud. >>So what is important for us? We have to dreams, right? The first one is for consumers. We want consumers to have access to the network so that they feel that they are VIP and often I know you and I, sometimes when we're connected to the network with tropical, we don't get the feeling where a V i p So that's something that's a journey for us to make people feel like they get the service and the network is following them and caring about them for the enterprises. You want to let them decide what they want. You were talking about policy building. They want to come with their own rating engine. They want to come with their own geographical maps. Like here. I have traffic here. I don't need coverage. So we want to open up so that the enterprise decide how they invest, how they spend the money on the network >>giving control back to the end user. Whether that's a consumer or enterprise, >>absolutely giving control to the end user and the enterprises. And we're there to support and accelerate the service for them. >>Mark, I want to ask you about leadership. You mentioned all these new things. Are there your dreams? And it's happening Giving engineers the canvas to paint their own future. It's gonna be fun is fun as you're affecting that change. What can people do as leaders to create that momentum to bring the whole organisation along is their tricks of the trade. Is their best practises >>Absolutely their best practises? Um, we were very much following develops where, you know, as a leader, you don't know, you're just learning and you're exposing and you're sharing. Uh, we're also creating an open world where we're asking all our partners to be open. Sometimes, you know, they feel like a bit challenge. Like, do I want to show what I'm doing? And I would say, Yeah, sure, because you're benefiting between each other. Um, And then you want to give tools to your engineers and your marketers to be fast speed, speed, speed, speed so that they can just play and learn. And at the end of the day, you said it. It's all about fun. You know, if it's fun, it's easy to do >>that. We're having fun here. >>That is true. We always have fun here. Last question for you is talk about some of the things that AWS announced this morning. Lots of stuff going on in Adam's keynote. What excites you about this continued partnership between AWS and Dish? >>Yeah, we were. We were surprised and so happy about AWS answer to when we came in with the first one to come big time in the telco and the Cloud was not ready. To be honest, it was Enterprise and Data Club and AWS. When is going all the way, we've asked to transform their cloud to make it a telco frantic, loud. So we have a lot of discussions about networking, routing, service level agreements and a lot of things that are very technical. And there are a true partner innovating with us. We have a road map with ideas and that's pretty unique. So, great partner, >>I was going to say it sounds like a really true >>trust and partnership. We're sharing ideas and challenging each other all the time, so that's really great. >>Awesome and users benefit consumers Benefit enterprises benefit Mark Thank you for joining Joining me on the programme today. Georgia Keynote enjoyed hearing more about dish and AWS. And what are you doing to power? The future. We appreciate your time. >>Thank you. Thank you >>for John Ferrier. I'm Lisa Martin. You're watching the Cube? The global leader in tech coverage, So mhm. Yeah.

>>Yeah. Welcome back to a W s reinvent 20 twenty-one. This is the live. In addition, the last year, of course, it was virtual. This is probably the most important hybrid event of the year. Over 20,000 people. We have two sets here at the Cube. My name is David. I'm really excited to have Caroline see more on the vice president of product marketing at Serato, which is now an H p e company. And Daniel, who is the director of worldwide partner Essays at A W s. Folks, welcome to the good to see you. >>Yeah, great to be here. So, >>Caroline, you got some news. Why don't we start their hard news? We always like to start with that. >>First of all, I think I just like to talk a little bit about the acquisition because it has been acquired by H. P. And in September, we announced, um, disaster recovery as a service is part of the Green Lake platform. And so that's really exciting. Both from, uh, customers as well is also H B customers. But the innovation continues here at a W s reinvent, we are announcing a new solution 02 in cloud, which is a disaster recovery for Amazon. Easy to, um, and if I think about the value that it brings to the customers, it's delivering orchestrated disaster. Recovery is delivering that simplicity at scale and scale is very important aspect because it will deliver that from tends to thousands of work clothes and as well, it's helping organizations to drive more operational efficiencies around their processes. So that's sort of a nutshell of the news. The cloud for a W s >>great. Thank you for that. So I wanna ask you, obviously, in lock down, people look to the cloud. Uh, and you know, data protection used to be just back up, and then people realize that recovery is important, but it used to be a bolt on an afterthought. You sort of launch the application of the service. And so we got to protect this thing and whatever and throw it on there that that's unacceptable. Today, if you're not going to run your digital business with a bolt on, So what? Our customers telling you in terms of what they want to see from their data protection portfolios and how are you seeing the ecosystem and a W s helping them to integrate that >>absolutely well to your point, the pandemic has absolutely accelerated a lot of businesses movement into the cloud. So companies that hadn't formerly thought about using cloud technologies are now doing that. And for them, in order to have a very simple and easy and scalable data protection solution, is critical for them to feel comfortable into moving into a W s. And so that's what we're seeing from a lot of customers. Um, and of course, back to your point about recovery with the challenges around ransomware, Um, that is definitely an area where a lot of companies have just done their back up. But they're also testing it and making sure that it's something that they know that they can rely on, um, as they moved there, workloads into the club. >>And speaking of ransomware, I mean, it's just front and center. Anybody can be a ransomware. Today they go in the dark web by ransomware service. They put a stick into a server and then bad things happen. Hopefully that that individual ends up in handcuffs, but not always so when we've seen Ransom's getting paid $40 million ransom's multi-million dollar. And we all know about the fact that our front and center So what are you seeing in terms of the customer base? How How h b n z two helping and where does a W s fit? Maybe you could start off Caroline. >>Great question, because I think from the perspective, we look at it from the need for recovery. Uh, strategy as part of your overarching, um, security and prevention is is one aspect that you always need two prevention. But to us, it's a matter of not if you're going to be attacked. It's when and when that gets through your firewall. And so you need to be able to have a recovery strategy in place that allows you to recover in minutes to set to within seconds of when that when an attack actually happens. And, um, I can give a case in, for example, for there's a company 10 Carter Protective fabric, textiles manufacturing company, MULTI-MILLION business. And they suffered to to a tax crypto attack first time, and they were using more traditional, um, back up to take. And it took him two weeks to recover having been attacked, and they suffered significant data loss, and then they deployed photo photo. Um, unfortunately, a little while later, they were attacked a second time with more sophisticated case of So it continues. Um, but this time the recovery was very different. What happened was that they were able to recover within minutes and they had seconds of data loss. And that is because of r c d p technology C D. P. Being continuous data protection. And that is with our replication and a unique journaling capability that allows you to, uh, set up the different checkpoint. So you have thousands of recovery points and you can recover to a specific recovery point with within seconds of that attack. Very, very powerful. >>I wanna ask you a question and what Caroline was just talking about with the classic metrics in this business r P O R T r P o recovery point objective. Always say, how much data do you want to lose? And people say none. Okay, how much? What kind of budget do you have? So that's always been the trade-off, although, as you mentioned, it's getting a little bit more cost-effective and then recovery time objective. How long does it take you to get back up. Absolutely. So so. Those are some of the concepts that you were talking about. I wanna ask you, Daniel, it feels like an Caroline. You feel like data protection is now becoming. It's certainly a tight adjacent to overall security. It's not security per se sick of it, so but it's but it's becoming. The lines are blurring. How do you see that you have a shared responsibility model? Where does this whole topic fit in? >>Well, I think lots of companies are really finding a lot of value in their data, right. Whereas, you know, perhaps years ago it was less. It was easy to hang on to it, to actually make it valuable to do metrics and analytics on it to do machine learning, perhaps on it. And so, by having, um, products such as the product, you know, they're now able to hang on to that data and make sure that they have it in perpetuity so that they can do what they need to do on it. So, yes, we're seeing, you know, companies that were traditionally storage cos thinking about security, security cos thinking about data, so yes, all of those lines are being blurred for sure. And I think that, you know, as far as the short security model we think of the you know, we think of our partners and ourselves, obviously as extensions. And we're really looking to have the best customer experience that we can >>can I think every company security company, Obviously you impact enterprise care a lot about security A W s. I don't know any company because I don't really care about security. That's that's not my swim land out of business. If you If you had that attitude now. So from from your standpoint, where does it fit inside of you know, you're you're thinking, How are you guys thinking about security and data protection? Back up and recovery? Is it all just coming together or they still kind of separate entities? >>No, you're absolutely right. It is coming together, and what we're seeing is we're having a lot more conversations with ISO's, um so the more the security offices of organizations and I think what's happening is that's where the budget is to. And so you're saying they're sort of the working together on the I T and also the Office of Security to um so we're having more conversations there, and we see that, as I mentioned before, the recovery strategy is a key element of our focus. And what we can do is part of the overarching strategy of an organization. >>So what? How should we think about the cloud? Is it another layer of protection? Um, is it a replacement for tape? Maybe not, but we need as much protection as possible. So how should we think about the cloud in the context of data protection? >>Well, the cloud, Yeah, absolutely. Um can provide an alternative to tape or, um disc, for example, of this year. We also added support for a mutability preserved for A W S. With so we are ensuring in the fact that you know you can be changed so that that's absolutely critical. >>So that's a a right once read only technology. That's a service that you tap. So your integrating zero was integrating with that capability. So that's another layer of protection. That's another layer of protection. And then, of course, you know there's there's gaps, is another part of the strategy. So let's talk strategy for a minute. What's the I know it's not one size fits all, but what are you seeing as best practice strategies for customers to protect themselves against traditional just human error? Cyber attacks? What's the what's the sort of prevailing approach? How should we think about that? >>Well, I mean, you're absolutely right. Those the, you know, the filed elections, the database corruptions, and so our solutions, that is, our continuous data protection. It absolutely is, um, the ability to be able to get that granular level of recovery, which you can do with backups. I'm not saying that backup isn't part of your overall strategy, but if you're actually trying to recover quickly and within seconds to whether it's an attack to whether it's a file deleted, a database corruption, you need that continuous data protection. And that's something that you need to us that we've been delivering since the day that um was formed. So >>that's your secret sauce is it is a very granular ability to dial down based on your r p o. That's requirements based on the application requirements, uh, and then bring in the cloud for things like mutability. Maybe gapping. Maybe Last resort is still the last resort. I don't know. Maybe >>there. So, um, you know, a w s to be a target for disaster recovery. So all back up. >>You talk about that? >>Yeah. So, with what we have enabled is first of all, if you want to, um, my great, your work clothes to a W s. And we're seeing an awful lot of that. We provide that capability. So the mobility aspect, if you are looking at instead of an on premises disaster recovery site, you can use a W S D R site. Um, And if you want to back up to a W s and use, um, cost efficient storage, we support that with cloud tearing and mutability. And as I say today, we're announcing cloud for a W s, which is once you've got your work clothes in a W s. We can protect them now in, um, in a W s itself. So the full spectrum. And then earlier this year, we announced for communities for US work clothes, So we're really trying to ensure that we can protect any A W s workload wherever it is. >>So I look around here pretty impressive given that we're in the second year of a pandemic here, pretty packed floor. But the ecosystem is just exploding. That's gonna make you feel good. Cos like choosing to partner with a W s leaning in writing to your cloud-native fooling. Maybe give us the update on how you see this partnership. >>Well, I mean, just to Caroline's earlier point, you can see how Xero is continuing to innovate, right? And that's really key. So, um, having a cloud-native solution and then also having a solution that works for us. We're seeing a lot of companies thinking about containers thinking about server lists. And so, you know, the best partnerships that we have are the ones in which they're innovating with us continuously. And I've known about since I started in 2014. So they've been around for a long time, and they're continuing, um, to do that. And they are working closely with us to do P O. C. D. S. And and to help our customers really get what they need, um, in the data protection space and continuing to innovate, which is >>your customers, they want that they need that your your deep into data protection. Yes. You're scale of cloud But you're not going to have the the capabilities of Stack. So that one plus one hopefully is greater than to How do you where can we find out more information about you know, the new solutions? What's the what's the call to >>action culture as well? A couple of things. We've, uh we just We just launched deserted for a W s hands-on lab. And what that does is allow in your own time in your own environment to be able to try with a W S as a target and back up. Um, so we've just launched that and that enables you to see how it works with a W S. We also have for communities, um, lab as well, so you can see how it works with a K s. Uh, coming soon, we're going to have to in cloud lab that you can actually see how to protect your workload in the cloud in a W s. So those are the really the best ways to be able to Well, for a call to action is try. The lab really is >>awesome. Guys, thanks so much for coming to the Cube. Very important topic and keep up the good work. >>Thank you. Thank you. Very well. So >>we're seeing the evolution of data protection rethinking data protection in 2020. No longer is it a Bolton cloud modernization with deep stacks. Fine granularity for your r p o. But also quick recovery protection from Ransomware. It's a whole new world, and we're here to cover it. My name is David. You're watching the Cube, the leader in high tech coverage. We'll be right back. Yeah, Yeah, yeah. Mm, yeah.

>>Mm. Welcome back to the cubes. Continuous coverage of A W s reinvent 2021 were running one of the industry's most important and largest hybrid tech events of the year with A W S and its ecosystem partners. And, of course, special thanks to a M D for supporting this year's editorial coverage at the event we got to live sets we had to remote sets one in Boston, one in Palo Alto. We've got more than 100 guests coming on the programme and we're looking >>deep into >>the next decade of cloud innovation. We're super excited to be joined by Ali Zafar, who is the senior director of platform strategy and operations at Dropbox Ali. Great to see you. Thanks for coming on. >>Awesome. It's a pleasure to be here with you, Dave. >>So Hey, what's your day job like at Dropbox? What's your role? >>Got it? Yeah. So I actually oversee the global supply chain at Dropbox. Also all of the capacity planning which entails both our budget and also capacity requirements and Dropbox. And then I also focus on the platform product management side which is basically building our build vs buy and our overall roadmap for our platform in the long run. >>Great. Thank you. So I mean, everybody knows Dropbox, But maybe you can talk a little bit about your business, your mission and how that's evolved. Over the past several years. >>Dropbox is a global collaboration platform, and our mission at Dropbox is to help design a more enlightened way of working. Dropbox has over 700 million registered users and over 550 billion pieces of content. So taking a step back, they've dropbox health. Let's use all of your content. Think of this as videos as music. Even your tax returns allows you to organise all of this content. And then you can share this content with anybody at any time. You can also take Dropbox to work. And actually, it makes you even more productive in the workplace integrating all of your tools seamlessly, also allowing you to collaborate with all of your teams internally and also externally. >>Yeah, so thank you. Uh, when Dropbox was founded, I mean, the cloud was really nascent, right? So it was early days, and so a lot has changed since you know, the mid last decade. And of course, with remote work and hybrid work that had to be a real tailwind to your business. But maybe you could explain your cloud and your hybrid cloud strategy. >>You're spot on Dave. So Dropbox has always been hybrid since its inception in 2000 and seven. And when I say hybrid, I mean, we have our own on prime infrastructure, and then we also leverage Public Cloud. Now, Public cloud still to these days remains absolutely critical for Dropbox to serve all of its customer needs. And when we talk about the decision between public or private, we think about three or four key things. One is the total cost of ownership. Look at the market. We also look at our customer requirements and the latest technology that's available in the market and then any international data storage requirements to make the decision of going towards public or private for that specific use case. >>So what if we could follow up on that? Like maybe you can talk about the key business, these conditions as a as a SAS storage provider? What are the real drivers in in your business framework? >>Got it at the end of the day, what really matters for us. There is to actually think about our customers and delight them And what better than to focus on performance, reliability and also security. Right. So we want to make sure that the infrastructure that we have today allows Dropbox to actually solve for the specific use case for our customers. What do they care about while also doing this in a very efficient management Manage, uh, way So to summarise that looking at performance, looking at liability, looking at scalability, looking at efficiency and then also compliance >>So that leads me to My next question is about the EC two instances that you use. I know you. You make heavy use of AMG compute. How >>did you >>come to that decision? Was that these factors was all performance. How did you migrate to really enable that capability? How complex was that? >>MD has has been a key strategic partners the partnership as well over 4 to 5 years right now and we've been leveraging them on our on prem infrastructure for compute. So we've always had aimed in our infrastructure. And when the time came where aws was also leveraging some of the MD instances, we wanted to see how we can expand the partnership with AMG and A W S and also experiment with these instances. So we looked at some of the tooling updates that were required. We also looked at specific instances which are either compute optimised and memory optimised instances. And then we actually build our footprint on M D. And what we saw is that the overall performance improvements and also cost improvements that we got for specific workloads. It was actually extremely, uh, overall awesome results for Dropbox and our customers, and we have been using them ever since. >>What kind of business impact did that make that make a difference to your business? That was noticeable >>on the business side, I think primarily it was more on the TCO side, which is where we got most of the benefits on the cost side. Um, and then also for some of our internal work clothes, we also saw benefit, uh, to our internal developers that are using some of those work clothes. >>Well, so you guys have kind of become the poster child for hybrid. A lot has been talked about about you all, but I wonder if you could help us understand what part of your infrastructure is going to be better served by public cloud versus kind of doing your own. I t on Prem. What are some of the value drivers that are that are making, you know, push workloads into the public cloud? Help us understand that better and squint through that >>got ready. I get asked that question a lot. So public cloud in general allows for faster go to market, Think about this as, like product launches teacher launches also international expansion. It allows us to scale and then also leveraging some of the existing technologies out there in the market for some of the common workloads. So just, you know, taking a step back and thinking about Dropbox. We keep on evaluating also the criteria and then also specific workloads on what makes sense on private or public load. And a W s had some instances, like as three rds and EC to that when we started looking at, we knew that some of our key services, like data platform, some parts of our, um, Melania and even paper platform would make more sense for us to actually leverage. Uh, some of these in public cloud for that. >>So what are the sort of characteristics of the workload that are sort of better suited to be in AWS? You know, what's the ideal workload profile? You know, we talk about ideal customer profile. What's the ideal workload profile for the for the AWS Cloud. >>Got it. So the way we think about it, at least we call it the rule of three at Dropbox. Um, and that means we look at scale. First, we look at technology and innovation. Um, and what I mean by that is, is there faster innovation in the public cloud? And is the workload common enough that there's already a lot of work going on in public Cloud? Then there's no reason for us to actually innovate faster than that. We probably can't. And if the scale is not large enough, right? So when we talk about our storage side like magic pocket, the scale is large enough. We're innovating. There makes sense, and it's better for the end customer, so we will probably go towards private cloud there. But then, when we talk about like international expansion, when we talk about, like, faster go to market or some of the innovation in the space. It really makes sense to use public Cloud because of all of the advancements that we've seen there. >>Yeah, so let me circle back to the sort of business benefits and impact of the sort of a MD based compute specifically. But you talked about TCO before. So there's certain things you mentioned on Prem you sometimes use You mean right. If the thing is hardened, you don't want to necessarily rip and replace it. But if you can accelerate, go to market and you spin up things in the cloud that makes sense. You mentioned customer requirements. So that's just kind of depends. And then the international expansion and scale. So it kind of comes down to those whatever. Four or five factors, right? Tco those other factors that I mentioned kind of the high level benefits, if you could, wouldn't mind summarising for us. Ali. >>Yeah, I think you're spot on there. So it's looking at the overall Decio, right? The cost of serving the overall cloud looking at like go to market in general, like can we leverage public cloud and go to market faster? Obviously, meeting that end customer requirements. We also looked at like international expansion, like any of the customer's data that is stored outside of the US is all on public load for Dropbox. Uh, no plans in the short term to do something different there, Um and then also just looking at, like I mentioned anything in the technology space that is ongoing, that we can leverage features side or the product side for our customers, like at Yale or, uh, VRML. We are going to leverage Public cloud there. >>So of course you know we've we've followed the progression of semiconductor technology for decades. This industry has marched to the cadence of performance improvements. What are the one of the futures hold from a technology roadmap standpoint, particularly as it relates to leveraging AMG EC Two instances, Ali >>got it. So drop boxes in a very unique position where we actually leverage AMG both on Prem and for public le leveraging some of the AWS EC two instances like like you mentioned and epic processors from MDR what we're using today, both on the hybrid infrastructure site and the performance and also the d. C o benefits are real and something that we are observing on a day to day basis. So we are gonna be leveraging that technology even in the future. Um, and the partnership with the MD continues to be very, very strong for Dropbox. >>Well, I really, really appreciate you coming on the cube as part of our coverage is great to have You love to have you back sometime. >>Awesome. Thank you. And also just last thing we wanted to also call out that we are also going to be experimenting with probably Milan that is coming out. Uh, room is the current process is from a m D. That we have been leveraging. And as Milan comes available, we do wanna continue to evaluate it and see how we can fit it in our infrastructure. >>Okay, So their their generations are city based, the all Italian city based. They were going to run out of cities soon. >>God, uh, again, the partnership with both A W s and an M. D is something that I'm very proud of. Execution. Thank you, Dave. >>Great to have you, Ali. And really appreciate you watching. Keep it right there for more action on the cube. Your leader in hybrid tech event coverage. Mhm.

>>Mhm. Mhm. >>We're here with the Cube covering Calm Vault Connections 21. We're gonna look at the data protection space and how cloud computing has advanced the way we think about backup recovery and protecting our most critical data. Ranga Rajagopalan, who is the vice president of products at Con vault and Stephen Orban, who's the General manager of AWS marketplace and control services gents. Welcome to the cube. Good to see you. >>Thank you. Always A pleasure to see you here >>steve. Thanks for having us. Very >>welcome, Stephen, let's start with you. Look the cloud has become a staple of digital infrastructure. I don't know where we'd be right now without being able to access enterprise services I. T. Services remotely. Um But specifically how our customers looking at backup and recovery in the cloud, is it a kind of a replacement for existing strategies? Is it another layer of protection? How are they thinking about that? >>Yeah. Great question. David again, thank thanks for having me. And I think you know, look if you look back to 15 years ago when the founders of AWS had the hypothesis that many enterprises governments and developers we're gonna want access to on demand pay as you go I. T. Resources in the cloud. Uh None of us would have been able to predict that it would have Matured and um you know become the staple that it has today over the last 15 years. But the reality is that a lot of these enterprise customers, many of whom have been doing their own IT infrastructure for the last 10, 20 or multiple decades do have to kind of figure out how they deal with the change management of moving to the cloud. And while a lot of our customers um will initially come to us because they're looking to save money or costs, almost all of them decided to stay and go big because of the speed at which they are able to innovate on behalf of their customers and when it comes to storage and backup, that just plays right into where they're headed. And there's a variety of different techniques that customers use, whether it be, you know, a lift and shift for a particular set of applications or a data center where they do very much. Look at how can they replace the backup and recovery that they have on premises in the cloud using solutions like, but we're partnering with console to do or completely reimagining their architecture for net new developments that they can really move quickly for their customers. Um and and completely developing something brand new, where it is really a, you know, a brand new replacement and innovation for for for what they've done in the past. >>Great, thank you, Stephen Rachael, I want to ask you about the d were digital. Look, if you're not a digital business today, you're basically out of business. So, my question to you is how have you seen customers change the way they think about data protection during what I call the forced March to digital over the last 18, 19 months or customers, you know, thinking about data protection differently today >>definitely Dave and and thank you for having me and steven. Pleasure to join you on this cube interview first going back to stevens comments can't agree more. Almost every business that we talked with today has a cloud first strategy, a cloud transformation mandate and you know, the reality is back to your digital comment. There are many different paths to the hybrid multi cloud and different customers. You know, there are different parts of the journey. So I still was saying most often customers at least in the data protection perspective start the conversation by thinking here have all these tips. Can I start using cloud as my air gap long term retention target and before they realized they start moving their workloads into the cloud and none of the backup and record yesterday's are going to change. So you need to continue protecting the clothes, which is where the cloud native data protection comes in and then they start innovating around er, can I use cloud as media sites so that you know, I don't need to meet in the other side. So this year is all around us. Cloud transformation is all around us and and the real essence of this partnership between AWS and calm vault is essentially to dr and simplify all the paths to the club regardless of whether you're going to use it as a storage started or you know, your production data center, all your dear disaster recovery site. >>Yeah, it really is about providing that optionality for customers. I talked to a lot of customers and said, hey, our business resilience strategy was really too focused on D. R. I've talked to all the customers at the other end of the spectrum said we don't even have a D. R. Strategy now, we're using the cloud for that. So it's really all over the map and you want that optionality. So steven and then go ahead. >>Please, ransomware plays a big role in many of these considerations that greatly. It's unfortunately not a question of whether you're going to be hit by ransomware, it's almost we can like, what do you do when you're hit by ransomware and the ability to use the clothes scaled immediately, bring up the resources, use the cloud backups has become a very popular choice simply because of the speed with which you can bring the business back to normal our patients. The agility and the power that cloud brings to the table. >>Yeah, ransomware is scary. You don't, you don't even need a high school diploma to be a ransomware ist you can just go on the dark web and by ransomware as a service and do bad things and hopefully you'll end up in jail. Uh Stephen we know about the success of the AWS marketplace, uh you guys are partnering here. I'm interested in how that partnership, you know, kind of where it started and how it's evolving. >>Yeah, happy to highlight on that. So, look when >>we when we started >>Aws or when the founders of aws started aws, as I said 15 years ago we we realized very early on that while we were going to be able to provide a number of tools for customers to have on demand access to compute storage, networking databases that many, particularly enterprise and government government customers still use a wide range of tools and solutions from hundreds, if not in some cases thousands of different partners. I mean I talked to enterprises who literally use thousands of of different vendors to help them deliver their solutions for their customers. So almost 10 years ago, we're almost at our 10 year anniversary for AWS marketplace, we launched the first substantiation of AWS marketplace which allowed builders and customers to find try buy and then deploy third party software solutions running on amazon machine instances also noticed as armies natively right in their AWS and cloud accounts to complement what they were doing in the cloud. And over the last nearly 10 years we've evolved quite a bit to the point where we support software and multiple different packaging types, whether it be amazon machine instances, containers, machine learning models and of course SAS and the rise of software as a service. So customers don't have to manage the software themselves. But we also support data products through the AWS Data exchange and professional services for customers who want to get services to help them integrate the software into their environments. And we now do that across a wide range of procurement options. So what used to be pay as you go amazon machine instances now includes multiple different ways to contract directly, customer can do that directly with the vendor with their channel partner or using kind of our public e commerce capabilities. And we're super excited, um, over the last couple of months we've been partnering with calm vault to get their industry leading backup and recovery solutions listed on AWS marketplace, which is available for our collective customers now. So not only do they have access to convulse awesome solutions to help them protect against ransomware as we talked about and to manage their backup and recovery environments, but they can find and deploy that directly in one click right into their AWS accounts and consolidate their building relationship right on the AWS and voice. And it's been awesome to work with with Rhonda and the product teams and convo to really, um, expose those capabilities where converts using a lot of different AWS services to provide a really great native experience for our collective customers as they migrate to the cloud. >>Yeah, the marketplace has been amazing. We've watched it evolve over the past decade and, and, and it's a, it's a key characteristic of everybody has a cloud today. We're a cloud to butt marketplaces unique uh, in that it's the power of the ecosystem versus the resources of one and Ringo. I wonder from, from your perspective, if you could talk about the partnership with AWS from your view and then specifically you've got some hard news, I wonder if you could talk about that as well. >>Absolute. So the partnership has been extended for more than 12 years. Right. So aws and Commonwealth have been bringing together solutions that help customers solve the data management challenges and everything that we've been doing has been driven by the customer demand that we seek. Right customers are moving their workloads in the cloud. They're finding new ways of deploying their workloads and protecting them. Um, you know, earlier we introduced cloud native integration with the EBS API which has driven almost 70% performance improvements in backup and restores. And when you look at huge customers like coca cola who have standardized on AWS um, combo. That is the scale that they want to operate in. You manage around 1 50,000 snapshots 1200 ec, two instances across six regions. But with just one resource dedicated for the data management strategy. Right? So that's where the real built in integration comes into play and we've been extending it to make use of the cloud efficiencies like our management and auto scale and so on. Another aspect is our commitment to a radically simple customer experience and that's, you know, I'm sure Stephen would agree it's a big month for at AWS as well. That's really together with the customer demand which brought us together to introduce com ball into the AWS marketplace exactly the way Stephen described it. Now the heart announcement is coming back up and recovery is available in native this marketplace. So the exact four steps that Stephen mentioned, find, try buy and deploy everything simplified through the marketplace So that our aws customers can start using far more back of software in less than 20 minutes. A 60 year trial version is included in the product through marketplace and you know, it's a single click buy, we use the cloud formation templates to deploy. So it becomes a super simple approach to protect the AWS workloads and we protect a lot of them. Starting from easy to rds dynamodb document DB um, you know, the containers, the list just keeps going on. So it becomes a very natural extension for our customers to make it super simple to start using convert data protection for the w >>well the con vault stack is very robust. You have extremely mature stack. I want, I'm curious as to how this sort of came about and it had to be customer driven. I'm sure where your customers saying, hey, we're moving to the cloud, we had a lot of workloads in the cloud, we're calm vault customer. That intersection between calm vault and AWS customers. So again, I presume this was customer driven. but maybe you can give us a little insight and add some color to that. >>Everything in this collaboration has been customer driven. We were earlier talking about the multiple paths to chlorine vapor example and still might probably add more color from his own experience at our jones. But I'll bring it to reference Parsons who's a civil engineering leader. They started with the cloud first mandate saying we need to start moving all our backups to the cloud but we have wanted that bad actors might find it easy to go and access the backups edible is um, Conwell came together with the security features and com well brought in its own authorization controls and now we have moved more than 14 petabytes of backup data into the club and it's so robust that not even the backup administrator and go and touch the backups without multiple levels of authorization. Right. So the customer needs, whether it is from a security perspective performance perspective or in this case from a simplicity perspective is really what is driving this. And and the need came exactly like that. There are many customers who have no standardized on it because they want to find everything through the AWS marketplace. They want to use their existing, you know, the AWS contracts and also bring data strategy as part of that so that that's the real um, driver behind this. Um, Stephen and I hope actually announced some of the customers that I actively started using it. You know, many notable customers have been behind this uh, innovation, don't even, I don't know, I wanted to add more to that. >>I would just, I would, I would just add Dave, you know, look if I look back before I joined a W S seven years ago, I was the C I O at dow jones and I was leading a a fairly big cloud migration there over a number of years. And one of the impetus is for us moving to the cloud in the first place was when Hurricane Sandy hit, we had a real disaster recovery scenario in one of our New Jersey data centers um, and we had to act pretty quickly convert was, was part of that solution. And I remember very clearly Even back then, back in 2013, they're being options available to help us accelerate are moved to the cloud and just to reiterate some of the stuff that Rhonda was talking about consoles, done a great job over the last more than a decade, taking features from things like EBS and S three and EC two and some of our networking capabilities and embedding them directly into their services so that customers are able to more quickly move their backup and recovery workloads to the cloud. So each and every one of those features was as a result of, I'm sure combo working backwards from their customer needs just as we do at >>AWS >>and we're super excited to take that to the next level to give customers the option to then also by that right on their AWS invoice on AWS marketplace. >>Yeah, I mean, we're gonna have to leave it there steven, you've mentioned several times the sort of the early days of back then we were talking about gigabytes and terabytes and now we're talking about petabytes and beyond. Guys. Thanks so much. I really appreciate your time and sharing the news with us. >>Dave. Thanks for having us. >>All right. Keep it right there more from combat connections. 21. You're watching the >>cube. Mm hmm.

>>Welcome to the Cubes Coverage of Splunk.com 2021. My name is Dave Atlanta and the Cube has been covering.com events since 2012 and I've personally hosted many of them. And since that time we've seen the evolution of Splunk as a company and also the maturation in the way customers analyzed, protect and secure their organizations, data and applications. But the forced march to digital over the past 19 months has brought more rapid changes to sec UP teams than we've ever seen before. The adversary is capable. They're motivated and they're deploying very sophisticated techniques that have pressured security pros like never before. And with me to talk about these challenges and how Splunk is helping customers respond as jane wang is the vice president of security products that Splunk jane. Great to have you on the cube. Thanks for coming on. >>Very nice to meet you. Thank you for having me. >>You're very welcome. So how d how can you think about or how do you think about the fact that the imperative to accelerate digital transformation has impacted security teams? How has it impacted sec ops teams in your view? >>Yeah. Well, just going back to our customers and what I've learned from all the customer conversations I have every every week many of our customers are under a massive digital transformation. They're moving to the cloud and the cloud opens up more attack surface, more attack work surface, there's more threats that come over cloud, new workspaces to attack services, new api is to manage secure and protect and our customers are really struggling to gain the visibility they need to really manage and secure across all that infrastructure. >>Yeah. And we've also seen the whole, obviously the work from home trend, the hybrid work movement, you know, people aren't set up for that. I mean, you remember people were ripping out literally ripping out desktops and bringing them home and you know, the home network had to be upgraded. So lots of changes there. And we've we've talked a lot in the cube jane about the fragmentation of tooling and the lack of qualified talent when we talked to see. So as you ask him, the number one problem, I can't get, I can't hire enough talent in the field of of cybersecurity. So I wonder if you can address how this has made it more difficult for security teams to maintain end to end visibility across their environments. What's the fundamental challenge there? >>Yeah, well you're really you're really nailing this. The fundamental challenges that many security products are not built to integrate seamlessly with one another. When I'm talking to customers, their frontline security operations teams often have 30 different consoles open on their monitor at one time and there really manual disjointed processes, the copying and pasting hash names and iP addresses from one consults the other. It slows them down. It really slows them down in protecting those threats. So because those products aren't assigned to integrate together and all that data from each of those security tools isn't brought into one place. It just exacerbates the challenge for security operations seems makes their job really, really hard to do. Which takes time. It takes time. It makes it harder to detect and respond to threats quickly and today more than ever we need to be able to detect and respond to threats quickly. >>Yeah, I do a weekly program called Breaking Analysis and once a quarter I look at the cyberspace and I use a chart to emphasize this complexity. It's it's a from a company called operative, I don't know if you've ever seen it but it's this eye chart, it's this taxonomy of the security landscape and it's mind blowing how much complexity there is. So how to Splunk help organization organizations address these challenges. >>Yeah, so I think bringing, we have one security operations platform cloud native cloud delivered. There are many parts of being able to streamline workflows for when you're first detect a threat or a potential threat right through to when teams close and immediate that threatened the changes in their environment to ensure they're protected. So the whole thing is helping security teams detects faster, investigate faster and respond faster to threat. There are four parts to that in our security operations, platform Splunk security cloud. The first one is advanced security analytics. So the nature of threats is evolving. They're becoming more sophisticated. We have very smart, well funded Attackers whose day job who spend all their time trying to break into organizations. So you need really advanced security analytics to detect those threats, then we need to automate security operations so that it's not so manual, so you don't have poor folks sitting in front of multiple consoles doing manual tasks to respond to those threats and make sure their organizations are protected. One key thing is that this year Splunk acquired true Star so that we can bring in d do rationalize multiple sources of threat intelligence and apply that threat intelligence both to our analytics and our operations so that you have broader insights from the security community outside Splunk and that intelligence can really help and speed both detection and response. And the last thing that's been true about Splunk since spunk became Splunk many many years ago is that we are committed to partners and we deeply integrate with many other security tools uh in a very seamless way. So whatever investments customers have made within their security operations center, we will integrate and bring together those tools in one workspace. So there's the big advantages I think you get when, when you run your security operations said transplant security cloud, >>that's a nice little description. And having followed Splint for so many years, it's sort of, it tracks the progression of your ascendancy. You know, you started you you we we used to have log analytics that were just impossible. You sort of made that much easier took that to advanced kind of use big data techniques even though Splunk really never used that term. But but you were like the leader and big data um in terms of being able to analyze um uh data to help remediate issues. The automation key is p pieces key the acquisitions. You've made a very interesting um you mentioned around de doop threat intelligence but also you've done some cool stuff in the cloud and we always used to say jane watch for the ecosystem. We early too early, you know, last decade we saw you as a really hot company. We said one of the keys to your growth is going to be the ecosystem. And you've you've clearly made some progress there. I wonder if you could tell us more About the announcements that you're making here at.com. >>Yeah. Well we're going back everything that we do on the security team, every line of code every engineer writes is all around helping detect, investigate and respond faster to really secure organizations. So if I look at those intern I start with faster time to detect what have we done. So bringing in the threat intelligence that I mentioned again, that's really gonna help to take new threats and to take them really, really quickly. You don't have to spend time going and looking manually at external sources of threat intelligence. It will be brought right in to enterprise security at your fingertips. So that that's pretty huge. We're bringing other more advanced content right into our stem enterprise security. So that will help detect threats that our research team sees as emerging again. This is going to just bring bring that intelligence right to customers where they work every day, um faster time to investigate. So this is this is really exciting uh back in november we reduced and we are really something called risk based alerting. That is an amazing new capability that we've iterated on ever since. And we have more iterations that we're announcing um tomorrow actually. And so risk based alerting pulls together what may have been single atomic alerts that can often be overwhelming to a sock brings those together into one overarching alert that helps you see the whole pattern of an attack, the whole series of things that happened over time. That might be an attack on your organization. One customer told us that that reduced the time it took for them to do an investigation from eight hours down to 10 minutes to really helping faster time to investigate. And then the next one is faster time to respond. So we have a new visual playbook editor for our sore security orchestration and response to which is in the cloud but also available on prayer. But that new visual playbook editor really reduces the need for custom code. Makes playbooks more modular, so it can help anyone in the security operations team respond to threats really, really quickly. So faster time to detect, investigate and respond those are, those are really cool for us. And then there's some exciting partnerships that I want to talk about just to really focus on reducing the burden of all those disparate tools on consoles and bringing them down and and integrating them together. So we'll have some announcements. There are new integrations that we're releasing with Mandiant Aziz scalar and detects. I'm personally very excited about a fireside chat that Kevin Mandia, the Ceo and president of Mandiant, we'll be having tomorrow with our Ceo Doug merit. So those are some of the things we're announcing. It's a big year for security. Very excited >>to tell you that's, that's key. I want to just kind of go through and follow up on some of the faster time to detect with the threat intelligence. That's so important because we read about how long it takes sometimes for for organizations to even find out that somebody has infiltrated their environment. This risk based learning, it sounds like and you're so right, it's like paper cuts having a bottoms up analysis. It's almost overwhelming. You don't have a sense as to really where the focus should be. So if you can have more of a top down, hey start here and sort of bucket ties things. It's gonna, it's gonna accelerate and then the faster response time. The thing that strikes me jane with your visual playbook editor is as you well know, the the way in which bad guys get in now they're very stealthy, you almost have to be stealthy in your response. So if you have to write custom code that's going to alert the bad guys that they're they're seeing now seeing code that they've never seen before, they must have detected us and then they escalate, you know, they get you in a harder, tighter headlock. Uh and I love the partnerships, you know, we, we followed the trend toward remote security. Cloud security, where's the scale is a big player, Amanda you mentioned. So that's that's great too. I mean it feels like the puzzle pieces are coming together. It's it's almost like a game of constant, you know, you're never there but you've got to stay vigilant. >>I really think so today. I mean it's been a great 12 months that's blank. We have done so much over the past year leading up to this.com. I'm very excited to talk to folks about it. I think one thing I didn't really mention that I kind of touched on earlier in the talk that we're having was around cloud security monitoring. So holistic cloud security monitoring. We've got some updates there as well with deeper integrations into G C P A W S Azure, one dr SharePoint box net G drive. Like customers are using many, many cloud services today and they don't have a holistic view across all those services I speak to see so every week that tell me they just really need one view. Not to go into each of those cloud service providers or cloud services, one at a time to look at the security posture, they need that all in a central location. So we normalize, we ingest and normalize data from each of those cloud services so you can see threats consistently across each of them. I think that's really, really something different that Splunk is doing um that other security offerings are not doing. >>I think that's a super important point and I do hear that a lot from CsoS where they say look we have so many different environments, so many different tools and they each have their own little framework so we have to go in and and investigate and then come back out and then our teams have to go into a new sort of view and come back out and and they just run out of time and they just don't again, lack of lack of skills to actually do this, can't hire half fast enough, can't train fast enough. So so that higher level view but still the ability to drill down and understand what those root causes. That's it's a it's a it's a top down bottoms up type of approach and and so as opposed to just throwing grains of sand at the second teams and then hoping, you know, they find the pearl, so jane, I'll give you the last word, Maybe some final thoughts. >>No, I just wanted to thank everyone for listening. I want to thank everyone for joining dot com 21. We're very excited to hear from you and speak with you. So thank you very much. >>Excellent. Great having you in the cube, keep it right there, everybody for more coverage of the cube. Splunk dot com 21. We'll be right back, >>Yeah.