>>mhm Yes. >>Welcome back to the Cube coverage of Red Hat summit 21 2021. I'm john for host of the Cubans virtual this year as we start preparing to come out of Covid a lot of great conversations here happening around technology. This is the emerging technology with Red hat segment. We've got three great guests steve watt manager, distinguished engineer at Red Hat hurl saying senior software engineer Red Hat and luke Hines, who's the senior software engineer as well. We got the engineering team steve, you're the the team leader, emerging tech within red hat. Always something to talk about. You guys have great tech chops that's well known in the industry and I'll see now part of IBM you've got a deep bench um what's your, how do you view emerging tech um how do you apply it? How do you prioritize, give us a quick overview of the emerging tech scene at Redhead? >>Yeah, sure. It's quite a conflated term. The way we define emerging technologies is that it's a technology that's typically 18 months plus out from commercialization and this can sometimes go six months either way. Another thing about it is it's typically not something on any of our product roadmaps within the portfolio. So in some sense, it's often a bit of a surprise that we have to react to. >>So no real agenda. And I mean you have some business unit kind of probably uh but you have to have first principles within red hat, but for this you're looking at kind of the moon shot, so to speak, the big game changing shifts. Quantum, you know, you got now supply chain from everything from new economics, new technology because that kind of getting it right. >>Yeah, I think we we definitely use a couple of different techniques to prioritize and filter what we're doing. And the first is something will pop up and it will be like, is it in our addressable market? So our addressable market is that we're a platform software company that builds enterprise software and so, you know, it's got to be sort of fit into that is a great example if somebody came up came to us with an idea for like a drone command center, which is a military application, it is an emerging technology, but it's something that we would pass on. >>Yeah, I mean I didn't make sense, but he also, what's interesting is that you guys have an open source D N A. So it's you have also a huge commercial impact and again, open sources of one of the 4th, 5th generation of awesomeness. So, you know, the good news is open source is well proven. But as you start getting into this more disruption, you've got the confluence of, you know, core cloud, cloud Native, industrial and IOT edge and data. All this is interesting, right. This is where the action is. How do you guys bring that open source community participation? You got more stakeholders emerging there before the break down, how that you guys manage all that complexity? >>Yeah, sure. So I think that the way I would start is that, you know, we like to act on good ideas, but I don't think good ideas come from any one place. And so we typically organize our teams around sort of horizontal technology sectors. So you've got, you know, luke who's heading up security, but I have an edge team, cloud networking team, a cloud storage team. Cloud application platforms team. So we've got these sort of different areas that we sort of attack work and opportunities, but you know, the good ideas can come from a variety of different places. So we try and leverage co creation with our customers and our partners. So as a good example of something we had to react to a few years ago, it was K Native right? So the sort of a new way of doing service um and eventing on top of kubernetes that was originated from google. Whereas if you look at Quantum right, ibms, the actual driver on quantum science and uh that originated from IBM were parole. We'll talk about exactly how we chose to respond to that. Some things are originated organically within the team. So uh luke talking about six law is a great example of that, but we do have a we sort of use the addressable market as a way to sort of focus what we're doing and then we try and land it within our different emerging technologies teams to go tackle it. Now. You asked about open source communities, which are quite interesting. Um so typically when you look at an open source project, it's it's there to tackle a particular problem or opportunity. Sometimes what you actually need commercial vendors to do is when there's a problem or opportunity that's not tackled by anyone open source project, we have to put them together to create a solution to go tackle that thing. That's also what we do. And so we sort of create this bridge between red hat and our customers and multiple different open source projects. And this is something we have to do because sometimes just that one open source project doesn't really care that much about that particular problem. They're motivated elsewhere. And so we sort of create that bridge. >>We got two great uh cohorts here and colleagues parole on the on the Quantum side and you got luke on the security side. Pro I'll start with you. Quantum is also a huge mentioned IBM great leadership there. Um Quantum on open shift. I mean come on. Just that's not coming together for me in my mind, it's not the first thing I think of. But it really that sounds compelling. Take us through, you know, um how this changes the computing landscape because heterogeneous systems is what we want and that's the world we live in. But now with distributed systems and all kinds of new computing modules out there, how does this makes sense? Take us through this? >>Um yeah john's but before I think I want to explain something which is called Quantum supremacy because it plays very important role in the road map that's been working on. So uh content computers, they are evolving and they have been around. But right now you see that they are going to be the next thing. And we define quantum supremacy as let's say you have any program that you run or any problems that you solve on a classical computer. Quantum computer would be giving you the results faster. So that is uh, that is how we define content supremacy when the same workload are doing better on content computer than they do in a classical computer. So the whole the whole drive is all the applications are all the companies, they're trying to find avenues where Quantum supremacy are going to change how they solve problems or how they run their applications. And even though quantum computers they are there. But uh, it is not as easily accessible for everyone to consume because it's it's a very new area that's being formed. So what, what we were thinking, how we can provide a mechanism that you can you don't connect this deal was you have a classical world, you have a country world and that's where a lot of thought process been. And we said okay, so with open shift we have the best of the classical components. You can take open shift, you can develop, deploy around your application in a country raised platform. What about you provide a mechanism that the world clothes that are running on open shift. They are also consuming quantum resources or they are able to run the competition and content computers take the results and integrate them in their normal classical work clothes. So that is the whole uh that was the whole inception that we have and that's what brought us here. So we took an operator based approach and what we are trying to do is establish the best practices that you can have these heterogeneous applications that can have classical components. Talking to our interacting the results are exchanging data with the quantum components. >>So I gotta ask with the rise of containers now, kubernetes at the center of the cloud native value proposition, what work clothes do you see benefiting from the quantum systems the most? Is there uh you guys have any visibility on some of those workloads? >>Uh So again, it's it's a very new, it's very it's really very early in the time and uh we talk with our customers and every customers, they are trying to identify themselves first where uh these contacts supremacy will be playing the role. What we are trying to do is when they reach their we should have a solution that they that they could uh use the existing in front that they have on open shift and use it to consume the content computers that may or may not be uh, inside their own uh, cloud. >>Well I want to come back and ask you some of the impact on the landscape. I want to get the look real quick because you know, I think security quantum break security, potentially some people have been saying, but you guys are also looking at a bunch of projects around supply chain, which is a huge issue when it comes to the landscape, whether its components on a machine in space to actually handling, you know, data on a corporate database. You guys have sig store. What's this about? >>Sure. Yes. So sick store a good way to frame six store is to think of let's encrypt and what let's encrypt did for website encryption is what we plan to do for software signing and transparency. So six Door itself is an umbrella organization that contains various different open source projects that are developed by the Six door community. Now, six door will be brought forth as a public good nonprofit service. So again, we're very much basing this on the successful model of let's Encrypt Six door will will enable developers to sign software artifacts, building materials, containers, binaries, all of these different artifacts that are part of the software supply chain. These can be signed with six door and then these signing events are recorded into a technology that we call a transparency log, which means that anybody can monitor signing events and a transparency log has this nature of being read only and immutable. It's very similar to a Blockchain allows you to have cryptographic proof auditing of our software supply chain and we've made six stores so that it's easy to adopt because traditional cryptographic signing tools are a challenge for a lot of developers to implement in their open source projects. They have to think about how to store the private keys. Do they need specialist hardware? If they were to lose a key then cleaning up afterwards the blast radius. So the key compromise can be incredibly difficult. So six doors role and purpose essentially is to make signing easy easy to adopt my projects. And then they have the protections around there being a public transparency law that could be monitored. >>See this is all about open. Being more open. Makes it more secure. Is the >>thief? Very much yes. Yes. It's that security principle of the more eyes on the code the better. >>So let me just back up, is this an open, you said it's gonna be a nonprofit? >>That's correct. Yes. Yes. So >>all of the code is developed by the community. It's all open source. anybody can look at this code. And then we plan alongside the Linux Foundation to launch a public good service. So this will make it available for anybody to use if your nonprofit free to use service. >>So luke maybe steve if you can way into on this. I mean, this goes back. If you look back at some of the early cloud days, people were really trashing cloud as there's no security. And cloud turns out it's a more security now with cloud uh, given the complexity and scale of it, does that apply the same here? Because I feel this is a similar kind of concept where it's open, but yet the more open it is, the more secure it is. And then and then might have to be a better fit for saying I. T. Security solution because right now everyone is scrambling on the I. T. Side. Um whether it's zero Trust or Endpoint Protection, everyone's kind of trying everything in sight. This is kind of changing the paradigm a little bit on software security. Could you comment on how you see this playing out in traditional enterprises? Because if this plays out like the cloud, open winds, >>so luke, why don't you take that? And then I'll follow up with another lens on it which is the operate first piece. >>Sure. Yes. So I think in a lot of ways this has to be open this technology because this way we have we have transparency. The code can be audited openly. Okay. Our operational procedures can be audit openly and the community can help to develop not only are code but our operational mechanisms so we look to use technology such as cuba netease, open ship operators and so forth. Uh Six store itself runs completely in a cloud. It is it is cloud native. Okay, so it's very much in the paradigm of cloud and yeah, essentially security, always it operates better when it's open, you know, I found that from looking at all aspects of security over the years that I've worked in this realm. >>Okay, so just just to add to that some some other context around Six Law, that's interesting, which is, you know, software secure supply chain, Sixth floor is a solution to help build more secure software secure supply chains, more secure software supply chain. And um so um there's there's a growing community around that and there's an ecosystem of sort of cloud native kubernetes centric approaches for building more secure software. I think we all caught the solar winds attack. It's sort of enterprise software industry is responding sort of as a whole to go and close out as many of those gaps as possible, reduce the attack surface. So that's one aspect about why 6th was so interesting. Another thing is how we're going about it. So we talked about um you mentioned some of the things that people like about open source, which is one is transparency, so sunlight is the best disinfectant, right? Everybody can see the code, we can kind of make it more secure. Um and then the other is agency where basically if you're waiting on a vendor to go do something, um if it's proprietary software, you you really don't have much agency to get that vendor to go do that thing. Where is the open source? If you don't, if you're tired of waiting around, you can just submit the patch. So, um what we've seen with package software is with open source, we've had all this transparency and agency, but we've lost it with software as a service, right? Where vendors or cloud service providers are taking package software and then they're making it available as a service but that operationalize ng that software that is proprietary and it doesn't get contributed back. And so what Lukes building here as long along with our partners down, Lawrence from google, very active contributor in it. Um, the, is the operational piece to actually run sixth or as a public service is part of the open source project so people can then go and take sixth or maybe run it as a smaller internal service. Maybe they discover a bug, they can fix that bug contributed back to the operational izing piece as well as the traditional package software to basically make it a much more robust and open service. So you bring that transparency and the agency back to the SAS model as well. >>Look if you don't mind before, before uh and this segment proportion of it. The importance of immune ability is huge in the world of data. Can you share more on that? Because you're seeing that as a key part of the Blockchain for instance, having this ability to have immune ability. Because you know, people worry about, you know, how things progress in this distributed world. You know, whether from a hacking standpoint or tracking changes, Mutability becomes super important and how it's going to be preserved in this uh new six doorway. >>Oh yeah, so um mutability essentially means cannot be changed. So the structure of something is set. If it is anyway tampered or changed, then it breaks the cryptographic structure that we have of our public transparency service. So this way anybody can effectively recreate the cryptographic structure that we have of this public transparency service. So this mutability provides trust that there is non repudiation of the data that you're getting. This data is data that you can trust because it's built upon a cryptographic foundation. So it has very much similar parallels to Blockchain. You can trust Blockchain because of the immutable nature of it. And there is some consensus as well. Anybody can effectively download the Blockchain and run it themselves and compute that the integrity of that system can be trusted because of this immutable nature. So that's why we made this an inherent part of Six door is so that anybody can publicly audit these events and data sets to establish that there tamper free. >>That is a huge point. I think one of the things beyond just the security aspect of being hacked and protecting assets um trust is a huge part of our society now, not just on data but everything, anything that's reputable, whether it's videos like this being deep faked or you know, or news or any information, all this ties to security again, fundamentally and amazing concepts. Um I really want to keep an eye on this great work. Um Pearl, I gotta get back to you on Quantum because again, you can't, I mean people love Quantum. It's just it feels like so sci fi and it's like almost right here, right, so close and it's happening. Um And then people get always, what does that mean for security? We go back to look and ask them well quantum, you know, crypto But before we get started I wanted, I'm curious about how that's gonna play out from the project because is it going to be more part of like a C. N. C. F. How do you bring the open source vibe to Quantum? >>Uh so that's a very good question because that was a plan, the whole work that we are going to do related to operators to enable Quantum is managed by the open source community and that project lies in the casket. So casket has their own open source community and all the modification by the way, I should first tell you what excuse did so cute skin is the dedicate that you use to develop circuits that are run on IBM or Honeywell back in. So there are certain Quantum computers back and that support uh, circuits that are created using uh Houston S ticket, which is an open source as well. So there is already a community around this which is the casket. Open source community and we have pushed the code and all the maintenance is taken care of by that community. Do answer your question about if we are going to integrate it with C and C. F. That is not in the picture right now. We are, it has a place in its own community and it is also very niche to people who are working on the Quantum. So right now you have like uh the contributors who who are from IBM as well as other uh communities that are specific specifically working on content. So right now I don't think so, we have the map to integrated the C. N. C. F. But open source is the way to go and we are on that tragic Torri >>you know, we joke here the cube that a cubit is coming around the corner can can help but we've that in you know different with a C. But um look, I want to ask you one of the things that while you're here your security guru. I wanted to ask you about Quantum because a lot of people are scared that Quantum is gonna crack all the keys on on encryption with his power and more hacking. You're just comment on that. What's your what's your reaction to >>that? Yes that's an incredibly good question. This will occur. Okay. And I think it's really about preparation more than anything now. One of the things that we there's a principle that we have within the security world when it comes to coding and designing of software and this aspect of future Cryptography being broken. As we've seen with the likes of MD five and Sha one and so forth. So we call this algorithm agility. So this means that when you write your code and you design your systems you make them conducive to being able to easily swap and pivot the algorithms that use. So the encryption algorithms that you have within your code, you do not become too fixed to those. So that if as computing gets more powerful and the current sets of algorithms are shown to have inherent security weaknesses, you can easily migrate and pivot to a stronger algorithms. So that's imperative. Lee is that when you build code, you practice this principle of algorithm agility so that when shot 256 or shot 5 12 becomes the shar one. You can swap out your systems. You can change the code in a very least disruptive way to allow you to address that floor within your within your code in your software projects. >>You know, luke. This is mind bender right there. Because you start thinking about what this means is when you think about algorithmic agility, you start thinking okay software countermeasures automation. You start thinking about these kinds of new trends where you need to have that kind of signature capability. You mentioned with this this project you're mentioning. So the ability to actually who signs off on these, this comes back down to the paradigm that you guys are talking about here. >>Yes, very much so. There's another analogy from the security world, they call it turtles all the way down, which is effectively you always have to get to the point that a human or a computer establishes that first point of trust to sign something off. And so so it is it's a it's a world that is ever increasing in complexity. So the best that you can do is to be prepared to be as open as you can to make that pivot as and when you need to. >>Pretty impressive, great insight steve. We can talk for hours on this panel, emerging tech with red hat. Just give us a quick summary of what's going on. Obviously you've got a serious brain trust going on over there. Real world impact. You talk about the future of trust, future of software, future of computing, all kind of going on real time right now. This is not so much R and D as it is the front range of tech. Give us a quick overview of >>Yeah, sure, yeah, sure. The first thing I would tell everyone is go check out next that red hat dot com, that's got all of our different projects, who to contact if you're interested in learning more about different areas that we're working on. And it also lists out the different areas that we're working on, but just as an overview. So we're working on software defined storage, cloud storage. Sage. Well, the creator of Cf is the person that leads that group. We've got a team focused on edge computing. They're doing some really cool projects around um very lightweight operating systems that and kubernetes, you know, open shift based deployments that can run on, you know, devices that you screw into the sheet rock, you know, for that's that's really interesting. Um We have a cloud networking team that's looking at over yin and just intersection of E B P F and networking and kubernetes. Um and then uh you know, we've got an application platforms team that's looking at Quantum, but also sort of how to advance kubernetes itself. So that's that's the team where you got the persistent volume framework from in kubernetes and that added block storage and object storage to kubernetes. So there's a lot of really exciting things going on. Our charter is to inform red hats long term technology strategy. We work the way my personal philosophy about how we do that is that Red hat has product engineering focuses on their product roadmap, which is by nature, you know, the 6 to 9 months. And then the longer term strategy is set by both of us. And it's just that they're not focused on it. We're focused on it and we spend a lot of time doing disambiguate nation of the future and that's kind of what we do. We love doing it. I get to work with all these really super smart people. It's a fun job. >>Well, great insights is super exciting, emerging tack within red hat. I'll see the industry. You guys are agile, your open source and now more than ever open sources, uh, product Ization of open source is happening at such an accelerated rate steve. Thanks for coming on parole. Thanks for coming on luke. Great insight all around. Thanks for sharing. Uh, the content here. Thank you. >>Our pleasure. >>Thank you. >>Okay. We were more, more redhead coverage after this. This video. Obviously, emerging tech is huge. Watch some of the game changing action here at Redhead Summit. I'm john ferrier. Thanks for watching. Yeah.

