(upbeat music) >> Good afternoon everyone. Welcome back to The Cube's live coverage of AWS Reinvent 22 from Vegas. We're at the Venetian Expo Hall, we're hearing north of 50 000 people. I know we've been giving you different numbers but that's kind of what we've settled on here. Hundreds of thousands are watching online. This is a huge event people. John Ferrior and Lisa Martin are ready to be back. >> Yes, it's really great show. A lot of change going on at Amazon. They're continuing the innovation, continuing to grow. The theme this year's Data Security. And their partner ecosystem, which is continuing to grow. Their partners are filling the gaps on solutions. And it's just a whole nother, I think partner friendly cloud. This NextGen wave that's coming is really, the next thing segment I think speaks to that, I'm looking forward to this. >> It does. We're going to be digging into that partner network. We've got two guests, one of them is an alumni, Reza Honarmand SVP Global Cloud at TD Synnex. Great to have you back. >> Yeah. >> Sergio Farache joins us as well the Chief Strategy Officer at TD Synnex. Welcome to the program. >> Thank you. >> Thank you for having us. >> Great to be back in person, isn't it? >> Yeah absolutely. That's great experience. >> Amazing, the energy here at the highest level since we came here Monday night, which is great. Sergio, I want to start with you. Last year when you guys were on the show Tech Data. Tech Data has been around a long time now you're TD Synnex. Talk a little bit about that, what's new, that transformation? >> Yeah, that is correct. It's great to be able now to present it in Synnex as a new merger between Tech Data and Synnex Corporation. And now we are the largest distributor basically across the world with more than $62 billion in a business. And Amazon is obviously an strategic partner with a hyper growth and we have been very focused to working with them to expand that partner ecosystem across solution ISVs and service providers. That has been very nice experience combine these two company and now have the reach and skill that enable more than 140,000 partners across the world. >> Wow. >> And the partner's message here is changing too. The new leader, Ruba is up on stage talking about this new partner paths, a lot of changes in a good way. They're bringing people together. What's your guys take and reaction to AWS's new posture towards partners? Obviously the ecosystem we see going to be doubling and tripling we see in size. And also the value proposition being stronger too and more money making of course. But the new Amazon's posture with partners. What's your reaction? >> Well, (indistinct) just an hour ago. Fantastic. I mean, if I look at the change from when we first got here a few years ago to now, it is beyond comparison. The realization is that technology and especially what we work with Amazon is deflationary force and we need scale to actually drive that across all of our partners to the customers. And yeah, I can only see that accelerating now in terms of what Amazon is doing and actually with the channel and what Ruba is doing. I think this is exactly in the right direction. >> What's your message? >> My message is, this is now channel. This is channel and this is serious. So partners with Amazon equals growth. >> As we've seen so much transformation in the last couple of years, Sergio, with every business having to become digital to survive. Right and then to eventually thrive and succeed and grow in the challenging economic times that we've had. What are some of the, the pivots that TD Synnex has made through your partner program to meet customer needs to accelerate their transformation? >> Yeah, as you said, has been a significant transformation. I think that in the past was clear what was a technology company and what industrial company, et cetera and those frontiers are blending right now. Then as a consequence we have been investing in several elements. Once is to really increase the capability of the partner network in a way that they can on one side provide more solution-oriented activities to those customers to drive either growth or cost optimization. The other element has been verticalization meaning know the industry where you are playing. We have been investing in the healthcare market, of course as a consequence of all the demand that has been generating. But at the same time and we recently announced the competence in the government sector where we expand drastically our capabilities around specifically the federal, and non feral business, but not only in US but across the world with those elements. Then I would say it's a combination of enhancing the skill, enhancing the knowledge on the industry, and finally provide the tools through our platform to enable the partner to operate in a digital way and enable the access of ISVs to digitally and serving the customers end to end. >> Is that the ISV experience project that I heard about? ISV experience with SaaS companies, Is that what you're referring to? >> Yeah, ISVs is one. ISP experience is one of the components that we use, but basically what we are trying to achieve with the ISV is helping in the journey of specification. It's how you transform either a partner that is born in the cloud or a partner that is still in the, in the OnPrem side how you transition to the cloud and enabling how you reach to the end user in a more effective way. And how we expose 140,000 partner across the multiple geographies to help those ISVs to reach more customers. >> It's great distribution. I mean this is, a business model innovation. >> Sorry? >> It's a business model innovation for these ISVs. >> Absolutely. Some of the ISVs, as you can imagine they're incumbent with us. We work with them. So actually it's finding new ways of consuming technology. But there's thousands of them that actually do not understand how to operate with a channel. And this is a part where we help them with the channel, build a program. Coach them through the process, help them access the partners and the customers that Sergio was referring to. >> Let me ask you guys a question. Where's the growth going to come from? I mean you mentioned ecosystem, more growth, Ruba was mentioned that's where the growth is. They are serious. She's going to deliver that keynote now. Where do you guys see your growth coming from? >> Well, to be honest the growth is unlimited in our opinion, right. It's so many areas. >> The wave is still coming. Yeah >> The wave is still there, you know. When you see still the amount of platform that need to be immigrated to the cloud then we have been investing in a significant way in enable capabilities of migration programs from the on-premise to off premise. At the same time, we have been expanding geographically because it's still several segments and markets we operate globally. As an example we recently launched our public sector capability in Latin America and Europe, expanding those segments. And in addition to that again, how we bring more ISVs more solution oriented driven than many spots of growth. And I think that Amazon message recently recognized more and more the value of nobody have all the solutions. You need this ecosystem plan together to bring those solutions to market. >> So if I build on that. If we look at the growth in public cloud last year, was around $40 billion. We expect a similar growth level this year as well. I mentioned about deflationary force, the technology being a deflationary force. Now everybody knows a lot of businesses out there are going under a lot of challenges. So they have to compete, they have to have the insights they have to be efficient and actually they're going to get a lot of that through the technologies that we're talking about here. The key to that is partners with the right skillsets. What we are seeing is the partners with the skillsets who can participate in that $40 billion growth, take a big, big share of it. >> And you guys are providing a great service. I think when I wrote the story on Friday that I published one of my premise was, is that this Next-Gen cloud is going to lift up more ISVs which is kind of a legacy classic, independent software vendor. Create new kinds of partners that have platforms or unique solutions for verticals. So, the ISV classic definition will still exist and new customers are emerging. It's got a new dynamic developing. We're seeing people build clouds on top of the cloud tap the ecosystem, partner distribution, services. It's a whole new way to build and take something to market. What do you guys think about that? >> Yeah, I think that the beauty of our position in the market is that we are in the center of that ecosystem. Again, we have access to thousands of ISVs thousands of hardware vendors, the hyper-scalers then somebody need to put all those pieces together. That is our role in the market. >> It's a good position to be in. >> It's a good place to be. And enabling those partners now to collaborate with all those entities to bring the solution because the customer is not acquiring technology anymore. They're acquiring a solution to a problem now. And that solution require multiple components. >> Last year. No, this year, I'm sorry. You guys were announced as EMEA distributor of the, of the year. Congratulations on that. >> Yeah, thank you. Talk about that in terms of just the evolution of the partnership. >> The partnership in EMEA is now across our entire geo. The growth that we have driven across the EMEA market space, is I think the reason why we have won it. As well as the competencies that we have built. Now you were just talking about ISVs to give you an example, there are many ISVs that sit in EMEA that want to access the US market and vice versa. So where we sit in the middle and enable that access. The frameworks that they need to move. So those are the kind of things that contribute to the strengthened in the relationship and what those awards are coming from. >> Yeah. The other critical factor here is, again how we bring more capillarity in terms of the serve to the market to Amazon. And that has been another component of data that we are very thankful. Again, we has been enabling and bringing numerous new partners and numerous new end customers that now have access, support and services. Including again, the competencies that we already described but including service oriented businesses like migration, like cost optimization of the use, et cetera. That now we through partners serve to the market. >> Reza and Sergio, I want ask you guys a question around trust. Trust. You're a trust broker because you have a lot of services and people and companies to put together. We were just talking about the good position you're in. >> Trust is a big part of your relationship with your customers. You've got two sides of your business, you got one side's the supply side and you got the distribution side and then both sides are working together, requires a lot of trust. What's that look like inside your company? Can you just chip in and explain, take a bit to explain what's that like? The culture of the company and that trust. >> Yeah, absolutely. And that is why the term of trust advisor came to the table right? And again, for more than 40 years we have been building this ecosystem. We have been driving that motion and we have been proving to the market a consistent approach with a strong support to the two tier model. We never, you know get in opposition to our customers and we enable those customers in a consistent way. And I think that trust is something that you earn, not something that you ask for. And that is what we are doing day to day basis. >> Congratulations, it's been great. Great chatting with you. Challenge time? For the challenge time? >> Challenge time. >> Alright guys. >> New challenge on the Cuba new format. We usually say yes at the end of the interview. What's take on the show, what's the bumper sticker? So think of it like an Instagram reel, thought leadership, hot take. Each of you, spend a minute 30 seconds to share a hot take, thought leadership, what you think was going on at Amazon? Why you're here? What's important? What would you say if you were going to do an Instagram reel right now? >> Yeah, the Amazon enable a new way to do business and a new transformation of the digital economy. We are here TD Synnex to expand that capability across the segments. Enhancing partners to reach to their goals and in users to get those transformations. In general we will provide what is needed and we continue investing to continue growing the capacity across all geographies and all the type of solutions that we deliver. >> All right, Sergio you nailed it. Reza you're up. Your hot take your sizzle reel. >> Well, frankly I think Sergio nailed it. It's about covering the geos and taking the competencies and make sure we execute consistently across all of our geos. >> All right, nailed it. Thanks so much. >> Consistent execution. Reza, Sergio. Thank you so much for joining John and me on the program, talking about what TD Synnex has done since we've last seen you. What you're doing with AWS and the partner ecosystem. We really appreciate you stopping by this side. >> Thank you very much. Thank you for the time. >> Alright, our pleasure. For our guests and for John Furrier, I'm Lisa Martin. You're watching theCUBE, the leader at Live Tech coverage.

>>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 all going? Making it super multi-Cloud is around the corner and public cloud is winning at the private cloud on premise and edge. Got a great guest here, Vascar go, D 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 thing about what you guys are doing a 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, >>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 to run the infrastructure. The biggest blocking factor now is having a unified platform. And that's what where we come into >>Patrick, we were talking before we came on stage here about your background and we were kind of talking about the glory days in 2000, 2001 when the first ASPs application service providers came out. Kind of a SaaS vibe, but that was kind of all kind of cloud-like >>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, >>In fact, you know, as we were talking offline, I was in one of those asbs 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, have been pumping on all cylinders as an economic input. And if you look at the tech trends, GDPs down, but not tech. Nope. Because 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 >>E Everyone, every company, regardless of size, regardless of location, has to become modernize their infrastructure. And modernizing infrastructure is not just some, you know, 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, Alan and I want to do with Super Cloud and calling at 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 the 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. >>I, 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? But they're not connected. So you can say okay, it's more than one cloud. So it's you know, multi-cloud. But Supercloud 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, 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 pane, 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, 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 in the journey is going on and you know, most companies are, 70 plus percent of them have 1, 2, 3 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 it, the beauty of it is yes, open source, but the biggest gating factor is the skillset. 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. There 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 on-prem 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 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. >>And what benefits are they seeing? Are they seeing speed? >>Speed, definitely. Okay. Definitely their 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 heard it all here, ops and security teams. Cause they're kind of two part of one thing, but ops and great specifically need to catch up. Speedwise, 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, >>So you were just two sides to that coin. You've got the dev side and then >>And the infrastructure >>Side. Okay, >>Another customer, I 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 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 rack in the store or they can't move everything to the cloud because the store operations have to be local. The menu changes based on it's classic edge. >>It's >>Classic edge, yeah. Right? They can't send it people to go install rack of 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 say little service, like how big one like a box, like a small little >>Box, right? 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. Yeah, 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 plugin >>Play two plugin 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 >>Youcar, of course Detroit's >>Coming in, so, so it's already there, right? 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, not 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 lot of our customers in that journey. Now everybody wants to be cloud native, 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 you use. Okay? So, so I think the complexities there, but the business benefits of agility and uniformity and customer experience are truly being done. >>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 Domino's 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, they were the pioneer in it. To me, those are the kinds of customer experiences that cloud native can provide. >>Being agility and having that flow through the application changes what the expectations >>Are >>For the customer. >>Customer, the customer's expectations change, right? Once you get used to a better customer experience, you will not, >>Thats got 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 in 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 of 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, 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, being at an asb, being 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 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, couple of parallels come to me. One is, think of it, which was forced to on us, 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 cloud native. You know, that is what I see >>Happening there. I think that that e-commerce is 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 then made you an e-commerce or e retailer or 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. >>Nascar, thank you for coming on. Spend 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.

>>Everyone, 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 Furry, your host of The Cube. We've got a great lineup of three interviews we're streaming today. Mattor Makki, 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 cloud native at scale. So enjoy the program, see you soon. Hello and welcome to the cube here in Palo Alto, California for a special program on cloud native at scale, enabling next generation cloud or super cloud for modern application cloud native developers. I'm John Forry, host of the Cube. Pleasure to have here me Makowski, 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 and 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 distributors 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 micro sites. These micro sites 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 super cloud is a, is an appropriate term for >>That. So you brought a couple things I want to dig into. You mentioned Edge Notes. 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, o ot, and it kind of coming together, but you also got this idea of regions, global infrastructures, big part of it. I just saw some news around cloud flare 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 it's something business consequences as well, but there are technical challenge. Can you share your view on what the technical challenges are for the super cloud 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 number of clusters in the Kubernetes space. And then on the other access 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 skill 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, 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 change, 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's 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 at 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 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 configure 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 hotpot is. And 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, the two factors of scale is 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 try us, right? And so in the Kubernetes environment, this problem kind of multi folds, it goes, you know, escalates to a higher degree because yeah, 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 you radio sell 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 it, 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 like ishly 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 our lawn is, this new product, What is it all about? Talk about this new introduction. >>Yeah, absolutely. I'm 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 arwan 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 sites of those clusters, security policies, your middleware plugins, and finally your applications. So what alarm lets 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 this solves 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 online. 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, 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 components, 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 I 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. C C I CD 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, the developers are responsible for one picture of that layer, which is my apps, and then maybe that middleware of application 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 native developer. The OP 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, Kubernetes really in introduced or elevated this declarative management, right? Because, you know, c communities clusters are Yeah. Or your, yeah, you know, specifications of components that go in Kubernetes are defined in 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 online addresses that problem at the heart of it, and it does that using existing open source well known solutions. >>Ed, do I wanna 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 on from 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 fi, 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 opensource 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. I mean, 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, 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, Well, 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 helpers to try before they buy, but also actually kind of date the application, if you will. We, you know, Adrian Karo uses the dating me 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, why should I be enthused about Arlo? 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 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 es, and then we have our C I CD 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 CD pipelines can deploy the apps. Somebody needs to do all of their 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 Spico would be delighted. The folks that we've talked, 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 s 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 >>Stability. 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 Lon uses Argo cd, which is probably one of the highest rated and used CD open source tools that's out there, right? It's created by folks that are as part of Intuit team now, you know, really brilliant team. And it's used at scale across enterprises. That's one. Second is arlon also makes use of cluster api capi, which is a ES 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 algo cd. Now Arlan just extends the scope of what Algo CD 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 nine has a role to play, which is when you are ready to deploy Alon 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 Arlo? What's been some of the feedback? >>Yeah, I, 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 CD and 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 line 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 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 customer's 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, >>So 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 Yeah. 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 >>Profile and policy based declarative configuration and life cycle management for clusters. >>If I asked you how this enables Super club, 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 alon 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, alarm flows >>In one. Okay, so now the next level is, Okay, that makes sense. There's 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 Arlo solution takes place, as you say, and the apps are gonna be stupid, there's 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, and on 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 in 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, 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 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, 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, 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 IIA terminals and some PCs and handhelds. Now if technology's running, the business is the business. Yeah. The 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 see, and boards is saying, how is technology driving the top line revenue? That's the number one conversation. Yeah. 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 with things. So just >>Taking care of, and the CIO doesn't exist. There's no CSO there at the beach. >>Yeah. >>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 at Bickley, who's the chief architect and co-founder of Platform nine b. Great to see you Cube alumni. We, we met at an OpenStack event in about eight years ago, or well later, earlier when opens Stack 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 was realized, and you've seen what Docker's doing with the new docker, the open source Docker now just a 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 infrastructure's code comes in, we talked to Bacar talking about Super Cloud, I met her about, you know, the new Arlon, our R lawn you guys just launched, the infrastructure's code is going to another level. And then it's always been DevOps infrastructure is 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 infrastructures 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 as 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 specify. So I think it's, it's a even better version of infrastructures code. >>Yeah, yeah. And, and that really means it's developer just accessing resources. Okay. Not declaring, 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. It's 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, 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, >>That's, I wrote a LinkedIn post today was comments about, you know, hey, enterprise is the 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 our GoCon, which was put on here in Silicon Valley at the, at the by intu. 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 inaugural 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 application 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 to 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 too 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 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 really wrote another post today on LinkedIn called the Silicon Wars AMD Stock is down arm has been on rise, we've 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 co con, which will be a covering. So that brings up the whole what's next? You guys just announced our lawn at ar GoCon, which came out of Intuit. We've had Maria Teel at our super cloud event, She's a 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 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 AR 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 the infrastructure. We talked a lot about what's going on below that. Yeah. Above our workloads at the end of the day, and I talk to CXOs and IT folks that, that are now DevOps engineers. They care about the workloads and they want the infrastructure's 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 here's 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 coming like an EC two instance, spin up a cluster. We've heard 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 AR loan 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 the profile. And then you can stamp out your app, your applications and your clusters and manage them in a very, So >>It's essentially standard, like creates a mechanism. Exactly. Standardized, declarative kind of configurations. And it's like a playbook, just deploy it. Now what there is between say a script like I'm, I have scripts, I can just automate scripts >>Or yes, this is where that declarative API and infrastructure as 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 are 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 as configuration is built kind of on, it's a 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 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. Kubernetes has value. We're gonna hear this year at CubeCon 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 rogue, that CubeCon coming up and now this'll be shipping this segment series out before. What do you expect to see at this year? It'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 jockeying 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 coupon 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 within 12 years with 14 years or something like that. Big number co-founder here a platform. I you's been around for a while at this game, man. We talked about OpenStack, that project we interviewed at one of their events. So OpenStack was the beginning of that, this new revolution. 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 Aati team at that time. We would 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 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? Opens Stack was an example and then 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, 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 need of its scale? >>The, the hyper squares? >>Yeah, yeah. A's Azure Google, >>You mean from a business perspective, 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 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 hyper skaters really want to be in the game in terms of, you know, the, the new risk and arm ecosystems, 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 you got software and you got middleware and he kinda 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 in the same game. 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 develop 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 is 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 there. Panel was really to discuss the role of Kubernetes. Now great conversation operations is impacted. What's just 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, 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 to run the infrastructure. The biggest blocking factor now is having a unified platform. And that's what where we come into >>Patrick, we were talking before we came on stage here about your background and we were kind of talking about the glory days in 2000, 2001 when the first ASPs application service providers came out. Kind of a SaaS vibe, but that was kind of all kind of cloud-like >>It wasn't, >>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, >>In fact, 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 inflations sea year. It's interesting. This is the first downturn, 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. Cause 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 infrastructure is not just some, you know, 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 Alon 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 unreal. >>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 pan or 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 as a pilot 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, >>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 in the journey is going on. And you know, most companies are, 70 plus percent of them have 1, 2, 3 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 it, 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 about 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 on-prem 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 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 heard it all here, ops and security teams. Cause they're kind of part of one thing, but option 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. So >>You working two sides to that coin. You've got the dev side and then >>And then infrastructure >>Side. >>Okay. Another customer that I give 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 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 box, like a small little box, >>Right? 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 locations. >>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, very well. >>Tucan, of course Detroit's >>Coming so, so it's already there, right? 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, not you have to rewrite and redevelop your application in 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 complexity is there, but the business benefits of agility and uniformity and customer experience are truly being done. >>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 >>Are >>For the customer. Customer, >>The customer's expectations change, right? Once you get used to a better customer experience, you learn. >>That's 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 let's 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. CARSs being been in an asb, being in a real time 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 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. You know, that is what I see >>Happening there. I think that that e-commerce is 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 gain, it's just changing how you operate, >>How you think and how you operate. See, if you think about the early days of e-commerce, just putting up a shopping cart that made you an e-commerce or e retailer or an e 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. >>Nascar, 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 Fur with Super Cloud 22 in the Cube. Thanks for watching. >>Thank you. Thank you. >>Hello and 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 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.

