>>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.

>>Hello and welcome today's cube presentation of eight of us startup showcase. I'm john for your host highlighting the hottest companies and devops data analytics and cloud management lisa martin and David want are here to kick it off. We've got a great program for you again. This is our, our new community event model where we're doing every quarter, we have every new episode, this is quarter three this year or episode three, season one of the hottest cloud startups and we're gonna be featured. Then we're gonna do a keynote package and then 15 countries will present their story, Go check them out and then have a closing keynote with a practitioner and we've got some great lineups, lisa Dave, great to see you. Thanks for joining me. >>Hey guys, >>great to be here. So David got to ask you, you know, back in events last night we're at the 14 it's event where they had the golf PGA championship with the cube Now we got the hybrid model, This is the new normal. We're in, we got these great companies were showcasing them. What's your take? >>Well, you're right. I mean, I think there's a combination of things. We're seeing some live shows. We saw what we did with at mobile world Congress. We did the show with AWS storage day where it was, we were at the spheres, there was no, there was a live audience, but they weren't there physically. It was just virtual and yeah, so, and I just got pained about reinvent. Hey Dave, you gotta make your flights. So I'm making my flights >>were gonna be at the amazon web services, public sector summit next week. At least a lot, a lot of cloud convergence going on here. We got many companies being featured here that we spoke with the Ceo and their top people cloud management, devops data, nelson security. Really cutting edge companies, >>yes, cutting edge companies who are all focused on acceleration. We've talked about the acceleration of digital transformation the last 18 months and we've seen a tremendous amount of acceleration in innovation with what these startups are doing. We've talked to like you said, there's, there's C suite, we've also talked to their customers about how they are innovating so quickly with this hybrid environment, this remote work and we've talked a lot about security in the last week or so. You mentioned that we were at Fortinet cybersecurity skills gap. What some of these companies are doing with automation for example, to help shorten that gap, which is a big opportunity >>for the job market. Great stuff. Dave so the format of this event, you're going to have a fireside chat with the practitioner, we'd like to end these programs with a great experienced practitioner cutting edge in data february. The beginning lisa are gonna be kicking off with of course Jeff bar to give us the update on what's going on AWS and then a special presentation from Emily Freeman who is the author of devops for dummies, she's introducing new content. The revolution in devops devops two point oh and of course jerry Chen from Greylock cube alumni is going to come on and talk about his new thesis castles in the cloud creating moats at cloud scale. We've got a great lineup of people and so the front ends can be great. Dave give us a little preview of what people can expect at the end of the fireside chat. >>Well at the highest level john I've always said we're entering that sort of third great wave of cloud. First wave was experimentation. The second big wave was migration. The third wave of integration, Deep business integration and what you're >>going to hear from >>Hello Fresh today is how they like many companies that started early last decade. They started with an on prem Hadoop system and then of course we all know what happened is S three essentially took the knees out from, from the on prem Hadoop market lowered costs, brought things into the cloud and what Hello Fresh is doing is they're transforming from that legacy Hadoop system into its running on AWS but into a data mess, you know, it's a passionate topic of mine. Hello Fresh was scaling they realized that they couldn't keep up so they had to rethink their entire data architecture and they built it around data mesh Clements key and christoph Soewandi gonna explain how they actually did that are on a journey or decentralized data >>measure it and your posts have been awesome on data measure. We get a lot of traction. Certainly you're breaking analysis for the folks watching check out David Landes, Breaking analysis every week, highlighting the cutting edge trends in tech Dave. We're gonna see you later, lisa and I are gonna be here in the morning talking about with Emily. We got Jeff Barr teed up. Dave. Thanks for coming on. Looking forward to fireside chat lisa. We'll see you when Emily comes back on. But we're gonna go to Jeff bar right now for Dave and I are gonna interview Jeff. Mm >>Hey Jeff, >>here he is. Hey, how are you? How's it going really well. So I gotta ask you, the reinvent is on, everyone wants to know that's happening right. We're good with Reinvent. >>Reinvent is happening. I've got my hotel and actually listening today, if I just remembered, I still need to actually book my flights. I've got my to do list on my desk and I do need to get my >>flights. Uh, >>really looking forward >>to it. I can't wait to see the all the announcements and blog posts. We're gonna, we're gonna hear from jerry Chen later. I love the after on our next event. Get your reaction to this castle and castles in the cloud where competitive advantages can be built in the cloud. We're seeing examples of that. But first I gotta ask you give us an update of what's going on. The ap and ecosystem has been an incredible uh, celebration these past couple weeks, >>so, so a lot of different things happening and the interesting thing to me is that as part of my job, I often think that I'm effectively living in the future because I get to see all this really cool stuff that we're building just a little bit before our customers get to, and so I'm always thinking okay, here I am now, and what's the world going to be like in a couple of weeks to a month or two when these launches? I'm working on actually get out the door and that, that's always really, really fun, just kind of getting that, that little edge into where we're going, but this year was a little interesting because we had to really significant birthdays, we had the 15 year anniversary of both EC two and S three and we're so focused on innovating and moving forward, that it's actually pretty rare for us at Aws to look back and say, wow, we've actually done all these amazing things in in the last 15 years, >>you know, it's kind of cool Jeff, if I may is is, you know, of course in the early days everybody said, well, a place for startup is a W. S and now the great thing about the startup showcases, we're seeing the startups that >>are >>very near, or some of them have even reached escape velocity, so they're not, they're not tiny little companies anymore, they're in their transforming their respective industries, >>they really are and I think that as they start ups grow, they really start to lean into the power of the cloud. They as they start to think, okay, we've we've got our basic infrastructure in place, we've got, we were serving data, we're serving up a few customers, everything is actually working pretty well for us. We've got our fundamental model proven out now, we can invest in publicity and marketing and scaling and but they don't have to think about what's happening behind the scenes. They just if they've got their auto scaling or if they're survivalists, the infrastructure simply grows to meet their demand and it's it's just a lot less things that they have to worry about. They can focus on the fun part of their business which is actually listening to customers and building up an awesome business >>Jeff as you guys are putting together all the big pre reinvented, knows a lot of stuff that goes on prior as well and they say all the big good stuff to reinvent. But you start to see some themes emerged this year. One of them is modernization of applications, the speed of application development in the cloud with the cloud scale devops personas, whatever persona you want to talk about but basically speed the speed of of the app developers where other departments have been slowing things down, I won't say name names, but security group and I t I mean I shouldn't have said that but only kidding but no but seriously people want in minutes and seconds now not days or weeks. You know whether it's policy. What are some of the trends that you're seeing around this this year as we get into some of the new stuff coming out >>So Dave customers really do want speed and for we've actually encapsulate this for a long time in amazon in what we call the bias for action leadership principle >>where >>we just need to jump in and move forward and and make things happen. A lot of customers look at that and they say yes this is great. We need to have the same bias fraction. Some do. Some are still trying to figure out exactly how to put it into play. And they absolutely for sure need to pay attention to security. They need to respect the past and make sure that whatever they're doing is in line with I. T. But they do want to move forward. And the interesting thing that I see time and time again is it's not simply about let's adopt a new technology. It's how do we >>how do we keep our workforce >>engaged? How do we make sure that they've got the right training? How do we bring our our I. T. Team along for this. Hopefully new and fun and exciting journey where they get to learn some interesting new technologies they've got all this very much accumulated business knowledge they still want to put to use, maybe they're a little bit apprehensive about something brand new and they hear about the cloud, but there by and large, they really want to move forward. They just need a little bit of >>help to make it happen >>real good guys. One of the things you're gonna hear today, we're talking about speed traditionally going fast. Oftentimes you meant you have to sacrifice some things on quality and what you're going to hear from some of the startups today is how they're addressing that to automation and modern devoPS technologies and sort of rethinking that whole application development approach. That's something I'm really excited to see organization is beginning to adopt so they don't have to make that tradeoff anymore. >>Yeah, I would >>never want to see someone >>sacrifice quality, >>but I do think that iterating very quickly and using the best of devoPS principles to be able to iterate incredibly quickly and get that first launch out there and then listen with both ears just >>as much >>as you can, Everything. You hear iterate really quickly to meet those needs in, in hours and days, not months, quarters or years. >>Great stuff. Chef and a lot of the companies were featuring here in the startup showcase represent that new kind of thinking, um, systems thinking as well as you know, the cloud scale and again and it's finally here, the revolution of deVOps is going to the next generation and uh, we're excited to have Emily Freeman who's going to come on and give a little preview for her new talk on this revolution. So Jeff, thank you for coming on, appreciate you sharing the update here on the cube. Happy >>to be. I'm actually really looking forward to hearing from Emily. >>Yeah, it's great. Great. Looking forward to the talk. Brand new Premier, Okay, uh, lisa martin, Emily Freeman is here. She's ready to come in and we're going to preview her lightning talk Emily. Um, thanks for coming on, we really appreciate you coming on really, this is about to talk around deVOPS next gen and I think lisa this is one of those things we've been, we've been discussing with all the companies. It's a new kind of thinking it's a revolution, it's a systems mindset, you're starting to see the connections there she is. Emily, Thanks for coming. I appreciate it. >>Thank you for having me. So your teaser video >>was amazing. Um, you know, that little secret radical idea, something completely different. Um, you gotta talk coming up, what's the premise behind this revolution, you know, these tying together architecture, development, automation deployment, operating altogether. >>Yes, well, we have traditionally always used the sclc, which is the software delivery life cycle. Um, and it is a straight linear process that has actually been around since the sixties, which is wild to me um, and really originated in manufacturing. Um, and as much as I love the Toyota production system and how much it has shown up in devops as a sort of inspiration on how to run things better. We are not making cars, we are making software and I think we have to use different approaches and create a sort of model that better reflects our modern software development process. >>It's a bold idea and looking forward to the talk and as motivation. I went into my basement and dusted off all my books from college in the 80s and the sea estimates it was waterfall. It was software development life cycle. They trained us to think this way and it came from the mainframe people. It was like, it's old school, like really, really old and it really hasn't been updated. Where's the motivation? I actually cloud is kind of converging everything together. We see that, but you kind of hit on this persona thing. Where did that come from this persona? Because you know, people want to put people in buckets release engineer. I mean, where's that motivation coming from? >>Yes, you're absolutely right that it came from the mainframes. I think, you know, waterfall is necessary when you're using a punch card or mag tape to load things onto a mainframe, but we don't exist in that world anymore. Thank goodness. And um, yes, so we, we use personas all the time in tech, you know, even to register, well not actually to register for this event, but a lot events. A lot of events, you have to click that drop down. Right. Are you a developer? Are you a manager, whatever? And the thing is personas are immutable in my opinion. I was a developer. I will always identify as a developer despite playing a lot of different roles and doing a lot of different jobs. Uh, and this can vary throughout the day. Right. You might have someone who has a title of software architect who ends up helping someone pair program or develop or test or deploy. Um, and so we wear a lot of hats day to day and I think our discussions around roles would be a better, um, certainly a better approach than personas >>lease. And I've been discussing with many of these companies around the roles and we're hearing from them directly and they're finding out that people have, they're mixing and matching on teams. So you're, you're an S R E on one team and you're doing something on another team where the workflows and the workloads defined the team formation. So this is a cultural discussion. >>It absolutely is. Yes. I think it is a cultural discussion and it really comes to the heart of devops, right? It's people process. And then tools deVOps has always been about culture and making sure that developers have all the tools they need to be productive and honestly happy. What good is all of this? If developing software isn't a joyful experience. Well, >>I got to ask you, I got you here obviously with server list and functions just starting to see this kind of this next gen. And we're gonna hear from jerry Chen, who's a Greylock VC who's going to talk about castles in the clouds, where he's discussing the moats that could be created with a competitive advantage in cloud scale. And I think he points to the snowflakes of the world. You're starting to see this new thing happening. This is devops 2.0, this is the revolution. Is this kind of where you see the same vision of your talk? >>Yes, so DeVOps created 2000 and 8, 2000 and nine, totally different ecosystem in the world we were living in, you know, we didn't have things like surveillance and containers, we didn't have this sort of default distributed nature, certainly not the cloud. Uh and so I'm very excited for jerry's talk. I'm curious to hear more about these moz. I think it's fascinating. Um but yeah, you're seeing different companies use different tools and processes to accelerate their delivery and that is the competitive advantage. How can we figure out how to utilize these tools in the most efficient way possible. >>Thank you for coming and giving us a preview. Let's now go to your lightning keynote talk. Fresh content. Premier of this revolution in Devops and the Freemans Talk, we'll go there now. >>Hi, I'm Emily Freeman, I'm the author of devops for dummies and the curator of 97 things every cloud engineer should know. I am thrilled to be here with you all today. I am really excited to share with you a kind of a wild idea, a complete re imagining of the S DLC and I want to be clear, I need your feedback. I want to know what you think of this. You can always find me on twitter at editing. Emily, most of my work centers around deVOps and I really can't overstate what an impact the concept of deVOPS has had on this industry in many ways it built on the foundation of Agile to become a default a standard we all reach for in our everyday work. When devops surfaced as an idea in 2008, the tech industry was in a vastly different space. AWS was an infancy offering only a handful of services. Azure and G C P didn't exist yet. The majority's majority of companies maintained their own infrastructure. Developers wrote code and relied on sys admins to deploy new code at scheduled intervals. Sometimes months apart, container technology hadn't been invented applications adhered to a monolithic architecture, databases were almost exclusively relational and serverless wasn't even a concept. Everything from the application to the engineers was centralized. Our current ecosystem couldn't be more different. Software is still hard, don't get me wrong, but we continue to find novel solutions to consistently difficult, persistent problems. Now, some of these end up being a sort of rebranding of old ideas, but others are a unique and clever take to abstracting complexity or automating toil or perhaps most important, rethinking challenging the very premises we have accepted as Cannon for years, if not decades. In the years since deVOps attempted to answer the critical conflict between developers and operations, engineers, deVOps has become a catch all term and there have been a number of derivative works. Devops has come to mean 5000 different things to 5000 different people. For some, it can be distilled to continuous integration and continuous delivery or C I C D. For others, it's simply deploying code more frequently, perhaps adding a smattering of tests for others. Still, its organizational, they've added a platform team, perhaps even a questionably named DEVOPS team or have created an engineering structure that focuses on a separation of concerns. Leaving feature teams to manage the development, deployment, security and maintenance of their siloed services, say, whatever the interpretation, what's important is that there isn't a universally accepted standard. Well, what deVOPS is or what it looks like an execution, it's a philosophy more than anything else. A framework people can utilize to configure and customize their specific circumstances to modern development practices. The characteristic of deVOPS that I think we can all agree on though, is that an attempted to capture the challenges of the entire software development process. It's that broad umbrella, that holistic view that I think we need to breathe life into again, The challenge we face is that DeVOps isn't increasingly outmoded solution to a previous problem developers now face. Cultural and technical challenge is far greater than how to more quickly deploy a monolithic application. Cloud native is the future the next collection of default development decisions and one the deVOPS story can't absorb in its current form. I believe the era of deVOPS is waning and in this moment as the sun sets on deVOPS, we have a unique opportunity to rethink rebuild free platform. Even now, I don't have a crystal ball. That would be very handy. I'm not completely certain with the next decade of tech looks like and I can't write this story alone. I need you but I have some ideas that can get the conversation started, I believe to build on what was we have to throw away assumptions that we've taken for granted all this time in order to move forward. We must first step back. Mhm. The software or systems development life cycle, what we call the S. D. L. C. has been in use since the 1960s and it's remained more or less the same since before color television and the touch tone phone. Over the last 60 or so odd years we've made tweaks, slight adjustments, massaged it. The stages or steps are always a little different with agile and deVOps we sort of looped it into a circle and then an infinity loop we've added pretty colors. But the sclc is more or less the same and it has become an assumption. We don't even think about it anymore, universally adopted constructs like the sclc have an unspoken permanence. They feel as if they have always been and always will be. I think the impact of that is even more potent. If you were born after a construct was popularized. Nearly everything around us is a construct, a model, an artifact of a human idea. The chair you're sitting in the desk, you work at the mug from which you drink coffee or sometimes wine, buildings, toilets, plumbing, roads, cars, art, computers, everything. The sclc is a remnant an artifact of a previous era and I think we should throw it away or perhaps more accurately replace it, replace it with something that better reflects the actual nature of our work. A linear, single threaded model designed for the manufacturer of material goods cannot possibly capture the distributed complexity of modern socio technical systems. It just can't. Mhm. And these two ideas aren't mutually exclusive that the sclc was industry changing, valuable and extraordinarily impactful and that it's time for something new. I believe we are strong enough to hold these two ideas at the same time, showing respect for the past while envisioning the future. Now, I don't know about you, I've never had a software project goes smoothly in one go. No matter how small. Even if I'm the only person working on it and committing directly to master software development is chaos. It's a study and entropy and it is not getting any more simple. The model with which we think and talk about software development must capture the multithreaded, non sequential nature of our work. It should embody the roles engineers take on and the considerations they make along the way. It should build on the foundations of agile and devops and represent the iterative nature of continuous innovation. Now, when I was thinking about this, I was inspired by ideas like extreme programming and the spiral model. I I wanted something that would have layers, threads, even a way of visually representing multiple processes happening in parallel. And what I settled on is the revolution model. I believe the visualization of revolution is capable of capturing the pivotal moments of any software scenario. And I'm going to dive into all the discrete elements. But I want to give you a moment to have a first impression, to absorb my idea. I call it revolution because well for one it revolves, it's circular shape reflects the continuous and iterative nature of our work, but also because it is revolutionary. I am challenging a 60 year old model that is embedded into our daily language. I don't expect Gartner to build a magic quadrant around this tomorrow, but that would be super cool. And you should call me my mission with. This is to challenge the status quo to create a model that I think more accurately reflects the complexity of modern cloud native software development. The revolution model is constructed of five concentric circles describing the critical roles of software development architect. Ng development, automating, deploying and operating intersecting each loop are six spokes that describe the production considerations every engineer has to consider throughout any engineering work and that's test, ability, secure ability, reliability, observe ability, flexibility and scalability. The considerations listed are not all encompassing. There are of course things not explicitly included. I figured if I put 20 spokes, some of us, including myself, might feel a little overwhelmed. So let's dive into each element in this model. We have long used personas as the default way to do divide audiences and tailor messages to group people. Every company in the world right now is repeating the mantra of developers, developers, developers but personas have always bugged me a bit because this approach typically either oversimplifies someone's career are needlessly complicated. Few people fit cleanly and completely into persona based buckets like developers and operations anymore. The lines have gotten fuzzy on the other hand, I don't think we need to specifically tailor messages as to call out the difference between a devops engineer and a release engineer or a security administrator versus a security engineer but perhaps most critically, I believe personas are immutable. A persona is wholly dependent on how someone identifies themselves. It's intrinsic not extrinsic. Their titles may change their jobs may differ, but they're probably still selecting the same persona on that ubiquitous drop down. We all have to choose from when registering for an event. Probably this one too. I I was a developer and I will always identify as a developer despite doing a ton of work in areas like devops and Ai Ops and Deverell in my heart. I'm a developer I think about problems from that perspective. First it influences my thinking and my approach roles are very different. Roles are temporary, inconsistent, constantly fluctuating. If I were an actress, the parts I would play would be lengthy and varied, but the persona I would identify as would remain an actress and artist lesbian. Your work isn't confined to a single set of skills. It may have been a decade ago, but it is not today in any given week or sprint, you may play the role of an architect. Thinking about how to design a feature or service, developer building out code or fixing a bug and on automation engineer, looking at how to improve manual processes. We often refer to as soil release engineer, deploying code to different environments or releasing it to customers or in operations. Engineer ensuring an application functions inconsistent expected ways and no matter what role we play. We have to consider a number of issues. The first is test ability. All software systems require testing to assure architects that designs work developers, the code works operators, that infrastructure is running as expected and engineers of all disciplines that code changes won't bring down the whole system testing in its many forms is what enables systems to be durable and have longevity. It's what reassures engineers that changes won't impact current functionality. A system without tests is a disaster waiting to happen, which is why test ability is first among equals at this particular roundtable. Security is everyone's responsibility. But if you understand how to design and execute secure systems, I struggle with this security incidents for the most part are high impact, low probability events. The really big disasters, the one that the ones that end up on the news and get us all free credit reporting for a year. They don't happen super frequently and then goodness because you know that there are endless small vulnerabilities lurking in our systems. Security is something we all know we should dedicate time to but often don't make time for. And let's be honest, it's hard and complicated and a little scary def sec apps. The first derivative of deVOPS asked engineers to move security left this approach. Mint security was a consideration early in the process, not something that would block release at the last moment. This is also the consideration under which I'm putting compliance and governance well not perfectly aligned. I figure all the things you have to call lawyers for should just live together. I'm kidding. But in all seriousness, these three concepts are really about risk management, identity, data, authorization. It doesn't really matter what specific issue you're speaking about, the question is who has access to what win and how and that is everyone's responsibility at every stage site reliability engineering or sorry, is a discipline job and approach for good reason. It is absolutely critical that applications and services work as expected. Most of the time. That said, availability is often mistakenly treated as a synonym for reliability. Instead, it's a single aspect of the concept if a system is available but customer data is inaccurate or out of sync. The system is not reliable, reliability has five key components, availability, latency, throughput. Fidelity and durability, reliability is the end result. But resiliency for me is the journey the action engineers can take to improve reliability, observe ability is the ability to have insight into an application or system. It's the combination of telemetry and monitoring and alerting available to engineers and leadership. There's an aspect of observe ability that overlaps with reliability, but the purpose of observe ability isn't just to maintain a reliable system though, that is of course important. It is the capacity for engineers working on a system to have visibility into the inner workings of that system. The concept of observe ability actually originates and linear dynamic systems. It's defined as how well internal states of a system can be understood based on information about its external outputs. If it is critical when companies move systems to the cloud or utilize managed services that they don't lose visibility and confidence in their systems. The shared responsibility model of cloud storage compute and managed services require that engineering teams be able to quickly be alerted to identify and remediate issues as they arise. Flexible systems are capable of adapting to meet the ever changing needs of the customer and the market segment, flexible code bases absorb new code smoothly. Embody a clean separation of concerns. Are partitioned into small components or classes and architected to enable the now as well as the next inflexible systems. Change dependencies are reduced or eliminated. Database schemas accommodate change well components, communicate via a standardized and well documented A. P. I. The only thing constant in our industry is change and every role we play, creating flexibility and solutions that can be flexible that will grow as the applications grow is absolutely critical. Finally, scalability scalability refers to more than a system's ability to scale for additional load. It implies growth scalability and the revolution model carries the continuous innovation of a team and the byproducts of that growth within a system. For me, scalability is the most human of the considerations. It requires each of us in our various roles to consider everyone around us, our customers who use the system or rely on its services, our colleagues current and future with whom we collaborate and even our future selves. Mhm. Software development isn't a straight line, nor is it a perfect loop. It is an ever changing complex dance. There are twirls and pivots and difficult spins forward and backward. Engineers move in parallel, creating truly magnificent pieces of art. We need a modern model for this modern era and I believe this is just the revolution to get us started. Thank you so much for having me. >>Hey, we're back here. Live in the keynote studio. I'm john for your host here with lisa martin. David lot is getting ready for the fireside chat ending keynote with the practitioner. Hello! Fresh without data mesh lisa Emily is amazing. The funky artwork there. She's amazing with the talk. I was mesmerized. It was impressive. >>The revolution of devops and the creative element was a really nice surprise there. But I love what she's doing. She's challenging the status quo. If we've learned nothing in the last year and a half, We need to challenge the status quo. A model from the 1960s that is no longer linear. What she's doing is revolutionary. >>And we hear this all the time. All the cube interviews we do is that you're seeing the leaders, the SVP's of engineering or these departments where there's new new people coming in that are engineering or developers, they're playing multiple roles. It's almost a multidisciplinary aspect where you know, it's like going into in and out burger in the fryer later and then you're doing the grill, you're doing the cashier, people are changing roles or an architect, their test release all in one no longer departmental, slow siloed groups. >>She brought up a great point about persona is that we no longer fit into these buckets. That the changing roles. It's really the driver of how we should be looking at this. >>I think I'm really impressed, really bold idea, no brainer as far as I'm concerned, I think one of the things and then the comments were off the charts in a lot of young people come from discord servers. We had a good traction over there but they're all like learning. Then you have the experience, people saying this is definitely has happened and happening. The dominoes are falling and they're falling in the direction of modernization. That's the key trend speed. >>Absolutely with speed. But the way that Emily is presenting it is not in a brash bold, but it's in a way that makes great sense. The way that she creatively visually lined out what she was talking about Is amenable to the folks that have been doing this for since the 60s and the new folks now to really look at this from a different >>lens and I think she's a great setup on that lightning top of the 15 companies we got because you think about sis dig harness. I white sourced flamingo hacker one send out, I oh, okay. Thought spot rock set Sarah Ops ramp and Ops Monte cloud apps, sani all are doing modern stuff and we talked to them and they're all on this new wave, this monster wave coming. What's your observation when you talk to these companies? >>They are, it was great. I got to talk with eight of the 15 and the amount of acceleration of innovation that they've done in the last 18 months is phenomenal obviously with the power and the fuel and the brand reputation of aws but really what they're all facilitating cultural shift when we think of devoPS and the security folks. Um, there's a lot of work going on with ai to an automation to really kind of enabled to develop the develops folks to be in control of the process and not have to be security experts but ensuring that the security is baked in shifting >>left. We saw that the chat room was really active on the security side and one of the things I noticed was not just shift left but the other groups, the security groups and the theme of cultural, I won't say war but collision cultural shift that's happening between the groups is interesting because you have this new devops persona has been around Emily put it out for a while. But now it's going to the next level. There's new revolutions about a mindset, a systems mindset. It's a thinking and you start to see the new young companies coming out being funded by the gray locks of the world who are now like not going to be given the we lost the top three clouds one, everything. there's new business models and new technical architecture in the cloud and that's gonna be jerry Chen talk coming up next is going to be castles in the clouds because jerry chant always talked about moats, competitive advantage and how moats are key to success to guard the castle. And then we always joke, there's no more moz because the cloud has killed all the boats. But now the motor in the cloud, the castles are in the cloud, not on the ground. So very interesting thought provoking. But he's got data and if you look at the successful companies like the snowflakes of the world, you're starting to see these new formations of this new layer of innovation where companies are growing rapidly, 98 unicorns now in the cloud. Unbelievable, >>wow, that's a lot. One of the things you mentioned, there's competitive advantage and these startups are all fueled by that they know that there are other companies in the rear view mirror right behind them. If they're not able to work as quickly and as flexibly as a competitor, they have to have that speed that time to market that time to value. It was absolutely critical. And that's one of the things I think thematically that I saw along the eighth sort of that I talked to is that time to value is absolutely table stakes. >>Well, I'm looking forward to talking to jerry chan because we've talked on the queue before about this whole idea of What happens when winner takes most would mean the top 3, 4 cloud players. What happens? And we were talking about that and saying, if you have a model where an ecosystem can develop, what does that look like and back in 2013, 2014, 2015, no one really had an answer. Jerry was the only BC. He really nailed it with this castles in the cloud. He nailed the idea that this is going to happen. And so I think, you know, we'll look back at the tape or the videos from the cube, we'll find those cuts. But we were talking about this then we were pontificating and riffing on the fact that there's going to be new winners and they're gonna look different as Andy Jassy always says in the cube you have to be misunderstood if you're really going to make something happen. Most of the most successful companies are misunderstood. Not anymore. The cloud scales there. And that's what's exciting about all this. >>It is exciting that the scale is there, the appetite is there the appetite to challenge the status quo, which is right now in this economic and dynamic market that we're living in is there's nothing better. >>One of the things that's come up and and that's just real quick before we bring jerry in is automation has been insecurity, absolutely security's been in every conversation, but automation is now so hot in the sense of it's real and it's becoming part of all the design decisions. How can we automate can we automate faster where the keys to automation? Is that having the right data, What data is available? So I think the idea of automation and Ai are driving all the change and that's to me is what these new companies represent this modern error where AI is built into the outcome and the apps and all that infrastructure. So it's super exciting. Um, let's check in, we got jerry Chen line at least a great. We're gonna come back after jerry and then kick off the day. Let's bring in jerry Chen from Greylock is he here? Let's bring him in there. He is. >>Hey john good to see you. >>Hey, congratulations on an amazing talk and thesis on the castles on the cloud. Thanks for coming on. >>All right, Well thanks for reading it. Um, always were being put a piece of workout out either. Not sure what the responses, but it seemed to resonate with a bunch of developers, founders, investors and folks like yourself. So smart people seem to gravitate to us. So thank you very much. >>Well, one of the benefits of doing the Cube for 11 years, Jerry's we have videotape of many, many people talking about what the future will hold. You kind of are on this early, it wasn't called castles in the cloud, but you were all I was, we had many conversations were kind of connecting the dots in real time. But you've been on this for a while. It's great to see the work. I really think you nailed this. I think you're absolutely on point here. So let's get into it. What is castles in the cloud? New research to come out from Greylock that you spearheaded? It's collaborative effort, but you've got data behind it. Give a quick overview of what is castle the cloud, the new modes of competitive advantage for companies. >>Yeah, it's as a group project that our team put together but basically john the question is, how do you win in the cloud? Remember the conversation we had eight years ago when amazon re event was holy cow, Like can you compete with them? Like is it a winner? Take all? Winner take most And if it is winner take most, where are the white spaces for Some starts to to emerge and clearly the past eight years in the cloud this journey, we've seen big companies, data breaks, snowflakes, elastic Mongo data robot. And so um they spotted the question is, you know, why are the castles in the cloud? The big three cloud providers, Amazon google and Azure winning. You know, what advantage do they have? And then given their modes of scale network effects, how can you as a startup win? And so look, there are 500 plus services between all three cloud vendors, but there are like 500 plus um startups competing gets a cloud vendors and there's like almost 100 unicorn of private companies competing successfully against the cloud vendors, including public companies. So like Alaska, Mongo Snowflake. No data breaks. Not public yet. Hashtag or not public yet. These are some examples of the names that I think are winning and watch this space because you see more of these guys storm the castle if you will. >>Yeah. And you know one of the things that's a funny metaphor because it has many different implications. One, as we talk about security, the perimeter of the gates, the moats being on land. But now you're in the cloud, you have also different security paradigm. You have a different um, new kinds of services that are coming on board faster than ever before. Not just from the cloud players but From companies contributing into the ecosystem. So the combination of the big three making the market the main markets you, I think you call 31 markets that we know of that probably maybe more. And then you have this notion of a sub market, which means that there's like we used to call it white space back in the day, remember how many whites? Where's the white space? I mean if you're in the cloud, there's like a zillion white spaces. So talk about this sub market dynamic between markets and that are being enabled by the cloud players and how these sub markets play into it. >>Sure. So first, the first problem was what we did. We downloaded all the services for the big three clowns. Right? And you know what as recalls a database or database service like a document DB and amazon is like Cosmo dB and Azure. So first thing first is we had to like look at all three cloud providers and you? Re categorize all the services almost 500 Apples, Apples, Apples # one number two is you look at all these markets or sub markets and said, okay, how can we cluster these services into things that you know you and I can rock right. That's what amazon Azure and google think about. It is very different and the beauty of the cloud is this kind of fat long tail of services for developers. So instead of like oracle is a single database for all your needs. They're like 20 or 30 different databases from time series um analytics, databases. We're talking rocks at later today. Right. Um uh, document databases like Mongo search database like elastic. And so what happens is there's not one giant market like databases, there's a database market And 30, 40 sub markets that serve the needs developers. So the Great News is cloud has reduced the cost and create something that new for developers. Um also the good news is for a start up you can find plenty of white speeds solving a pain point, very specific to a different type of problem >>and you can sequence up to power law to this. I love the power of a metaphor, you know, used to be a very thin neck note no torso and then a long tail. But now as you're pointing out this expansion of the fat tail of services, but also there's big tam's and markets available at the top of the power law where you see coming like snowflake essentially take on the data warehousing market by basically sitting on amazon re factoring with new services and then getting a flywheel completely changing the economic unit economics completely changing the consumption model completely changing the value proposition >>literally you >>get Snowflake has created like a storm, create a hole, that mode or that castle wall against red shift. Then companies like rock set do your real time analytics is Russian right behind snowflakes saying, hey snowflake is great for data warehouse but it's not fast enough for real time analytics. Let me give you something new to your, to your parallel argument. Even the big optic snowflake have created kind of a wake behind them that created even more white space for Gaza rock set. So that's exciting for guys like me and >>you. And then also as we were talking about our last episode two or quarter two of our showcase. Um, from a VC came on, it's like the old shelf where you didn't know if a company's successful until they had to return the inventory now with cloud you if you're not successful, you know it right away. It's like there's no debate. Like, I mean you're either winning or not. This is like that's so instrumented so a company can have a good better mousetrap and win and fill the white space and then move up. >>It goes both ways. The cloud vendor, the big three amazon google and Azure for sure. They instrument their own class. They know john which ecosystem partners doing well in which ecosystems doing poorly and they hear from the customers exactly what they want. So it goes both ways they can weaponize that. And just as well as you started to weaponize that info >>and that's the big argument of do that snowflake still pays the amazon bills. They're still there. So again, repatriation comes back, That's a big conversation that's come up. What's your quick take on that? Because if you're gonna have a castle in the cloud, then you're gonna bring it back to land. I mean, what's that dynamic? Where do you see that compete? Because on one hand is innovation. The other ones maybe cost efficiency. Is that a growth indicator slow down? What's your view on the movement from and to the cloud? >>I think there's probably three forces you're finding here. One is the cost advantage in the scale advantage of cloud so that I think has been going for the past eight years, there's a repatriation movement for a certain subset of customers, I think for cost purposes makes sense. I think that's a tiny handful that believe they can actually run things better than a cloud. The third thing we're seeing around repatriation is not necessary against cloud, but you're gonna see more decentralized clouds and things pushed to the edge. Right? So you look at companies like Cloudflare Fastly or a company that we're investing in Cato networks. All ideas focus on secure access at the edge. And so I think that's not the repatriation of my own data center, which is kind of a disaggregated of cloud from one giant monolithic cloud, like AWS east or like a google region in europe to multiple smaller clouds for governance purposes, security purposes or legacy purposes. >>So I'm looking at my notes here, looking down on the screen here for this to read this because it's uh to cut and paste from your thesis on the cloud. The excellent cloud. The of the $38 billion invested this quarter. Um Ai and ml number one, um analytics. Number two, security number three. Actually, security number one. But you can see the bubbles here. So all those are data problems I need to ask you. I see data is hot data as intellectual property. How do you look at that? Because we've been reporting on this and we just started the cube conversation around workflows as intellectual property. If you have scale and your motives in the cloud. You could argue that data and the workflows around those data streams is intellectual property. It's a protocol >>I believe both are. And they just kind of go hand in hand like peanut butter and jelly. Right? So data for sure. I. P. So if you know people talk about days in the oil, the new resource. That's largely true because of powers a bunch. But the workflow to your point john is sticky because every company is a unique snowflake right? Like the process used to run the cube and your business different how we run our business. So if you can build a workflow that leverages the data, that's super sticky. So in terms of switching costs, if my work is very bespoke to your business, then I think that's competitive advantage. >>Well certainly your workflow is a lot different than the cube. You guys just a lot of billions of dollars in capital. We're talking to all the people out here jerry. Great to have you on final thought on your thesis. Where does it go from here? What's been the reaction? Uh No, you put it out there. Great love the restart. Think you're on point on this one. Where did we go from here? >>We have to follow pieces um in the near term one around, you know, deep diver on open source. So look out for that pretty soon and how that's been a powerful strategy a second. Is this kind of just aggregation of the cloud be a Blockchain and you know, decentralized apps, be edge applications. So that's in the near term two more pieces of, of deep dive we're doing. And then the goal here is to update this on a quarterly and annual basis. So we're getting submissions from founders that wanted to say, hey, you missed us or he screwed up here. We got the big cloud vendors saying, Hey jerry, we just lost his new things. So our goal here is to update this every single year and then probably do look back saying, okay, uh, where were we wrong? We're right. And then let's say the castle clouds 2022. We'll see the difference were the more unicorns were there more services were the IPO's happening. So look for some short term work from us on analytics, like around open source and clouds. And then next year we hope that all of this forward saying, Hey, you have two year, what's happening? What's changing? >>Great stuff and, and congratulations on the southern news. You guys put another half a billion dollars into early, early stage, which is your roots. Are you still doing a lot of great investments in a lot of unicorns. Congratulations that. Great luck on the team. Thanks for coming on and congratulations you nailed this one. I think I'm gonna look back and say that this is a pretty seminal piece of work here. Thanks for sharing. >>Thanks john thanks for having us. >>Okay. Okay. This is the cube here and 81 startup showcase. We're about to get going in on all the hot companies closing out the kino lisa uh, see jerry Chen cube alumni. He was right from day one. We've been riffing on this, but he nails it here. I think Greylock is lucky to have him as a general partner. He's done great deals, but I think he's hitting the next wave big. This is, this is huge. >>I was listening to you guys talking thinking if if you had a crystal ball back in 2013, some of the things Jerry saying now his narrative now, what did he have a crystal >>ball? He did. I mean he could be a cuBA host and I could be a venture capital. We were both right. I think so. We could have been, you know, doing that together now and all serious now. He was right. I mean, we talked off camera about who's the next amazon who's going to challenge amazon and Andy Jassy was quoted many times in the queue by saying, you know, he was surprised that it took so long for people to figure out what they were doing. Okay, jerry was that VM where he had visibility into the cloud. He saw amazon right away like we did like this is a winning formula and so he was really out front on this one. >>Well in the investments that they're making in these unicorns is exciting. They have this, this lens that they're able to see the opportunities there almost before anybody else can. And finding more white space where we didn't even know there was any. >>Yeah. And what's interesting about the report I'm gonna dig into and I want to get to him while he's on camera because it's a great report, but He says it's like 500 services I think Amazon has 5000. So how you define services as an interesting thing and a lot of amazon services that they have as your doesn't have and vice versa, they do call that out. So I find the report interesting. It's gonna be a feature game in the future between clouds the big three. They're gonna say we do this, you're starting to see the formation, Google's much more developer oriented. Amazon is much more stronger in the governance area with data obviously as he pointed out, they have such experience Microsoft, not so much their developer cloud and more office, not so much on the government's side. So that that's an indicator of my, my opinion of kind of where they rank. So including the number one is still amazon web services as your long second place, way behind google, right behind Azure. So we'll see how the horses come in, >>right. And it's also kind of speaks to the hybrid world in which we're living the hybrid multi cloud world in which many companies are living as companies to not just survive in the last year and a half, but to thrive and really have to become data companies and leverage that data as a competitive advantage to be able to unlock the value of it. And a lot of these startups that we talked to in the showcase are talking about how they're helping organizations unlock that data value. As jerry said, it is the new oil, it's the new gold. Not unless you can unlock that value faster than your competition. >>Yeah, well, I'm just super excited. We got a great day ahead of us with with all the cots startups. And then at the end day, Volonte is gonna interview, hello, fresh practitioners, We're gonna close it out every episode now, we're going to do with the closing practitioner. We try to get jpmorgan chase data measures. The hottest area right now in the enterprise data is new competitive advantage. We know that data workflows are now intellectual property. You're starting to see data really factoring into these applications now as a key aspect of the competitive advantage and the value creation. So companies that are smart are investing heavily in that and the ones that are kind of slow on the uptake are lagging the market and just trying to figure it out. So you start to see that transition and you're starting to see people fall away now from the fact that they're not gonna make it right, You're starting to, you know, you can look at look at any happens saying how much ai is really in there. Real ai what's their data strategy and you almost squint through that and go, okay, that's gonna be losing application. >>Well the winners are making it a board level conversation >>And security isn't built in. Great to have you on this morning kicking it off. Thanks John Okay, we're going to go into the next set of the program at 10:00 we're going to move into the breakouts. Check out the companies is three tracks in there. We have an awesome track on devops pure devops. We've got the data and analytics and we got the cloud management and just to run down real quick check out the sis dig harness. Io system is doing great, securing devops harness. IO modern software delivery platform, White Source. They're preventing and remediating the rest of the internet for them for the company's that's a really interesting and lumbago, effortless acres land and monitoring functions, server list super hot. And of course hacker one is always great doing a lot of great missions and and bounties you see those success continue to send i O there in Palo alto changing the game on data engineering and data pipe lining. Okay. Data driven another new platform, horizontally scalable and of course thought spot ai driven kind of a search paradigm and of course rock set jerry Chen's companies here and press are all doing great in the analytics and then the cloud management cost side 80 operations day to operate. Ops ramps and ops multi cloud are all there and sunny, all all going to present. So check them out. This is the Cubes Adria's startup showcase episode three.