>> from our studios in the heart of Silicon Valley. HOLLOWAY ALTO, California It is a cube conversation. >> Welcome to this Special Cube conversation here in Palo Alto, California at the Cube Studios at the Cube headquarters. I'm John for the host, like you were a Dustin Kirkland product manager and Google friend of the Cuban. The community with Cooper Netease been on the Cube Cube alumni. Dustin. Welcome to the Cube conversation. >> Thanks. John's a beautiful studio. I've never been in the studio and on the show floor a few times, but this is This is fun. >> Great to have you on a great opportunity to chat about Cooper Netease yet of what you do out some product man's working Google. But really more importantly on this conversation is about the fifth anniversary, the birthday of Cuba Netease. Today we're celebrating the fifth birthday of Cooper Netease. Still, it's still a >> toddler, absolutely still growing. You think about how you know Lennox has been around for a long time. Open stack has been around these other big projects that have been around for, you know, going on decades and Lenox this case and Cooper nineties. It's going so fast, but It's only five years old, you know. >> You know, I remember Adam Open Stack event in Seattle many, many years ago. That was six years ago. Pubes on his 10th year. So many of these look backs moments. This is one of them. I was having a beer with Lou Tucker. J J Kiss Matic was like one of the first comes at the time didn't make it, But we were talking about open stagger like this Cooper Netease thing. This is really hot. This paper, this initiative this could really be the abstraction layer to kind of bring all this cloud Native wasn't part of the time, but it was like more of an open stack. Try and move up to stack. And it turned out it ended up happening. Cooper Netease then went on to change the landscape of what containers did. Dr. Got a lot of credit for pioneering that got the big VC funding became a unicorn, and then containers kind of went into a different direction because of Cooper duties. >> Very much so. I mean, the modernization of software infrastructure has been coming for a long time, and Cooper nutty sort of brings it all brings it all together at this point, but putting software into a container. We've been doing that different forest for for a lot of time, uh, for a long time, but But once you have a lot of containers, what do you do with that? Right? And that was the problem that Cooper Nettie solved so eloquently and has, you know, now for a couple of years, and it just keeps getting better. >> You know, you mentioned modernization. Let's talk about that because I think the modernization the theme is now pretty much prevalent in every vertical. I'll be in D. C. Next week for the Amazon Webster was public sector Summit, where modernization of governments and nations are being discussed. Education, modernization of it. We've seen it here. The media business that were participating in is about not where you store the code. It's how you code. How you build is a mindset shift. This has been the rial revelation around the Dev Ops Movement Infrastructures Code, now called Cloud Native. Share your thoughts on this modernization mindset because it really is how you build. >> Yeah, I think the cross pollination actually across industries and we even we see that even just in the word containers, right and all the imagery around shipping and shipping containers, we've applied these age old concepts that have been I don't have perfected but certainly optimized over decades of, actually centuries or millennia of moving things across water in containers. Right. But we apply that to software and boom. We have the step function difference in the way that we we manage and we orchestrated and administer code. That's one example of that cross pollination, and now you're talking about, like optimizing optimized governments or economies but being able to maybe then apply other concepts that we've come a long way in computer science do de bop set a good example? You know, applying Dev ops principles to non computer feels. Just think about that for a second. >> It's mind blowing. And if you think about also the step function you mentioned because I think this actually changed a lot of the entrepreneurial landscape as well and also has shaped open source and, you know, big news this this quarter is map are going to shut down due one of the biggest do players. Cloudera merge with Horton Works fired their CEO, the founder Michael. So has retired, Some say forced out. I don't think so. I think it's more of his time. I'm Rodel still there. Open source is a business model, you know. Can we be the red hat for her? Duped the red? Not really kind of the viable, but it's evolving. So open source has been impacted by this step function. There's a business impact. Talk about the dynamics with step function both on the business side and on how software's built specifically open source. >> You know, you and I have been around open source for a long, long time. I think it started when I was in college in the late nineties on then through my career at IBM. And it's It's interesting how on the fringe open source was for so long and such so so much of my BM career. And then early time spent onside it at Red Hat. It was it was something that was it was different, was weird. It was. It was very much fringe where the right uh, but now it's in mainstream and it's everywhere, and it's so mainstream that it's almost the defacto standard to just start with open source. But you know, there's some other news that's been happening lately that she didn't bring up. But it's a really touchy aspect of open source right now on that's on some of the licenses and how those licenses get applied by software, especially databases. When offered as a service in the cloud. That's one of the big problems. I think that that's that we're we're working within the open >> source, summarize the news and what it means. What's what's happening? What's the news and what's the really business? Our technical impact to the licensing? What's the issue? What's the core issue? >> Yeah, eso without taking judgment any any way, shape or form on this, the the the TL D are on. This is a number of open source database is most recently cockroach D. B. I have adopted a different licensing model that is nonstandard from an open source perspective. Uh, and from one perspective, they're they're adopting these different licensing models because other vendors can take that software and offered as a service, yes, and in some some cases, like Amazon like Sure, you said, uh, and offered as a as a service, uh, and maybe contribute. Maybe pay money to the smaller startup or the open source community behind it. But not necessarily. Uh, and it's in some ways is quite threatening to open source communities and open source companies on other cases, quite empowering. And it's going to be interesting to see how that plays out. The tension between open sourcing software and eventually making money off of it is something that we've we've seen for, you know, at least 25. >> And it continues to go on today, and this is, to me a real fascinating area that I think is going to be super important to keep an eye on because you want to encourage contribution and openness. Att the same time we look at the scale of just the Lenox foundations numbers. It's pretty massive in terms of now, the open source contribution. When you factor in even China and other nations, it's it's on exponential growth, right? So is it just open source? Is the model not necessarily a business? Yeah. So this is the big question. No one knows. >> I think we crossed that. And open source is the model. Um, and this is where me is a product manager. That's worked around open source. I've spent a lot of time thinking about how to create commercial offerings around open source. I spent 10 years at Economical, the first half of which, as an engineer, the second half of which, as a product manager around, uh, about building services, commercial services around 12 And I learned quite a few things that now apply absolutely to communities as well as to a number of open source startups. That that I've advised on DH kind of given them some perspective on maybe some successful and unsuccessful ways to monetize that that opens. >> Okay, so doesn't talk about Let's get back to Coburg. And so I think this is the next level Talk track is as Cooper Netease has established itself and landed in the industry and has adoption. It's now an expansion votes the land adopted expand. We've seen adoption. Now it's an expansion mode. Where does it go from here? Because you look at the tale signs things like service meshes server. Listen, you get some interesting trends that going to support this expansionary stage of uber netease. What is your view about the next expansion everyway what >> comes next? Yeah, I I think I think the next stage is really about democratizing communities for workloads that you know. It's quite obvious where when communities is the right answer at the scale of a Google or a Twitter or Netflix or, you know, some of these massive services that it is obviously and clearly the best answer to orchestrating containers. Now I think the next question is, how does that same thing that works at that massive scale Also worked for me as a developer at a very small scale helped me develop my software. My small team of five or 10 people. Do I need a coup? Burnett. He's If I'm ah five or 10 person startup. Well, I mean, not the original sort of borde vision of communities. It's probably overkill, but actually the tooling has really advanced, and we now >> have >> communities that makes sense on very small scales. You've got things like a three s from from Rancher. You've got micro Kates from from my colleagues at economical other ways of making shrinking communities down to something that fits, perhaps on devices perhaps at the edge, beyond just the traditional data center and into remote locations that need to deploy manage applications >> on the Cooper Netease clustering the some of the tech side. You know, we've seen some great tech trends as mentioned in Claudia Horton. Works and map Our Let's Take Claudia and Horton work. Remember back in the old days when it was booming? Oh, they were so proud to talk about their clusters. I stood up all these clusters and then I would ask them, Well, what do you doing with it? Well, we're storing data. I think so. That became kind of this use case where standing up the cluster was the use case and they're like, OK, now let's put some data in it. It's a question for you is Coburn. Eddie's a little bit different. I'm not seeing they were seeing real use cases. What are people standing up? Cuban is clusters for what specific Besides the same Besides saying I've done it. Yeah, What's the what's the main use case that you're seeing this that has real value? >> Yeah, actually, there's you just jog t mind of really funny memory. You know, back in those big data days, I was CEO of a startup. We were encrypting data, and we were helping encrypt healthcare data for health care companies and the number of health care companies that I worked with at that time who said they had a big data problem and they had all of I don't know, 33 terabytes worth of worth of data that they needed to encrypt. It was kind of humorous sometimes like, Is that really a big, big data problem? This fits on a single disc, you know, Uh, but yeah, I mean, it's interesting how >> that the hype of of the tech was preceding. The reality needs needs, says Cooper Nettie. So I have a Cuban Eddie's cluster for blank. Fill in the blank. What are people saying? >> Yeah, uh, it's It's largely about the modernization. So I need to modernize my infrastructure. I'm going to adopt the platform. That's probably not, er, the old er job, a Web WebSphere type platform or something like that. I'm investing in hardware investing in Software Middle, where I'm investing in people, and I want all of those things to line up with where industry is going from a software perspective, and that's where Cooper Nighties is sort of the cornerstone piece of that Lennox Of course, that's That's pretty well established >> canoes delivery in an integration piece of is that the pipeline in was, that was the fit on the low hanging fruit use cases of Cooper Netease just development >> process. Or it's the operations it's the operations of now got software that I need to deploy across multiple versions, perhaps multiple sites. Uh, I need to handle that upgrade ideally without downtime in a way that you said service mash in a way that meshes together makes sense. I've got a roll out new certificates I need to address the security, vulnerability, thes air, all the things that Cooper and I used to such a better job at then, what people were doing previously, which was a whole lot of four loops, shell strips and sshh pushing, uh, pushing tar balls around. Maybe Debs or rpm's around. That is what Cooper not he's actually really solves and does an elegant job of solving as just a starting point. And that's just the beginning and, you know, without getting ve injury here, you know, Anthros is the thing that we had at Google have built around Cooper Netease that brings it to enterprise >> here the other day did a tweet. I called Anthem. I just typing too fast. I got a lot of crap on Twitter for that mission. And those multi cloud has been a big part of where Cubans seems to fit. You mentioned some of the licensing changes. Cloud has been a great resource for a lot of the new Web scale applications from all kinds of companies. Now, with several issues seeing a lot more than capabilities, how do you see the next shift with data State coming in? Because God stateless date and you got state full data. Yeah, this has become a conversation point. >> Yeah, I think Kelsey Hightower has said it pretty eloquently, as he usually does around the sort of the serval ist movement and lets lets developers focus on just their code and literally just their code, perhaps even just their function in just their piece of code, without having to be an expert on all of the turtles all the way, all the way down. That's the big difference about service have having written a couple of those functions. I can I can really invest my time on the couple of 100 lines of code that matter and not choosing a destro choosing a cougar Nati is choosing, you know, all the stack underneath. I simply choose the platform where I'm gonna drop that that function, compile it, uploaded and then riff and rub. On that >> fifth anniversary, Cooper Netease were riffing on Cooper Netease. Dustin Circle here inside the Cube Cube Alumni you were recently at the coop con in overseas in Europe, Barcelona, Barcelona, great city. Keeps been there many times. Do was there covering for us. Couldn't make this trip, Unfortunately, had a couple daughter's graduating, so I didn't make the trip. Sorry, guys. Um, what was the summary? What was the takeaway? Was the big walk away from that event? What synthesized? The main stories were the most important stories being >> told. >> Big news, big observations. >> It was a huge event to start with. It was that fear of Barcelona. Um, didn't take over the whole space. But I've been there a number of times from Mobile World Congress. But, you know, this is this is cube con in the same building that hosts all of mobile world Congress. So I think 8,000 attendees was what we saw. It's quite celebratory. You know, I think we were doing some some pre fifth birthday bash celebrations, Key takeaways, hybrid hybrid, Cloud, multi Cloud. I think that's the world that we've evolved into. You know, there was a lot of tension. I think in the early days about must stay on. Prem must go to the cloud. Everything's there's gonna be a winner and a loser and everything's gonna go one direction or another. I think the chips have fallen, and it's pretty obvious now that the world will exist in a very hybrid, multi cloud state. Ultimately, there's gonna be some stuff on Prem that doesn't move. There's going to be some stuff better hosted in one arm or public clouds. That's the multi cloud aspect, Uh, and there will be stubborn stuff at the edge and remote locations and vehicles on oil rigs at restaurants and stores and >> so forth. What's most exciting from a trans statement? What do you what? What's what's getting you excited from what you see on the landscape out there? >> So the tying all of that to Cooper Netease, Cuban aunties, is the thing that basically normalizes all of that. You write your application put it in a container and expect to communities to be there to scale that toe. Operate that top grade that to migrate that over time. From that perspective, Cooper nineties has really ticked, ticked all the boxes, and you've got a lot of choices now about which companies here, you're going to use it and where >> beyond communities, a lot of variety of projects coop flow, you got service messes out there a lot of difference. Project. What's What's a dark horse? What's something that sets out there that people should be paying attention to? That you see emerging? That's notable. That should be paying attention. To >> think is a combination of two things. One is pretty obvious, and that's a ML is coming like a freight train and is sort of the next layer of excitement. I think after Cooper, Netease becomes boring, which hopefully if we've done our jobs well, that communities layer gets settled and we'll evolve. But the sort of the hockey stick hopefully settles down and it becomes something super stable. Uh, the application of machine learning to create artificial intelligence conclusions, trends from things that is sort of the next big trend on then I would say another one If you really want the dark horse. I think it's around communications. And I think it's around the difference in the way that we communicate with one another across all forms of media voice, video chat, writing, how we interact with people, how we interact with our our tools with our software and in fact, how our software in Iraq's with us in our software acts with with other software that communications industry is, it's ripe for some pretty radical disruption. And you know some of the organizations and they're doing that. It's early early days on those >> changes. Final point you mentioned earlier in our conversation here about how Dev Ops is influencing impacting non tech and computer science. Really? What did you mean by that? >> Uh, well, I think you brought up unexpectedly and that that you were looking at the way Uh, some other industries are changing, and I think that cross pollination is actually quite quite powerful when you take and apply a skill and expertise you have outside of your industry. But it adds something new and interesting, too, to your professional environment. That's where you get these provocative operations. He's really creative, innovative things that you know. No one really saw it coming. >> Dave Ops principles apply to other disciplines. Yeah, agility. That's that's pointing down waterfall based processes. That's >> one phenomenal example. Imagine that for governments, right to remove some of the like the pain that you and I know. I've got to go and renew my license. My birthday's coming up. I gotta go to renew my driver's license. You know much. I'm dreading going to the the DMV Root >> Canal driver's license on the same. Exactly >> how waterfall is that experience. And could we could we beam or Mohr Agile More Dev Autopsy and some of our government across >> the U. S. Government's procurement practices airbase upon 1990 standards they still want Request a manual, a physical manual for every product violent? Who does that? >> I know that there are organizations trying to apply some open source principles to government. But I mean, think about, you know, just democracy and how being a little bit more open and transparent in the way that we are in open source code, the ability to accept patches. I have a side project, a passion for brewing beer and I love applying open source practices to the industry of brewing. And that's an example of where use professional work, Tio. Compliment a hobby. >> All right, we got to bring some cubic private label, some Q beer. >> If you like sour beer, I'm in the sour beer. >> That's okay. We like to get the pus for us. Final question for you. Five years from now, Cooper needs to be 10 years old. What's the world gonna look like when we wake up five years from now with two Cuban aunties? >> Yeah, I think, uh, I don't think we're struggling with the Cooper nutties. Uh, the community's layer. At that point, I think that's settled science, inasmuch as Lennox is pretty settled. Science, Yes, there's a release, and it comes out with incremental features and bug fixes. I think Cuban aunties is settled. Science management of of those containers is pretty well settled. Uh, five years from now, I think we end up with software, some software that that's writing software. And I don't quite mean that in the way That sounds scary, uh, and that we're eliminating developers, but I think we're creating Mohr powerful, more robust software that actually creates that that software and that's all built on top of the really strong, robust systems we have underneath >> automation to take the heavy lifting. But the human creation still keeping one of the >> humans Aaron the look it's were We're many decades away from humans being out of the loop on creative processes. >> Dustin Kirkland, he a product manager of Google Uh, Cooper Netease guru also keep alumni here in the studio talking about the coup. Burnett. He's 50 year anniversary. Of course, the kid was president creation during the beginning of the wave of communities. We love the trend we love Cloud would left home a tec. I'm Sean for here in Palo Alto. Thanks for watching.