>>Hey guys. Welcome back to the Cubes coverage of Ansible Fast 2022. This is day two of our wall to wall coverage. Lisa Martin here with John Ferer. John, we're seeing this world where companies are saying if we can't automate it, we need to, The automation market is transforming. There's been a lot of buzz about that. A lot of technical chops here at Ansible Fest. >>Yeah, I mean, we've got a great guest here coming on Cuba alumni, Dean Newman, future room. He travels every event he's got. He's got his nose to the grindstone ear to the ground. Great analysis. I mean, we're gonna get into why it's important. How does Ansible fit into the big picture? It's really gonna be a great segment. The >>Board do it well, John just did my job for me about, I'll introduce him again. Daniel Newman, one of our alumni is Back Principal Analyst at Future and Research. Great to have you back on the cube. >>Yeah, it's good to join you. Excited to be back in Chicago. I don't know if you guys knew this, but for 40 years, this was my hometown. Now I don't necessarily brag about that anymore. I'm, I live in Austin now. I'm a proud Texan, but I did grow up here actually out in the west suburbs. I got off the plane, I felt the cold air, and I almost turned around and said, Does this thing go back? Yeah. Cause I'm, I've, I've grown thin skin. It did not take me long. I, I like the warm, Come on, >>I'm the saying, I'm from California and I got off the plane Monday. I went, Whoa, I need a coat. And I was in Miami a week ago and it was 85. >>Oh goodness. >>Crazy. So you just flew in. Talk about what's going on, your take on, on Ansible. We've talked a lot with the community, with partners, with customers, a lot of momentum. The flywheel of the community is going around and round and round. What are some of your perspectives that you see? >>Yeah, absolutely. Well, let's you know, I'm gonna take a quick step back. We're entering an era where companies are gonna have to figure out how to do more with less. Okay? We've got exponential data growth, we've got more architectural complexity than ever before. Companies are trying to discern how to deal with many different environments. And just at a macro level, Red Hat is one of the companies that is almost certainly gonna be part of this multi-cloud hybrid cloud era. So that should initially give a lot of confidence to the buying group that are looking at how to automate their environments. You're automating workflows, but really with, with Ansible, we're focused on automating it, automating the network. So as companies are kind of dig out, we're entering this recessionary period, Okay, we're gonna call it what it is. The first thing that they're gonna look at is how do we tech our way out of it? >>I had a wonderful one-on-one conversation with ServiceNow ceo, Bill McDermott, and we saw ServiceNow was in focus this morning in the initial opening session. This is the integration, right? Ansible integrating with ServiceNow. What we need to see is infrastructure automation, layers and applications working in concert to basically enable enterprises to be up and running all the time. Let's first fix the problems that are most common. Let's, let's automate 'em, let's script them. And then at some point, let's have them self resolving, which we saw at the end with Project Wisdom. So as I see it, automation is that layer that enterprises, boards, technologists, all can agree upon are basically here's something that can make our business more efficient, more profitable, and it's gonna deal with this short term downturn in a way that tech is actually gonna be the answer. Just like Bill and I said, let's tech our way out of it. >>If you look at the Red Hat being bought by ibm, you see Project Wisdom Project, not a product, it's a project. Project Wisdom is the confluence of research and practitioners kind of coming together with ai. So bringing AI power to the Ansible is interesting. Red Hat, Linux, Rel OpenShift, I mean, Red Hat's kind of position, isn't it? Kind of be in that right spot where a puck might be coming maybe. I mean, what do you think? >>Yeah, as analysts, we're really good at predicting the, the recent past. It's a joke I always like to make, but Red Hat's been building toward the future. I think for some time. Project Wisdom, first of all, I was very encouraged with it. One of the things that many people in the market probably have commented on is how close is IBM in Red Hat? Now, again, it's a $34 billion acquisition that was made, but boy, the cultures of these two companies couldn't be more different. And of course, Red Hat kind of carries this, this sort of middle ground layer where they provide a lot of value in services to companies that maybe don't use IBM at, at, for the public cloud especially. This was a great indication of how you can take the power of IBM's research, which of course has some of the world's most prolific data scientists, engineers, building things for the future. >>You know, you see things like yesterday they launched a, you know, an AI solution. You know, they're building chips, semiconductors, and technologies that are gonna power the future. They're building quantum. Long story short, they have these really brilliant technologists here that could be adding value to Red Hat. And I don't know that the, the world has fully been able to appreciate that. So when, when they got on stage and they kind of say, Here's how IBM is gonna help power the next generation, I was immediately very encouraged by the fact that the two companies are starting to show signs of how they can collaborate to offer value to their customers. Because of course, as John kind of started off with, his question is, they've kind of been where the puck is going. Open source, Linux hybrid cloud, This is the future. In the future. Every company's multi-cloud. And I said in a one-on-one meeting this morning, every company is going to probably have workloads on every cloud, especially large enterprises. >>Yeah. And I think that the secret's gonna be how do you make that evolve? And one of the things that's coming out of the industry over the years, and looking back as historians, we would say, gotta have standards. Well, with cloud, now people standards might slow things down. So you're gonna start to figure out how does the community and the developers are thinking it'll be the canary in the coal mine. And I'd love to get your reaction on that, because we got Cuban next week. You're seeing people kind of align and try to win the developers, which, you know, I always laugh cuz like, you don't wanna win, you want, you want them on your team, but you don't wanna win them. It's like a, it's like, so developers will decide, >>Well, I, I think what's happening is there are multiple forces that are driving product adoption. And John, getting the developers to support the utilization and adoption of any sort of stack goes a long way. We've seen how sticky it can be, how sticky it is with many of the public cloud pro providers, how sticky it is with certain applications. And it's gonna be sticky here in these interim layers like open source automation. And Red Hat does have a very compelling developer ecosystem. I mean, if you sat in the keynote this morning, I said, you know, if you're not a developer, some of this stuff would've been fairly difficult to understand. But as a developer you saw them laughing at jokes because, you know, what was it the whole part about, you know, it didn't actually, the ping wasn't a success, right? And everybody started laughing and you know, I, I was sitting next to someone who wasn't technical and, and you know, she kinda goes, What, what was so funny? >>I'm like, well, he said it worked. Do you see that? It said zero data trans or whatever that was. So, but if I may just really quickly, one, one other thing I did wanna say about Project Wisdom, John, that the low code and no code to the full stack developer is a continuum that every technology company is gonna have to think deeply about as we go to the future. Because the people that tend to know the process that needs to be automated tend to not be able to code it. And so we've seen every automation company on the planet sort of figuring out and how to address this low code, no code environment. I think the power of this partnership between IBM Research and Red Hat is that they have an incredibly deep bench of capabilities to do things like, like self-training. Okay, you've got so much data, such significant size models and accuracy is a problem, but we need systems that can self teach. They need to be able self-teach, self learn, self-heal so that we can actually get to the crux of what automation is supposed to do for us. And that's supposed to take the mundane out and enable those humans that know how to code to work on the really difficult and hard stuff because the automation's not gonna replace any of that stuff anytime soon. >>So where do you think looking at, at the partnership and the evolution of it between IBM research and Red Hat, and you're saying, you know, they're, they're, they're finally getting this synergy together. How is it gonna affect the future of automation and how is it poised to give them a competitive advantage in the market? >>Yeah, I think the future or the, the competitive space is that, that is, is ecosystems and integration. So yesterday you heard, you know, Red Hat Ansible focusing on a partnership with aws. You know, this week I was at Oracle Cloud world and they're talking about running their database in aws. And, and so I'm kind of going around to get to the answer to your question, but I think collaboration is sort of the future of growth and innovation. You need multiple companies working towards the same goal to put gobs of resources, that's the technical term, gobs of resources towards doing really hard things. And so Ansible has been very successful in automating and securing and focusing on very certain specific workloads that need to be automated, but we need more and there's gonna be more data created. The proliferation, especially the edge. So you saw all this stuff about Rockwell, How do you really automate the edge at scale? You need large models that are able to look and consume a ton of data that are gonna be continuously learning, and then eventually they're gonna be able to deliver value to these companies at scale. IBM plus Red Hat have really great resources to drive this kind of automation. Having said that, I see those partnerships with aws, with Microsoft, with ibm, with ServiceNow. It's not one player coming to the table. It's a lot of players. They >>Gotta be Switzerland. I mean they have the Switzerland. I mean, but the thing about the Amazon deal is like that marketplace integration essentially puts Ansible once a client's in on, on marketplace and you get the central on the same bill. I mean, that's gonna be a money maker for Ansible. I >>Couldn't agree more, John. I think being part of these public cloud marketplaces is gonna be so critical and having Ansible land and of course AWS largest public cloud by volume, largest marketplace today. And my opinion is that partnership will be extensible to the other public clouds over time. That just makes sense. And so you start, you know, I think we've learned this, John, you've done enough of these interviews that, you know, you start with the biggest, with the highest distribution and probability rates, which in this case right now is aws, but it'll land on in Azure, it'll land in Google and it'll continue to, to grow. And that kind of adoption, streamlining make it consumption more consumable. That's >>Always, I think, Red Hat and Ansible, you nailed it on that whole point about multicloud, because what happens then is why would I want to alienate a marketplace audience to use my product when it could span multiple environments, right? So you saw, you heard that Stephanie yesterday talk about they, they didn't say multiple clouds, multiple environments. And I think that is where I think I see this layer coming in because some companies just have to work on all clouds. That's the way it has to be. Why wouldn't you? >>Yeah. Well every, every company will probably end up with some workloads in every cloud. I just think that is the fate. Whether it's how we consume our SaaS, which a lot of people don't think about, but it always tends to be running on another hyperscale public cloud. Most companies tend to be consuming some workloads from every cloud. It's not always direct. So they might have a single control plane that they tend to lead the way with, but that is only gonna continue to change. And every public cloud company seems to be working on figuring out what their niche is. What is the one thing that sort of drives whether, you know, it is, you know, traditional, we know the commoditization of traditional storage network compute. So now you're seeing things like ai, things like automation, things like the edge collaboration tools, software being put into the, to the forefront because it's a different consumption model, it's a different margin and economic model. And then of course it gives competitive advantages. And we've seen that, you know, I came back from Google Cloud next and at Google Cloud next, you know, you can see they're leaning into the data AI cloud. I mean, that is their focus, like data ai. This is how we get people to come in and start using Google, who in most cases, they're probably using AWS or Microsoft today. >>It's a great specialty cloud right there. That's a big use case. I can run data on Google and run something on aws. >>And then of course you've got all kinds of, and this is a little off topic, but you got sovereignty, compliance, regulatory that tends to drive different clouds over, you know, global clouds like Tencent and Alibaba. You know, if your workloads are in China, >>Well, this comes back down at least to the whole complexity issue. I mean, it has to get complex before it gets easier. And I think that's what we're seeing companies opportunities like Ansible to be like, Okay, tame, tame the complexity. >>Yeah. Yeah, I totally agree with you. I mean, look, when I was watching the demonstrations today, my take is there's so many kind of simple, repeatable and mundane tasks in everyday life that enterprises need to, to automate. Do that first, you know? Then the second thing is working on how do you create self-healing, self-teaching, self-learning, You know, and, and I realize I'm a little broken of a broken record at this, but these are those first things to fix. You know, I know we want to jump to the future where we automate every task and we have multi-term conversational AI that is booking our calendars and driving our cars for us. But in the first place, we just need to say, Hey, the network's down. Like, let's make sure that we can quickly get access back to that network again. Let's make sure that we're able to reach our different zones and locations. Let's make sure that robotic arm is continually doing the thing it's supposed to be doing on the schedule that it's been committed to. That's first. And then we can get to some of these really intensive deep metaverse state of automation that we talk about. Self-learning, data replication, synthetic data. I'm just gonna throw terms around. So I sound super smart. >>In your customer conversations though, from an looking at the automation journey, are you finding most of them, or some percentage is, is wanting to go directly into those really complex projects rather than starting with the basics? >>I don't know that you're, you're finding that the customers want to do that? I think it's the architecture that often ends up being a problem is we as, as the vendor side, will tend to talk about the most complex problems that they're able to solve before companies have really started solving the, the immediate problems that are before them. You know, it's, we talk about, you know, the metaphor of the cloud is a great one, but we talk about the cloud, like it's ubiquitous. Yeah. But less than 30% of our workloads are in the public cloud. Automation is still in very early days and in many industries it's fairly nascent. And doing things like self-healing networks is still something that hasn't even been able to be deployed on an enterprise-wide basis, let alone at the industrial layer. Maybe at the company's on manufacturing PLAs or in oil fields. Like these are places that have difficult to reach infrastructure that needs to be running all the time. We need to build systems and leverage the power of automation to keep that stuff up and running. That's, that's just business value, which by the way is what makes the world go running. Yeah. Awesome. >>A lot of customers and users are struggling to find what's the value in automating certain process, What's the ROI in it? How do you help them get there so that they understand how to start, but truly to make it a journey that is a success. >>ROI tends to be a little bit nebulous. It's one of those things I think a lot of analysts do. Things like TCO analysis Yeah. Is an ROI analysis. I think the businesses actually tend to know what the ROI is gonna be because they can basically look at something like, you know, when you have an msa, here's the downtime, right? Business can typically tell you, you know, I guarantee you Amazon could say, Look for every second of downtime, this is how much commerce it costs us. Yeah. A company can generally say, if it was, you know, we had the energy, the windmills company, like they could say every minute that windmill isn't running, we're creating, you know, X amount less energy. So there's a, there's a time value proposition that companies can determine. Now the question is, is about the deployment. You know, we, I've seen it more nascent, like cybersecurity can tend to be nascent. >>Like what does a breach cost us? Well there's, you know, specific costs of actually getting the breach cured or paying for the cybersecurity services. And then there's the actual, you know, ephemeral costs of brand damage and of risks and customer, you know, negative customer sentiment that potentially comes out of it. With automation, I think it's actually pretty well understood. They can look at, hey, if we can do this many more cycles, if we can keep our uptime at this rate, if we can reduce specific workforce, and I'm always very careful about this because I don't believe automation is about replacement or displacement, but I do think it is about up-leveling and it is about helping people work on things that are complex problems that machines can't solve. I mean, said that if you don't need to put as many bodies on something that can be immediately returned to the organization's bottom line, or those resources can be used for something more innovative. So all those things are pretty well understood. Getting the automation to full deployment at scale, though, I think what often, it's not that roi, it's the timeline that gets misunderstood. Like all it projects, they tend to take longer. And even when things are made really easy, like with what Project Wisdom is trying to do, semantically enable through low code, no code and the ability to get more accuracy, it just never tends to happen quite as fast. So, but that's not an automation problem, That's just the crux of it. >>Okay. What are some of the, the next things on your plate? You're quite a, a busy guy. We, you, you were at Google, you were at Oracle, you're here today. What are some of the next things that we can expect from Daniel Newman? >>Oh boy, I moved Really, I do move really quickly and thank you for that. Well, I'm very excited. I'm taking a couple of work personal days. I don't know if you're a fan, but F1 is this weekend. I'm the US Grand Prix. Oh, you're gonna Austin. So I will be, I live in Austin. Oh. So I will be in Austin. I will be at the Grand Prix. It is work because it, you know, I'm going with a number of our clients that have, have sponsorships there. So I'll be spending time figuring out how the data that comes off of these really fun cars is meaningfully gonna change the world. I'll actually be talking to Splunk CEO at the, at the race on Saturday morning. But yeah, I got a lot of great things. I got a, a conversation coming up with the CEO of Twilio next week. We got a huge week of earnings ahead and so I do a lot of work on that. So I'll be on Bloomberg next week with Emily Chang talking about Microsoft and Google. Love talking to Emily, but just as much love being here on, on the queue with you >>Guys. Well we like to hear that. Who you're rooting for F one's your favorite driver. I, >>I, I like Lando. Do you? I'm Norris. I know it's not necessarily a fan favorite, but I'm a bit of a McLaren guy. I mean obviously I have clients with Oracle and Red Bull with Ball Common Ferrari. I've got Cly Splunk and so I have clients in all. So I'm cheering for all of 'em. And on Sunday I'm actually gonna be in the Williams Paddock. So I don't, I don't know if that's gonna gimme me a chance to really root for anything, but I'm always, always a big fan of the underdog. So maybe Latifi. >>There you go. And the data that comes off the how many central unbeliev, the car, it's crazy's. Such a scientific sport. Believable. >>We could have Christian, I was with Christian Horner yesterday, the team principal from Reside. Oh yeah, yeah. He was at the Oracle event and we did a q and a with him and with the CMO of, it's so much fun. F1 has been unbelievable to watch the momentum and what a great, you know, transitional conversation to to, to CX and automation of experiences for fans as the fan has grown by hundreds of percent. But just to circle back full way, I was very encouraged with what I saw today. Red Hat, Ansible, IBM Strong partnership. I like what they're doing in their expanded ecosystem. And automation, by the way, is gonna be one of the most robust investment areas over the next few years, even as other parts of tech continue to struggle that in cyber security. >>You heard it here. First guys, investment in automation and cyber security straight from two analysts. I got to sit between. For our guests and John Furrier, I'm Lisa Martin, you're watching The Cube Live from Chicago, Ansible Fest 22. John and I will be back after a short break. SO'S stick around.