>>Hi, I'm Emily Freeman, I'm the author of devops for dummies and the curator of 97 things every cloud engineer should know. I am thrilled to be here with you all today. >>I'm really excited to share with you a kind of a wild idea. A complete re imagining >>of the S DLC >>and I want to be clear, I need your feedback. I want to >>know what you think of this. You can always find me >>on twitter at editing. Emily, >>most of my work centers around devops and I really >>can't overstate what an impact >>the concept of devoPS has had on this industry >>in many ways it built on the foundation of agile to become a default a standard we all reach for in our everyday work. >>When devops surfaced as an idea in 2000 >>and eight, the tech industry was in a vastly different space. >>AWS was an infancy >>offering. Only a handful >>of services, >>Azure and G C P didn't exist yet. The majority's majority of companies maintained their own infrastructure. >>Developers wrote code and relied on sys admins to deploy new code at scheduled intervals. Sometimes months apart, container technology hadn't been invented. >>Applications adhered >>to a monolithic architecture, databases were almost exclusively relational >>and serverless wasn't even a concept. Everything from the application to the engineers >>was centralized. >>Our current ecosystem couldn't >>be more different. Software is still hard. Don't get me wrong, >>but we continue to find novel solutions to consistently difficult, persistent problems. >>Now, some of these end up being a sort of rebranding of old ideas >>but others are a unique and clever take to abstracting complexity >>or >>automating toil or >>perhaps most important, >>rethinking challenging the very >>premises we have accepted as Cannon for years, if not decades. >>In the years since deVOps attempted to answer the critical conflict between developers and operations engineers. Devops has become a catch all term >>and there have been a number of >>derivative works. DeVos has come to mean 5000 different things to 5000 different people. For some, it can be distilled >>to continuous integration and continuous delivery or C I C D. For others, it's >>simply deploying code more frequently, perhaps adding a smattering of tests >>for others. Still its organizational, they've added a platform team, perhaps even a >>questionably named DevoPS team or have created an engineering structure that focuses on a separation of concerns, leaving feature teams to manage the development, >>deployment, security and maintenance of their siloed services. Whatever >>the interpretation, what's important is that there isn't a universally accepted >>standard, well what deVOPS is or what it looks like an execution, it's a philosophy more than anything else. >>A framework people can utilize to configure >>and customize >>their specific circumstances >>to modern development practices. The characteristic of DEVOPS that I think we can all >>agree on though, is that an attempted to capture the challenges of the entire >>software development process. It's that broad >>umbrella, that holistic view that I think we need to breathe life into again, The challenge we face >>is that devops isn't >>increasingly outmoded solution to a >>previous problem developers now face >>cultural and technical challenge is far greater than how to more quickly deploy a monolithic application >>cloud native is the future. The next collection of default development decisions >>and one the deVOps story can't absorb in its current form. >>I believe the era of devops is waning and in this moment as the sun sets on >>deVOps, we have a unique opportunity to rethink >>rebuild free platform. Even now, I don't have a crystal ball that would be >>very handy. >>I'm not completely certain with the next decade of tech looks like >>and I can't write this story alone. I need you >>but I have some ideas >>that can get the conversation >>started, I believe to >>build on what was we have to throw away assumptions >>that we've taken for granted all this time in order to move forward. We must first step back. Mhm. The software or systems development life cycle, what we call the S DLC >>has been in use since the 1960s and it's remained more or less the same since before >>color television >>and the touch tone phone >>Over the last 60 or so odd years we've made tweaks, slight adjustments, massaged it. The stages or steps are always a little different >>with agile and devops we sort of looped it into a circle >>and then an infinity loop. >>We've added pretty colors. But the sclc >>is more or less >>the same and it has become an assumption. We don't even think about it anymore, >>universally adopted constructs like the sclc have an unspoken >>permanence. They feel as if they have always been and always will be. I think the impact of that is even more potent. If you were born after a >>construct was popularized, nearly everything around us is a construct. A model, an artifact of >>a human idea. >>The chair you're sitting in the >>desk, you work at the mug from which you drink coffee or sometimes wine, >>buildings, toilets, >>plumbing, roads, cars, art, computers, everything. The splc is a remnant an artifact of a previous era and I think we should throw it away >>or perhaps more accurately replace >>it, replace it with something that better reflects the actual nature of our work. A linear, single threaded model designed for the manufacturer of material goods cannot possibly capture the distributed >>complexity of modern socio technical systems. >>It just can't. Mhm. >>And these two ideas aren't mutually exclusive that >>the sclc was industry changing, valuable and extraordinarily impactful and that it's time for something new. I believe we are strong enough to hold these two ideas at the same time showing respect for the past while envisioning the future. >>No, I don't know about you. I've never had a software project goes smoothly in one >>go, no matter how small, even if I'm the only person working on it and committing directly to master >>Software development >>is chaos. It's a study and entropy and it is not getting any more simple. The model with which we think and talk about software development must capture the multithreaded, non sequential nature of our work. It should embody the roles engineers take on and the considerations they make along the way. It should build on the foundations >>of agile >>and devops and represent the iterative nature of continuous innovation. >>Now when I was thinking about this I was inspired by ideas like extreme programming and the spiral model. Yeah >>I wanted something that would have layers, >>threads, even a way >>of visually representing multiple processes happening in parallel. >>And what I settled on is the revolution model. >>I believe the visualization of revolution is capable of capturing the pivotal moments of any software scenario >>and I'm going to dive into all the discrete elements but I want to give you a moment to have a first impression to absorb >>my idea. >>I call it revolution because well for one it revolves, >>it's circular shape reflects the continuous and iterative nature of our work. >>But also because it is >>revolutionary. I am challenging a 60 year old model that is embedded into our daily language. I don't expect Gartner to build a magic quadrant around this tomorrow but that would be super cool and you should call me my mission with this is to challenge the status quo. To create a model that I think more accurately reflects the complexity of modern cloud. Native >>software development. The revolution model is constructed of five concentric circles describing the critical roles of software development architect. Ng development, >>automating, >>deploying and operating >>intersecting each loop are six >>spokes >>that describe the production considerations every engineer has to consider throughout any engineering work and that's test, >>ability, secure ability, reliability, observe ability, flexibility and scalability. The considerations listed >>are not all >>encompassing. There are of course things not explicitly included. I figured if I put 20 spokes, some of us, including myself, might feel a little overwhelmed. So let's dive into each element in this model, >>we have long used personas as the default way to do divide >>audiences and tailor messages to group people. >>Every company in the world right now is repeating the mantra of developers, developers, developers, but personas have >>always bugged me a bit >>because this approach typically >>either oversimplifies someone's career >>are needlessly complicated. Few people fit cleanly and completely >>into persona based buckets like developers and >>operations anymore. The lines have gotten fuzzy on the other hand, I don't think we need to specifically tailor >>messages >>as to call out the difference between a devops engineer and a release engineer or security administrator versus a security engineer. But perhaps most critically, I believe personas are immutable. Mhm. A persona is wholly dependent on how someone identifies themselves. It's intrinsic not extrinsic. Their titles may change their jobs may differ but they're probably >>still selecting the same persona on that ubiquitous drop down. We all have to choose >>from when registering for an >>event. Probably this one too. I I was a developer and I will always identify as a developer despite doing a ton of work in areas like devops and Ai ops and Deverell >>in my heart. I'm a developer I think about problems from that perspective. First it influences my thinking and my approach. Mhm roles are very different. Roles are temporary, >>inconsistent, >>constantly fluctuating. If I were an actress, the parts I would play would be lengthy and varied but the persona I would identify as would remain an actress and artist >>lesbian. >>Your work isn't confined >>to a single set of skills. It may have been a decade ago but it is not today >>in any given week or sprint. You may play the role of an architect thinking about how to design a feature or service, >>developer, building out code or fixing a bug >>and on automation engineer, looking at how to improve manual >>processes. We often refer to as soil release engineer, deploying code to different environments or releasing it to customers. >>We're in operations. Engineer, ensuring an application functions >>inconsistent expected ways >>and no matter what role we play. We have to consider a number of issues. >>The first is test ability. All software systems require >>testing to assure architects >>that designs work developers that code works operators, that >>infrastructure is running as expected >>and engineers of all disciplines >>that code changes won't >>bring down the whole system testing >>in its many forms >>is what enables >>systems to be durable and have >>longevity. It's what reassures engineers that changes >>won't impact current functionality. A system without tests >>is a disaster waiting to happen. Which is why test ability >>is first among >>equals at this particular roundtable. Security is everyone's responsibility. But if you understand how to design and execute secure systems, I struggle with this security incidents for the most >>part are high impact, low >>probability events. The really big disasters, the one that the ones that end up on the news and get us all free credit reporting >>for a year. They don't happen super frequently and >>then goodness because you know that there are >>endless small >>vulnerabilities lurking in our systems. >>Security is something we all know we should dedicate time to but often don't make time for. >>And let's be honest, it's hard and >>complicated >>and a little scary. The cops. The first derivative of deVOPS asked engineers >>to move >>security left this approach. Mint security was a consideration >>early in the process, not something that would block >>release at the last moment. >>This is also the consideration under which I'm putting compliance >>and governance >>well not perfectly aligned. I figure all the things you have to call lawyers for should just live together. >>I'm kidding. But >>in all seriousness, these three concepts >>are really about >>risk management, >>identity, >>data, authorization. It doesn't really matter what specific issue you're speaking about. The question >>is who has access to what, when and how and that is everyone's responsibility at every stage, site, reliability, engineering or SRE is a discipline and job and approach for good reason, it is absolutely >>critical that >>applications and services work as expected. Most of the time. That said, availability is often mistakenly >>treated as a synonym >>for reliability. Instead, it's a single aspect of the concept if a system is available but customer data is inaccurate or out of sync. >>The system is >>not reliable, reliability has five key components, availability latency through but fidelity and durability, reliability >>is the end result. But resiliency for me is the journey the action engineers >>can take to improve reliability, observe ability is the ability to have insight into an application or >>system. It's the combination of telemetry and monitoring and alerting available to engineers >>and leadership. There's an aspect of observe ability that overlaps with reliability but the purpose of observe ability >>isn't just to maintain a reliable system though, that is of course important. It is the capacity for engineers working on a system to have visibility into the inner >>workings of that system. The concept of observe ability actually >>originates and linear >>dynamic systems. It's defined as how well internal states of a system can be understood based on information about its external outputs when it is critical when companies move systems to the cloud or utilize managed services that they don't lose visibility and confidence in their systems. The shared >>responsibility model >>of cloud storage compute and managed services >>require that engineering teams be able to quickly be alerted to identify and remediate >>issues as they arise, flexible systems are capable of >>adapting to meet the ever changing >>needs of the customer and the market segment, flexible code bases absorb new code smoothly. Embody a clean separation of concerns, are partitioned into small components or classes >>and architected to enable the Now as >>well as the next inflexible systems. Change dependencies are reduced or eliminated. Database schemas, accommodate change well components communicate via a standardized and well documented A. P. I. >>The only thing >>constant in our industry is >>change and every role we play, >>creating flexibility and solutions that can be >>flexible that will grow >>as the applications grow >>is absolutely critical. >>Finally, scalability scalability refers to more than a system's ability to scale for additional >>load. It implies growth >>scalability in the revolution model carries the continuous >>innovation of a team >>and the byproducts of that growth within a system. For me, scalability is the most human of the considerations. It requires each of us in our various roles >>to consider everyone >>around us, our customers who use the system or rely on its services, our colleagues, >>current and future with whom we collaborate and even our future selves. Mhm. >>Software development isn't a straight line, nor is it a perfect loop. >>It isn't ever changing complex dance. >>There are twirls and pivots and difficult spins >>forward and backward engineers move in parallel, creating truly magnificent pieces of art. We need a modern >>model for this modern >>era, and I believe this is just the >>revolution to get us started. Thank you so much for having me. Mm.

