>>Hello, welcome to the Cube here in Palo Alto, California for a special presentation on Cloud native at scale, enabling super cloud modern applications with Platform nine. I'm John Furr, your host of The Cube. We had a great lineup of three interviews we're streaming today. Meor Ma Makowski, who's the co-founder and VP of Product of Platform nine. She's gonna go into detail around Arlon, the open source products, and also the value of what this means for infrastructure as code and for cloud native at scale. Bickley the chief architect of Platform nine Cube alumni. Going back to the OpenStack days. He's gonna go into why Arlon, why this infrastructure as code implication, what it means for customers and the implications in the open source community and where that value is. Really great wide ranging conversation there. And of course, Vascar, Gort, the CEO of Platform nine, is gonna talk with me about his views on Super Cloud and why Platform nine has a scalable solutions to bring cloudnative at scale. So enjoy the program. See you soon. Hello everyone. Welcome to the cube here in Palo Alto, California for special program on cloud native at scale, enabling next generation cloud or super cloud for modern application cloud native developers. I'm John Furry, host of the Cube. A pleasure to have here, me Makoski, co-founder and VP of product at Platform nine. Thanks for coming in today for this Cloudnative at scale conversation. Thank >>You for having me. >>So Cloudnative at scale, something that we're talking about because we're seeing the, the next level of mainstream success of containers Kubernetes and cloud native develop, basically DevOps in the C I C D pipeline. It's changing the landscape of infrastructure as code, it's accelerating the value proposition and the super cloud as we call it, has been getting a lot of traction because this next generation cloud is looking a lot different, but kind of the same as the first generation. What's your view on super cloud as it fits to cloud native as scales up? >>Yeah, you know, I think what's interesting, and I think the reason why Super Cloud is a really good, in a really fit term for this, and I think, I know my CEO was chatting with you as well, and he was mentioning this as well, but I think there needs to be a different term than just multi-cloud or cloud. And the reason is because as cloud native and cloud deployments have scaled, I think we've reached a point now where instead of having the traditional data center style model where you have a few large distributions of infrastructure and workload at a few locations, I think the model is kind of flipped around, right? Where you have a large number of microsites, these microsites could be your public cloud deployment, your private on-prem infrastructure deployments, or it could be your edge environment, right? And every single enterprise, every single industry is moving in that direction. And so you gotta rougher that with a terminology that, that, that indicates the scale and complexity of it. And so I think supercloud is a, is an appropriate term for that. >>So you brought a couple of things I want to dig into. You mentioned edge nodes. We're seeing not only edge nodes being the next kind of area of innovation, mainly because it's just popping up everywhere. And that's just the beginning. Wouldn't even know what's around the corner. You got buildings, you got iot, ot, and IT kind of coming together, but you also got this idea of regions, global infras infrastructures, big part of it. I just saw some news around CloudFlare shutting down a site here. There's policies being made at scale, These new challenges there. Can you share because you can have edge. So hybrid cloud is a winning formula. Everybody knows that it's a steady state. Yeah. But across multiple clouds brings in this new un engineered area, yet it hasn't been done yet. Spanning clouds. People say they're doing it, but you start to see the toe in the water, it's happening, it's gonna happen. It's only gonna get accelerated with the edge and beyond globally. So I have to ask you, what is the technical challenges in doing this? Because there's something business consequences as well, but there are technical challenges. Can you share your view on what the technical challenges are for the super cloud or across multiple edges and regions? >>Yeah, absolutely. So I think, you know, in in the context of this, the, this, this term of super cloud, I think it's sometimes easier to visualize things in terms of two access, right? I think on one end you can think of the scale in terms of just pure number of nodes that you have deploy a number of clusters in the Kubernetes space. And then on the other axis you would have your distribution factor, right? Which is, do you have these tens of thousands of nodes in one site or do you have them distributed across tens of thousands of sites with one node at each site? Right? And if you have just one flavor of this, there is enough complexity, but potentially manageable. But when you are expanding on both these access, you really get to a point where that scale really needs some well thought out, well structured solutions to address it, right? A combination of homegrown tooling along with your, you know, favorite distribution of Kubernetes is not a strategy that can help you in this environment. It may help you when you have one of this or when you, when you scale, is not at the level. >>Can you scope the complexity? Because I mean, I hear a lot of moving parts going on there, the technology's also getting better. We we're seeing cloud native become successful. There's a lot to configure, there's a lot to install. Can you scope the scale of the problem? Because we're talking about at scale Yep. Challenges here. Yeah, >>Absolutely. And I think, you know, I I like to call it, you know, the, the, the problem that the scale creates, you know, there's various problems, but I think one, one problem, one way to think about it is, is, you know, it works on my cluster problem, right? So I, you know, I come from engineering background and there's a, you know, there's a famous saying between engineers and QA and the support folks, right? Which is, it works on my laptop, which is I tested this chain, everything was fantastic, it worked flawlessly on my machine, on production, It's not working. The exact same problem now happens and these distributed environments, but at massive scale, right? Which is that, you know, developers test their applications, et cetera within the sanctity of their sandbox environments. But once you expose that change in the wild world of your production deployment, right? >>And the production deployment could be going at the radio cell tower at the edge location where a cluster is running there, or it could be sending, you know, these applications and having them run at my customer site where they might not have configured that cluster exactly the same way as I configured it, or they configured the cluster, right? But maybe they didn't deploy the security policies, or they didn't deploy the other infrastructure plugins that my app relies on. All of these various factors are their own layer of complexity. And there really isn't a simple way to solve that today. And that is just, you know, one example of an issue that happens. I think another, you know, whole new ball game of issues come in the context of security, right? Because when you are deploying applications at scale in a distributed manner, you gotta make sure someone's job is on the line to ensure that the right security policies are enforced regardless of that scale factor. So I think that's another example of problems that occur. >>Okay. So I have to ask about scale, because there are a lot of multiple steps involved when you see the success of cloud native. You know, you see some, you know, some experimentation. They set up a cluster, say it's containers and Kubernetes, and then you say, Okay, we got this, we can figure it. And then they do it again and again, they call it day two. Some people call it day one, day two operation, whatever you call it. Once you get past the first initial thing, then you gotta scale it. Then you're seeing security breaches, you're seeing configuration errors. This seems to be where the hotspot is in when companies transition from, I got this to, Oh no, it's harder than I thought at scale. Can you share your reaction to that and how you see this playing out? >>Yeah, so, you know, I think it's interesting. There's multiple problems that occur when, you know, the two factors of scale, as we talked about, start expanding. I think one of them is what I like to call the, you know, it, it works fine on my cluster problem, which is back in, when I was a developer, we used to call this, it works on my laptop problem, which is, you know, you have your perfectly written code that is operating just fine on your machine, your sandbox environment. But the moment it runs production, it comes back with p zeros and pos from support teams, et cetera. And those issues can be really difficult to triage us, right? And so in the Kubernetes environment, this problem kind of multi folds, it goes, you know, escalates to a higher degree because you have your sandbox developer environments, they have their clusters and things work perfectly fine in those clusters because these clusters are typically handcrafted or a combination of some scripting and handcrafting. >>And so as you give that change to then run at your production edge location, like say your radio cell tower site, or you hand it over to a customer to run it on their cluster, they might not have not have configured that cluster exactly how you did, or they might not have configured some of the infrastructure plugins. And so the things don't work. And when things don't work, triaging them becomes nightmarishly hard, right? It's just one of the examples of the problem, another whole bucket of issues is security, which is, is you have these distributed clusters at scale, you gotta ensure someone's job is on the line to make sure that these security policies are configured properly. >>So this is a huge problem. I love that comment. That's not not happening on my system. It's the classic, you know, debugging mentality. Yeah. But at scale it's hard to do that with error prone. I can see that being a problem. And you guys have a solution you're launching. Can you share what Arlon is this new product? What is it all about? Talk about this new introduction. >>Yeah, absolutely. Very, very excited. You know, it's one of the projects that we've been working on for some time now because we are very passionate about this problem and just solving problems at scale in on-prem or at in the cloud or at edge environments. And what arlon is, it's an open source project, and it is a tool, it's a Kubernetes native tool for complete end to end management of not just your clusters, but your clusters. All of the infrastructure that goes within and along the site of those clusters, security policies, your middleware, plug-ins, and finally your applications. So what our LA you do in a nutshell is in a declarative way, it lets you handle the configuration and management of all of these components in at scale. >>So what's the elevator pitch simply put for what dissolves in, in terms of the chaos you guys are reigning in, what's the, what's the bumper sticker? Yeah, what >>Would it do? There's a perfect analogy that I love to reference in this context, which is think of your assembly line, you know, in a traditional, let's say, you know, an auto manufacturing factory or et cetera, and the level of efficiency at scale that that assembly line brings, right? Our line, and if you look at the logo we've designed, it's this funny little robot. And it's because when we think of online, we think of these enterprise large scale environments, you know, sprawling at scale, creating chaos because there isn't necessarily a well thought through, well structured solution that's similar to an assembly line, which is taking each component, you know, addressing them, manufacturing, processing them in a standardized way, then handing to the next stage. But again, it gets, you know, processed in a standardized way. And that's what arlon really does. That's like the deliver pitch. If you have problems of scale of managing your infrastructure, you know, that is distributed. Arlon brings the assembly line level of efficiency and consistency for >>Those. So keeping it smooth, the assembly on things are flowing. See c i CD pipe pipelining. Exactly. So that's what you're trying to simplify that ops piece for the developer. I mean, it's not really ops, it's their ops, it's coding. >>Yeah. Not just developer, the ops, the operations folks as well, right? Because developers, you know, there is, developers are responsible for one picture of that layer, which is my apps, and then maybe that middleware of applications that they interface with, but then they hand it over to someone else who's then responsible to ensure that these apps are secure properly, that they are logging, logs are being collected properly, monitoring and observability integrated. And so it solves problems for both >>Those teams. Yeah. It's DevOps. So the DevOps is the cloud needed developer's. That's right. The option teams have to kind of set policies. Is that where the declarative piece comes in? Is that why that's important? >>Absolutely. Yeah. And, and, and, and you know, ES really in introduced or elevated this declarative management, right? Because, you know, s clusters are Yeah. Or your, yeah, you know, specifications of components that go in Kubernetes are defined a declarative way, and Kubernetes always keeps that state consistent with your defined state. But when you go outside of that world of a single cluster, and when you actually talk about defining the clusters or defining everything that's around it, there really isn't a solution that does that today. And so Arlon addresses that problem at the heart of it, and it does that using existing open source well known solutions. >>And do I want to get into the benefits? What's in it for me as the customer developer? But I want to finish this out real quick and get your thoughts. You mentioned open source. Why open source? What's the, what's the current state of the product? You run the product group over at Platform nine, is it open source? And you guys have a product that's commercial? Can you explain the open source dynamic? And first of all, why open source? Yeah. And what is the consumption? I mean, open source is great, People want open source, they can download it, look up the code, but maybe wanna buy the commercial. So I'm assuming you have that thought through, can you share open source and commercial relationship? >>Yeah, I think, you know, starting with why open source? I think it's, you know, we as a company, we have, you know, one of the things that's absolutely critical to us is that we take mainstream open source technologies components and then we, you know, make them available to our customers at scale through either a SaaS model or on-prem model, right? But, so as we are a company or startup or a company that benefits, you know, in a massive way by this open source economy, it's only right, I think in my mind that we do our part of the duty, right? And contribute back to the community that feeds us. And so, you know, we have always held that strongly as one of our principles. And we have, you know, created and built independent products starting all the way with fision, which was a serverless product, you know, that we had built to various other, you know, examples that I can give. But that's one of the main reasons why opensource and also open source, because we want the community to really firsthand engage with us on this problem, which is very difficult to achieve if your product is behind a wall, you know, behind, behind a block box. >>Well, and that's, that's what the developers want too. And what we're seeing in reporting with Super Cloud is the new model of consumption is I wanna look at the code and see what's in there. That's right. And then also, if I want to use it, I'll do it. Great. That's open source, that's the value. But then at the end of the day, if I wanna move fast, that's when people buy in. So it's a new kind of freemium, I guess, business model. I guess that's the way that long. But that's, that's the benefit. Open source. This is why standards and open source is growing so fast. You have that confluence of, you know, a way for developers to try before they buy, but also actually kind of date the application, if you will. We, you know, Adrian Karo uses the dating met metaphor, you know, Hey, you know, I wanna check it out first before I get married. Right? And that's what open source, So this is the new, this is how people are selling. This is not just open source, this is how companies are selling. >>Absolutely. Yeah. Yeah. You know, I think, and you know, two things. I think one is just, you know, this, this, this cloud native space is so vast that if you, if you're building a close flow solution, sometimes there's also a risk that it may not apply to every single enterprises use cases. And so having it open source gives them an opportunity to extend it, expand it, to make it proper to their use case if they choose to do so, right? But at the same time, what's also critical to us is we are able to provide a supported version of it with an SLA that we, you know, that's backed by us, a SAS hosted version of it as well, for those customers who choose to go that route, you know, once they have used the open source version and loved it and want to take it at scale and in production and need, need, need a partner to collaborate with, who can, you know, support them for that production >>Environment. I have to ask you now, let's get into what's in it for the customer. I'm a customer. Yep. Why should I be enthused about Arla? What's in it for me? You know? Cause if I'm not enthused about it, I'm not gonna be confident and it's gonna be hard for me to get behind this. Can you share your enthusiastic view of, you know, why I should be enthused about Arlo? I'm a >>Customer. Yeah, absolutely. And so, and there's multiple, you know, enterprises that we talk to, many of them, you know, our customers, where this is a very kind of typical story that you hear, which is we have, you know, a Kubernetes distribution. It could be on premise, it could be public clouds, native Kubernetes, and then we have our C I C D pipelines that are automating the deployment of applications, et cetera. And then there's this gray zone. And the gray zone is well before you can you, your CS c D pipelines can deploy the apps. Somebody needs to do all of that groundwork of, you know, defining those clusters and yeah. You know, properly configuring them. And as these things, these things start by being done hand grown. And then as the, as you scale, what typically enterprises would do today is they will have their home homegrown DIY solutions for this. >>I mean, the number of folks that I talk to that have built Terra from automation, and then, you know, some of those key developers leave. So it's a typical open source or typical, you know, DIY challenge. And the reason that they're writing it themselves is not because they want to. I mean, of course technology is always interesting to everybody, but it's because they can't find a solution that's out there that perfectly fits the problem. And so that's that pitch. I think Ops FICO would be delighted. The folks that we've talk, you know, spoken with, have been absolutely excited and have, you know, shared that this is a major challenge we have today because we have, you know, few hundreds of clusters on ecos Amazon, and we wanna scale them to few thousands, but we don't think we are ready to do that. And this will give us the >>Ability to, Yeah, I think people are scared. Not sc I won't say scare, that's a bad word. Maybe I should say that they feel nervous because, you know, at scale small mistakes can become large mistakes. This is something that is concerning to enterprises. And, and I think this is gonna come up at co con this year where enterprises are gonna say, Okay, I need to see SLAs. I wanna see track record, I wanna see other companies that have used it. Yeah. How would you answer that question to, or, or challenge, you know, Hey, I love this, but is there any guarantees? Is there any, what's the SLAs? I'm an enterprise, I got tight, you know, I love the open source trying to free fast and loose, but I need hardened code. >>Yeah, absolutely. So, so two parts to that, right? One is Arlan leverages existing open source components, products that are extremely popular. Two specifically. One is Arlan uses Argo cd, which is probably one of the highest and used CD open source tools that's out there. Right's created by folks that are as part of into team now, you know, really brilliant team. And it's used at scale across enterprises. That's one. Second is Alon also makes use of Cluster api cappi, which is a Kubernetes sub-component, right? For lifecycle management of clusters. So there is enough of, you know, community users, et cetera, around these two products, right? Or, or, or open source projects that will find Arlan to be right up in their alley because they're already comfortable, familiar with Argo cd. Now Arlan just extends the scope of what City can do. And so that's one. And then the second part is going back to a point of the comfort. And that's where, you know, platform line has a role to play, which is when you are ready to deploy online at scale, because you've been, you know, playing with it in your DEF test environments, you're happy with what you get with it, then Platform nine will stand behind it and provide that >>Sla. And what's been the reaction from customers you've talked to Platform nine customers with, with that are familiar with, with Argo and then rlo? What's been some of the feedback? >>Yeah, I, I think the feedback's been fantastic. I mean, I can give you examples of customers where, you know, initially, you know, when you are, when you're telling them about your entire portfolio of solutions, it might not strike a card right away. But then we start talking about Arlan and, and we talk about the fact that it uses Argo adn, they start opening up, they say, We have standardized on Argo and we have built these components, homegrown, we would be very interested. Can we co-develop? Does it support these use cases? So we've had that kind of validation. We've had validation all the way at the beginning of our land before we even wrote a single line of code saying this is something we plan on doing. And the customer said, If you had it today, I would've purchased it. So it's been really great validation. >>All right. So next question is, what is the solution to the customer? If I asked you, Look it, I have, I'm so busy, my team's overworked. I got a skills gap. I don't need another project that's, I'm so tied up right now and I'm just chasing my tail. How does Platform nine help me? >>Yeah, absolutely. So I think, you know, one of the core tenets of Platform nine has always been been that we try to bring that public cloud like simplicity by hosting, you know, this in a lot of such similar tools in a SaaS hosted manner for our customers, right? So our goal behind doing that is taking away or trying to take away all of that complexity from customers' hands and offloading it to our hands, right? And giving them that full white glove treatment, as we call it. And so from a customer's perspective, one, something like arlon will integrate with what they have so they don't have to rip and replace anything. In fact, it will, even in the next versions, it may even discover your clusters that you have today and you know, give you an inventory. And that will, >>So if customers have clusters that are growing, that's a sign correct call you guys. >>Absolutely. Either they're, they have massive large clusters, right? That they wanna split into smaller clusters, but they're not comfortable doing that today, or they've done that already on say, public cloud or otherwise. And now they have management challenges. So >>Especially operationalizing the clusters, whether they want to kind of reset everything and remove things around and reconfigure Yep. And or scale out. >>That's right. Exactly. And >>You provide that layer of policy. >>Absolutely. >>Yes. That's the key value here. >>That's right. >>So policy based configuration for cluster scale up, >>Well profile and policy based declarative configuration and lifecycle management for clusters. >>If I asked you how this enables supercloud, what would you say to that? >>I think this is one of the key ingredients to super cloud, right? If you think about a super cloud environment, there's at least few key ingredients that that come to my mind that are really critical. Like they are, you know, life saving ingredients at that scale. One is having a really good strategy for managing that scale, you know, in a, going back to assembly line in a very consistent, predictable way so that our lot solves then you, you need to compliment that with the right kind of observability and monitoring tools at scale, right? Because ultimately issues are gonna happen and you're gonna have to figure out, you know, how to solve them fast. And arlon by the way, also helps in that direction, but you also need observability tools. And then especially if you're running it on the public cloud, you need some cost management tools. In my mind, these three things are like the most necessary ingredients to make Super Cloud successful. And you know, our alarm fills in >>One. Okay. So now the next level is, Okay, that makes sense. Is under the covers kind of speak under the hood. Yeah. How does that impact the app developers and the cloud native modern application workflows? Because the impact to me, seems the apps are gonna be impacted. Are they gonna be faster, stronger? I mean, what's the impact if you do all those things, as you mentioned, what's the impact of the apps? >>Yeah, the impact is that your apps are more likely to operate in production the way you expect them to, because the right checks and balances have gone through, and any discrepancies have been identified prior to those apps, prior to your customer running into them, right? Because developers run into this challenge to their, where there's a split responsibility, right? I'm responsible for my code, I'm responsible for some of these other plugins, but I don't own the stack end to end. I have to rely on my ops counterpart to do their part, right? And so this really gives them, you know, the right tooling for that. >>So this is actually a great kind of relevant point, you know, as cloud becomes more scalable, you're starting to see this fragmentation gone of the days of the full stack developer to the more specialized role. But this is a key point, and I have to ask you because if this RLO solution takes place, as you say, and the apps are gonna be stupid, they're designed to do, the question is, what did does the current pain look like of the apps breaking? What does the signals to the customer Yeah. That they should be calling you guys up into implementing Arlo, Argo and, and all the other goodness to automate? What are some of the signals? Is it downtime? Is it, is it failed apps, Is it latency? What are some of the things that Yeah, absolutely would be indications of things are effed up a little bit. Yeah. >>More frequent down times, down times that are, that take longer to triage. And so you are, you know, the, you know, your mean times on resolution, et cetera, are escalating or growing larger, right? Like we have environments of customers where they're, they have a number of folks on in the field that have to take these apps and run them at customer sites. And that's one of our partners. And they're extremely interested in this because they're the, the rate of failures they're encountering for this, you know, the field when they're running these apps on site, because the field is automating their clusters that are running on sites using their own script. So these are the kinds of challenges, and those are the pain points, which is, you know, if you're looking to reduce your meantime to resolution, if you're looking to reduce the number of failures that occur on your production site, that's one. And second, if you are looking to manage these at scale environments with a relatively small, focused, nimble ops team, which has an immediate impact on your budget. So those are, those are the signals. >>This is the cloud native at scale situation, the innovation going on. Final thought is your reaction to the idea that if the world goes digital, which it is, and the confluence of physical and digital coming together, and cloud continues to do its thing, the company becomes the application, not where it used to be supporting the business, you know, the back office and the maybe terminals and some PCs and handhelds. Now if technology's running, the business is the business. Yeah. Company's the application. Yeah. So it can't be down. So there's a lot of pressure on, on CSOs and CIOs now and boards is saying, How is technology driving the top line revenue? That's the number one conversation. Yep. Do you see that same thing? >>Yeah. It's interesting. I think there's multiple pressures at the CXO CIO level, right? One is that there needs to be that visibility and clarity and guarantee almost that, you know, that the, the technology that's, you know, that's gonna drive your top line is gonna drive that in a consistent, reliable, predictable manner. And then second, there is the constant pressure to do that while always lowering your costs of doing it, right? Especially when you're talking about, let's say retailers or those kinds of large scale vendors, they many times make money by lowering the amount that they spend on, you know, providing those goods to their end customers. So I think those, both those factors kind of come into play and the solution to all of them is usually in a very structured strategy around automation. >>Final question. What does cloudnative at scale look like to you? If all the things happen the way we want 'em to happen, The magic wand, the magic dust, what does it look like? >>What that looks like to me is a CIO sipping at his desk on coffee production is running absolutely smooth. And his, he's running that at a nimble, nimble team size of at the most, a handful of folks that are just looking after things, but things are >>Just taking care of the CIO doesn't exist. There's no ciso, they're at the beach. >>Yep. >>Thank you for coming on, sharing the cloud native at scale here on the cube. Thank you for your time. >>Fantastic. Thanks for >>Having me. Okay. I'm John Fur here for special program presentation, special programming cloud native at scale, enabling super cloud modern applications with Platform nine. Thanks for watching. Welcome back everyone to the special presentation of cloud native at scale, the cube and platform nine special presentation going in and digging into the next generation super cloud infrastructure as code and the future of application development. We're here with Bickley, who's the chief architect and co-founder of Platform nine Pick. Great to see you Cube alumni. We, we met at an OpenStack event in about eight years ago, or later, earlier when OpenStack was going. Great to see you and great to see congratulations on the success of platform nine. >>Thank you very much. >>Yeah. You guys have been at this for a while and this is really the, the, the year we're seeing the, the crossover of Kubernetes because of what happens with containers. Everyone now has realized, and you've seen what Docker's doing with the new docker, the open source Docker now just the success Exactly. Of containerization, right? And now the Kubernetes layer that we've been working on for years is coming, bearing fruit. This is huge. >>Exactly. Yes. >>And so as infrastructures code comes in, we talked to Bacar talking about Super Cloud, I met her about, you know, the new Arlon, our, our lawn, and you guys just launched the infrastructures code is going to another level, and then it's always been DevOps infrastructures code. That's been the ethos that's been like from day one, developers just code. Then you saw the rise of serverless and you see now multi-cloud or on the horizon, connect the dots for us. What is the state of infrastructure as code today? >>So I think, I think I'm, I'm glad you mentioned it, everybody or most people know about infrastructures code. But with Kubernetes, I think that project has evolved at the concept even further. And these dates, it's infrastructure is configuration, right? So, which is an evolution of infrastructure as code. So instead of telling the system, here's how I want my infrastructure by telling it, you know, do step A, B, C, and D instead with Kubernetes, you can describe your desired state declaratively using things called manifest resources. And then the system kind of magically figures it out and tries to converge the state towards the one that you specified. So I think it's, it's a even better version of infrastructures code. >>Yeah. And that really means it's developer just accessing resources. Okay. That declare, Okay, give me some compute, stand me up some, turn the lights on, turn 'em off, turn 'em on. That's kind of where we see this going. And I like the configuration piece. Some people say composability, I mean now with open source so popular, you don't have to have to write a lot of code, this code being developed. And so it's into integration, it's configuration. These are areas that we're starting to see computer science principles around automation, machine learning, assisting open source. Cuz you got a lot of code that's right in hearing software, supply chain issues. So infrastructure as code has to factor in these new dynamics. Can you share your opinion on these new dynamics of, as open source grows, the glue layers, the configurations, the integration, what are the core issues? >>I think one of the major core issues is with all that power comes complexity, right? So, you know, despite its expressive power systems like Kubernetes and declarative APIs let you express a lot of complicated and complex stacks, right? But you're dealing with hundreds if not thousands of these yamo files or resources. And so I think, you know, the emergence of systems and layers to help you manage that complexity is becoming a key challenge and opportunity in, in this space. >>That's, I wrote a LinkedIn post today was comments about, you know, hey, enterprise is a new breed. The trend of SaaS companies moving our consumer comp consumer-like thinking into the enterprise has been happening for a long time, but now more than ever, you're seeing it the old way used to be solve complexity with more complexity and then lock the customer in. Now with open source, it's speed, simplification and integration, right? These are the new dynamic power dynamics for developers. Yeah. So as companies are starting to now deploy and look at Kubernetes, what are the things that need to be in place? Because you have some, I won't say technical debt, but maybe some shortcuts, some scripts here that make it look like infrastructure is code. People have done some things to simulate or or make infrastructure as code happen. Yes. But to do it at scale Yes. Is harder. What's your take on this? What's your view? >>It's hard because there's a per proliferation of methods, tools, technologies. So for example, today it's very common for DevOps and platform engineering tools, I mean, sorry, teams to have to deploy a large number of Kubernetes clusters, but then apply the applications and configurations on top of those clusters. And they're using a wide range of tools to do this, right? For example, maybe Ansible or Terraform or bash scripts to bring up the infrastructure and then the clusters. And then they may use a different set of tools such as Argo CD or other tools to apply configurations and applications on top of the clusters. So you have this sprawl of tools. You, you also have this sprawl of configurations and files because the more objects you're dealing with, the more resources you have to manage. And there's a risk of drift that people call that where, you know, you think you have things under control, but some people from various teams will make changes here and there and then before the end of the day systems break and you have no idea of tracking them. So I think there's real need to kind of unify, simplify, and try to solve these problems using a smaller, more unified set of tools and methodologies. And that's something that we try to do with this new project. Arlon. >>Yeah. So, so we're gonna get into Arlan in a second. I wanna get into the why Arlon. You guys announced that at AR GoCon, which was put on here in Silicon Valley at the, at the community meeting by in two, they had their own little day over there at their headquarters. But before we get there, vascar, your CEO came on and he talked about Super Cloud at our in AAL event. What's your definition of super cloud? If you had to kind of explain that to someone at a cocktail party or someone in the industry technical, how would you look at the super cloud trend that's emerging? It's become a thing. What's your, what would be your contribution to that definition or the narrative? >>Well, it's, it's, it's funny because I've actually heard of the term for the first time today, speaking to you earlier today. But I think based on what you said, I I already get kind of some of the, the gist and the, the main concepts. It seems like super cloud, the way I interpret that is, you know, clouds and infrastructure, programmable infrastructure, all of those things are becoming commodity in a way. And everyone's got their own flavor, but there's a real opportunity for people to solve real business problems by perhaps trying to abstract away, you know, all of those various implementations and then building better abstractions that are perhaps business or applications specific to help companies and businesses solve real business problems. >>Yeah, I remember that's a great, great definition. I remember, not to date myself, but back in the old days, you know, IBM had a proprietary network operating system, so of deck for the mini computer vendors, deck net and SNA respectively. But T C P I P came out of the osi, the open systems interconnect and remember, ethernet beat token ring out. So not to get all nerdy for all the young kids out there, look, just look up token ring, you'll see, you've probably never heard of it. It's IBM's, you know, connection for the internet at the, the layer two is Amazon, the ethernet, right? So if T C P I P could be the Kubernetes and the container abstraction that made the industry completely change at that point in history. So at every major inflection point where there's been serious industry change and wealth creation and business value, there's been an abstraction Yes. Somewhere. Yes. What's your reaction to that? >>I think this is, I think a saying that's been heard many times in this industry and, and I forgot who originated it, but I think that the saying goes like, there's no problem that can't be solved with another layer of indirection, right? And we've seen this over and over and over again where Amazon and its peers have inserted this layer that has simplified, you know, computing and, and infrastructure management. And I believe this trend is going to continue, right? The next set of problems are going to be solved with these insertions of additional abstraction layers. I think that that's really a, yeah, it's gonna >>Continue. It's interesting. I just, when I wrote another post today on LinkedIn called the Silicon Wars AMD stock is down arm has been on a rise. We remember pointing for many years now that arm's gonna be hugely, it has become true. If you look at the success of the infrastructure as a service layer across the clouds, Azure, aws, Amazon's clearly way ahead of everybody. The stuff that they're doing with the silicon and the physics and the, the atoms, the pro, you know, this is where the innovation, they're going so deep and so strong at ISAs, the more that they get that gets come on, they have more performance. So if you're an app developer, wouldn't you want the best performance and you'd wanna have the best abstraction layer that gives you the most ability to do infrastructures, code or infrastructure for configuration, for provisioning, for managing services. And you're seeing that today with service MeSHs, a lot of action going on in the service mesh area in in this community of, of co con, which will be a covering. So that brings up the whole what's next? You guys just announced our lawn at Argo Con, which came out of Intuit. We've had Mariana Tessel at our super cloud event. She's the cto, you know, they're all in the cloud. So they contributed that project. Where did Arlon come from? What was the origination? What's the purpose? Why our lawn, why this announcement? >>Yeah, so the, the inception of the project, this was the result of us realizing that problem that we spoke about earlier, which is complexity, right? With all of this, these clouds, these infrastructure, all the variations around and, you know, compute storage networks and the proliferation of tools we talked about the Ansibles and Terraforms and Kubernetes itself. You can, you can think of that as another tool, right? We saw a need to solve that complexity problem, and especially for people and users who use Kubernetes at scale. So when you have, you know, hundreds of clusters, thousands of applications, thousands of users spread out over many, many locations, there, there needs to be a system that helps simplify that management, right? So that means fewer tools, more expressive ways of describing the state that you want and more consistency. And, and that's why, you know, we built our lawn and we built it recognizing that many of these problems or sub problems have already been solved. So Arlon doesn't try to reinvent the wheel, it instead rests on the shoulders of several giants, right? So for example, Kubernetes is one building block, GI ops, and Argo CD is another one, which provides a very structured way of applying configuration. And then we have projects like cluster API and cross plane, which provide APIs for describing infrastructure. So arlon takes all of those building blocks and builds a thin layer, which gives users a very expressive way of defining configuration and desired state. So that's, that's kind of the inception of, And >>What's the benefit of that? What does that give the, what does that give the developer, the user, in this case, >>The developers, the, the platform engineer, team members, the DevOps engineers, they get a a ways to provision not just infrastructure and clusters, but also applications and configurations. They get a way, a system for provisioning, configuring, deploying, and doing life cycle management in a, in a much simpler way. Okay. Especially as I said, if you're dealing with a large number of applications. >>So it's like an operating fabric, if you will. Yes. For them. Okay, so let's get into what that means for up above and below the the, this abstraction or thin layer below as the infrastructure. We talked a lot about what's going on below that. Yeah. Above our workloads. At the end of the day, you know, I talk to CXOs and IT folks that are now DevOps engineers. They care about the workloads and they want the infrastructures code to work. They wanna spend their time getting in the weeds, figuring out what happened when someone made a push that that happened or something happened. They need observability and they need to, to know that it's working. That's right. And is my workloads running effectively? So how do you guys look at the workload side of it? Cuz now you have multiple workloads on these fabric, >>Right? So workloads, so Kubernetes has defined kind of a standard way to describe workloads and you can, you know, tell Kubernetes, I want to run this container this particular way, or you can use other projects that are in the Kubernetes cloud native ecosystem like K native, where you can express your application in more at a higher level, right? But what's also happening is in addition to the workloads, DevOps and platform engineering teams, they need to very often deploy the applications with the clusters themselves. Clusters are becoming this commodity. It's, it's becoming this host for the application and it kind of comes bundled with it. In many cases it is like an appliance, right? So DevOps teams have to provision clusters at a really incredible rate and they need to tear them down. Clusters are becoming more, >>It's kinda like an EC two instance, spin up a cluster. We very, people used words like that. That's >>Right. And before arlon you kind of had to do all of that using a different set of tools as, as I explained. So with Armon you can kind of express everything together. You can say I want a cluster with a health monitoring stack and a logging stack and this ingress controller and I want these applications and these security policies. You can describe all of that using something we call a profile. And then you can stamp out your app, your applications and your clusters and manage them in a very, so >>Essentially standard creates a mechanism. Exactly. Standardized, declarative kind of configurations. And it's like a playbook. You deploy it. Now what's there is between say a script like I'm, I have scripts, I could just automate scripts >>Or yes, this is where that declarative API and infrastructures configuration comes in, right? Because scripts, yes you can automate scripts, but the order in which they run matters, right? They can break, things can break in the middle and, and sometimes you need to debug them. Whereas the declarative way is much more expressive and powerful. You just tell the system what you want and then the system kind of figures it out. And there are these things about controllers which will in the background reconcile all the state to converge towards your desire. It's a much more powerful, expressive and reliable way of getting things done. >>So infrastructure has configuration is built kind of on, it's as super set of infrastructures code because it's >>An evolution. >>You need edge's code, but then you can configure the code by just saying do it. You basically declaring and saying Go, go do that. That's right. Okay, so, alright, so cloud native at scale, take me through your vision of what that means. Someone says, Hey, what does cloud native at scale mean? What's success look like? How does it roll out in the future as you, not future next couple years? I mean people are now starting to figure out, okay, it's not as easy as it sounds. Could be nice, it has value. We're gonna hear this year coan a lot of this. What does cloud native at scale >>Mean? Yeah, there are different interpretations, but if you ask me, when people think of scale, they think of a large number of deployments, right? Geographies, many, you know, supporting thousands or tens or millions of, of users there, there's that aspect to scale. There's also an equally important a aspect of scale, which is also something that we try to address with Arran. And that is just complexity for the people operating this or configuring this, right? So in order to describe that desired state and in order to perform things like maybe upgrades or updates on a very large scale, you want the humans behind that to be able to express and direct the system to do that in, in relatively simple terms, right? And so we want the tools and the abstractions and the mechanisms available to the user to be as powerful but as simple as possible. So there's, I think there's gonna be a number and there have been a number of CNCF and cloud native projects that are trying to attack that complexity problem as well. And Arlon kind of falls in in that >>Category. Okay, so I'll put you on the spot road that CubeCon coming up and obviously this will be shipping this segment series out before. What do you expect to see at Coan this year? What's the big story this year? What's the, what's the most important thing happening? Is it in the open source community and also within a lot of the, the people jogging for leadership. I know there's a lot of projects and still there's some white space in the overall systems map about the different areas get run time and there's ability in all these different areas. What's the, where's the action? Where, where's the smoke? Where's the fire? Where's the piece? Where's the tension? >>Yeah, so I think one thing that has been happening over the past couple of cons and I expect to continue and, and that is the, the word on the street is Kubernetes is getting boring, right? Which is good, right? >>Boring means simple. >>Well, well >>Maybe, >>Yeah, >>Invisible, >>No drama, right? So, so the, the rate of change of the Kubernetes features and, and all that has slowed but in, in a, in a positive way. But there's still a general sentiment and feeling that there's just too much stuff. If you look at a stack necessary for hosting applications based on Kubernetes, there are just still too many moving parts, too many components, right? Too much complexity. I go, I keep going back to the complexity problem. So I expect Cube Con and all the vendors and the players and the startups and the people there to continue to focus on that complexity problem and introduce further simplifications to, to the stack. >>Yeah. Vic, you've had an storied career, VMware over decades with them obviously in 12 years with 14 years or something like that. Big number co-founder here at Platform. Now you guys have been around for a while at this game. We, man, we talked about OpenStack, that project you, we interviewed at one of their events. So OpenStack was the beginning of that, this new revolution. And I remember the early days it was, it wasn't supposed to be an alternative to Amazon, but it was a way to do more cloud cloud native. I think we had a cloud ERO team at that time. We would to joke we, you know, about, about the dream. It's happening now, now at Platform nine. You guys have been doing this for a while. What's the, what are you most excited about as the chief architect? What did you guys double down on? What did you guys tr pivot from or two, did you do any pivots? Did you extend out certain areas? Cuz you guys are in a good position right now, a lot of DNA in Cloud native. What are you most excited about and what does Platform nine bring to the table for customers and for people in the industry watching this? >>Yeah, so I think our mission really hasn't changed over the years, right? It's been always about taking complex open source software because open source software, it's powerful. It solves new problems, you know, every year and you have new things coming out all the time, right? OpenStack was an example when the Kubernetes took the world by storm. But there's always that complexity of, you know, just configuring it, deploying it, running it, operating it. And our mission has always been that we will take all that complexity and just make it, you know, easy for users to consume regardless of the technology, right? So the successor to Kubernetes, you know, I don't have a crystal ball, but you know, you have some indications that people are coming up of new and simpler ways of running applications. There are many projects around there who knows what's coming next year or the year after that. But platform will a, platform nine will be there and we will, you know, take the innovations from the the community. We will contribute our own innovations and make all of those things very consumable to customers. >>Simpler, faster, cheaper. Exactly. Always a good business model technically to make that happen. Yes. Yeah, I think the, the reigning in the chaos is key, you know, Now we have now visibility into the scale. Final question before we depart this segment. What is at scale, how many clusters do you see that would be a watermark for an at scale conversation around an enterprise? Is it workloads we're looking at or, or clusters? How would you, Yeah, how would you describe that? When people try to squint through and evaluate what's a scale, what's the at scale kind of threshold? >>Yeah. And, and the number of clusters doesn't tell the whole story because clusters can be small in terms of the number of nodes or they can be large. But roughly speaking when we say, you know, large scale cluster deployments, we're talking about maybe hundreds, two thousands. >>Yeah. And final final question, what's the role of the hyperscalers? You got AWS continuing to do well, but they got their core ias, they got a PAs, they're not too too much putting a SaaS out there. They have some SaaS apps, but mostly it's the ecosystem. They have marketplaces doing over $2 billion billions of transactions a year and, and it's just like, just sitting there. It hasn't really, they're now innovating on it, but that's gonna change ecosystems. What's the role the cloud play in the cloud native of its scale? >>The, the hyperscalers, >>Yeahs Azure, Google. >>You mean from a business perspective? Yeah, they're, they have their own interests that, you know, that they're, they will keep catering to, they, they will continue to find ways to lock their users into their ecosystem of services and, and APIs. So I don't think that's gonna change, right? They're just gonna keep, >>Well they got great I performance, I mean from a, from a hardware standpoint, yes, that's gonna be key, right? >>Yes. I think the, the move from X 86 being the dominant way and platform to run workloads is changing, right? That, that, that, that, and I think the, the hyperscalers really want to be in the game in terms of, you know, the the new risk and arm ecosystems and the platforms. >>Yeah, not joking aside, Paul Morritz, when he was the CEO of VMware, when he took over once said, I remember our first year doing the cube. Oh the cloud is one big distributed computer, it's, it's hardware and he got software and you got middleware and he kind over, well he's kind of tongue in cheek, but really you're talking about large compute and sets of services that is essentially a distributed computer. >>Yes, >>Exactly. It's, we're back on the same game. Vic, thank you for coming on the segment. Appreciate your time. This is cloud native at scale special presentation with Platform nine. Really unpacking super cloud Arlon open source and how to run large scale applications on the cloud Cloud Native Phil for developers and John Furrier with the cube. Thanks for Washington. We'll stay tuned for another great segment coming right up. Hey, welcome back everyone to Super Cloud 22. I'm John Fur, host of the Cuba here all day talking about the future of cloud. Where's it all going? Making it super multi-cloud clouds around the corner and public cloud is winning. Got the private cloud on premise and edge. Got a great guest here, Vascar Gorde, CEO of Platform nine, just on the panel on Kubernetes. An enabler blocker. Welcome back. Great to have you on. >>Good to see you >>Again. So Kubernetes is a blocker enabler by, with a question mark. I put on on that panel was really to discuss the role of Kubernetes. Now great conversation operations is impacted. What's interest thing about what you guys are doing at Platform nine? Is your role there as CEO and the company's position, kind of like the world spun into the direction of Platform nine while you're at the helm? Yeah, right. >>Absolutely. In fact, things are moving very well and since they came to us, it was an insight to call ourselves the platform company eight years ago, right? So absolutely whether you are doing it in public clouds or private clouds, you know, the application world is moving very fast in trying to become digital and cloud native. There are many options for you do on the infrastructure. The biggest blocking factor now is having a unified platform. And that's what we, we come into, >>Patrick, we were talking before we came on stage here about your background and we were gonna talk about the glory days in 2000, 2001, when the first as piece application service providers came out, kind of a SaaS vibe, but that was kind of all kind of cloudlike. >>It wasn't, >>And and web services started then too. So you saw that whole growth. Now, fast forward 20 years later, 22 years later, where we are now, when you look back then to here and all the different cycles, >>I, in fact you, you know, as we were talking offline, I was in one of those ASPs in the year 2000 where it was a novel concept of saying we are providing a software and a capability as a service, right? You sign up and start using it. I think a lot has changed since then. The tooling, the tools, the technology has really skyrocketed. The app development environment has really taken off exceptionally well. There are many, many choices of infrastructure now, right? So I think things are in a way the same but also extremely different. But more importantly now for any company, regardless of size, to be a digital native, to become a digital company is extremely mission critical. It's no longer a nice to have everybody's in the journey somewhere. >>Everyone is going digital transformation here. Even on a so-called downturn recession that's upcoming inflation's here. It's interesting. This is the first downturn in the history of the world where the hyperscale clouds have been pumping on all cylinders as an economic input. And if you look at the tech trends, GDPs down, but not tech. >>Nope. >>Cuz the pandemic showed everyone digital transformation is here and more spend and more growth is coming even in, in tech. So this is a unique factor which proves that that digital transformation's happening and company, every company will need a super cloud. >>Everyone, every company, regardless of size, regardless of location, has to become modernize their infrastructure. And modernizing Infras infrastructure is not just some new servers and new application tools, It's your approach, how you're serving your customers, how you're bringing agility in your organization. I think that is becoming a necessity for every enterprise to survive. >>I wanna get your thoughts on Super Cloud because one of the things Dave Ante and I want to do with Super Cloud and calling it that was we, I, I personally, and I know Dave as well, he can, I'll speak from, he can speak for himself. We didn't like multi-cloud. I mean not because Amazon said don't call things multi-cloud, it just didn't feel right. I mean everyone has multiple clouds by default. If you're running productivity software, you have Azure and Office 365. But it wasn't truly distributed. It wasn't truly decentralized, it wasn't truly cloud enabled. It didn't, it felt like they're not ready for a market yet. Yet public clouds booming on premise. Private cloud and Edge is much more on, you know, more, more dynamic, more real. >>Yeah. I think the reason why we think super cloud is a better term than multi-cloud. Multi-cloud are more than one cloud, but they're disconnected. Okay, you have a productivity cloud, you have a Salesforce cloud, you may have, everyone has an internal cloud, right? So, but they're not connected. So you can say okay, it's more than one cloud. So it's you know, multi-cloud. But super cloud is where you are actually trying to look at this holistically. Whether it is on-prem, whether it is public, whether it's at the edge, it's a store at the branch. You are looking at this as one unit. And that's where we see the term super cloud is more applicable because what are the qualities that you require if you're in a super cloud, right? You need choice of infrastructure, you need, but at the same time you need a single pain, a single platform for you to build your innovations on regardless of which cloud you're doing it on, right? So I think Super Cloud is actually a more tightly integrated orchestrated management philosophy we think. >>So let's get into some of the super cloud type trends that we've been reporting on. Again, the purpose of this event is to, as a pilots, to get the conversations flowing with with the influencers like yourselves who are running companies and building products and the builders, Amazon and Azure are doing extremely well. Google's coming up in third cloudworks in public cloud. We see the use cases on premises use cases. Kubernetes has been an interesting phenomenon because it's become from the developer side a little bit, but a lot of ops people love Kubernetes. It's really more of an ops thing. You mentioned OpenStack earlier. Kubernetes kind of came out of that open stack. We need an orchestration and then containers had a good shot with, with Docker. They re pivoted the company. Now they're all in an open source. So you got containers booming and Kubernetes as a new layer there. What's the, what's the take on that? What does that really mean? Is that a new defacto enabler? It >>Is here. It's for here for sure. Every enterprise somewhere else in the journey is going on. And you know, most companies are, 70 plus percent of them have won two, three container based, Kubernetes based applications now being rolled out. So it's very much here, it is in production at scale by many customers. And the beauty of it is, yes, open source, but the biggest gating factor is the skill set. And that's where we have a phenomenal engineering team, right? So it's, it's one thing to buy a tool >>And just be clear, you're a managed service for Kubernetes. >>We provide, provide a software platform for cloud acceleration as a service and it can run anywhere. It can run in public private. We have customers who do it in truly multi-cloud environments. It runs on the edge, it runs at this in stores are thousands of stores in a retailer. So we provide that and also for specific segments where data sovereignty and data residency are key regulatory reasons. We also un OnPrem as an air gap version. >>Can you give an example on how you guys are deploying your platform to enable a super cloud experience for your >>Customer? Right. So I'll give you two different examples. One is a very large networking company, public networking company. They have, I dunno, hundreds of products, hundreds of r and d teams that are building different, different products. And if you look at few years back, each one was doing it on a different platforms but they really needed to bring the agility and they worked with us now over three years where we are their build test dev pro platform where all their products are built on, right? And it has dramatically increased their agility to release new products. Number two, it actually is a light out operation. In fact the customer says like, like the Maytag service person cuz we provide it as a service and it barely takes one or two people to maintain it for them. >>So it's kinda like an SRE vibe. One person managing a >>Large 4,000 engineers building infrastructure >>On their tools, >>Whatever they want on their tools. They're using whatever app development tools they use, but they use our platform. >>What benefits are they seeing? Are they seeing speed? >>Speed, definitely. Okay. Definitely they're speeding. Speed uniformity because now they're building able to build, so their customers who are using product A and product B are seeing a similar set of tools that are being used. >>So a big problem that's coming outta this super cloud event that we're, we're seeing and we've heard it all here, ops and security teams cuz they're kind of too part of one theme, but ops and security specifically need to catch up speed wise. Are you delivering that value to ops and security? Right. >>So we, we work with ops and security teams and infrastructure teams and we layer on top of that. We have like a platform team. If you think about it, depending on where you have data centers, where you have infrastructure, you have multiple teams, okay, but you need a unified platform. Who's your buyer? Our buyer is usually, you know, the product divisions of companies that are looking at or the CTO would be a buyer for us functionally cio definitely. So it it's, it's somewhere in the DevOps to infrastructure. But the ideal one we are beginning to see now many large corporations are really looking at it as a platform and saying we have a platform group on which any app can be developed and it is run on any infrastructure. So the platform engineering teams, >>You working two sides of that coin. You've got the dev side and then >>And then infrastructure >>Side side, okay. >>Another customer like give you an example, which I would say is kind of the edge of the store. So they have thousands of stores. Retail, retail, you know food retailer, right? They have thousands of stores that are on the globe, 50,000, 60,000. And they really want to enhance the customer experience that happens when you either order the product or go into the store and pick up your product or buy or browse or sit there. They have applications that were written in the nineties and then they have very modern AIML applications today. They want something that will not have to send an IT person to install a rack in the store or they can't move everything to the cloud because the store operations has to be local. The menu changes based on, It's a classic edge. It's classic edge. Yeah. Right. They can't send it people to go install rack access servers then they can't sell software people to go install the software and any change you wanna put through that, you know, truck roll. So they've been working with us where all they do is they ship, depending on the size of the store, one or two or three little servers with instructions that >>You, you say little servers like how big one like a net box box, like a small little >>Box and all the person in the store has to do like what you and I do at home and we get a, you know, a router is connect the power, connect the internet and turn the switch on. And from there we pick it up. >>Yep. >>We provide the operating system, everything and then the applications are put on it. And so that dramatically brings the velocity for them. They manage >>Thousands of them. True plug and play >>Two, plug and play thousands of stores. They manage it centrally. We do it for them, right? So, so that's another example where on the edge then we have some customers who have both a large private presence and one of the public clouds. Okay. But they want to have the same platform layer of orchestration and management that they can use regardless of the location. So >>You guys got some success. Congratulations. Got some traction there. It's awesome. The question I want to ask you is that's come up is what is truly cloud native? Cuz there's lift and shift of the cloud >>That's not cloud native. >>Then there's cloud native. Cloud native seems to be the driver for the super cloud. How do you talk to customers? How do you explain when someone says what's cloud native, what isn't cloud native? >>Right. Look, I think first of all, the best place to look at what is the definition and what are the attributes and characteristics of what is truly a cloud native, is CNC foundation. And I think it's very well documented where you, well >>Con of course Detroit's >>Coming here, so, so it's already there, right? So, so we follow that very closely, right? I think just lifting and shifting your 20 year old application onto a data center somewhere is not cloud native. Okay? You can't put to cloud native, you have to rewrite and redevelop your application and business logic using modern tools. Hopefully more open source and, and I think that's what Cloudnative is and we are seeing a lot of our customers in that journey. Now everybody wants to be cloudnative, but it's not that easy, okay? Because it's, I think it's first of all, skill set is very important. Uniformity of tools that there's so many tools there. Thousands and thousands of tools you could spend your time figuring out which tool to use. Okay? So I think the complexities there, but the business benefits of agility and uniformity and customer experience are truly them. >>And I'll give you an example. I don't know how clear native they are, right? And they're not a customer of ours, but you order pizzas, you do, right? If you just watch the pizza industry, how dominoes actually increase their share and mind share and wallet share was not because they were making better pizzas or not, I don't know anything about that, but the whole experience of how you order, how you watch what's happening, how it's delivered. There were a pioneer in it. To me, those are the kinds of customer experiences that cloud native can provide. >>Being agility and having that flow to the application changes what the expectations of the, for the customer. >>Customer, the customer's expectations change, right? Once you get used to a better customer experience, you learn >>Best car. To wrap it up, I wanna just get your perspective again. One of the benefits of chatting with you here and having you part of the Super Cloud 22 is you've seen many cycles, you have a lot of insights. I want to ask you, given your career where you've been and what you've done and now the CEO platform nine, how would you compare what's happening now with other inflection points in the industry? And you've been, again, you've been an entrepreneur, you sold your company to Oracle, you've been seeing the big companies, you've seen the different waves. What's going on right now put into context this moment in time around Super >>Cloud. Sure. I think as you said, a lot of battles. Cars being been, been in an asp, been in a realtime software company, being in large enterprise software houses and a transformation. I've been on the app side, I did the infrastructure right and then tried to build our own platforms. I've gone through all of this myself with a lot of lessons learned in there. I think this is an event which is happening now for companies to go through to become cloud native and digitalize. If I were to look back and look at some parallels of the tsunami that's going on is a couple of paddles come to me. One is, think of it, which was forced to honors like y2k. Everybody around the world had to have a plan, a strategy, and an execution for y2k. I would say the next big thing was e-commerce. I think e-commerce has been pervasive right across all industries. >>And disruptive. >>And disruptive, extremely disruptive. If you did not adapt and adapt and accelerate your e-commerce initiative, you were, it was an existence question. Yeah. I think we are at that pivotal moment now in companies trying to become digital and cloudnative that know that is what I see >>Happening there. I think that that e-commerce was interesting and I think just to riff with you on that is that it's disrupting and refactoring the business models. I think that is something that's coming out of this is that it's not just completely changing the game, it's just changing how you operate, >>How you think, and how you operate. See, if you think about the early days of eCommerce, just putting up a shopping cart didn't made you an eCommerce or an E retailer or an e e customer, right? Or so. I think it's the same thing now is I think this is a fundamental shift on how you're thinking about your business. How are you gonna operate? How are you gonna service your customers? I think it requires that just lift and shift is not gonna work. >>Mascar, thank you for coming on, spending the time to come in and share with our community and being part of Super Cloud 22. We really appreciate, we're gonna keep this open. We're gonna keep this conversation going even after the event, to open up and look at the structural changes happening now and continue to look at it in the open in the community. And we're gonna keep this going for, for a long, long time as we get answers to the problems that customers are looking for with cloud cloud computing. I'm Sean Feer with Super Cloud 22 in the Cube. Thanks for watching. >>Thank you. Thank you, John. >>Hello. Welcome back. This is the end of our program, our special presentation with Platform nine on cloud native at scale, enabling the super cloud. We're continuing the theme here. You heard the interviews Super Cloud and its challenges, new opportunities around the solutions around like Platform nine and others with Arlon. This is really about the edge situations on the internet and managing the edge multiple regions, avoiding vendor lock in. This is what this new super cloud is all about. The business consequences we heard and and the wide ranging conversations around what it means for open source and the complexity problem all being solved. I hope you enjoyed this program. There's a lot of moving pieces and things to configure with cloud native install, all making it easier for you here with Super Cloud and of course Platform nine contributing to that. Thank you for watching.