>>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 is around the corner and public cloud is winning. Got the private cloud on premise and Edge. Got a great guest here, Bacar, go deep 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 just 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, 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 to run the infrastructure. The biggest blocking factor now is having a unified platform. And that's what where we come into >>Patrick, we were talking before we came on stage here about your background and we were kind of talking about the glory days in 2000, 2001 when the first ASPs 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, >>In fact, you know, as we were talking offline, I was in one of those asbs 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 their 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, 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. Because 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 infrastructure is not just some, you know, 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 Alon and I want to do with Super Cloud and calling at 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, more >>Real. I, 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 to, 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, 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 pan, 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 OpenStack, 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 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 it, the beauty of it is yes, open source, but the biggest gating factor is the skill. 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. There are thousands of stores in a retailer. So we provide that and also for specific segments where data sovereignty and data residency, our key regulatory reasons. We also run 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 their tools, they're using whatever app development tools they use, but they use our platform. >>And 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 two part of one thing, 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, So you were just two sides of that coin. You've got the dev side and then and the infrastructure side. Okay, >>Another customer, like give 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 rack in the store or they can't move everything to the cloud because the store operations have to be local. The menu changes based on it's classic edge if >>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 >>Say little shares, like how big one like a box, like a small little box, >>Right? 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, 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 >>Tucan of course Detroit's >>Coming here, so, So it's already there, right? 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 cloudnative, okay? You can't port to cloud, not 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 lot of our customers in that journey. Now everybody wants to be cloud native, 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 you use. Okay? So, so I think the complexity is there, but the business benefits of agility and uniformity and customer experience are truly being done. >>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 Domino's 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, they were the pioneer in it. To me, those are the kinds of customer experiences that cloud native can provide. >>Being agility and having that flow through the application changes what the expectations of are for the customer. >>Customer, the customer's expectations change, right? Once you get used to a better customer experience, you will not >>Best part. 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 in 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 of 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, the big companies, you've seen the different waves. What's going on right now Put into context this moment in time. Sure. Around Super >>Cloud. Sure. I think as you said, a lot of battles. Cars being, being in an asb, being in a real time 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 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, couple of parallels come to me. One is, think of it, which was forced to on us 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 wasn't existence. Question. Yeah, I think we are at that pivotal moment now in companies trying to become digital and cloud native and that is what I see >>Happening there. I think that that e-commerce is 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 gain, it's just changing how you operate, >>How you think and how you operate. See, if you think about the early days of e-commerce, just putting up a shopping cart then made you an e-commerce or e retailer or 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 for 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 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.

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

>>Hi, this is Dave Volonte. We're winding down Day two of the Cubes coverage of Vim on 2022. We're here at the area in Las Vegas. Myself and Dave Nicholson had been going for two days. Everybody's excited about the VM on party tonight. It's It's always epic, and, uh, it's a great show in terms of its energy. Danny Allen is here. He's cto of in his back. He gave the keynote this morning. I say, Danny, you know, you look pretty good up there with two hours of sleep. I >>had three. >>Look, don't look that good, but your energy was very high. And I got to tell you the story you told was amazing. It was one of the best keynotes I've ever seen. Even even the technology pieces were outstanding. But you weaving in that story was incredible. I'm hoping that people will go back and and watch it. We probably don't have time to go into it, but wow. Um, can you give us the the one minute version of that >>long story? >>Sure. Yeah. I read a book back in 2013 about a ship that sank off Portsmouth, Maine, and I >>thought, I'm gonna go find that >>ship. And so it's a long, >>complicated process. Five >>years in the making. But we used data, and the data that found the ship was actually from 15 years earlier. >>And in 20 >>18, we found the bow of the ship. We found the stern of the ship, but what we were really trying to answer was torpedoed. Or did the boilers explode? Because >>the navy said the boilers exploded >>and two survivors said, No, it was torpedoed or there was a German U boat there. >>And so >>our goal was fine. The ship find the boiler. >>So in 20 >>19, Sorry, Uh, it was 2018. We found the bow and the stern. And then in 2019, we found both boilers perfectly intact. And in fact, the rear end of that torpedo wasn't much left >>of it, of course, but >>data found that wreck. And so it, um, it exonerated essentially any implication that somebody screwed >>up in >>the boiler system and the survivors or the Children of the survivors obviously appreciated >>that. I'm sure. Yes, Several >>outcomes to it. So the >>chief engineer was one >>of the 13 survivors, >>and he lived with the weight of this for 75 years. 49 sailors dead because of myself. But I had the opportunity of meeting some of the Children of the victims and also attending ceremonies. The families of those victims received purple hearts because they were killed due to enemy action. And then you actually knew how to do this. I wasn't aware you had experience finding Rex. You've >>discovered several of >>them prior to this one. But >>the interesting connection >>the reason why this keynote was so powerful as we're a >>team, it's a data conference. >>You connected that to data because you you went out and bought a How do you say this? Magnanimous magnetometer. Magnetometer, Magnetometer. I don't know what that >>is. And a side >>scan Sonar, Right? I got that right. That was >>easy. But >>then you know what this stuff is. And then you >>built the model >>tensorflow. You took all the data and you found anomalies. And then you went right to that spot. Found the >>wreck with 12 >>£1000 of dynamite, >>which made your heart >>beat. But >>then you found >>the boilers. That's incredible. And >>but the point was, >>this is data >>uh, let's see, >>a lot of years after, >>right? >>Yeah. Two sets of data were used. One was the original set of side scan sonar >>data by the historian >>who discovered there was a U boat in the area that was 15 years old. >>And then we used, of >>course, the wind and weather and wave pattern data that was 75 years old to figure out where the boiler should be because they knew that the ship had continued to float for eight minutes. And so you had to go back and determine the models of where should the boilers >>be if it exploded and the boilers >>dropped out and it floated along >>for eight minutes and then sank? Where was >>that data? >>It was was a scanned was an electronic was a paper. How did you get that data? So the original side scan sonar data was just hard >>drive >>data by the historian. >>I wish I could say he used them to >>back it up. But I don't know that I can say that. But he still had >>the data. 15 years later, the >>weather and >>wind and wave data, That was all public information, and we actually used that extensively. We find other wrecks. A lot of wrecks off Boston Sunken World War Two. So we were We were used to that model of tracking what happened. Wow. So, yes, imagine if that data weren't available >>and it >>probably shouldn't have been right by all rights. So now fast forward to 2022. We've got Let's talk about just a cloud >>data. I think you said a >>couple of 100 >>petabytes in the >>cloud 2019. 500 in, Uh, >>no. Yeah. In >>20 2200 and 42. Petabytes in 20 2500 Petabytes last year. And we've already done the same as 2020. So >>240 petabytes >>in Q one. I expect >>this year to move an exhibit of >>data into the public cloud. >>Okay, so you got all that data. Who knows what's in there, right? And if it's not protected, who's going to know in 50 60 7100 years? Right. So that was your tie in? Yes. To the to the importance of data protection, which was just really, really well done. Congratulations. Honestly, one of the best keynotes I've ever seen keynotes often really boring, But you did a great job again on two hours. Sleep. So much to unpack here. The other thing that really is. I mean, we can talk about the demos. We can talk about the announcements. Um, so? Well, yeah, Let's see. Salesforce. Uh, data protection is now public. I almost spilled the beans yesterday in the cube. Caught myself the version 12. Obviously, you guys gave a great demo showing the island >>cloud with I think it >>was just four minutes. It was super fast. Recovery in four minutes of data loss was so glad you didn't say zero minutes because that would have been a live demos which, Okay, which I appreciate and also think is crazy. So some really cool demos, Um, and some really cool features. So I have so much impact, but the the insights that you can provide through them it's VM one, uh, was actually something that I hadn't heard you talk about extensively in the past. That maybe I just missed it. But I wonder if you could talk about that layer and why it's critical differentiator for Wien. It's >>the hidden gem >>within the Wien portfolio because it knows about absolutely >>everything. >>And what determines the actions >>that we take is the >>context in which >>data is surviving. So in the context of security, which we are showing, we look for CPU utilisation, memory utilisation, data change rate. If you encrypt all of the data in a file server, it's going to blow up overnight. And so we're leveraging heuristics in their reporting. But even more than that, one of the things in Wien one people don't realise we have this concept of the intelligent diagnostics. It's machine learning, which we drive on our end and we push out as packages intervene one. There's up to 200 signatures, but it helps our customers find issues before they become issues. Okay, so I want to get into because I often time times, don't geek out with you. And don't take advantage of your your technical knowledge. And you've you've triggered a couple of things, >>especially when the >>analysts call you said it again today that >>modern >>data protection has meaning to you. We talked a little bit about this yesterday, but back in >>the days of >>virtualisation, you shunned agents >>and took a different >>approach because you were going for what was then >>modern. Then you >>went to bare metal cloud hybrid >>cloud containers. Super Cloud. Using the analyst meeting. You didn't use the table. Come on, say Super Cloud and then we'll talk about the edge. So I would like to know specifically if we can go back to Virtualised >>because I didn't know >>this exactly how you guys >>defined modern >>back then >>and then. Let's take that to modern today. >>So what do you >>do back then? And then we'll get into cloud and sure, So if you go back to and being started, everyone who's using agents, you'd instal something in the operating system. It would take 10% 15% of your CPU because it was collecting all the data and sending it outside of the machine when we went through a virtual environment. If you put an agent inside that machine, what happens is you would have 100 operating systems all on the same >>server, consuming >>resources from that hyper visor. And so he said, there's a better way of capturing the data instead of capturing the data inside the operating system. And by the way, managing thousands of agents is no fun. So What we did is we captured a snapshot of the image at the hyper visor level. And then over time, we just leverage changed block >>tracking from the hyper >>visor to determine what >>had changed. And so that was modern. Because no more >>managing agents >>there was no impact >>on the operating system, >>and it was a far more >>efficient way to store >>data. You leverage CBT through the A P. Is that correct? Yeah. We used the VCR API >>for data protection. >>Okay, so I said this to Michael earlier. Fast forward to today. Your your your data protection competitors aren't as fat, dumb and happy as they used to be, so they can do things in containers, containers. And we talked about that. So now let's talk about Cloud. What's different about cloud data protection? What defines modern data protection? And where are the innovations that you're providing? >>Let me do one step in >>between those because one of the things that happened between hypervisors and Cloud was >>offline. The capture of the data >>to the storage system because >>even better than doing it >>at the hyper visor clusters >>do it on the storage >>array because that can capture the >>data instantly. Right? So as we go to the cloud, we want to do the same thing. Except we don't have access to either the hyper visor or the storage system. But what they do provide is an API. So we can use the API to capture all of the blocks, all of the data, all of the changes on that particular operating system. Now, here's where we've kind of gone full circle on a hyper >>visor. You can use the V >>sphere agent to reach into the operating system to do >>things like application consistency. What we've done modern data protection is create specific cloud agents that say Forget >>about the block changes. Make sure that I have application consistency inside that cloud operating >>system. Even though you don't have access to the hyper visor of the storage, >>you're still getting the >>operating system consistency >>while getting the really >>fast capture of data. So that gets into you talking on stage about how synapse don't equal data protection. I think you just explained it, but explain why, but let me highlight something that VM does that is important. We manage both snapshots and back up because if you can recover from your storage array >>snapshot. That is the best >>possible thing to recover from right, But we don't. So we manage both the snapshots and we converted >>into the VM portable >>data format. And here's where the super cloud comes into play because if I can convert it into the VM portable data format, I can move >>that OS >>anywhere. I can move it from >>physical to virtual to cloud >>to another cloud back to virtual. I can put it back on physical if I want to. It actually abstracts >>the cloud >>layer. There are things >>that we do when we go >>between clouds. Some use bio, >>some use, um, fee. >>But we have the data in backup format, not snapshot format. That's theirs. But we have been in backup format that we can move >>around and abstract >>workloads across. All of the infrastructure in your >>catalogue is control >>of that. Is that Is >>that right? That is about >>that 100%. And you know what's interesting about our catalogue? Dave. The catalogue is inside the backup, and so historically, one of the problems with backup is that you had a separate catalogue and if it ever got corrupted. All of your >>data is meaningless >>because the catalogue is inside >>the backup >>for that unique VM or that unique instance, you can move it anywhere and power it on. That's why people said were >>so reliable. As long >>as you have the backup file, you can delete our >>software. You can >>still get the data back, so I love this fast paced so that >>enables >>what I call Super Cloud we now call Super Cloud >>because now >>take that to the edge. >>If I want to go to the edge, I presume you can extend that. And I also presume the containers play a role there. Yes, so here's what's interesting about the edge to things on the edge. You don't want to have any state if you can help it, >>and so >>containers help with that. You can have stateless environment, some >>persistent data storage, >>but we not only >>provide the portability >>in operating systems. We also do this for containers, >>and that's >>true if you go to the cloud and you're using SE CKs >>with relational >>database service is already >>asked for the persistent data. >>Later, we can pick that up and move it to G K E or move it to open shift >>on premises. And >>so that's why I call this the super cloud. We have all of this data. Actually, I think you termed the term super thank you for I'm looking for confirmation from a technologist that it's technically feasible. It >>is technically feasible, >>and you can do it today and that's a I think it's a winning strategy. Personally, Will there be >>such a thing as edge Native? You know, there's cloud native. Will there be edge native new architectures, new ways of doing things, new workloads use cases? We talk about hardware, new hardware, architectures, arm based stuff that are going to change everything to edge Native Yes and no. There's going to be small tweaks that make it better for the edge. You're gonna see a lot of iron at the edge, obviously for power consumption purposes, and you're also going to see different constructs for networking. We're not going to use the traditional networking, probably a lot more software to find stuff. Same thing on the storage. They're going to try and >>minimise the persistent >>storage to the smallest footprint possible. But ultimately I think we're gonna see containers >>will lead >>the edge. We're seeing this now. We have a I probably can't name them, but we have a large retail organisation that is running containers in every single store with a small, persistent footprint of the point of sale and local data, but that what >>is running the actual >>system is containers, and it's completely ephemeral. So we were >>at Red Hat, I was saying >>earlier last week, and I'd say half 40 50% of the conversation was edge open shift, obviously >>playing a big role there. I >>know doing work with Rancher and Town Zoo. And so there's a lot of options there. >>But obviously, open shift has >>strong momentum in the >>marketplace. >>I've been dominating. You want to chime in? No, I'm just No, >>I yeah, I know. Sometimes >>I'll sit here like a sponge, which isn't my job absorbing stuff. I'm just fascinated by the whole concept of of a >>of a portable format for data that encapsulates virtual machines and or instances that can live in the containerised world. And once you once you create that common denominator, that's really that's >>That's the secret sauce >>for what you're talking about is a super club and what's been fascinating to watch because I've been paying attention since the beginning. You go from simply V. M. F s and here it is. And by the way, the pitch to E. M. C. About buying VM ware. It was all about reducing servers to files that can be stored on storage arrays. All of a sudden, the light bulbs went off. We can store those things, and it just began. It became it became a marriage afterwards. But to watch that progression that you guys have gone from from that fundamental to all of the other areas where now you've created this common denominator layer has has been amazing. So my question is, What's the singer? What doesn't work? Where the holes. You don't want to look at it from a from a glass half empty perspective. What's the next opportunity? We've talked about edge, but what are the things that you need to fill in to make this truly ubiquitous? Well, there's a lot of services out there that we're not protecting. To be fair, right, we do. Microsoft 3 65. We announced sales for us, but there's a dozen other paths services that >>people are moving data >>into. And until >>we had data protection >>for the assassin path services, you know >>you have to figure out how >>to protect them. Now here's the kicker about >>those services. >>Most of them have the >>ability to dump date >>out. The trick is, do they have the A >>P? I is needed to put data >>back into it right, >>which is which is a >>gap. As an industry, we need to address this. I actually think we need a common >>framework for >>how to manage the >>export of data, but also the import of data not at a at a system level, but at an atomic level of the elements within those applications. >>So there are gaps >>there at the industry, but we'll fill them >>if you look on the >>infrastructure side. We've done a lot with containers and kubernetes. I think there's a next wave around server list. There's still servers and these micro services, but we're making things smaller and smaller and smaller, and there's going to be an essential need to protect those services as well. So modern data protection is something that's going to we're gonna need modern data protection five years from now, the modern will just be different. Do you ever see the day, Danny, where governance becomes an >>adjacency opportunity for >>you guys? It's clearly an opportunity even now if you look, we spent a lot of time talking about security and what you find is when organisations go, for example, of ransomware insurance or for compliance, they need to be able to prove that they have certifications or they have security or they have governance. We just saw transatlantic privacy >>packed only >>to be able to prove what type of data they're collecting. Where are they storing it? Where are they allowed to recovered? And yes, those are very much adjacency is for our customers. They're trying to manage that data. >>So given that I mean, >>am I correct that architecturally you are, are you location agnostic? Right. We are a location agnostic, and you can actually tag data to allowable location. So the big trend that I think is happening is going to happen in in this >>this this decade. >>I think we're >>scratching the surface. Is this idea >>that, you know, leave data where it is, >>whether it's an S three >>bucket, it could be in an Oracle >>database. It could be in a snowflake database. It can be a data lake that's, you know, data, >>bricks or whatever, >>and it stays where >>it is. And it's just a note on the on the call of the data >>mesh. Not my term. Jim >>Octagon coined that term. The >>problem with that, and it puts data in the hands of closer to the domain experts. The problem with that >>scenario >>is you need self service infrastructure, which really doesn't exist today anyway. But it's coming, and the big problem is Federated >>computational >>governance. How do I automate that governance so that the people who should have access to that it can have access to that data? That, to me, seems to be an adjacency. It doesn't exist except in >>a proprietary >>platform. Today. There needs to be a horizontal >>layer >>that is more open than anybody >>can use. And I >>would think that's a perfect opportunity for you guys. Just strategically it is. There's no question, and I would argue, Dave, that it's actually >>valuable to take snapshots and to keep the data out at the edge wherever it happens to be collected. But then Federated centrally. It's why I get so excited by an exhibit of data this year going into the cloud, because then you're centralising the aggregation, and that's where you're really going to drive the insights. You're not gonna be writing tensorflow and machine learning and things on premises unless you have a lot of money and a lot of GPS and a lot of capacity. That's the type of thing that is actually better suited for the cloud. And, I would argue, better suited for not your organisation. You're gonna want to delegate that to a third party who has expertise in privacy, data analysis or security forensics or whatever it is that you're trying to do with the data. But you're gonna today when you think about AI. We talked about A. I haven't had a tonne of talk about AI some >>appropriate >>amount. Most of the >>AI today correct me if you think >>this is not true is modelling that's done in the cloud. It's dominant. >>Don't >>you think that's gonna flip when edge >>really starts to take >>off where it's it's more real time >>influencing >>at the edge in new use cases at the edge now how much of that data >>is going to be >>persisted is a >>point of discussion. But what >>are your thoughts on that? I completely agree. So my expectation of the way >>that this will work is that >>the true machine learning will happen in the centralised location, and what it will do is similar to someone will push out to the edge the signatures that drive the inferences. So my example of this is always the Tesla driving down the road. >>There's no way that that >>car should be figuring it sending up to the cloud. Is that a stop sign? Is it not? It can't. It has to be able to figure out what the stop sign is before it gets to it, so we'll do the influencing at the edge. But when it doesn't know what to do with the data, then it should send it to the court to determine, to learn about it and send signatures back out, not just to that edge location, but all the edge locations within the within the ecosystem. So I get what you're saying. They might >>send data back >>when there's an anomaly, >>or I always use the example of a deer running in front of the car. David Floyd gave me that one. That's when I want to. I do want to send the data back to the cloud because Tesla doesn't persist. A tonne of data, I presume, right, right less than 5% of it. You know, I want to. Usually I'm here to dive into the weeds. I want kind of uplevel this >>to sort of the >>larger picture. From an I T perspective. >>There's been a lot of consolidation going on if you divide the >>world into vendors >>and customers. On the customer side, there are only if there's a finite number of seats at the table for truly strategic partners. Those get gobbled up often by hyper >>scale cloud >>providers. The challenge there, and I'm part of a CEO accreditation programme. So this >>is aimed at my students who >>are CEOs and CIOs. The challenge is that a lot of CEOs and CIOs on the customer side don't exhaustively drag out of their vendor partners like a theme everything that Saveem >>can do for >>them. Maybe they're leveraging a point >>solution, >>but I guarantee you they don't all know that you've got cast in in the portfolio. Not every one of them does yet, let alone this idea of a super >>cloud and and and >>how much of a strategic role you can play. So I don't know if it's a blanket admonition to folks out there, but you have got to leverage the people who are building the solutions that are going to help you solve problems in the business. And I guess, as in the form of >>a question, >>uh, do you Do you see that as a challenge? Now those the limited number of seats at >>the Table for >>Strategic Partners >>Challenge and >>Opportunity. If you look at the types of partners that we've partnered with storage partners because they own the storage of the data, at the end of the day, we actually just manage it. We don't actually store it the cloud partners. So I see that as the opportunity and my belief is I thought that the storage doesn't matter, >>but I think the >>organisation that can centralise and manage that data is the one that can rule the world, and so >>clearly I'm a team. I think we can do amazing things, but we do have key >>strategic partners hp >>E Amazon. You heard >>them on stage yesterday. >>18 different >>integrations with AWS. So we have very strategic partners. Azure. I go out there all the time. >>So there >>you don't need to be >>in the room at the table because your partners are >>and they have a relationship with the customer as well. Fair enough. But the key to this it's not just technology. It is these relationships and what is possible between our organisations. So I'm sorry to be >>so dense on this, but when you talk about >>centralising that data you're talking about physically centralising it or can actually live across clouds, >>for instance. But you've got >>visibility and your catalogues >>have visibility on >>all that. Is that what you mean by centralised obliterated? We have understanding of all the places that lives, and we can do things with >>it. We can move it from one >>cloud to another. We can take, you know, everyone talks about data warehouses. >>They're actually pretty expensive. >>You got to take data and stream it into this thing, and there's a massive computing power. On the other hand, we're >>not like that. You've storage on there. We can ephemeral e. Spin up a database when you need it for five minutes and then destroy it. We can spin up an image when you need it and then destroy it. And so on your perspective of locations. So irrespective of >>location, it doesn't >>have to be in a central place, and that's been a challenge. You extract, >>transform and load, >>and moving the data to the central >>location has been a problem. We >>have awareness of >>all the data everywhere, >>and then we can make >>decisions as to what you >>do based >>on where it is and >>what it is. And that's a metadata >>innovation. I guess that >>comes back to the catalogue, >>right? Is that correct? >>You have data >>about the data that informs you as to where it is and how to get to it. And yes, so metadata within the data that allows you to recover it and then data across the federation of all that to determine where it is. And machine intelligence plays a role in all that, not yet not yet in that space. Now. I do think there's opportunity in the future to be able to distribute storage across many different locations and that's a whole conversation in itself. But but our machine learning is more just on helping our customers address the problems in their infrastructures rather than determining right now where that data should be. >>These guys they want me to break, But I'm >>refusing. So your >>Hadoop back >>in their rooms via, um that's >>well, >>that scale. A lot of customers. I talked to Renee Dupuis. Hey, we we got there >>was heavy lift. You >>know, we're looking at new >>ways. New >>approaches, uh, going. And of course, it's all in the cloud >>anyway. But what's >>that look like? That future look like we haven't reached bottle and X ray yet on our on our Hadoop clusters, and we do continuously examine >>them for anomalies that might happen. >>Not saying we won't run into a >>bottle like we always do at some >>point, But we haven't yet >>awesome. We've covered a lot of We've certainly covered extensively the research that you did on cyber >>security and ransomware. Um, you're kind of your vision for modern >>data protection. I think we hit on that pretty well casting, you know, we talked to Michael about that, and then, you know, the future product releases the Salesforce data protection. You guys, I think you're the first there. I think you were threatened at first from Microsoft. 3 65. No, there are other vendors in the in the salesforce space. But what I tell people we weren't the first to do data capture at the hyper >>visor level. There's two other >>vendors I won't tell you they were No one remembers them. Microsoft 3 65. We weren't the first one to for that, but we're now >>the largest. So >>there are other vendors in the salesforce space. But we're looking at We're going to be aggressive. Danielle, Thanks >>so much for coming to Cuba and letting us pick your brain like that Really great job today. And congratulations on >>being back >>in semi normal. Thank you for having me. I love being on all right. And thank you for watching. Keep it right there. More coverage. Day volonte for Dave >>Nicholson, By >>the way, check out silicon angle dot com for all the written coverage. All the news >>The cube dot >>net is where all these videos We'll we'll live. Check out wiki bond dot com I published every week. I think I'm gonna dig into the cybersecurity >>research that you guys did this week. If I can >>get a hands my hands on those charts which Dave Russell promised >>me, we'll be right back >>right after this short break. Mm.