>>Welcome back to HPD discovered 2021. The virtual edition. My name is Dave Volonte and you're watching the cubes continuous coverage of H. P. S. Big customer event. Patrick Moorehead is here of moor insights and strategy is the number one analyst in the research analyst. Business. Patrick. Always a pleasure. Great to see you, >>David. Great to see you too. And I know you're you're up there fighting for that number one spot to. It's great to see you and it's great to see you in the meetings that were in. But it's even more fun to be here on the cube. I love to be on the cube and every once in a while you'll even call me a friend of the cube, >>unquestionably my friend and so and I can't wait second half. I mean you're traveling right now. We're headed to Barcelona to mobile World Congress later on this month. So so we're gonna we're gonna see each other face to face this year. 100%. So looking forward to that. So you know, let's get into it. Um you know, before we get into H. P. E. Let's talk a little bit about what you're seeing in the market. We've got, you know, we we finally, it feels like the on prem guys are finally getting their cloud act together. Um it's maybe taken a while, but we're seeing as a service models emerge. I think it's resonating with customers. The clearly not everything is moving to the cloud. There's this hybrid model emerging. Multi cloud is real despite what, you know, >>some some >>cloud players want to say. And then there's this edges like jump ball, what are you seeing in the marketplace? >>Yeah. Davis, as exciting as ever in. Just to put in perspective, I mean the public cloud has been around for about 10 years and still only 20% around 20% of the data in 20% of the applications are there now will be a very important ones and I'm certainly not a public cloud denier, I never have been, but there are some missing pieces that need to come together. And you know, even five years ago we were debating dave the hybrid cloud. And I feel like when amazon brought out outposts, the conversation was over right now, what you have is cloud native folks building out hybrid and on prem capabilities, you have a classic on, on prem folks building out hybrid and as a service capabilities. And I really think it boils down 22 things. I mean it's, it's wanting to have more flexibility and you know, I hate to use it because it sounds like a marketing word, but agility, the ability to spin up things and spin down things in a very, a quick way. And uh you know what they've learned, The veterans also know, hey, let's do this in a way that doesn't lock us in too much into a certain vendor. And I've been around for a long time. David and I'm a realist too. Well, you have to lock yourself into something. Uh it just depends on what do you want to lock yourself into, but super exciting and what H. P. E. You know, when they further acts in the sea with Green Lake, I think it was four years ago, uh I think really started to stir the pot. >>You know, you mentioned the term cloud denial, but you know, and I feel like the narrative from, I like to determine as I think you should use the term veteran. You know, it's very, they're ours is the only industry patrick where legacy is a pejorative, but so, but the point I want to make is I feel like there's been a lot of sort of fear from the veteran players, but, but I look at it differently, I wonder what your take is. I, I think, I think I calculated that the Capex spending by the big four public clouds including Alibaba last year was $100 billion. That's like a gift to the world. Here we're gonna spend $100 billion like the internet. Here you go build. And so I, and I feel like companies like HP are finally saying, yeah, we're gonna build, we're gonna build a layer and we're gonna hide the complexity and we're gonna add value on top. What do you think about that? >>Yeah. So I think it's now, I wish, I wish the on prem folks like HP, you would have done it 10 years ago, but I don't think anybody expected the cloud to be as big as it's become over the last 10 years. I think we saw companies like salesforce with sas taking off, but I think it is the right direction because there are advantages to having workloads on prem and if you add an as a service capability on top of the top of that, and let's say even do a Coehlo or a managed service, it's pretty close to being similar to the public cloud with the exception, that you can't necessarily swipe a credit card for a bespoke workload if you're a developer and it is a little harder to scale out. But that is the next step in the equation day, which is having, having these folks make capital expenditures, make them in a Polo facility and then put a layer to swipe a credit card and you literally have the public cloud. >>Yeah. So that's, that's a great point. And that's where it's headed, isn't it? Um, so let's, let's talk about the horses on the track. Hp as you mentioned, I didn't realize it was four years ago. I thought it was, wow, That's amazing. So everybody's followed suit. You see, Dallas announced, Cisco has announced, uh, Lenovo was announced, I think IBM as well. So we, so everybody's sort of following suit there. The reality is, is it's taken some time to get this stuff standardized. What are you seeing from, from HP? They've made some additional announcements, discover what's your take on all this. >>Yeah. So HPD was definitely the rabbit here and they were first in the market. It was good to see. First off some of their, Um, announcements on, on how it's going and they talked about $428 billion 1200 customers over 900 partners and 95% retention. And I think that's important. Anybody who's in the lead and remember what aws I used to do with the slide with the amount of customers would just get bigger and bigger and bigger and that's a good way to show momentum. I like the retention part two which is 95%. And I think that that says a lot uh probably the more important announcements that they made is they talked about the G. A. Of some of their solutions on Green Lake and whether it is A. S. A. P. Hana. Ml apps HPC with Francis, VD. I was Citrus and video but they also brought more of what I would call a vertical layer and I'm sure you've seen the vertical ization of all of these cloud and as a service workloads. But what they're doing with Epic, with EMR and looseness, with financial payments and Splunk and intel with data and risk analysis and finally, a full stack for telco five G. One of the biggest secrets and I covered this about five years ago is HPV actually has a full stack that Western european carriers use and they're now extending that to five G. And um, so more horizontal, uh, and, and more vertical. That was the one of the big swipes, uh, that I saw that there was a second though, but maybe we can talk about these. >>Yeah. Okay. Okay. So, so the other piece of that of course is standardization right there there because there was a, there was a, there was a lot of customization leading up to this and everybody sort of, everybody always had some kind of financial game they can play and say, hey, there's an adversary as a service model, but this is definitely more of a standardized scalable move that H P E. Is making with what they call Lighthouse. Right? >>Yeah, that's exactly right. And I've talked to some Green Lake customers and they obviously gave it kudos or they wouldn't have HP wouldn't have served them up and they wouldn't have been buying it. But they did say, um, it took, it took a while, took some paperwork to get it going. It's not 100% of push button, but that's partially because hp allows you to customize the hardware. You want a one off network adapter. Hp says yes, right. You want to integrate a different type of storage? They said yes. But with Green Lake Lighthouse, it's more of a, what you see is what you get, which by the way, is very much like the public cloud or you go to a public cloud product sheet or order sheet. You're picking from a list and you really don't know everything that's underneath the covers, aside from, let's say, the speed of the network, the type of the storage and the amount of the storage you get. You do get to pick between, let's say, an intel processor, Graviton two or an M. D processor. You get to pick your own GPU. But that's pretty much it. And HP Lighthouse, sorry, Green Lake Lighthouse uh is bringing, I think a simplification to Green Lake that it needs to truly scale beyond, let's say the White House customers that HP Yeah, >>Well done. So, you know, and I hear your point about we're 10 years in plus. And to me this is like a mandate. I mean, this is okay, good, good job guys about time. But if I had a, you know, sort of look at the big player, it's like we have an oligopoly here in this, in this business. It's HP, Cisco, you got Dell Lenovo, you've got, you know, IBM, they're all doing this and they all have a different little difference, you know, waste of skin of catch. And your point about simplicity, it seems like HP HP is all in antony's like, okay, here's what we're going to announce that, you know, a while ago. So, and they seem to have done a good job with Wall Street and they got a simple model, you know, Dell is obviously bigger portfolio, much more complicated. IBM is even more complicated than that. I don't know so much about Lenovo and in Cisco of course, has acquired a ton of SAAS companies and sort of they've got a lot of bespoke products that they're trying to put together. So they've got, but they do have SAS models. So each of them is coming at it from a different perspective. How do you think? And so and the other point we got lighthouse, which is sort of Phase one, get product market fit. Phase two now is scale, codify standardized and then phase three is the moat build your unique advantage that protects your business. What do you see as HP ES sort of unique value proposition and moat that they can build longer term. >>That's a great, great question. And let me rattle off kind of what I'm seeing that some of these players here, So Cisco, ironically has sells the most software of any of those players that you mentioned, uh with the exception of IBM um and yeah, C I >>CSDB two. Yeah, >>yeah, they're the they're the number two security player, uh Microsoft, number one, So and I think the evaluation on the street uh indicate that shows that I feel like Dell tech is a very broad play because not only do they have servers, storage, networking insecurity, but they also have Pcs and devices. So it's a it's a scale and end play with a focus on VM ware solutions, not exclusively of course. Uh And um then you've got Lenovo who is just getting into the as a service game and are gosh, they're doing great in hyper scale, they've got scale there vertically integrated. I don't know if if too many people talk about that, but Lenovo does a lot of their own manufacturing and they actually manufacture Netapp storage solutions as well. So yeah, each of these folks brings a different game to the table. I think with h P e, what you're bringing the table is nimble. When HP and HP split, the number one thing that I said was that ah, h P E is going to have to be so much faster than it offsets the scale that Dell technology has and the HBs credit, although there, I don't think we're getting credit for this in the stock market yet. Um and I know you and I are both industry folks, not financial folks, but I think their biggest thing is speed and the ability to move faster. And that is what I've seen as it relates to the moat, which is a unique uh competitive advantage. Quite frankly, I'm still looking for that day uh in in in what that is. And I think in this industry it's nearly impossible. And I would posit that that any, even the cloud folks, if you say, is there something that AWS can do that as your can't if it put it put its mind to it or G C P. I don't think so. I think it's more of a kind of land and expand and I think for H P E. When it comes to high performance computing and I'm not just talking about government installations, I'm talking about product development, drug development. I think that is a landing place where H P. E already does pretty well can come in and expand its footprint. >>You know, that's really interesting um, observations. So, and I would agree with you. It's kind of like, this is a copycat industry. It's like the west coast offense like the NFL, >>so, >>so the moat comes from, you know, brand execution and your other point about when HP and HP split, that was a game changer because all of a sudden you saw companies like them, you always had a long term relationship with H P E, but or HP, but then they came out of the woodworks and started to explode. And so it really opened up opportunities. So it really is a execution, isn't it? But go ahead please. >>Dave if I had to pick something that I think HP HPV needs to always be ahead in as a service and listen you and I both know announcements don't mean delivery, but there is correlation between if you start four years ahead of somebody that other company is going to have to put just, I mean they're going to have to turn that ship and many of its competitors really big ships to be able to get there. So I think what Antonio needs to do is run like hell, right? Because it, it I think it is in the lead and as a service holistically doesn't mean they're going to be there forever, but they have to stay ahead. They have to add more horizontal solutions. They have to add more vertical solutions. And I believe that at some point it does need to invest in some Capex at somebody like Anna Quinn X play credit card swiper on top of that. And Dave, you have the public, you have the public cloud, you don't have all the availability zones, but you have a public cloud. >>Yeah, that's going to happen. I think you're right on. So we see this notion of cloud expanding. It's no longer just remote set of services. Somewhere out in the cloud. It's like you said, outpost was the sort of signal. Okay, We're coming on prem. Clearly the on prem uh, guys are connecting to the cloud. Multi cloud exists, we know this and then there's the edge but but but that brings me to that sort of vision and everybody's laying out of this this this seamless integration hiding the complexity log into my cloud and then life will be good. But the edge is different. Right? It's not just, you know, retail store or a race track. I mean there's the far edge, there's the Tesla car, there's gonna be compute everywhere and that sort of ties into the data. The data flows, you know the real time influencing at the edge ai new semiconductor models. You you came out of the semiconductor industry, you know it inside and out arm is exploding, dominating in the edge with apple and amazon Alexa and things like that. That's really where the action is. So this is a really interesting cocktail and soup that we have going on. How do >>you say? Well, you know, Dave if the data most data, I think one thing most everybody agrees on is that most of the data will be created on the edge, whether that's a moving edge a car, a smartphone or what I call an edge data center without tile flooring. Like that server that's bolted to the wall of Mcdonald's. When you drive through, you can see it versus the walmart. Every walmart has a raised tile floor. It's the edge to economically and performance wise, it doesn't make any sense to send all that data to the mother ships. Okay. And whether that's unproven data center or the giant public cloud, more efficient way is to do the compute at the closest way possible. But what it does, it does bring up challenges. The first challenge is security. If I wanted to, I could walk in and I could take that server off the Mcdonald's or the Shell gas station wall. So I can't do that in a big data center. Okay, so security, physical security is a challenge. The second is you don't have the people to go in there and fix stuff that are qualified. If you have a networking problem that goes wrong in Mcdonald's, there's nobody there that can help uh they can they can help you fix that. So this notion of autonomy and management and not keeping hyper critical data sitting out there and it becomes it becomes a security issue becomes a management issue. Let me talk about the benefits though. The benefits are lower latency. You want you want answers more quickly when that car is driving down the road And it has a 5GV 2 x communication cameras can't see around corners. But that car communicating ahead, that ran into the stop sign can, through Vita X talked to the car behind it and say, hey, something is going on there, you can't go to, you can't go to the big data center in the sky, let's make that happen, that is to be in near real time and that computer has to happen on the edge. So I think this is a tremendous opportunity and ironically the classic on prem guys, they own this, they own this space aside from smartphones of course, but if you look at compute on a light pole, companies like Intel have built complete architecture is to do that, putting compute into five G base stations, heck, I just, there was an announcement this week of google cloud and its gaming solution putting compute in a carrier edge to give lower latency to deliver a better experience. >>Yeah, so there, of course there is no one edge, it's highly fragmented, but I'm interested in your thoughts on kinda whose stack actually can play at the edge. And I've been sort of poking uh H P E about this. And the one thing that comes back consistently is Aruba, we we could take a room but not only to the, to the near edge, but to the far edge. And and that, do you see that as a competitive advantage? >>Oh gosh, yes. I mean, I would say the best acquisition That hp has made in 10 years has been aruba, it's fantastic and they also managed it in the right way. I mean it was part of HB but it was, it was managed a lot more loosely then, you know, a company that might get sucked into the board and I think that paid off tremendously. They're giving Cisco on the edge a absolute run for their money, their first with new technologies, but it's about the solution. What I love about what a ruble looks at is it's looking at entertainment solutions inside of a stadium, a information solution inside of an airport as opposed to just pushing the technology forward. And then when you integrate compute with with with Aruba, I think that's where the real magic happens. Most of the data on a permanent basis is actually video data. And a lot of it's for security, uh for surveillance. And quite frankly, people taking videos off, they're off their smartphones and downloaded video. I I just interviewed the chief network officer of T mobile and their number one bit of data is video, video uploaded, video download. But that's where the magic happens when you put that connectivity and the compute together and you can manage it in a, in an orderly and secure fashion. >>Well, I have you we have a ton of time here, but I I don't pick your brain about intel the future of intel. I know you've been following it quite closely, you always have Intel's fighting a forefront war, you got there battling a. M. D. There, battling your arm slash and video. They're they're taking on TSMC now and in foundry and, and I'll add china for the looming threat there. So what's your prognosis for for intel? >>Yeah, I liked bob the previous Ceo and I think he was doing a lot of of the right things, but I really think that customers and investors and even their ecosystem wanted somebody leading the company with a high degree of technical aptitude and Pat coming, I mean, Pat had a great job at VM or, I mean he had a great run there and I think it is a very positive move. I've never seen the energy at Intel. Probably in the last 10 years that I've seen today. I actually got a chance to talk with Pat. I visited Pat uhh last month and and talk to him about pretty much everything and where he wanted to take the company the way you looked at technology, what was important, what's not important. But I think first off in the world of semiconductors, there are no quick fixes. Okay. Intel has a another two years Before we see what the results are. And I think 2023 for them is gonna be a huge year. But even with all this competition though, Dave they still have close to 85% market share in servers and revenue share for client computing around 90%. Okay. So and they built out there networking business, they build out a storage business um with obtain they have the leading Aid as provider with Mobileye. And and listen I was I was one of Intel's biggest, I was into one of Intel's biggest, I was Intel's biggest customer when I was a compact. I was their biggest competitor at A. M. B. So um I'm not obviously not overly pushing or there's just got to wait and see. They're doing the right things. They have the right strategy. They need to execute. One of the most important things That Intel did is extend their alliance with TSMC. So in 2023 we're going to see Intel compute units these tiles they integrate into the larger chips called S. O. C. S. B. Manufactured by TSMC. Not exclusively, but we could see that. So literally we could have AMG three nanometer on TSMC CPU blocks, competing with intel chips with TSMC three nanometer CPU blocks and it's on with regard to video. I mean in video is one of these companies that just keeps going charging, charging hard and I'm actually meeting with Jensen wang this week and Arm Ceo Simon Segers to talk about this opportunity and that's a company that keeps on moving interestingly enough in video. If the Arm deal does go through will be the largest chip license, see CPU licensee and have the largest CPU footprint on on the planet. So here we have A and D. Who's CPU and Gpu and buying an F. P. G. A company called Xilinx, you have Intel, Cpus, Gpus machine learning accelerators and F. P. G. S and then you've got arms slashing video bit with everything as well. We have three massive ecosystems. They're gonna be colliding here and I think it's gonna be great for competition date. Competition is great. You know, when there's not competition in Cpus and Gpus, we know what happens, right. Uh, the B just does not go on and we start to stagnate. And I did, I do feel like the industry on CPU started to stagnate when intel had no competition. So bring it on. This is gonna be great for for enterprises then customers to, and then, oh, by the way, the custom Chip providers, WS has created no less than 15 custom semiconductors started with networking uh, and, and nitro and building out an edge that surrounded the general compute and then it moved to Inferential to for inference trainee um, is about to come out for training Graviton and gravitas to for general purpose CPU and then you've got Apple. So innovation is huge and you know, I love to always make fun of the software is eating the world. I always say yeah but has to run on something. And so I think the combination of semiconductors, software and cloud is just really a magical combination. >>Real quick handicap the video arm acquisition. What what are the odds that that they will be successful? They say it's on track. You've got to 2 to 13 to 1 10 to 1. >>I say 75%. Yes 25%. No China is always the has been the odd odd man out for the last three years. They scuttled the qualcomm NXP deal. You just don't know what china is going to do. I think the Eu with some conditions is gonna let this fly. I think the U. S. Is absolutely going to let this fly. And even though the I. P. Will still stay over in the UK, I think the U. S. Wants to see, wants to see this happen. Japan and Korea. I think we'll allow this china is the odd man out. >>In a word, the future of H. P. E. Is blank >>as a service >>patrick Moorehead. Always a pleasure my friend. Great to see you. Thanks so much for coming back in the cube. >>Yeah, Thanks for having me on. I appreciate that. >>Everybody stay tuned for more great coverage from HP discover 21 this is day Volonte for the cube. The leader and enterprise tech coverage. We'll be right back. >>Mm.

>>Welcome back to Vienna on 2021 you're watching the Cube and my name is Dave Volonte. You know, the last 10 years of cloud, they were largely about spinning up virtualized compute infrastructure and accessing cheap and simple object storage and some other things like networking. The cloud was largely though a set of remote resources that simplify deployment and supported the whole spate of native applications that have emerged to power the activity of individuals and businesses the next decade, however, promises to build on the troves of data that live in the cloud, make connections to on premises applications and support new application innovations that are agile, iterative, portable and span resources in all in all the clouds, public clouds, private clouds, cross cloud connections all the way out to the near and far edge. In a linchpin of this new application development model is container platforms and container orchestration, which brings immense scale and capability to technology driven organizations, especially as they have evolved from supporting stateless applications to underpinning mission critical workloads as such containers bring complexities and risks that need to be addressed, not the least of which is protecting the massive amounts of data that are flowing through these systems. And with me to discuss these exciting and challenging trends or Danny Allen, who's the ceo of in and Niraj Tolia, the president at Kasten Bivins gentlemen welcome to the cube. >>Thank you delighted to be here with you Dave. >>Likewise, very excited to be a Dave. >>Okay, so Danny big M and a move. Great little acquisition. You're now seeing others try to make similar moves. Why what did you see in cast in? What was the fit? Why'd you make that move? >>Well, I think you nailed it. Dave's. We've seen an evolution in the infrastructure that's being used over the last two decades. So if you go back 20 years, there was a massive digital transformation to enable users to be self service with digital applications. About 2000 or so, 2010, everything started being virtualized. I know virtualization came along before that but virtualization really started to take off because it gave return on investment and gave flexibility all kinds of benefits. But now we're in a third wave which is built on containers. And the amazing thing about containers is that as you said, it allows you to connect multi cloud, hybrid cloud the edge to the core. And they're designed for the consumption world. If you think about the cloud, you can provision things deep provisions things. That's the way that containers are designed the applications and so because they're designed for a consumption based world because they are designed for portability across all of these different infrastructures, it only made sense for us to invest in the industry's leading provider of data protection for kubernetes. And that of course is costume, >>there's some garage, I mean take us back. I mean, you know, container has been around forever. But then, you know, they started to, you know, hit go mainstream and and and and at first, you know, they were obviously ephemeral, stateless apps, kind of lightweight stuff. But but you at the time you and the team said, okay, these are gonna become more complex microservices. Maybe so micro, but you had to have the vision and you made a bet uh maybe take us back to sort of how you saw that and where where's containers have have come from? >>Sure. So let's rewind the clock right. As you said, containers, old technology in the same way virtualization started with IBM mainframes, right, containers in different forms have been around for a while. But I think when the light bulb went off for me was very early days in 2015 when my engineering team, a previous company started complaining. And the reason they were complaining about different other engineering groups and the reason they were complaining was because the right things, things were coming together sooner. We're identifying things sooner. And that's when I said, this is going to be the next wave of infrastructure. The same way watch a light virtualization revolutionized how people built deployed apps. We saw that with containers and in particular in those days we made that bet on commodities. Right? So we said from first Principles and that's where you know, you had other things like Docker, swarm esos, etcetera and we said community, that's going to be the way to go because it is just so powerful and it is, you know, at the end of the day, what we all do is infrastructure. But what we saw was that containers optimizing for the developer, they were optimizing for the people that really build applications, deliver value to all of their and customers. And that is what made us see that even though the initially we only saw stateless applications state will was going to happen because there's just so much momentum behind it And the writing for us at least was on the wall. And that's how we started off on this journey in 2017. >>What are the unique nuances and differences really in terms of protecting containers from a, from a technical standpoint, what what's different? >>So there are a couple of subtle things. Right again, the jokers, you know, I say, is that I'm a recovering infrastructure person have always worked in infrastructure systems in the past and recovering them. But in this case we really had to flip things around right. I've come at it from the cloud disks volumes. VMS perspective, in this case to do the right thing by the customer needed a clean slate approach of coming out from the application down. So what we look at is what does the application look like? And that means protecting, not just the stuff that sits on disk, what your secrets in networking information, all those hundreds of pieces that make up a cloud native application and that involves scale challenges, work, visualisation challenges for admins, KPI So all of that shifts in a very dramatic way. >>So Danny, I mean typically VM you guys haven't done a ton of acquisitions, uh, you've grown organically. So now you, you, you poppin cast in, what does that mean for you from a platform perspective? You know, IBM has this term blue washing when they buy a company did you green wash cast and how did that all work? And again, what does what does it mean from the, from the platform perspective? >>Well, so our platform is designed for this type of integration and the first type of integration we do with any of our technologies because we do have native technologies, if you think about what we do being back up for AWS for Azure, for G C p, we have backup for Acropolis Hyper Visor. These are all native purpose built solutions for those environments and we integrate with what we call being platform services. And one of the first steps that we do of course is we take the data from those native solutions and send it into the repository and the benefit that you get from that is that you have this portable, self describing format that you can move around the vein platform. And so the platform was already designed for this Now. We already showed this at demon. You saw this on the main stage where we have this integration at a data level but it goes beyond that beam platform services allows us to do not just day one operations, but day two operations. Think about um updating the components of those infrastructures or those software components that also allows reporting. So for example you can report on what is protected, what's not protected. So the platform was already designed for this integration model. But the one thing I want to stress is we will always have that stand alone product for kubernetes for uh you know, for the container world. And the reason for that is the administrator for Kubernetes wants their own purpose build solution. They want it running on kubernetes. They want to protect the uniqueness of their infrastructure. If you think about a lot of the container based systems there, They're using structured data. Non structured data. Sure. But they're also using object based storage. They're using message queues. And so they have their nuances. And we want to maintain that in a stand alone product but integrated back into the Corvin platform. >>So we do these we have a data partner called GTR Enterprise Technology Research. They do these quarterly surveys and and they have this metric called net score is a measure of spending momentum and for the last, I don't know, 8, 10, 12 quarters the big four have been robotic process automation. That's hot space. Cloud obviously is hot and then A I of course. And but containers and container orchestration right up there. Those are the Big four that outshine everything else, even things like security and other infrastructure etcetera. So that's good. I mean you guys skating to the puck back in 2015 rush, you've made some announcements and I'm and I'm wondering sort of how they fit into the trends in the industry. Uh, what what's, what's significant about those announcements and you know, what's new that we need to know about. >>Sure. So let me take that one day. So we've made a couple of big interesting announcement. The most recent one of those was four dot release after casting by women platform, right? We call it kitten and right. We've known rate since a couple of weeks colonial pipeline ransom. Where has been in the news in the US gas prices are being driven up because of that. And that's really what we're seeing from customers where we are >>seeing this >>increase in communities adoption today. We have customers from the world's largest banks all the way to weakly connected cruise ships that one could burn. It is on them. People's data is precious. People are running a large fleet of notes for communities, large number of clusters. So what we said is how do you protect against these malicious attacks that want to lock people out? How do you bring in mutability so that even someone with keys to the kingdom can't go compromise your backups and restores, right? So this echoes a lot of what we hear from customers and what we hear about in the news so well protected that. But we still help through to some of the original vision behind cast. And that is, it's not just saying, hey, I give you ransomware protection. We'll do it in such an easy way. The admin barely notices. This new feature has been turned on if they wanted Do it in a way that gives them choice right. If you're running in a public cloud, if you're running at the edge you have choice of infrastructure available to you and do it in a way that you have 100% automation when you have 100 clusters when you deploy on ships, right, you're not going to be able to have we spoke things. So how do you hook into CHED pipelines and make the job of the admin easier? Is what we focused on in that last >>night. And and that's because you're basically doing this at the point of writing code and it's essentially infrastructure as code. We always talk about, you know, you want to you don't want to bolt on data protection as an afterthought, but that's what we've done forever. Uh This you can't >>so in fact I would say step before that day, right are the most leading customers we work with. Right to light up one of the U. S. Government's largest contractors. Um Hey do this before the first line of code is written right there on the scalp cloud as an example. But with the whole shift left that we all hear the cube talks a lot about. We see at this point where as you bring up infrastructure, you bring up a complete development environment, a complete test environment. And within that you want to deploy security, you want to deploy backup your to deploy protection at day zero before the developer in so it's the first line of cordon. So you protected every step of the journey while trying to bolt it on the sound. Seemingly yes, I stitched together a few pieces of technology but it fundamentally impacts how we're going to build the next generation of secure applications >>Danny, I think I heard you say or announced that this is going to be integrated into Wien backup and replication. Um can you explain what that took? Why? That's important. >>Yeah. So the the timeline on this and when we do integrations from these native solutions into the core platform, typically it begins with the data integration, in other words, the data being collected by the backup tool is sent to a repository and that gives us all the benefits of course of things like instant recovery and leveraging, de doop storage appliances and all of that step to typically is around day to operations, things like pushing out updates to that native solutions. So if you look at what we're doing with the backup for AWS and Azure, we can deploy the components, we can deploy the data proxies and data movers. And then lastly there's also a reporting aspect to this because we want to centralize the visibility for the organization across everywhere. So if your policy says hey I need two weeks of backups and after two weeks and I need weekly backups for X amount of time. This gives you the ability to see and manage across the organization. So what we've demonstrated already is this data level integration between the two platforms and we expect this to continue to go deeper and deeper as we move forward. The interesting thing right now is that the containers team often is different than the standard data center I. T. Team but we are quickly seeing the merge and I think the speed of that merging will also impact how quickly we integrate them within our platform. >>Well I mean obviously you see this for cloud developers and now you're bringing this to any developers and you know, if I'm a developer and I'm living in an insurance company, I've been, you know, writing COBOL code for a while, I want to be signed me up. I want to get trained on this, right? Because it's gonna I'm gonna become more valuable. So this is this is where the industry is headed. You guys talk about modern data protection. I wondered if you could you could paint a picture for us of sort of what what this new world of application development and deployment and and data protection looks like and how it's different from the old world. >>Mhm. So I think that if you mentioned the most important word, which is developer, they come first, they are the decision makers in this environment, the other people that have the most bull and rightly so. Oh, so I think that's the biggest thing at the cultural level that is, developers are saying this is what we want and this is what we need to get the job done, we want to move quickly. So some of the things are let's not slow them down. Let's enable them, let's give them any P I to work with. Right? No. Where in bulk of production, use will be api based versus EY base. Let's transparently integrate into the environment. So therefore protection for security, they need zero lines have changed code. Mm So those are some of the ways we approach things. Now when you go look at the requirements of the developers, they said I have a Ci cd pipeline to integrate into that. I have a development pipeline to integrate into that. I deploy across multiple clouds sometimes. Can you integrate into that and work seamlessly across all those environments? And we see those category of us coming up over and over again from people. >>So the developer rights once and it doesn't have to worry about where it's running. Uh it's got the right security, there are a protection and those policies go with it, so that's that's definitely a different world. Um Okay, last question. Uh maybe you guys could each give your opinion on sort of where we're headed, uh what we can expect from the the acquisition, the the integration, what should we look forward to and what should we pay attention to? >>Well, the one obvious thing that you're going to see is tremendous growth on the company's side and that's because Kubernetes is taking off cloud is taking off um SaAS is taking off and so there's obvious growth there. And one of the things that were clearly doing is um we're leveraging the power of of, you know, a few 1000 sales people to bring this out to market. Um, and so there is emerging of of sales and marketing activities and leveraging that scale. But what you shouldn't expect to see anything different on is this obsessive focus on the product, on quality, on making sure that we're highly differentiated that we have a product that the company that our customers and companies actually need no garage. >>Yeah. So I'll agree with everything down, he said. But a couple of things. Excite me a lot. Dave we've been roughly eight months or so since acquisition and I particularly love how last what in this quarter have gone in terms of how we focuses on solving customer problems. All right. So we'll always have that independent support for a cloud date of customers, but I'm excited about not just working with the broadest side of customers and as we scale the team that's going to happen, but providing a bridge to all the folks that grew up in the virtualization world, right? Grew up in the physical wall of physical service, etcetera and saying, how do we make it easy for you to come over to this new container Ization world? What is the on ramps bridging that gap serving as the on ramp? And we're doing a lot of work there from the product integration and independent product features that just make it easy. Right? And we're already seeing feel very good feedback for that from the field right now. >>I really like your position. I just dropped my quarterly cloud update. I focused, I look at the Big Four, the Big Four last year, spent $100 billion on Capex. And I always say that is a gift to companies like yours because you can be that connection point between the virtualization crowd, the on prem cloud, any cloud. Eventually we'll be, we'll be more than just talking about the Edge will actually be out there, you know, doing real work. Uh, and I just see great times ahead for you guys. So thanks so much for coming on the cube explaining this really exciting new area. Really appreciate it. >>Thank you so much. >>Thank you everybody for watching this day. Volonte for the Cube and our continuous coverage of the mon 2021, the virtual edition. Keep it right there. >>Mm mm mm