(upbeat music) >> Live in Washington, DC. This is day two of two days of coverage. I'm John Furr, your host. We're in person face-to-face event it's kicking off day two. Dave Levy's here, Vice President of US government Nonprofit and healthcare businesses for AWS Public Sector. Dave, great to see you again, welcome back. >> Dave: Great to see you, John. >> So, great time last time we were in person, 2019, looks like the event, the last year was virtual, what's new? >> Well, first of all, I think it's just exciting. I mean, I'm excited to be back and in-person and so much has happened in our personal lives in our communities and so I'm really glad that we can all be together and it's been great so far. >> I was talking yesterday with some folks and I saw people doing some networking. I heard someone, "Hey, I'm want to hire someone." So, the face-to-face is back, we're also streaming. Max Peterson told me they're pushing it everywhere on Facebook, LinkedIn, Twitter, everywhere, Twitch, so free content, but still a lot of registrations here in person, good stuff. >> Yeah, great registrations. We're thrilled with the support from partners and customers. And also too, like you said, the connections that people are making, so it does feel good that things are flowing and people are having conversations and- >> Well, you got healthcare, nonprofits, US government, healthcare has been a big focus so far in this show. A lot of action, local governments, governments and healthcare seem to be like pandemic enabled to change. What's the update? What's the highlights so far for you? >> Well, I think the highlights are in those areas that, what we've been able to help our customers with is the ability to respond and that's what Cloud is all about and their ability to react and to respond to things that they don't necessarily know is going to happen and the big thing that none of us knew was going to happen was the pandemic. And so that ability and agility and preparedness to respond has really been great to see from a lot of those customers. >> You know, Max Peterson had the CIO from the Air Force up on stage and she's known for her comments about data and data's our data, the US Air Force and so data's big part of it. They are having a transformation and the how's that project going? What's the update there? What's your impression on that? >> Yeah, well, it was great to see the Air Force on stage and great to see Laura up there and we're really proud to support the DOD and the Air Force. And the Air Force has a lot to be proud of in their transformation journey and what they're doing with Cloud One is pretty substantial and amazing transformation for them. And then they've got 35 applications running on AWS. And so we think their progress is really good and they're thinking the right way in terms of their software factories and other types of projects. >> What's interesting is it's watching like who's adopting, it's like you look at like the pandemic has really opened up the view of the projects, which ones are doing well. And how do I say this politely? The projects that were being blocked or hidden, or the KPIs camouflaging the value were exposed because I mean, once that pulled back the curtain, people realized, "Oh my God, we're stuck," Or "we're inadequate, we are antiquated. We need to change," because now the pressure to deliver shifted to digital. I mean, this literally exposed the good, bad, and the ugly. >> It did and some were more prepared than others. There are great examples. We worked with the SBA to help expand the portal for the payroll protection program to get more lenders access faster. And that was a great project. They were able to respond really quickly and we were able to support them in that. Others, not so much. I think it you're right, it did expose that there's an opportunity. There's an opportunity to accelerate some of the things that they were doing already in terms of digital transformation. >> How about the GovCloud and the federal customers that you have, what's the traction point? How has that going? Is there a new generation here? >> GovCloud has been a great success. GovCloud it's our- >> John: 10-year anniversary. >> It's our 10-year anniversary, so we're thrilled to celebrate that. I can't believe it's 2011. >> EC2 is 15. Is that 315? I guess 15, too is SQS, the original building blocks. >> So, we've got a lot of great success through GovCloud and GovCloud was really something that was born out of what customers wanted, primarily federal customers. But we've also seen over the last few years, real adoption from regulated industry, real adoption from partners that are going into GovCloud that really want to take advantage of the security and compliance that federal customers need and the larger defense industrial base organizations need. So, GovCloud's been a fabulous success and expect I expect a lot of growth going forward. >> Yeah, is there a cultural shift in the federal government now? I can imagine some countries have been exploring this. I did talk briefly about it with Ms. Shannon Kellogg and John Wood, about how, if you're under the age of 40 and you work in the federal government, you got to be like, "Why aren't we doing this?" Like there seems to be like a cultural shift, younger generation coming in and be like, looking at the old way and be like, "Why are we still doing that?" >> Well, I think look bipartisan support for digital transformation, for making sure that we have the competitive edge for generations and generations to come in the US both in business and in defense and national security, I think is an imperative. I mean nobody I've talked to disagrees that we need to do this. And I think that younger workforce coming in behind I'm jealous of the 40-year olds, I wish I was under 40, but none of workforce really sees the obstacles that maybe previous generation saw these emerging technologies are becoming, the basic unit of computer's getting smaller, the cost to do these things is coming way down and I think that younger workforce says, "Why aren't we doing this?" >> Yeah and I think the Air Force projects are interesting too because that shows us not just about the CIA or the DOD that you have, they're leaning into production workloads, and the mission critical workloads too, the DOD is also now continuing to adopt. What else are you guys doing with the DOD? >> Well, we're partnering with GDIT on milCloud and that's going to give DOD mission owners access to a whole suite of AWS services. So, we're really excited about that. And those are available now. We're the only Cloud provider that's making that accessible to them on milCloud. And so this is going to open up the opportunity for them to start doing that mission work that you described. A good example of that are programs like ABMS, Air Force's Advanced Battle Management System. It's part of their effort around JADC2 and a great set of capabilities that they're delivering there. We're happy to have participated. We did some testing and some show intel, if you will at Ramstein Air Force Base and we're really proud to support that effort and we're excited about what the Air Force is doing. >> You know, I've always been impressed with the DOD when the tactical edge concept came out, that was very impressive because they're really using the data properly and I know Amazon has been doing well in this area because you've got things like Outpost, Wavelength, Snowball products. How's that edge piece developing? Do you see that becoming more critical now? >> It's absolutely critical. It's not becoming critical, it is critical and I think if you look at what the DOD and all of their partners are trying to accomplish, it's really moving all of that data around from the very edge in theater, back home to where it needs to be analyzed, doing it fast, doing it secure, being able to deliver on their missions and that's what this is all about. So, we see huge, huge opportunities to really innovate around the edge. >> Yeah, the data equation really is fascinating to me. Just when you think about things like words, highly available versus high availability means something 'cause you're going to want real time, not just on available data, you got to have it real time so the pressure around these projects are high. And so technically, you've got to have low latency on all this stuff. >> That's true, that's true. You've got to either have near real time or real-time availability and in many cases there's high stakes. So, the ability the DOD to pull this off is really, really important and we're a big supporter of that. >> Dave, I want to get your perspective because you've been in the industry, you've seen that the ways, we talked before cameras about the '90s and data centers and stuff. 10 years of GovCloud, look at public sector, just to look at the 10 years, interesting evolution. I mean, you couldn't give Cloud a wait 15 years ago. They weren't moving, glacier speed of adoption, now, massive adoption, uptakes there, the transformations are happening, migrations are huge, healthcare, which is like silo the data, HIPAA compliance lock everything down, everything's opening up. This is causing a lot of change. What's your reaction to that? >> Well, my reaction to that is I think customers are starting to connect what their outcomes are, whether it's a business outcome or a mission outcome or both to what Cloud can actually do. And I think that's freeing them up to make decisions about enabling Cloud in their environment, enabling experimentation, because that's what you want. You don't know what you're going to be faced with. We don't know what the threats are. We don't know if there's going to be another major pandemic. We hope there's not, but we don't know and if you set goals around your outcomes for mission and tie those, Cloud becomes such an enabler for that. And I see customers embracing that. Customers across the spectrum, nonprofit, healthcare providers, everybody, Homeland Security, VA, they're all thinking about, "What are the mission outcomes we're trying to drive?" >> Yeah, what's interesting too on that is that, just to point out is that the applications now aren't as complex to build relatively to the speed. In other words, you can get the time to value. So, the pandemic showed people that if you were in the Cloud and had that agility or optionality to be agile, you could write software 'cause software is the key in this, and not let's do the waterfall, 12-weeks assessment, 10-month rollout. Now people are doing it in 10 days, new applications. >> Sure, sure. Well, I tell customers a lot, "Think about McDonald's during the pandemic and think about customers like that who had to react to a new environment of delivery and your fast food fresh and how quickly companies like that are able to roll out capabilities." And I don't know that federal customers will be able to do it in a week or two weeks, but it's certainly possible. And it certainly will shorten that lead time that they have now in their software development. >> Well, great to see you, Dave. Is there any customers you want to highlight and you want to talk about, get a plug in for? >> Yeah, a lot of great customers here representing today and we're really appreciative also just want to say it was really great to see Max on stage for his first summit and think it was great to see Laura and others as well too. We've got some great customers coming here, The Veteran's affairs is going to be here as well as the Navy presenting on a lot of their capabilities today. So, I'm really excited about that. >> Yeah, a lot of action and education, healthcare, really blooming, really changing and modernizing. Big-wave migration, modernization, all kinds of the big wave. >> Yeah, it is. Yeah, big things coming and some of these systems are ready, so these systems are 40 and 50 years old and we're here to help these customers deliver on the agility and the extensibility of these systems to really serve citizens. >> What's your outlook for next year? What are you seeing next year so happening? How do you see everything unfolding? So you mentioned the pandemic, we're still in it, Delta Virus, who knows what's going to happen next, the world stage is changing, the global economy, space. >> I see customers really leaning in and starting to see the benefits of moving their data to the Cloud, number one, and then also to getting the insights using AI and ML to really drive the insights that they need to make the decisions on that data and I see more and more customers doing that. I did a panel this week, moderated a panel with some great customers around that and getting started is probably the biggest thing that I see and we're going to have more and more customers getting started. >> Yeah, getting into the Cloud. Congratulations to milCloud by the way, too. That was a good call out. All right, thanks for coming, I appreciate it. >> John: Yeah, thanks, Sean. >> Okay, keep coverage here. The Public Sector Summit, live in Washington, D.C. in-person event also hybrid we're streaming out. We're doing remote interviews and Amazon is streaming all the keynotes and key sessions for the digital folks out there. Thanks for watching. (upbeat music)