>>The cube presents, Coon and cloud native con Europe 22, brought to you by the cloud native computing foundation. >>Welcome to Valencia Spain and Coon cloud native con Europe, 2022. I'm Keith towns, along with Paul Gillon, senior editor, enterprise architecture and Silicon angle. We are going to talk to some amazing folks, especially in today's segment. Paul, uh, there's a lot of companies here, like what what's been the, the consistent theme you've heard so far in the show. >>Well, you know, one thing that's different from this show, it seems to me than others I've attended is it's all around open source. We're not seeing a lot of companies bringing new proprietary technology to market. We are seeing them try to piece together, open source components with some kind of, perhaps there's a proprietary element to it, but to create some kind of a, a common management interface or control plane, and that's quite different from what I think we've seen in the past open source business models have been difficult to make work historically. Uh, and these companies are all taking their, their own approaches to it. But I think the, the degree to which this, the people here of coalesced around the importance of open source is building blocks to the future of, of applications is something I've not seen quite this way before. >>Well, with our current segment, guess we're gonna go deep into kind of these challenges and how enterprises are addressing, and their partners are addressing with those challenges we have with us, a flower head of cloud native HCL technologies. We'll get into how a system integrator is helping with this transition to Ramon neon, senior product manager, redhead. Welcome to the show. You're now cube alum. Welcome. Thanks for having us. So we're gonna get right off, uh, off the bat. We're gonna talk about this. What are some of the trends you're seeing when it comes to application migration? You've done, I'm assuming at this point, thousands of them, what are some of the common trends? >>Well, it's a very good question. And clearly ACL we've helped thousands of clients move tens of thousands of applications to what we would call a cloud native, um, you know, environment. I think the overwhelming trend that we're seeing of course is clients realize it's a particularly complex, sophisticated journey. It requires a certain set of skills and capability clients increasingly us for anything that we can do to simplify and accelerate the journey, cuz what's really important to clients. If you're on a transformation journey to cloud is you wanna see some value very quickly. So I don't wanna wait three to five years to transform my applications portfolio. If you can do something in three to five days, that would be perfect. Thank you. >>Well, three to five days, that sounds more akin to when we were doing, uh, P to V or V to V migrations. I'm sure. Uh, HCL is at this point done in the millions of those types of migrations. What are some of the challenges or the nuance in doing a traditional migration from a traditional MI monolithic application to a cloud native? >>Well, it's another good question. Of course you notice that there's a general trend in the industry. Clients don't really want to lift and shift anymore. Lift and shift doesn't really bring any transformational value to my, to my company. So clients are looking for increasingly what we could recall, cloud native modernization. I want my applications to really take advantage of the cloud native environment. They need to be elastic and kind of more robust than maybe before now in particular, I think a lot of clients have realized that this state of Nirvana, which was we're gonna modernize everything to be a cloud native microservices based application. That is a tremendous journey, but no client really has the time patient or resources to fully refactor or rearchitect all of their applications. They're looking for more immediate kind of impact. So a key trend that we've seen of course is clients still want to refactor and modernize applications, but they're focusing those resources on those applications that will bring greater impact to their business. >>What they now see as a better replacement for lift and shift is probably what we would call replatforming, where they want all of the advantages of a cloud native environment, but they haven't necessarily got the time to modernize the code base. They wanna refactor to Kubernetes in re replatform to Kubernetes in particular, and they want us to take them there quickly. And that's why, for example, this week at cuon eight sellers announced a new set of tools called KMP based on conveyor, an open source project supported by red hat. And the key attraction of KMP is it lets me replatform my applications to Kubernetes immediately, right? Within two or three minutes, I can bring an application from a legacy platform directly onto Kubernetes and I can take it straight into production. That's the kind of acceleration that clients are looking for today. Isn't >>That just a form of lift and shift though? >>Well, no lift and shift typically of course, was moving virtual machines from one place to another. You know, the focus of Kubernetes of course is containerization of solutions. And it's not just about containerizing the solution and moving it. It's the DevOps tool chain around the solution as well. And of course, when I take that application into production in a Kubernetes based environment, I'm expecting to operate it in a different way as well. So that's where we see tremendous focus on what we would call cloud native operations clients expecting to use practices like site reliability engineering, to run these replatformed applications in a different way to, so >>It sounds like you're saying, I, I mean, replatforming has been a, a spectrum of options. I think Gartner has seven different types of re-platforming. Uh, are you seeing clients take more mature attitude now toward replatforming? Are they looking more carefully at the characteristics of their legacy applications and, and trying to try to make maybe more nuanced choices about what to replatform, what to just leave >>Alone? I think clients and I I'm sure Ramon's got some comments on this too, but clients have a lot more insight now in terms of what works for them. They they've realized that this, this promise of maybe a microservices based applications estate is a good one, but I can't do that for every application. If I am a large enterprise with several thousand applications in my portfolio, I can't refactor everything to become microservices based. So clients see replatforming possibly is a middle ground. I, I get a lot of the advantages from a cloud native environment. My applications are inherently more efficient, hopefully a lot more performance. >>Yeah. It's, it's a matter of software delivery performance. Yeah. So, uh, legacy workloads will definitely benefit from, uh, being brought into Kubernetes in the software delivery per performance department. So, uh, it's a matter of, uh, somehow Rebump your, your legacy applications and getting the benefits in, in life's application, life cycle management, a, uh, full tolerance and all that stuff. It's about leveraging the, what Kubernetes offers. >>When you say bringing legacy applications into Kubernetes. It's not that simple, right? I mean, what's involved in doing that. >>It, it, isn't, it's just a matter of taking a holistic view at your application portfolio and understanding the nuances of each application type within your organization and trying to come up with a suitable migration strategy for each one of these application types. And for that, what we're trying to do is provide a series of standardized, um, tools and methodologies, uh, from a community perspective, uh, we created this conveyor community. Uh, it, it was kick started by red hat and IBM, but we are trying to bring as many vendors and GSI, uh, as possible to try to set up these standards to make these, uh, road towards Kubernetes as easy as >>Possible. So we've done a little bit of, uh, app modernization in the CTO advisor hybrid infrastructure. And one of the things that we've found, there's plenty of Avan advantages. If I take a monolithic application that has, uh, that I've traditionally had to scale off to, uh, game performance, I can take selective parts of that, and now I can add auto-scaling to it. Exactly. However, as I look at a landscape Allen of thousands of applications, uh, I need to dedicate developer resources to get that done and my traditional environment, but my traditional environment is busy building new. My traditional or my developers are building new applications and new capabilities. I just don't have the resources to do that. How does HCL and red hat team together to kind of fast track that capability? >>Well, um, I'll comment on two things in particular, actually the, the first thing when it comes to skilling, I think the thing that's really surprised us at HCL is so many of our clients around the world have said, we are desperately short of skills. We cannot hire ourselves out of this problem. We need to get our existing developer community re-skilled around platforms like OpenShift, conveyor, and other projects too. So the first thing that's happened to us at eight still is we've been incredibly busy undertaken, probably what we would call developer workforce modernization, right, where we have to help the client reskill their entire technical and developer community to give them the skills, right. So we will help the clients develop a community, build the cloud native understanding, help them understand how to modernize tools for example, uh, or applications. But the second thing I mention is, and this comes back to a comment that Ramon made around around conveyor. >>It's been really encouraging to see the open source community start to invest in building the supporting frameworks around my kind of modernization journey, because if I'm a developer that's re-skilling and I'm attempting to maybe modernize an application, being able to dip into an open source project, I mean, a good example would be tackled part of the conveyor project. Exactly. You now have open source based tools that will help you analyze your applications. They will go into the source code and they will give the developer guidance in terms of what would be effective treatments to undertake. So perhaps a development team that are new to this modernization journey, they would benefit from a project like conveyor, for example, because I need to know where can I safely modernize my application now for experience organizations like HCL that comes naturally to us, but for people who are just starting this journey, if I can take an open source tool like tackle or the rest of the conveyor, for example, and use that to accelerate my journey, it takes a lot of pressure off, off my organization, but it also accelerates the journey too. >>And it's not just a matter of, of tooling. We we're also opensourcing, uh, the, the modernization methodology that we've been using in red hat consulting for years. So this whole conveyor communities, it's all about knowledge sharing on one hand and building a set of tools together, based on that knowledge that we are sharing to make it as easy as possible. >>And what role does red hat play in all that, I mean, is your you've carved out this position for yourself as the, as the true open source company. Is that, does that position you for a leadership role in helping companies make this >>Transition? I wouldn't say we should be leading the whole thing. Uh, we, we kick started it, but we want to get other vendors on board for this thing. One cool thing about the Camira community is that IBM is, uh, opensourcing a lot of their IP. So IBM research is on board. In this thing, we have some really crazy stuff related to a AI being applied to application analysis. We have some machine learning in place. We have very cool stuff that has been sitting on a, on a corner in IBM research for quite some years that now it's being open sourced and integrated in a, uh, unified user experience to streamline the, uh, modernization process as much as >>Possible. So let's talk about the elephant of the room. Uh, HCL was leading the conversation around cloud Foundry circa five plus years ago. And as customers are thinking about their journey to cloud native, how should they think about that cloud Foundry to cloud native or Kubernetes, uh, replatforming? >>Well within the cloud Foundry community, we've, we've been quite staunched supporters of Kubernetes for quite some time, right? It's, it's quite a, a stated intent of the cloud Foundry foundation to, to move across to Kubernetes platform right now that is a significant engineering journey for cloud Foundry to take. Now we're in this position where a lot of large users of cloud Foundry have a certain urgency to their journey. They, they want to consolidate on a single Kubernetes based, okay. Um, infrastructure. We, we see a lot of traction around OpenShift, for example, from red hat in terms of its market leadership. So a lot of clients are saying we would like to consolidate all of our platforms around a single kind of Kubernetes vendor, whether that's red hat or anyone else, you know, quite frankly. So what ATL is doing right now with the tools and the solutions we've announced this week is we're simply accelerating that journey for clients. If I've got a large installed base of applications running in my cloud Foundry environment, and I've also started to invest in standardize on Kubernetes based platforms like OpenShift, most clients would see it as quite a sensible choice to now try and consolidate those two environments into one. And that's simply what we're doing at HCL. We're making it very, very easy. In fact, we fully automated the journey so I can move all of my applications from cloud Foundry into for example, OpenShift pretty much immediately. And it just simplifies the entire journey. >>So the, as we start to wrap up the segment, I like to know customer stories. What, what, how customers either surprised or challenged when they get into, even with the help of an ACL in redhead, why are they seeing the most difficult parts of their migrations? >>Well, my, my simple comment would be maybe complexity, right? And the, the associated requirement for skilled people to undertake this modernization work, right? We spoke about this, of course, in terms of clients now are a lot more realistic. They understand that their ambition now needs to be somewhat tempered by their ability to sort of drive modernization quickly. So we see a lot of clients when they look at their very large global portfolios of applications, they're trying to invest their resources in the higher priority applications, the revenue generative applications in particular, but they have to bring everything else with them as well. Now, a common kind of separation point was we see a lot of clients who might say I'm gonna properly modernize and refactor, maybe five to 10% of my portfolio, but the other 90% also needs to come on the journey as well. And that's really where replatforming in particular kicks in. So, so the key trend again, is, is clients send to us, I've gotta take the entire journey. All right, I've got the resources and the skills to really focus on this much of my application base. Can someone simplify the overall journey so I can afford to bring everything on a cloud native journey? >>So the key to success here is having a holistic view at the application portfolio, segmenting the application portfolio in different application types and ordering the, the priorities of these application types and come up with suitable migration strategies for each one of them is >>Really necess necessary to move everything though. >>Not necessarily no, or, uh, not necessarily. Yeah, absolutely not everything. But, uh, it would make sense. Uh, as we were saying before, it will definitely move, make sense to move legacy applications towards Kubernetes, to leverage all the, uh, software delivery >>That's >>That's project, right? >>It is. If >>You're gonna restructure the application around APIs and microservices, >>That it should be taken the, the way I've seen, uh, organizations succeeding the most in this, uh, road towards cloud native and Kubernetes in general is trying to address the whole portfolio. Maybe not move everything, but try, try to have this holistic view and not leave anything behind, because if you try to do this isolated, uh, initiatives of bringing this or that applications in a, in isolation, you're Def you, you will miss part of the picture and you might be, uh, doomed to fail >>There. Yeah. It's been my experience that if you don't have a plan to migrate your applications to a cloud native operating model, then you're doomed to follow lift and shift examples to the public cloud. Yeah. Whether you're, uh, going to any other clouds, if you don't make that, that operational transition. Last question on operational transition, we've talked a lot about the replatforming process itself. What about day two, uh, at the I've landed to the cloud? What are some of the top considerations for, for compliance, uh, op op observability, just making sure my apps stay up and transitioning my workforce to that model. >>I, I, I think the over, you know, the overarching trend or theme that, that I see is clients now are, are asking for what I would call cloud native operations. Now in particular, there's a very solid theme around what we would call reliability engineering. So think about site reliability, engineering, SRE platform, reliability engineering, PR E. These are the dominant topics that clients and I want to engage, uh, HCL on in particular, because the point you make is a valid one. I've modernized my application. Now I need to modernize the way that I operate the application in production. Otherwise I won't see those benefits. So that general theme of SRE is keeping us really busy. We're busy, re-skilling all of those operations teams around the world as well, because they need to know how to run these environments appropriately too. >>And also being able to measure your progress while your transitioning is important. And that's one of the concerns that we are addressing as well in the premier community with a tool called polars to, to measure, to effectively measure the software delivery performance of, of the organization after the transition has been done. >>And this is a really good point by the way, cuz most, most people think it's a bit of a black art. How do I understand how I modernize my application? How do I understand how I've improved my kind of value chain around software creation and many people thought you needed to bring in very expensive consultants to advise you on these, on these black lives? No, >>Definitely >>Not. But in open source projects like conveyor from, from red hat, the availability of these tools available on an open source model means exactly any engineer, any developer can get these tools off the shelf and get that immediate benefit. >>Well, a flower head of creative labs at HCL at Ramon neon, senior product manager, redhead. Thank you for joining the QPI. Now Cuba alum, uh, you'll have a nice profile like the profile picture on here. Awesome. >>Absolutely. Thank you. >>From Valencia Spain. I'm Keith towns, along with Paul Gillon and you're watching the cue, the leader in high tech coverage.