>>Hi lisa martin here with the cubes coverage of demon 2021. I've got to alumni joining me. Please welcome back to the cube Danny. Alan beam's ceo Danny. It's great to see you. >>I am delighted to be here lisa. >>Excellent brian Schwartz is here as well. Google director outbound product management brian welcome back to the program. Uh >>thanks for having me again. Excited to be >>here. Excited to be here. Yes, definitely. We're gonna be talking all about what Demon google are doing today. But let's go ahead and start Danny with you. Seems vision is to be the number one trusted provider of backup and recovery solutions for the, for for modern data protection. Unpack that for me, trust is absolutely critical. But when you're talking about modern data protection to your customers, what does that mean? >>Yeah. So I always, I always tell our customers there's three things in there that are really important. Trust is obviously number one and google knows this. You've been the most trusted search provider uh, forever. And, and so we have 400,000 customers. We need to make sure that our products work. We need to make sure they do data protection, but we need to do it in a modern way. And so it's not just back up and recovery, that's clearly important. It's also all of the automation and orchestration to move workloads across infrastructures, move it from on premises to the google cloud, for example, it also includes things like governance and compliance because we're faced with ransomware, malware and security threats. And so modern data protection is far more than just back up. It's the automation, it's the monitoring, it's a governance and compliance. It's the ability to move workloads. Um, but everything that we look at within our platform, we focus on all of those different characteristics and to make sure that it works for our customers. >>One of the things that we've seen in the last year, Danny big optic in ransom were obviously the one that everyone is the most familiar with right now. The colonial pipeline. Talk to me about some of the things that the team has seen, what your 400,000 customers have seen in the last 12 months of such a dynamic market, a massive shift to work from home and to supporting SAS for clothes and things like that. What have you seen? >>Well, certainly the employees working from home, there's a massive increase in the attack surface for organizations because now, instead of having three offices, they have, you know, hundreds of locations for their end users. And so it's all about protecting their data at the same time as well. There's been this explosion in malware and ransomware attacks. So we really see customers focusing on three different areas. The first is making sure that when they take a copy of their data, that it is actually secure and we can get into, you know, a mutability and keeping things offline. But really taking the data, making sure it's secure. The second thing that we see customers doing is monitoring their environment. So this is both inspection of the compute environment and of the data itself. Because when ransomware hits, for example, you'll see change rates on data explode. So secure your data monitor the environment. And then lastly make sure that you can recover intelligently is let us say because the last thing that you want to do if you're hit by ransomware is to bring the ransomware back online from a backup. So we call this security cover re secure, restore. We really see customers focusing on those three areas >>And that restoration is critical there because as we know these days, it's not if we get hit with ransomware, it's really a matter of when. Let's go ahead now and go into the google partnership, jenny talked to me about it from your perspective, the history of the strength of the partnership, all that good stuff. >>Yeah. So we have a very deep and long and lengthy relationship with google um, on a number of different areas. So for example, we have 400,000 customers. Where do they send their backups? Most customers don't want to continue to invest in storage solutions on their premises. And so they'll send their data from on premises and tear it into google cloud storage. So that's one integration point. The second is when the running workloads within the clouds. So this is now cloud native. If you're running on top of the google cloud platform, we are inside the google America place and we can protect those workloads. A third area is around the google vm ware engine, there's customers that have a hybrid model where they have some capacity on premises and some in google using the VM ware infrastructure and we support that as well. That's a third area and then 1/4 and perhaps the longest running um, google is synonymous with containers and especially kubernetes, they were very instrumental in the foundations of kubernetes and so r K 10 product which does data protection for kubernetes is also in the google America place. So a very long and deep relationship with them and it's to the benefit of our customers. >>Absolutely. And I think I just saw the other day that google celebrated the search engine. It's 15th birthday. I thought what, what did we do 16 years ago when we couldn't just find anything we wanted brian talked to me about it from Google's perspective of being partnership. >>Yeah, so as Danny mentioned, it's really multifaceted, um it really starts with a hybrid scenario, you know, there's still a lot of customers that are on their journey into the cloud and protecting those on premises workloads and in some senses, even using beams capabilities to move data to help migrate into the cloud is I'd say a great color of the relationship. Um but as Danny mentioned increasingly, more and more primary applications are running in the cloud and you know, the ability to protect those and have, you know, the great features and capabilities, uh you know, that being provides, whether it be for GCB er VM where you know, capability and google cloud or things like G k e R kubernetes offering, which has mentioned, you know, we've been deep and wide in kubernetes, we really birthed it many, many years ago um and have a huge successful business in, in the managing and hosting containers, that having the capabilities to add to those. It really adds to our ecosystem. So we're super excited about the partnership, we're happy to have this great foundation to build together with them into the future. >>And Danny Wien launched, just been in february a couple of months ago, being backup for google cloud platform. Talk to us about that technology and what you're announcing at them on this year. >>Yeah, sure. So back in february we released the first version of the VM backup for G C p product in the marketplace and that's really intended to protect of course, i as infrastructure as a service workloads running on top of G C p and it's been very, very successful. It has integration with the core platform and what I mean by that is if you do a backup in G C P, you can do you can copy that back up on premises and vice versa. So it has a light integration at the data level. What we're about to release later on this summer is version two of that product that has a deep integration with the VM platform via what we call the uh team service platform, a PS themselves. And that allows a rich bidirectional uh interaction between the two products that you can do not just day one operations, but also day to operations. So you can update the software, you can harmonize schedules between on premises and in the cloud. It really allows customers to be more successful in a hybrid model where they're moving from on premises to the cloud. >>And that seems to be really critically important. As we talk about hybrid club all the time, customers are in hybrid. They're living in the hybrid cloud for many reasons, whether it's acquisition or you know, just the nature of lines of business leveraging their cloud vendor of choice. So being able to support the hybrid cloud environment for customers and ensure that that data is recoverable is table stakes these days. Does that give them an advantage over your competition Danny? >>It does. Absolutely. So customers want the hybrid cloud experience. What we find over time is they do trend towards the cloud. There's no question. So if you have the hybrid experience, if they're sending their data there, for example, a step one, step two, of course, is just to move the workload into the cloud and then step three, they really start to be able to unleash their data. If you think about what google is known for, they have incredible capabilities around machine learning and artificial intelligence and they've been doing that for a very long time. So you can imagine customers after they start putting their data there, they start putting their workloads here, they want to unlock it into leverage the insights from the data that they're storing and that's really exciting about where we're going. It's, they were early days for most customers. They're still kind of moving and transitioning into the cloud. But if you think of the capabilities that are unlocked with that massive platform in google, it just opens up the ability to address big challenges of today, like climate change and sustainability and you know, all the health care challenges that we're faced with it. It really is an exciting time to be partnered with Google >>Ryan. Let's dig into the infrastructure in the architecture from your perspective, help us unpack that and what customers are coming to you for help with. >>Yeah. So Danny mentioned, you know the prowess that google has with data and analytics and, and a, I I think we're pretty well known for that. Uh, there's a tremendous opportunity for people in the future. Um, the thing that people get just right out of the box is the access to the technology that we built to build google cloud itself. Just the scale and, and technology, it's, you know, it's, it's a, you know, just incredible. You know, it's a fact that we have eight products here at google that have a billion users and when you have, you know, most people know the search and maps and gmail and all these things. When you have that kind of infrastructure, you build a platform like google cloud platform and you know, the network as a perfect example, the network endpoints, they're actually close to your house. There's a reason our technology is so fast because you get onto the google private network, someplace really close to where you actually live. We have thousands and thousands of points of presence spread around the world and from that point forward you're riding on our internal network, you get better quality of service. Uh the other thing I like to mention is, you know, the google cloud storage, that team is built on our object storage. It's uh it's the same technology that underpins Youtube and other things that most people are familiar with and you just think about that for a minute, you can find the most obscure Youtube video and it's gonna load really fast. You know, you're not going to sit there waiting for like two minutes waiting for something to load and that same under underlying technology underpins GCS So when you're going to go and you know, go back to an old restore, you know, to do a restore, it's gonna load fast even if you're on one of the more inexpensive storage classes. So it's a really nice experience for data protection. It has this global network properties you can restore to a different region if there was ever a disaster, there's just the scale of our foundation of infrastructure and also, you know, Danny mentioned if we're super proud about the investments that google has made for sustainability, You know, our cloud runs on 100% renewable energy at the cloud at our scale. That's a lot of, that's a lot of green energy. We're happy to be one of the largest consumers of green energy out there and make continued investments in sustainability. So, you know, we think we have some of the greenest data centers in the world and it's just one more benefit that people have when they come to run on Google Cloud. >>I don't know what any of us would do without google google cloud platform or google cloud storage. I mean you just mentioned all of the enterprise things as well as the at home. I've got to find this really crazy, obscure youtube video but as demanding customers as we are, we want things asAP not the same thing. If you know, an employee can't find a file or calendar has been deleted or whatnot. Let's go in to finish our time here with some joint customer use case examples. Let's talk about backing up on prem workloads to google cloud storage using existing VM licensing Danny. Tell us about that. >>Yeah. So one of the things that we've introduced at beam is this beam, universal licensing and it's completely portable license, you can be running your workloads on premises now and on a physical system and then you can, you know, make that portable to go to a virtual system and then if you want to go to the cloud, you can send that data up to the work load up to the cloud. One of the neat things about this transition for customers from a storage perspective, we don't charge for that. If you're backing up a physical system and sending your your back up on premises, you know, we don't charge for that. If you want to move to the cloud, we don't charge for that. And so as they go through this, there's a predictability and and customers want that predictability so much um that it's a big differentiating factor for us. They don't want to be surprised by a bill. And so we just make it simple and seamless. They have a single licensing model and its future proof as they move forward on the cloud journey. They don't have to change anything. >>Tell me what you mean by future proof as a marketer. I know that term very well, but it doesn't mean different things to different people. So for means customers in the context of the expansion of partnership with google the opportunities, the choices that you're giving customers to your customers, what does future proof actually delivered to them? >>It means that they're not locked into where they are today. If you think about a customer right now that's running a workload on premises maybe because they have to um they need to be close to the data that's being generated or feeding into that application system. Maybe they're locked into that on premises model. Now they have one of two choices when their hardware gets to the end of life. They can either buy more hardware which locks them into where they are today for the next three years in the next four years Or they can say, you know what, I don't want to lock into that. I want to model the license that is portable that maybe 12 months from now, 18 months from now, I can move to the cloud and so it future proof some, it doesn't give them another reason to stay on premises. It allows them the flexibility that licensing is taken off the table because it moves with you that there's zero thought or consideration and that locks you into where you are today. And that's exciting because it unlocks the capabilities of the cloud without being handicapped if you will by what you have on premises. >>Excellent. Let's go to the second uh use case lift and shift in that portability brian. Talk to us about it from your perspective. >>Yeah, so we obviously constantly in discussions with our customers about moving more applications to the cloud and there's really two different kind of approach is the lift and shift and modernization. You know, do you want to change and run on kubernetes when you come to the cloud as you move it in? In some cases people want to do that or they're gonna obviously build a new application in the cloud. But increasingly we see a lot of customers wanting to do lift and shift, they want to move into the cloud relatively quickly. As Danny said, there's like compelling events on like refreshes and in many cases we've had a number of customers come to us and say look we're going to exit our data centers. We did a big announcement Nokia, they're gonna exit 50 data centers in the coming years around the world and just move that into the cloud. In many cases you want to lift and shift that application to do the migration with his little change as possible. And that's one of the reasons we've really invested in a lot of enterprise, more classic enterprise support type technologies. And also we're super excited to have a really wide set of partners and ecosystem like the folks here at Wien. So the customers can really preserve those technologies, preserve that operational experience that they're already familiar with on prem and use that in the cloud. It just makes it easier for them to move to the cloud faster without having to rebuild as much stuff on the way in. >>And that's critical. Let's talk about one more use case and that is native protection of workloads that run on g c p Danny. What are you enabling customers to do there? >>Well? So we actually merged the capabilities of two different things. One is we leverage the native Api is of G C p to take a snapshot and we merge that with our ability to put it in a portable data format. Now. Why is that important? Because you want to use the native capabilities of G CPU want to leverage those native snapshots. The fastest way to recover a file or the fastest way to recover of'em is from the G C p snapshot. However, if you want to take a copy of that and move it into another locale or you want to pull it back on premises for compliance reasons or put it in a long term storage format, you probably want to put it in GCS or in our portable storage format. And so we merge those two capabilities, the snapshot and back up into a single product. And in addition to that, one of the things that we do, again, I talked about predictability. We tell customers what that policy is going to cost them because if for example a customer said, well I like the idea of doing my backups in the cloud, but I want to store it on premises. We'll tell them, well if you're copying that data continually, you know what the network charges look like, What the CPU and compute charges look like, What do the storage costs looks like. So we give them the forecast of what the cost model looks like even before they do a single backup. >>That forecasting has got to be key, as you said with so much unpredicted things that we can't predict going on in this world the last year has taught us that with a massive shift, the acceleration of digital business and digital transformation, it's really critical that customers have an idea of what their costs are going to be so that they can make adjustments and be agile as they need the technology to be. Last question Bryant is for you, give us a view uh, and all the V mon attendees, what can we expect from the partnership in the next 12 >>months? You know, we're excited about the foundation of the partnership across hybrid and in cloud for both VMS and containers. I think this is the real beginning of a long standing relationship. Um, and it's really about a marriage of technology. You think about all the great data protection and orchestration, all the things that Danny mentioned married with the cloud foundation that we have at scale this tremendous network. You know, we just signed a deal with SpaceX in the last couple of days to hook their satellite network up to the google cloud network, you know, chosen again because we just have this foundational capability to push large amounts of data around the world. And that's you know, for Youtube. We signed a deal with Univision, same type of thing, just massive media uh, you know, being pushed around the world. And if you think about it that that same foundation is used for data protection. Data protection. There's a lot of data and moving large sets of data is hard. You know, we have just this incredible prowess and we're excited about the future of how our technology and beans. Technology is going to evolve over time >>theme and google a marriage of technology Guys, thank you so much for joining me, sharing what's new? The opportunities that demand google are joined me delivering to your joint customers. Lots of great step. We appreciate your time. >>Thanks lisa >>For Danielle in and Brian Schwartz. I'm Lisa Martin. You're watching the cubes coverage of Lehman 2021.

>>mhm Yes, Welcome back to the cubes coverage of red hat summit 2021 virtual, which we were in person this year but we're still remote. We still got the Covid coming around the corner. Soon to be in post. Covid got a great guest here, Clayton Coleman architect that red hat cuba love and I've been on many times expanded role again this year. More cloud, more cloud action. Great, great to see you. Thanks for coming on. >>It's a pleasure >>to be here. So great to see you were just riffing before we came on camera about distributed computing uh and the future of the internet, how it's all evolving, how much fun it is, how it's all changing still. The game is still the same, all that good stuff. But here at Red had some and we're gonna get into that, but I want to just get into the hard news and the real big, big opportunities here you're announcing with red hat new managed cloud services portfolio, take us through that. >>Sure. We're continuing to evolve our open shift managed offerings which has grown now to include um the redhead open shift service on amazon to complement our as your redhead open shift service. Um that means that we have um along with our partnership on IBM cloud and open ship dedicated on both a W S and G C P. We now have um managed open shift on all of the major clouds. And along with that we are bringing in and introducing the first, I think really the first step what we see as uh huh growing and involving the hybrid cloud ecosystem on top of open shift and there's many different ways to slice that, but it's about bringing capabilities on top of open shift in multiple environments and multiple clouds in ways that make developers and operation teams more productive because at the heart of it, that's our goal for open shift. And the broader, open source ecosystem is do what makes all of us safer, more, uh, more productive and able to deliver business value? >>Yeah. And that's a great steak you guys put in the ground. Um, and that's great messaging, great marketing, great value proposition. I want to dig into a little bit with you. I mean, you guys have, I think the only native offering on all the clouds out there that I know of, is that true? I mean, you guys have, it's not just, you know, you support AWS as your and I B M and G C P, but native offerings. >>We do not have a native offering on GCPD offered the same service. And this is actually interesting as we've evolved our approach. You know, everyone, when we talk about hybrid, Hybrid is, um, you know, dealing with the realities of the computing world, We live in, um, working with each of the major clouds, trying to deliver the best immigration possible in a way that drives that consistency across those environments. And so actually are open shift dedicated on AWS service gave us the inspiration a lot of the basic foundations for what became the integrated Native service. And we've worked with amazon very closely to make sure that that does the right thing for customers who have chosen amazon. And likewise, we're trying to continue to deliver the best experience, the best operational reliability that we can so that the choice of where you run your cloud, um, where you run your applications, um, matches the decisions you've already made and where your future investments are gonna be. So we want to be where customers are, but we also want to give you that consistency. That has been a hallmark of um of open shift since the beginning. >>Yeah. And thanks for clarifying, I appreciate that because the manage serves on GCB rest or native. Um let me ask about the application services because Jeff Barr from AWS posted a few weeks ago amazon celebrated their 15th birthday. They're still teenagers uh relatively speaking. But one comment he made that he that was interesting to me. And this applies kind of this cloud native megatrend happening is he says the A. P. I. S are basically the same and this brings up the hybrid environment. You guys are always been into the api side of the management with the cloud services and supporting all that. As you guys look at this ecosystem in open source. How is the role of A PS and these integrations? Because without solid integration all these services could break down and certainly the open source, more and more people are coding. So take me through how you guys look at these applications services because many people are predicting more service is going to be on boarding faster than ever before. >>It's interesting. So um for us working across multiple cloud environments, there are many similarities in those mps, but for every similarity there is a difference and those differences are actually what dr costs and drive complexity when you're integrating. Um and I think a lot of the role of this is, you know, the irresponsible to talk about the role of an individual company in the computing ecosystem moving to cloud native because as many of these capabilities are unlocked by large cloud providers and transformations in the kinds of software that we run at scale. You know, everybody is a participant in that. But then you look at the broad swath of developer and operator ecosystem and it's the communities of people who paper over those differences, who write run books and build um you know, the policies and who build the experience and the automation. Um not just in individual products or an individual clouds, but across the open source ecosystem. Whether it's technologies like answerable or Terror form, whether it's best practices websites around running kubernetes, um every every part of the community is really involved in driving up uh driving consistency, um driving predictability and driving reliability and what we try to do is actually work within those constraints um to take the ecosystem and to push it a little bit further. So the A. P. I. S. May be similar, but over time those differences can trip you up. And a lot of what I think we talked about where the industry is going, where where we want to be is everyone ultimately is going to own some responsibility for keeping their services running and making sure that their applications and their businesses are successful. The best outcome would be that the A. P. R. S are the same and they're open and that both the cloud providers and the open source ecosystem and vendors and partners who drive many of these open source communities are actually all working together to have the most consistent environment to make portability a true strength. But when someone does differentiate and has a true best to bring service, we don't want to build artificial walls between those. I mean, I mean, that's hybrid cloud is you're going to make choices that make sense for you if we tell people that their choices don't work or they can't integrate or, you know, an open source project doesn't support this vendor, that vendor, we're actually leaving a lot of the complexity buried in those organizations. So I think this is a great time to, as we turn over for cloud. Native looking at how we, as much as possible try to drive those ap is closer together and the consistency underneath them is both a community and a vendor. And uh for red hat, it's part of what we do is a core mission is trying to make sure that that consistency is actually real. You don't have to worry about those details when you're ignoring them. >>That's a great point. Before I get into some architectural impact, I want to get your thoughts on um, the, this trends going on, Everyone jumps on the bandwagon. You know, you say, oh yeah, I gotta, I want a data cloud, you know, everything is like the new, you know, they saw Snowflake Apollo, I gotta have some, I got some of that data, You've got streaming data services, you've got data services and native into the, these platforms. But a lot of these companies think it's just, you're just gonna get a data cloud, just, it's so easy. Um, they might try something and then they get stuck with it or they have to re factor, >>how do you look >>at that as an architect when you have these new hot trends like say a data cloud, how should customers be thinking about kicking the tires on services like that And how should they think holistically around architect in that? >>There's a really interesting mindset is, uh, you know, we deal with this a lot. Everyone I talked to, you know, I've been with red hat for 10 years now in an open shift. All 10 years of that. We've gone through a bunch of transformations. Um, and every time I talked to, you know, I've talked to the same companies and organizations over the last 10 years, each point in their evolution, they're making decisions that are the right decision at the time. Um, they're choosing a new capability. So platform as a service is a great example of a capability that allowed a lot of really large organizations to standardize. Um, that ties into digital transformation. Ci CD is another big trend where it's an obvious wind. But depending on where you jumped on the bandwagon, depending on when you adopted, you're going to make a bunch of different trade offs. And that, that process is how do we improve the ability to keep all of the old stuff moving forward as well? And so open api is open standards are a big part of that, but equally it's understanding the trade offs that you're going to make and clearly communicating those so with data lakes. Um, there was kind of the 1st and 2nd iterations of data lakes, there was the uh, in the early days these capabilities were knew they were based around open source software. Um, a lot of the Hadoop and big data ecosystem, you know, started based on some of these key papers from amazon and google and others taking infrastructure ideas bringing them to scale. We went through a whole evolution of that and the input and the output of that basically let us into the next phase, which I think is the second phase of data leak, which is we have this data are tools are so much better because of that first phase that the investments we made the first time around, we're going to have to pay another investment to make that transformation. And so I've actually, I never want to caution someone not to jump early, but it has to be the right jump and it has to be something that really gives you a competitive advantage. A lot of infrastructure technology is you should make the choices that you make one or two big bets and sometimes people say this, you call it using their innovation tokens. You need to make the bets on big technologies that you operate more effectively at scale. It is somewhat hard to predict that. I certainly say that I've missed quite a few of the exciting transformations in the field just because, um, it wasn't always obvious that it was going to pay off to the degree that um, customers would need. >>So I gotta ask you on the real time applications side of it, that's been a big trend, certainly in cloud. But as you look at hybrid hybrid cloud environments, for instance, streaming data has been a big issue. Uh any updates there from you on your managed service? >>That's right. So one of we have to manage services um that are both closely aligned three managed services that are closely aligned with data in three different ways. And so um one of them is redhead open shift streams for Apache Kafka, which is managed cloud service that focuses on bringing that streaming data and letting you run it across multiple environments. And I think that, you know, we get to the heart of what's the purpose of uh managed services is to reduce operational overhead and to take responsibilities that allow users to focus on the things that actually matter for them. So for us, um managed open shift streams is really about the flow of data between applications in different environments, whether that's from the edge to an on premise data center, whether it's an on premise data center to the cloud. And increasingly these services which were running in the public cloud, increasingly these services have elements that run in the public cloud, but also key elements that run close to where your applications are. And I think that bridge is actually really important for us. That's a key component of hybrid is connecting the different locations and different footprints. So for us the focus is really how do we get data moving to the right place that complements our API management service, which is an add on for open ship dedicated, which means once you've brought the data and you need to expose it back out to other applications in the environment, you can build those applications on open shift, you can leverage the capabilities of open shift api management to expose them more easily, both to end customers or to other applications. And then our third services redhead open shift data science. Um and that is a, an integration that makes it easy for data scientists in a kubernetes environment. On open shift, they easily bring together the data to make, to analyze it and to help route it is appropriate. So those three facets for us are pretty important. They can be used in many different ways, but that focus on the flow of data across these different environments is really a key part of our longer term strategy. >>You know, all the customer checkboxes there you mentioned earlier. I mean I'll just summarize that that you said, you know, obviously value faster application velocity time to value. Those are like the checkboxes, Gardner told analysts check those lower complexity. Oh, we do the heavy lifting, all cloud benefits, so that's all cool. Everyone kind of gets that, everyone's been around cloud knows devops all those things come into play right now. The innovation focuses on operations and day to operations, becoming much more specific. When people say, hey, I've done some lift and shift, I've done some Greenfield born in the cloud now, it's like, whoa, this stuff, I haven't seen this before. As you start scaling. So this brings up that concept and then you add in multi cloud and hybrid cloud, you gotta have a unified experience. So these are the hot areas right this year, I would say, you know, that day to operate has been around for a while, but this idea of unification around environments to be fully distributed for developers is huge. >>How do you >>architect for that? This is the number one question I get. And I tease out when people are kind of talking about their environments that challenges their opportunities, they're really trying to architect, you know, the foundation that building to be um future proof, they don't want to get screwed over when they have, they realize they made a decision, they weren't thinking about day to operation or they didn't think about the unified experience across clouds across environments and services. This is huge. What's your take on this? >>So this is um, this is probably one of the hardest questions I think I could get asked, which is uh looking into the crystal ball, what are the aspects of today's environments that are accidental complexity? That's really just a result of the slow accretion of technologies and we all need to make bets when, when the time is right within the business, um and which parts of it are essential. What are the fundamental hard problems and so on. The accidental complexity side for red hat, it's really about um that consistent environment through open shift bringing capabilities, our connection to open source and making sure that there's an open ecosystem where um community members, users vendors can all work together to um find solutions that work for them because there's not, there's no way to solve for all of computing. It's just impossible. I think that is kind of our that's our development process and that's what helps make that accidental complexity of all that self away over time. But in the essential complexity data is tied the location, data has gravity data. Lakes are a great example of because data has gravity. The more data that you bring together, the bigger the scale the tools you can bring, you can invest in more specialized tools. I've almost do that as a specialization centralization. There's a ton of centralization going on right now at the same time that these new technologies are available to make it easier and easier. Whether that's large scale automation um with conflict management technologies, whether that's kubernetes and deploying it in multiple sites in multiple locations and open shift, bringing consistency so that you can run the apps the same way. But even further than that is concentrating, mhm. More of what would have typically been a specialist problem, something that you build a one off around in your organization to work through the problem. We're really getting to a point where pretty soon now there is a technology or a service for everyone. How do you get the data into that service out? How do you secure it? How do you glue it together? Um I think of, you know, some people might call this um you know, the ultimate integration problem, which is we're going to have all of this stuff and all of these places, what are the core concepts, location, security, placement, topology, latency, where data resides, who's accessing that data, We think of these as kind of the building blocks of where we're going next. So for us trying to make investments in, how do we make kubernetes work better across lots of environments. I have a coupon talk coming up this coupon, it's really exciting for me to talk about where we're going with, you know, the evolution of kubernetes, bringing the different pieces more closely together across multiple environments. But likewise, when we talk about our managed services, we've approached the strategy for managed services as it's not just the service in isolation, it's how it connects to the other pieces. What can we learn in the community, in our services, working with users that benefits that connectivity. So I mentioned the open shift streams connecting up environments, we'd really like to improve how applications connect across disparate environments. That's a fundamental property of if you're going to have data uh in one geographic region and you didn't move services closer to that well, those services I need to know and encode and have that behavior to get closer to where the data is, whether it's one data lake or 10. We gotta have that flexibility in place. And so those obstructions are really, and to >>your point about the building blocks where you've got to factor in those building blocks, because you're gonna need to understand the latency impact, that's going to impact how you're gonna handle the compute piece, that's gonna handle all these things are coming into play. So, again, if you're mindful of the building blocks, just as a cloud concept, um, then you're okay. >>We hear this a lot. Actually, there's real challenges in the, the ecosystem of uh, we see a lot of the problems of I want to help someone automate and improved, but the more balkanize, the more spread out, the more individual solutions are in play, it's harder for someone to bring their technology to bear to help solve the problem. So looking for ways that we can um, you know, grease the skids to build the glue. I think open source works best when it's defining de facto solutions that everybody agrees on that openness and the easy access is a key property that makes de facto standards emerged from open source. What can we do to grow defacto standards around multi cloud and application movement and application interconnect I think is a very, it's already happening and what can we do to accelerate it? That's it. >>Well, I think you bring up a really good point. This is probably a follow up, maybe a clubhouse talk or you guys will do a separate session on this. But I've been riffing on this idea of uh, today's silos, tomorrow's component, right, or module. If most people don't realize that these silos can be problematic if not thought through. So you have to kill the silos to bring in kind of an open police. So if you're open, not closed, you can leverage a monolith. Today's monolithic app or full stack could be tomorrow's building block unless you don't open up. So this is where interesting design question comes in, which is, it's okay to have pre existing stuff if you're open about it. But if you stay siloed, you're gonna get really stuck >>and there's going to be more and more pre existing stuff I think, you know, uh even the data lake for every day to lake, there is a huge problem of how to get data into the data lake or taking existing applications that came from the previous data link. And so there's a, there's a natural evolutionary process where let's focus on the mechanisms that actually move that day to get that data flowing. Um, I think we're still in the early phases of thinking about huge amounts of applications. Microservices or you know, 10 years old in the sense of it being a fairly common industry talking point before that we have service oriented architecture. But the difference now is that we're encouraging and building one developer, one team might run several services. They might use three or four different sas vendors. They might depend on five or 10 or 15 cloud services. Those integration points make them easier. But it's a new opportunity for us to say, well, what are the differences to go back to? The point is you can keep your silos, we just want to have great integration in and out of >>those. Exactly, they don't have to you have to break down the silos. So again, it's a tried and true formula integration, interoperability and abstracting away the complexity with some sort of new software abstraction layer. You bring that to play as long as you can paddle with that, you apply the new building blocks, you're classified. >>It sounds so that's so simple, doesn't it? It does. And you know, of course it'll take us 10 years to get there. And uh, you know, after cloud native will be will be galactic native or something like that. You know, there's always going to be a new uh concept that we need to work in. I think the key concepts we're really going after our everyone is trying to run resilient and reliable services and the clouds give us in the clouds take it away. They give us those opportunities to have some of those building blocks like location of geographic hardware resources, but they will always be data that spread. And again, you still have to apply those principles to the cloud to get the service guarantees that you need. I think there's a completely untapped area for helping software developers and software teams understand the actual availability and guarantees of the underlying environment. It's a property of the services you run with. If you're using a disk in a particular availability zone, that's a property of your application. I think there's a rich area that hasn't been mined yet. Of helping you understand what your effective service level goals which of those can be met. Which cannot, it doesn't make a lot of sense in a single cluster or single machine or a single location world the moment you start to talk about, Well I have my data lake. Well what are the ways my data leg can fail? How do we look at your complex web of interdependencies and say, well clearly if you lose this cloud provider, you're going to lose not just the things that you have running there, but these other dependencies, there's a lot of, there's a lot of next steps that we're just learning what happens when a major cloud goes down for a day or a region of a cloud goes down for a day. You still have to design and work around those >>cases. It's distributed computing. And again, I love the space where galactic cloud, you got SpaceX? Where's Cloud X? I mean, you know, space is the next frontier. You know, you've got all kinds of action happening in space. Great space reference there. Clayton, Great insight. Thanks for coming on. Uh, Clayton Coleman architect at red Hat. Clayton, Thanks for coming on. >>Pretty pleasure. >>Always. Great chat. I'm talking under the hood. What's going on in red hats? New managed cloud service portfolio? Again, the world's getting complex, abstract away. The complexities with software Inter operate integrate. That's the key formula with the cloud building blocks. I'm john ferry with the cube. Thanks for watching. Yeah.