(upbeat music) >> Narrator: From around the globe. It's theCUBE with digital coverage of IBM Think 2021. Brought to you by IBM. >> Welcome back to theCUBE coverage of IBM. Think 2021 virtual. I'm John Furrier, host of theCUBE. And this is theCUBE virtual and Uli Homann who's here Corporate Vice President, of cloud and AI at Microsoft. Thanks for coming on. I love this session, obviously, Microsoft one of the big clouds. Awesome. You guys partnering with IBM here at IBM Think. First of all, congratulations on all the success with Azure and just the transformation of IBM. I mean, Microsoft's Cloud has been phenomenal and hybrid is spinning perfectly into the vision of what enterprises want. And this has certainly been a great tailwind for everybody. So congratulations. So for first question, thanks for coming on and tell us the vision for hybrid cloud for Microsoft. It's almost like a perfect storm. >> Yeah. Thank you, John. I really appreciate you hosting me here and asking some great questions. We certainly appreciate it being part of IBM Think 2021 virtual. Although I do wish to see some people again, at some point. From our perspective, hybrid computing has always been part of the strategy that Microsoft as policed. We didn't think that public cloud was the answer to all questions. We always believed that there is multiple scenarios where either safety latency or other key capabilities impeded the usage of public cloud. Although we will see more public cloud scenarios with 5G and other capabilities coming along. Hybrid computing will still be something that is important. And Microsoft has been building capabilities on our own as a first party solution like Azure Stack and other capabilities. But we also partnering with VMware and others to effectively enable investment usage of capabilities that our clients have invested in to bring them forward into a cloud native application and compute model. So Microsoft is continuing investing in hybrid computing and we're taking more and more Azure capabilities and making them available in a hybrid scenario. For example, we took our entire database Stack SQL Server PostgreSQL and recently our Azure machine learning capabilities and make them available on a platform so that clients can run them where they need them in a factory in on-premise environment or in another cloud for example, because they trust the Microsoft investments in relational technology or machine learning. And we're also extending our management capabilities that Azure provides and make them available for Kubernetes virtual machine and other environments wherever they might run. So we believe that bringing Azure capabilities into our clients is important and taking also the capabilities that our clients are using into Azure and make it available so that they can manage them end to end is a key element of our strategy. >> Yeah. Thanks Uli for sharing that, I really appreciate that. You and I have been in this industry for a while. And you guys have a good view on this how Microsoft's got perspective riding the wave from the original computer industry. I remember during the client server days in the 80s, late 80s to early 90s the open systems interconnect was a big part of opening up the computer industry that was networking, internetworking and really created more lans and more connections for PCs, et cetera. And the world just went on from there. Similar now with hybrid cloud you're seeing that same kind of vibe. You seeing the same kind of alignment with distributed computing architectures for businesses where now you have, it's not just networking and plumbing and connecting lans and PCs and printers. It's connecting everything. It's almost kind of a whole another world but similar movie, if you will. So this is really going to be good for people who understand that market. IBM does, you guys do. Talk about the alignment between IBM and Microsoft in this new hybrid cloud space? It's really kind of now standardized but yet it's just now coming. >> Yeah. So again, fantastic question. So the way I think about this is first of all, Microsoft and IBM are philosophically very much aligned. We're both investing in key open source initiatives like the Cloud Native Computing Foundation, CNCF something that we both believe in. We are both partnering with the Red Hat organizations. So Red Hat forms a common bond if you still want to between Microsoft and IBM. And again, part of this is how can we establish a system of capabilities that every client has access to and then build on top of that stack. And again, IBM does this very well with their cloud packs which are coming out now with data and AI and others. And again, as I mentioned before we're investing in similar capabilities to make sure that core Azure functions are available on that CNCF cloud environment. So open source, open standards are key elements. And then you mentioned something critical which I believe is misunderstood but certainly not appreciated enough is, this is about connectivity between businesses. And so part of the power of the IBM perspective together with Microsoft is bringing together key business applications for healthcare, for retail, for manufacturing and really make them work together so that our clients that are critical scenarios get the support they need from both IBM as well as Microsoft on top of this common foundation of the CNCF and other open standards. >> It's interesting. I love that point. I'm going to double down and amplify that late and continue to bring it up. Connecting between businesses is one thread. But now people, because you have an edge, that's also industrial business but also people. People are participating in open source. People have wearables, people are connected. And also they're connecting with collaboration. So this kind of brings a whole 'nother architecture which I want to get into the solutions with you on on how you see that playing out. But first I know, you're a veteran with Microsoft for many, many years of decades. Microsoft's core competency has been ecosystems developer ecosystems, customer ecosystems. Today, that the services motion is built around ecosystems. You guys have that playbook IBM's well versed in it as well. How does that impact your partnerships, your solutions and how you deal with down this open marketplace? >> Well, let's start with the obvious. Obviously Microsoft and IBM will work together in common ecosystem. Again, I'm going to reference the CNCF again as the foundation for a lot of these initiatives. But then we're also working together in the ed hat ecosystem because Red Hat has built an ecosystem and Microsoft and IBM are players in that ecosystem. However, we also are looking a higher level there's a lot of times when people think ecosystems it's fairly low level technology. But Microsoft and IBM are talking about partnerships that are focused on industry scenarios. Again retail, for example, or healthcare and others where we're building on top of these lower level ecosystem capabilities and then bringing together the solution scenarios where the strength of IBM capabilities is coupled with Microsoft capabilities to drive this very famous one plus one equals three. And then the other piece that I think we both agree on is the open source ecosystem for software development and software development collaboration and GitHub is a common anchor that we both believe can feed the world's economy with respect to the software solutions that are needed to really bring the capabilities forward, help improve the wealth economy and so forth by effectively bringing together brilliant minds across the ecosystem. And again, just Microsoft and IBM bringing some people but the rest of the world obviously participating in that as well. So thinking again, open source, open standards and then industry specific collaboration and capabilities being a key part. You mentioned people. We certainly believe that people play a key role in software developers and the get hub notion being a key one. But there are others where, again, Microsoft with Microsoft 365 has a lot of capabilities in connecting people within the organization and across organizations. And while we're using zoom here, a lot of people are utilizing teams because teams is on the one side of collaboration platform. But on the other side is also an application host. And so bringing together people collaboration supported and powered by applications from IBM from Microsoft and others is going to be, I think a huge differentiation in terms of how people interact with software in the future. >> Yeah, and I think that whole joint development is a big part of this new people equation where it's not just partnering in market, it's also at the tech and you got open source and just phenomenal innovation, a formula there. So let's ask what solutions here. I want to get into some of the top solutions you're doing with Microsoft and maybe with IBM, but your title is corporate vice president of cloud and AI come on, cause you get a better department. I mean, more relevant than that. I mean, it's exciting. Your cloud-scale is driving tons of innovation. AI is eating software, changing the software paradigm. We can see that playing out. I've done dozens of interviews just in this past month on how AI is more certainly with machine learning and having a control plane with data, changing the game. So tell us what are the hot solutions for hybrid cloud? And why is this a different ball game than say public cloud? >> Well, so first of all let's talk a little bit about the AI capabilities and data because I think there are two categories. You're seeing an evolution of AI capabilities that are coming out. And again, I just read IBM's announcement about integrating the cloud pack with IBM Satellite. I think that's a key capability that IBM is putting out there and we're partnering with IBM in two directions there. Making it run very well on Azure with our Red Hat partners. But on the other side, also thinking through how we can optimize the experience for clients that choose Azure as their platform and IBM cloud Pak for data and AI as their technology, but that's a technology play. And then the next layer up is again, IBM has done a fantastic job to build AI capabilities that are relevant for industries. Healthcare being a very good example. Again, retail being another one. And I believe Microsoft and IBM will work on both partnerships on the technology side as well as the AI usage in specific verticals. Microsoft is doing similar things within our dynamics product line. We're using AI for business applications for planning, scheduling, optimizations, risk assessments those kinds of scenarios. And of course we're using those in the Microsoft 365 environment as well. I always joke that despite my 30 years at Microsoft, I still don't know how to read or use PowerPoint. And I can't do a PowerPoint slide for the life of me but with a new designer, I can actually get help from the system to make beautiful PowerPoint happen. So bringing AI into real life usage I think is the key part. The hybrid scenario is critical here as well. And especially when you start to think about real life scenarios, like safety, worker safety in a critical environment, freshness of product we're seeing retailers deploying cameras and AI inside the retail stores to effectively make sure that the shelves are stocked. That the quality of the vegetables for example, continues to be high and monitored. And previously people would do this on a occasional basis running around in the store. Now the store is monitored 24/7 and people get notified when things need fixing. Another really cool scenario set, is quality. We're working with a finished steel producer that effectively is looking at the stainless steel as it's being produced. And they have cameras on this steel that look at specific marks. And if these marks show up, then they know that the stainless steel will be bad. And I don't know if you've looked at a manufacturing process, but the earlier they can get a failure detected the better it is because they can most likely or more often than not return the product back into the beginning of the funnel and start over. And that's what they're using. So you can see molten steel, logically speaking with a camera and AI. And previously humans did this which is obviously a less reliable and be dangerous because this is very, very hot. This is very blowing steel. And so increasing safety while at the same time, improving the quality is something that we see hybrid scenarios. Again, autonomous driving, another great scenario where perception AI is going to be utilized. So there's a bunch of capabilities out there that really are hybrid in nature and will help us move forward with key scenarios, safety, quality and autonomous behaviors like driving and so forth. >> Uli, great insight, great product vision great alignment with IBM's hybrid cloud space with all customers are looking for now and certainly multi-cloud around the horizon. So great to have you on, great agility and congratulations for your continued success. You got great area cloud and AI and we'll be keeping in touch. I'd love to do a deep dive sometime. Thanks for coming on. >> John, thank you very much for the invitation and great questions. Great interview. Love it. Appreciate it. >> Okay, CUBE coverage here at IBM Think 2021 virtual. I'm John Furrier, your host. Thanks for watching. (upbeat music)