>>Yeah. Hello and welcome to the Cuba's International Women's Showcase, featuring International Women's Day. I'm John, host of the Kiwi here in California. Great remote guest. She's amazing founder and C e O of Cuba, and great to see you. Okay, thanks for coming on. Um, good to see you. >>You as well. Always a pleasure. You >>know, International Women's Day is the big celebration. We're doing a lot of interviews with great people making things happen, moving and shaking things. Um, but every day, International Women's Day, As far as I'm concerned, it's happening all around the world. But these are stories of innovation, the stories of changes, the stories of transformation for the better. You've been doing a lot of things. Um and I want to get into that. But let's start with your background. Tell us a bit about who you are and what you've got going on. >>Yeah, my background is a little strange. I used to be a maritime archaeologists. So dumb shit breaks for a little bit. That was amazing. I always just It's only partial just because it's actually a bit of truth to it, that learning how to, you know, handle things at depth really does train you to be a C e o. Because you learn to control your breath and and focus on the things that matter and not be so reactive because it's three activity that will panic that will kill you. Uh, always knowing how to reframe. Return to the basics. Um, there's a really good things to hold on to, even in the world of business. Right? So I at some point, ended up doing doing a lot of things. Largely business development, following my time diving and amazing woman. Um, another woman for International Women's Day named Doctor who was a biotech entrepreneur from Japan, stepping down as her role at the helm of her company. Um, and she wanted to launch a space for a young innovators from around the world who are doing amazing work to tackle this very complex challenges we all know exist, um, and figure out a way to give them time and space to do their best work and pursue their their highest visions for change. We decided that we would focus on for-profit companies largely who were using sustainable, scalable business models to pursue both profit and purpose. Um creating a virtuous cycle between the return of money to a company and putting that into to go even further and faster towards, um, solving a problem. Um, so we now have companies over 200 companies from around the world that we have helped support tackling every single, sustainable development goal. Um, and I'm proud to say, you know, particularly related to the subject that fifty-nine percent of our companies have a woman founder or CO-FOUNDER. Um, and 69% of the founder of color. Um, so we're working with entrepreneurs from every every area of the world. Many approximate to the problem that they are trying to solve, so they intimately understand it. Um, and they're doing amazing things. >>Yeah, you can help the great mission. You have a lot of other things going on your helping women encouraging them to your career in the tech sector. Um, good statistics could be better, right? Is higher and better. So, um, what are you guys doing? What, you specifically to help and encourage women to forge their career and tech? >>Yeah. I mean, look, the good news is I do think that it's getting better. I particularly think that we will see the adventure is improving. Um, it takes a while because the companies that have been funded up until now are still working in the biggest amount in the later stages. So I think that percentage hasn't been shifting. But I have to believe that that's a bit of an illusion, and then a couple of years, we're going to start to sea level out. But you know as well as I do that they're pretty poultry statistics in terms of the amount of venture that women like cos. Capture, Um, and the other ways that women are doubted, um, in terms of their ability and potential. Um, so we we love to work with any underrepresented group of entrepreneurs, and there's ways that we do that whether it's helping them sort of find their power and hold space and be confident. And, um, you know, be able to pitch to any room, talk to any investor, talk to any customer but also working to be directed about some of the systemic challenges, both in terms of talking to existing investors and trying to educate them to see the opportunities that they're missing because there is a an economic imperative to them understanding what they're missing. Um, but there's also some things that we're doing in-house to make sure that we're also helping to close capital gaps for all our entrepreneurs. So we actually now have a suite of three capital mechanisms that are entrepreneurs can access on the back end of our incubator, a microphone fund, which is very quick turnaround, small amounts of capital for entrepreneurs who existing opportunities owns, which is a tax destination. Just this in the U. S. But that's meant to be deployed so that they can access capital towards revenue without credit checks, collateral being put up, a slow moving pace of banks and C. D. S s. It's particularly useful for people who may not raise venture. And it's useful for, uh, you know, people who maybe don't have that friends and family check that they can expect similar. We've got a great angel network who look at the best impact deals from around the world. Um, and it doesn't have to be a housing company, just a great venture that's pursuing impact on profit. Um, and then lastly, we're just about to announce that we have a fund of our own on the back end of our incubator that funds only healthy and companies. Um, it's an early stage fund. Um, but watch this space because our pipeline is just increasing your every year. We used to sort of just 16 companies here. Now, we're serving 60 this year, so, um, yeah, it's really exciting. Um, and so obviously, it's really great that, you know, we're going to be able to help scale the impact that we want to see. Uh, ideally a lot. A lot faster. >>Well, you definitely taking control. I remember when we had a few years ago. I think four years ago, you just thinking about getting going and going now with great tailwind. Um, >>and the diversity >>of sources of capital as well as diversity of firms is increasing. That's helping, uh, that we're seeing, but you're also got the back end fun for the housing companies. But also, you've been involved in we capital for a long time. Can you talk about that? Because that's a specific supporting women entrepreneurs initiative. Um, yeah. What's up with capital share? That >>was That was another venture that I-i embarked on with such coz. Um as well as Sheila Johnson and Jonny Adam, Person who runs Rethink Impact. We capital is a group of about 16 women that I pulled together women investors to invest through rethink impact, which is another fun that is looking for impact businesses but predominantly looking for those businesses that are led by women. So this investment group is women supporting women. Um, through the use of deployment of capital, um, they're doing amazingly well. They've had some really stunning news recently that I'll let you dig up. >>I'll definitely thanks for the lead there. I'm gonna go jump on that story. >>Yeah, >>the Okay, Thanks for that lead on that trend, though in Silicon Valley and certainly in other areas that are hot like New York, Boston and D. C. Where you're at, um, you're seeing now multiple years in almost a decade in of the pioneers of these women, only funds or women only firms and your investment. Um, and it's starting to increase to under all underrepresented minorities and entrepreneurs. Right? So take us through how you see that because it's just getting more popular. Is that going to continue to accelerate in your mind? Are their networks of networks. They cross pollinating. >>Yeah, I think you know, it's It's I'm glad to see it. And, you know, it's been a long time coming. I think you know, I think we all look forward to a future where it's not necessary. Um, and you know, funds. Just invest in everyone Until then, making sure that we have specific pools of capital allocated to ensure that that, you know, those entrepreneurs who have not always been equally represented get to pursue their ideas not just because they deserve to pursue their ideas, but because the world needs their ideas. Right. And as I mentioned, there is a business imperative, right? We've got lots of examples of businesses like banks that you wouldn't have gotten a shot just because the investors just didn't understand the opportunity. Um, and I think that's normal. That's human. It happens to everyone. You are successful as an investor largely because you recognize patterns. And if something is, you know, outside of your life experience, you are not going to identify it. So it's very important that we create different kinds of capital run by different types of people. Um, and, uh, and you know. I know lots of investors have every type that are investing in these funds because they recognize that, you know, perhaps the highest growth potential is gonna come out of these, you know, particular kind of funds, which is really exciting. >>That's super important, because half the world is women, and that's just like the population is inspired by many new ventures. And that's super exciting trend. I wanna ask you about your other areas of doing a lot of work in the queue has been to buy multiple times, um, initially reporting on a region out there, and that's certainly isn't important part of the world. Um, you've got a lot of good news going on there. Can you share what's going on with, uh, the social entrepreneurship going on in Bahrain around the region? >>Yeah, I'm happy to. We we've actually been so privileged to work with a W S for a very long time. Almost since the start of the incubator they've supported are entrepreneurs, all of our entrepreneurs with access to cloud credits and services. Um, and we've sort of double down with a W S in the last couple of years in areas where We both want to create an uplift, um, for small businesses and rapidly growing tax solutions to these these social environmental problems. We see. So there's been an excellent partner to do that. And one of the areas we did in the water was with rain, particularly with women, tech startups, women tech startups in Bahrain. Yeah, we did that last year. We had an amazing group of women over in D. C. Um, and we continue to support them. One of them is actually in the process of raising. I think she just closed her seed round recently. And that's why for, um, al yet, um, and she created playbook, which is an amazing, uh, platform for women to take master classes and network and really sort of level up, as one says, Um, but also, um, the mall of work. Um uh, just really talented women over in Bahrain, um, pushing the envelope and all sorts of directions, and it was wonderful to get the opportunity to work with them. Um, that has now spawned another set of programs serving entrepreneurs in the Middle East in North Africa. They were also working on with us as well as the U S. State Department. Um, so we're going to be working for the next two years with entrepreneurs to help our recovery from covid. Um, in China. Um, and then I'm also proud to say that we're working with a W s in South Africa because there is just an extraordinary energy, you know, in the continent, Um, and some amazing entrepreneurial minds working on, you know, the many problems and opportunities that they're facing and recognizing. Um So we're supporting, you know, companies that are working on finding, um, skilled refugees to be able to help them resettle and use their talents and make money. Um, sadly, are very relevant company now with what's going on in Ukraine. Um, but also, uh, zombie and satellite company, um, companies that are preventing food, food waste by providing, um, solar-powered refrigerators to rural areas in South Africa. Um, so a lot of, um, you know, just incredible talent and ideas that we're seeing globally. Um, and happy to be doubling down on that with the help of a W s. >>That's awesome. Yeah, following the work when we met in D. C. And again, you always had this international view um it's International Women's Day. It's not North America >>Women's Day. It's >>International Women's Day. Can you share your thoughts on how that landscape is changing outside the U. S. For example, and around the world and how the international peace is important and you mentioned pattern matching? Um, you also, when you see patterns, they become trends. What do you see forming that have been that that are locked in on the U. C they're locked in on that are happening that are driving. What are some of those trends that you see on the international side that's evolving? >>Yeah. You know, I think the wonderful opportunity with the Internet and social media is that, you know, both, uh, we can be more transparent about areas for improvement and put a little pressure where maybe things are moving fast enough. We've all seen the power of that, Um, the other, um, you know, things that certainly in countries where women maybe as free to move and operate, they can still acquire skills education they can set up cos they can do so so much. Um, you know, through these amazing technologies that we now have at our disposal growing an amazing rates. Um, they can connect via zoom. Right? I think that while the pandemic definitely set women back and we should acknowledge that, um, uh, the things that the pandemic perhaps helped us to exponentially scale will move women forward. And perhaps that's the target to hang on to, to feel optimistic about where we're headed. >>And also, there's a lot of problems to solve. And I think one of the things we're seeing you mentioned the Ukraine situation. You're seeing the geopolitical landscape changing radically with technology driving a lot of value. So with problems comes opportunities. Um, innovation plays a big role. Can you share some of the successful stories that you were inspired by that you've seen, um, in the past couple of years. And as you look forward, what What some of those innovation stories look like? And what are you inspired by? >>Yeah. I mean, there's so, so many. Um, you know, we just, uh, had a couple of entrepreneurs, and just the last year, Um, you know, after I think everyone sort of took an initial breath with the pandemic, They realize that they either had an opportunity or they had a problem to solve to your point. Um, and they did that well or not. And or some of them, you know, just didn't didn't have any more cards to play and had to really pivot. Um, it was really interesting to see how everyone handled handled that particular moment in time. One company that I think of is everywhere. Um, and she had created a wearable device that you can just put on your ear. It looks like an earring right at the top of your ear. Um, and it was for her for herself because she suffered from pulmonary complications. And, uh, without more discreet wearable, you know, had to wear a huge device and look around and oxygen tank and, you know, just to sort of have a good quality of life. Um, it turns out, obviously, during covid, that is a very useful item, not just for patients suffering from covid and wanting to know what their oxygen levels were doing, but also potentially athletics. So, um, she's really been able to double down as a result of the trends from the pandemic. Um, and I'm really proud of part of her. And that's actually where another great one that we just just came through. Our last 15 is Maya. Um, and she had a brick and mortar store. Um, uh, called Cherry Blossom. Intimate where she helped women have an enjoyable experience finding, uh, and fitting bras post mastectomy to include sort of, you know, the necessary, um, prosthetics and things like that. Um, she even made it so that you could go with your friends who haven't had a mistake, and she could also find some lovely luxury. Um, but the pandemic meant that that experience was sort of off the table. Um, and what they did was she decided to make it a technological one. So now she's she's essentially will be part of it. You can, you know, go to my, um, online. And you can, um, you know, order, uh, measure yourself, work with a specialist, all online, get a few different options, figure out the one that's perfect for you and the rest back. Um, and I don't think without the pandemic, that would not have happened. So she's now able to serve exponentially more. Um, you know, women who deserve to feel like themselves post it to me. >>That's also a model and inspirational. I have to ask you for the young women out there watching. What advice would you share with them as they navigate into a world that's changing and evolving and getting better with other women, mentors and entrepreneurs and or just an ecosystem of community? What advice would you give them as they step into the world and have to engage and experience life? >>Yeah, gosh, part of me always wants to resist that they don't listen to anyone to do you follow your heart, follow your gut, or at least be careful who you listen to because a lot of people will want to give you advice. I would >>say, Uh, that's good advice. Don't take my advice. Well, you've been a great leader. Love the work, you're doing it and I'll say N D. C. But all around the world and again, there's so much change going on with innovation. I mean, just the advances in technology across the board, from with machine learning and AI from linguistics and understanding. And I think we're going to be a bigger community. Your thoughts on as you see community organically becoming a big part of how people are engaging. What's your what's your view As you look out across the landscape, communities becoming a big part of tribes. What's your vision on how the role of communities place? >>You know, we we actually do you think a lot about community and healthy. And we say that are you know, alchemy really is providing space, you know, physical and mental space to think, um, access access to capital access to networks, Um, community, Um, and the community piece is very, very important. Are entrepreneurs leave us like the number one thing that they miss is being among like-minded, um, you know, slightly slightly crazy audacious people. Um, and I often joked that we're building a kind army because it is, you know, it's people who want to do it differently if people want to do it with integrity. Is people who are in it for a very different motivations than just money. Um, and, you know, you start to feel the power of that group together and its entirety and what that might look like as as a community solving global problems. Um, and it really is inspiring. Um, I do think that people are starving for FaceTime and people time, real human time after the pandemic, I think they won't go away. It's a great tool, but we all want a little bit of that, and I will mention just along those lines. And if you don't mind a quick plug for an event that we're having March 16, Um, also in partnership with a W s called Build her relevant to International Women's Day as well. People can, either. If they're in the city, they can come in person. But we also have a virtual program, and we'll be listening to some of the most inspiring. Women leaders and entrepreneurs both in government and also the private sector share their knowledge on the side of the pandemic for for, you know, the next tribal group of women entrepreneurs and leaders. >>That's great. Well, you are on our website for sure. >>Thank you. Thank you. Appreciate it. >>And we love the fact that you're in our community as well. Doing great work. Thanks for spending time with the Cube and on International Women's Day celebration. Thanks for coming on and sharing. >>Thank you, John. >>Okay. The Cube International showcase Women's Day, featuring some great guests all around the world, Not just in the U S. But all over the world. I'm your host. Thanks for watching. Yeah, Yeah, yeah, hm, Yeah.