>>Okay, We're now going into the technical deep dive. We're gonna geek out here a little bit. Ben Wa Dodgeville is here. He's co founder of Snowflake and president of products. And also joining us is Christian Kleinerman. Who's the senior vice president of products. Gentlemen, welcome. Good to see you. >>Yeah, you that >>get this year, they Thanks for having us. >>Very welcome. So it been well, we've heard a lot this morning about the data cloud, and it's becoming my view anyway, the linchpin of your strategy. I'm interested in what technical decisions you made early on. That that led you to this point and even enabled the data cloud. >>Yes. So? So I would say that that a crowd was built in tow in three phases. Really? The initial phase, as you call it, was it was really about 20 minutes. One regions Teoh, Data Cloud and and that region. What was important is to make that region infinity, infinity scalable, right. And that's our architectural, which we call the beauty cross to share the architectural er so that you can plug in as many were clues in that region as a Z without any limits. The limit is really the underlying prop Provide the, you know, resource is which you know, Cal provide the region as a really no limits. So So that z you know, region architecture, I think, was really the building block of the snowflake. That a cloud. But it really didn't stop there. The second aspect Waas Well, it was really data sharing. How you know munity internets within the region, how to share data between 10 and off that region between different customers on that was also enabled by architectures Because we discover, you know, compute and storage so compute You know clusters can access any storage within the region. Eso that's based off the data cloud and then really faced three Which is critical is the expansion the global expansion how we made you know, our cloud domestic layers so that we could talk You know the snowflake vision on different clouds on DNA Now we are running in three cloud on top of three cloud providers. We started with the ws and US West. We moved to assure and then uh, Google g c p On how this this crowd region way started with one crowd region as I said in the W S U S West, and then we create we created, you know, many you know, different regions. We have 22 regions today, all over the world and all over the different in the cloud providers. And what's more important is that these regions are not isolated. You know, Snowflake is one single, you know, system for the world where we created this global data mesh which connects every region such that not only there's no flex system as a whole can can be aware of for these regions, But customers can replicate data across regions on and, you know, share. There are, you know, across the planet if need be. So So this is one single, you know, really? I call it the World Wide Web. Off data that, that's, you know, is this vision of the data cloud. And it really started with this building block, which is a cloud region. >>Thank you for that. Ben White Christian. You and I have talked about this. I mean, that notion of a stripping away the complexity and that's kind of what the data cloud does. But if you think about data architectures, historically they really had no domain knowledge. They've really been focused on the technology toe ingest and analyze and prepare And then, you know, push data out to the business and you're really flipping that model, allowing the sort of domain leaders to be first class citizens if you will, uh, because they're the ones that creating data value, and they're worrying less about infrastructure. But I wonder, do you feel like customers air ready for that change? >>I I love the observation. They've that, uh, so much energy goes in in in enterprises, in organizations today, just dealing with infrastructure and dealing with pipes and plumbing and things like that and something that was insightful from from Ben Juan and and our founders from from Day one WAAS. This is a managed service. We want our customers to focus on the data, getting the insights, getting the decisions in time, not just managing pipes and plumbing and patches and upgrades, and and the the other piece that it's it's it's an interesting reality is that there is this belief that the cloud is simplifying this, and all of a sudden there's no problem but actually understanding each of the public cloud providers is a large undertaking, right? Each of them have 100 plus services, uh, sending upgrades and updates on a constant basis. And that just distracts from the time that it takes to go and say, Here's my data. Here's my data model. Here's how it make better decisions. So at the heart of everything we do is we wanna abstract the infrastructure. We don't wanna abstract the nuance of each of the cloud providers. And as you said, have companies focus on This is the domain expertise or the knowledge for my industry. Are all companies ready for it? I think it's a It's a mixed bag. We we talk to customers on a regular basis every way, every week, every day, and some of them are full on. They've sort of burned the bridges and, like I'm going to the cloud, I'm going to embrace a new model. Some others. You can see the complete like, uh, shock and all expressions like What do you mean? I don't have all these knobs. 2 to 3 can turn. Uh, but I think the future is very clear on how do we get companies to be more competitive through data? >>Well, Ben Ben. Well, it's interesting that Christian mentioned to manage service and that used to be in a hosting. Guys run around the lab lab coats and plugging things in. And of course, you're looking at this differently. It's high degrees of automation. But, you know, one of those areas is workload management. And I wonder how you think about workload management and how that changes with the data cloud. >>Yeah, this is a great question. Actually, Workload management used to be a nightmare. You know, traditional systems on it was a nightmare for the B s and they had to spend most a lot of their time, you know, just managing workloads. And why is that is because all these workloads are running on the single, you know, system and a single cluster The compete for resources. So managing workload that always explain it as explain Tetris, right? You had the first to know when to run. This work will make sure that too big workers are not overlapping. You know, maybe it really is pushed at night, you know, And And you have this 90 window which is not, you know, efficient. Of course, for you a TL because you have delays because of that. But but you have no choice, right? You have a speaks and more for resource is and you have to get the best out of this speaks resource is. And and for sure you don't want to eat here with her to impact your dash boarding workload or your reports, you know, impact and with data science and and And this became a true nine man because because everyone wants to be that a driven meaning that all the entire company wants to run new workers on on this system. And these systems are completely overwhelmed. So so, well below management was, and I may have before Snowflake and Snowflake made it really >>easy. The >>reason is it's no flag. We leverage the crowds who dedicates, you know, compute resources to each work. It's in the snowflake terminology. It's called a warehouse virtual warehouse, and each workload can run in its own virtual warehouse, and each virtual warehouse has its own dedicated competition resources. It's on, you know, I opened with and you can really control how much resources which workload gas by sizing this warehouses. You know, I just think the compute resources that they can use When the workload, you know, starts to execute automatically. The warehouse, the compute resources are turned off, but turned on by snowflake is for resuming a warehouse and you can dynamically resized this warehouse. It can be done by the system automatically. You know if if the conference see of the workload increases or it can be done manually by the administrator or, you know, just suggesting, you know, uh, compute power. You know, for each workload and and the best off that model is not only it gives you a very fine grain. Control on resource is that this work can get Not only workloads are not competing and not impacting it in any other workload. But because of that model, you can hand as many workload as you want. And that's really critical because, as I said, you know, everyone in the organization wants to use data to make decisions, So you have more and more work roads running. And then the Patriots game, you know, would have been impossible in in a in a centralized one single computer, cross the system On the flip side. Oh, is that you have to have a zone administrator off the system. You have to to justify that. The workload is worth running for your organization, right? It's so easy in literally in seconds, you can stand up a new warehouse and and start to run your your crazy on that new compute cluster. And of course, you have to justify if the cost of that because there is a cost, right, snowflake charges by seconds off compute So that cost, you know, is it's justified and you have toe. You know, it's so easy now to hire new workflow than you do new things with snowflake that that that you have to to see, you know, and and look at the trade off the cost off course and managing costs. >>So, Christian been while I use the term nightmare, I'm thinking about previous days of workload management. I mean, I talked to a lot of customers that are trying to reduce the elapsed time of going from data insights, and their nightmare is they've got this complicated data lifecycle. Andi, I'm wondering how you guys think about that. That notion of compressing elapsed time toe data value from raw data to insights. >>Yeah, so? So we we obsess or we we think a lot about this time to insight from the moment that an event happens toe the point that it shows up in a dashboard or a report or some decision or action happens based on it. There are three parts that we think on. How do we reduce that life cycle? The first one which ties to our previous conversation is related toe. Where is their muscle memory on processes or ways of doing things that don't actually make us much sense? My favorite example is you say you ask any any organization. Do you run pipelines and ingestion and transformation at two and three in the morning? And the answer is, Oh yeah, we do that. And if you go in and say, Why do you do that? The answer is typically, well, that's when the resource is are available Back to Ben Wallace. Tetris, right? That's that's when it was possible. But then you ask, Would you really want to run it two and three in the morning? If if you could do it sooner, we could do it. Mawr in time, riel time with when the event happened. So first part of it is back to removing the constraints of the infrastructures. How about running transformations and their ingestion when the business best needs it? When it's the lowest time to inside the lowest latency, not one of technology lets you do it. So that's the the the easy one out the door. The second one is instead of just fully optimizing a process, where can you remove steps of the process? This is where all of our data sharing and the snowflake data marketplace come into place. How about if you need to go in and just data from a SAS application vendor or maybe from a commercial data provider and imagine the dream off? You wouldn't have to be running constant iterations and FTP s and cracking C S V files and things like that. What if it's always available in your environment, always up to date, And that, in our mind, is a lot more revolutionary, which is not? Let's take away a process of ingesting and copying data and optimize it. How about not copying in the first place? So that's back to number two on, then back to number three is is what we do day in and day out on making sure our platform delivers the best performance. Make it faster. The combination of those three things has led many of our customers, and and And you'll see it through many of the customer testimonials today that they get insights and decisions and actions way faster, in part by removing steps, in part by doing away with all habits and in part because we deliver exceptional performance. >>Thank you, Christian. Now, Ben Wa is you know, we're big proponents of this idea of the main driven design and data architecture. Er, you know, for example, customers building entire applications and what I like all data products or data services on their data platform. I wonder if you could talk about the types of applications and services that you're seeing >>built >>on top of snowflake. >>Yeah, and And I have to say that this is a critical aspect of snowflake is to create this platform and and really help application to be built on top of this platform. And the more application we have, the better the platform will be. It is like, you know, the the analogies with your iPhone. If your iPhone that no applications, you know it would be useless. It's it's an empty platforms. So So we are really encouraging. You know, applications to be belong to the top of snowflake and from there one actually many applications and many off our customers are building applications on snowflake. We estimated that's about 30% are running already applications on top off our platform. And the reason is is off course because it's it's so easy to get compute resources. There is no limit in scale in our viability, their ability. So all these characteristics are critical for for an application on DWI deliver that you know from day One Now we have improved, you know, our increased the scope off the platform by adding, you know, Java in competition and Snow Park, which which was announced today. That's also you know, it is an enabler. Eso in terms off type of application. It's really, you know, all over and and what I like actually needs to be surprised, right? I don't know what well being on top of snowflake and how it will be the world, but with that are sharing. Also, we are opening the door to a new type of applications which are deliver of the other marketplace. Uh, where, You know, one can get this application died inside the platform, right? The platform is distributing this application, and today there was a presentation on a Christian T notes about, >>you >>know, 20 finds, which, you know, is this machine learning, you know, which is providing toe. You know, any users off snowflake off the application and and machine learning, you know, to find, you know, and apply model on on your data and enrich your data. So data enrichment, I think, will be a huge aspect of snowflake and data enrichment with machine learning would be a big, you know, use case for these applications. Also, how to get there are, you know, inside the platform. You know, a lot of applications led him to do that. Eso machine learning. Uh, that engineering enrichments away. These are application that we run on the platform. >>Great. Hey, we just got a minute or so left in. Earlier today, we ran a video. We saw that you guys announced the startup competition, >>which >>is awesome. Ben, while you're a judge in this competition, what can you tell us about this >>Yeah, >>e you know, for me, we are still a startup. I didn't you know yet, you know, realize that we're not anymore. Startup. I really, you know, you really feel about you know, l things, you know, a new startups, you know, on that. That's very important for Snowflake. We have. We were started yesterday, and we want to have new startups. So So the ends, the idea of this program, the other aspect off that program is also toe help, you know, started to build on top of snowflake and to enrich. You know, this this pain, you know, rich ecosystem that snowflake is or the data cloud off that a cloud is And we want to, you know, add and boost. You know that that excitement for the platform, so So the ants, you know, it's a win win. It's a win, you know, for for new startups. And it's a win, ofcourse for us. Because it will make the platform even better. >>Yeah, And startups, or where innovation happens. So registrations open. I've heard, uh, several, uh, startups have have signed up. You goto snowflake dot com slash startup challenge, and you can learn mawr. That's exciting program. An initiative. So thank you for doing that on behalf of of startups out there and thanks. Ben Wa and Christian. Yeah, I really appreciate you guys coming on Great conversation. >>Thanks for David. >>You're welcome. And when we talk, Thio go to market >>pros. They >>always tell us that one of the key tenets is to stay close to the customer. Well, we want to find out how data helps us. To do that in our next segment. Brings in to chief revenue officers to give us their perspective on how data is helping their customers transform. Business is digitally. Let's watch.

>>from around the globe. It's the Cube with coverage of Yukon and Cloud. Native Con North America. 2020. Virtual Brought to You by Red Hat, The Cloud, Native Computing Foundation and Ecosystem Partners. Hey, welcome back, everybody. Jeffrey here with the Cube coming to you from our Palo Alto studios with our ongoing coverage of Q. Khan Cloud, Native Con 2020 North America. Of course, it's virtual like everything else is in 2020 but we're excited to be back. It's a terrific show, and we're excited our next guest. So let's introduce him. And we've got Sam Warner, the VP of offering manager and business line executive for storage for IBM. Sam. Great to see you. >>Great to be here. >>And also joining us is Brent Compton. He's a senior director of data services for Redhead. Great. See you, Brent. >>Thank you. >>So let's let's jump into it. Cloud Native. Everything's about cloud native. Everything's about containers. Everything is about kind of container ization and flexibility. But then there's this thing in the back and called storage. We actually have toe keep this stuff and record this stuff and have data protection for this stuff in business resiliency love to jump into it, so lets you know where does storage fit within a container world? And how is the growth of containers and the adoption containers really had you rethink the way that you think about storage and how clients you think about stories saying, Let's start with you >>e mean, it's a great question. And first off, I'm really excited about another cube con. Uh, we did Europe now, uh, doing North America so very excited to be, you know, seeing all the you know, all the news and all the people talking about the advancements around kubernetes. And we're very excited about it now. You asked a very good question. Important question. We're seeing an acceleration of digital transformation, and the people that are going through this digital transformation are using containers to now modernize the rest of their infrastructure. The interesting thing about it, though, is those initiatives are being driven out of the application teams. The business lines in an organization, and a lot of them don't understand that there's a lot of complexity to this storage piece here. So the storage teams I talked to are all of a sudden getting these initiatives thrown on them or a kind of halfway their strategy. And they're scratching their heads, trying to figure out now how they can support these applications with persistent storage. Because that's not where containers started. They started with micro services, and now now they're in a quandary. They have to deliver a certain S L. A to their customers, and they're trying to figure out how they do it in this new environment, which in a lot of cases, has been designed outside of their scope. So they're seeing issues with data protection. Some of the kind of core things that they've been dealing with for years are now. They're now having to solve all over again. So that's what we're working on helping them with reinventing how storage is deployed to help them deliver the same level of security, availability and everything they have in the past. Uh, in these new environments, >>right? So, yeah, e say you've been involved in this for a long time. You know, you've worked in hyper converge. You've worked in big data. You know, the evolution of big data continues to change, as ultimately we want to get people the information to make good decisions, but we've gone through a lot of integrations over the years. So how is it different? You know? Now how is it different with containers? What can we finally do you as a as an architect that we couldn't do before? >>Infrastructure is code. That's, I think, one of the fundamental differences of the storage admin of yesteryear versus storage admin of today today, Azaz Sam mentioned As people are developing and deploying applications, those applications need to dynamically provisioned the infrastructure dynamically provisioned what they need from compute dynamically provisioned what they need from storage dynamically provisioned network paths and so that that that element of infrastructure is code. A dynamically provisioned infrastructure is very different from well from yesterday, when applications or teams needed to. Well, when they needed storage, they would you know, they would file a ticket and typically wait. Now they make an a p A. Now they make an A p. I call and storage is dynamically provisioned and provided to their application. >>But what what I think hard to understand for the layman. And maybe it's just me, right? I It's very easy to understand dynamic infrastructure around, um compute right, I'm Pepsi. I'm running it out for the Super Bowl. I need I know how much people are gonna hit by hit my site and it's kind of easy to understand. Dynamic provisioning around networking again for the same example. What's less easy to understand its dynamic provisioning for storage? It's one thing to say, you know, there's a there's a pool of storage resource is that I'm going to dynamically provisioned for this particular after this particular moment. But one of the whole things about the dynamic is not only is it available when you need it, but I could make it big, and conversely, I could make it smaller go away. I get that for servers, and I kind of get that for networking, supporting an application and that example I just talked about. But we can't It doesn't go away a lot of the time for storage, right? That's important data that's maybe feeding another process. There's all kinds of rules and regulations, So when you talk about dynamic infrastructure for storage, it makes a lot of sense for grabbing some to provision for some new application. But it's >>hard to >>understand in terms of true dynamics in terms of either scaling down or scaling up or turning off when I don't particularly need that much capacity or even that application right now, how does it work within storage versus No, just servers or I'm grabbing them and then I'm putting it back in the pool. >>Let me start on this one, and then I'm gonna hand it off to Brent. Um, you know, let's not forget, by the way, that enterprises have very significant investments in infrastructure and they're able to deliver six nines of availability on their storage. And they have d are worked out in all of their security, encryption, everything. It's already in place, and they're sure that they can deliver on their SLS. So they want to start with that. You have to leverage that investment. So first of all, you have to figure out how to automate that into the environment, that existing sand, and that's where things like uh, a P I s the container storage interface CS I drivers come in. IBM provides that across your entire portfolio, allowing you to integrate your storage into a kubernetes environment into an open shipped environment so that it can be automated, but you have to go beyond that and be able to extend that environment, then into other infrastructure, for example, into a public cloud. So with the IBM flash system, family with our spectrum virtualized software were actually able to deploy that storage layer not only on Prem on our award winning a race, but we can also do it in the cloud. So we allow you to take your existing infrastructure investments and integrate that into your communities environment and using things like danceable, fully automated environment. I'll get into data protection before we're done talking. But I do want Brent to talk a bit about how container native storage comes into that next as well. On how you can start building out new environments for, uh, for your applications. >>Yeah, What the two of you are alluding to is effectively kubernetes services layer, which is not storage. It consumes storage from the infrastructure, Assam said. Just because people deploy Kubernetes cluster doesn't mean that they go out and get an entirely new infrastructure for that. If they're deploying their kubernetes cluster on premises, they have servers. If they're deploying their kubernetes cluster on AWS or an azure on G C P. They have infrastructure there. Uh, what the two of you are alluding to is that services layer, which is independent of storage that can dynamically provisioned, provide data protection services. As I mentioned, we have good stuff to talk about their relative to data protection services for kubernetes clusters. But that's it's the abstraction layer or data services layer that sits on top of storage, which is different. So the basics of storage underneath in the infrastructure, you know, remain the same, Jeff. But the how that storage is provisioned and this abstraction layer of services which sits on top of the storage storage might be IBM flash system array storage, maybe E m c sand storage, maybe a W S E B s. That's the storage infrastructure. But this abstraction layer that sits on top this data services layer is what allows for the dynamic interaction of applications with the underlying storage infrastructure. >>And then again, just for people that aren't completely tuned in, Then what's the benefit to the application developer provider distributor with that type of an infrastructure behind And what can they do that they just couldn't do before? >>Well, I mean Look, we're, uh, e I mean, we're trying to solve the same problem over and over again, right? It's always about helping application developers build applications more quickly helps them be more agile. I t is always trying to keep up with the application developer and always struggles to. In fact, that's where the emergency cloud really came from. Just trying to keep up with the developer eso by giving them that automation. It gives them the ability to provision storage in real time, of course, without having open a ticket like friends said. But really, the Holy Grail here is getting to a developed once and deploy anywhere model. That's what they're trying to get to. So having an automated storage layer allows them to do that and ensure that they have access to storage and data, no matter where their application gets it >>right, Right, that pesky little detail. When I have to develop that up, it does have to sit somewhere and and I don't think storage really has gotten enough of of the bright light, really in kind of this app centric, developer centric world, we talk all the time about having compute available and and software defined networking. But you know, having this software defined storage that lives comfortably in this container world is pretty is pretty interesting. In a great development, I want to shift gears a >>little bit. Just one thing. Go >>ahead, >>plus one to Sam's comments. There all the application developer wants, they want an A P I and they want the same a p I to provision the storage regardless of where their app is running. The rest of the details they usually don't care about. Sure. They wanted to perform what not give him an A p I and make it the same regardless of where they're running the app. >>Because not only do they want to perform, they probably just presume performance, right? I mean, that's the other thing is that the best in class quickly becomes presumed baseline in a very short short period of time. So you've got to just you just got to just deliver the goods, right? They're gonna get frustrated and not be productive. But I wanted to shift gears up a little bit and talk about some of the macro trends. Right? We're here towards the end of 2020. Obviously, Cove It had a huge impact on business and a lot of different ways. And it's really evolved from March, this light switch moment. Everybody work from home, too. Now, this kind of extended time, that's probably gonna go on for a while. I'm just curious some of the things that you've seen with your customers not so much at the beginning, because that was that was a special and short period of time. But mawr, as we've extended and and are looking to, um, probably extended this for a while, you know, What is the impact of this increased work from home increase attack surface? You know, some of these macro things that we're seeing that cove it has caused and any other kind of macro trends beyond just this container ization that you guys were seeing impacting your world. Start with you, Sam. >>You know, I don't think it's actually changed what people were going to do or the strategy. What I've seen it do is accelerate things and maybe changed the way they're getting their, uh and so they're actually a lot of enterprises were running into challenges more quickly than they thought they would. And so they're coming to us and asking us to help them. Saw them, for example, backing up their data and these container environments as you move mission critical applications that maybe we're gonna move more slowly. They're realizing that as they've moved them, they can't get the level of data protection they need. And that's why actually we just announced it at the end of October. Updates to our modern data protection portfolio. It now is containerized. It could be deployed very easily in an automated fashion, but on top of that, it integrates down into the A P. I layer down into CSE drivers and allows you to do container where snapshots of your applications so you could do operational recovery. If there's some sort of an event you can recover from that you can do D R. And you can even use it for data migration. So we're helping them accelerate. So the biggest I think requests I'm getting from our customers, and how can you help us accelerate? And how can you help us fix these problems that we went running into as we tried to accelerate our digital transformation? >>Brent, Anyone that you wanna highlight? >>Mm. Okay. Ironically, one of my team was just speaking with one of the cruise lines, um, two days ago. We all know what's happened them. So if we just use them as an example, I'm clearly our customers need to do things differently now. So plus one to Sam's statement about acceleration on I would add another word to that which is agility, you know, frankly, they're having to do things in ways they never envisioned 10 months ago. So there need to cut cycle times to deploy effectively new ways of how they transact business has resulted in accelerated poll for these types of infrastructure is code technologies. >>That's great. The one that jumped in my mind. Sam, is you were talking. We've we've had a lot of conversations. Obvious security always comes up on baking security and is is a theme. But ransomware as a specific type of security threat and the fact that these guys not only wanna lock up your data, but they want to go in and find the backup copies and and you know and really mess you up so it sounds like that's even more important to have the safe. And we're hearing, you know, all these conversations about air gaps and dynamic air gaps and, you know, can we get air gaps and some of these infrastructure set up so that we can, you know, put put those backups? Um, and recovery data sets in a safe place so that if we have a ransomware issue, getting back online is a really, really important thing, and it seems to just be increasing every day. We're seeing things, you know, if you can actually break the law sometimes if you if you pay the ransom because where these people operate, there's all kind of weird stuff that's coming out of. Ransomware is a very specific, you know, kind of type of security threat that even elevates, you know, kind of business continuity and resiliency on a whole nother level for this one particular risk factor. When if you're seeing some of that as well, >>it's a great point. In fact, it's clearly an industry that was resilient to a pandemic because we've seen it increase things. Is organized crime at this point, right? This isn't the old days of hackers, you know, playing around this is organized crime and it is accelerating. And that's one thing. I'm really glad you brought up. It's an area we've been really focused on across our whole portfolio. Of course, IBM tape offers the best most of the actual riel air gapping, physical air gapping We could take a cartridge offline. But beyond that we offer you the ability to dio you know, different types of logical air gaps, whether it's to a cloud we support. In fact, we just announced Now the spectrum protect. We have support for Google Cloud. We already supported AWS Azure IBM Cloud. So we give you the ability to do logical air gapping off to those different cloud environments. We give you the ability to use worm capability so you can put your backups in a vault that can't be changed. So we give you lots of different ways to do it. In our high end enterprise storage, we offer something called Safeguarded copy where we'll actually take data off line that could be recovered almost instantly. Something very unique to our storage that gives you, for the most mission critical applications. The fastest path recovery. One of things we've seen is some of our customers have done a great job creating a copy. But when the event actually happens, they find is gonna take too long to recover the data and they end up having to pay the ransom anyway. So you really have to think through an Indian strategy on we're able to help customers do a kind of health checks of their environment and figure out the right strategy. We have some offerings to help come in and do that for our customers. >>Shift gears a little bit, uh, were unanswerable fest earlier this year and a lot of talk about automation. Obviously, answer was part of the Red Hat family, which is part of the IBM family. But, you know, we're seeing Mawr and Mawr conversations about automation about, you know, moving the mundane and the air prone and all the things that we shouldn't be doing as people and letting people doom or high value stuff. When if you could talk a little bit about the role of automation, that the kind of development of automation and how you're seeing that, you know, impact your deployments, >>right? You want to take that one first? >>Yeah, sure. Um, s o the first is, um when you think about individual kubernetes clusters. There's a level of automation that's required there. I mean, that's the fundamental. I mean, back to the infrastructure is code that's inherently. That's automation. To effectively declare the state of what you want your application, your cluster to be, and that's the essence of kubernetes. You declare what the state is, and then you pass that declaration to kubernetes, and it makes it so. So there's the kubernetes level automation. But then there's, You know what happens for larger enterprises when you have, you know, tens or hundreds of kubernetes clusters. Eso That's an area of Jeff you mentioned answerable. Now that's an area of with, you know, the work, the red hats doing the community for multi cluster management, actually in the community and together with IBM for automating the management of multiple clusters. And last thing I'll touch on here is that's particularly important as you go to the edge. I mean, this is all well and good when you're talking about, you know, safe raised floor data center environments. But what happens when you're tens or hundreds or even thousands of kubernetes clusters are running in an oil field somewhere? Automation becomes not only nice to have, but it's fundamental to the operation. >>Yeah, but let me just add onto that real quick. You know, it's funny, because actually, in this cove it era, you're starting to see that same requirement in the data center in the core data center. In fact, I would say that because there's less bodies now in the data center, more people working remotely. The automation in need for automation is actually actually accelerating as well. So I think what you said is actually true for the core data center now as well, >>right? So I wanna give you guys the last word before before we close the segment. Um, I'm gonna start with you, Brent. Really, From a perspective of big data and you've been involved again in big data for a long time. As you look back, it kind of the data warehouse era. And then we had kind of this whole rage with the Hadoop era, and, you know, we just continue to get more and more sophisticated with big data processes and applications. But at the end of the day, still about getting the right data to the right person at the right time to do something about it. I wonder if if you can, you know, kind of reflect over that journey and where we are now in terms of this mission of getting, you know, the right data to the right person at the right time so they could make the right decision. >>I think I'll close with accessibility. Um, that Z these days, we you know, the data scientists and data engineers that we work with. The key problem that they have is is accessibility and sharing of data. I mean, this has been wonderfully manifest. In fact, we did some work with the province of Ontario. You could look that stop hashtag house my flattening eso the work with them to get a pool of data. Scientists in the community in the province of Ontario, Canada, toe work together toe understand how to track co vid cases s such so that government could make intelligent responses and policy based on based on the fax so that that need highlights the accessibility that's required from today's, you know, yesteryear. It was maybe, uh, smaller groups of individual data scientists working in silos. Now it's people across industry as manifest by that That need accessibility as well as agility. They need to be able to spin up an environment that will allow them to in this case, um, to develop and deploy inference models using shared data sets without going through years of design. So accessibility on back to the back to the the acceleration and agility that Sam talked about. So I'll close with those words >>That's great. And the consistent with the democratization of two is another word that we're here, you know, over and over again in terms of, you know, getting it out of the hands of the data scientists and getting it into the hands of the people who are making frontline business decisions every day. And Sam for you, for your clothes. I love for you Thio reflect on kind of the changing environment in terms of your requirements for the types of workloads that you now are, you know, looking to support. So it's not just taking care of the data center and relatively straightforward stuff. But you've got hybrid. You've got multi cloud, not to mention all the media, the developments in the media between tape and obviously flash, um, spinning, spinning drives. But you know, really, We've seen this huge thing with flash. But now, with cloud and the increased kind of autumn autonomy ization of of units to be able to apply big batches in small batches to particular workloads across all these different requirements. When if you could just share a little bit about how you guys are thinking about, you know, modernizing storage and moving storage forward. What are some of your what are some of your your priorities? What are you looking forward to, uh, to be able to deliver, You know, basically the stuff underneath all these other applications. I mean, applications basically is data whether you I and some in some computer on top. You guys something underneath the whole package? >>Yeah. Yeah. You know, first of all, you know, back toe what Brent was saying, Uh, data could be the most valuable asset of an enterprise. You could give an enterprising, incredible, uh, competitive advantage as an incumbent if you could take advantage of that data using modern analytics and a I. So it could be your greatest asset. And it can also be the biggest inhibitor to digital transformation. If you don't figure out how to build a new type of modern infrastructure to support access to that data and support these new deployment models of your application. So you have to think that through. And that's not just for your big data, which the big data, of course, is extremely important and growing at incredible pace. All this unstructured data, You also have to think about your mission critical applications. We see a lot of people going through their transformation and modernization of S a p with move toe s four Hana. They have to think about how that fits into a multi cloud environment. They need to think about the life cycle of their data is they go into these new modern environments. And, yes, tape is still a very vibrant part of that deployment. So what we're working on an IBM has always been a leader in software defined storage. We have an incredible portfolio of capabilities. We're working on modernizing that software to help you automate your infrastructure. And sure, you can deliver enterprise class sls. There's no nobody's going to alleviate the requirements of having, you know, near perfect availability. You don't because you're moving into a kubernetes environment. Get a break on your downtime. So we're able to give that riel enterprise class support for doing that. One of the things we just announced that the end of October was we've containerized our spectrum scale client, allowing you now toe automate the deployment of your cluster file system through communities. So you'll see more and more of that. We're offering you leading modern native protection for kubernetes will be the first to integrate with OCP and open ship container storage for data protection. And our flashes from family will continue to be on the leading edge of the curve around answerable automation and C s I integration with who are already so we'll continue to focus on that and ensure that you could take advantage of our world class storage products in your new modern environment. And, of course, giving you that portability between on from in any cloud that you choose to run in >>exciting times. No, no shortage of job security for you, gentlemen, that's for sure. All right, Well, Brent, Sam, thanks for taking a few minutes and, uh, is great to catch up. And again. Congratulations on the success. Thank you. Thank you. Thank you. Alrighty, Sammy's Brent. I'm Jeff, You're watching the cubes. Continuing coverage of Q. Khan Cloud, Native Con North America 2020. Thanks for watching. We'll see you next time.