>> Live from San Francisco. It's the cube covering IBM thing twenty nineteen brought to you by IBM. >> Welcome back to the Cube here in Mosconi North at IBM. Think twenty nineteen. I'm stupid. And my CLO host for the segment is Day Volante. We have four days, a water wall. Coverage of this big show happened. Welcome back to the program. Jason McGee, who is an IBM fellow, and he's the vice president. CTO of Cloud Platform at IBM. Jason, Great to see a >> guy to have fair. >> All right, So, Jason, we spoke with you at Que Con Way. We're saying it's a slightly different audience. A little bit bigger here. Not as many hoodies and jeans and T shirts a little bit more of a business crowd were still talking about clouds. So let's talk about your kind of your role here at the show. What's gonna keep you busy all week? >> S o? I mean, obviously, cloud is a huge part of what's going on. I think talking a lot about both public and private, about hybrid and some are multi called management capabilities. You know, my role as the leader called Platform. I'm talking a lot about platform as a service and communities and containers in the studio and kind of all the new technologies that people are using to help build the next generation of applications. >> All right, so we've had a few interviews today already talk about some of the multi cloud pieces. We had Sandberg on alien talk about eternity. So first you're gonna help correct the things that he got >> anything. Gang >> and service measures have been a really hot conversation the last year or so SDO envoy and the like t talk to us about where IBM fits into this discussion of service meshes. >> Yeah, so you know, I think >> we've been on this kind of journey as an industry of last year's to build anew at platform on DH service meshes kind of fit the part of the problem, which is, How does everything talk to each other and how to actually control that and get visibility into it? You know, IBM has had a founding role in that project. My team at IBM and Google got together with the guys, a lift to create it. Theo, what I'm most excited about, I think a twenty nineteen is that's that technology is really transitioning into something people are using in production and their applications. It's becoming more of kind of the default stack that people are using Really helping them do security invisibility control over their applications? >> Yeah. What? One thing that I heard just from the community and wonder if you could tell me is, you know, is dio itself. The governance model is still not fully into CNC s. Yeah, I heard a little bit, hasn't he? On some envoy? Of course. Out there in the like. So, you know, where are we? What needs to happen to kind of >> move forward? Yeah, you're right. So we're not there quite yet. We're pushing hard to make that happen. Certainly. From an IBM perspective, we absolutely believe that CNC F is the right home for Osteo as you mentioned some of the pieces like Envoy or they're ready. You know, C N c f has done such a tremendous job over the last eighteen months. Really rallying all the core technologies that make up this new coordinate A platform that we're building on costo is no out there's one. Oh, it's been sure people are using it. You know, that last step needs to happen to get into the community. >> So I have to ask you So things move so fast in this world, you go back to the open stack days, and that was going to change the world. And then Dakar Containers. And then Cooper netease, usto I can't help but thinking, Okay, This isn't the end of the line. What's Jason? What's the underlying trend here that's going on in the coding world? Yeah, sure. I'll put it in, maybe in >> my own lens. Given my history, you nominal WebSphere app server guy. You know that in the first half of my career I built that Andi, >> I think the fundamental >> problem solving is actually exactly the same. It's like, how do you build a platform that's app developers focus on building their APS, and I'll focus on all the plumbing and the infrastructure for running those aps. We did that twenty years ago in Java with APP servers, and we're doing it now with cloud, and we're doing it on top of containers. Things like usto like, while they're important in their own right there really actually Mohr important because they're just part of this bigger puzzle that we're putting together. And I think for the average suffer developer, they shouldn't really have to care about. What part of this deal will part is is Cuban eighties. And which part is K native like all that needs to come together into a single platform that they can use to build their APS and run them security. Right? And and I think it's Seo is just recognizing that next piece. You know, I think we've all agreed on containers and communities. We all talk about it all the time, and it's tio Is that next layer I catalyze securing >> control things. Yeah. So you teed it up nicely because we want out. Developers just be able to worry about the application. So you mentioned K native. The whole server list trend is one where you know the idea, of course, is I shouldn't have to worry about the infrastructure layer it just be taking care of me. We've talked about it for pass for a number of years. There are various ways to do it. So at, uh, Cube Colin and we've been looking for about the last year. Now you know, Where does you No, Crew, Burnett, ease and surveillance. How do they fit together? And K Native looks to be a pieces. Toe bridge. Some of those barrels? Absolutely. Where are we and what? What? What's? What's IBM doing there? >> So I think >> you rightly say that they should fit together like they're all part of this continuum of how developers build APS. And, you know, if you look at server, less applications, you know, there's the servos to mention I'm personally not a big service terminology fan. I think they're Maura about event oriented computing. And how do you have a good model for event oriented systems today? With Cuba Netease, anise Teo, I think we've built the base platform, I think, with a native what we're doing is bringing server lists and also just kind of twelve factor applications into the fold in a more formal way on when we get all those pieces together and we integrate them. I think then developers really unleashed to just build their application, whatever way it makes the most sense for what they're doing. And some things like server lists of Anna Marie. And it's going to be easier. And some problems. Straight containers will be an easier way to do >> it. You know, you say you don't like survivalists you like event better a function. So so explain that to the audience, like Why? Why should we care? And why is that different? How is that different? Yeah, I think, for >> a couple things. First off, the idea of server lists applies much more broadly than just what we think of this kind of function based program. You know, like any system that does a good job of managing and masking the infrastructure below me, you could consider a surveillance system, right? So when you just say server Lis, it's kind of like secondhand for functions. I'd rather we just kind of say, functions because that's actually a different programming model where you kind of trigger off of events and you write a functional piece of code and the system takes care of those details. You could argue that caught foundries, a server list system in the sense that you just as a developer anyway, you just see if push your code and it just runs and its scales and it does whatever you need, right? So part of my mission, you know, part of what I look at a lot is how do we bring all these things together in a way that is easy for the developer to stay focused. It steals a great example. You know, one of things were announcing this week is managed osteo support as part of our community service. What does that really mean? It means the developer can use the capability Viste without worrying about How do I install in Rennes D'oh, which they don't really care about? They just really care about how they get value out of its capability. >> Yeah, that's one of the things that having watched all these crew Benetti system and the like is how many companies really need to understand how to build this and run that because can I just get it delivered to me as a service? And therefore that you know that whole you know what I want out of cloud? I want a simple model to be able to consume, Not necessarily. I want to build the stuff that's important to me and not the rest of you. >> And I think if you look at the industry, there's really, I think, kind of two dominant consumption models that have actually emerged for people really using these things, there's public cloud platforms you're delivering things as a service. And then there's kind of platform software stacks like open shifts like I've been called private, which take all of these pieces and bring them together. And I think for most developers, they'll consume in one of those two ways because they don't really want the task of how to assemble all these pieces together. >> Tio, go back to the service piece like what? One distinction I heard made is okay. If I can really scale it down to zero, if I don't need to make it, then that can be serve a list. But there there's alternatives coming out there like what K native has. If I want to run this in my own environment, it's not turbulence because I do need toe. It might be functions, but I need to manage this environment. The infrastructure is my responsibility, not some >> service provider, right? And I think if you'll get server list to me, I was personally, I always think of it in kind of two scenarios. There's like surveillance as ah program remodel in a technology and surveillance as a business model, right? As a consumption model for payment. I think this programming model parts applicable in lots of cases, including private clouds. And in Custer, the business model parties, I think, frankly, unique to public. I'll thing that says I can just pay for the milliseconds of CPU, Compute that amusing and nothing more. >> That's a good thing for consumers. For >> the consumer, it's actually good thing for cloud providers because it gives us a way Tio reuse our infrastructure and creative ways, Right? But I think first and foremost, we have to get Mohr adoption of it as a programming model that developers used to build their applications and do it combined with other things. Because I think most realistic APs aren't gonna all be cirrhosis or all B Cooper nineties. They're going to be something. >> Yeah, right. It's like everything else. It's it's you know, what percent into the applications? Will this takeover? We had this discussion with virtual ization. We've been having this discussion with cloud and certain list, of course, is is pretty early in that environment. K native did I hear is there's some announcement this week that IBM >> so Soak a native, obviously is a project is kind of much earlier in its maturation and something like Castillo is. But we're making that available as part of our Republican private cards as well, Really? So people can get started with the ideas of K native. They can have an easy way to get that environment stood up, and they can start building those applications on DSO. That's now something that, you know, we're kind of bringing out as we work in the community to actually mature the project itself. >> Excellent. One of the things everybody's, of course, keeping an eye on. I saw Arvin Christian talking about the clouds. Tragedy is how red hat fits into all this. So we know you can't talk about kind of post acquisition. But red hats involved in K native. They're involved in a lot of the >> services and developers you gotta be exciting for. Yeah, >> it is. And obviously, like, Look, we've been partners for many years, you know, in on the open source side of things. We've worked closely with Red Hat for a long time. We actually view the world in very similar ways. You know, like you said, we're working on a native together. We've been working on Open West Feather. We obviously work in Cuban eighties together. So personally, I'm pretty excited about them coming in IBM. Assuming that acquisition goes through, they, you know, they fit into our strategy really well. And I think we'll just kind of enhance what we've all been working to build. >> All right, Jason, what else? What's looking? You talk about the maturity of these solutions, give us, um, guide post for the people watching the industry that we should be looking at as twenty nineteen rolls through >> us. So I think there's a >> couple things that, you know, I think this unified application platform notion that we've been kind of touching on here, I think will really come into its own in twenty nineteen. And and I would really love to see people kind of embraced that idea that we don't need. Three container stacks were not tryingto build these seven things. You know, one of things I'm kind of excited about with a native is by bringing server lists and twelve factor into Cuba Netease. It allows each of those frameworks to be kind of the best they can be at their part of the problem space and not solved unrelated problems. You know, I looked at the kind of server less versus coop camps, you know, the purest. And both think all problems will be solved in their camp. Which means they tried to solve all problems. Like, how do I do state full systems and server, Wes. And how do I bring in storage and solve all these things that maybe containers is better at. So I think this unification that I see happening will allow us to have really high efficiency, twelve factor and surveillance in the context of Koob and will change how people are able to use these platforms. I think twenty nineteen is really about adoption of all of this stuff. You know, we still are really early, frankly, in the kind of container adoption landscape, and I think most people in the broader industry or just kind of getting their feet wet they all agree that they're all trying, but they're just starting, and he knows a lot of interesting work. >> Jason, are there any anything that air holding people back? Anything that you You know what? What do you see is some of the things that might help accelerate some of this adoption? >> Yeah, I think one of the things that's >> holding people back is just the diversity of options that exists in the cognitive space means you guys have all probably rising like the C in C F landscape chart. I've never seen so many icons on something in my life. That's really frightening for the average enterprise. To look at a picture like that and go like which of these things are going to be useful, which are going to exist in a year like how Doe, I bet, make that sort >> of those things. So I think that's actually >> help people back a lot. I think that kind of agreement around communities that happened in the last eighteen months or so was really liberating, for a lot of people have helped them kind of move forward there. I think if we can all agree on a few more pieces around this deal, reckon native like it'll really help kind of unlock people and get them trying actually doing it. And I don't think it's anything more than picking a project and starting. I think a lot of enterprises over analyze everything, and they just need to pick something and go and learn. And they'll >> so pick some narrow use case pick, pick an app, pick >> a use case and go do it right and you'll learn and you'll figure out how it works for you. And then you do the second and the fourth in the tenth. And before you know it, you're on your way. That's what we did at IBM ourselves, and you know, now we're running our whole entire public out on top of communities. >> Jason and any any warnings from that kind of experience that you trade to users? A CZ. They looked forward. >> Yeah, we had a >> lot of learnings from music. One is we could run a heck of a lot more diverse work less than we thought when we started. You know, we're running databases where any data warehouses, running machine learning. We're running Blockchain. We're running every kind of application you didn't think could ever work on containers on containers s so one of the lessons Wass. It's much more flexible than you think. It isthe right. The >> other thing is you >> really have to rethink everything. Like the way you do compliance, the way you do security, the way you monitor the system. Like all of those things I need to change because the underlying kind of container system enables you to solve them in such a powerful way. And so if you go into it just thinking, Oh, I'm just going to change this one part of how I do aps and the rest will change. I think you'll find in a year that you're changing the whole operating model around your environment. >> Well, Jason, rethink everything we're here at IBM. Thing up twenty nineteen. Thinks is always for catching up with Thanks for everything going on for David. Want a, um, stew? Minutemen got three more days of live coverage here for Mosconi North. If you hear, stop by and say hi or reach out to us on the interwebs. Thanks so much for watching the cues.