>>Yeah. Hello and welcome to the Cubes Presentation of Women in text. Global event Celebrating International Women's Day I'm John for a host of the Cube were with Sally E. Senior Policy Advisor Global Foundation for Cyber Studies and Research. Sally, great to see you. Thanks for coming on the cue for International Women's Day. Appreciate it. >>Pleasure, John. Great speech again. >>Love your title. Global Foundation for Cyber Studies. Um, global is a big part of the theme this year. Uh, cyber studies. We're seeing a lot of cyber activity all around the world, networks, communities coming together, the role of data. I mean, everything is touching our lives. There are no boundaries anymore. What does it all mean? There's so much to talk about your in the middle of it before we get into it. Tell us about your career and your history. How you got interested in tech and what you're working on. >>Absolutely. I love it. Kind of this age of convergence coming together right now, isn't it? That's how I would describe it. And that's kind of a bit like my career. I think in many ways as well. So for the audience, really great to be here and share about that today, and I kind of say, three main palace, so one would be emergent technologies. So, you know, I started off right through from coding to advisory to CTO type roles as well also change management. And now I'm more advisors right across from a I to five G to to Iot and security, for example as well. Also passionate about education checking education for me. They always go hand in hand, some a professor at a number of universities and in my non for profit, we really do a lot of outreach around educational opportunities as well. And that third pillar opponent hinted at it already will be social impact. So really passionate about how we can use tech as a force for good things around sustainability right at the heart of that, but also around diversity equity and inclusion. So we do a lot of pro project your locally and globally around kind of reframing what a tech career looks like, giving people more democratised access. Those tech opportunities outside of that a bit like yourself, you know, podcast host and writer and speaker and things as well, so very much going to building that community around key tech topics. >>Well, folks watching should check it out on Twitter. She's that great content you mentioned Mobile World Congress. Before we get on camera, you mentioned convergence. I mean, we're at a time now. I got to ask you while I got you here before we get into the whole schools and career tech thing, we've seen this movie before, but never at this scale. The convergence and the confluence of education and scale of cloud computing, the ability to level up and get, um, I won't say democratised. That's kind of overused. But I'm just talking about like with cloud computing could be educated and in market with a job instantly. Um, the barriers just seem to be moving away because of the the openings and the roles are changing. So, more than ever, this whole new tech scene comes together in a way. Can you share your thoughts and vision because to me, we're seeing this happening at such a scale unprecedented in my career? >>It is. And that's one of those words that the part had been overused, unprecedented, but right now it really, really is. It's not just a speed of change. I think it's a scale of change as well. You know, I think previously we've talked about disciplines in silos to a certain extent. Haven't we know in terms of like, an AI special is, um or five g one or other disciplines as well? But really, now that convergence about what one tech enables another, it really is that smart technology coming together for more and more different use cases, but that residents around how important education is alongside that alongside process alongside culture and shared values as well it really is. It's kind of holistic integration of everything that matters at the moment. And it's evolving business models as well. You know, shared values rights centre stage around that MWC just come back from that, And the key topics there weren't just by G, it was the importance of ecosystem collaboration. For example, there are less tracks that were isolated on one technology. It was more this conflation of these different technologies coming together and what we can achieve from that from business but also for society so really exciting focus areas now things that maybe once or a few years ago, more than periphery. They're now absolutely centre stage. So it's good to see that progress in that area. And I love to advocate around that. >>And the education piece is so important, and we always stay here in Cuba. It's a data problem, right? Everything's a data problem when you look at schools and education is structured and unstructured data kind of our our systems right, So structured as schools, institutions, those kinds of career paths or education pathways. And then you haven't structured freeform communities, seeing a lot more education going on within groups. Um, off structured environments like schools, Can you and you do a lot with schools? Can you share more how you're doing? Um uh, work with schools specifically on the structured side to get girls into careers faster and tech? And then can you also comment on the other side? What's going on in the communities because it's it's kind of going on in parallel, but they're not mutually exclusive. >>No, absolutely community, absolutely key word that I love that, and I think when we're talking about diversity and technology, it's not just what we're doing now with what we're looking at is looking ahead, but also looking at future pipeline as well. So for me, I use this express a little bit. But change the narrative. That's what springs to mind for me when we're talking about that, and particularly for girls going into technology but also more broadly, diversity of experience. More broadly, we do have these drop offs, so UK is one example, but it is really representative of the global trends that we're seeing. Now. We get a drop off of girls in particular, taking ice subjects at GCSE level so kind of that subject choice choice at 12 to 14, that kind of area. We get the same thing at a level that's equivalent of 16 to 18 and then even safer university or even apprenticeships, whichever both equally valid. But even if people are taking those types of skills, they're not then choosing to apply them in their careers. So we're seeing these kind of three pillars where we need to intervene earlier. So for me, the more that we can do things you know from dedicated educational offers, but equally partnering with tech companies to do outreach around this area. We need to go in younger and younger is so important to address that. Why? Why are people thinking they can't? Why is his career not for me, for example, so addressing that is huge. And that's one of the things we do with my nonprofit that's called aspirational futures. We go into schools and two universities, but equally do things with older adults and re Skilling and up Skilling as well. Because again, we can't leave that behind either. There's something for all different kind of age groups and backgrounds here, but specifically, I think, in terms of getting people interested in this career, curiosity matters. You know, I think it's an underrated skills. So it's changing the narrative again. And what the tech career actually is, what skills are valid? You know, I mentioned, I have a coding background as a starter. But not all tech careers involve coding, particularly the rise of low code or no code, for example as well. So really valued skill. But so many other skills are valid as well, you know, creativity or emotional intelligence problem solving skills. So for me, I like to drive forward. All those skills can make a difference as an individual, as a team, so your you know your tech career. All those skills are valid and you can make a huge difference. And I also think, you know, just kind of really bringing to the fore what different types of projects you can be involved in in tech as well. And I found really resonating when you can talk about tech for good projects and show how you're making a difference about some of those big challenges. Um, that's kind of really kind of resonating responsible people as well. So again, the more we can show tangible projects where you can make a difference and the whole range of skills that are involved in that it really helps people to think differently and gain that skills confidence. So it's like, >>Well, that's awesome insight. I want to just double click on that for a second, because one the drop off. Can you just repeat the ages where you see the drop off with the drop offs are >>absolutely yeah, no problem, John. So it's kind of when you're making your first choices around your first kind of qualifications. Between that 12 to 14 age group, 16 to 18 and then 18 to 21 I think we've really got to tackle that So again the earlier we can go in the better and again supporting people within organisations as well. So I do a lot of work like internally, with organisations as well people looking to up skill and re skill. You mentioned about data and the importance of data literacy earlier on in the conversation as well. For example, going into organisations and really helping to support people in all roles, not just tech facing roles develop that skills, confidence as well. So for me it's access to skills really bringing forward the difference. You can make that holistic range of skills that makes a difference, but also the confidence to apply them as well. You know, we talk about agility, of organisations, a lot areas, one of those kind of words in the last 12 months. But maybe we don't talk about personal agility and team agility as well. So I kind of talked about it. This little toolbox, if we can give people more and more things to draw from it, the only constant is this rate of change. If you've got more things in your armoury to cope with that and be an agile to that. It takes that fear away about what happens next because you feel you've got more skills to dip into it and to apply. So for me, it's that that confidence, not just the access to the skills >>and the other thing, too, I thought was insightful. I want to just reiterate and bring to the surface again as skills, right? So you don't have to be a coder. And I see I have two daughters just with my family. Yeah, I do python. They kind of put their toe in the water cause it's cool. Maybe that's a path, and they kind of don't like, maybe get into it. But it's not about coding anymore because you said low code, no code. Certainly. Maybe AI writes the code. We all see that happening. It's problem solving. It's you could be in health care and you could be nerd native, as we say, as on some of the other interviews of that year at the problem, solving the aperture of skills is much broader now. Can >>you share more than >>more than because with your with your programme and your nonprofit, I know you're in the middle of it, and this is important to get that out there. >>Absolutely so skills. You know, I think we need to change the focus on what skills make a difference if you see what I mean. I think you're absolutely right. There's some misconceptions about, you know, you want to go into tech, you need to be a coda. And you're right with the upscale around low Skilling. Sorry, Low code and the code opportunities. Um, I think the niches around being a specialist. Koda. We're gonna get more roles in that area, but in other areas, we need to look at different skills gap. So I'm advising people to look at where the gaps are now. So cyber security is a key example of that testing architecture. Those gaps are getting bigger. Their amazing skills, opportunities. They're so focused on a particular discipline. But it's all those skills that surround that that make a difference as well. So as I mentioned, you know, e Q creativity, communication skills, because it's not just about having the skills to build the future, knew that imagination to refocus about what that could even be. You know, that was one of the MWC 20 to refrain, reimagine and I love to kind of galvanise that spirit and people that you can be part of that, you know, wherever you are now. And I actually run a little series called 365, and you mentioned something right at the start of our conversation about International Women's Day being such an important focus area. But also we need to think about this beyond that as well. So hence that's the title of the series that I run because it's a focus on that every single day of the year. You know, I interviewed people that could be a C suite roles, but equally I've had some amazing interviews with 12 to 14 year olds, even younger, the youngest of the seven year old. He's doing like an amazing project in their kitchen with a three D printer working with local school or a hospice doing something around Ukraine. Another project we're doing at the moment, actually, and it's so resonating it's trying to show people wherever you are now, wherever you want to be, there's somebody relatable that you can make. You can see whatever sector, in whatever age, whatever background, and I think it's to give that inspiration. Hey, you know what I can do that that can be me. So visibility of role models, it really matters. And to really broaden out what role model looks like, you know? >>And then I think people out there you see yourself. I mean, this is what we been >>proven right? >>It's proven I want to get into the aspirational futures thing that you have going on, and I know this is important to you, but also something else you said was, is that there's more jobs open and say cybersecurity than ever before. And you're seeing this trend where all these new roles are emerging because of the tech that weren't around years ago, right? And so we've been having conversations in the Cube saying, Hey, all these roles are new, but also problems are new to these New new problems are surfacing because of the this new environment we're in. So these new roles still have to solve problems, so we need people to solve those problems. This is the future. This is the conversation that people are trying to get zero in on misinformation, cybersecurity, you name it. Society is changing with >>new. You >>have new new problems and new opportunities. Could you share your aspirational future? How you vector into that? >>Yeah, absolutely. And for me it's just again that we're convergence around people in technology and partnership, and that's what we aim to do. We do projects at a very local level, but equally we do them at national and international level as well. And one of our kind of people assume I'm talking pillars a lot, but I like it as a framework. So one of those esteem learning. So putting an equal value on the arts as well as science, technology, engineering, mathematics because I think they are. You know, as I mentioned before, hand that imagination, creativity, curiosity, collaboration, skills. They're equally valid as a different types of tech skills as well. We need an equal value and all of them. I think that's hugely important, important today. I think over the last 5 to 10 years, maybe there's been less of a focus within curriculums on the arts area than the other areas. So for me, putting that equal focus back is hugely important to navigate change, you know, I think that's that's that's absolutely key. So we focus on that area and we do a whole range of tech for good projects, and that's the way we help people to learn, you know, for example, data 90% at the moment of data isn't touched again when it's archived after three months. How can we turn that into a learning opportunity? For example? Some of the projects we use some of this is not going to be used again. We do it in a very safe, secure way, but we use that as one of our training aids, and then we apply them for local projects. We have initiatives from hackathons and ideation right through to very tangible hubs that we've actually built out where people can go, learn up skill and kind of learn through play and experimentation as well. Because again, I think that sometimes under explored that type of value and that freedom to be able to do that. And we also do things, change management skills. We talk about agile learning, agile technology need agile change management as well. So it's a very holistic skills. Look at what you need to navigate that future and have the confidence to apply them. So steam is very much our focus, applying them for tech for good projects and doing that externally, but also within organisations as well. So that very much is shared value approach to good business, but good for society as well. So yes, that this toolbox, that technology I applied earlier we really try and give people that support. To be able to do that, to move forward with confidence and optimism. >>I think adding the aid to stem really for steam is really smart because entrepreneurship or any problem solving creativity is the spark of innovation. >>And that's a super >>important skill. And we've seen it, whether it's startup or in a big company or in society, so super, super insightful. So I got to ask you, as a policy senior policy advisor on cyber studies globally, what are the core issues you're looking at right now? What are you shutting the light on and what's the most important thing you're working on? And then what's the most important thing you're working that people aren't talking about, that people should pay attention to >>Absolutely so. One of my key roles of the foundation is is kind of share of global trust. Essentially, um, and again trust is that one of the key issues of our time? One thing that people are talking about so much that relates with that actually is there's there's research from a group called The Woman. They've been looking at this for about 17 years or so. The research that came out most recently and I've got some original research that kind of support this as well is that for the first time ever, consumers are looking at organisations like tech organisations and other large organisations, in particular the enterprise level, really, as the bastions of trust to a bigger extent than NGOs or even governments. And that's the first time we've seen it at that level. So trust really really matters. It's one of the biggest differentiators of our time, so we're trying to help people. How do you establish trust? How do you build transparency, commitment and accountability, particularly in areas where there's currently confusion, so as one example going back Security zero Trust That phrase is used an awful lot, isn't it? But it's sometimes causing some confusion. Actually, it against what it's trying to deliver if you see what to me. So now I just do something recently with SMB s in particular and there is a confusion that effectively, you know, you could You could buy off the shelf and it's once and done. Um, And then we're sorted for the zero Trust security. And obviously it's not like that. It's an ongoing journey, and there's so many different constituent parts. So there's some things I'm seeing at the moment in the market with there's confusion around around certain language, for example. So again it goes back to backing things up with the technology but also research and awareness so we can see where those skills gaps are. You can see where there's awareness gaps are we can help to fill them. So that's an important part of that particular role bringing the technology in the culture and the education hand in hand together. So it's something I'm really passionate about, and for me sort of related to this, Um, I do a lot of work around S G, um, to the sustainable development goals. In particular, environmental and social governance is something that's becoming much more of a bigger kind of centre stage conversation. I'm an action point in a moment which is fantastic because this is something I've been involved in kind as long as I can remember. So I work directly with organisations like, um Unesco, lots of different professional bodies. It's kind of a huge driver for me. So one thing to kind of look out for that's coming very soon. I'm seeing an issue around around measurement in this area. You know, we're seeing consumers becoming more and more conscious and employees, you know you want to work for by from advocate organisations that have that same value alignment that you have personally and professionally, hugely important. We're seeing some great reports coming out around better e S g measurement. But it can be hard to compare between different organisations, so we are getting more transparency. But it's difficult sometimes to make fare comparisons. Um, so what I'm trying to do a lot of work on at the moment is how you go beyond that transparency to commitment to accountability and that deeper level and that comparability. So I would say kind of to the audience moment, Look out for a bit of a new index. It's going to help people, I think, make those conscious choices make informed choices. So it's something I'm super, super passionate about. I want to try and take that to next level in terms of its actualisation. >>That's awesome. And certainly we'll link to it on our site. All the work you're doing on interviews will put links there as well. We'll make sure we'll follow up on that. Great to have you on. You're such an inspiration. Amazing work, cutting edge work. And I'm I'm super impressed with the cyber studies, and I think this is really important. I have to ask you a final question because you're in the middle of it again with covid and the unfortunate situations we've been living with Covid. And now, obviously with this Ukraine situation that the cyber has been pulled to the front of the agenda and you're seeing a cultural shift. You certainly got Web three. Cyber is now part of everyone's life, and they can see it. They've been seeing it living it. Everything's been pulled forward as a cultural shift happening, okay, and and it's really interesting right now, and I want to get your thoughts because this now people are now aware what cyberwar means cyber security cyber. At home, I have remote work. Cyber has become front and centre or digital. However you want to call it in our lives pulled forward. >>So I'm not even sure in some >>cases, maybe rightfully so, and others. What's your view on this whole cultural cyber being pulled forward? >>It is. It's really, really interesting. And so one of the things I do is I am now ready to a Cyber Insights magazine as well. So we're developing a lot of content pieces around this and lots of things I'm seeing here. So your covid point, I think one of the most interesting things there is around literacy. For example, you remember when we went back to 18 months ago? We're having daily briefings, whether that's from from UK Parliament or the U. S. Equivalent. And different phrases were coming into everyday language driven by the curve or driven by the data. And they're coming into everyday life and people family kitchen table. It was something that hasn't been spoken about before, but suddenly it was driving everyday decision making and what you could and couldn't do. And that's raised awareness. And I think it helped people to ask better questions and to challenge things that they're seeing. And where has that data come from? How has it been presented to have seen that there? I think similarly, where we're having that same understanding and raise of questioning around what we're hearing around cyber as well. You're looking at where that source has come from, and how can we look at that in a different way? So again, I think it's raising that awareness, which is really, really crucial, >>the >>other thing as well around cyber security in particular. And again, I don't think this is talked about as much. When we talk about aspects around inclusion, we talk about diversity equity. Um, I'll see inclusion. I talk about belonging a lot as well. I think there's other aspects around sustainability that Inter relate as well, because when we find, for example, communities that are not included, they tend to be more adversely affected by, for example, climate factors as well. There's an interrelation. They're equally We find that people that haven't got, for example, the same level of cybersecurity protection are also in that same. There's an interrelation across all those elements were not talking about that either. So that's the other thing. I want to kind of bring attention to their again. They aren't separate conversations is a huge crossover between these different conversations and actions that we can do to make a difference. So there's some positive aspects about things that have happened over the last period of time and also some challenges that if we're aware of them, we can work together again, that collaboration piece to be able to overcome them. You know, I've got I've got a book coming out, all for charity called Tech for Good and one of my kind of tag lines. There is around contagion of positive change. Again, let's reframe the language around what's been happening. And let's kind of put that together is something that's far more positive. >>Language is super important, great >>content here. So >>thanks so much for coming. I really appreciate all the great insight and taking the time out of your busy day to to join us here in the Cube. Women in tech Global Event. Thank you so much. >>My absolute pleasure. Thank you. Thank you all for watching. >>Okay. The cubes presentation of women in text. Global event Celebrating International Women's Day. I'm John for a host of the Cube. Thanks for watching