>>from around the globe. It's the Cube with digital coverage of Dell Technologies. World Digital Experience Brought to You by Dell Technologies. >>Welcome to the Cubes Coverage of Dell Technologies World 2020. The Digital Experience. I'm Lisa Martin, and I'm pleased to welcome back a Cube alumni and a new Cube member to the program today. China. My Mondal is back with US Director of Solutions Marketing for Dell Technologies China. But it's great to see you at Dell Technologies world, even though we're very specially death. >>Happy to be back. Thank you, Lisa. >>And Thomas Henson is joining us for the first time. Global business development manager for a I and analytics. Thomas, Welcome to the Cube. >>I am excited to be here. It's my first virtual cube. >>Yeah, well, you better make it a good one. All right. I said we're talking about a I so so much has changed John to me. The last time I saw you were probably were sitting a lot closer together. So much has changed in the last 67 months, but a lot has changed with the adoption of Ai Thomas. Kick us off. What are some of the big things feeling ai adoption right now? >>Yeah, I >>would have to >>say the two biggest things right now or as we look at accelerated compute and by accelerated compute we're not just talking about the continuation of Moore's law, but how In Data Analytics, we're actually doing more processing now with GP use, which give us faster insights. And so now we have the ability to get quicker insights in jobs that may have taken, you know, taking weeks to months a song as we were measuring. And then the second portion is when we start to talk about the innovation going on in the software and framework world, right? So no longer do you have toe know C plus plus or a lower level language. You can actually do it in Python and even pull it off of Get Hub. And it's all part of that open source community. So we're seeing Mawr more folks in the field of data science and deep learning that can actually implement some code. And then we've got faster compute to be able to process that. >>Tell me, what are your thoughts? >>Think I want to add? Is the explosive growth off data on that's actually are fulfilling the AI adoption. Think off. Like all the devices we have, the i o t. On age devices are doing data are pumping data into the pipeline. Our high resolution satellite imagery, all social media generating data. No. All of this data are actually helping the adoption off a I because now we have very granular data tow our friend the AI model Make the AI models are much better. Besides, so the combination off both in, uh, data the power off Like GPU, power surfers are coupled with the inefficient in the eye after and tools helping off. Well, the AI growth that we're seeing today >>trying to make one of the things that we've known for a while now is that it's for a I to be valuable. It's about extracting value from that. Did it? You talked about the massive explosion and data, but yet we know for a long time we've been talking about AI for decades. Initiatives can fail. What can Dell Technologies do now to help companies have successfully I project? >>Yeah, eso As you were saying, Lisa, what we're seeing is the companies are trying to add up AI Technologies toe Dr Value and extract value from their data set. Now the way it needs to be framed is there is a business challenge that customers air trying to solve. The business challenge gets transformed into a data science problem. That data scientist is going toe work with the high technology, trained them on it. That data science problem gets to the data science solution on. Then it needs to be mapped to production deployment as a business solution. What happens? Ah, lot off. The time is the companies do not plan for output transition from all scale proof of concept that it a scientists are playing with, like a smaller set of data two, when it goes toe the large production deployment dealing with terabytes toe terabyte self data. Now that's where we come in. At their technologies, we have into end solutions for the, uh for the ai for pollution in the customers journeys starting from proof of concept to production. And it is all a seamless consular and very scalable. >>So if some of the challenges there are just starting with iterations. Thomas question for you as business development manager, those folks that John um I talked about the data scientists, the business. How are you helping them come together from the beginning so that when the POC is initiated, it actually can go on the right trajectory to be successful? >>No, that's a great point. And just to kind of build off of what Shonda my was talking about, You know, we call it that last mile, right? Like, Hey, I've got a great POC. How do I get into production? Well, if you have executive sponsorship and it's like, Hey, everybody was on board, but it's gonna take six months to a year. It's like, Whoa, you're gonna lose some momentum. So where we help our customers is, you know, by partnering with them to show them how to build, you know, from an i t. And infrastructure perspective what that ai architectural looks like, right? So we have multiple solutions around that, and at the end of the day, it's about just like Sean. Um, I was saying, You know, we may start off with a project that maybe it's only half a terabyte. Maybe it's 10 terabytes, but once you go into production, if it turns out to be three petabytes four petabytes. Nobody really, you know, has the infrastructure built unless they built on those solid practices. And that's where our solutions come in. So we can go from small scale laboratory all the way large scale production without having to move any of that data. Right? So, you know, at the heart of that is power scale and giving you that ability to scale your data and no more data migration so that you can handle one PC or multiple PCs as those models continue to improve as you start to move into production >>and I'm sticking with you 1st. 2nd 0, sorry. Trying to go ahead. >>So I was going to add that, uh, just like posthumous said right. So if you were a data scientist, you are working with this data science workstations, but getting the data from, uh, L M c our scales thes scale out platform and, uh, as it is growing from, you see two large kills production data can stay in place with the power scale platform. You can add notes, and it can grow to petabytes. And you can add in not just the workstations, but also our They'll power it, solve our switches building out our enter A I ready solutions are already solution for your production. Giving are very seamless experience from the data scientist with the i t. >>So China may will stick with you then. I'm curious to know in the last 6 to 7 months since 2020 has gone in a very different direction thing we all would have predicted our last Dell Technologies world together. What are you seeing? China. My in terms of acceleration or maybe different industries. What our customers needs, how they changed. I guess I should say in the in 2020. >>So in 2020 we're seeing the adoption off a I even more rapidly. Uh, if you think about customers ranging from like say, uh, media and entertainment industry toe, uh, the customer services off any organization to, uh the healthcare and life sciences with lots off genome analysts is going on in all of these places where we're dealing with large are datasets. We're seeing ah, lot off adoption foster processing off A. I R. Technologies, uh, giving with, say, the all the research that the's Biosciences organizations are happening. Uh, Thomas, I know like you are working with, like, a customer. So, uh, can you give us a little bit more example in there? >>Yes, one of the areas. You know, we're talking about 2021 of the things that we're seeing Mawr and Mawr is just the expansion of Just look at the need for customer support, right arm or folks working remotely their arm or folks that are learning remote. I know my child is going through virtual schools, So think about your I t organization and how Maney calls you're having now to expand. And so this is a great area where we're starting to see innovation within a I and model building to be ableto have you know, let's call it, you know, the next generation of chatbots rights. You can actually build these models off the data toe, augment those soup sports systems >>because you >>have two choices, right? You can either. You know, you you can either expand out your call center right for for we're not sure how long or you can use AI and analytics to help augment to help maybe answer some of those first baseline questions. The great thing about customers who are choosing power scale and Dell Technologies. Their partner is they already have. The resource is to be able to hold on to that data That's gonna help them train those models to help. >>So, Thomas, whenever we're talking about data, the explosions it brings to mind compliance. Protection, security. We've seen ransom where really skyrocket in 2020. Just you know, the other week there was the VA was hit. Um, I think there was also a social media Facebook instagram ticktock, 235 million users because there was an unsecured cloud database. So that vector is expanding. How can you help customers? Customers accelerate their AI projects? Well, ensuring compliance and protection and security of that data. >>Really? That's the sweet spot for power scale. We're talking with customers, right? You know, built on one FS with all the security features in mind. And I, too, came from the analytics world. So I remember in the early days of Hadoop, where, you know, as a software developer, we didn't need security, right? We you know, we were doing researching stuff, but then when we took it to the customer and and we're pushing to production, But what about all the security features. We needed >>the same thing >>for artificial intelligence, right? We want toe. We want to make sure that we're putting those security features and compliance is in. And that's where you know, from from an AI architecture perspective, by starting with one FS is at the heart of that solution. You can know that you're protecting for you know, all the enterprise features that you need, whether it be from compliance, thio, data strategy, toe backup and recovery as well. >>So when we're talking about big data volumes Chanda, mind we have to talk about the hyper scale er's talk to us about, you know, they each offer azure A W s Google cloud hundreds of AI services. So how does DEL help customers use the public cloud the data that's created outside of it and use all of those use that the right AI services to extract that value? >>Yeah. Now, as you mentioned, all of these hyper scholars are they differentiate with our office is like a i m l r Deep Learning Technologies, right? And as our customer, you want toe leverage based off all the, uh, all the cloud has to offer and not stuck with one particular cloud provider. However, we're talking about terabytes off data, right? So if you are happy with what doing service A from cloud provider say Google what you want to move to take advantage off another surface off from Asia? It comes with a very high English p a migration risk on time it will take to move the data itself. Now that's not good, right? As the customer, we should be able to live for it. Best off breed our cloud services for AI and for that matter, for anything across the board. Now, how we help customers is you can have all of your data say, in a managed, uh, managed cloud service provider running on power scale. But then you can connect from this managed cloud service provider directly toe any off the hyper scholars. You can connect toe aws, azure, Google Cloud and even, like even, uh, the in place analytics that power scale offers you can run. Uh, those, uh I mean, run those clouds AI services directly on that data simultaneously from these three, and I'll add like one more thing, right? Thes keep learning. Technologies need GPU power solvers, right? and cloud even within like one cloud is not homogeneous environment. Like sometimes you'll find a US East has or gp part solvers. But like you are in the West and the same for other providers. No, with our still our technologies cloud power scale for multi cloud our scale is sitting outside off those hyper scholars connected directly to our any off this on. Then you can burst into different clouds, take advantage off our spot. Instances on are like leverage. All the GP is not from one particular service provider part. All of those be our hyper scholars. So those are some examples off the work we're doing in the multi cloud world for a I >>So that's day. You're talking about data there. So powers failed for multi cloud for data that's created outside the public club. But Thomas, what about for data that's created inside the cloud? How does Del help with that? >>Yes. So, this year, we actually released a solution, uh, in conjunction with G C. P. So within Google Cloud, you can have power scale for one fs, right? And so that's that native native feature. So, you know, goes through all the compliance and all the features within being a part of that G c p natively eso counts towards your credits and your GP Google building as well. But it's still all the features that you have. And so we've been running some, actually, some benchmarks. So we've got a couple of white papers out there, that kind of detail. You know what we can do from an artificial intelligence perspective back to Sean Demise Example. We were just talking about, you know, being able to use more and more GPU. So we we've done that to run some of our AI benchmarks against that and then also, you know, jumped into the Hadoop space. But because you know, that's 11 area from a power scale, prospective customers were really interested. Um, and they have been for years. And then, really, the the awesome portion about this is for customers that are looking for a hybrid solution. Or maybe it's their first kickoff to it. So back Lisa to those compliance features that we were talking about those air still inherent within that native Google G C P one fs version, but then also for customers that have it on prim. You can use those same features to burst your data into, um, your isil on cluster using all the same native tools that you've been using for years within your enterprise. >>God, it's so starting out for power. Skill for Google Cloud Trying to get back to you Kind of wrapping things up here. What are some of the things that we're going to see next from Dell from an AI Solutions perspective? >>Yes. So we are working on many different interesting projects ranging from, uh, the latest, uh, in video Salford's that they have announced d d x a 100. And in fact, two weeks ago at GTC, uh, Syria announced take too far parts with, uh, it takes a 100 solvers. We're part off that ecosystem. And we are working with, uh, the leading, uh uh, solutions toe benchmark, our ai, uh, environments, uh, for all the storage, uh, ensuring, like we are providing, like, all the throughput and scalability that we have to offer >>Thomas finishing with you from the customer perspective. As we talked about so many changes this year alone as we approach calendar year 2021 what are some of the things that Dell is doing with its customers with its partners, the hyper scale er's and video, for example, Do you think customers are really going to be able to truly accelerate successful AI projects? >>Yeah. So the first thing I'd like to talk about is what we're doing with the D. G. S A 100. So this month that GTC you saw our solution for a reference architecture for the G s, a 100 plus power scale. So you talk about speed and how we can move customers insights. I mean, some of the numbers that we're seeing off of that are really a really amazing right. And so this is gives the customers the ability to still, you know, take all the features and use use I salon and one f s, um, like they have in the past, but now combined with the speed of the A 100 still be ableto speed up. How fast they're using those building out those deep learning models and then secondly, with that that gives them the ability to scale to. So there's some features inherent within this reference architecture that allow for you to make more use, right? So bring mawr data scientists and more modelers GP use because that's one thing you don't see Data scientist turning away right there always like, Hey, you know, I mean, this this project here needs needs a GPU. And so, you know, from a power scale one fs perspective, we want to be able to make sure that we're supporting that. So that as that data continues to grow, which, you know we're seeing is one of the large factors. Whenever we're talking about artificial intelligence is the scale for the data. We wanna them to be able to continue to build out that data consolidation area for all these multiple different workloads. That air coming in. >>Excellent, Thomas. Thanks for sharing that. Hopefully next time we get to see you guys in person and we can talk about a customer who has done something very successful with you guys. Kind of me. Always great to talk to you. Thank you for joining us. >>Thank you. Thank you >>for China. May Mandel and Thomas Henson. I'm Lisa Martin. You're watching the cubes Coverage of Dell Technologies, World 2020