(upbeat music) >> Narrator: Live from Las Vegas, it's theCube. Covering AWS re:Invent 2019 brought to you by Amazon Web Services and Intel, along with it's ecosystem partners. >> Hello there and welcome back to theCube's live coverage here in Las Vegas for AWS re:Invent 2019. This is theCube's seventh year covering re:Invent. They've been doing this show for eight years, we missed the first year, I'm John Furr, and my co-host David Vellante. We're here extracting the signal from the noise, and we're here with an amazing guest, our friend, she's been here with us from the beginning of theCube, since inception. Always great to get to comment with her. Sandy Carter Vice President with Amazon Web Services. >> Thank you. >> Now in the public sector handling partners. Great to see you, thanks for coming on again and sharing your content. >> So great to see you guys, so dressed up and looking good guys, I have to say. (laughs) >> You're looking good to, but I can't help but stare at our other guest here, the IoT suitcase. >> First, tell us-- >> Yes. >> About the IoT suitcase. >> Well we, in public sector we have a partner program, and that program helps entrepreneurs. And we're really keen on especially helping female entrepreneurs. So one of our entrepreneurs created this suitcase, that's an IoT based suitcase, you can put your logo's and that sort of thing on it, but more importantly for public sectors, she created this safety ring, John. And so, if I touch it I've de-activated it, but if I touch it, it will call the police for me, if I'm being assaulted. Or if I'm having an emergency, I can touch it and have an ambulance come for me as well. And the really cool thing about it is she worked backwards from the customer, figuring out like how are most people assaulted, and if you have an emergency and you fall, what's the best way to get ahold of someone. It's not your phone, because you don't always carry it, it's for a device like this. >> Or a bigger device that you can't, or you leave on the table somewhere, but that's you know it's attractive. >> It's awesome. >> And it's boom, simple. >> And it's pink. (laughs) >> What I love fast about re:Invent as an event is that there's so much innovation going on, but one of the areas that's become modernized very rapidly is the public sector. Your now in this area, there's a lot of partners, a huge ecosystem going, and the modernization effort is real. >> It is. >> Could you share some commentary on what's going on. Give people a feel for the pace of change, what's accelerating? What are people doubling down on, what are some of the dynamics in public sector? >> Yeah, so if you know public sector, public sector actually has a lot of Windows or Microsoft workloads in it. And so we're seeing a lot of public sector customers looking to modernize their Windows workloads, in fact we made several announcements just yesterday around helping more public sector customers modernize. For example, one is Windows Servers 2003, and 2008 will go out of support, and so we have a great new offering, with technology, that can help them to not re-factor, but actually abstract those layers and move quickly to 2016 and 2019, because both of those will go out of support in January. >> A lot of people don't know, and I've learned this from talking with Andy Jassy in the keynote, as well as hearing from some other folks, is that you got, Amazon runs a lot of Windows. >> Oh, we have 57% Windows workloads on AWS in terms of market segment share. Which is 2x the next nearest cloud provider, 2x. And most customers choose to run their Windows workloads on us, because we are so innovative, we move really fast. We're more reliable. The latest public data from 2018 shows that the nearest cloud provider had seven times more downtime. So if your in public sector or even commercial, who can afford to be down that long, and then finally, we have better security. So one of the things we've been focused on for public sector is FedRamp solutions. We know have over 90 solutions that are FedRamp ready. Which is four times more than the next two cloud providers. Four times more than the two combined. >> That's interesting, so I got to ask the question that's popping up in my mind, I'm sure people are curious about. >> Yeah. >> I get the Windows working on Amazon, and that makes a lot of sense, why wouldn't you want to run on the best cloud. The question I would have is, how would the licensing work, because, that's seems to be lock-in spec, Oracle does it, Microsoft does it, does license become the lock-in. So, when something expires, what happens on the licensing side. Licensing is really tricky, and in fact, October 1st, Microsoft made some new licensing changes. And so, we have some announcement to help our customers still bring their own licenses, or what we call fondly, BYOL over to AWS, so they don't have to double invest on the license. >> So you can honor that license on AWS. >> Yeah, and you have to do it on a dedicated host. Which at midnight madness, we announced new dedicated host solution, that's very cloud-like. Makes it as easy to run a dedicated host instance as it is an EC2 instance. So, wicked easy, very cost effective if your moving those on-premises workloads over. >> I just want to point out John, something that's really important here is a lot of times, software companies will use scare tactics, to your point. They'll jack up the cost of the license, to say, ah you got to stay with us, if you run on our hardware or our platform, you pay half. And then they'll put out, "Oh, Amazon's twice as expensive." But these are all negotiable. I've talked to a number of customers, particularly on the Oracle side, and said, no, no, we just went to Oracle and said look, you got a choice, I either give us the same license price or we're migrating off your database. Okay, all right. But some of it is scare tactics, and I think you know increasingly, that's not working in the marketplace. So I just wanted to point that out. >> So what's the strategy for customers to take, I guess that's the question. Because, certainly the licensing becomes again like they get squeezed, I can see that. But what do customers do, is there a playbook? >> Well there is, and so the best one is you buy your license from Microsoft, and then using BYOL, you can bring that over to AWS. It's faster, more performance, more reliable, that sort of thing. If you do get restricted though John, like they are doing for instance with their end of support, you could run that on Azure, and get all the security fixes. We are trying to provide technical solutions, like the ability to abstract Windows Server 2003 and Server 2008 as it goes out of support. >> I mean certainly in the case of Oracle, it used to be you know 10-15 years ago, you didn't have a choice. Instead of one RDBMS, and now it's so much optionality in databases. >> And I will also tell you that we have a lot of customers today, who are migrating from SQL server, or Oracle over to Aurora. Aurora, is equally as performant, and a tenth of the cost. So we actually have this team called the database freedom team that will help you do that migration. In fact I was talking to a very large customer last night, and I was explaining some of the options. And their like, "Let's do the Aurora thing." Let's do it two-step. Let's start by migrating the database over, Oracle and SQL and then I want to go to Aurora. It's like database built for the cloud, it's faster and its cheaper. So why wouldn't you do that? >> Yeah, and I think the key is, to my question about a friction. What's frictionless? How can they get it done quickly without going through the trip-wires of the licensing. >> Certain workloads are tough, right. You know if you're running your business on high transaction volume. But a lot of the analytics stuff, the data warehouse, you know look at Amazon's own experiences. You guys are just ticking it off, moving over from Oracle to Aurora, it's been fun to watch. >> I want to get you guy's perspective Dave, you and Sandy, because I think you guys might have good insight on this, because everyone knows that I'm really passionate about public sector, I've been really enamored with Teresa's business from Day one, but when she won the CIA deal, that really got my attention. As I dug into the Jedi deal, and that all went sideways, it really jumped out at me, that public sector is probably the most transformative market, because they are modernizing at a record pace. I mean this is like a glacier moving market. They don't really have old ways, they got the beltway bandits, they got old procurement, old technology, and like literally in a short period of time, they have to modernize. So they're becoming more enterprise like, can you guys, I mean pros in the enterprise, what's your take? It just seems like a Tsunami of change in the public sector, because the technology is driving it. What do you guys think about this? Am I on or off base? What are some of the trends that are going on? >> I mean I have a perspective, but please. >> No, okay. So I'll start. So I see so much transformation regardless of what industry your looking at. If you're looking at Government for example working with SAP NS2, we just actually took 26 different flavors of SAP ERP for the Navy, and helped them to migrate to the cloud. For the US Navy, which is awesome. Arkis Global, did the same thing for the UK. We actually have Amazon Connect in there, so that's like a cool call center driven by Machine Learning, and the health care system for the UK. Or you can even look at things, like here in the U.S. there's a company that really looks at how you do monitoring for the children to keep them safe. They've partnered up with a National Police Association, and they are bringing that to the cloud. So regardless of education, non-profits, government, and it's around the world, it's not just the US. We are seeing these governments education, start-ups, non-profits, all moving to the cloud, and taking their own legacy systems to Linux, to Aurora, and moving very rapidly. >> And I think Andy hit on it yesterday, it's got to start with top-down leadership. And in the government, if you can get somebody whose a leading thinker, CIO, we're going cloud first. Mandate cloud, you know you saw that years ago, but today, I think it's becoming more mainstream. I think the one big challenge is obviously the disruption in defense and that's why you talked about Jedi, in defense it's very high risk, and it needs disruption, it's like healthcare its like certain parts of financial services are very high risk industries, so they need leadership, and they need the best platform underneath in a long term strategy. >> Well Jedi actually went different. It was actually the right call, but I reported on that. But I think that what gets me is that Cerner on stage yesterday, on Yaney's keynote highlights that it's just not inefficiencies that you can solve, there's multiple win-win-win benefits so in that health care example, lower the costs, better care, better, the providers are in better shape, so in government in public sector, there's really no excuse to take the slack out of the system. >> Yeah. >> Well, there's regulation though. >> Yeah, and Dave mentioned cloud first strategies, we're also seeing a lot of movement around data. You know data is really powerful. Andy mentioned this as well yesterday, but for example in our partner keynote where I just came from. We had on stage Avis. Now, Avis, not public sector customer, but what they're doing is, the gentleman said, was that your car can now talk to you, and that data is now being given to local state officials, local city officials, they can use it for emergency response systems. So that public and private use of data, coming together, is also a big trend that we're seeing. >> I think that's a great example, because Avis I think what he said is a 70 year old company, I think the fleet was 18 billion dollar fleet. >> 600,000 vehicles. >> 600,000 vehicles, 18 billion dollars worth of assets, this is not a born in the cloud start-up, right. That's essentially transformed the entire fleet and made it intelligent. >> Right, and using data to drive a lot of their changes. Like the way they manage fuel for 600,000 cars, and the way they exchange that with local officials is helping them to you know not just be number two, but to start to take over number one. >> But to your point, data is at the core, right. >> Yeah. >> If you are the incumbent and you want to transform, you got to start with the data. >> Sandy, I want to get your reaction to two memes that have been developing on theCube this week. One is, if you take the T out of Cloud Native, and it's Cloud Naive. (Sandy laughs) The other one is, if your born in the cloud, that's great, your winning, but at the price of becoming re-born in the cloud. This is the transformation. Some are, and they're going to not have a long shelf life. So there's a real enterprise and now public sector re-birth, re-borning in the cloud, the new awakening. This is something that is happening. You're an industry veteran, you've seen a lot of waves, what's the re-born, what's this getting back on the cloud, really happening. What is going on? >> It's really interesting, because now I'm in the partner business, and one of our most successful programs is called our partner transformation program. And what that does, is it's a hundred day transformation program to get our partners drinking our own champagne, which is to be on the cloud. And one of the things, we know we first started testing it out, we didn't have a lot of takers, but now, those partners who have gone through that transformation, they're seeing 70% year to year growth, versus other apion partners, even though they're at an advanced layer, they're only seeing 34% growth. So its 2x of revenue growth having transformed to the cloud. So I think, you know back to your question, I think some of this showing the power. Like, why do you go to the cloud, it's not just about cost, it's about agility, it's about innovation, it's about that revenue growth, right. I mean 2x, 70% growth, you can't sneeze at that. That's pretty impactful. >> And you know this really hits, something of passion for me and Dave and our team is the impact on a society. This is a real focus across all generations now, not just millennials, and born in the web, into older folks like us, who have seen before the web. There's real impact, mission driven things. This is a check for good, shaping technology for good. Educate you guys have. This is a big part of what you guys are doing. >> Absolutely, this is one of the reasons why I really wanted to come work in the public sector, because it's fun helping customers make money, and we still do that. But it's really better, when you can help them make money and do great things. So you know, making with the Mayo clinic, for example, and some of these non-profit hospitals, so they can get better data. The GE example that Andy used yesterday, that data is used in public sector. Doing things, like, I know that you guys are part of re-powered tech. You know we brought a 112 unrepresented minorities and women to the conference. And I have to tell you I got goosebumps when one person came up to me and he said, it's the first time he stayed in a hotel, and he's coming here to enhance his coding. You don't realize when I go back to my country, you will have changed my life. And that's just like, don't you get goosebumps from that, versus it's great to change a company, and we want to do that, but it's really great when you can impact people, and that form or fashion. >> And the agility makes that happen faster, its a communal activity, tech for good is here. >> Absolutely, and we just announced today, right before this in the partner's session, that we now have the public safety and disaster response competency for our partners. Because when a customer is dealing with some sort of disaster or emergency they need a disconnected environment for a long periods of time. They need a cloud solution to rally the troops. So we announced that, and we had 17 partners step up immediately to sign up for that. And again, that's all about, giving back, helping in emergency situations, whether it's Ebola in Africa or Hurricane Dorene, right. >> Well, Sandy congratulations, not only have you a senior leader for AWS doing a great job. >> Thank you. >> Just a great passion, and Women in Tech, Underabridged Minorities, you do an amazing job on Tech for Good. >> Thank you. Well it's such an honor to always be on the show. I love what you guys do. I love the memes, I'm going to steal them, okay. >> Can I ask you another question? >> Absolutely. >> Before you wrap. You've had an opportunity to work with developers, you've experienced other clouds. Now you're with AWS and a couple of different roles. Can you describe, what's different about AWS, is it cultural, is it the innovation, I mean what's tangible that you can share with our audience in terms of the difference. >> I think it's a couple of things, the first one the way they we hire. So we hire builders, and you know what it really starts from that hiring. I actually interviewed Vernor the other day, and he and I had a debate about can you transform a company where you have all the same people, or do you need to bring in some new talent as well. So I think it's the way we hire. We search for people that not only meet the leadership criteria, but also are builders, are innovators. And the second one is, you know when Andy says we're customer obsessed, we're partnered obsessed. We really are. We have the mechanisms in place, we have the product management discipline. We have the process to learn from customers. So my first service I launched at AWS, I personally talked to 141 customers and another 100 partners. So think about that, that's almost two hundred almost fifty customers and partners. And at most large companies, as a senior executive you only spend about 20% of your time with customers, I spent about 80% of my time here with customers and partners. And that's a big difference. >> Well we look forward to covering the partner network this year. >> Awesome >> Your amazing, we'll see Teresa Carson on theCube here at 3:30. We are going to ask her some tough questions. What should we ask Teresa? >> What to jest Teresa? Where did you get those red pants? (everyone laughs) >> She's amazing, and again. >> She is amazing. >> We totally believe in what you're doing, and we love the impact, not only the technology advancement for modernizing the public sector across the board. But there's real opportunity for the industry to make, shape technology for betterment. >> Yeah. >> You're doing a great job. Thank you so much. >> Thank you. I think we should start another hashtag for theCube too, is #technologyforgood. >> Awesome. >> What do you think? >> Let's do it. >> I love that. >> But Jonathan been doing a lot of work in that area. >> I know he has. >> We love that. #technologyforgood, #techforgood. This is theCube here live in Las Vegas for re:Invent. I want to thank Intel and AWS, this is the big stage. We had two stages, without sponsoring our mission we wouldn't be here. Thank you AWS and Intel. More coverage after this short break. (dramatic music)