>>Yeah. Hello and welcome to the Cubes Presentation of Women in Tech Global Event Celebrating International Women's Day I'm John for a host of the Cube. We had a great guest in Cuba. Alumni Veranda re vice president. Commercial sales for Europe, Middle East and Africa. EMEA at AWS Amazon Web service to great to see you. Thank you for coming in all the way across the pond and the US to Palo Alto from London. >>Thank you, John. Great to see you again. I'm super excited to be part of this particularly special event. >>Well, this is a celebration of International Women's Day. It's gonna continue throughout the rest of the year, and every day is International Women's Day. But you're actually international. Your women in Tech had a great career. We talk that reinvent. Let's step back and walk through your career. Highlights to date. What have been some of the key things in your career history that you can share? >>Uh, thanks, John. It's always nice to reflect on this, you know? Look, I the way I would classify my career. First of all, it's very it's been very international. I was born and raised in India I went to study in the US It was always a dream to go do that. I did my masters in Boston University. I then worked in the U S. For a good 17 years across A number of tech, uh, tech companies in particular, started my career at McKinsey in the very early days and then moved on to work for E M. C. You'll you'll probably remember them, John. Very well, of course, There now, Del um And then I moved over to Europe. So I've spent the last 18 years here in Europe. Um, and that's been across a couple of different things. I I always classify. Half my career has been strategy, transformation, consulting, and the other half of my career is doing the real job of actually running operations. And I've been, you know, 12 15 years in the tech and telecom sector had the excitement of running Schneider Electric's business in the UK Denniston and Private Equity went back to McKinsey Boomerang, and then a W s called me, and how could I possibly refuse that? So it's been really exciting, I think the one big take away when I reflect on my career is. I've always had this Northstar about leading a business someday, and then I've sort of through my career master set of skills to be able to do that. And I think that's probably what you see. Very eclectic, very mobile, very international and cross industry. Uh, in particular. >>I love the strategy and operations comment because they're both fun, but they're different ones. Very execution, tactical operating. The business strategy is kind of figuring out the future of the 20 mile stare. You know, playing that chess match, so to speak, all great skills and impressive. But I have to ask you, what got you in the tech sector? Why technology? >>Well, so you know, in some ways I kind of fell into it, John, right? Because when I was growing up, my father was always in the tech space, so he had a business and fax machines and he was a reseller of cannon. If you remember Cannon, um, and microfilm equipment and I grew up around him, and he was a real entrepreneur. I mean, always super visionary about new things that were coming out. And so as I followed him around, I said, I kind of wanna be him. And it's a little bit about that sort of role model right early in your career. And then when I moved to the U. S. To study again, it wasn't like I thought I was gonna go to attack. I mean, I wasn't an engineer, you know. I grew up in India with economics degree. That's when women went into We didn't necessarily go into science. But when I joined McKinsey in the early days, I ended up working with, you know, the big companies of the days. You know, the IBMs, the E M. C. Is the Microsoft the oracles, etcetera. So I just then began to love, love the innovation, always being on the sort of bleeding edge. Um, and I guess it was a little bit just fascinating for me not being an engineer to learn how technology had all these applications in terms of how businesses advanced. So I guess, Yeah, that's kind of why I still think it around with it. It's interesting >>how you mentioned how you at that time you pipeline into economics, which is math. Of course. Uh, math is needed for economics, but also the big picture and This is one of the conversation we're having, Uh, this year, the breaking down the barriers for women in tech. Now there's more jobs you don't You don't need to have one pathway into into science or, you know, we're talking stem versus steam arts are super important, being creative. So the barriers to get in are being removed. I mean, if you think about the surface area for technology. So I got to ask you, what barriers do you think Stop girls and young women the most in considering a career in Tech? >>I've got to start with role models, John. Right? Because I think a number of us grew up, by the way, being the only not having the allies in the business, right? All of us, all the all the managers and hiring people are males rather than females. And the fact of the matter is, we didn't have this sort of he for she movement. And I think that's the biggest barrier is not having enough role models and positive role models in the business. I can tell you that research shows that actually, when you have female role models, you tend to hire more and actually what employees say is they feel more supportive when they have actually female managers. So I think there are lots of goodness, but we just need to accelerate how many role models we have. I think the other things I will say to you as well is, if you look at just the curriculum and the ability to get women into stem, right, I mean, we need to have colleges, universities, schools also encouraging women into stem. And you've probably heard about our programme. You know, it's something we do to encourage girls into stem. I think it's really important that teachers and others are actually encouraging girls to do math, for example, right? It's not just about science. Math is great. Logic is great, by the way. Philosophy is great. I just love what you said. I think increasingly, the EQ and EQ parts have to come together, and I think that's what women excel at. Um, so I think that's another very, very big carrier, and then the only other thing I will say is we're gonna watch the language we use, like when I think about job descriptions, they tend to be very male oriented languages we look at CVS now, if you haven't been a female in tech for a long time, your CV isn't going to show a lot of tech, is it? So for recruiters out there, look for competencies. Look for capabilities. You mentioned strategy and arts earlier. We have this leadership principles, As you know, John, really well, think big and dive deep, right? That strategy and operations. And so I think we we need to recruit for that. And we need to recruit for culture. And we need to recruit for people with ambition, an aspiration and not always Just look at 20 years of experience because you're not gonna find it. So I think those are some of the big barriers. Um, that I that I at least think, is stopping women from getting into town. But the biggest one is not enough women at the top hiring women. >>I think people want to see themselves, or at least an aspirational version of what they could be. And I think that's only gonna get better. Lots changed. A lot has happened over the years, but now, with technology in everyone's life, covid pulled forward a lot of realities. You know, the current situation in Europe where you're you are now has pulled forward a lot of realities around community, cyber, digital, our lives. And I think this opens up new positions, clearly cybersecurity. And I'm sure the job boards in every company is hiring people that didn't exist years ago, but also this new problems to solve. So the younger generation coming up, um, is gonna work on these problems, and they need to have role models. So what's your reaction to that? You know, new problems are opportunities their new so usually solved by probably the next generation. Uh, they need mentors. All this kind of works together. What's your reaction? >>Yeah, and, you know, let me pick up on something we're doing that I think is really important. I think you have to address age on the pipeline problem, you know, because they're just is a pipeline problem, you know, at the end of the day, And by that, what I mean is, we need to have more and more people with the and I'm not gonna use the word engineering or science. I'm going to use the word digital skills, right? And I think what we've we've committed to doing, John, you know, I'm very proud of this is we said we're gonna train 29 people 29 million people around this world on digital skills for free by 2025. Right, That's gonna help us get that pipeline going. The other thing we do is something called Restart where we actually do 12 weeks of training for the under, employed and under served right and underrepresented communities. And that means in 12 weeks we can get someone. And you know, this case I talk to you about this before I love it. Fast food operator to cloud, right? I mean, that's that's what I call changing the game on pipeline. But But here's the other stand. Even if the pipeline is good and we often see that the pipeline can be as much as 50% at the very early career women, by the time you get into the C suite, you're not a 50 anymore. You're less than 20%. So the other big thing John there, and this comes back to the types of roles you have an opportunities you create. We've got to pull women through the pipeline. We've really got to encourage that there are sponsors and not just mentors. I think women are sorry to say this over mentored and under sponsored. We need more people say I'm gonna open the door for you and create the opportunity I had that advantage. I hit people through my career. By the way, they were all men, right? Who actually stood out there and bang on the door and said, Okay, Tunisia is gonna go do this. And my first break I remember was having done strategy all my life when the CEO come into the room and you said, You're gonna better locks and you're gonna go run the P and L in Benelux and I almost fainted because I thought, Oh, my God, I've never run a PNR before But it's that type of risk taking that's going to be critical. And I think we've got to train our leaders and our managers to have those conversations be the sponsors, get that unconscious bias training. We all have it. Every single one of us has it. I think those are the combinations of things that are going to actually help open the door and make a see that Actually, it's not just about coding. It's actually about sales. It's about marketing. It's about product management. It's about strategy. It's about sales operations. It's about really, really thinking differently about your customers, right? And that's the thing that I think is attractive about technology. And you know what? Maybe that leads you to eventually become a coder. Or maybe not. Maybe you enter from coding, but those are all the range is available to you in technology, which is not good at advertising, >>that there's more applications than ever before. But I love your comment about over mentoring and under sponsored. Can you quickly just define the difference between those two support elements sponsoring versus, uh, mentoring sponsoring >>So mentors And by the way they can range from my son is my mentor, you know, is a great reverse mentor. By the way, I really encourage you to have the reverse mentoring going. So many mentors are people from all walks of your life, right? And you should have, you know, half a dozen of those. At least I think right who are going to be able to help you deal with situations, help coach you give you feedback respond to concerns You're having find ways for you to navigate all the stuff you need, by the way. Right? And feedback the gift we need that sponsors. It's not about the feedback. Necessarily. It's people who literally will create opportunities for you. Mentors don't necessarily do that. Sponsors will say you You know what? We got the phone. Call John and say, John, I've got the perfect person for you. You need to go speak to her. That's the big difference. John and a couple of sponsors. It's not about many, >>and that's where the change happens. I love that comment. Good call. I'm glad I could double down on that. Now that you have the environment, pipeline and working, you have the people themselves in the environment getting better sponsors and mentors, hopefully working more and more together. But once they're in the environment, they still got to be part of it. So as girls and young women and to the working sector for tech, what advice would you give them? Because now they're in the game there in the arena. So what advice would you give them? Because the environments they are now >>yeah, yeah. I mean, Gosh, John, it's you know, you've lived your career in this space. It's an exciting place to be right. Um, it's a growth opportunity. And I think that's a really important point because the more you enter sectors where there's a lot of growth and I would say hyper right growth, that's just gonna open the doors to so many more things. If you're in a place where it's all about cost cutting and restructuring, do you know what? It's super hard to really compete and have fun, right? And as we say, make history. So it's an exciting place. Today's world transformation equals digital transformation, right? So tech is the place to be, because tech is about transformation, Right? So coming in here, the one advice I would give you is Just do it because believe me, there's so much you can do, like take the risk, find someone is going to give you that entree point and get in the door right? And look, you know what's the worst that could happen? The worst that could happen is you don't like it. Fine. There's lots of other things than to go to. So my advice is, you know, don't take the mm. The really bad tips I've received in my career, right? Don't let people tell you you can't do it. You're not good enough. You don't have the experience, right? It's a male's world. You're a woman. It's all about you and not about EQ. Because that's just rubbish, Frankly, right. The top tip I was ever given was actually to take the risk and go for it. And that was my father. And then all these other sponsors I've had around the way. So that's that's the one thing I would say. The other thing I will say to you is the reason I advise it and the reason you should go for it. It's purposeful. Technology is changing our lives, you know, And we will all live to be no longer. 87 I think 100 right? And so you have the opportunity to change the course of the world by coming to technology. The vaccine deployment John was a great example, right? Without cloud, we couldn't have launch these vaccines as fast as we did. Right? Um, so I think there's a tonne of purpose. You've got to get in and then you've got to find. As I said, those sponsors, you've got to find those mentors. You've got to not worry about vertical opportunities and getting promoted. You gotta worry about horizontal opportunities, right? And doing the things that I needed to get the skills that you require, right? I also say one thing. Um, don't Don't let people tell you not to speak up, not to express your opinion. Do all of the above be authentic, Be authentic style. You will see more role models. Many, many more role models are gonna come out in tech that are going to be female role models. And actually, the men are really stepping up to the role models. And so we will be better together. And here's the big thing. We need you. We can do this without women. There's no possible way that we will be able to deliver on the absolute incredible transformation we have ahead of us without you. >>Inclusion, Diversity equity. These are force multipliers for companies. If applied properly, it's competitive advantage. And so breaking the bias. The theme this year is super super important. It sounds like common sense, but the reality is you break the bias It's not just women as men, as all of us. What can we do? Better to bring that force multiplier capabilities and competitive advantage of inclusion, diversity, equity to business. >>So the first thing I would say and my doctor used to always tell me this if it hurts, don't do it right. I would say to you just do it. Get diverse teams in place because if you have diverse teams, you have diversity of thought. You don't have to worry as much about bias because, you know, you've got the people around the table who actually represent the world. We also do something really cool. We have something called biassed busters. And so in meetings we have bias borders. People are going to, like, raise their hand and say, I'm not sure that that was really meant the way it was supposed to be, So I think that's just a nice little mechanism that we have here, Um, in a W s that helps. The other thing I would say to you is being your authentic self. You can't be a man and mentioned be women, and you're not gonna replicate somebody else because you're never gonna succeed if you do that, you know? So I would say be your authentic self all of the time, You know, we know. We know that women are sometimes labelled as aggressive when they're really not. Don't worry about it. It's not personal. I think the main thing you have to do is and I advise women all the time Is calibrate the feedback you're getting okay? Don't catastrophizing it right. Calibrate it. Taken in, you don't have to react to every feedback in the world, right? And make sure that you're also conscious of your own biases, right? So I think those are my Those are my two cents John for what they were for breaking device. I love the thing. >>Be yourself, You know, Don't take it too personal. Have some fun. That's life. That's a life lesson. Um, Final question, while I got you here, you're a great inspiration, and you're a great role model. You're running a very big business for Amazon web services. Europe, Middle East and Africa is a huge territory. It's its own thing. It's It's like you're bigger than some companies out there. Your role in your organisation. What's the hot area out there you were talking before camera. That's emerging areas that you're focused on. People are watching this young women, young ladies around the world. We're gonna look at this and say, What wave should I jump on? What's the hot things happening in in Europe? Middle Eastern Africa? >>I think the three things I would mention and I'm sure there's I'm sure, John, as we've spoken to my peers across the other gos, right, there are some similarities. The very, very hot thing right now is sustainability. Um, and you know, people are really building sustainability into their strategy. It's no longer sort of just an E S G goal in itself. It's actually very much part of changing the way they do business. So I think that's the hard part. And that's why again, I think it's a phenomenal place to be. I think the other big thing that we're absolutely talking about a lot is, and you know, this is getting even more complicated right now is just around security and cyber security and where that's going and how can we be really thinking about how we address some of these concerns that are coming out and I think there's There's something. There's a lot to be said about the way we build our infrastructure in terms of that context. So I think that's the second one. I think the third one is. People are really looking at technology to change the way businesses operate. So how does HR operate? How do you improve your employee value proposition? How do you do marketing in the next generation? How do you do finance in the next generation? So across the business is no longer the place of I t. It really is about changing the way we are as businesses and all of us becoming tech companies at the core. So the big thing there, John, is data data at the heart of everything we do data not because it's there in front of you, but data because you can actually make decisions on the back of it. So those are the things, Um, I seem to come across a lot more than anything else. >>It's always great to talk to you, your senior leader at AWS, um, inspirational to many. And thank you for taking the time to speak with us here on this great event. Women in text. Global Celebration of International Women's Day. Thank you so much for your time. >>Thank you, John. Always great to talk to you. >>We will definitely be keeping in touch More storeys to be had and we're gonna bring it to you. This is the cubes continuing presentation of women in tech. A global event celebrating International Women's Day. I'm John for your host. Thanks for watching. Yeah.