>>Hello, everyone. My name is Rick Pew. I'm a senior product manager at Mirant. This and I have been working on the Doctor Enterprise Container Cloud for the last eight months. Today we're gonna be talking about multi cloud kubernetes. So the first thing to kind of look at is, you know, is multi cloud rial. You know, the terms thrown around a lot and by the way, I should mention that in this presentation, we use the term multi cloud to mean both multi cloud, which you know in the technical sense, really means multiple public clouds and hybrid cloud means public clouds. And on Prem, uh, we use in this presentation will use the term multi cloud to refer to all different types of multiple clouds, whether it's all public cloud or a mixture of on Prem and Public Cloud or, for that matter, multiple on Prem clouds as doctor and price container. Cloud supports all of those scenarios. So it really well, let's look at some research that came out of flex era in their 2020 State of the cloud report. You'll notice that ah, 33% state that they've got multiple public and one private cloud. 53% say they've got multiple public and multiple private cloud. So if you have those two up, you get 86% of the people say that they're in multiple public clowns and at least one private cloud. So I think at this stage we could say that multi cloud is a reality. According to 4 51 research, you know, a number of CEO stated that the strong driver their desire was to optimize cost savings across their private and public clouds. Um, they also wanted to avoid vendor lock in by operating in multiple clouds and try to dissuade their teams from taking too much advantage of a given providers proprietary infrastructure. But they also indicated that there the complexity of using multiple clouds hindered the rate of adoption of doing it doesn't mean they're not doing it. It just means that they don't go assed fast as they would like to go in many cases because of the complexity. And here it Miranda's. We surveyed our customers as well, and they're telling us similar things, you know. Risk management, through the diversification of providers, is key on their list cost optimization and the democratization of allowing their development teams, uh, to create kubernetes clusters without having to file a nightie ticket. But to give them a self service, uh, cloud like environment, even if it's on prem or multi cloud to give them the ability to create their own clusters, resize their own clusters and delete their own clusters without needing to have I t. Or of their operations teams involved at all. But there are some challenges with this, with the different clouds you know require different automation. Thio provisioned the underlying infrastructure or deploy and operating system or deployed kubernetes, for that matter, in a given cloud. You could say that they're not that complicated. They all have, you know, very powerful consoles and a P I s to do that. But did you get across three or four or five different clouds? Then you have to learn three or four or five different AP ice and Web consoles in order to make that happen on in. That scenario is difficult to provide self service for developers across all the cloud options, which is what you want to really accelerate your application innovation. So what's in it for me? You know We've got a number of roles and their prizes developers, operators and business leaders, and they have somewhat different needs. So when the developer side the need is flexibility to meet their development schedules, Number one you know they're under constant pressure to produce, and in order to do that, they need flexibility and in this case, the flexibility to create kubernetes clusters and use them across multiple clouds. Now they also have C I C D tools, and they want them to be able to be normalized on automated across all of the the on prim and public clouds that they're using. You know, in many cases they'll have a test and deployment scenario where they'll want to create a cluster, deploy their software, run their test, score the tests and then delete that cluster because the only point of that cluster, perhaps, was to test ah pipeline of delivery. So they need that kind of flexibility. From the operator's perspective, you know, they always want to be able to customize the control of their infrastructure and deployment. Uh, they certainly have the desire to optimize their optics and Capex fans. They also want to support their develops teams who many times their their customers through a p I access for on Prem and public clouds burst. Scaling is something operators are interested in, and something public clouds can provide eso the ability to scale out into public clouds, perhaps from there on prem infrastructure in a seamless manner. And many times they need to support geographic distribution of applications either for compliance or performance reasons. So having you know, data centers all across the world and be able to specifically target a given region, uh, is high on their list. Business leaders want flexibility and confidence to know that you know, they're on prim and public cloud uh, deployments. Air fully supported. They want to be able, like the operator, optimize their cloud, spends business leaders, think about disaster recovery. So having the applications running and living in different data centers gives them the opportunity to have disaster recovery. And they really want the flexibility of keeping private data under their control. On on Prem In certain applications may access that on Prem. Other applications may be able to fully run in the cloud. So what should I look for in a container cloud? So you really want something that fully automates these cluster deployments for virtual machine or bare metal. The operating system, uh, and kubernetes eso It's not just deploying kubernetes. It's, you know, how do I create my underlying infrastructure of a VM or bare metal? How do I deploy the operating system? And then, on top of all that, I want to be able to deploy kubernetes. Uh, you also want one that gives a unified cluster lifecycle management across all the clouds. So these clusters air running software gets updated. Cooper Netease has a new release cycle. Uh, they come out with something new. It's available, you know, How do you get that across all of your clusters? That air running in multiple clouds. We also need a container cloud that can provide you the visibility through logging, monitoring and alerting again across all the clouds. You know, many offerings have these for a particular cloud, but getting that across multiple clouds, uh, becomes a little more difficult. The Doctor Enterprise Container cloud, you know, is a very strong solution and really meets many of these, uh, dimensions along the left or kind of the dimensions we went through in the last slide we've got on Prem and public clouds as of RG A Today we're supporting open stack and bare metal for the on Prem Solutions and AWS in the public cloud. We'll be adding VM ware very soon for another on Prem uh, solution as well as azure and G C P. So thank you very much. Uh, look forward, Thio answering any questions you might have and we'll call that a rap. Thank you. >>Hi, Rick. Thanks very much for that. For that talk, I I am John James. You've probably seen me in other sessions. I do marketing here in Miran Tous on. I wanted to to take this opportunity while we had Rick to ask some more questions about about multi cloud. It's ah, potentially a pretty big topic, isn't it, Rick? >>Yeah. I mean, you know, the devil's in the details and there's, uh, lots of details that we could go through if you'd like, be happy to answer any questions that you have. >>Well, we've been talking about hybrid cloud for literally years. Um, this is something that I think you know, several generations of folks in the in the I. A s space doing on premise. I s, for example, with open stack the way Miran Tous Uh does, um, found, um, you know, thought that that it had a lot of potential. A lot of enterprises believed that, but there were There were things stopping people from from making it. Really, In many cases, um, it required a very, ah, very high degree of willingness to create homogeneous platforms in the cloud and on the premise. Um, and that was often very challenging. Um, but it seems like with things like kubernetes and with the isolation provided by containers, that this is beginning to shift, that that people are actually looking for some degree of application portability between their own Prem and there and their cloud environments. And that this is opening up, Uh, you know, investment on interest in pursuing this stuff. Is that the right perception? >>Yeah. So let's let's break that down a little bit. So what's nice about kubernetes is through the a. P. I s are the same. Regardless of whether it's something that Google or or a W s is offering as a platform as a service or whether you've taken the upstream open source project and deploy it yourself on parameter in a public cloud or whatever the scenario might be or could be a competitor of Frances's product, the Kubernetes A. P I is the same, which is the thing that really gives you that application portability. So you know, the container itself is contained arising, obviously your application and minimizing any kind of dependency issues that you might have And then the ability to deploy that to any of the coup bernetti clusters you know, is the same regardless of where it's running, the complexity comes and how doe I actually spend up a cluster in AWS and open stack and D M Where and gp An azure. How do I build that infrastructure and and spin that up and then, you know, used the ubiquitous kubernetes a p I toe actually deploy my application and get it to run. So you know what we've done is we've we've unified and created A I use the word normalized. But a lot of times people think that normalization means that you're kind of going to a lowest common denominator, which really isn't the case and how we've attacked the the enabling of multi cloud. Uh, you know, what we've done is that we've looked at each one of the providers and are basically providing an AP that allows you to utilize. You know, whatever the best of you know, that particular breed of provider has and not, uh, you know, going to at least common denominator. But, you know, still giving you a ah single ap by which you can, you know, create the infrastructure and the infrastructure could be on Prem is a bare metal infrastructure. It could be on preeminent open stack or VM ware infrastructure. Any of the public clouds, you know, used to have a a napi I that works for all of them. And we've implemented that a p i as an extension to kubernetes itself. So all of the developers, Dev ops and operators that air already familiar operating within the, uh, within the aapi of kubernetes. It's very, very natural. Extension toe actually be able to spend up these clusters and deploy them >>Now that's interesting. Without giving away, obviously what? Maybe special sauce. Um, are you actually using operators to do this in the Cooper 90? Sense of the word? >>Yes. Yeah, we've extended it with with C R D s, uh, and and operators and controllers, you know in the way that it was meant to be extended. So Kubernetes has a recipe on how you extend their A P I on that. That's what we used as our model. >>That, at least to me, makes enormous sense. Nick Chase, My colleague and I were digging into operators a couple of weeks ago, and that's a very elegant technology. Obviously, it's a it's evolving very fast, but it's remarkably unintimidating once you start trying to write them. We were able toe to compose operators around Cron and other simple processes and just, >>you know, >>a couple of minutes on day worked, which I found pretty astonishing. >>Yeah, I mean, you know, Kubernetes does a lot of things and they spent a lot of effort, um, in being able, you know, knowing that their a p I was gonna be ubiquitous and knowing that people wanted to extend it, uh, they spent a lot of effort in the early development days of being able to define that a p I to find what an operator was, what a controller was, how they interact. How a third party who doesn't know anything about the internals of kubernetes could add whatever it is that they wanted, you know, and follow the model that makes it work. Exactly. Aziz, the native kubernetes ap CSTO >>What's also fascinating to me? And, you know, I've I've had a little perspective on this over the past, uh, several weeks or a month or so working with various stakeholders inside the company around sessions related to this event that the understanding of how things work is by no means evenly distributed, even in a company as sort of tightly knit as Moran Tous. Um, some people who shall remain nameless have represented to me that Dr Underprice Container Cloud basically works. Uh, if you handed some of the EMS, it will make things for you, you know, and this is clearly not what's going on that that what's going on is a lot more nuanced that you are using, um, optimal resource is from each provider to provide, uh, you know, really coherent architected solutions. Um, the load balancing the d. N s. The storage that this that that right? Um all of which would ultimately be. And, you know, you've probably tried this. I certainly have hard to script by yourself in answerable or cloud formation or whatever. Um, this is, you know, this is not easy work. I I wrote a about the middle of last year for my prior employer. I wrote a dip lawyer in no Js against the raw aws a piece for deployment and configuration of virtual networks and servers. Um, and that was not a trivial project. Um, it took a long time to get thio. Uh, you know, a dependable result. And to do it in parallel and do other things that you need to do in order to maintain speed. One of the things, in fact, that I've noticed in working with Dr Enterprise Container Cloud recently, is how much parallelism it's capable of within single platforms. It's It's pretty powerful. I mean, if you want to clusters to be deployed simultaneously, that's not hard for Doc. Aerated price container cloud to dio on. I found it pretty remarkable because I have sat in front of a single laptop trying to churn out of cluster under answerable, for example, and just on >>you get into that serial nature, your >>poor little devil, every you know, it's it's going out and it's ssh, Indian Terminals and it's pretending it's a person and it's doing all that stuff. This is much more magical. Um, so So that's all built into the system to, isn't it? >>Yeah. Interesting, Really Interesting point on that. Is that you know, the complexity isn't not necessarily and just creating a virtual machine because all of these companies have, you know, spend a lot of effort to try to make that as easy as possible. But when you get into networking, load balancing, routing, storage and hooking those up, you know, two containers automating that if you were to do that in terror form or answerable or something like that is many, many, many lines of code, you know, people have to experiment. Could you never get it right the first or second or the third time? Uh, you know, and then you have to maintain that. So one of the things that we've heard from customers that have looked a container cloud was that they just can't wait to throw away their answerable or their terror form that they've been maintaining for a couple of years. The kind of enables them to do this. It's very brittle. If if the clouds change something, you know on the network side, let's say that's really buried. And it's not something that's kind of top of mind. Uh, you know, your your thing fails or maybe worse, you think that it works. And it's not until you actually go to use it that you notice that you can't get any of your containers. So you know, it's really great the way that we've simplified that for the users and again democratizing it. So the developers and Dev ops people can create these clusters, you know, with ease and not worry about all the complexities of networking and storage. >>Another thing that amazed me as I was digging into my first, uh, Dr Price container Cloud Management cluster deployment was how, uh, I want I don't want to use the word nuanced again, but I can't think of a better word. Nuanced. The the security thinking is in how things air set up. How, um, really delicate the thinking about about how much credential power you give to the deploy. Er the to the seed server that deploys your management cluster as opposed thio Um uh or rather the how much how much administrative access you give to the to the administrator who owns the entire implementation around a given provider versus how much power the seed server gets because that gets its own user right? It gets a bootstrap user specifically created so that it's not your administrator, you know, more limited visibility and permissions. And this whole hierarchy of permissions is then extended down into the child clusters that this management cluster will ultimately create. So that Dev's who request clusters will get appropriate permissions granted within. Ah, you know, a corporate schema of permissions. But they don't get the keys to the kingdom. They don't have access to anything they don't you know they're not supposed to have access to, but within their own scope, they're safe. They could do anything they want, so it's like a It's a It's a really neat kind of elegant way of protecting organizations against, for example, resource over use. Um, you know, give people the power to deploy clusters, and basically you're giving them the power toe. Make sure that a big bill hits you know, your corporate accounting office at the end of the billing cycle, um so there have to be controls and those controls exist in this, you know, in this. >>Yeah, And there's kind of two flavors of that. One is kind of the day one that you're doing the deployment you mentioned the seed servers, you know, And then it creates a bastion server, and then it creates, you know, the management cluster and so forth, you know, and how all those permissions air handled. And then once the system is running, you know, then you have full access to going into key cloak, which is a very powerful open source identity management tool on you have dozens of, you know, granular permissions that you can give to an individual user that gives them permission to do certain things and not others within the context of kubernetes eso. It's really well thought out. And the defaults, you know, our 80% right. You know, there's very few people are gonna have to go in and sort of change those defaults. You mentioned the corporate directory. You know, hooks right upto l bap or active directory can suck everybody down. So there's no kind of work from a day. One perspective of having to go add. You know everybody that you can think of different teams and groupings of of people. Uh, you know, that's kind of all given from the three interface to the corporate directory. And so it just makes kind of managing the users and and controlling who can do what? Uh, really easy. And, you know, you know, day one day two it's really almost like our one hour to write because it's just all the defaults were really well thought out. You can deploy, you know, very powerful doctor and price container cloud, you know, within an hour, and then you could just start using it. And you know, you can create users if you want. You can use the default users. That air set up a time goes on, you can fine tune that, and it's a really, really nice model again for the whole frictionless democratization of giving developers the ability to go in and get it out of, you know, kind of their way and doing what they want to do. And I t is happy to do that because they don't like dozens of tickets and saying, you know, create a cluster for this team created cluster for that team. You know, here's the size of these guys. Want to resize when you know let's move all that into a self service model and really fulfill the prophecy of, you know, speeding up application development. >>It strikes me is extremely ironic that one of the things that public cloud providers bless them, uh, have always claimed, is that their products provide this democratization when in the experience, I think my own experience and the experience of most of the AWS developers, for example, not toe you know, name names, um, that I've encountered is that an initial experience of trying to start start a virtual machine and figuring out how to log into it? A. W s could take the better part of an afternoon. It's just it's not familiar once you have it in your fingers. Boom. Two seconds, right. But, wow, that learning curve is steep and precipitous, and you slip back and you make stupid mistakes your first couple 1000 times through the loop. Um, by letting people skip that and letting them skip it potentially on multiple providers, in a sense, I would think products like this are actually doing the public cloud industry is, you know, a real surface Hide as much of that as you can without without taking the power away. Because ultimately people want, you know, to control their destiny. They want choice for a reason. Um, and and they want access to the infinite services And, uh, and, uh, innovation that AWS and Azure and Google are all doing on their platforms. >>Yeah, you know, and they're solving, uh, very broad problems in the public clouds, you know, here were saying, you know, this is a world of containers, right? This is a world of orchestration of these containers. And why should I have to worry about the underlying infrastructure, whether it's a virtual machine or bare metal? You know, I shouldn't care if I'm an application developer developing some database application. You know, the last thing I wanna worry about is how do I go in and create a virtual machine? Oh, this is running. And Google. It's totally different than the one I was creating. An AWS I can't find. You know where I get the I P address in Google. It's not like it was an eight of us, you know, and you have to relearn the whole thing. And that's really not what your job is. Anyways, your job is to write data base coat, for example. And what you really want to do is just push a button, deploy a nor kiss traitor, get your app on it and start debugging it and getting it >>to work. Yep. Yeah, it's It's powerful. I've been really excited to work with the product the past week or so, and, uh, I hope that folks will look at the links at the bottoms of our thank you slides and, uh, and, uh, avail themselves of of free trial downloads of both Dr Enterprise Container, Cloud and Lens. Thank you very much for spending this extra time with me. Rick. I I think we've produced some added value here for for attendees. >>Well, thank you, John. I appreciate your help. >>Have a great rest of your session by bike. >>Okay, Thanks. Bye.

>>from our studios in the heart of Silicon Valley. Palo ALTO, California It is a cute conversation. >>Welcome to another wicked bond digital community event, this one sponsored by Clue Me. Oh, I'm your host, Peter Burroughs. Any business that aspires to be a digital business needs to think about its data differently. It needs to think about how data could be applied to customer experience, value propositions, operations and improve profitability and strategic options for the businesses that moves forward. But that means openly, either. We're thinking about how we embed data more deeply into our operations. That means we must also think about how we're going to protect that data. So the business is not suffer because someone got a hold of our data or corrupted our data or that system just failed and we needed to restore that data very quickly. Now what we want to be able to do is we're going to do that in a way that's natural and looks a lot like a cloud because we want that cloud experience in our data protection as well. So that's we're gonna talk about with Clue Meo Today, a lot of folks think in terms of moving all the data into the cloud. We think increasingly we have to recognize the cloud is not a strategy for centralizing data but rather distributing data and being able to protect that data where it is utilizing a simple, common cloudlike experience has become an increasingly central competitive need for a lot of digital enterprises. The first conversation we had was with poo John Kamar, who John is a CEO and co founder of Cuneo. Let's hear a Peugeot on had to say about data value. Data service is and clue Meo. John, Welcome to the show. >>Thank you. Very nice to be here. >>So give us the update. Include me. Oh, >>so come you. Ah, a two year old company, right? We dress recently launched out of stealth. So so far, you know, we we came out with the innovative offering which is a sass solution to go and protect on premises in November and vmc environments. That's what we launched out of style two months ago. We want our best of show. When we came out off Stilton in November 2019. But ultimately we started with a vision about protecting data respective off buried, recites So it was all about, you know, you know, on premises on Cloud and other SAS service is so one single service that protects data introspective about recites So far, we executed on on premises VM wear and Vmc. Today What we're announcing for the first time is our protection to go and protect applications natively built on aws. So these are application that ineptitude natively built on aws that clue me in as a service will protect respective off. You know them running, you know, in one region or cross region cross accounts and a single service little our customers to protect native AWS applications. The other big announcement we're making is a new round of financing, and that is testament to the interest in the space and the innovative nature off the platform that we have built. So when we came out of still, we announced we had raised two rounds of financing $51 million in series and series B round of financing. Today, what we're announcing is a serious see around the financing off $135 million the largest. I would say Siri see financing for a sass and the price company, especially a company that's a little over two years >>old. Look, graduations that's gonna buy a lot of new technology and a lot of customer engagement. But what customers is a set up from where customers are really looking for is they're looking for tooling and methods and capabilities that allow them to treat their data differently. Talk a bit about the central importance of data and how it's driving decisions. ACLU mia >>Yes, so fundamentally. You know, when we built out the data platform, it was about going after the data protection as the first use case in the platform. Longer term, the journey really is to go from a data protection company to a data management company, and this is possible for the first time because you have the public cloud on your side. If you're truly built a platform for the cloud on the public cloud, you have this distinct and want a JJ off. Now, taking the data that you're protecting and really leveraging it for other service is that you can enable the enterprise for, and this is exactly what and the prices are asking for, especially as they you know, you make a transition from on premises. So the public cloud where they're powering on more and more applications in the public cloud and they really, you know, sometimes have no idea in terms off where the data is sitting and how they can take advantage off all these data sources that ultimately clueless protecting >>Well, no idea where the data sitting take advantage of these data. Sources presumably facilitate new classes of integration because that's how you generate value out of data. That suggests that we're not just looking at protection as crucially important as it is we're looking at new classes of service is they're gonna make it possible to alter the way you think about data management. If I got that right and what are those in service is? >>Yes, it's It's a journey, As I said, very starting with Finnegan Data protection. It's also about doing there the protection across multiple clouds, right? So ultimately we had a platform. Even though we're announcing, you know, aws, you know, applications support. Today. We've already done the ember and BMC as we go along. You'll see us kind of doing this across multiple clouds, an application that's built on the cloud running across multiple clouds, AWS, Azure and DCP. Whatever it might be, you see, it's kind of doing there, the protection across in applications and multiple clouds. And then it's about going and saying, Can we take advantage of the data that we're protecting and really power on adjusting to use cases, they could be security use cases because we know exactly what's changing when it's changing. There could be infrastructure. Analytics use cases because people are running tens of thousands off instances and containers and envy EMS in the public cloud. And if a problem happens, nobody really knows what caused it. And we have all the data and we can kind off index it in the back end and lies in the back end without the customer needing to lift a finger and really show them what happened in their environment that didn't know about right. So there's a lot of interesting use cases that get powered on because you have the ability to index all the data year. You have the ability to essentially look at all the changes that are happening and really give that visibility. Tow the end customer and all of this one click and automating it without the customer needing to do much. >>I will tell you this that we've talked to a number of customers of Romeo and the fundamental choice. The clue. Meo choice was simplicity. How are you going to sustain that? Even as you have these new classes of service is >>that is the key right? And that is about the foundation we have built at the end of the day, right? So if you look at all of our customers that have on border today, it's really the experience where in less than 15 minutes they can essentially start enjoying the power of the platform and the back end that we have built. And the focus on design that we have is ultimately why we're able to do this with simplicity. So so when when we when we think about you know all the things we do in the back, and there's obviously a lot of complexity in the back end because it is a complex platform. But every time we ask ourselves the question that okay from a customer perspective, how do we make sure that it is one click and easy for them? So that focus and that attention to detail that we have behind the scenes to make sure that the customer ultimately should just consumed the service and should not need to do anything more than what they absolutely need to do so that they can essentially focus on what eggs value to the business >>takes a lot of technology, a lot of dedication to make complex things really simple. Absolutely. John Kumar, CEO and co founder of Coolio. Thanks very much for being on the Cube. Thank you. Great conversation with you, John. Data value leading to data service is now. Let's think a little bit more about how enterprises ultimately need to start thinking about how to manifest that in a cloud rich world, Chad Kenney is the vice president and chief acknowledges a Cuneo and Chad and I had an opportunity to sit down to talk about some of the interesting approach. Is that air possible because of cloud and very importantly, to talk about a new announcement that clue me is making as they expand their support of different cloud types? What's your Chad had to say? The notion of data service is has been around for a long time, but it's being upended, recast, reformed as a consequence of what cloud can do. But that also means that Cloud is creating new ways of thinking about data service. Is new opportunities to introduce and drive this powerful approach of thinking about digital businesses centralized assets and to have that conversation about what that means. We've got Chad Candy, who's a VP and chief technologist of Kumiko with us today. Chad, welcome to the Cube. >>Thanks so much for having me. >>Okay, so what? Start with that notion of data service is and the role because gonna play clue. Meo has looked at this problem or looked this challenge from the ground up. What does that mean? >>So if you look at the cloud is a whole customers have gone through a significant journey. We've seen you know that the first shadow I t kind of play out where people decided to go to the cloud I t was too slow. It moved into kind of a cloud first movement where people realize the power of cloud service is that then got them to understand a little bit of interesting things that played out one moving applications as they exist. We're not very efficient, and so they needed to re architect certain applications. Second, SAS was a core way of getting to the cloud in a very simplistic fashion without having to do much of whatsoever. And so, for applications that were not core competencies, they realized they should go sass. And for anything that was a core competency, they needed to really re architect to be able to take advantage of those very powerful cloud service is. And so when you look at it, if people were to develop applications today, cloud is the default. They'd go tours. And so for us, we had the luxury of building from the cloud up on these very powerful cloud service is to enable a much more simple model for our customers to consume. But even more so to be able to actually leverage the agility and elasticity of the cloud. Think about this for a quick second. We can take facilities, break them up, expand them across many different compute resource is within the cloud versus having to take kind of what you did on prim in a single server or multitudes of servers and try to plant that in the cloud from a customer's experience perspective. It's vastly different. You get a world where you don't think about how you manage the infrastructure, how you manage the service, you just consume it. And the value that customers get out of that is not only getting their data there, which is the on ramp around our data protection mechanisms, but also being able to leverage cloud. Native service is on top of that data in the longer term, as we have this one comment global index and platform. What we're super excited today to announce is that we're adding in eight of US native capabilities to be ableto protect that data in the public cloud. And this is kind of the default place where most people go to from a cloud perspective to really get their applications are up and running and take advantage of a lot of those cloud. Native service is >>well, if you're gonna be Claude native and promised to customers is going to support There were clothes. You've got to be obviously on eight of us, So congratulations on that. But let's go back to this notion of you use the word powerful 80 of the U. S. Is a mature platform, G C P is coming along very rapidly. Azure is also very, very good. There are others as well, but sometimes enterprises discover that they have to make some tradeoffs. To get the simplicity, they have to get less function, to get the reliability they have to get rid of simplicity. How does clue Meo think through those trade offs to deliver that simple? That powerful, that reliable platform for something is important. Data protection and data service is in general, >>so we wanted to create an experience that was single click, discover everything and be able to help people consume that service quickly. And if you look at the problem that people are dealing with a customer's talk to us about this all time is the power of the cloud resulted in hundreds, if not thousands of accounts within eight of us. And now you get into a world where you're having to try to figure out how did I manage all of these for one? Discover all of it and consistently make sure that my data, which, as you've mentioned, is incredibly important to businesses today as protected. And so having that one common view is incredibly important to start with, and the simplicity of that is immensely powerful. When you look at what we do as a business, to make sure that that continues to occur is first, we leverage cloud. Native Service is on the back, which are complex, and getting those things to run and orchestrate are things that we build on the back end on the front end. We take the customers view and looking at what is the most simple way of getting this experience to occur for both discovery as well as you know, backup recovery and even being able to search in a global fashion and so really taking their seats to figure out what would be the easiest way to both consume the service and then also be able to get value from it by running that service >>A W s has been around well, a ws in many respects founded the cloud industry. It's it's certainly sales force on the South side. But a W. S is the first company to make the promise that it was gonna provide this very flexible, very powerful, very agile infrastructures of service. And they've done absolutely marvelous job about it, and they've also advanced the stadium to the technology dramatically and in many respects, are in the driver's seat. What tradeoffs? What limits does your new platform faces? It goes to eight of us. Or is it the same Coolio experience, adding, Now all of the capabilities of eight of us? >>It's a great question. I think a lot of solutions out there today are different parts and pieces kind of club together. What we built is a platform that these new service is just get instantly added. Next time you log in to that service, you'll see that that available Thio and you could just go ahead and log in to your accounts and build to discover directly. And I think that the the power of sass is really that not only have we made it immensely secure, which is something that people think about quite a bit with having, you know, not only did in flight, but data at rest, encryption on and leveraging really the cloud capabilities of security. But we've made it incredibly simple for them to be able to consume that easily, literally not lift a finger to get anything done. It's available for you when you log into that system. And so having more and more data sources in one single pane of glass and being able to see all the accounts, especially in AWS, where you have quite a few of those accounts, and to be able to apply policies in a consistent fashion to ensure that your you know, compliant within the environment for whatever business requirements that you have around data protection is immensely powerful to our >>customers. Judd Jenny, chief technologist Clue me Oh, thanks very much for being on the Cube. Thank you. Great conversation. Chad especially interested in hearing about how Camilo is being extended to include eight of US service, is within its overall data protection approach and obviously into data service is let's take a little bit more into that clue. MEOWS actually generated and prepared a short video we could take a look at that goes a little bit more deeply into how this is all gonna work. >>Enterprises air moving rapidly to the cloud. Embracing sass for simplified delivery of key service is in this cloud centric world. I T teams could focus on more strategic work, accelerating digital transformation initiatives when it comes to backup. I t is stuck designing, patching and capacity planning for on Prem Systems. Snapshots alone for data protection in the public cloud is risky, and there are hundreds of unprotected SAS applications in the typical enterprise. Move to cloud should make backup simpler, but it can quickly become exponentially worse. It's time to rethink the backup experience. What if there were no hardware, software or virtual appliances to size, configure, manage or even by it all? And by adding enterprise backup, public cloud workloads are no longer exposed to accidental data Deletion and Ransomware and Clooney. Oh, we deliver secure data backup and recovery without any of that complexity or risk. We provide all of the critical functions of enterprise backup de Doop and scheduling user and key management and cataloging because were built in the public cloud, weaken rapidly, deliver new innovations and take advantage of inherent data security controls. Our mission is to protect your data wherever it's stored. The clue. Meo authentic SAS backup experience scales on demand to manage and protect your data more easily and efficiently. And without things like cloud bills or egress charges, Clooney oh gives you predictable costs. Monitor and global back of compliance is far simpler, and the built in always on security of clue. Meo means that your data is safe. Take advantage of the cloud for backup with no constraints. Clue. Meo Authentic sass for the Enterprise. >>Great video as we think about moving forward in the future and what customers are trying to do. We have to think more in terms of the native service is that cloud can provide and how to fully exploit them to increase the aggregate flexibility both within our enterprises, but also based on what our supplies have to offer. We had a great conversation with Runes Young, who is thesis CTO and co founder of Cuneo, about just that. Let's hear it wound had to say everybody's talking about the cloud and what the cloud might be able to do for their business. The challenge is there are a limited number of people in the world who really understands what it means to build for the cloud utilizing the cloud. It's a lot of approximations out there, but not a lot of folks are deeply involved in actually doing it right. We've got one here with us today, wound junk is thesis CEO and co founder of Clue Meo Womb. Welcome to the Cube. >>Happy to be here. >>So let's start with this issue of what it means to build for the cloud. Now Lou MEOWS made the decision to have everything fit into that as a service model. What is that practically need? >>So from the engineering point of view, building our sauce application is fundamentally different. So the way that I'll go and say is that at Cuneo we actually don't build software and ship software. What we actually do, it builds service and service is what you're actually shipped Our customers. Let me give you an example. In the case of Kun, you they say backups fail like so far sometimes fails. We get that failures too. The difference in between Clooney oh, and traditional solutions is that if something were to fail, we are they one detecting that failure before our customers do Not only that, when something fails, we actually know exactly why it failed. Therefore, we can actually troubleshoot it, and we can actually fix it and operate the service without the customer intervention. So it's not about the books also or about the troubleshooting aspect, but it's also about new features. If you were to introduce a new features, we can actually do this without having customers upgraded call. We will actually do it ourselves. So essentially it frees the customers from actually doing all these actions because we will do them on behalf of them >>at scale. And I think that's the second thing I want to talk about quickly. Is that the ability to use the cloud to do many of the things that you're talking about? At scale creates incredible ranges of options that customers have at their disposal. So, for example, a W s customers of historically used things like snapshots to provide ah modicum of data protection to their AWS workloads. But there are other new options that could be applied if the systems are built to supply them. Give us a sense of how clue Meal is looking at this question of, you know, snapshots were something else. >>Yes, So, basically, traditionally, even on the imprints, out of the things, you have something called the snapshots and you had your backups right, and they're they're fundamentally different. But if you actually shift your gears and you look at what A. W s offers today. They actually offers stability for you to take snapshots. But actually, that's not a backup, right, And they're fundamentally different. So let's talk about it a little bit more what it means to be snapshots and a backup, right? So they say, there's a bad actor and your account gets compromised like your AWS account gets compromised. So then the bad actor has access not only to the EBS volumes, but also to the snap shows. What that means is that that person can actually go in and delete the E. V s volume as well as the TVs nuptials. Now, if you had a backup, let's say you are should take a backup of that TVs William to whom you that bad actor would have access to the CVS volumes. However, it won't be able to delete the backup that we actually have, including you. So in the whole thing. The idea off Romeo is that you should be able to protect all of your assets, that being either an on Prem or neither of us by setting up a single policies. And these are true backups and not just snapshots >>and that leads to the last question I have, which is ultimately the ability to introduce thes capabilities. At scale creates a lot of new opportunities of customers can utilize to do a better job of building applications, but also, I presume, managing how they use AWS because snapshots and other types of service can expand dramatically, which can increase your cost. How is doing it better with things like Native Backup Service is improve customers ability to administer the AWS spend and accounts. >>So, great question. So, essentially, if you look at the enterprises today, obviously they have multiple on premise data centers and also a different car providers that they use like AWS and Azure and also a few SAS applications, Right? So then the idea is for Camilo is to create this single platform what all of the stains can actually be backed up in a uniform way where you can actually manage all of them. And then the other thing is all doing it in the cloud. So if you think about it, if you don't solve the problem, fundamental in the cow, their stings that you end up paying later on. So let's take an example. Right. Uh, moving bites. Moving bites in between one server to the other. Traditionally basically moving bites from one rack to the other. It was always free. You never had to pay anything for that. >>Certainly in the data center. >>Right? But if you actually go to the public cloud, you cannot say the same thing, right? Basically, moving by across AWS recent regions is not free anymore. Moving data from AWS to the on premises. That's not for either. So these are all the things that you know cop provider service providers are gods has to consider and actually solved so that the customers can on Lee back it up into come you. But then they actually can leverage different cloud providers, you know, in a seamless way, without having to worry all of this costs associated with it so criminal we should be able to back it up. But we should be able to also offer mobility in between either aws back up the M word or the M C. >>So if I can kind of summarize what you just said that you want to be able to provide to an account to an enterprise, the ability to not have to worry about the back and infrastructure from a technical and process standpoint, but not also have to worry so much about the back and infrastructure from a cost of financial standpoint that by providing a service and then administering how that service is optimally handled, the customer doesn't have to think about some of those financial considerations of moving get around in the same way that they used to. Have I got that right, >>I absolutely, yes, basically multiple accounts, multiple regions, multiple couple providers. It is extremely hard to manage. What come your does. It will actually provide you a single pane of glass where you can actually manage them all. But then, if you actually think about just and manageability this, actually you can actually do that by just building a management layer on top of it. But more importantly, you really need to have a single data repository for you. For us to be able to provide a true mobility in between them. One is about managing, but the other thing is about if you're done, if you're done in the real divide way, it provides you the ability to move them and leverages the cloud power so that you don't have to worry about the cloud expenses but whom you internally is the one that actually optimizing all of this for our customers. >>Wound young cto and co founder of Coolio. Thanks very much for being on the Q. Thank you. Thanks very much. Room I want to thank clue me Oh, for providing this important content about the increasingly important evolution of data protection Cloud. Now, here's your opportunity to weigh in on this crucially important arena. What do you think about this evolving relationship? How do you foresee it operating in your enterprise? What comments do you have? What questions do you have of the thought leaders from Clue Me? Oh, and elsewhere. That's what we gonna do now we're gonna go into the crowd chat. We're gonna hear from each other about this really important topic and what you foresee in your enterprise as your digital business transforms, it's crochet