>> Hello everyone. Welcome to this CUBE conversation. I'm John Furrier host like you here in our Palo Alto studio here in Palo Alto. Here with Dominic Wilde, known as Dom, CEO of SnapRoute, a hot new startup. A great venture. Backers don. Welcome to skip conversation. So love having to start ups. And so talk about Snape route the company because you're doing something interesting that we've been covering your pretty aggressively the convergence between Dev Ops and Networking. We've known you for many, many years. You were a former Hewlett Packard than you woodpecker enterprise running the networking group over there. You know, networking. And you're an operator. Snap rows. Interesting, because, um, great names back behind it. Big venture backers. Lightspeed Norwest, among others. Yes. Take a minute. Explain what? A SnapRoute. >> So SnapRoute was founded to really address one of the big, big problems we see in infrastructure, which is that, you know, essentially the network gets in the way of the deployment the rapid and angel deployment of applications. And so in the modern environment that we're in, you know, the business environment, highly competitive environment of disruption, continuous disruption going on in our industry, every company out there is constantly looking over their shoulder is, you know, making sure that they're moving fast enough there innovating fast enough that they don't want to be disrupted. They don't want to be overrun by, you know, a new upstart. And in order to do that, you know the application is is actually the work product that you really want to deploy, that you you want to roll out, and you want to be able to do that on a continuous basis. You want to be really agile about how you do it. And, quite frankly, when it comes to infrastructure, networking has been fifteen years behind the rest of the infrastructure and enabling that it's, ah, it's a big roadblock. It's obviously, you know, some of the innovations and developments and networking of lag behind other areas on what we snap Brown set out to do was to say, You know, look, if we're if we're going to bring networking forward and we're going to try and solve some of these problems, how do we do that? In a way, architecturally, that will enable networking to become not just a part of Ah, you know a cloud native infrastructure but actually enable those those organizations to drive forward. And so what we did was we took all of our sort of devops principles and Dev ups tools, and we built a network operating system from the ground up using devops principles, devops architectures and devops tools. And so what we're delivering is a cloud native network operating system that is built entirely on containers and is delivered is a micro services architecture on the big...one of the big value propositions that we deliver is what we call see a CD for networking, which is your continuous integration. Continuous deployment is obviously, you know, Big devops principal there. But doing that for networking, allowing a network to be constantly up enabling network Teo adapt to immutable infrastructure principles. You know we're just replacing pieces that need to be replaced. Different pieces of the operating system can be replaced If there's a security vulnerability, for instance, or if there's ah, bugger and you feature needed so you know we can innovate quicker. We can enable the network to be more reliable, allow it to be more agile, more responsive to the needs of the organization on all of this, fundamentally means that your Operation shins model now becomes ah, lot more unified. A lot more simple. You. Now, we now enable the net ox teams to become a sort of more native part of the conversation with devils. Reduce the tension there, eliminate any conflicts and everything. And we do that through this. You know, this innovative offices. >> Classically, the infrastructure is code ethos. >> Yeah, exactly right. I mean, it's you know, a lot of people have been talking about infrastructure is code for a long, long time. But what we really do, I mean, if if you deploy our network operating system you employ onto the bare metal switching, then you really enable Dev ops to hang have, you know, I take control and to drive the network in the way they want using their native tool chains. So, you know, Cuba Netease, for instance, ears. You know that the big growing dev ops orchestration to all of the moment. In fact, we think it's more than of the moment. You know, I've never seen in the industry that sort of, you know, this kind of momentum behind on open source initiative like there is behind Cuba. Netease. And we've taken communities and baked it natively into the operating system. Such that now our network operating system that runs on a physical switch can be a native part off that communities and develops tool >> Dom, I want to get to the marketplace, dynamics. Kind of what's different. Why now? But I think what's interesting about SnapRoute you're the chief of is that it's a venture back with big names? Yeah. Lightspeed, Norwest, among others. It's a signal of a wave that we've been covering people are interested in. How do you make developers deploy faster, more agility at scale, on premises and in clouds. But I want you to before we get there, want to talk about the origin story of company? Yeah. Why does it exist? How did it come to bear you mentioned? Operation is a big part of cloud to cloud is about operating model so much a company. Yes. This is the big trend. That's the big way. But how did it all get started? What's the SnapRoute story? >> Yeah, it's an interesting story. Our founders were actually operators at at Apple back in the day, and they were responsible for building out some of Apple's biggest. You know, data centers for their sort of customer facing services, like, you know, like loud iTunes, all those good things and you know they would. They were tasked with, sort of, you know, sort of modernizing the operational model with with those data centers and, you know, and then they, like many other operators, do you know, had a sense of community and worked with their peers. You know, another big organizations, even you know, other hyper scale organizations and wanted to learn from what they did on DH. What they recognised was that, you know, cos like, you know, Google and Facebook and Microsoft is urine things. They had done some incredible things and some incredible innovations around infrastructure and particularly in networking, that enabled them to Dr Thie infrastructure from A from a Devil ops perspective and make it more native. But those words that if you know, fairly tailored for there, if you know, for their organizations and so what they saw was the opportunity to say, Well, you know, there's there's many other organizations who are delivering, you know, infrastructure is a service or SAS, or you know, who are just very large enterprises who are acting as these new cloud service providers. And they would have a need to, you know, to also have, you know, tools and capabilities, particularly in the network, to enable the network to be more responsive, more to the devil apps like. And so, you know, they they they founded SnapRoute on that principle that, you know, here's the problem that we know we can solve. It's been solved, you know, some degree, but it's an architectural problem, and it's not about taking, You know, all of the, you know, the last twenty five years of networking knowledge and just incrementally doing a sort of, you know, dot upgrade and, you know, trying to sort of say, Hey, we're just add on some AP eyes and things. You really needed to start from the ground up and rethink this entirely from an architectural perspective and design the network operating system as on with Dev ups, tools and principles. So they started the company, you know, been around just very late two thousand fifteen early two thousand sixteen. >> And how much money have you read >> The last around. We are Siri's, eh? We took in twenty five million. >> And who were the venture? >> It was Lightspeed Ventures on DH Norwest. And we also had some strategic investment from Microsoft Ventures and from teams >> from great name blue chips. What was their interest? What was their thesis? Well, and you mentioned the problem. What was the core problem that you're solving that they were attracted to? Why would that why was the thirst with such big name VCs? >> Yeah, I mean, I think it was, you know, a zip said, I think it's the the opportunity to change the operational more. And I think one of the big things that was very different about our company is and, you know, we like to say, you know, we're building for effort. Operators, by operators, you know, I've found is, as I said, well, more operators from Apple, they have lived and breathed what it is to be woken up at three. A. M. On Christmas Eve toe. You know, some outage and have to, you know, try and figure that out and fight your way through a legacy kind of network and figure out what's going on. So you know, so they empathize with what that means and having that DNA and our company is incredibly meaningful in terms of how we build that you know the product on how we engage with customers. We're not just a bunch of vendors who you know we're coming from, you know, previous spender backgrounds. Although I do, you know, I bring to the table the ability to, you know, to deliver a package and you know, So there's just a cloud scale its clouds, Gail. It's it's but it's It's enabling a bridge if you like. If you look at what the hyper scales have done, what they're achieving and the operational models they have, where a if you like a bridge to enable that capability for a much broader set of operators and C. S. P s and as a service companies and dry forward a an aggressive Angela innovation agenda for companies, >> businesses. You know, we always discussing the Cuban. Everyone who watches the Kiev knows I'm always ranting about how cloud providers make their market share numbers, and lot of people include sass, right? I think everyone will be in the SAS business, so I kind of look at the SAS numbers on, say, it's really infrastructures service platform to service Amazon, Google, Microsoft and then, you know, Ali Baba in China. Others. Then you got IBM or one of it's kind of in the big kind of cluster there top. That is a whole nother set of business requirements that sass driven this cloud based. Yeah, this seems to be a really growing market. Is that what you're targeting? And the question is, how do you relate Visa? Visa Cooper? Netease trend? Because communities and these abstraction layers, you're starting to hear things like service mesh, policy based state Full application states up. Is that you trying to that trend explain. >> We're very complimentary, Teo. Those trends, we're, you know, we're not looking to replace any of that, really. And and my big philosophy is, if you're not simplifying something, then you're not really adding back here, you know, what you're doing is complicating matters or adding another layer on top. So so yeah, I mean, we are of value to those companies who are looking at hybrid approaches or have some on prime asset. Our operating system will land on a physical, bare metal switch So you know what? What we do is when you look at it, you know, service most is your message measures and all the other, You know, technologies you talked about with very, very complimentary to those approaches because we're delivering the on underlying network infrastructure on network fabric. Whatever you'd like to call it, that can be managed natively with class native tools, squeezing the alliteration there. But but, you know, it means that you don't need toe add overlays. We don't need to sort of say, Hey, look, the network is this static, archaic thing that's really fragile. And And I mean, if we touch it, it's going to break. So let's just leave it alone and let's let's put some kind of overlay over the top of it on do you know, run over the top? What we're saying is you can collapse that down. Now what you can say, what you can do is you can say, Well, let's make the network dynamic responsive. Let's build a network operating system out of micro services so you can replace parts of it. You can, you know, fix bugs. You can fix security vulnerabilities and you can do all that on the fly without having to schedule outage windows, which is, you know, for a cloud native company or a sass or infrastructure service company. I mean, that's your business. You can't take outage windows. Your business depends on being available all the time. And so we were really changing that fundamentals of a principle of networking and saying, You know, networking is now dynamic, you know, in a very, very native way, but it also integrates very closely with Dev ops. Operational model >> is a lot of innovation that network. We're seeing that clearly around the industry. No doubt everyone sees late and see that comes into multi Cloud was saying that the trend moving the data to the compute coyote again that's a network issue network is now an innovation opportunity. So I gotta ask you, where do you guys see that happening? And I want to ask you specifically talking about the cloud architects out in the marketplace in these enterprises who were trying to figure out about the architecture of clowns. So they know on premises there, moving that into a cloud operations. We see Amazon, they see Google and Microsoft has clouds that might want to engage with have cloud native presence in a hybrid and multi cloud fashion for those cloud architects. What are the things that you like to see them doing? More of that relates to your value problems. In other words, if they're using containers or they're using micro services, is this good or bad? What? What you should enterprise to be working on that ties into your value proposition. >> So I think about this the other way around, actually, if I can kind of turn that turn that question. But on his head, I think what you know, enterprises, you know, organization C, S. P s. I think what they should be doing is focusing on their business and what their business needs. They shouldn't be looking at their infrastructure architecture and saying, you know, okay, how can we, you know, build all these pieces? And then you know what can the business and do on top of that infrastructure? You wanna look at it the other way around? I need to deploy applications rapidly. I need to innovate those applications. I need to, you know, upgrade, change whatever you need to do with those applications. And I need an infrastructure that can be responsive. I need an infrastructure that can be hybrid. I need infrastructure that can be, you know, orchestrated in the hybrid manner on DH. Therefore, I want to go and look for the building blocks out there of those those architectural and infrastructure building blocks out there that can service that application in the most appropriate way to enable the velocity of my business and the innovation from my business. Because at the end of the day, I mean, you know, when we talk to customers, the most important thing T customers, you know, is the velocity of their business. It is keeping ahead in the highly competitive environment and staying so far ahead that you're not going to be disrupted. And, you know, if any element of your infrastructure is holding you back and even you know, you know the most mild way it's a problem. It's something you should address. And we now have the capability to do that for, you know, for many, many years. In fact, you know, I would claim up to today without snap route that you know, you you do not have the ability to remove the network problem. The network is always going to be a boat anchor on your business. It introduces extra cycles. It introduces big security, of underplaying >> the problems of the network and the consequences that prior to snap her out that you guys saw. >> So I take the security issue right? I mean, everybody is very concerned about security today. One of the biggest attack vectors in the security world world today is the infrastructure. It's it's it's so vulnerable. A lot of infrastructure is is built on sort of proprietary software and operating systems. You know, it's very complex. There's a lot of, you know, operations, operational, moves out and change it. So there's there's a lot of opportunity for mistakes to be made. There's a lot of opportunity for, you know, for vulnerabilities to be exposed. And so what you want to do is you want to reduce the threat surface of, you know, your your infrastructure. So one of the things that we can do it SnapRoute that was never possible before is when you look at a traditional network operating system. Andreas, A traditional. I mean, any operating system is out there, other you know, Other >> than our own. >> It's basically a monolithic Lennox blob. It is one blob of code that contains all of the features. And it could be, you know, architect in in a way that it Sze chopped up nicely. But if you're not using certain features, they're still there. And that increases the threat surface with our sat proud plant native network operating system. Because it is a micro services are key picture. If you are not using certain services or features, you can destroy and remove the containers that contain those features and reduce the threat surface of the operating system. And then beyond that, if you do become aware ofthe vulnerability or a threat that you know is somewhere in there, you can replace it in seconds on the fly without taking the infrastructure. Damn, without having to completely replace that whole blob of software causing, you know, an outage window. So that's just one example of, you know, the things we can do. But even when it comes to simple things, like, you know, adding in new services or things because we're containerized service is a ll boot together. It's no, eh? You know it doesn't. It doesn't have a one after the other. It it's all in parallel. So you know this this operating system comes up faster. It's more reliable. It eliminates the risk factors, the security, you know, the issues that you have. It provides native automation capabilities. It natively integrates with, You know, your Dev Ops tool chain. It brings networking into the cloud. Native >> really, really isn't in frustrations. Code is an operating system, so it sounds like your solution is a cloud native operating system. That's correct. That's pretty much the solution. That's it. How do customers engage with you guys? And what do you say? That cloud architect this is Don't tell me what to do. What's the playbook, right? How you guys advice? Because I see this is a new solution. Talk about the solution and your recommendation to architects as they start thinking about building that elastic in that flexible environment. >> Yeah. I mean, I think you know, Ah, big recommendation is, you know, is to embrace, you know, that all the all of the cloud native principles and most of the companies that were talking to, you know, definitely doing that and moving very quickly. But, you know, my recommendation. You know, engaging with us is you should be looking for the network to in naval, your your goals and your you know your applications rather than limiting. I mean, that's that's the big difference that, you know, the people who really see the value in what we do recognize that, you know, the network should be Andi is an asset. It should be enabling new innovation, new capabilities in the business rather than looking at the network as necessary evil where we you know, where we have to get over its limitations or it's holding us back. And so, you know, for any organization that is, you know, is looking at deploying, you know, new switching infrastructure in any way, shape or form. I think, you know, you should be looking at Well, how am I going to integrate this into a dev ops? You know, world, how may going to integrate this into a cloud native world. So as my business moves forward, I'm actually servicing the application in enabling a faster time to service for the application for the business. At the end of the day, that's that's everybody's going, >> you know, we've been seeing in reporting this consistently, and it's even more mainstream now that cloud computing has opened up the aperture of the value and the economics and also the technical innovation around application developers coding faster having the kind of resource is. But it also created a CZ creating a renaissance and networking. So the value of networking and application development that collision is coming together very quickly. So the intersection you guys play. So I'm sure this will resonate well with customers Will as they try to figure out the role the network because against security number one analytics all the things that go into what Sadiq they care about share data, shared coat all this is kind of coming together. So if someone hears this story, they'll go, OK, love this snap around store. I gotta I gotta dig in. How do they engage you? What do you guys sell to them? What's the pitch? Give the quick plug for the company real >> quick. Engaging with us is, you know, is a simple issue. No, come to www snapper out dot com. And you know, you know contacts are up there. You know, we were currently obviously we're a small company. We sell direct, more engaged with, you know, our first customers and deploying our product, you know, right now, and it's going very, very well, and, you know, it's a PSE faras. You know how you know what and when to engage us. I would say you can engage us at any stage and and value whether or not your architect ing a whole new network deploying a new data center. Obviously. Which is, you know, it is an ideal is built from the ground up, but we add value to the >> data center preexisting data saying that wants >> the modernizing data centers. I mean, very want >> to modernize my data center, my candidate. >> So one of the biggest challenges in an existing data center in when one of the biggest areas of tension is at the top of rack switch the top of racks, which is where you connect in your you know, your your application assets, your servers are connected. You're connecting into the into the, you know, first leap into the network. One of the challenges there is. You know, Dev ops engineers, They want Teo, you know, deploy containers. They want to deploy virtual machines they wantto and stuff move stuff, change stuff and they need network engineers to help them to do that. For a network engineer, the least interesting part of the infrastructure is the top Arax. Which it is a constant barrage day in, day, out of request. Hey, can I have a villain? Can have an i p address. Can we move this? And it's not interesting. It just chews up time we alleviate that tension. What we enable you to do is network engineer can you know, deploy the network, get it up and running, and then control what needs to be controlled natively from their box from debits tool chains and allow the devil ups engineers to take control as infrastructure. So the >> Taelon is taking the stress out of the top of racks. Wedge, take the drama out of this. >> Take that arm around the network. Right. >> So okay, you have the soul from a customer. What am I buying? What do you guys offering? Is that a professional services package? Is it software? Is it a sad solution? Itself is the product. >> It is software, you know. We are. We're selling a network operating system. It lands on, you know, bare metal. He liked white box switching. Ah, nde. We offer that as both perpetual licenses or as a subscription. We also office, um, you know, the value and services around that as well. You know, Andre, right now that is, you know, that is our approach to market. You know, we may expand that, you know, two other services in the future, but that is what we're selling right now. It is a network operating >> system down. Thanks for coming and sharing this story of SnapRoute. Final question for you is you've been in this century. While we've had many conversations we'd love to talk about gear, speeds and feeds. I'll see softwares eating. The world was seeing that we're seeing cloud create massive amounts. Opportunity. You're in a big wave, right? What is this wave look like for the next couple of years? How do you see this? Playing out as Cloud continues to go global and you start to Seymour networking becoming much more innovative. Part of the equation with Mohr developers coming onboard. Faster, more scale. How do you see? It's all playing out in the industry. >> Yeah. So I think the next sort of, you know, big wave of things is really around the operational. But I mean, we've we've we've concentrated for many years in the networking industry on speeds and feeds. And then it was, you know, it's all about protocols and you know how protocol stacks of building stuff. That's all noise. It's really about How do you engage with the network? How do you how do you operate your network to service your business? Quite frankly, you know, you should not even know the network is there. If we're doing a really good job of network, you shouldn't even know about it. And that's where we need to get to is an industry. And you know that's that's my belief is where, where we can take >> it. Low latent. See programmable networks. Great stuff. SnapRoute Dominic. While no one is dominant industry friend of the Cube also keep alumni CEO of Snapper Out. Hot new start up with some big backers. Interesting signal. Programmable networks software Cloud Global all kind of big Party innovation equation. Here in Silicon Valley, I'm showing for with cube conversations. Thanks for watching