>>Here you are new. Welcome back to the cubes. Continuing coverage of AWS reinvent 2021 live from Las Vegas. Lisa Martin, with John farrier, John, we have two live sets. There's a dueling set right across from us two remote studios over 100 guests on the cube at AWS reinvent 2021. Been great. We've had great conversations. We're talking about the next generation of cloud innovation and we're pleased to welcome one of our alumni back to the program. Lisa Bernays here, the CEO and co-founder of D L Z P group. Lisa. Welcome. >>Hi, thank you. I appreciate the opportunity to be here with you and John. It's a great opportunity >>And John's lucky he gets to lease us for the price of London. One second. Talk to me about da DLDP. This is a woman and minority owned company. Congratulations. That's awesome. But talk to us about your organization and then we'll kind of dig into your partnership with AWS. >>Sure. So DLC P group, we found it in 2012. Um, and for us, we were at the time we were just looking for a way to offer a value added service to our customers. We wanted to always make sure that we were giving them the best quality, but what I also wanted to do is I wanted to create an environment for my employees, where they felt valued, and we kind of built these core values back then about respect, flat hierarchy, um, team, team learning, mentorship, and we incorporated, so everybody can do this remotely from around the world. So we've always made sure that our employees and customers are getting the best value. >>Well, what kind of customers, what target market, what kind of customers do you guys work with? >>Well, we've actually made sure that we're diverse. We make sure that we have 50% in public sector and 50% in private sector, but it's been very, very interesting journey for us because once we started one sec, like we started with cities and then a number of cities started contacting us to do more business. So it's always been this hurdle to make sure we're diverse enough to make sure we offer the best solutions. >>And you jumped in with AWS back in 2012 when most folks were still to your point. I saw your interview earlier this summer, thinking about Amazon as a bookstore, why a debit? What did you see as the opportunity back in 2012 with them? >>Well, when we first heard about AWS, my first thought is, well, it's amazon.com. What is AWS? And then once we started talking to them, we saw the capabilities and the potential there. We saw what it could do. So we partnered with them to actually have the first working PeopleSoft customer on AWS. So that's a large ERP application and that helped build the foundation to prove what could actually run on the cloud. And since then, we've been able to prove so much more about the technology and what AWS is accomplishing. >>Was it a hard sell back in the day? >>It was a little bit hard, but it was interesting because we were speaking with one of our customers they're on premise and they're like, well, you know, we're going to have to re do a whole data center. We're talking about millions of dollars. We don't really have the budget to redo this. And that's when we're like, well, we have this great partnership with Amazon. We think this would be the perfect opportunity to let you try the cloud and see how successful it was. >>At least I want to point out you got your, one of the Pathfinders that Adams Leschi pointed out because back in 2012, getting PeopleSoft onto the cloud, which is really big effort, but that's what everyone's doing now. I just saw the news here. SAP is running their application on graviton too, right? So you start to see and public sector during the pandemic, we saw a ton of connect. So you were really on this whole ERP. ERP is our big applications. It's not small, but now it's, everyone's kind of going that way. What's the current, uh, you feel how you feel about that one? And what's the current update relative to the kind of projects you got going on? >>Well, we've, we've evolved quite a bit. I mean, PeopleSoft is always going to be in our DNA. A lot of my employees are ex or Oracle employees. They have developed a lot of the foundations for PeopleSoft, but since then, like we've worked with serverless technology when that was released a number of years ago, we, we asked our team, okay, AWS just talked about Lambda, serverless technology, go figure out what is the best solution. We ended up running ours, our website serverless. We were one of the first. And from that, we brought our website costs down from hundreds of dollars to pennies a month. So it's a huge savings. And then we started, um, about two years ago, we spoke with our utility company. Um, there were saying how with machine learning, they were only going to be able to get a 75% accuracy for their wind turbines. And we said, well, let us take a shot at it. We have some great solutions on AWS that we think might work. We were able to redo their algorithm using AWS cloud native tools, open source data to get a 97 to 99% accuracy on a daily basis. And that saves them millions of dollars each day. >>Don's right. And as Adam was saying with some of the folks, customers, he was highlighting on main stage the other day, you are a Pathfinder. How did you get the confidence? Especially as a female minority owned business. I'd love to just get maybe for some of those younger viewers out there. How did you get the confidence to, you know what? I think we can do this. >>I think for me, I, I, I don't like to take no for an answer. There's always a solution. So we're always looking at technology, seeing how we can use it to get a better answer. >>What do you think about reinvent this year? A lot of goodies here every year, there's always new creative juices flowing because it's a learning conference, but it's also feels like a futuristic kind of conference. What's your take this year? >>I don't know if you happen to attend midnight madness when they were talking about robotics and the future with that. I mean, we've been talking about that for a number of years of what could be created with robotics. Like even my son back in middle school was talking about creating a robot Butler. He just, everybody knows what the future is. And it's so great that we finally have the foundation in technology to be able to create these >>Well, if you're someone that doesn't like to say, no, does your son actually have a robot Butler these >>Days? He's still working on it. >>That's a good answer to say, Hey, sorry, your mom's not going to be there to get the robot. The latency thing. This is the robot. First of all, we'd love the robotics, I think is huge. We just had George on who's the fraught PM for ECE to edge and late, the wavelength stuff looks really promising for the robotics stuff. Super exciting. >>Yes. We can't wait to start playing with it more. I mean, it's something that our team has been dabbling. We spent probably about 30% of our time on R and D. So we're looking at the future and what we can invent next because >>You guys can affect such dramatic changes for customers. You talked about that wind turbine customer going from 75% accuracy to 97, 90 8%. Where are your customer conversations? Cause that's, is, are they at the C level with showing organizations that dramatic reduction in costs and workforce productivity increased that they can get? >>We talk with everyone it's it could be the solution architect. It could be an intern. It could, and we're just sharing our ideas with them. And we also talk with the C level. Um, it's just, it's everybody is interested in and they have different, different ideas that they want to share. So with the solution architect, we can share with them the code and how we're going to architect it. While the C level, we just pointed out black and white, this is your cost. Now this is what your cost is going to be. And everybody is happy. They, they jump on board with it. >>Lisa, you mentioned 30% R and D by the way, it's awesome. By the way, that's well above most averages, what are you working on? Because I totally think companies should have a big R and D play around budget, get a sandbox, going get some tinkering. Cause you never know where the real discoveries we had. David Brown who runs NC to nitro, came out of a card on the network. So you'd never know where the next innovation comes from. What's the, what are you guys doing for R and D? What's the fun projects are what endeavors. >>So there's two of them. One is actually a product, which is a little bit out of our comfort zone, but we're, we're, we're looking to develop something that will be able to help, um, NASA. So that's the goal where, you know, we've been working on it since they released their ma their mission to Mars projection. So it's something that we're very passionate about, but then we're also building a software. Uh, we've been working on it for about three years now and we actually have two customers prototyping it. So we're hoping to be able to launch it to the public within the next year. >>You mentioned NASA and I just about jumped out of my chair. That was my first job out of grad school was really the space program. Can you tell us a little bit more about what you're helping them do? I love how forward-thinking that they are, obviously they always have been, but tell me a little bit more about that. >>So I can't share too much because it's one of those things is a common sense thing. Once you think about a little bit more, it's kind of like why didn't anybody never think about this? So we're using new technology and old technology together to combine the solution. >>Ooh, I can't wait to learn more. Talk to us about these. Think big for small business TB SB program at AWS. How long have you guys been a part of that and what is it enabling? What is it going to enable you to do in 2022? So >>The think big for small business program was the brainchild is Sandy Carter. And I am always, always going to be grateful to her. Um, I met with her in 2019. I shared her journey, our journey with her about how we started out being a premier partner and then over time, because there's so many other partners, we were downgraded. And because just because we're a small business, and even if I had every employee, even my admin staff certified, we would never have enough employees to be to the next level, even though we had the customers, the references. So she listened to us and other small businesses and created the program. And it's been a great opportunity for us because we're, we're gaining access to capital, you know, funding for opportunities. We're getting resources for training. So it, for us, it's been a huge advantage. >>It sounds like a part of that AWS flywheel that we always talk about. John Sandy Carter being one of our famous Cuba alumni. She was just on yesterday with you. Okay. >>And there's so many opportunities for all businesses because you can, you can tackle these problems. You don't have to be a large partner. You can have specialty in AI works really well in these specialized environments. And even technically single-threaded multithreaded applications, which is a technical CS term is actually better to have a single threaded. If you have too many cores, it's actually bad technically. So the world's changing like big time on how technology. So I'm a huge fan of the program. And I think like it's just one of those things where people can get it from cloud and be successful. >>Yes. And that's the goal. I mean, there is so much opportunity in the cloud and we bring interns on all the time, just so they can learn. And what, what resonated with me the most was we brought a high school senior in, he goes, I was with you guys for three months. I learned more in three months, I did four years of high school. And he's like, you set me up for the future. >>Oh my gosh. If there's not validation for you doing in that statement alone. My goodness. Well, you know, some of the things that, that are so many exciting announcements that have come out of this reinvent, so great to be back in person one. Um, but also, you know, being able to help AWS customers become data companies. Because as we were been talking about the last couple of days, every company has to be a data company. You gotta figure it out. If you're, if you haven't by now, there's a competitor right back here, who's ready to take your spot. Talk to us about what excites you about enabling companies to become data companies as we head into 2020. >>Well, for us, everybody has so much data nowadays. You know, I mean even think about cell phones, how much data is stored in that. So each device has so much information, but what do you do with it? So it's great because a lot of these companies are trying to figure out what, how can we use this data to prove that improve the experience for our customers? So that's where we've been coming in and showing them, okay, well, you can take that data. You look at Lisa and John cell phone. You see that they, they love to look up where they're going to go on their next vacation. You can start creating algorithms to make sure that they get the best experience one for the next vacation to make sure it's not a won't Rob the bank. >>Awesome. And going on vacation tomorrow. So I'll be, I'll be expecting some help from you on that. It's been great to have you on the program. Yeah. Congratulations on the success, the partnership, and where can folks go if if young or old years are watching and are interested in working with you, it's the website where they, where can they go to learn more >>Information? So they can go to D L Z P group.com >>DLZ P group.com. Awesome. Lisa, thanks so much for coming back on the program. Great >>To see you. Thank you so much. All >>Right. For John furrier, I'm Lisa Martin and you're watching the cube, the global leader in live tech coverage.

>>Hey everyone. Welcome back to the cubes. Continuous coverage of AWS reinvent 2021 live. Yes. Live in Las Vegas, Lisa Martin, with Dave Nicholson. David's great to co-host with you. How you doing >>Fantastic. Great to be here with >>You, Lisa, as always, we're going to have a great conversation. Next to Cuba actually is two lifestyles, two remote studios. We've got over a hundred guests on the program talking about the next decade and cloud innovation and Dave and I are pleased to welcome Scott Carter, the CTO of TSS to the program. Scott. Welcome. >>Thank you. It's really, really great to be here. Really >>This a little bit. Great to have you on the program. Talk to us a little bit about, about TCIs and let's talk about your kind of journey to the cloud and your relationship with AWS. >>Absolutely. Um, you know, TCIs, we've been around as a company for about 40 years. We specialize in, uh, payment products specifically on the issuing side. So card issuing, we've worked with some of the largest financial brands in the world and retailers as well. Uh, and, and a lot of, you know, what I always tell people is if you have a card in your wallet today, uh, you could probably pull it out. And at least one of those cards is something that we manage and service for our customers. And, and we, uh, do everything full lifecycle of those payment products for our customers around the globe >>On behalf of being a cardholder. Thank you. Talk to me a little bit about the AWS partnership here we are at re-invent. >>Yeah, well, we started a very special, uh, partnership with AWS about 18 months ago. We're about 18 months into the journey, uh, and really our goal and our vision is to build out a financial services cloud for all of our clients and our retailers and fintechs. Uh, we're really focused right now on migrating some of our key products to the AWS cloud environment. We built we've used us a variety of AWS technology by some on-premise and in the cloud environment to migrate our processing platforms and all of our customer servicing systems. So we're in the middle of that journey. Uh, we've had a lot of successes so far. AWS is helping us out. Our engineering team is working side by side with the AWS engineering team to produce what we believe is going to be the next generation of payments, especially on the card issuing side, >>Next gen that's, that's important as a consumers, consumer life business life. We have that expectation that we're going to be able to transact whatever we want anytime day or night, >>Absolutely choice is key, uh, virtual physical, no matter where you are, we want to be able to facilitate your payment and make sure you have everything you need to support you through the full card life cycles, the life cycle of your account. >>So you talk about those cards being in our wallets and handbags. I know there's one that's actually smoking. It's so hot from use in my co-hosts handbag, but, >>Uh, we appreciate that >>Talk, talk, talk about this journey from the perspective of someone who, um, I assume like me is not just out of college, right? You've working, you've been working in this business for a while. And so you're going through the transition from the world of what some will refer to as legacy it into the world of cloud. Uh, talk about the challenges there. How do you go after the low hanging fruit versus the high hanging fruit? How do you evaluate something from an ROI perspective? Talk about that. >>Yeah, and I, you know, uh, I get that quite a similar question a lot. I get, you know, people are, are interested in the journey and especially CTOs and CEOs who were starting journeys at their own. I get a chance to talk with a lot of banks and retailers about their individual like modernization and transformation journeys. Um, and you know, the, the basics are true about the journey. And I had somebody tell me years ago that it's, it's, it's psychology, it's not technology. Uh, you've really got to address the people's side of the equation. First, you've got to focus on training and upskilling, make sure that the team comes along on the journey. And then you've gotta be a really good recruiter. You've got to go out and get the talent, the skills you need to build a good foundation. You gotta have the right partners. >>You know, we have partners like PWC and, and, uh, AWS and others that are really helping us with the journey. So that part of it's really, really important. The key is, and I think for us, uh, we really started building our talent pool, uh, probably more than five years ago. And so we were able to bring in some skill sets in dev ops and some skill sets. And, you know, nowadays AI we'd do a lot with ML and AI skill sets. Uh, but we were able to build in a lot of cloud skills and start to build out our development environments first, very, very early on. That's what we did. And we used those development environments for our engineers to cut their teeth and really get comfortable in the cloud. Um, I remember probably about three years ago, we installed our first Kubernetes cluster. Um, and we did it with a small team. >>And then over time we really incented the team by allowing them to get more and more certifications and grow their skills. And we really built up a really large team around just our on-premise cloud first. And then later that helped us with the migration, the journey into the actual public cloud for those same services. Um, and we use that, that same team as there today, we really invest in our people. We think it's important to have a staff that's there. We insource our staff. We really believe in that. Um, that's super important, even though we have partners that we really value, we make sure that we've got a core group of people that are really passionate about the journey and about cloud. And so that >>You mentioned that, that kind of cultural aspect. Yeah. And you mentioned bringing in a team starting years ago with a specific focus. What about the transition of folks who have been it practitioners for maybe decades making that transition? How has, how has that worked out culturally? Have you adopted a policy where you're basically saying, look, if you have experience with this stuff, great, stay with it. Yeah. But we're hiring net new people for the new stuff. Is that the strategy or is it >>Look like I've seen some do that? I personally don't feel that that works because you need some subject matter experts. You need people who really know your products and your company and your solutions and your customers. You really need those people to come along the journey. So what we've done internally is we created, for example, a digital boot camps where our team members could sign up that could come in. We actually construct the boot boot camps on about a six week schedule. Uh, we do two week sprints. So we do three sprints. We, we get them sort of inculcated and agile from the very beginning, we have demos at the end of each sprint. So they're working in an agile way as they're going through their training course. And then of course we, that gives us a chance to identify people who are really high potential to move into some of our cloud teams and our dev ops teams. >>And so that's been really, really beneficial for us. And I would tell you that today we've got people that have a broad range of skills just because of that digital bootcamp. So they may have started their career doing assembler or COBOL or something like that. But now they've tacked on some dev ops and some cloud skills. Uh, we have some that know dynamo DB, and they also know DB too. And we like that. So they have a broad range and those people bring a lot of deep expertise that you're not going to necessarily get with somebody that you're bringing, you know, new, you know, sometimes straight out of college into your company. You've got to grow those people too, but you need the experience, people there to help develop them. >>No, we often talk about people, process and technology, and it's kind of a phrase that's thrown around right. At every event with every vendor. But I really admire the focus on the people, part that you're talking about there and how it's really essential to enable, to enable the people, how you started very strategically starting with the people in the focus and the training on-prem then making the decision that they've, they've got the foundation. Now we need to migrate to the cloud. I'm curious the why AWS, you have a lot of choice course here we are at reinvent. But talk to me about why AWS is that strategic partner. >>We've, we've looked at a number of different cloud platforms for our business. And in fact, uh, global payments is a large company. So TCIs is sort of the issuing part of that. And so we have really great relationships with GCP and other cloud platforms, even some Azure in certain pockets of the company for the issuing side of the business, we went through a thorough evaluation and we felt like the tools, the technology, the platforms, really the, the maturity of that platform. And then the scale, you know, scale matters in our business. And a lot of businesses, it matters, uh, you know, the locations of all of the, uh, uh, availability zones and the regions that was really important to us. We were able to align all of the different AWS regions to where our customer locations are. And that's becoming more and more important as we, you know, we try to be more flexible now about where we, uh, you know, deploy our products around the globe. We want to make sure that whoever we partner with has a point of presence in those markets and that we can do that very, very quickly. We can stand up a new environment when we need to. And so that's what that's been really beneficial that we made that choice with AWS. Um, you know, there's a lot of cloud platforms out out there there's a lot of choice, but we just felt like AWS was the best for us. >>AWS is also very, very, very customer focused, but they probably would say customer obsessed, really that customer flywheel that generates everything that we'd even heard this morning in the keynote culturally, is TCIs similar to AWS in that respect. And can you share a little bit about that? >>Very much. So our reputation as a business is based on the relationships that we built with our customers, and we're known for that in financial services, the TCIs brand and the way that we think about our customers and the way that we partner with them. Um, you know, we, when we taught with the AWS team, we, we try to explain, you know, our history is, you know, w we're kind of the cloud for our customers. So they have a number of products and services. We support those, we manage those products. We, we build on top of, of those products for them. And so we really understand that it's important, not only that you're building a platform, but that platform has got to be able to support all the different things that our customers do every day. And we want that to be broad. We don't want it to be narrow. It's not just focused in one area. If our customers come to us and they say, well, you know, I need to build a data and an analytics platform, or I need some really specific fraud capabilities. We want to be able to support that on demand with our customers. And that's really the journey that we've taken with AWS. AWS is enabling that for us. >>And on-demand is key. I think we've one of the things that's been in short supply during the last 22 months is patients, right? That's >>Right. Absolutely. >>So describe the role of a CTO in that process. What does that look like? Because this isn't, you're not making unilateral decisions here, obviously you're working with the team, but talk about the CTO's perspective as you make decisions about whether AWS is the right fit for a part of your environment or GCP or something else. >>Yeah. I think, you know, um, we, we have, uh, a long history of supporting our own solutions and supporting our systems. And we run some of the world's largest like authorizations platforms, which those are the platforms where when you go into the store and you swipe your card, you, you have to get a response back from us. Like we have to give you that and we have to give it, we have a really specific amount of time. We have to give that back to you. And so we really understand operations and support and how to scale, uh, applications and systems and, and, and how to build really, really reliable solutions. We really understand that part of the business. So whoever we partner with, and, and you asked about my decision to CTO, it was really a group decision. You know, I have to partner with our business team, I have to get their buy-in. Um, they have to support the decision, whatever we do, it's a big investment, we're making the move to the cloud. And so, um, but we have to make sure that we, we cover off the basis. They've gotta be able to at least whatever, whoever our partner is, they've got to be able to at least provide the operational support and the reliability that we're able to give our customers today. So it's just a spreadsheet that's right. Technical qualifier, >>And whoever has the most boxes checked wins. That's right. You're taking into consideration all of those cultural aspects and the goals of the business. That's right. So as a chief technology officer, it's not just about the technology, it's about the business >>That's right, right. So I have a very, very close relationship with the president of our business, Galen, Jowers, um, and, and we built a team and we have on, on the, uh, the actual modernization or transformation team, we have members that represent that from a business perspective there I report into, uh, directly into the business teams. And then we have, uh, people from my, from my side of the, of the company. And we work every single day together and we're driving this forward. So the important part of that is at some point, we, we go to our customers and we show them, Hey, for this particular product or service that we're offering, we're going to be moving that to cloud on this kind of a schedule. And we're there together as a unified front and a unified communication with our customer to explain that journey. And we think that's really important that we do it that way and not do it. You know, like I've seen some companies they'll segment it and sort of technology, or it goes off and they kind of do their own sort of cloud initiative to us that wouldn't work for our business. It's gotta be together and enjoy it with the business. >>You sound like a very much a transformational CTO to me versus a traditional CTO and working at a legacy company that's been around for 40 years. That's impressive that the company is that forward in thinking, first of all, about its people, but also about that business, it partnership. But that has to be in lock step. We talk about that all the time, but it's hard to facilitate that, but you really sound like you guys have done a phenomenal job with some key strategic foresight is not the word. Um, I liked, like Dave was saying, it's not a spreadsheet. It's a checklist of technology requirements that people element is absolutely. >>Absolutely. And you have to, you have to, you have to be all in together on it because you know that as you go on the journey, you're going to have some failure. You're going to experience some challenges. Your customers might not be happy with every decision you make. So you have to be in it together. You're going to have to make that commitment as a company. And that's what we decided early earlier on is that we were going to do that and it's worked out well for us. >>What are some of the things that are going to be happening next for TCIs as we hopefully round out the year 2021 and go into a much better 20, 22, >>We've got a, we've got some really big things on the horizon. One of the things that we're working on right now is, um, we've, since we've been at this for 18 months, we're starting to get to a point where we have certain solutions that are ready to go. We're ready. We're going to be able in 2022 to make some key announcements around some parts of our platform, they're going to be available in AWS as a, as an offering. So we're excited about that. A lot of our customer servicing and some of the things that we do outside of our core processing platform are already cloud native. We run them in a cloud environment on our premise and some of those services, we're going to be able to go ahead and launch into the AWS in 2022. So we're really excited about that. We're right now in the throws of building an onboarding team, that's going to be working with both our customers and with our internal teams to make that shift and start migrating those applications out to the environment. >>So big, big things underway there. We've got a couple of, uh, really key strategic relationships that we've built over the last 12 months or so, um, that are all in, on our cloud journey. And so we're going to be able to announce some of those, uh, pretty soon as some of our customers and prospects, uh, that really want to be on the journey with us. So we're pretty excited about that. And I don't want to spoil any surprises there, so we'll wait and let that come out with the, with the schedule. But yeah, we've got a lot of great things ahead and we're very, very excited for where we're going. >>Awesome, Scott, great stuff. I love how transformational you are, the focus that you guys have on the people, as well as the technologies and the processes. Exciting. Congratulations on your, on your 18 month journey. And we'll have to have you back on so we can hear some of those, those, uh, you know, little, uh, Easter eggs that you just dropped. >>I'd love to, I'd love to be back on. This has been great. All right. >>And how did you know I have a credit card in my wallet running a whole. >>I've been feeling bad about saying that the whole time. He's not going to go well when we're done here, >>Wherever in Vegas, we hope you've enjoyed this. Like for Dave Nicholson, I'm Lisa Martin. You're watching the cube, the global leader in a live chat coverage.