>>lie from Copenhagen, Denmark. >>It's the >>Q covering Nutanix dot Next 2019. Brought to you by >>Nutanix. Welcome back, everyone to the cubes. Live coverage of Nutanix. Stop! Next here in Copenhagen, Denmark. I'm your host, Rebecca Knight, coasting along side of stew minimum. Of course. We're joined by Regime Mirani. He is the CTO clad platforms at Nutanix. Thank you so much for coming on the Cubans. You need >>to be here as usual. >>So you were up on the main stage talking about your guiding force. Your mission to make enterprise computing so reliable, so ubiquitous that it's invisible. >>You don't think about >>it. You don't even get a little No, I mean, look, >>if you look at any successful technology, consumer technology doesn't need to be aware of the details around it, right? I mean, take cars, even because the first introduced you probably had to understand Rick operate. There was how it all works. Remember for water in the radiator. But most people don't know how to do that today. I wouldn't know how to do that today, even though my Utah actually had to do some of those things. Um, that isn't the point. of the cars or self driving. Now the same thing should happen to computing. And we spend way too much time today just doing things that keep the light. Don't nights on. Just imagine infrastructure patching things up, grading them. I really should be something that not what idea is doing i d should be focusing on the business, delivering applications that their customers need and not so much on managing infrastructure. >>Rajiv, that one click Simplicity is so important, yet we know things are becoming even more complicated. Bring us inside a little bit that you know, you've got 14,000 customers. Guess and there's been a major, basically rewrite of a less to be able to be ready for all of the new ash cloud Native envy me obtained, you know, you name it all of these things. How do you balance getting all of this new stuff up with making sure that you keep that simplicity and don't make things for all of your customers while all the jet engines, uh, you know, >>it takes constant effort. It takes a conscious effort to make sure that things are in drifting away from our goal of being simple and to be frank. At times it has and you know, we periodically to audits off all our work floors. Make sure that as simple as you think they are and haven't drifted over time. And occasionally we do find some rail clunkers and have to go back and fix those things. What >>makes it >>different is that we start with a fairly opinionated view on how things should be done. The idea is to make it simple for 99% of the people, while still offering the all that washed options of one person power users would need them and making sure that we understand what 90% 99% of people need. And focusing on that is very important to a lot of customer focus study sort of design reviews, but also this constant going back and you're taking work feel like we m creation like provisioning of'em. When he started, it was pretty simple right then, as we started adding more and more options eyes, this thing going to use a PC I passed through isn't going to use this option. That option suddenly realized that now they're 30 things that people are feeling into provisional we have, most of which nobody cares I care about. So you go back, read I tte keep doing that again and again and again. >>So rich Eve It's one thing when you talk about living on different servers, whether it be super micro underneath or Delhi Emcee Lenovo H p e. It's >>gonna be a >>little bit different if you're talking about where you're going with H p E Green Lake with, you know, the X in AWS that you talk about when I talk to people, you know, it's like, Oh, I'm trying to use terror form and you know, But I have to write it. One way to work with Amazon. I have to write it another way. If it's, you know, azure G C P S o. You know, will Nutanix be able to keep that simplicity and bring, you know, homogeneity to thes dispersed invite? >>Absolutely. So the point is, watch a layer of abstraction right the way we are going to public cloud away we go every server winter out the way of doing things and sigh all if it starts with the hyper wiser and the story of stock and networking with three layers of abstraction. And if you have the same three components everywhere, everything we built on top of that remains exactly the same. Prison was the same on a P S. On the same. Everything looks the same. So higher level constructs like calm and so on don't have to be aware of what the actual substrate is creating a calm blueprint, whether it works on ZAY on AWS or whether Trump's on SX or whether runs on Nutanix H way. The blue blueprint remains exactly the same. Now, if you want to consume more, service is if you want to consume. So this is an Amazon, which are not available on premises. You want to use things like auto scaling groups in Ec2. Sure, you could then create blueprints that our customers we're putting in the substrate. >>So, in terms of this, you said, you start with a very opinionated place of where the customer is well, First of all, it's based on customer feedback and customer surveys. And so where were are you right now in terms of where the customer is? Are you meeting the customer now, or is the customer ahead or what? Where would you describe that? I think it >>depends on what you're looking at. If you're looking at the core products, absolutely, the customers are with us. They were ready to consume. They actually drive a lot of the innovation that we're doing. We're feeding, feeding back changes that we could be doing to make things even simpler on the private cloud side that's getting there. I think we get a lot off feedback on files on on present pro on com on on Flow because those have started getting a lot of adoption in the market, and we do get a lot of feedback on them on. So our newer products that you started a war being more recently, it's a more collaborative process. There were actually working with customers directly understanding their problems on dhe, moving a roadmap forward based on that. So while it's early in terms off adoption in production, the whole process is very collaborative in those situations. So we really are very close to the customers there. >>What are some of the biggest customer problems right now that they're facing what's what's keeping them up at night and therefore keeping you up at night? >>Security is always a big one. Complexity, people skills. All those things are big problems. In fact, one of the biggest things like that was just training enough people to handle all the complexity in a data set. Is the Morrigan removed from that? The more they don't have to focus on that, the easier you make their lives. The other thing is just a lot of time to spend on routine activities which, which acquired disruption to service is right. This is something we've talked about before. Why does it Why does it require a legacy three tier system to have maintenance windows and downtime to do an upgrade? Google our has downtime. Google is never down for maintenance. Doesn't mean they're not already there waiting all the time. So how do we bring that same kind of capabilities on premises that's gonna focus our long power? >>So, Rajiv, when I'm talking to users out there, when they talk about all of the items that are out there that they need to deal with and the routine task automation is something keeps, you know, coming up. So tell us where automation fits into some of the new things that you were talking about today in this week with your customer? >>Yeah, automation >>for us. Waking automation in three steps anything that's automatic better be safe. First of all, safety is paramount. Started security. It has to be simple, and we talked about how calm provides for that. And then you can start adding in this new wave off technologies around artificial intelligence and machine learning. And it's not so much about automation right now. It's all gone to me. It's it's autonomous operations, not just scripts. That due to a task on dhe, that's >>an area >>we invested in very heavily early on with our prison pro product way, build our own patented or thumbs for machine learning applied them to operational metrics like capacity planning. And what if modeling and dynamic alerts and what we've been doing with that is extending that more into the application layer so that not only can you apply these algorithms to CP when memory, we can actually get insights into Hey, the Leighton see on this particular application looks somewhat unusual, or the amount of cash available on a sequel server is unusually low and act on those, and the other part is acting on on alert. Something happens. There's a human being need to get in wall to solve for that. And if it does, then well, it's not really automatic. Right? So that's the other part that we introduce, which is a cross for a product which lets you define these action chains that automatically, uh, what about to be triggered when Annie went on alert takes place, they can go ahead and fix the problem. But also, you know, simple things like send your slack notification or an email locked. They went, maybe create a snapshot of your wee am so that you could go back and be back problems later. All that sort of thing made really, really simple. >>Yes, it goes back to the simplicity and the invisibility to this. >>Yes, yes. Uh, autonomous data centers, by definition, have to be invisible, right? If if if If you're to get involved in marriage and autonomous Data center, then what's the plane? It's a point. Exactly. So the whole idea is that, uh, human involvement in day to day operations against solo that everybody's focused on applications on line of business use cases. >>Rajiv, when it when it comes to those applications. You know, you talked about some of the new enhancements like envy me on and obtain, You know, Where are your customers today? You know, Are there any interesting applications that you're seeing them deploying today? Ah, Pattern. I've talked about the last couple of years of the Nutanix show, is modernized the platform and then modernized the absolute top of it. Things like container ization. I'm sure to bell curve in a journey where all the customers But you know, what are some of the patterns that air starting emergen where they finding success? >>Yeah, This >>whole wave off new applications around data pipelines with Kafka spark things like that Apache stack effectively which are putting more more off load on storage in particular. So that's that's one area. We see customers looking for more performance. But >>even, >>you know, some of the traditional ah traditional uh, applications like ASAP Hana and epic and meditate expanse. They also have patterns which can benefit greatly with some of that wants wants that we have been making and gets a technical issue. No, The size of the working said with it all fits and car and on sst was spitting on magnetic drives. But something like we've been doing is moving the overheads. If you do have a miss and you go to slow a media, you still get good performance. And that's really how we're getting good to the new. >>Well, yeah, maybe without getting, you know, we don't need to go drill down into the core of the intel chip everything. But you know, Nutanix doesn't just take off the shelf stuff and, you know, put a box together. It's software, and there's work that happens with your partners in the ecosystem. Give us a little flavor as toe. You know where you're making the investments and where some of those partnerships and integrations or a key? >>Yeah, So on the platform side, Ah, a lot of the investments happen in validation of the platforms, making sure that we're ahead of the curve in adopting technologies but also feeding back from our side things we would like to see in the platform. Right? So how do you adapt things like R d m A. To handle not just the traditional work with the happy converge workload? How do you essentially look for things in this new class? of memories that would benefit from data locality for us. So that's one class off partnership that we have the hardware vendors with GHB, with Intel, with the IBM, a whole bunch of people. But >>then >>we also have partnerships up the stock these days with companies like service. Now, with we for backup for for our mind product. I think you saw a little bit of that today. It's a whole bunch of things happening across all areas. >>One of the things that it really comes across at this conference is just how strong Nutanix culture is. The company culture, the humble, honest, hungry and another word that's creeping in now is resilient. I'm wondering if you could talk a little bit about your division of the company and describe how the company's resilience, the employees and the company itself has really displayed itself. >>So, you know, as it any company you know, Any time you go through the kind of growth we have, there's the forward momentum that everybody sees. They also a lot of setbacks that people don't really see, and they've been a whole bunch of us off these in our history. They've been areas where literally. The product has has a floor which is so fundamental we call it internally a near death experience. What's really great until again, from an engineering point of yours, how the teams come together at that point instead of these war rooms, even working weekends, Everybody's there. Everybody's on it and nobody talks about. Hey, look, where's my work? Life? Balance of things like that, especially when they're the customer in world. If there's if there's a problem that's causing customers outages, our engineers will give up everything. They'll give up everything and not just at work with their lives to make sure that gets fixed. And that has helped us get Basti setbacks get back in stride. Happens last Now. It used to happen a lot earlier, but spill this real culture resilience from the big *** in the early engineers. >>All right, Rajiv, what's exciting? You going forward? You know you don't have to touch on this one. But you know, when I saw at the end, the site clusters and hibernate feature was something that was like, Oh, yeah. I don't think I've seen that as to how I could make sure I save my data be ableto, you know, Shut things down. Maybe start there. But give us You know what a little bit. Look forward as to where the team's playing. >>Now, that's kind of, >>you know, thinking that detail thing that you have to do. What, you want to launch a new product, right? Okay, look, the whole point of doing doings, I clusters on Amazon. One of the biggest use cases. This cloud bursting cloud busting is not just about increasing your workload size, scaling it up at some point, you want to scale it down? How do you do that for state for work? Stateless. It's easy. All I'm registering Web servers over that sort of my way, they're gone. But our database that I scaled out over there well, that data can't go away. So we had to find ways to essentially solve for those from. So that's how the hibernate feature came around in general, The bigger question that you asked about, You know what I'm most excited about? I >>think this >>whole convergence of private and public cloud with same stack on both sides is a new new tank. It really hasn't existed before. Um, the father applications can now move back and forth seamlessly between public cloud and private cloud without rewriting without re factoring without a big lift and shift is very, very interesting. But by itself, it's not enough. Um, the flip that's missing is what about data movement? What about if you have your data and Amazon and I want to move it on premises? That there really are no good solutions of the Amazon doesn't give you a P eyes on dhe the tools to do that. So I think data movement's gonna be a big thing. And then Billy, a common service's tack on board because it's not just networking, storage in and compute anymore, right? If you're an Amazon, you're probably using all kinds off. Networking service is security groups. Ah, Route 53. How do you take those kind of service is and also make them available on premises. >>So, Rajiv, is there anything you've learned as a team when you look at AWS outposts or Oracle clouded customer, we've had a few years of talking about, but not a lot of deployments yet, so, you know, not saying you're late to the market, but you know what would have been able to sit back and learn from what has been done so far. >>So the >>reason we >>a little bit late to the market is that we think of solving a problem which the other windows are not, Which is kind of what I alluded to before that is that how do you support both the legacy applications on the cloud Net Cloud applications? How do you provide for migration both ways? Applications of a born in the cloud and now you want to move them on premises or applications of a born on premises and you want to move them to the Cloud Outpost is great. I think it's a good good product of technologies that AWS are thinks that hybrid is the right strategy, but it's also one problem. It's also the problem off cloud applications running on premises it does not solve for the problem of legacy applications running and cloud right, that is just a cz difficult as ever. That's that's not become any easier without force. Similarly, if you look at what we are very swing with AWS, it's also legacy applications going going to AWS. But in doing so, they don't have access to all the different networking services that AWS offers because you're not running and a sex, and you're kind of running a different networking start tonight. So with well, thought long and hard about this problem. And I said, Hey, look, we're not going to take the easy answer over here. You can take Take our stock, which is known to run both legacy and cloud native applications. If probe in that on Internet natively into Amazon so that you can use Amazon service is you can use our service is you can a legacy. Applications can run more than applications without giving up. Anything on that, I think is why signal this longer? But I think it's a more powerful solution for the long term. >>Thank you so much for coming on the Cube. It's always a pleasure having you on my back and see us again. Thanks. I'm Rebecca Knight for stew. Minutemen stay more of the cubes. Live coverage of dot Next Nutanix here in Copenhagen,

>> live from San Francisco celebrating 10 years of high tech coverage. It's the Cube covering Veum World 2019 brought to you by IBM Wear and its ecosystem partners. >> Welcome back to San Francisco. We continue our coverage here. Live on the Cube. 10th year John of covering Veum World This is 29 teens version John for John Wall's Got to have inside the Moscone Center. We're joined now by Varun Chabrol It was the vice president of marketing at Delhi M. C. Good to see you today. >> Thanks for having me. >> How's your week been? So far? >> It's been amazing. How can you don't get excited? All the innovation we're seeing this week >> we'll hear about some big announcements. Do you guys have made? And Moon Young Man Azzedine, who is the vice president of product marketing that for cloud security and works based solutions at Veum wear when you're good to see you. >> Good to see you again. You, By >> the way, you might be the busiest guy here. Yesterday, when you came into the set, you were coming in. Just spoken to 1300 people in a standing room only session You coming out? 500 folks, How many sessions have you done? The seven. So >> you don't count the the one on one with the analyst. And, uh, you know, the customers and partners and press. And tomorrow actually host ah 140 press media analyst on campus in Palo Alto from Asia Pacific because they float all the way from Asia >> plus 140. Yeah, it's a piece of cake. >> Yeah, hose them from 10 to 4. So, I mean, >> you're always smiling >> knowing that this is a pretty wide audience to whom you've been speaking. But just generally, what are you if there's a common thread at all about the kinds of questions that people are coming to you with, or or the concerns or maybe just the things they want to talk about being inspired. But what they're hearing here at the show, >> Okay. Now, according to two aspects of it, one obviously from analysts themselves, you know, they are actually have been very complimentary about the way we've taken our approach. I'm not sure if you could have paid attention. In the last couple of years, we've been talking especially the cloud side, the narrative, to be very much about use cases, solving problems. You know the key? No, we talked about hate my grade modernize. It wasn't about Hey, I've got the next big product here with all these features and capabilities. You do this and that. So we're gonna shifted out narrative. And it was very, you know, the the analyst across the boat. You know, we've been seeing an appreciative of the fact that you actually changing a narrative to be re compelling and we're gonna reflected. And we have some things here like Cloud City, where it's not a standard demo boot. It's a it's ah, Customers walk in and they touch and feel and see which we did it, Adele technology will, too. It's like, What's your business? Probably going through these applications. I'm sitting. I don't know if I should be modernizing them or should be migrating into Amazon. A ridge or so. So you know that narrative the analysts are appreciative off, and that reflects into the customer conversations I've been having in the briefings, like one on one with customers. They're really kind of lost us. D'oh! Hey, I've I'm working in this environment. There's a lot of pressure for me. Thio modernize my applications or go adopt my cloud. First strategy is where do I start? Where do I go? It's like, you know, there's a big pressure, so they just want clarity. I think in the end, everything we're gonna we're doing in our study that comes out obviously the buzzword for this weird world. It stanza, right? And, you know, >> we've won the product announcements was >> actually Brandon can Oh, yeah. Branding announcement, to be honest is yeah, because we're trying to bring together, as you know, in Tansy has landed in Bill Run Manage billed as in you know how our intent to acquire Pivotal Already acquired Big Tommy. How all our different acquisitions with different brand names are coming together to establish our bills portfolio again. The sphere. Everybody knows the sphere Project Pacific P ks. All of those create a good run time, environment and manageability like Adi manage with assets from ve Franta gain morbid Nami and you know it. So this multiple brands that are coming into this package off Iran. So we had a creative tan Xue too, you know, put forward statement together that yes is going to be 78 different brands coming into this, but going forward to stand. >> So so that's a great strategy on De Liam Seaside on Del Technology. Michael Dell was in here and I asked him. I said he could have been number one in everything you could. Let's talk about I'm number one in servers again. You kind of get on HP, little baby. But those air peace parts now. So we've got the cloud game. It's bringing despair it at parts together kind and making it coherent from a positioning standpoint and understandable and deployable. So you guys are going down there. That's your cloud strategy. Take a minute to explain that. >> Yeah, absolutely, John. So So what? What we've been doing. We announced this at Del Technologies will this year. But, you know, in the cloud infrastructure space, we're working very closely with the anywhere too tightly integrate our hardware solutions with their their cloud software. And we think that by combining these two in a tightly integrated joined engineer, jointly engineered solutions coupled with the service, is that you know, both of'em were and l e m c bring the customers we think we have. We're giving customers are very consistent experience both with their own premises, infrastructure with public cloud as well as with the edge cloud. And that's really what we're trying to do. That's what we've been building upon and uniting the announcements this week. You know, just just hopefully show customers that the sky's the limit, whether it's not just your infrastructure management. Also app development. Managing your APS both traditional and and cloud native. It's all here for And >> what's the big takeaway free from your standpoint that you'd like people to know about what's going on? Adele the emcee for the VM. Where relation. What's the big top item? >> Yeah, there's there's there's just so much good Doctor Wait forever drank the town about. If someone rises >> way, only have two hours >> time work. The most important thing that people should should know about it, >> you know, both deli M. C and V. M. R. I think, are very, very customer driven companies that we respond to customer feedback and we try to respond to them very fast. That's been true to our respective lifetimes and what we've done in the so that I think there's two broad areas of collaboration. One is in the cloud space, which is all about, you know, making sure that the the innovation that GM is bringing the market, we're providing that in a toy tightly integrated infrastructure solution. Right. So we announced from a deli in seaside support for Vienna, where p ks being deployed automatically on Vieques trail using VCF return. Our customers can you know, a lot of teams were telling us we have our developers and turning developers banging slash knocking on the door, saying we need to build a cloud. Native applications. You need to give us an environment that we can use. And you know, if if all righty, if these IittIe teams don't turn around and give them something relatively quickly Well, guess what? The developers will go somewhere else, right? Yeah, exactly. So And if you look at the kubernetes environment today, if you really look look at what the work that's required to set up kubernetes and ready infrastructure. So a lot of scripting a lot of manual, you know, work command line interface is testing stuff. And what what? V m r p k s does. And you know what times you will do as well is really makes it easy when we've taken that with the magic of the American Foundation sitting on top of the exhale to make it super easy for our customers to be able to deploy kubernetes ready infrastructure and then have it be ready for scale, right? And then the important thing here also is this is the same infrastructure of the expelling bcf that our customers are using for traditional applications as well, right? Trying to reduce that complexity. Give them the one platform. So this cloud, you know, we had we were doing the same integration on just with R A C I platform, but also with our best to breach storage or we're not working with the C f. And then we're also making investments on data protection like it's so important to be able to manage your data in this multi cloud world. We have applications sitting everywhere, data. We all know that it is a crown jewel. So >> it's really a king validating from the Vienna a point of view. How that works right is is about applications is about the infrastructure, and it's about the operation and it really kind of together as we talk about Han Xue p. K s is giving our customers that Chuy's off. You pick Cuban eighties, you know, environments, application choice. >> Um, >> it took us. Actually, we didn't We didn't arrive it in that order. Wait. Did it. In the outer off Infrastructure Plot Foundation is a critical piece of the joint engineering. But being aware and the Della Bella Technologies is really from aviary perspective. It took Locke Foundation, and that's the stack that runs in every public cloud. So, you know AWS as your G C P 4000 plus, you know, cloud provider partners. But Flat Foundation is a platform that was validated on. They'll take hardware and you know, that's the package. But now, as you see, we're lighting that it's same infrastructure up for traditional and culminated applications. >> I think the app sides important to point out, because if you could ve m wears heritage, you look at Dale's heritage. You had abs that ran on PCs absent, ran on servers, client server. And if you look at the fertilization that wasn't under the covers, apt an innovation that didn't require code changes. So that's the DNA that you guys have. Now, when you think about like cloud to point out which we've been riffing on that concept that's basically enterprise cloud mean donut. Hybrid cloud applications are gonna drive. The value on our premises is that they're going to be customer requirements that traditionally wouldn't have fit in the product. Marketing, management, featureless customs. Gonna define what they want. They'll build it, and then they'll dictate to the infrastructure to make it run. What? We can't do that yet. It'll be, Yes, we cannot be enabled to be dynamics. This is a a new cloud. 2.0, feature. This changes the complete game on suppliers >> completely agree. You know to your point, because, you know, you bring it thio back toward civilization. We've been going higher up the stack on So Day zero virtualization infrastructure will virtual eyes. So the line off abstraction has just been climbing from hardware retort realization next to like, you know, Pat platform of the service, and you kind of were working up our way down infrastructure. Now that base infrastructure platform looks like plants. Right? >> And there were times out a little bit over here. On the upside, you meet in the middle of >> it in the middle >> that is Hello, >> absolutely so ap and at middle wears shrinking down this way. Infrastructures. You know that the cloud incriminating stride in the middle to say, Well, that's a bit of, you know, infrastructure is a Kodak and pull. He's a bit of a AP AP eyes I can can I draw from And that's kind of nice future middleware. But our dad, I >> mean, I think applications air in charge, right? I mean, that's not sure That's the dynamic. That's the way it should be. But it never was that way before is basically the infrastructure was your gating factor. The network exact cloud two points Network security data. Yes, Dev Ops. A true Dev Ops Devane, Ops, Infrastructures Code. >> The only point I wanted to add is the reason the emphasis on abscess change acts in the past. Used to be a business support system after today is business. >> Yeah, I mean, it's >> really or you're you're gonna live or die based on the digital services you provide your customers. The other thing I was going to say about cloud 2.0, is that it's also becoming increasingly clear when we Dr customers that, um, customers are realizing Cloud is not a place right. There was this kind of cloud. One point it was okay. Big honking data centers, hyper skaters will be found now is that customers have gone through that process of and there's a lot more maturity in terms of understanding. What is good, better running on premises. What is what's better running in public Cloud? There's a place for both of them and that, um, and the cloud is actually the automation, the service delivery. It's Maurin operation and a way of being almost than a place. >> And what is it? Well, what does it do for you all? Then, in terms of challenge, especially at your teams, because you talk about all this customization, you're allowing the application to almost drive. You know, you're changing places in terms of who's the power of the relationship? Yes. Oh, me, yeah, How what? What does that do for you? Oh, in terms of how you approach that, how you change of mindset and how you change what you deliver? >> I think John, it's the way I think about it is that both daily emcee in Vienna, or any technology provider that's worth their salt is in the business of building platforms. Right? And platforms are essentially extensible. They're really they really provide a foundation that other people can innovate on top of it. And that's how I think you handled the customers issue. If one thing I think we can all agree on is that I t has always taught us there's no one size fits. All right? Right. So I think providing choice along every single dimension is super important for our >> customers. Yeah, I think that platform thing is a huge point. And I was gonna ask that question before John got jumped in because one of the things that you just brought up was platform is you guys have to build an enabling platform. One as suppliers. Okay, The successful cloud to point out cos are ones that are innovating in weird areas. Monitoring, for instance, they who will have thought that monitoring now observe ability would be such a massive, lucrative sector four. I pose M and A Why? Because it's data. It's instrumentation. This is operating system kind of thinking here is like network. So thinking like a platform on the supplier size one, the customers got to start thinking like a platform because their stakeholders air their internal developers or a P I shipping to suppliers. This is new for enterprises. This is news requires full hybrid capability. This requires date at the center of the value proposition. >> That's again the biggest value is business and I tr coming together on the area of applications and data. Yeah, that's starting up giving because the successful businesses are the ones who leveraged. Those guys have failed in the future, or the ones who don't pay attention to how critical applications are to the business logic and how critical data is to be able to mine and get the behavioral analytics to get ahead. And >> now the challenge in all this. But I'm learning and covering some of the public sector activity from the C I. A contract Jedi with Amazon to we had Raytheon Her here earlier is another customer example with another client is that procurement? And how they do business is not just a technical thing. There's like all this old legacy, things like, How do you procure technology, who you hire her and we hire developers? We build our own stack, so there's a lot of things going on. >> Yes, and you know, it's really interesting on the even on the procurement front, how our customers experience with Cloud has changed expectations, right, And that's really what we're doing with the McLaren DMC is what customers told us is, Hey, I love the agility of the cloud portal based access. Easy procurement. I love just being able to click a button and not have to navigate all this complexity. I need that for my own premises infrastructure. Imagine FRA structure. And that's, you know, in an example, while all of these dynamics are really all converging, >> well, if you can create abstraction, layer on a level of complexity and make things easy, simple and affordable, that's good business. Model >> one of our customers without taking the name right. The massive retailer you know they're spinning up, um, the retail outlets like crazy. They measure success in This was one truck roll, so they wanna have the entire infrastructure come into stand up one of the retail outlets in one truck roll. When everything comes in one button push that everything gets in a provision and up together. >> So that means I gotta have full software instrumentation automation Got intelligence. This is kind of where cloud 2.0, will lead us all >> likely. And that's expectation now that they go so fast and deploying this one Truck roll Hardware's there. Switch it on from the cloud it stood up and they're in operation 24 hours. >> Well, guys, we're going to get you on our power panels in our Palace of studio on this topic cloudy. But it's gonna be very aggressive and controversial topic because it's going to challenge the status quo. And that's really what this we're talking about >> that's in our DNA. >> And the good news is that that's more time with John. >> So as we before, we say so long, we've talked about clients. We talked about the folks you bet here. We talked about the presentation on this thing and what they're all getting out of it. What are you getting out of this? I mean, what are your takeaways? As you had back to your respective work orders, you get first. Okay? >> I think for me the biggest takeaway is just how incredibly vibrant via more user communities. I mean, it is unlike anything else I've seen before and now with the things like Project Pacific. I just feel like it's It's an opportunity for this community to be able to take the skills they have right now and actually go into this brave new world of containers with so much help forces having to do this all by yourself. Which means it's gonna be, you know, if you think about how largest community is, think about how much innovation this will spore in the container space and because of that in the application space and then because of that in business is I mean, this is a It just feels like a tipping point for me >> to me. Sure, I got high fives from every tech geek, you know, when we came out, you know, I also on our technical advisory boats for the company that these are the hot core geeks who were followed and you know us to the, you know, these were the fans and they were like, you know, they always kind of like if you walk out of them and you talk to them and they, uh how did it work? Because they my bar, you have a very high bar. They cut through all your marketing messaging. They go right to the hay. Is there meet in this And the high fives? I got the hajj. I got out. This is like, guys, you're nailing it. That's enough to tell me that a This is, like, 10 years ago. Yeah, that body. It's like you're so busy. I'm still smiling because the energy is I >> can't give you a hug. Give me a high five. Right. Good work, gentlemen. Thanks for the time. Always, he's still smiling to >> get you to a step. >> Good deal. Thanks for being with us. Thank you. Live on the Cube. You're watching our coverage in world 2019. Where? San Francisco. Back with more. Right after this.