>>Oh, MABA. It so good. It, so, so. Oh my, to make my move a in nothing. Lose open. Let go. Here I go. Ready to >>Ready. >>Ready for Are you >>Ready? Coverage of AWS Reinvent 22 continues in a moment.

>>Oh, MABA. It so good. It, so, so. Oh my, to make my move a in nothing. Lose open. Let go. Here I go. Are ready to go. >>Ready. >>Ready for more? Are you >>Ready? Coverage of AWS Reinvent 22 continues in a moment.

>>Welcome to Las Vegas. It's the cube live at AWS Reinvent 22. >>The show floor doors just opened people pouring in, and you can certainly feel the excitement here. >>I've heard it's the largest >>Reinvent ever. I call that NextGen Cloud NextGen. It is. It's happening. It's happening right now. >>It is hot. It's a hot >>Show. >>Knowing you in covering your company, that this is not just yesterday, you came up with this idea that now everyone's talking about >>The >>Cube, where we are the leader in high tech coverage. >>It is. It's happening. It's happening right now. >>Wow. That was good. Woo. All right. There we go. Nice job guys.

>>Welcome back to the Cube, as a continued coverage here from AWS Reinvent 22. It's day three of our coverage here at the Venetian in Las Vegas, and we're part of the AWS Global Startup Showcase. With me to talk about what Kong's to in that regard is Marco Palladino, who's the, the CTO and the co-founder of Con Marco. Good >>To see you. Well, thanks for having me >>Here. Yeah, I was gonna say, by the way, I, I, you've got a beautiful exhibit down on the show floor. How's the week been for you so far as an exhibitor here? >>It's been very busy. You know, to this year we made a big investment at the WS reinvent. You know, I think this is one of the best conferences in the industry. There is technology developers, but it's also business oriented. So you can learn about all the business outcomes that our, you know, customers or, you know, people are trying to make when, when adopting these new technologies. So it's very good so far. >>Good, good, good to hear. Alright, so in your world, the API world, you know, it used to be we had this, you know, giant elephant. Now we're cutting down the little pieces, right? That's right. We're all going micro now these days. That's right. Talk about that trend a little bit, what you're seeing, and we'll jump in a little deeper as to how you're addressing that. >>Well, I think the industry learned a long time ago that running large code bases is actually quite problematic when it comes to scaling the organization and capturing new opportunities. And so, you know, we're transitioning to microservices because we want to get more opportunities in our business. We want to be able to create new products, fasters, we want to be able to leverage existing services or data that we have built, like an assembly line of software, you know, picking up APIs that other developers are building, and then assemble them together to create new experiences or new products, enter new markets. And so microservices are fantastic for that, except microservices. They also introduce significant concerns on the networking layer, on the API layer. And so this is where Kong specializes by providing API infrastructure to our customers. >>Right. So more about the problems, more about the challenges there, because you're right, it, opportunities always create, you know, big upside and, and I, I don't wanna say downside, but they do introduce new complexities. >>That's right. And introducing new complexity. It's a little bit the biggest enemy of any large organization, right? We want to reduce complexity, we want to move faster, we want to be more agile, and, and we need an API vision to be able to do that. Our teams, you know, I'm speaking with customers here at Reinvent, they're telling me that in the next five years, the organization is going to be creating more APIs than all the APIs they've created up until now. Right? So how do you >>Support, that's a mind boggling number, right? >>It's mind boggling. Yeah, exactly. How do you support that type of growth? And things have been moving so fast. I feel like there is a big dilemma in, you know, with certain organizations where, you know, we have not taught a long term strategy for APIs, whereas we do have a long term strategy for our business, but APIs are running the business. We must have a long term strategy for our APIs, otherwise we're not gonna be able to execute. And that's a big dilemma right now. Yeah. >>So, so how do we get the horse back in front of the cart then? Because it's like you said, it's almost as if we've, we're, we're reprioritizing, you know, incorrectly or inaccurately, right? You're, you're getting a little bit ahead of ourselves. >>Well, so, you know, whenever we have a long-term strategy for pretty much anything in the organization, right? We know what we want to do. We know the outcome that we want to achieve. We work backwards to, you know, determine what are the steps that are gonna bring us there. And, and the responsibility for thinking long term in, in every organization, including for APIs at the end of the day, always falls on the leaders and the should on the shoulders of the leadership and, and to see executives of the organization, right? And so we're seeing, you know, look at aws by the way. Look at Amazon. This conference would not have been possible without a very strong API vision from Amazon. And the CEO himself, Jeff Bezos, everybody talks about wanting to become an API first organization. And Amazon did that with the famous Jeff Bezos mandate today, aws, it's a hundred billion revenue for Amazon. You see, Amazon was not the first organization with, with an e-commerce, but if it was the first one that married a very strong e-commerce business execution with a very strong API vision, and here we are. >>So yeah, here we are putting you squarely in, in, in a pretty good position, right? In terms of what you're offering to the marketplace who has this high demand, you see this trend starting to explode. The hockey sticks headed up a little bit, right? You know, how are you answering that call specifically at how, how are you looking at your client's needs and, and trying to address what they need and when they need it, and how they need it. Because everybody's in a kind of a different place right now. >>Right? That's exactly right. And so you have multiple teams at different stages of their journey, right? With technology, some of them are still working on legacy, some of them are moving to the cloud. Yep. Some of them are working in containers and in microservices and Kubernetes. And so how do you, how do we provide an API vision that can fulfill the needs of the entire organization in such a way that we reduce that type of fragmentation and we don't introduce too much complexity? Well, so at con, we do it by essentially splitting the API platform in three different components. Okay. One is API management. When, whenever we want to expose APIs internally or to an ecosystem of partners, right? Or to mobile, DRA is a service mesh. You know, as we're splitting these microservices into smaller parts, we have a lot of connectivity, all, you know, across all the services that the teams are building that we need to, to manage. >>You know, the network is unreliable. It's by default, not secure, not observable. There is nothing that that works in there. And so how do we make that network reliable without asking our teams to go and build these cross-cut concerns whenever they create a new service. And so we need a service match for that, right? And then finally, we could have the best AP infrastructure in the world, millions of APIs and millions of microservices. Everything is working great. And with no API consumption, all of that would be useless. The value of our APIs and the value of our infrastructure is being driven by the consumption that we're able to drive to all of these APIs. And so there is a whole area of API productivity and discovery and design and testing and mocking that enables the application teams to be successful with APIs, even when they do have a, the proper API infrastructure in place that's made of meshes and management products and so on and so forth. Right. >>Can you gimme some examples? I mean, at least with people that you've been working with in terms of addressing maybe unique needs. Cuz again, as you've addressed, journeys are in different stages now. Some people are on level one, some people are on level five. So maybe just a couple of examples Yeah. Of clients with whom you've been working. Yeah, >>So listen, I I was talking with many organizations here at AWS Reinvent that are of course trying to migrate to the cloud. That's a very common common transformation that pretty much everybody's doing in the world. And, and how do you transition to the cloud by de-risking the migration while at the same time being able to get all the benefits of, of running in the cloud? Well, we think that, you know, we can do that in two, two ways. One, by containerizing our workloads so that we can make them portable. But then we also need to lift and shift the API connectivity in such a way that we can determine how much traffic goes to the legacy and how much traffic goes to the new cloud infrastructure. And by doing that, we're able to deal with some of these transformations that can be quite complex. And then finally, API infrastructure must support every team in the organization. >>And so being able to run on a single cloud, multi-cloud, single cluster, multi cluster VMs containers, that's important and essential because we want the entire organization to be on board. Because whenever we do not do that, then the developers will make short term decisions that are not going to be fitting into the organizational outcomes that we want to achieve. And we look at any outcome that your organization wants to achieve the cloud transformation, improving customer retention, creating new products, being more agile. At the end of the day, there is an API that's powering that outcome. >>Right? Right. Well, and, and there's always a security component, right? That you have to be concerned about. So how are you raising that specter with your clients to make them aware? Because sometimes it, I wouldn't say it's an afterthought, but sometimes it's not the first thought. And, and obviously with APIs and with their integral place, you know, in, in the system now security's gotta be included in that, right? >>API security is perhaps the biggest, biggest request that we're hearing from customers. You know, 83% of the world's internet traffic at the end of the day runs on APIs, right? That's a lot of traffic. As a matter of fact, APIs are the first attack vector for any, you know, malicious store party. Whenever there is a breach, APIs must be secured. And we can secure APIs on different layers of our infrastructure. We can secure APIs at the L four mesh layer by implementing zero trust security, for example, encrypting all the traffic, assigning an identity to every service, removing the concept of trust from our systems because trust is exploitable, right? And so we need to remove the cut zero trust, remove the concept of trust, and then once we have that underlying networking that's being secure and encrypted, we want to secure access to our APIs. >>And so this is the typical authentication, authorization concerns. You know, we can use patterns like op, op or opa open policy agent to create a security layer that does not rely on the team's writing code every time they're creating a new service. But the infrastructure is enforcing the type of layer. So for example, last week I was in Sweden, as a matter of fact speaking with the largest bank in Sweden while our customers, and they were telling us that they are implementing GDPR validation in the service mesh on the OPPA layer across every service that anybody's building. Why? Well, because you can embed the GDPR settings of the consumer into a claim in a gel token, and then you can use OPPA to validate in a blanket way that Jo Token across every service in the mesh, developers don't have to do that. It just comes out of the box like that. And then finally, so networking, security, API security for access and, and management of those APIs. And then finally we have deep inspection of our API traffic. And here you will see more exotic solutions for API security, where we essentially take a subset of our API traffic and we try to inspect it to see if there is anybody doing anything that they shouldn't be doing and, and perhaps block them or, you know, raise, raise, raise the flag, so to speak. >>Well, the answer is probably yes, they are. Somebody's trying to, somebody's trying to, yeah, you're trying to block 'em out. Before I let you go, you've had some announcements leading up here to the show that's just to hit a few of those highlights, if you would. >>Well, you know, Kong is an organization that you know, is very proud of the technology that we create. Of course, we started with a, with the API gateway Con Gateway, which was our first product, the most adopted gateway in the world. But then we've expanded our platform with service mesh. We just announced D B P F support in the service mesh. For example, we made our con gateway, which was already one of the fastest gateway, if not the fastest gateway out there, 30% faster with Con Gateway 3.0. We have shipped an official con operator for Kubernetes, both community and enterprise. And then finally we're doubling down on insomnia, insomnia's, our API productivity application that essentially connects the developers with the APIs that are creating and allows them to create a discovery mechanism for testing, mocking the bagging, those APIs, all of this, we of course ship it OnPrem, but then also on the cloud. And you know, in a cloud conference right now, of course, cloud, right? Right. Is a very important part of our corporate strategy. And our customers are asking us that. Why? Because they don't wanna manage the software, they want the API platform, they don't, don't wanna manage it. >>Well, no, nobody does. And there are a few stragglers, >>A few, a few. And for them there is the on-prem >>Platform. Fine, let 'em go. Right? Exactly. But if you wanna make it a little quick and dirty, hand it off, right? Oh, >>That's exactly right. Yes. >>Let Con do the heavy lifting for you. Hey Marco, thanks for the time. Yeah, thank you so much. We appreciate, and again, congratulations on what appears to be a pretty good show for you guys. Yeah, thank you. Well done. All right, we continue our discussions here at aws. Reinvent 22. You're watching the Cube, the leader in high tech coverage. >>Okay.

(techno music) >> Welcome back to the Cube. I'm John Walls. We continue our coverage here at AWS reInvent 22. We're in the Venetian in Las Vegas, wrapping up our day one coverage here in the executive summit sponsored by Accenture and with me to talk about Accenture, couple of guys who are no strangers at all to the Cube. In fact, I think we got to give you like alumni passes or something. (Chris and Merim laugh) We got to come up with something like that. Um, Merim Becirovic is with us. Uh, Merim's a global IT at Accenture. And Chris Wegmann, who's already been on once today, as a matter of fact. >> Yeah (indistinct) >> So we're going to start charging you rent, Chris. (Chris and Merim laugh) Uh, global technology and practice lead with the AWS business group at Accenture. Good, glad to have you both back and, um, you're welcome to the Cube any time, by the way. >> So don't be scared. >> Thanks, great to be back. Let's talk about >> Sure. >> What, what you folks have been up to. So, um, you are, as we were talking earlier, you are where a lot of your clients would like to be. You, you've begun this transformation. You have fully migrated to the cloud, you've learned, right? >> Yes. You've hit all the bumps along the way. So talk about your journey. >> Yeah. >> And then how you think that experience could be translated to what your clients are going through. >> Yeah, so I'll, I'll hit it from the lessons learned and working together with our business group partners. We, so Accenture's journey to the cloud is complete. We have finished that journey, and as part of that journey, we have migrated all of the services it takes to run Accenture to the public cloud. So now that's done. That was complete. But now we are this, now it is this cloud continuum living in the cloud. And the, now, the thing we talk about, and I'd love to have Chris, you know, shine a little bit more, is we have built our digital core in a cloud, now. We're no longer dependent on data centers. And that has given us tremendous flexibility around how to enable the business as it has grown significantly since we started this journey a few years back. >> Yeah, you know, Merim, like you talk about, right? We talk about our client, we've talked to our clients about building this digital core, right? And, and we've been through that as Accenture, as a global IT organization, you know. Supporting well over 720,000 people. >> Yeah. >> Right? That growth over the last year has been tremendous. Right? So, without the strong digital core built on cloud, right? We couldn't do that, right? We couldn't add that number of people, right? We couldn't make the, the, the changes were needed during, uh, Covid to bring people home, working from home. You know, whether it being uh, the way we changed our business model or things like that, um, you know that was all enabled by cloud. It couldn't be done without that. And, you know, also the variable in our business, right? Is very tied now to our cloud consumption, right? So, you know, it goes up, it goes down, right? We've, you know, Merim and his team have completely built their, their their core with those, with those concepts uh, in mind. >> Yeah, I mean, you're talking about, you know, 700, 800,000 employees and how many countries did you say? >> 130 different countries, at least. >> 130 different countries. So, I mean, no small task, obviously, uh, to get everything done. When did you start? >> So our cloud journey, effectively, we started in 2015. And we were done, kind of right before Covid around 2019. We took a pause for a couple of different things but we could have probably done that faster. And if we were, if I was to do it again now, today we could probably do it in two to three years, flat. With everything that we've learned so far. >> So what's the application, then, to your clients' experiences that, I mean, been there, done that, right? >> You can, exactly right. I mean, you know, we always say that we want to be our best credential, right? And Merim and his team are our best credential in this space. Um, so, you know, a lot of our customers, you know, struggle making that commitment. A lot of 'em are past that struggle, now. They're committed, they're going. Uh, but I talk to a lot of my customers about, you know, do I, do I migrate? Do I modernize? You know, how do I do it? And, and it was interesting with Accenture, right? It, it started out very much as a migration program. >> Yeah. >> Right, so, we made the decision, Merim and his team made the decision to do a migration and now a modernization, right? And, and that's proven very effective. Uh, it, it's, it's, it's proven, you know, uh, we got that core in place, right? We were able to build off of that versus, you know, spending- it would've taken a lot more time just to start with a modernization approach. >> Yeah. Where, where do you draw the line between the two, between migration and modernization, then? Because just by migrating alone, you are modernizing, you know, some of your operations, so you're getting up to speed. But, but how do you draw that line and then how do you get people to jump over it? >> So I, I'll hit it from how our lessons learned. So, when we first started and we did the migrations it was literally lift and shift. And it was a lot of argument about lift and shift isn't worth it. But we found out it was, because it wasn't just about moving the work loads and keeping it like a data center. It was moving the work loads and then optimizing because everything in the cloud was significantly faster. So then I didn't have to consume all the services the same way I did in the data center. I can actually consume them smaller. But also as time went by, what we learned is, hey, now these services are working here. Which ones are actually costing us more money to run? And not that they were costing more than the data center, but it's relative to the cloud which ones cost more in the cloud? Then we looked at that and said, okay how do we want to modernize those? And then we modernized as container capabilities started the evolving, got much more mature. We shifted a lot of workloads to containers. But otherwise, the other principle we push very hard is big consumption of Lambda and uh, serverless capabilities on Amazon. So we have refactored multiple applications to give us that capability to say we no longer need the IAS capabilities, those servers, those VM's, and we run on, on serverless capability. And what's great about that is, now I don't have a server to patch, to scan, to remediate, to upgrade. I've moved away from that capability. And the teams can focus more on building the business capabilities the business wants. Um, like we did to our pricing team. I don't know if you knew this one, Chris, but all the pricing capability has been redone to be cloud native on, on AWS. >> And how, how do you deal with the folks that, that still kind of have a foot in the on-prem world that, um, that they're just not ready to give it up? You know, they, they like the control, they like the self-management. >> Yeah. >> They, they want to be in charge. >> Well, yeah. I mean, a lot of, a lot of our customers, it's, there's a reason why they need on-prem still. And there is on-prem, let's be clear. I mean, it, it is a hybrid cloud world for most of our, our customers, right? Whether they got manufacturing, whether they've got, you know, datas that are, you know, SCADA systems or, or operational IT systems that have to be close to their, their execution or to their, to their factories and things like that. So that's going to happen. I think everyone, and I shouldn't say everyone, but you know, most of our customers know they need to get there, right? And are somewhere on their journey, right? Very few have not started at all. Uh, but it's about acceleration, right? And I, I do think, um, we're going to see more and more acceleration. We saw it with Covid, right? >> Mm-hm. >> And then, you know, obviously I think we're going to see it again, right? With you know, kind of what's going on with the economy and stuff like that. It, it's, you know, it's a great way to push that change through. >> Right. >> And I, I'm really excited, to be honest what I'm really excited about, if I look at what Merim and his team's doing, is they're just leveraging that digital core and truly taking the investments that the hyper scaler's are making, the AWS's are making, and leveraging 'em. So we're not making that investment, right? We're a capital white company, right? So we don't like making good capital investments, right? And we're taking advantage of the capital investments. And we couldn't do that of the, of the hyper scales. We couldn't do that without being there. Right? >> Right. >> We just couldn't do it. >> And maybe, John, if I can build on that. >> Sure. >> Like, one of, one of the things for me when I think about the cloud is, I'm not alone. You know, because when you're in a data center when you're running a data center, you're kind of on an island. And on that island, if you've got security issues, if you got stuff you're dealing with with attackers, you know, you're, you're kind of on an island and you're alone. Whereas in this world, I am where all the investment is, where all the security capabilities are being built, and I have partners that are there with us that help us when these situations come up. So for me, I'm very uh, grateful that we pushed very hard in the beginning to get here. But I wouldn't have it any other way. For us. >> So like, do you- do you want to live outside the fort? >> Yeah. >> No >> No. (laughs) >> You're exactly right. >> Yeah. >> I don't want to live outside the fort. >> Right. >> There are a lot of bad guys out there right now. >> Yeah. >> All right, so, the journey is over. >> Right. You can unpack your bags and get comfortable, right? (Merim laughs) >> No. >> Hardly. >> No. >> So, so what is the, what has this done in terms of setting you up for your future plans? And, and >> So I'll talk about a couple different things and maybe you can build on it, Chris, from what you're seeing, like for us, we, we got very good at, I hate the concept of just FinOps but it's the way of being in the cloud. It's different than running a data center and uh, the way we think about building services, consuming services, allocating services, provisioning services. There's just so much more flexibility there that we can completely fine tune the service that we want to provide. That helps us from when we think about 360 degree value, as we talk to our clients, for ourselves to say it also helps just simply on the sustainability agenda, right, because now, as Amazon builds their capabilities to be more sustainable, those SKUs are available to us, we can naturally consume those SKUs much more effectively. Um, and then uh, the next thing to me, what I'm, what I'm especially excited about is all the stuff we're doing around network. So, you know, pre-Covid, 95% of our traffic was just straight to the internet because we had already finished the journey. So now what do you need a wide area network for anymore? >> Right. >> If you're not routing traffic between data centers what do you need it for? So, we have been working with, with AWS especially, like building these cloud land type capabilities and consuming it. So think of consuming, uh, network same way as you do the cloud. So I'm excited about that one. >> Yeah. That, that, I'm super excited about that, right? Because you know, network's at the core of everything you do, right? And there's always a lot of concern, hey, when I go to the cloud, my network costs are going to go up, right? Um, but I think we've proven, right? >> Yes. >> Being able, that those costs can come down, right? And we can have a better experience, uh, deal with the ebbs and flows of our business whether it's people working from home, people working in the office, you know, or at the client sites. We, we've, you know, we've got that cloud-based backbone that we support. You know, I, I mean Merim, I agree a hundred percent. I think you and your team have done a great job of cost management, cloud cost management, optimization, right? You didn't stop, right? >> No. >> You didn't lo- you didn't just live after the migration on VMs. Right? You know, you went serverless, you went, you know, containerization. >> Yep. >> Uh, and that's kept our cloud bill going down. >> Yes. >> Right. Versus going up, right? >> Yes. >> And I hear from a lot of customers concerned about cloud costs and that type of stuff, but you've proven right, >> Yes. >> That you can keep it flat, if not going down because you're using those last minutes. Sustainability is the other thing that I truly am, I, I love, right? Is, you know, we're all trying to become a more sustainable, sustainable organization. We're trying to help our clients become more sustainable organizations. And you know, you know, your ability to take on Gravitant processors, right? Which use less power. >> Yes. >> Right? Overnight, right? >> Yes. >> Or, hey, I'm using a, you know a, uh, serverless lambda, whatever, right? And I'm not running that server. >> Right. >> You know, so, you're able to show that sustainability gains, um, you know, very quickly. Which you could not do, right? You know, in just doing cloud basic migrations. >> Well, I tell you what I think is impressive, is that you put your money where your mouth is, right? >> Yep. (laughs) >> Is that, that it's, and, and if I'm going to be a client, not to, you know, give you guys a pat on the back, you don't need it. You're doing great without me. But I'd say you've been there, you've done that. And, and so I can learn from you. You understand my pain. >> Yes. >> You understand my reservations, my challenges and uh, you could be my, my headlights here. (Merim laughs) >> So, I think great approach. Kudos to you and certainly wish you both success and to your fourth and fifth appearances on the Cube. (Merim and Chris laugh) Um, we have slots tomorrow if you're arou- available. So, maybe we'll fill it up >> There you go. >> and bring it back again. >> Awesome. >> Guys, thanks for being here. >> Sure. >> It was very nice. >> Appreciate the time. >> All right. >> That's great. >> I've been talking, uh, about Accenture. This is the, of course, executive summit being sponsored by Accenture here at AWS reInvent 22. I'm John Walls. You're watching the Cube, the leader in tech coverage.

>>Hey everyone, welcome back. It's the Cube live in Las Vegas. We've been here since Monday covering the event wall to coverage on the cube at AWS Reinvent 22, Lisa Martin here with Dave Ante. Dave, we're hearing consistently north of 50,000 people here. I'm hearing close to 300,000 online. People are back. They are ready to hear from AWS and its ecosystem. Yeah, >>I think 55 is the number I'm hearing. I've been using 50 for 2019, but somebody the other day told me, no, no, it was way more than that. Right, right. Well this feels bigger in >>2019. It does feel bigger. It does feel bigger. And we've had such great conversations as you know, because you've been watching the Cube since Monday night. We're pleased to welcome from Sumo Logic. Lynn Doherty, the president of Worldwide Field Operations. Lynn, welcome to the program. >>Thank you for having me. I'm glad to be here. Talk >>To us about what's going on at Sumo Logic. We cover them. We've been following them for a long time, but what's what's new? >>We have a lot going on at Sumo Logic. What we do is provide solutions for both observability and security. And if you think about the challenges that our customers are facing today, everybody as they're doing this digital transformation is in a situation where the data and the digital exhausts that they have is growing faster than their budgets and especially in what looks like potentially uncertain economic times. And so what we do is enable them to bring that together on a platform so that they can solve both of those problems in a really cost effective way. >>What are some of the things that you're hearing from customers in the field where it relates to Sumo logic and aws? What are they asking for? >>They continue to ask for security and, and I think as everybody goes on that journey of digital transformation and, and I think what's going on now is that there are people who are kind of in wave two of that digital transformation, but security continues to be top of mind. And again, as as our customers are moving into potentially uncertain economic times and they're saying, Hey, I've gotta shore up and, and maybe do smarter things with my budget, cybersecurity is one piece of that that is not falling off the table. That their requirements around security, around audits, around compliance don't go away regardless of what else happens. >>How do you fit in the cloud ecosystem generally? AWS specifically? I think AWS is generally perceived as a more friendly environment for the ecosystem partners. We saw CrowdStrike yesterday, you know, stock got crushed. They had a great quarter, but not as great as they thought it could be. Yeah. And one, some of the analysts were saying, well, it could be Microsoft competition at the low end of the market. Okay. AWS is like the ecosystem partners are really strong in security, lot of places to add value. Where does Sumo Logic >>Fit? Yeah, we are all in with aws. So AWS is our platform of choice. It's the platform that we're built on. It's the only platform that we use. And so we work incredibly closely with aws. In fact, last year we were the first ever AWS ISV partner of the year for as Sumo Logic, which we're not as big as some of the other players, but it just is a testament to the partnership that we have with aws. >>When you're out in the field talking with customers, we talked about some of the challenges there, but where are your customer conversations? You talked about security and cyber as is not falling off the table. In fact, it's, it's rising up the stock, it's a board level conversation. So where are the customer conversations that you're having? Are they, are they at the developer level? Are they higher? Are they at the C-suite? What does that look like? >>Yeah, it's, it's actually at both the developer and the C-suite. And so there's really two motions. The first is around developers and practitioners and people that run security operation centers. And they need tools that are easy to use that integrate in their environment. And so we absolutely work with them as a starting point because if, if they aren't happy with the tools that they have, you know, the customer can't go on that digital transformation, can't have effective application usage. But we also need to talk to C-Suite and that to CIO or a CISO who's really thinking often more broadly about how do we do things as a platform and how do we consolidate some of our tools to rationalize what we're using and really make the most of the budget that we have. And so we come at it from both angles. We call it selling above the line and below the line because both of those are really important people for us to work with. >>Above the line being sort of the business executives, >>Business executives and C-suite executives. And then, but below the line are the actual people who are using the product and using a day to day interacting with the tools. >>So how are those above the line and below the line conversations, you know, different? What, what are the, what are the above the line conversations? What are the sort of keywords that, you know, that resonate? Let's start there. >>Yeah, above the line, there's a lot that's around how do we make the most of the investments that we're making. And so there are no shortage of tools, right? You can look around this AWS floor and see that there are no shortage of tools and software products out there. And so above the line it's how do we make use of the budget that we have and get the most out of the investments we've made and do that in a really smart way. Often thinking about platforms and consolidating tools and, and using the tools and getting full value of what they have below the line. I think it's really how do they have really strong ease of use? How do they get the fastest time to value? Because time to value is really important when you're a practitioner, when you're developing an application, when you're migrating and modernizing an application, having tools that are easy to use and not just give you data but give you insights. And so that's what a conversation with a practitioner for us is, is taking data and turning it into insights that they can use. >>You know, and it seems like we never get rid of stuff in it, but there's a big conversation now when you talk to practitioners, okay, well you got some budget pressures, your sales cycles are elongating. What are you doing about, a lot of 'em are saying, well, we're consolidating and nowhere is that more needed probably than insecurity. So how, how are you seeing that play out in the market? Are you able to take advantage of that as Sumo? >>I think there's the old joke that says there is no ciso. Whoever says, if I just had one more tool, I'd be secure. >>And >>Nobody ever says that it's not one more tool. It's having effective tools and having tools that integrate. And so when I think of Sumo Logic in that space, it's number one, we really integrate with so many different tools out there that give, again, not just security information, but security insights. And so that becomes a really important part of the conversation. What, when you talk about tool consolidation, that's absolutely, I think something that has been a journey that a lot of our customers have been on and probably will be on for the foreseeable future. And so that's a place that we can really help because we have a platform that you can leverage our tool on the DevOps side and on the security side. And that's a conversation that we have a lot with our customers. Are >>You helping bridge those two, the security folks, the dev folks? Cause we talk about Shift left and CISO being involved now. Is Sumo Logic helping from a cultural perspective to bridge those two? >>Yeah, well I think it's a really good point that you make. It's, there's part of it that's a technology challenge and then there's part of it that's a cultural challenge and an organization silo challenge that happens. And so it is something that we try to bring our customers together and often start in one area of the business and help move into other areas and bring them together. It, it also comes down to that data growing faster than budgets and customers can no longer afford to keep multiple copies of the same data, the same metrics, and all of that digital exhaust that comes as they move to the cloud and modernize their applications. And so we bring that together and help them get the most use out of it. >>There are a lot of, we've been talking all week in the cube about sort of adjacencies to security. We've talking about data protections now becoming an adjacency. You know, you talk about resilience within an organization, everybody was sort of caught off guard, obviously with the pandemic, not as resilient as they could have been. So it seems like the scope of security is really expanding. You know, they always say it's, it's a team sport, okay, it's a pro mine, but it's true. Right? Whereas it used to be that guy's problem. Yeah. What are you seeing in terms of that evolution? >>Yeah, I think you're absolutely right. I think the pandemics force some of that faster than was happening, but it's absolutely something that is going on that cybersecurity is now built in from the ground up and I've been in cyber security for years and it's moved from an afterthought or something that comes after the fact, Hey, let's build the application and then we'll worry about security to, it needs to be a secure application from the ground up. And so that is bringing together that dev and SEC ops a lot because it needs to be built in, the security piece needs to be built in from the ground up on the development side. >>Absolutely. The, the threat landscape has changed so much in the last couple of years. Has the fraudsters, bad actors, whatever you wanna call 'em, are getting far more sophisticated. Yeah. So security can't be an afterthought. Can't be a built on. Yeah, it's gotta be integrated, built in from the ground up for organizations to be able to be, as they've said, resilient. We're hearing a lot about resiliency and the importance of it. For any business. >>For any business, it's important for every business. And if you think about how we interact with companies now, our view of a bank isn't the branch, it's the app, our view of office, it's this, right? It's, it's on the phone, it's on digital devices, it's on a website. And so that is your interaction, that is your experience. And so that plays into, is it up, is it running, is it responsive? That application performance piece, but also the security piece of is it secure? Is my data protected? You know, do I have any vulnerability? >>Yeah, you must have, being in field operations, a favorite customer story that you really think defines the value proposition beautifully of Sumo Logic. What story is that? >>Wow, that's a good question. I have a lot of favorite stories. You know, we have customers, for example, gaming customers that maybe aren't able to predict what their usage looks like. And that's something that we really help our customers with is the peaks and valleys. And so we have gaming customers or retail customers that we're able to take their data sources and they may be at one level and go to 10 x in a day without any notice. And we're able to handle that for them. And I think that's something that I'm really proud of is that we don't make that the customer's problem. They're, they're peaks and valleys, they're spikes that may happen seasonally in retail. It's Black Friday sales that are coming up. It's a new game that gets released. It's a new music piece that gets released and they are going to see that, but they don't have to worry about that because of us. And so that really makes me proud that we handle that and take that problem off of their shoulders. I >>See Pokemon on the website, that's a hugely popular >>Game, Pokemon now. Yes. >>Last question for you, we've got about 30 seconds left. If you had a billboard to put up in Denver where you live about Sumo Logic and its impact like an elevator pitch or a phrase that you think really summarizes the impact, what would it >>Say? Yeah, well it's a really good question. I've got it on my shirt. I dunno, it's not for the G-rated, but we fix things faster. Fix shit faster. And so for us that's really, ultimately, it's not just about having information, it's not just about having the data, it's about being able to resolve your problems quickly. And whether that's an application or a security issue, we've gotta be able to fix it faster for our customers and that's what we enable them to do. >>Fix bleep faster. Lynn, it's been a pleasure having you on the program. Thank you so much. Thank you for joining us. Awesome step at Sumo Logic. For our guest and for Dave Ante. I'm Lisa Martin. You're watching The Cube Live from Las Vegas, the leader in live enterprise and emerging tech coverage.

>>Hey guys and girls, welcome back to The Cube's Live coverage of AWS Reinvent 22 from Sin City. We've been here, this is our third day of coverage. We started Monday night first. Full day of the show was yesterday. Big news yesterday. Big news. Today we're hearing north of 50,000 people, and I'm hearing hundreds of thousands online. We've been having great conversations with AWS folks in the ecosystem, AWS customers, partners, ISVs, you name it. We're pleased to welcome back one of our alumni to the program, talking about partner ecosystem. Dominic Rav Vida joins us, the VP of Developer relations at single store. It's so great to have you on the program. Dominic. Thanks for coming. >>Thanks. Great. Great to see you >>Again. Great to see you too. We go way back. >>We do, yeah. >>So let's talk about reinvent 22. This is the 11th reinvent. Yeah. What are some of the things that you've heard this week that are exciting that are newsworthy from single stores perspective? >>I think in particular what we heard AWS announce on the zero ETL between Aurora and Redshift, I think it's, it's significant in that AWS has provided lots of services for building blocks for applications for a long time. And that's a great amount of flexibility for developers. But there are cases where, you know, it's a common thing to need to move data from transactional systems to analytics systems and making that easy with zero etl, I think it's a significant thing and in general we see in the market and especially in the data management market in the cloud, a unification of different types of workloads. So I think that's a step in the right direction for aws. And I think for the market as a whole, why it's significant for single store is, that's our specialty in particular, is to unify transactions and analytics for realtime applications and analytics. When you've got customer facing analytic applications and you need low latency data from realtime streaming data sources and you've gotta crunch and compute that. Those are diverse types of workloads over document transactional workloads as well as, you know, analytical workloads of various shapes and the data types could be diverse from geospatial time series. And then you've gotta serve that because we're all living in this digital service first world and you need that relevant, consistent, fresh data. And so that unification is what we think is like the big thing in data right >>Now. So validation for single store, >>It does feel like that. I mean, I'd say in the recent like six months, you've seen announcements from Google with Alloy db basically adding the complement to their workload types. You see it with Snowflake adding the complement to their traditional analytical workload site. You see it with Mongo and others. And yeah, we do feel it was validation cuz at single store we completed the functionality for what we call universal storage, which is, is the industry's first third type of storage after row store and column store, single store dbs, universal storage, unifies those. So on a single copy of data you can form these diverse workloads. And that was completed three years ago. So we sort of see like, you know, we're onto something >>Here. Welcome to the game guys. >>That's right. >>What's the value in that universal storage for customers, whether it's a healthcare organization, a financial institution, what's the value in it in those business outcomes that you guys are really helping to fuel? >>I think in short, if there were like a, a bumper sticker for that message, it's like, are you ready for the next interaction? The next interaction with your customer, the next interaction with your supply chain partner, the next interaction with your internal stakeholders, your operational managers being ready for that interaction means you've gotta have the historical data at the ready, accessible, efficiently accessible, and and, and queryable along with the most recent fresh data. And that's the context that's expected and be able to serve that instantaneously. So being ready for that next interaction is what single store helps companies do. >>Talk about single store helping customers. You know, every company these days has to be a data company. I always think, whether it's my grocery store that has all my information and helps keep me fed or a gas station or a car dealer or my bank. And we've also here, one of the things that John Furrier got to do, and he does this every year before aws, he gets to sit down with the CEO and gets really kind of a preview of what's gonna happen at at the show, right? And Adams Lisky said to him some interesting very poignant things. One is that that data, we talk about data democratization, but he says the role of the data analyst is gonna go away. Or that maybe that term in, in that every person within an organization, whether you're marketing, sales, ops, finance, is going to be analyzing data for their jobs to become data driven. Right? How does single store help customers really become data companies, especially powering data intensive apps like I know you do. >>Yeah, that's, there's a lot of talk about that and, and I think there's a lot of work that's been done with companies to make that easier to analyze data in all these different job functions. While we do that, it's not really our starting point because, and our starting point is like operationalizing that analytics as part of the business. So you can think of it in terms of database terms. Like is it batch analysis? Batch analytics after the fact, what happened last week? What happened last month? That's a lot of what those data teams are doing and those analysts are doing. What single store focuses more is in putting those insights into action for the business operations, which typically is more on the application side, it's the API side, you might call it a data product. If you're monetizing your data and you're transacting with that providing as an api, or you're delivering it as software as a service, and you're providing an end-to-end function for, you know, our marketing marketer, then we help power those kinds of real time data applications that have the interactivity and have that customer touchpoint or that partner touchpoint. So you can say we sort of, we put the data in action in that way. >>And that's the most, one of the most important things is putting data in action. If it's, it can be gold, it can be whatever you wanna call it, but if you can't actually put it into action, act on insights in real time, right? The value goes way down or there's liability, >>Right? And I think you have to do that with privacy in mind as well, right? And so you have to take control of that data and use it for your business strategy And the way that you can do that, there's technology like single store makes that possible in ways that weren't possible before. And I'll give you an example. So we have a, a customer named Fathom Analytics. They provide web analytics for marketers, right? So if you're in marketing, you understand this use case. Any demand gen marketer knows that they want to see what the traffic that hits their site is. What are the page views, what are the click streams, what are the sequences? Have these visitors to my website hit certain goals? So the big name in that for years of course has been Google Analytics and that's a free service. And you interact with that and you can see how your website's performing. >>So what Fathom does is a privacy first alternative to Google Analytics. And when you think about, well, how is that possible that they, and as a paid service, it's as software, as a service, how, first of all, how can you keep up with that real time deluge of clickstream data at the rate that Google Analytics can do it? That's the technical problem. But also at the data layer, how could you keep up with Google has, you know, in terms of databases And Fathom's answer to that is to use single store. Their, their prior architecture had four different types of database technologies under the hood. They were using Redis to have fast read time cash. They were using MySEQ database as the application database they were using. They were looking at last search to do full tech search. And they were using DynamoDB as part of a another kind of fast look up fast cash. They replaced all four of those with single store. And, and again, what they're doing is like sort of battling defacto giant in Google Analytics and having a great success at doing that for posting tens of thousands of websites. Some big names that you've heard of as well. >>I can imagine that's a big reduction from four to one, four x reduction in databases. The complexities that go away, the simplification that happens, I can imagine is quite huge for them. >>And we've done a study, an independent study with Giga Home Research. We published this back in June looking at total cost of ownership with benchmarks and the relevant benchmarks for transactions and analytics and databases are tpcc for transactions, TPC H for analytics, TPC DS for analytics. And we did a TCO study using those benchmark datas on a combination of transactional and analytical databases together and saw some pretty big improvements. 60% improvement over Myse Snowflake, for >>Instance. Awesome. Big business outcomes. We only have a few seconds left, so you've already given me a bumper sticker. Yeah. And I know I live in Silicon Valley, I've seen those billboards. I know single store has done some cheeky billboard marketing campaigns. But if you had a new billboard to create from your perspective about single store, what does it say? >>I, I think it's that, are you, are you ready for the next interaction? Because business is won and lost in every moment, in every location, in every digital moment passing by. And if you're not ready to, to interact and transact rather your systems on your behalf, then you're behind the curve. It's easy to be displaced people swipe left and pick your competitor. So I think that's the next bumper sticker. I may, I would say our, my favorite billboard so far of what we've run is cover your SaaS, which is what is how, what is the data layer to, to manage the next level of SaaS applications, the next generation. And we think single store is a big part >>Of that. Cover your SaaS. Love it. Dominic, thank you so much for joining me, giving us an update on single store from your perspective, what's going on there, kind of really where you are in the market. We appreciate that. We'll have to >>Have you back. Thank you. Glad to >>Be here. All right. For Dominic rta, I'm Lisa Martin. You're watching The Cube, the leader in live, emerging and enterprise tech coverage.

>>Well, hello everybody. John Walls here and continuing our coverage here at AWS Reinvent 22 on the queue. We continue our segments here in the Global Startup program, which of course is sponsored by AWS Startup Showcase, and with us to talk about any scale as the co-founder and CEO of the company, Robert and n, you are Robert. Good to see you. Thanks for joining us. >>Yeah, great. And thank you. >>You bet. Yeah. Glad to have you aboard here. So let's talk about Annie Scale, first off, for those at home and might not be familiar with what you do. Yeah. Because you've only been around for a short period of time, you're telling me >>Company's about >>Three years now. Three >>Years old, >>Yeah. Yeah. So tell us all about it. Yeah, >>Absolutely. So one of the biggest things happening in computing right now is the proliferation of ai. AI is just spreading throughout every industry has the potential to transform every industry. But the thing about doing AI is that it's incredibly computationally intensive. So if you wanna do do ai, you're not, you're probably not just doing it on your laptop, you're doing it across many machines, many gpu, many compute resources, and that's incredibly hard to do. It requires a lot of software engineering expertise, a lot of infrastructure expertise, a lot of cloud computing expertise to build the software infrastructure and distributed systems to really scale AI across all of the, across the cloud. And to do it in a way where you're really getting value out of ai. And so that is the, the problem statement that AI has tremendous potential. It's incredibly hard to do because of the, the scale required. >>And what we are building at any scale is really trying to make that easy. So trying to get to the point where, as a developer, if you know how to program on your laptop, then if you know how to program saying Python on your laptop, then that's enough, right? Then you can do ai, you can get value out of it, you can scale it, you can build the kinds of, you know, incredibly powerful applica AI applications that companies like Google and, and Facebook and others can build. But you don't have to learn about all of the distributed systems and infrastructure. It just, you know, we'll handle that for you. So that's, if we're successful, you know, that's what we're trying to achieve here. >>Yeah. What, what makes AI so hard to work with? I mean, you talk about the complexity. Yeah. A lot of moving parts. I mean, literally moving parts, but, but what is it in, in your mind that, that gets people's eyes spinning a little bit when they, they look at great potential. Yeah. But also they look at the downside of maybe having to work your way through Pike mere of sorts. >>So, so the potential is definitely there, but it's important to remember that a lot of AI initiatives fail. Like a lot of initiative AI initiatives, something like 80 or 90% don't make it out of, you know, the research or prototyping phase and inter production. Hmm. So, some of the things that are hard about AI and the reasons that AI initiatives can fail, one is the scale required, you know, moving. It's one thing to develop something on your laptop, it's another thing to run it across thousands of machines. So that's scale, right? Another is the transition from development and prototyping to production. Those are very different, have very different requirements. Absolutely. A lot of times it's different teams within a company. They have different tech stacks, different software they're using. You know, we hear companies say that when they move from develop, you know, once they prototype and develop a model, it could take six to 12 weeks to get that model in production. >>And that often involves rewriting a lot of code and handing it off to another team. So the transition from development to production is, is a big challenge. So the scale, the development to production handoff. And then lastly, a big challenge is around flexibility. So AI's a fast moving field, you see new developments, new algorithms, new models coming out all the time. And a lot of teams we work with, you know, they've, they've built infrastructure. They're using products out there to do ai, but they've found that it's sort of locking them into rigid workflows or specific tools, and they don't have the flexibility to adopt new algorithms or new strategies or approaches as they're being developed as they come out. And so they, but their developers want the flexibility to use the latest tools, the latest strategies. And so those are some of the main problems we see. It's really like, how do you scale scalability? How do you move easily from development and production and back? And how do you remain flexible? How do you adapt and, and use the best tools that are coming out? And so those are, yeah, just those are and often reasons that people start to use Ray, which is our open source project in any scale, which is our, our product. So tell >>Me about Ray, right? Yeah. Opensource project. I think you said you worked on it >>At Berkeley. That's right. Yeah. So before this company, I did a PhD in machine learning at Berkeley. And one of the challenges that we were running into ourselves, we were trying to do machine learning. We actually weren't infrastructure or distributed systems people, but we found ourselves in order to do machine learning, we found ourselves building all sorts of tools, ad hoc tools and systems to scale the machine learning, to be able to run it in a reasonable amount of time and to be able to leverage the compute that we needed. And it wasn't just us people all across, you know, machine learning researchers, machine learning practitioners were building their own tooling and infrastructure. And that was one of the things that we felt was really holding back progress. And so that's how we slowly and kind of gradually got into saying, Hey, we could build better tools here. >>We could build, we could try to make this easier to do so that all of these people don't have to build their own infrastructure. They can focus on the actual machine learning applications that they're trying to build. And so we started, Ray started this open source project for basically scaling Python applications and scaling machine learning applications. And, well, initially we were running around Berkeley trying to get all of our friends to try it out and, and adopt it and, you know, and give us feedback. And if it didn't work, we would debug it right away. And that slow, you know, that gradually turned into more companies starting to adopt it, bigger teams starting to adopt it, external contributors starting to, to contribute back to the open source project and make it better. And, you know, before you know it, we were hosting meetups, giving to talks, running tutorials, and the project was just taking off. And so that's a big part of what we continue to develop today at any scale, is like really fostering this open source community, growing the open source user base, making sure Ray is just the best way to scale Python applications and, and machine learning applications. >>So, so this was a graduate school project That's right. You say on, on your way to getting your doctorate and now you commercializing now, right? Yeah. I mean, so you're being able to offer it, first off, what a journey that was, right? I mean, who would've thought Absolutely. I guess you probably did think that at some point, but >>No, you know, when we started, when we were working on Ray, we actually didn't anticipate becoming a company, or we at least just weren't looking that far ahead. We were really excited about solving this problem of making distributed computing easy, you know, getting to the point where developers just don't have to learn about infrastructure and distributed systems, but get all the benefits. And of course, it wasn't until, you know, later on as we were graduating from Berkeley and we wanted to continue really taking this project further and, and really solving this problem that it, we realized it made sense to start a company. >>So help me out, like, like what, what, and I might have missed this, so I apologize if I did, but in terms of, of Ray's that building block and essential for your, your ML or AI work down the road, you know, what, what is it doing for me or what, what will it allow me to do in either one of those realms that I, I can't do now? >>Yeah. And so, so like why use Ray versus not using Ray? Yeah, I think the, the answer is that you, you know, if you're doing ai, you need to scale. It's becoming, if you don't find that to be the case today, you probably will tomorrow, you know, or the day after that. And so it's really increasingly, it's a requirement. It's not an option. And so if you're scaling, if you're trying to build these scalable applications you are building, you're either going to use Ray or, or something like Ray or you're going to build the infrastructure yourself and building the infrastructure yourself, that's a long journey. >>So why take that on, right? >>And many of the companies we work with don't want to be in the business of building and managing infrastructure. No. Because, you know, if they, they want their their best engineers to build their product, right? To, to get their product to market faster. >>I want, I want you to do that for me. >>Right? Exactly. And so, you know, we can really accelerate what these teams can do and, you know, and if we can make the infrastructure something they just don't have to think about, that's, that's why you would choose to use Ray. >>Okay. You know, between a and I and ml are, are they different animals in terms of what you're trying to get done or what Ray can do? >>Yeah, and actually I should say like, it's not just, you know, teams that are new teams that are starting out, that are using Ray, many companies that have built, already built their own infrastructure will then switch to using Ray. And to give you a few examples, like Uber runs all their deep learning on Ray, okay. And, you know, open ai, which is really at the frontier of training large models and, and you know, pushing the boundaries of, of ai, they train their largest models using Ray. You know, companies like Shopify rebuilt their entire machine learning platform using Ray, >>But they started somewhere else. >>They had, this is all, you know, like, it's not like the v1, you know, of their, of their machine learning infrastructure. This is like, they did it a different way before, this is like the second version or the third iteration of of, of how they're doing it. And they realize often it's because, you know, I mean in the case of, of Uber, just to give you one example, they built a system called hova for scaling deep learning on a bunch of GPUs. Right Now, as you scale deep learning on GPUs for them, the bottleneck shifted away from, you know, as you scale GPU's training, the bottleneck shifted away from training and to the data ingest and pre-processing. And they wanted to scale data ingest and pre-processing on CPUs. So now Hova, it's a deep learning framework. It doesn't do the data ingest and pre-processing on CPUs, but you can, if you run Hova on top of Ray, you can scale training on GPUs. >>And then Ray has another library called Ray Data you can, that lets you scale the ingest and pre-processing on CPUs. You can pipeline them together. And that allowed them to train larger models on more data before, just to take one example, ETA prediction, if you get in an Uber, it tells you what time you're supposed to arrive. Sure. That uses a deep learning model called d eta. And before they were able to train on about two weeks worth of data. Now, you know, using Ray and for scaling the data, ingestive pre-processing and training, they can train on much more data. You know, you can get more accurate ETA predictions. So that's just one example of the kind of benefit they were able to get. Right. Also, because it's running on top of, of Ray and Ray has this ecosystem of libraries, you know, they can also use Ray's hyper parameter tuning library to do hyper parameter tuning for their deep learning models. >>They can also use it for inference and you know, because these are all built on top of Ray, they inherit the like, elasticity and fault tolerance of running on top of Ray. So really it simplifies things on the infrastructure side cuz there's just, if you have Ray as common infrastructure for your machine learning workloads, there's just one system to, to kind of manage and operate. And if you are, it simplifies things for the end users like the developers because from their perspective, they're just writing a Python application. They don't have to learn how to use three different distributed systems and stitch them together and all of this. >>So aws, before I let you go, how do they come into play here for you? I mean, are you part of the showcase, a startup showcase? So obviously a major partner and major figure in the offering that you're presenting >>People? Yeah, well you can run. So any scale is a managed ray service. Like any scale is just the best way to run Ray and deploy Ray. And we run on top of aws. So many of our customers are, you know, using Ray through any scale on aws. And so we work very closely together and, and you know, we have, we have joint customers and basically, and you know, a lot of the value that any scale is adding on top of Ray is around the production story. So basically, you know, things like high availability, things like failure handling, retry alerting, persistence, reproducibility, these are a lot of the value, the values of, you know, the value that our platform adds on top of the open source project. A lot of stuff as well around collaboration, you know, imagine you are, you, something goes wrong with your application, your production job, you want to debug it, you can just share the URL with your, your coworker. They can click a button, reproduce the exact same thing, look at the same logs, you know, and, and, and figure out what's going on. And also a lot around, one thing that's, that's important for a lot of our customers is efficiency around cost. And so we >>Support every customer. >>Exactly. A lot of people are spending a lot of money on, on aws. Yeah. Right? And so any scale supports running out of the box on cheaper like spot instances, these preempt instances, which, you know, just reduce costs by quite a bit. And so things like that. >>Well, the company is any scale and you're on the show floor, right? So if you're having a chance to watch this during reinvent, go down and check 'em out. Robert Ashihara joining us here, the co-founder and ceo and Robert, thanks for being with us. Yeah. Here on the cube. Really enjoyed it. Me too. Thanks so much. Boy, three years graduate program and boom, here you are, you know, with off to the enterprise you go. Very nicely done. All right, we're gonna continue our coverage here on the Cube with more here from Las Vegas. We're the Venetian, we're AWS Reinvent 22 and you're watching the Cube, the leader in high tech coverage.

>>Hey everyone, it's Vegas. Welcome back. We know you've been watching all day. We appreciate that. We always love being able to bring you some great content on the Cube Live from AWS Reinvented 22. Lisa Martin here with Paul Gill. And Paul, we've had such a great event. We've, I think we've done nearly 70 interviews since we started on the Cube on >>Monday night. I believe we just hit 70. Yeah, we just hit 70. You must feel like you've done half of >>Them. I really do. But we've been having great conversations. There's so much innovation going on at aws. Nothing slowed them down during the pandemic. We love also talking about the innovation, the flywheel that is their partner ecosystem. We're gonna have a great conversation about that >>Next. And as we've said, going back to day one, the energy of the show is remarkable. And here we are, we're getting late in the afternoon on day two, and there's just as much activity, just as much energy out there as, as the beginning of the first day. I have no doubt day three will be the >>Same. I agree. There's been no slowdown. We've got two guests here. We're gonna have a great conversation. Chuck Kubota joins us, senior Director of Cloud Services, GTM at Red Hat. Great to have you on the program. And Ted Stanton, global head of Sales, red Hat at IBM at aws. Welcome. >>Thanks for having us. >>How's the show going so far for you guys? >>It's a blur. Is it? Oh my gosh. >>Don't they all >>Blur? Well, yes, yes. I actually like last year a bit better. It was half the size. Yeah. And a lot easier to get around, but this is back to normal, so >>It is back to normal. Yeah. And and Ted, we're hearing north of 50,000 in-person attendees. I heard a, something I think was published. I heard the second hand over like 300,000 online attendees. This is maybe the biggest one we ever had. >>Yeah, yeah, I would agree. And frankly, it's my first time here, so I am massively impressed with the overall show, the meeting with partners, the meeting with customers, the announcements that were made, just fantastic. And >>If you remember back to two years ago, there were a lot of questions about whether in-person conferences would ever return and the volume that we used to see them. And that appears to be >>The case. I think we, I think we've answered, I think AWS has answered that for us, which I'm very pleased to see. Talk about some of those announcements. Ted. There's been so much that that's always one of the things we know and love about re men is there's slew of announcements. You were saying this morning, Paul, and then keynote, you lost, you stopped counting after I >>Lost 15, I lost count for 15. I think it was over 30 announcements this morning alone >>Where IBM and Red Hat are concern. What are some of the things that you are excited about in terms of some of the news, the innovation, and where the partnership is going? >>Well, definitely where the partnership is going, and I think even as we're speaking right now, is a keynote going on with Aruba, talking about some of the partners and the way in which we support partners and the new technologies and the new abilities for partners to take advantage of these technologies to frankly delight our customers is really what most excites me. >>Chuck, what about you? What's going on with Red Hat? You've been there a long time. Sales, everything, picking up customers, massively transforming. What are some of the things that you're seeing and that you're excited >>About? Yeah, I mean, first of all, you know, as customers have, you know, years ago discovered it's not competitively advantageous to manage their own data centers in most cases. So they would like to, you know, give that responsibility to Amazon. We're seeing them move further up the stack, right? So that would be more beyond the operating system, the application platforms like OpenShift. And now we have a managed application platform built on OpenShift called Red Out OpenShift service on AWS or Rosa. And then we're even further going up the stack with that with, we just announced this week that red out OpenShift data science is available in the AWS marketplace, runs on Rosa, helps break the land speed record to getting those data models out there that are so important to make, you know, help organizations become more, much more data driven to remain competitive themselves. >>So talk about Rosa and how it differs from previous iterations of, of OpenShift. I mean, you had, you had an online version of OpenShift several years ago. What's different about Rosa? >>Yeah, so the old OpenShift online that was several years old, right? For one thing, wasn't a joint partnership between Amazon and Red Hat. So we work together, right? Very closely on this, which is great. Also, the awesome thing about Rosa, you know, if you think about like OpenShift for, for, as a matter of fact, Amazon is the number one cloud that OpenShift runs on, right? So a lot of those customers want to take advantage of their committed spins, their EDPs, they want one bill. And so Rosa comes through the one bill comes through the marketplace, right? Which is, which is totally awesome. Not only that or financially backing OpenShift with a 99.95% financially backed sla, right? We didn't have that before either, right? >>When you say financially backed sla, >>What do you mean? That means that if we drop below 99.95% of availability, we're gonna give you some money back, right? So we're really, you know, for lack of better words, putting our money where our mouth is. Absolutely right. >>And, and some of the key reasons that we even work together to build Rosa was frankly we've had a mirror of customers and virtually every single region, every single industry been using OpenShift on AWS for years, right? And we listened to them, they wanted a more managed version of it and we worked very closely together. And what's really great about Rosa too is we built some really fantastic integrations with some of the AWS native services like API gateway, Amazon rds, private link, right? To make it very simple and easy for customers to get started. We talked a little bit about the marketplace, but it's also available just on the AWS console, right? So customers can get started in a pay as you go fashion start to use it. And if they wanna move into a more commitment, more of a set schedule of payments, they can move into a marketplace private offer. >>Chuck, talk about, how about Rosen? How is unlocking the power of technology like containers Kubernetes for customers while dialing down some of the complexity that's >>There? Yeah, I mean if you think about, you know, kind of what we did, you know, earlier on, right? If you think about like virtualization, how it dialed down the complexity of having to get something rack, get a blade rack, stack cable and cooled every time you wanted to deploy new application, right? So what we do is we, our message is this, we want developers to focus on what matters most. And that's build, deploy, and running applications. Most of our customers are not in the business of building app platforms. They're not in the business of building platforms like banks, I, you know, financials, right? Government, et cetera. Right? So what we do is we allow those developers that are, enable those developers that know Java and Node and springing and what have you, just to keep writing what they know. And then, you know, I don't wanna get too technical here, but get pushed through way and, and OpenShift takes care of the rest, builds it for them, runs it through a pipeline, a CICD pipeline, goes through all the testing and quality gates and things like that, deploys it, auto wires it up, you know, to monitoring which is what you need. >>And we have all kinds of other, you know, higher order services and an ecosystem around that. And oh, by the way, also plugging into and taking advantage of the services like rds, right? If you're gonna write an application, a tradition, a cloud native application on Amazon, you're probably going to wanna run it in Rosa and consuming one of those databases, right? Like RDS or Aurora, what have you. >>And I, and I would say it's not even just the customers. We have a variety of ecosystem partners, both of our partners leveraging it as well. We have solos built their executive management system that they go ahead and turn and sell to their customers, streamlines data and collects data from a variety of different sources. They decided, you know, it's better to run that on top of Rosa than manage OpenShift themselves. We've seen IBM restack a lot of their software, you know, to run on top of Rose, take advantage of that capabilities. So lots of partners as well as customers are taking advantage of fully managed stack of that OpenShift that that turnkey capabilities that it provides >>For, for OpenShift customers who wanna move to Rose, is that gonna be a one button migration? Is that gonna be, can they run both environments simultaneously and migrate over time? What kind of tools are you giving them? >>We have quite, we have quite a few migration tools such as conveyor, right? That's one of our projects, part of our migration application toolkit, right? And you know, with those, there's also partners like Trilio, right? Who can help move, you know, applications back 'em up. In fact, we're working on a pretty cool joint go to market with that right now. But generally speaking, the OpenShift experience that the customers that we have know and love and those who have never used OpenShift either are coming to it as well via Rosa, right? The experience is primarily the same. You don't have to really retrain your people, right? If anything, there's a reduction in operational cost. We increase developer productivity cuz we manage so much of the stack for you. We have SRE site reliability engineers that are backing the platform that proactively get ahead of anything that may go wrong. So maybe you don't even notice if something went wrong, wrong. And then also reactively fixing it if it comes to that, right? So, you know, all those kind of things that your customers are having to do on their own or hire a contractor, a consultant, what have to do Now we benefit from a managed offering in the cloud, right? In Amazon, right? And your developers still have that great experience too, like to say, you know, again, break the land speed record to prod. >>I >>Like that. And, and I would actually say migrations from OpenShift are on premise. OpenShift to Rosa maybe only represents about a third of the customers we have. About another third of the customers is frankly existing AWS customers. Maybe they're doing Kubernetes, do it, the, you know, do it themselves. We're struggling with some of the management of that. And so actually started to lean on top of using Rosa as a better platform to actually build upon their applications. And another third, we have quite a few customers that were frankly new OpenShift customers, new Red Hat customers and new AWS customers that were looking to build that next cloud native application. Lots of in the startup space that I've actually chosen to go with Rosa. >>It's funny you mention that because the largest Rosa consumer is new to OpenShift. Oh wow. Right. That's pretty, that's pretty powerful, right? It's not just for existing OpenShift customers, existing OpenShift. If you're running OpenShift, you know, on EC two, right. Self-managed, there's really no better way to run it than Rosa. You know, I think about whether this is the 10th year, 10 year anniversary of re right? Right. Yep. This is also the 10 year anniversary of OpenShift. Yeah, right. I think it one oh came out about sometime around a week, 10 years ago, right? When I came over to Red Hat in 2015. You know, if you, if you know your Kubernetes history was at July 25th, I think was when Kubernetes ga, July 25th, 2015 is when it g you have >>A good >>Memory. Well I remember those days back then, right? Those were fun, right? The, we had a, a large customer roll out on OpenShift three, which is our OpenShift RE based on Kubernetes. And where do you think they ran Amazon, right? Naturally. So, you know, as you move forward and, and, and OpenShift V four came out, the, reduces the operational complexity and becomes even more powerful through our operator framework and things like that. Now they revolved up to Rosa, right? And again, to help those customers focus on what matters most. And that's the applications, not the containers, not those underlying implementation and technical details while critically important, are not necessarily core to the business to most of our customers. >>Tremendous amount of innovation in OpenShift in a decade, >>Pardon me? >>Tremendous amount of innovation in OpenShift in the >>Last decade. Oh absolutely. And, and and tons more to come like every day. Right. I think what you're gonna see more of is, you know, as Kubernetes becomes more, more and more of the plumbing, you know, I call 'em productive abstractions on top of it, as you mentioned earlier, unlocking the power of these technologies while minimizing, even hiding the complexity of them so that you can just move fast Yeah. And safely move fast. >>I wanna be sure we get to, to marketplaces because you have been, red Hat has made, has really stepped up as commitment to the AWS marketplace. Why are you doing that now and how are, how are the marketplaces evolving as a channel for you? >>Well, cuz our customers want us to be there, right? I mean we, we, we are customer centric, customer first approach. Our customers want to buy through the marketplace. If you're an Amazon, if you're an Amazon customer, it's really easy for you to go procure software through the marketplace and have, instead of having to call up Red Hat and get on paper and write a second check, right? One stop shop one bill. Right? That is very, very attractive to our customers. Not only that, it opens up other ways to buy, you know, Ted mentioned earlier, you know, pay as you go buy the drink pricing using exactly what you need right now. Right? You know, AWS pioneered that, right? That provides that elasticity, you know, one of the core tenants at aws, AWS cloud, right? And we weren't able to get that with the traditional self-managed on Red Hat paper subscriptions. >>Talk a little bit about the go to market, what's, you talked about Ted, the kind of the three tenants of, of customer types. But talk a little bit about the gtm, the joint go to market, the joint engineering, so we get an understanding of how customers engage multiple options. >>Yeah, I mean, so if you think about go to market, you know, and the way I think of it is it's the intersection of a few areas, right? So the product and the product experience that we work together has to be so good that a customer or user, actually many start talk, talking about users now cuz it's self-service has a more than likely chance of getting their application to prod without ever talking to a person. Which is historically not what a lot of enterprise software companies are able to do, right? So that's one of those biggest things we do. We want customers to just be successful, turn it on, get going, be productive, right? At the same time we wanna to position the product in such a way that's differentiating that you can't get that experience anywhere else. And then part of that is ensuring that the education and enablement of our customers and our partners as such that they use the platform the right way to get as much value out of as possible. >>All backed by, you know, a very smart field that ensures that the customer get is making the right decision. A customer success org, this is attached to my org now that we can go on site and team with our customers to make sure that they get their first workloads up as quickly as possible, by the way, on our date, our, our dime. And then SRE and CEA backing that up with support and operational integrity to ensure that the service is always up and available so you can sleep, sleep, sleep well at night. Right? Right. One of our PMs of, of of Rosa, he says, what does he say? He says, Rosa allows organizations, enables organizations to go from 24 7 operations to nine to five innovation. Right? And that's powerful. That's how our customers remain more competitive running on Rosa with aws, >>When you're in customer conversations and you have 30 seconds, what are the key differentiators of the solution that you go boom, boom, boom, and they just go, I get it. >>Well, I mean, my 32nd elevator pitch, I think I've already said, I'll say it again. And that is OpenShift allows you to focus on your applications, build, deploy, and run applications while unlocking the power of the technologies like containers and Kubernetes and hiding or minimizing those complexities. So you can do as fast as possible. >>Mic drop Ted, question for you? Sure. Here we are at the, this is the, I leave the 11th reinvent, 10th anniversary, 11th event. You've been in the industry a long time. What is your biggest takeaway from what's been announced and discussed so far at Reinvent 22, where the AWS and and its partner ecosystem is concerned? If you had 30 seconds or if you had a bumper sticker to put on your DeLorean, what would you say? >>I would say we're continuing to innovate on behalf of our customers, but making sure we bring all of our partners and ecosystems along in that innovation. >>Yeah. I love the customer obsession on both sides there. Great work guides. Congrats on the 10th anniversary of OpenShift and so much evolution, the customer obsession is really clear for both of you guys. We appreciate your time. You're gonna have to come back now. Absolutely. Absolutely. Thank you. All right. Thank you so much for joining us. For our guests and for Paul Gillin. I'm Lisa Martin. You're watching The Cube, the leader in live enterprise and emerging tech coverage.

>>Good afternoon everybody. I'm John Walls and welcome back to our coverage here on the cube of AWS Reinvent 22. We are bringing you another segment with the Global Startup Program, which is part of the AWS Start Showcase, and it's a pleasure to welcome two new guests here to the showcase. First, immediately to my right Han w lre. Good to see you Han. Good to see you. The leader of the Enterprise Solutions Architecture at aws. And on the far right, Rolin Lee, who is the co-founder and CEO of Heim Doll Data. Roland, good to see you. Great >>To be here. >>All right, good. Thanks for joining us. Well first off, for those at home, I may not be familiar with Heim Doll. What do you do? Why are you here? But I'll let you take it from there. >>Well, we're one of the sponsors here at AWS and great to be here. We offer a data access layer in the form of a proxy, and what it does is it provides complete visibility and the capability to enhance the interaction between the application and one's current database. And as a result, you'll, the customer will improve database scale, database security and availability. And all these features don't require any application changes. So that's sort of our marketing pitch, if you will, all these types of features to improve the experience of managing a database without any application >>Changes. And, and where's the cloud come into play then, for you then, where, where did it come into play for you? >>So we started out actually helping out customers on premise, and a lot of enterprise customers are moving over to the cloud, and it was just a natural progression to do that. And so aws, which is a key part of ours, partners with us to help solve customer problems, especially on the database side, as the application being application performance tends to have issues between the interaction between the application database and we're solving that issue. >>Right. Sohan, I mean, Roan just touched on it about OnPrem, right? There's still some kickers and screamers out there that, that don't, haven't bought in or, or they're about to, but you're about to get 'em. I, I'm sure. But talk about that, that conversion or that transition, if you would, from going OnPrem into a hybrid environment or to into the, the bigger cloud environment and and how difficult that is sometimes. Yes. Maybe to get people to, to make that kind of a leap. >>Well, I would say that a lot of customers are wanting to focus more on product innovation experimentation, and also in terms of having to manage servers and patching, you know, it's to take away from that initiative that they're trying to do. So with aws, we provide undifferentiated heavy lifting so that they can focus on product innovation. And one of the areas talking about Heim is that from the database side, we do provide Amazon rds, which is database and also Aurora, to give them that lift so they don't have to worry about patching servers and setting up provisioning servers as well. >>Right. So Roland, can you get the idea across to people very simply, let us take care of the, the hard stuff and, and that will free you up to do your product innovations, to do your experimentations to, to really free up your team, basically to do the fun stuff and, and let us sweat over the, the, the details basically. Right? >>Exactly. Our, our motto is not only why build when, when you can buy. So a lot of it has to do with offering the, the value in terms of price and the features such as it's gonna benefit a team. Large companies like amazon.com, Google, they have huge teams that can build data access layers and proxies. And what we're trying to do here is commercialize those cuz those are built in house and it's not readily available for customers to use. And you'd need some type of interface between the application and the database. And we provide that sort of why build when you can buy. >>Well, I was gonna say why h right? I mean what's your special sauce? Because everybody's got something, obviously a market differentiator that you're bringing into place here. So you started to touch on a little bit there for me, but, but dive a little deeper there. I mean, what, what is it that, that you're bringing to the table with AWS that you think puts you above the crowd? >>Well, lemme give you a use case here. In typical events like let's say Black Friday where there's a surge traffic that can overwhelm the database, the Heim doll data access layer database proxy provides an auto scaling distributed architecture such that it can absorb those surges and traffic and help scale the database while keeping the data fresh and up to date. And so basically traffic based on season time of day, we can, we can adjust automatically and all these types of features that we offer, most notably automated query caching, ReadWrite split for asset compliance don't require any code changes, which typically requires the application developer to make those changes. So we're saving months, maybe years of development and maintenance. >>Yeah, a lot of gray hairs too, right? Yeah, you're, you're solving a lot of problems there. What about database trends in just in general Hunt, if you will. I mean, this is your space, right? I mean, what we're hearing about from Heindel, you know, in terms of solutions they're providing, but what are you seeing just from the macro level in terms of what people are doing and thinking about the database and how it relates to the cloud? Right. >>And some of the things that we're seeing is that we're seeing an explosion of data, relevant data that customers need to be able to consume and also process as well. So with the explosion of data, there's also, we see customers trying to modernize their application as well through microservices, which does change the design patterns of like the applications we call the access data patterns as well. So again, going back to that, a differentiated heavy lifting, we do have something called purpose built databases, right? It's the right tool for the right purpose. And so it depends on what their like rpo, rto their access to data pattern. Is it a base, is it an acid? So we want to be able to provide them the options to build and also innovate. So with that, that's why we have the Amazon rds, the also the, we also have Redshift, we also have Aurora and et cetera. The Rediff is more of the BI side, but usually when you ingest the data, you have some level of processing to get more insight. So with that, that's why customers are moving more of towards the managed service so that they can give that lift and then focusing on that product and innovation. Yeah. >>Have we kind of caught up or are we catching up to this just the tsunami of data to begin with, right? Because I mean, that was it, you know, what, seven, eight years ago when, when that data became kind of, or becoming king and, and reams and reams and reams and all, you know, can't handle it, right? And, and are we now able to manage that process and manage that flow and get the right data into the right hands at the right time? We're doing better with that. >>I would say that it, it definitely has grown in size of the amount of data that we're ingesting. And so with the scalability and agility of the cloud, we're able to, I would say, adapt to the rapid changes and ingestions of the data. So, so that's why we have things like Aurora servers to have that or auto scale so they can do like MySQL or Postgres and then they can still, like what you know, I'm trying to do is basically don't have to co do like any code changes. It would be a data migration. They still use the same underlying database on also mechanisms, but here we're providing them at scale on the cloud. >>Yeah. Our proxies, they must have for all databases. I mean, is that, is that essential these days? >>Well, good question John. I would say yes. And this is often built in house, as I mentioned, for large companies, they do build some type of data access layer or proxy and, or some utilize some orm, some object relational map to do it. And what again, what we're trying to do is offer this, put this out into the market commercially speaking, such that it can be readily used for, for all the customers to use rather than building it from scratch all the time. >>You know what I didn't ask you was Roy, how does AWS come into play for you then? And, and as in the startup mode, the focus that they've had in startups in general, but in you in particular, I mean, talk about that partnership or that relationship and the value that you're extracting from that. >>The ad AWS partnership has been absolutely wonderful. The collaboration, they have one of the best managed service databases. The value that it that adds in terms of the durability, the manageability, what the Heim doll data does is it compliments Amazon rds, Amazon Redshift very well in the sense that we're not replacing the database. What we're doing is we are allowing the customer to get the most out of the managed service database, whether it be Redshift or Aurora Serverless, rds, all without code changes. And or the analogy that I would give John is a car, a race car may be very fast, but it takes a driver to get to those fast speeds. We're the driver, the Hyundai proxy provides that intelligence so that you can get the most out of that database engine. >>And, and Hfi would then touch on, first off AWS and the emphasis that you have put on startups and are obviously, you know, kind of putting your money where your mouth is, right? With, with the way you've encouraged and nurtured that environment. And they would be about Heim doll in general about where you see this going or what you would like to have, where you want to take this in the next say 12 months, 18 months. >>I think it's more of a better together story of how we can basically coil with our partners, right? And, and basically focusing on helping our customers drive that innovation and be collaboration. So as Heim, as a independent service vendor isv, most customers can leverage that through a marketplace where basically it integrates very nicely with aws. So that gives 'em that lift and it goes back to the undifferentiated heavy lifting on the Hein proxy side, if you will, because then you have this proxy in the middle where then it helps them with their SQL performance. And I've seen use cases where customers were, have some legacy system that they may not have time to modernize the application. So they use this as a lift to keep, keep going as they try to modernize. But also I've seen customers who use are trying to use it as a, a way to give that performance lift because they may have a third party software that they cannot change the code by putting this in there that helps optimize their lines of business or whatever that is, and maybe can be online store or whatever. So I would say it was a better together type of story. >>Yeah. Which is, there's gotta be a song in there somewhere. So peek around the corner and if you wanna be headlights here right now in terms of 12, 18 months, I mean, what, you know, what what next to solve, right? You've already taken, you've slayed a few dragons along the way, but there are others I'm sure is it always happens in innovation in this space. Just when you solve a problem you've just dealt or you have to deal with others that pop up as maybe unintended consequences or at least a new challenge. So what would that be in your world right now? What, what do you see, you know, occupying your sleepless nights here for the next year or so? >>Well, for, for HOMEDALE data, it's all about improving database performance and scale. And those workloads change. We have O ltp, we have OLA with artificial intelligence ml. There's different type of traffic profiles and we're focused on improving those data profiles. It could be unstructured structured. Right now we're focused on structured data, which is relational databases, but there's a lot of opportunity to improve the performance of data. >>Well, you're driving the car, you got a good navigator. I think the GPS is working. So keep up the good work and thank you for sharing the time today. Thank you. Thank you, joy. Do appreciate it. All right, you are watching the cube. We continue our coverage here from AWS Reinvent 22, the Cube, of course, the leader in high tech coverage.

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

>>And good afternoon. Welcome back here on the Cub as to continue our coverage at aws Reinvent 22, win the Venetian here in Las Vegas, day two, it's Wednesday. Thanks. Still rolling. Quite a along. We have another segment for you as part of the Global Startup program, which is under the AWS Startup Showcase. I'm joined now by Vink at Viera, who is the CEO and co-founder of R Set. And good to see you, >>Sir. Thanks for having me here. Yeah, >>No, a real pleasure. Looking forward to it. So first off, for some of, for yours who might not be familiar with Roxette, I know you've been on the cube a little bit, so you're, you're an alum, but, but why don't you set the stage a little bit for Rock set and you know, where you're engaged with in terms of, with aws? >>Definitely. Rock Set is a realtime analytics database that is built for the cloud. You know, we make realtime applications possible in the cloud. You know, realtime applications need high concurrency, low latency query processing data needs to be fresh, your analytic needs to be fast. And, you know, we built on aws and that's why we are here. We are very, very proud partners of aws. We are in the AWS Accelerate program, and also we are in the startup program of aws. We are strategic ISV partner. And so yeah, we make real time analytics possible without all the cost and complexity barriers that are usually associated with it. And very, very happy to be part of this movement from batch to real time that is happening in the world. >>Right. Which is certainly an exciting trend. Right. I know great news for you, you made news yesterday, had an announcement involved with the intel with aws, who wants to share some of that >>With us too? Definitely. So, you know, one, one question that I always ask people is like, you know, if you go perspective that I share is like, if you go ask a hundred people, do you want fast analytics on fresh data or slow analytics on stale data? You know, a hundred out of a hundred would say fast and fresh, right? Sure. So then the question is, why hasn't this happened already? Why is this still a new trend that is emerging as opposed to something that everybody's taking for granted? It really comes down to compute efficiency, right? I think, you know, at the end of the day, real time analytics was always in using, you know, technologies that are, let's say 10 years ago using let's say processors that were available 10 years ago to, you know, three cloud, you know, days. There was a lot of complexity barriers associated with realtime analytics and also a lot of cost and, and performance barriers associated with it. >>And so Rox said from the, you know, from the very beginning, has been obsessing about building the most compute efficient realtime database in the world. And, you know, AWS on one hand, you know, allows us to make a consumption based pricing model. So you only pay for what you use. Sure. And that shatters all the cost barriers. But in terms of computer efficiency, what we announced yesterday is the Intel's third generation Zon scalable processors, it's code named Intel Ice Lake. When we port it over Rock said to that architecture, taking advantage of some of the instructions sets that Intel has, we got an 84% performance boost, 84, 84, 84. >>It's, it's incredible, right? >>It's, it's an incredible charts, it's an incredible milestone. It reduces the barrier even more in terms of cost and, you know, and, and pushes the efficiency and sets a, a really new record for how efficient realtime, you know, data processing can be in the cloud. And, and it's very, very exciting news. And so we used to benchmark ourselves against some of our other, you know, realtime, you know, did up providers and we were already faster and now we've set a, a much, much higher bar for other people to follow. >>Yep. And, and so what is, or what was it about real time that, that, you know, was such a barrier because, and now you've got the speed of, of course, obviously, and maybe that's what it was, but I think cost is probably part of that too, right? That's all part of that equation. I mean, real time, so elusive. >>Yeah. So real time has this inherent pattern that your data never stops coming. And when your data never stops coming, and you can now actually do analytics on that. Now, initially people start with saying, oh, I just want a real time dashboard. And then very quickly they realize, well, the dashboard is actually in real time. I'm not gonna be staring at the 24 7. Can you tap on my shoulder when something is off, something needs to be looked at. So in which case you're constantly also asking the question, is everything okay? Is everything all right? Do I need to, is is that something that I need to be, you know, double clicking on and, and following up on? So essentially very quickly in real time analytics, what happens is your queries never stop. The questions that you're asking on your data never stops. And it's often a program asking the question to detect anomalies and things like that. >>And your data never stops coming. And so compute is running 24 7. If you look at traditional data warehouses and data lakes, they're not really optimized for these kinds of workloads. They're optimized to store massive volumes of data and in a storage efficient format. And when an analyst comes and asks a question to generate a report, you can spin up a whole bunch of compute, generate the report and tear it all down when you're done. Well, that is not compute running 24 7 to continuously, you know, you know, keep ingesting the data or continuously keep answering questions. So the compute efficiency that is needed is, is much, much, much higher. Right? And that is why, you know, Rox was born. So from the very beginning, we're only built, you know, for these use cases, we have a, an extremely powerful SQL engine that can give you full feature SQL analytics in a very, very compute efficient way in the cloud. >>Right. So, so let's talk about the leap that you've made, say in the last two years and, and, and what's been the spur of that? What has been allowed you to, to create this, you know, obviously a, a different kind of an array for your customers from which to choose, but, but what's been the spark you think >>We touched upon this a little earlier, right? This spark is really, you know, the world going from batch to real time. So if you look at mainstream adoption of technologies like Apache, Kafka and Confluent doing a really good job at that. In, in, in growing that community and, and use cases, now businesses are now acquiring business data, really important business data in real time. Now they want to operationalize it, right? So, you know, extract based static reports and bi you know, business intelligence is getting replaced in all modern enterprises with what we call operational intelligence, right? Don't tell me what happened last quarter and how to plan this quarter better. Tell me what's happening today, what's happening right now. And it's, it's your business operations using data to make day to day decisions better that either grows your top line, compresses your bottom line, eliminates risk that are inherently creeping up in your business. >>Sure. You know, eliminate potential churn from a customer or fraud, you know, deduction and, and getting on top of, you know, that, you know, a minute into this, into, into an outage as opposed to an hour into the outage. Right? And so essentially I think businesses are now realizing that operational intelligence and operational analytics really, you know, allows them to leverage data and especially real time data to make their, you know, to grow their businesses faster and more efficiently. And especially in this kind of macro environment that is, you know, more important to have better unit economics in your business than ever before. Sure. And so that is really, I think that is the real market movement happening. And, and we are here to just serve that market. We are making it much, much easier for companies that have already adopted, you know, streaming technologies like Kafka and, and, and knows Canis MSK and all these technologies. Now businesses are acquiring these data in real time now. They can also get realtime analytics on the other end of it. Sure. >>You know, you just touched on this and, and I'd like to hear your thoughts about this, about, about the economic environment because it does drive decisions, right? And it does motivate people to look for efficiencies and maybe costs, you know, right. Cutting costs. What are you seeing right now in terms of that, that kind of looming influence, right? That the economy can have in terms of driving decisions about where investments are being made and what expectations are in terms of delivering value, more value for the buck? >>Exactly. I think we see across the board, all of our customers come back and tell us, we don't want to manage data infrastructure and we don't want to do kind of DIY open source clusters. We don't wanna manage and scale and build giant data ops and DevOps teams to manage that, because that is not really, you know, in their business. You know, we have car rental companies want to be better at car rentals, we want airlines to be a better airline, and they don't, don't want their, you know, a massive investment in DevOps and data ops, which is not really their core business. And they really want to leverage, you know, you know, fully managed and, you know, cloud offerings like Rock said, you know, built on aws, massively scalable in the cloud with zero operational overhead, very, very easy to get started and scale. >>And so that completely removes all the operational overhead. And so they can invest the resources they have, the manpower, they have, the calories that they have on actually growing their businesses because that is what really gonna allow them to have better unit economics, right? So everybody that is on my payroll is helping me grow my top line or shrink my bottom line, eliminate risk in my business and, and, and, and churn and, and fraud and other, and eliminate all those risks that are inherent in my business. So, so that is where I think a lot of the investments going. So gone are the days where, you know, you're gonna have these in like five to 10% team managing a very hard to operate, you know, open source data management clusters on EC two nodes in, in AWS and, and kind of DIYing it their way because those 10 people, you know, if all they do is just operational maintenance of infrastructure, which is a means to an end, you're way better off, you know, using a cloud, you know, a bond in the cloud built for the cloud solution like rock and eliminate all that cost and, and replace that with an operationally much, much simpler, you know, system to op, you know, to to work with such as, such as rock. >>So that is really the big trend that we are seeing why, you know, not only real time is going more and more mainstream cloud native solutions or the real future even when it comes to real time because the complexity barrier needs to be shattered and only cloud native solutions can actually, >>You get the two Cs cost and complexity, right. That you, you need to address. Exactly. Yeah, for sure. You know, what is it about building trust with your, with your clients, with your partners? Because you, you're talking about this cloud environment that, that everyone is talking about, right? Not everyone's made that commitment. There are still some foot draggers out there. How are you going about establishing confidence and establishing trust and, and, and providing them with really concrete examples of the values and the benefits that you can provide, you know, with, with these opportunities? >>So, you know, I grew up, so there's a few ways to to, to answer this question. I'll, I'll, I'll come, I'll cover all the angles. So in, in order to establish trust, you have to create value. They, you know, your customer has to see that with you. They were able to solve the problem faster, better, cheaper, and they're able to, you know, have a, the business impact they were looking for, which is why they started the project in the first place. And so establishing that and proving that, I think there's no equivalence to that. And, you know, I grew up at, at, you know, at Facebook back in the day, you know, I was managing online data infrastructure, okay. For Facebook from 2007 and 2015. And internally we always had this kind of culture of all the product teams building on top of the infrastructure that my team was responsible for. >>And so they were not ever, there was never a, a customer vendor relationship internally within Facebook that we're all like, we're all part of the same team. We're partnering here to have you, you know, to help you have a successful product launch. There's a very similar DNA that, that exists in Rock said, when our customers work with us and they come to us and we are there to make them successful, our consumption based pricing model also forces us to say they're not gonna really use Rock said and consume more. I mean, we don't make money until they consume, right? And so their success is very much integral part of our, our success. And so that I think is one really important angle on, you know, give us a shot, come and do an evaluation, and we will work with you to build the most efficient way to solve your problem. >>And then when you succeed, we succeed. So that I think is a very important aspect. The second one is AWS partnership. You know, we are an ISV partner, you know, AWS a lot of the time. That really helps us establish trust. And a lot of the time, one of the, the, the people that they look up to, when a customer comes in saying, Hey, what is, who is Rock? Said? You know, who are your friends? Yeah. Who are your friends? And then, you know, and then the AWS will go like, oh, you know, we'll tell you, you know, all these other successful case studies that R has, you know, you know, built up on, you know, the world's largest insurance provider, Europe's largest insurance provider. We have customers like, you know, JetBlue Airlines to Klarna, which is a big bator company. And so, so all these case studies help and, and, and, and platform and partners like AWS helps us, helps you amplify that, that, you know, and, and, and, and, and give more credibility. And last but not least, compliance matters. You know, being Soto type two compliant is, is a really important part of establishing trust. We are hip hop compliant now so that, you know, we can, you know, pi I phi data handling that. And so I think that will continue to be a part, a big part of our focus in improving the security, you know, functionality and, and capabilities that R set has in the cloud, and also compliance and, and the set of com, you know, you know, standards that we are gonna be compliant against. >>Well, I'm glad you hit on the AWS too, cause I did wanna bring that up. I, I appreciate that and I know they appreciate the relationship as well. Thanks for the time here. It's been a pleasure. Awesome. Learning about Rockette and what you're up to. Thank you. >>You bet. >>It's a pleasure. Thank you. Vi ka. All right. You are watching the cube coverage here at AWS Reinvent 22. And on the cube, of course, the leader, the leader in high tech coverage.

>>Well, hello everybody at John Wallace here on the Cube, and glad to have you along here for day two of our coverage here at AWS Reinvent 22. We're up in the global startup program, which is part of AWS's Startup Showcase, and I've got Kevin Farley with me. He is the director of Strategic Alliances with Maria Day db. And Kevin, good to see you this morning. Good to see you, John. Thanks for joining us. Thank >>You. >>Appreciate it. Yeah. First off, tell us about Maria db. Sure. Obviously data's your thing. Yep. But to share that with some folks at home who might not be familiar with your offering. >>Yeah. So Maria DB's been around as a corporate entity for 10 plus years, and we have a massive customer base. You know, there's a billion downloads from Docker Hub, 75% of the Fortune 500. We have an enormous sea of really happy users. But what we realize is that all of these users are really thinking about what do we, what does it mean to transform it? What does cloud modernization mean? And how do we build a strategy on something we really love to drive it into the cloud and take it to the future. So what we launched about two years ago, two and a half years ago, is Skye. It's our database as a service. It leverages all the best elements, what we provide on the enterprise platform. It marries to the AWS cloud, and it really provides the best of both worlds for our >>Customers. So in your thought then, what, what problem is that solving? >>I think what you see in the overall database market is that many people have been using what we would call legacy technology. There's been lots of sort of stratification and mixes of different database solutions. All of them come with some promise, and all of 'em come with a lot of compromise. So I think what the market is really looking for is something that can take what they know and love, can bring it to the cloud and can survive the port drive the performance and scale. That completely changes the landscape, especially as you think about what modern data needs look like, right? What people did 10 years ago with the exponential scale of data no longer works. And what they need is something that not only can really deliver against their core business values and their core business deliverables, but gets 'em to the future. How do we drive something new? How do we innovate? How do we change the game? And I think what we built with AWS really delivers what we call cloud scale. It's taking something that is the best technology, and I as a V can build, marrying it to, you know, Kubernetes layer, marrying it to global availability, thinking about having true global high availability across all of your environments and really delivering that to customers through an integrated partnership. >>Could we see this coming? I mean, because you know data, right? I mean, yeah, we, we, everybody talked about the tsunami of growth, you know, >>Back 10 >>Sure. 11 years ago. But, but maybe the headlights didn't go far enough or, or, but, but you could see that there was going to be crunch time. >>There's no doubt. And I think that this has been a, there's, there's been these sort of pocket solutions, right? So if you think at the entire no sequel world, right? People said, oh, I need scale, I can get it, but what do I have to give up asset compliance? So I have to change the way I think about what data is and how I, I can govern it. So there's been these things that deliver on half the promise, but there's never been something that comes together and really drives what we deliver through CIQ is something called expand. So distributed SQL really tied to the SQL Query language, having that asset data. So having everything you need without the compromise built on the cloud allows you to scale out and allows you to think about, I can actually do exponential layers of, of data, data modeling, data querying, complete read, write, driving that forward. And I think it gives us a whole nother dynamic that we can deliver on in a way that hasn't been before. And I think that's kind of the holy grail of what people are looking for is how am I building modern applications and how do I have a database in the cloud that's really gonna support >>It? You know, you talk about distributed, you know, sequel and, and I mean, there's a little mystery behind it, isn't there? Or at least maybe not mystery. There's a little, I guess, confusion or, or just misunderstanding. I mean, I, how, nail that down a little bit. I >>Would say the best way to say it, honestly, this is the great thing, is it people believe it's too good to be true. And I think what we see over and over >>Again, you know, what they say about that. >>But this is the great part is, you know, you know, we've just had two taste studies recently with aws, with HIT labs and Certified power, both on expand, both proof in the pudding. They did the POCs, they're like, oh my God, this works. If you watch the keynote yesterday, you know, Adam had a slide that was, you know, as big as the entire room and it highlighted Samsung and they said, you know, we're doing 80,000 requests per second. So the, you know, the story there is that AWS is able as, as an entity with their scale and their breadth to handle that kind of workload. But guess what that is? That's MariaDB expand underneath there driving all of that utilization. So it's already there, it's already married, it's already in the cloud, and now we're taking it to a completely different level with a fully managed database solution. Right? >>How impressive is that? Right? I mean, you would think that somebody out there who, I mean that that volume, that kind of capacity is, is mind blowing. >>I mean, to your kind of previous point, it's like one of those things, do I see what's coming and it's here, right? You know, it's, is it actually ever gonna be possible? And now we're showing that it really is on a daily basis for some of the biggest brands in the world. We're also seeing companies moving off not only transitioning from, you know, MariaDB or myse, but all of the big licensed, you know, conversions as well. So you think about Oracle DBS Bank is one of our biggest customers, one of the largest Oracle conversions in the world onto MariaDB. And now thinking about what is the promise of connecting that to the cloud? How do you take things that you're currently doing, OnPrem delivering a hybrid model that also then starts to say, Hey, here's my path to cloud modernization. Skye gives me that bridge. And then you take it one layer farther and you think about multi-cloud, right? That's one of the things that's critical that ISVs can really only deliver in a meaningful way, is how can we have a solution for a customer that we can take to any availability zone. We can have performance, proximity, cost, proximity. We're always able to have that total data dexterity across any environment we need and we can build on that for the future. >>So if, if we're talking about cloud database and there's so many good things going forward here. You're talking about easy use and scalability and all that. But as with ever have you talked about this, there's some push and there's some pull. Yeah. So, so what's the, what's the other side that's still, you know, you that you think has to be >>Addressed? And I think that's a great question. So there's, we see that there's poll, right? We've seen these deals, this pipeline growth, this, there's great adoption. But what I think we're still not at the point of massive hockey stick adoption is that customers still don't fully understand the capabilities distributed SQL and the power they can actually deliver. So the more we drive case studies, the more we drive POCs, the more we prove the model, I think you're gonna see just a massive adoption scale. And I also think customers are tired of doing lots of different things in lots of different pockets. So neither one of the key elements of Sky SQL is we can do both transactional and analytical data out of the same database driven by the same proxy. So what, instead of having DBAs and developers try to figure out, okay, I'm gonna pull from this database here. >>Yeah. That there, it's, it's this big spaghetti wire concept that is super expensive and super time intensive. So the ability to write modern applications and pull data from both pockets and really be able to have that as a seamless entity and deliver that to customers is massive. I mean, another part of the keynote yesterday was a new deliverable, like kind of no etl. Adam talked about Aurora and Redshift and the massive complexity of what used to exist for getting data back and forth. You also have to pay for two different databases. It's super expensive. So I think the idea that you can take the real focus of AWS and US is customer value. How do you deliver that next thing that changes the game? Always utilizes AWS delivers on that promise, but then takes a net new technology that really starts to think about how do we bring things together? How do we make it more simple? How do we make it more powerful? And how do we deliver more customer value as we go forward? >>But you know, if, if I'm, I'm still an on-prim guy, just pretend I'm not saying I am. Just pretend I just for the sake of the discussion here, it's like I just can't let it go. Yeah. Right. I, I still, you know, there's control, there's the known versus the unknown. The uncertain. Yeah. So twist my arm just a little bit more and get me over the hum. >>Well, first of all, you don't have to, right? And there's gonna be some industries and some verticals that will always have elements of their business that will be OnPrem. Guess what? We make the best based in the world. It can be MariaDB, but there's those that then say, these, these elements of our business are gonna be far more effective moving to the cloud. So we give you Skye, there's a natural symbiotic bridge between everything we do and how we deliver it. Where you can be hybrid and it's great. You can adopt the cloud as your business needs grow. And you can have multi-cloud. This is that, that idea that you can, can have your cake and eat it too, right? You can literally have all these elements of your business met without these big pressure to say, you gotta throw that away. You gotta move to this. It's really, how do you kind of gracefully adopt the cloud in a way that makes sense for your business? Where are you trying to drive your business? Is it time to value, right? Is it governance? Is it is there's different elements of what matters the most to individual businesses. You know, we wanna address those and we can address >>Those. So you're saying you don't have to dive >>In, you don't have to dive >>In. You, you can, you can go ankle deep, knee deep, whatever you wanna >>Do. Absolutely. And you know, some of the largest MariaDB users still have massive, massive on-prem implementations. And that's okay. But there's elements that are starting to fall behind. There's cost savings, there's things that they need to do in the cloud that they can't do. OnPrem. And that's where expand Skye really says, okay, here is your platform. Grow as you want to, migrate as you want to. And we're there every step along the way. We, we also provide a whole Sky DBA team. Some guys just say, I wanna get outta the database world at all. This is, this is expensive, it's costly and it's difficult to be an expert. So you can bring in our DBA team and they'll man and run, they'll, they'll run your entire environment. They'll optimize it, you know, they'll troubleshoot it, they'll bug fix, they'll do everything for you. So you can just say, I just wanna focus on building phenomenal applications for my customers. And the database game as we knew it is not something that I know I want to invest in anymore. Right. I wanna make that transition >>That makes that really, yeah. You know, I mean really attractive to a lot of people because you are, you talk about a lot of headache there. Yeah. So let's talk about AWS before Sure. I let you go just about that relationship. Okay. You've talked about the platform that it provides you and, and obviously the benefits, but just talk about how you've worked with AWS over the years Yep. And, and how you see that relationship allowing you to expand your services, no pun intended. >>For sure. So, I mean, I would start with the way we even contemplated architecture. You know, we worked with the satisfactory team. We made sure that the things that we built were optimized in their environment. You know, I think it was a lot of collaboration on how does this combined entity really make the most value for our customers? How does it make the most sense for our developers as we build it out? Then we work in the, in the global startup team. So the strategic element of who we are, not all startups are created equal, right? We have, right, we have 75% of the Fortune 100, we've got over a billion downloads. So, you know, we come in with promise. And the reason this partnership is so valuable and the reason there's so much investment going forward is cuz what really, what do the cloud guys care about? >>The very, very most, they want all of these mission critical, big workloads that are on prem to land in their cloud. What do we have a massive, massive TAM sitting out there, these customers that could go to aws. So we both see, like if we can deliver incredible value to that customer base, these big workloads will end up in aws. They'll use other AWS services. And as we scale and grow, you know, we have that platform that's already built for it. So I think that when you go back to like the tenants, the core principles of aws, the one that always stands out, the one that we always kind of lean back on is, are we delivering customer value? Is this the best thing for the customer? Because we do have some competition just like many other, other partners do, right? So there is Aurora and there is rds and there is times when that's a great service for a customer. But when people are really thinking about where do I need my database to go? Where do I really need to be set for the future growth? Where am I gonna get the kind of ROI I need going forward? That's where you can go, Hey, sky sql, expand distributed sql. This is the best game in town. It's built on aws and collectively, you know, we're gonna present that to a customer. I'm >>Sold. Done. >>I love it. Right? >>Maria db, check 'em out, they're on the show floor. Great traffic. I know at at the, at the booth. They're here at AWS Reinvent. So check 'em out. Maria db. Thanks >>Kevin. Hey, thanks John. Appreciate your >>Time. Appreciate Great. That was great. Right back with more, you're watching the cube, the leader in high tech coverage.

>>Welcome back here on the Cube. I'm John Walls. We are in Las Vegas at the Venetian, and this is Reinvent 22 in the Executive Summit sponsored by Accenture. Glad to have you with us here as we continue our conversations. I'm joined by Paul Puckett, who's the former director of the Enterprise Cloud Management Services at the US Army. Paul, good to see you sir. Hey, you as well, John. Thank you. And Justin, she who is managing director and cloud go to market lead at Accenture Federal Services. Justin, good morning to you. Good morning, John. Yeah, glad to have you both here on the cube. First time too, I believe, right? Yes sir. Well, welcome. I wish we had some kind of baptism or indoctrination, but I'll see what I can come up with in the next 10 minutes for you. Let's talk about the Army, Paul. So enterprise cloud management, US Army. You know, I can't imagine the scale we're talking about here. I can't imagine the solutions we're talking about. I can't imagine the users we're talking about. Just for our folks at home, paint the picture a little bit of what kind of landscape it is that you have to cover with that kind of title. >>Sure. The United States Army, about 1.4 million people. Obviously a global organization responsible for protecting and defending the United States as part of our sister services in the Department of Defense. And scale often comes up a lot, right? And we talk about any capability to your solution for the United States Army scale is the, the number one thing, but oftentimes people overlook quality first. And actually when you think of the partnership between the Army and Accenture Federal, we thought a lot when it came to establishing the enterprise Cloud management agency that we wanted to deliver quality first when it came to adopting cloud computing and then scale that quality and not so much be afraid of the, the scale of the army and the size that forces us to make bad decisions. Cuz we wanted to make sure that we proved that there was opportunity and value in the cloud first, and then we wanted to truly scale that. And so no doubt, an immense challenge. The organization's been around for now three years, but I think that we've established irreversible momentum when it comes to modernization, leveraging cloud computing >>For the army. So let's back up. You kind of threw it in there, the ecma. So this agency was, was your a collaboration, right? To create from the ground up and it's in three years in existence. So let's just talk about that. What went into that thinking? What went into the planning and then how did you actually get it up and run into the extent that it is today? >>Sure. Well, it was once the enterprise cloud management office. It was a directorate within the, the CIO G six of the United States Army. So at the headquarters, the army, the chief information Officer, and the G six, which is essentially the military arm for all IT capability were once a joint's organization and the ECMO was created to catalyze the adoption of cloud computing. The army had actually been on a, a cloud adoption journey for many years, but there wasn't a lot of value that was actually derived. And so they created the ecma, well, the ECMO at the time brought me in as the director. And so we were responsible for establishing the new strategy for the adoption of cloud. One of the components of that strategy was essentially we needed an opportunity to be able to buy cloud services at scale. And this was part of our buy secure and build model that we had in place. And so part of the buy piece, we put an acquisition strategy together around how we wanted to buy cloud at scale. We called it the cloud account management optimization. OTA >>Just rolls right off the >>Tongue, it just rolls right off the tongue. And for those that love acronyms, camo, >>Which I liked it when I was say cama, I loved that. That was, that was, >>You always have to have like a tundra, a little >>Piece of that. Very good. It was good. >>But at the time it was novetta, no, Nevada's been bought up by afs, but Novea won that agreement. And so we've had this partnership in place now for just about a year and a half for buying cloud computing net scale. >>So let's talk about, about what you deal with on, on the federal services side here, Justin, in terms of the army. So obviously governance, a major issue, compliance, a major issue, security, you know, paramount importance and all that STEM leads up to quality that Paul was talking about. So when you were looking at this and keeping all those factors in, in your mind, right? I mean, how many, like, oh my God, what kind of days did you have? Oh, well, because this was a handful. >>Well, it was, but you could see when we were responding to the acquisition that it was really, you know, forward thinking and forward leaning in terms of how they thought about cloud acquisition and cloud governance and cloud management. And it's really kind of a sleepy area like cloud account acquisition. Everyone's like, oh, it's easy to get in the cloud, you know, run your credit card on Amazon and you're in, in 30 seconds or less. That's really not the case inside the federal government, whether it's the army, the Air Force or whoever, right? Those, those are, they're real challenges in procuring and acquiring cloud. And so it was clear from, you know, Paul's office that they understood those challenges and we were excited to really meet them with them. >>And, and how, I guess from an institutional perspective, before this was right, I I assume very protective, very tight cloistered, right? You, you, in terms of being open to or, or a more open environment, there might have been some pushback was they're not. Right? So dealing with that, what did you find that to be the case? Well, so >>There's kind of a few pieces to unpacking that. There's a lot of fear in trepidation around something you don't understand, right? And so part of it is the teaching and training and the, and the capability and the opportunity in the cloud and the ability to be exceptionally secure when it comes to no doubt, the sensitivity of the information of the Department of Defense, but also from an action acquisition strategy perspective, more from a financial perspective, the DOD is accustomed to buying hardware. We make these big bets of these big things to, to live in today's centers. And so when we talk about consuming cloud as a utility, there's a lot of fear there as well, because they don't really understand how to kind of pay for something by the drink, if you will, because it incentivizes them to be more efficient with their utilization of resources. >>But when you look at the budgeting process of the d od, there really is not that much of incentive for efficiency. The p PPE process, the planning program, budgeting, execution, they care about execution, which is spending money and you can spend a lot of money in the cloud, right? But how are you actually utilizing that? And so what we wanted to do is create that feedback loop and so the utilization is actually fed into our financial systems that help us then estimate into the future. And that's the capability that we partnered with AFS on is establishing the closing of that feedback loop. So now we can actually optimize our utilization of the cloud. And that's actually driving better incentives in the PPE >>Process. You know, when you think about these keywords here, modernized, digitized, data driven, so on, so forth, I, I don't think a lot of people might connect that to the US government in general just because of, you know, it's a large intentionally slow moving bureaucratic machine, right? Is that fair to characterize it that way? It >>Is, but not in this case. Right? So what we done, >>You you totally juxtapose that. Yeah. >>Yeah. So what we've done is we've really enabled data driven decision making as it relates to cloud accounts and cloud governance. And so we have a, a tool called Cloud Tracker. We deployed for the army at a number of different classifications, and you get a full 360 view of all of your cloud utilization and cloud spend, you know, really up to date within 24 hours of it occurring, right? And there a lot of folks, you know, they didn't never went into the console, they never looked at what they were spending in cloud previously. And so now you just go to a simple web portal and see the entire entirety of the army cloud spend right there at your fingertips. So that really enables like better decision making in terms of like purchasing savings plans and reserved instances and other sorts of AWS specific tools to help you save money. >>So Paul, tell me about Cloud Tracker then. Yeah, I mean from the client side then, can you just say this dashboard lays it out for you right? In great detail about what kind of usage, what kind of efficiencies I assume Yeah. What's working, what's not? >>Absolutely. Well, and, and I think a few things to unpack that's really important here is listen, any cloud service provider has a concept. You can see what you're actually spending. But when it comes to money in the United States government, there are different colors of money. There's regulations when it comes to how money is identified for different capabilities or incentives. And you've gotta be very explicit in how you track and how you spend that money from an auditability perspective. Beyond that, there is a move when it comes to the technology business management, which is the actual labeling of what we actually spend money on for different services or labor or software. And what Cloud Tracker allows us to do is speak the language of the different colors of money. It allows us to also get very fine grain in the actual analysis of, from a TBM perspective, what we're spending on. >>But then also it has real time hooks into our financial systems for execution. And so what that really does for us is it allows us to complete the picture, not just be able to see our spend in the cloud, but also be able to able to see that spending context of all things in the P P P E process as well as the execution process that then really empowers the government to make better investments. And all we're seeing is either cost avoidance or cost savings simply because we're able to close that loop, like I said. Yep. And then we're able to redirect those funds, retag them, remove them through our actual financial office within the headquarters of the army, and be able to repurpose that to other modernization efforts that Congress is essentially asking us to invest >>In. Right. So you know how much money you have, basically. Exactly. Right. You know how much you've already spent, you know how you're spending it, and now you how much you have left, >>You can provide a reliable forecast for your spend. >>Right. You know, hey, we're, we're halfway through this quarter, we're halfway through the, the fiscal year, whatever the case might be. >>Exactly. And the focus on expenditures, you know, the government rates you on, you know, how much have you spent, right? So you have a clear total transparency into what you're going to spend through the rest of the fiscal. Sure. >>All right. Let's just talk about the relationship quickly then about going forward then in terms of federal services and then what on, on the, the US Army side. I mean, what now you've laid this great groundwork, right? You have a really solid foundation where now what next? >>We wanna be all things cloud to the army. I mean, we think there's tremendous opportunity to really aid the modernization efforts and governance across the holistic part of the army. So, you know, we just, we want to, we wanna do it all with the Army as much as we can. It's, it's, it's a fantastic >>Opportunity. Yeah. AFS is, is in a very kind of a strategic role. So as part of the ecma, we own the greater strategy and execution for adoption of cloud on behalf of the entire army. Now, when it comes to delivery of individual capabilities for mission here and there, that's all specific to system owners and different organizations. AFS plays a different role in this instance where they're able to more facilitate the greater strategy on the financial side of the house. And what we've done is we've proven the ability to adopt cloud as a utility rather than this fixed thing, kind of predict the future, spend a whole bunch of money and never use the resource. We're seeing the efficiency for the actual utilization of cloud as a utility. This actually came out as one of the previous NDAs. And so how we actually address nda, I believe it was 2018 in the adoption of cloud as a utility, really is now cornerstone of modernization across all of the do d and really feeds into the Jo Warfighting cloud capability, major acquisition on behalf of all of the D O D to establish buying cloud as just a common service for everyone. >>And so we've been fortunate to inform that team of some of our lessons learned, but when it comes to the partnership, we just see camo moving into production. We've been live for now a year and a half. And so there's another two and a half years of runway there. And then AFS also plays a strategic role at part of our cloud enablement division, which is essentially back to that teaching part, helping the Army understand the opportunity of cloud computing, align the architectures to actually leverage those resources and then deliver capabilities that save soldier's >>Lives. Well, you know, we've, we've always known that the Army does its best work on the ground, and you've done all this groundwork for the military, so I'm not surprised, right? It's, it's a winning formula. Thanks to both of you for being with us here in the executive summit. Great conversation. Awesome. Thanks for having us. A good deal. All right. Thank you. All right. You are watching the executive summit sponsored by Accenture here at Reinvent 22, and you're catching it all on the cube, the leader in high tech coverage.

(bright upbeat music) >> Well, hi everybody, John Wallace here and welcome to theCUBE, the leader in high-tech coverage. Glad to have you aboard here as we continue our coverage here at re:Invent 2022. We're out at The Venetian in Las Vegas. A lot of energy down on that exhibit floor, I promise you. We're a little bit away from the maddening crowd, but we're here with the Executive Summit sponsored by Accenture. I've got two guests I want to introduce you to. Jason Beyer who is the vice president of Data and Analytics at Bridgestone Americas. Jason, good to see you, sir. >> Hello, John. >> And Josh von Schaumburg, who is the managing director and North America lead for AWS Security at Accenture. Josh, good to see you. >> Thanks for having us. >> Yeah, first off, just quick take on the show. I know you've only been here about a day or so, but just your thoughts about what you're seeing on the floor in terms of energy, enthusiasm and, I think, turnout, right? I'm really impressed by it. We've got a lot of people down there. >> Yeah, I've been certainly impressed, John, with the turnout. But just as you say, the energy of the crowd, the excitement for the new things coming, it seems like it's a really pivotal moment for many organizations, including my own, and really excited to see what's coming over the next couple days. >> Let's jump into Bridgestone then. I kind of kidded you before we started the interview saying, all right, tires and golf balls, that's what I relate to, but you have a full array of consumer products and solution you're offering and your responsibility is managing the data and the analytics and making sure those business lines are as efficient as possible. >> Absolutely, John. So in my role, I have the privilege of being in an enterprise position. So I get to see the vast array of Bridgestone, which it is a large, highly vertically integrated company all the way from raw material sourcing of natural rubber to retail services in the automotive industry. We're at scale across those areas. The exciting thing about the company right now is we're going through this business transformation of becoming, you know, building on that heritage and that great legacy of having high quality high performance, highly focused on safety products to becoming a product and solutions company, and particular a sustainable solutions company. So what that means is we're bringing not only those great products to market, tires, golf balls, hoses, all kinds of rubber, air springs products to market, but thinking about how do we service those after they're in the market, how do we bring solutions to help fleets, vehicle owners, vehicle operators operate those in a sustainable way, in a cost effective way? So those solutions, of course, bring all new sets of data and analytics that come with it, and technology and moving to the cloud to be cloud native. So this new phase for the organization that we refer to as Bridgestone 3.0, and that business strategy is driving our cloud strategy, our technology strategy, and our data strategy and AWS and Accenture are important partners in that. >> Yeah, so we hear a lot about that these days about this transformation, this journey that people are on now. And Josh, when Bridgestone or other clients come to you and they talk about their migrations and what's their footprint going to look like and how do they get there, in the case of Bridgestone when they came to you and said, "All right, this is where we want to go with this. We're going to embark on a significant upgrade of our systems here," how do you lead 'em? How do you get 'em there? >> Yeah, I think there are a couple key cloud transformation value drivers that we've emphasized and that I've seen at Bridgestone in my time there. I mean, number one, just the rapid increase in the pace of innovation that we've seen over the last couple years. And a lot of that is also led by the scalability of all of the cloud native AWS services that we're leveraging, and in particular with the CDP platform. It really started off as a single-use case and really a single-tenant data lake. And then through the strategic vision of Jason and the leadership team, we've been able to expand that to 10 plus tenants and use cases. And a big reason behind that is the scalability of all these AWS services, right? So as we add more and more tenants, all the infrastructure just scales without any manual provisioning any tuning that we need to do. And that allows us to go really from idea, to POC, to production in really a matter of months when traditionally it might take years. >> So- >> If I can build upon that. >> Please do, yeah. >> The CDP, or central data platform, is part of a broader reference architecture that reflects that business strategy. So we looked at it and said, we could have taken a couple of different approaches to recognize the business challenges we're facing. We needed to modernize our core, our ERP, our manufacturing solutions move to smart factory and green factories, our PLM solutions. But at the same time, we're moving quickly. We have a startup mindset in our mobility solutions businesses where we're going to market on our customer and commerce solutions, and we needed to move at a different pace. And so to decouple those, we, in partnership with Accenture and AWS, built out a reference architecture that has a decoupling layer that's built around a data fabric, a data connected layer, integrated data services as well. A key part of that architecture is our central data platform built on AWS. This is a comprehensive data lake architecture using all the modern techniques within AWS to bring data together, to coalesce data, as well as recognize the multiple different modes of consumption, whether that's classic reporting, business intelligence, analytics, machine learning data science, as well as API consumption. And so we're building that out. A year ago it was a concept on a PowerPoint and just show and kind of reflect the innovation and speed. As Josh mentioned, we're up to 10 tenants, we're growing exponentially. There's high demand from the organization to leverage data at scale because of the business transformation that I mentioned and that modernization of the core ecosystem. >> That's crazy fast, right? And all of a sudden, whoa! >> Faster than I expected. >> Almost snap overnight. And you raise an interesting point too. I think when you talk about how there was a segment of your business that you wanted to get in the startup mode, whereas I don't think Bridgestone, I don't think about startup, right? I think in a much more, I wouldn't say traditional, but you've got big systems, right? And so how did you kind of inject your teams with that kind of mindset, right? That, hey, you're going to have to hit the pedal here, right? And I want you to experiment. I want you to innovate. And that might be a little bit against the grain from what they were used to. >> So just over two years ago, we built and started the organization that I have the privilege of leading, our data and analytics organization. And it's a COE. It's a center of expertise in the organization. We partner with specialized teams in product development, marketing, other places to enable data and analytics everywhere. We wanted to be pervasive, it's a team sport. But we really embraced at that moment what we refer to as a dual speed mindset. Speed one, we've got to move at the speed of the business. And that's variable. Based on the different business units and lines of lines of business and functional areas, the core modernization efforts, those are multi-year transformation programs that have multiple phases to them, and we're embedded there building the fundamentals of data governance and data management and reporting operational things. But at the same time, we needed to recognize that speed of those startup businesses where we're taking solutions and service offerings to market, doing quick minimum viable product, put it in a market, try it, learn from it adapt. Sometimes shut it down and take those learnings into the next area as well as joint ventures. We've been much more aggressive in terms of the partnerships in the marketplace, the joint ventures, the minority investments, et cetera, really to give us that edge in how we corner the market on the fleet and mobility solutions of the future. So having that dual speed approach of operating at the speed of the business, we also needed to balance that with speed two, which is building those long term capabilities and fundamentals. And that's where we've been building out those practical examples of having data governance and data management across these areas, building robust governance of how we're thinking about data science and the evolution of data science and that maturity towards machine learning. And so having that dual speed approach, it's a difficult balancing act, but it's served us well, really partnering with our key business stakeholders of where we can engage, what services they need, and where do we need to make smart choices between those two different speeds. >> Yeah, you just hit on something I want to ask Josh about, about how you said sometimes you have to shut things down, right? It's one thing to embark on I guess a new opportunity or explore, right? New avenues. And then to tell your client, "Well, might be some bumps along the way." >> Yeah. >> A lot of times people in Jason's position don't want to hear that. (laughs) It's like, I don't want to hear about bumps. >> Yeah. >> We want this to be, again, working with clients in that respect and understanding that there's going to be a learning curve and that some things might not function the way you want them to, we might have to take a right instead of a left. >> Yeah, and I think the value of AWS is you really can fail fast and try to innovate and try different use cases out. You don't have any enormous upfront capital expenditure to start building all these servers in your data center for all of your use cases. You can spin something up easily based in idea and then fail fast and move on to the next idea. And I also wanted to emphasize I think how critical top-down executive buy-in is for any cloud transformation. And you could hear it, the excitement in Jason's voice. And anytime we've seen a failed cloud transformation, the common theme is typically lack of executive buy-in and leadership and vision. And I think from day one, Bridgestone has had that buy-in from Jason throughout the whole executive team, and I think that's really evident in the success of the CDP platform. >> Absolutely. >> And what's been your experience in that regard then? Because I think that's a great point Josh raised that you might be really excited in your position, but you've got to convince the C-suite. >> Yeah. >> And there are a lot of variables there that have to be considered, that are kind of out of your sandbox, right? So for somebody else to make decisions based on a holistic approach, right? >> I could tell you, John, talking with with peers of mine, I recognize that I've probably had a little bit of privilege in that regard because the leadership at Bridgestone has recognized to move to this product and solutions organization and have sustainable solutions for the future we needed to move to the cloud. We needed to shift that technology forward. We needed to have a more data-driven approach to things. And so the selling of that was not a huge uphill a battle to be honest. It was almost more of a pull from the top, from our global group CEO, from our CEOs in our different regions, including in Bridgestone Americas. They've been pushing that forward, they've been driving it. And as Josh mentioned, that's been a really huge key to our success, is that executive alignment to move at this new pace, at this new frame of innovation, because that's what the market is demanding in the changing landscape of mobility and the movement of vehicles and things on the road. >> So how do you two work together going forward, Ben? Because you're in a great position now. You've had this tremendous acceleration in the past year, right? Talking about this tenfold increase and what the platform's enabled you to do, but as you know, you can't stand still. Right? (laughs) >> Yeah. There's so much excitement, so many use cases in the backlog now, and it's really been a snowball effect. I think one of the use cases I'm most excited about is starting to apply ML, you know, machine learning to the data sets. And I think there's an amazing IoT predictive maintenance use case there for all of the the censored data collected across all of the tires that are sold. There's an immense amount of data and ultimately we can use that data to predict failures and make our roads safer and help save lives >> Right. >> It's hard to not take a long time to explain all the things because there is a lot ahead of us. The demand curve for capabilities and the enabling things that AWS is going to support is just tremendous. As Josh mentioned, the, the AI ML use cases ahead of us, incredibly exciting. The way we're building and co-innovating things around how we make data more accessible in our data marketplace and more advanced data governance and data quality techniques. The use of, you know, creating data hubs and moving our API landscape into this environment as well is going to be incredibly empowering in terms of accessibility of data across our enterprise globally, as well as both for our internal stakeholders and our external stakeholders. So, I'll stop there because there's a lot of things in there. >> We could be here a long time. >> Yes, we could. >> But it is an exciting time and I appreciate that you're both sharing your perspectives on this because you've got a winning formula going and look forward to what's happening. And we'll see you next year right back here on the Executive Summit. >> Absolutely. >> To measure the success in 2023. How about that? >> Sounds good, thank you, Jim. >> Is that a deal? >> Awesome. >> Sounds good. >> Excellent, good deal. You've been watching AWS here at Coverage of Reinvent '22. We are the Executive Summit sponsored by Accenture and you are watching theCUBE, the leader in high tech coverage. (gentle music)

(upbeat music) >> You got it, it's theCUBE. We are in Vegas. This is the Cube's live coverage day one of the full event coverage of AWS reInvent '22 from the Venetian Expo Center. Lisa Martin here with Dave Vellante. We love being in Vegas, Dave. >> Well, you know, this is where Super Cloud sort of was born. >> It is. >> Last year, just about a year ago. Steve Mullaney, CEO of of Aviatrix, you know, kind of helped us think it through. And we got some fun stories around. It's happening, but... >> It is happening. We're going to be talking about Super Cloud guys. >> I guess I just did the intro, Steve Mullaney >> You did my intro, don't do it again. >> Sorry I stole that from you, yeah. >> Steve Mullaney, joined just once again, one of our alumni. Steve, great to have you back on the program. >> Thanks for having me back. >> Dave: It's happening. >> It is happening. >> Dave: We talked about a year ago. Net Studio was right there. >> That was two years. Was that year ago, that was a year ago. >> Dave: It was last year. >> Yeah, I leaned over >> What's happening? >> so it's happening. It's happening. You know what, the thing I noticed what's happening now is the maturity of the cloud, right? So, if you think about this whole journey to cloud that has been, what, AWS 12 years. But really over the last few years is when enterprises have really kind of joined that journey. And three or four years ago, and this is why I came out of retirement and went to Aviatrix, was they all said, okay, now we're going to do cloud. You fast forward now three, four years from now, all of a sudden those five-year plans of evacuating the data center, they got one year left, two year left, and they're going, oh crap, we don't have five years anymore. We're, now the maturity's starting to say, we're starting to put more apps into the cloud. We're starting to put business critical apps like SAP into the cloud. This is not just like the low-hanging fruit anymore. So what's happening now is the business criticality, the scale, the maturity. And they're all now starting to hit a lot of limits that have been put into the CSPs that you never used to hit when you didn't have business critical and you didn't have that scale. They were always there. The rocks were always there. Just it was, you never hit 'em. People are starting to hit 'em now. So what's happening now is people are realizing, and I'm going to jump the gun, you asked me for my bumper sticker. The bumper sticker for Aviatrix is, "Good enough is no longer good enough." Now it's funny, it came in a keynote today, but what we see from our customers is it's time to upgrade the native constructs of networking and network security to be enterprise-grade now. It's no longer good enough to just use the native constructs because of a lack of visibility, the lack of controls, the lack of troubleshooting capabilities, all these things. "I now need enterprise grade networking." >> Let me ask you a question 'cause you got a good historical perspective on the industry. When you think about when Maritz was running VMWare. He was like any app, he said basically we're building a software mainframe. And they kind of did that, right? But then they, you know, hit the issue with scale, right? And they can't replicate the cloud. Are there things that we can draw from that experience and apply that to the cloud? What's the same, what's different? >> Oh yeah. So, 1992, do you remember what happened in 1992? I do this, weird German software company called SAP >> Yeah, R3. announced a release as R/3. Which was their first three-tier client-server application of SAP. Before that it ran on mainframes, TCP/IP. Remember that Protocol War? Guess what happened post-1992, everybody goes up like this. Infrastructure completely changes. Cisco, EMC, you name it, builds out these PCE client-server architectures. The WAN changes, MPLS, the campus, everything's home running back to that data center running SAP. That was the last 30 years ago. Great transformation of SAP. They've did it again. It's called S/4Hana. And now it's running and people are switching to S/4Hana and they're moving to the cloud. It's just starting. And that is going to alter how you build infrastructure. And so when you have that, being able to troubleshoot in hours versus minutes is a big deal. This is business critical, millions of dollars. This is not fun and games. So again, back to my, what was good enough for the last three or four years for enterprises no longer good enough, now I'm running business critical apps like SAP, and it's going to completely change infrastructure. That's happening in the cloud right now. And that's obviously a significant seismic shift, but what are some of the barriers that customers have been able to eliminate in order to get there? Or is it just good enough isn't good enough anymore? >> Barriers in terms of, well, I mean >> Lisa: The adoption. Yeah well, I mean, I think it's all the things that they go to cloud is, you know, the complexity, really, it's the agility, right? So the barrier that they have to get over is how do I keep the developer happy because the developer went to the cloud in the first place, why? Swipe the credit card because IT wasn't doing their job, 'cause every time I asked them for something, they said no. So I went around 'em. We need that. That's what they have to overcome in the move to the cloud. That is the obstacle is how do I deliver that visibility, that control, the enterprise, great functionality, but yet give the developer what they want. Because the minute I stop giving them that swipe the card operational model, what do you think they're going to do? They're going to go around me again and I can't, and the enterprise can't have that. >> That's a cultural shift. >> That's the main barrier they've got to overcome. >> Let me ask you another question. Is what we think of as mission critical, the definition changing? I mean, you mentioned SAP, obviously that's mission critical for operations, but you're also seeing new applications being developed in the cloud. >> I would say anything that's, I call business critical, same thing, but it's, business critical is internal to me, like SAP, but also anything customer-facing. That's business critical to me. If that app goes down or it has a problem, I'm not collecting revenue. So, you know, back 30 years ago, we didn't have a lot of customer-facing apps, right? It really was just SAP. I mean there wasn't a heck of a lot of cust- There were customer-facing things. But you didn't have all the digitalization that we have now, like the digital economy, where that's where the real explosion has come, is you think about all the customer-facing applications. And now every enterprise is what? A technology, digital company with a customer-facing and you're trying to get closer and closer to who? The consumer. >> Yeah, self-service. >> Self-service, B2C, everybody wants to do that. Get out of the middle man. And those are business critical applications for people. >> So what's needed under the covers to make all this happen? Give us a little double click on where you guys fit. >> You need consistent architecture. Obviously not just for one cloud, but for any cloud. But even within one cloud, forget multicloud, it gets worst with multicloud. You need a consistent architecture, right? That is automated, that is as code. I can't have the human involved. These are all, this is the API generation, you've got to be able to use automation, Terraform. And all the way from the application development platform you know, through Jenkins and all other software, through CICD pipeline and Terraform, when you, when that developer says, I want infrastructure, it has to go build that infrastructure in real time. And then when it says, I don't need it anymore it's got to take it away. And you cannot have a human involved in that process. That's what's completely changed. And that's what's giving the agility. And that's kind of a cloud model, right? Use software. >> Well, okay, so isn't that what serverless does, right? >> That's part of it. Absolutely. >> But I might still want control sometimes over the runtime if I'm running those mission critical applications. Everything in enterprise is a heterogeneous thing. It's like people, people say, well there's going to, the people going to repatriate back to on-prem, they are not repatriating back to on-prem. >> We were just talking about that, I'm like- >> Steve: It's not going to happen, right? >> It's a myth, it's a myth. >> And there's things that maybe shouldn't have ever gone into the cloud, I get that. Look, do people still have mainframes? Of course. There's certain things that you just, doesn't make sense to move to the new generation. There were things, certain applications that are very static, they weren't dynamic. You know what, keeping it on-prem it's, probably makes sense. So some of those things maybe will go back, but they never should have gone. But we are not repatriating ever, you know, that's not going to happen. >> No I agree. I mean, you know, there was an interesting paper by Andreessen, >> Yeah. >> But, I mean- >> Steve: Yeah it was a little self-serving for some company that need more funding, yeah. You look at the numbers. >> Steve: Yeah. >> It tells the story. It's just not happening. >> No. And the reason is, it's that agility, right? And so that's what people, I would say that what you need to do is, and in order to get that agility, you have to have that consistency. You have to have automation, you have to get these people out of the way. You have to use software, right? So it's that you have that swipe the card operational model for the developers. They don't want to hear the word no. >> Lisa: Right. >> What do you think is going to happen with AWS? Because we heard, I don't know if you heard Selipsky's keynote this morning, but you've probably heard the hallway talk. >> Steve: I did, yeah. >> Okay. You did. So, you know, connecting the dots, you know doubling down on all the primitives, that we expected. We kind of expected more of the higher level stuff, which really didn't see much of that, a little bit. >> Steve: Yeah. So, you know, there's a whole thing about, okay, does the cloud get commoditized? Does it not? I think the secret weapon's the ecosystem, right? Because they're able to sell through with guys like you. Make great margins on that. >> Steve: Yeah, well, yeah. >> What are your thoughts though on the future of AWS? >> IAS is going to get commoditized. So this is the fallacy that a lot of the CSPs have, is they thought that they were going to commoditize enterprise. It never happens that way. What's going to happen is infrastructure as a service, the lower level, which is why you see all the CSPs talking about what? Oracle Cloud, industry cloud. >> Well, sure, absolutely, yeah. >> We got to get to the apps, we got to get to SAP, we got to get to all that, because that's not going to get commoditized, right. But all the infrastructural service where AWS is king that is going to get commoditized, absolutely. >> Okay, so, but historically, you know Cisco's still got 60% plus gross margins. EMC always had good margin. How pure is the lone survivor in Flash? They got 70% gross margins. So infrastructure actually has always been a pretty good business. >> Yeah that's true. But it's a hell of a lot easier, particularly with people like Aviatrix and others that are building these common architectural things that create simplicity and abstract the way the complexities of underneath such that we allow your network to run an AWS, Azure, Google, Oracle, whatever, exactly the same. So it makes it a hell of a lot easier >> Dave: Super cloud. >> to go move. >> But I want to tap your brain because you have a good perspective of this because servers used to be a great margin business too on-prem and now it's not. It's a low margin business 'cause all the margin went to Intel. >> Yeah. But the cloud guys, you know, AWS in particular, makes a ton of dough on servers, so, or compute. So it's going to be interesting to see over time if that gets com- that's why they're going so hard after silicon. >> I think if they can, I think if you can capture the workload. So AWS and everyone else, as another example, this SAP, they call that a gravity workload. You know what gravity workload is? It's a black hole. It drags everything else with it. If you get SAP or Oracle or a mainframe app, it ain't going anywhere. And then what's going to happen is all your other apps are going to follow it. So that's what they're all going to fight for, is type of app. >> You said something earlier about, forget multicloud, for a moment, but, that idea of the super cloud, this abstraction layer, I mean, is that a real business value for customers other than, oh I got all these clouds, I need 'em to work together. You know, from your perspective from Aviatrix perspective, is it an opportunity for you to build on top of that? Or are you just looking at, look, I'm going to do really good work in AWS, in Azure? Now we're making the same experience. >> I hear this every single day from our customers is they look and they say, good enough isn't good enough. I've now hit the point, I'm hitting route limitations. I'm hitting, I'm doing things manually, and that's fine when I don't have that many applications or I don't have mission critical. The dogs are eating the dog food, we're going into the cloud and they're looking and then saying this is not an operational model for me. I've hit the point where I can't keep doing this, I can't throw bodies at this, I need software. And that's the opportunity for us, is they look and they say, I'm doing it in one cloud, but, and there's zero chance I'm going to be able to figure that out in the two or three other clouds. Every enterprise I talk to says multicloud is inevitable. Whether they're in it now, they all know they're going to go, because it's the business units that demand it. It's not the IT teams that demand it, it's the line of business that says, I like GCP for this reason. >> The driver's functionality that they're getting. >> It's the app teams that say, I have this service and GCP's better at it than AWS. >> Yeah, so it's not so much a cost game or the end all coffee mug, right? >> No, no. >> Google does this better than Microsoft, or better than- >> If you asked an IT person, they would rather not have multicloud. They actually tried to fight it. No, why would you want to support four clouds when you could support one right? That's insane. >> Dave and Lisa: Right. If they didn't have a choice and, and so it, the decision was made without them, and actually they weren't even notified until day before. They said, oh, good news, we're going to GCP tomorrow. Well, why wasn't I notified? Well, we're notifying you now. >> Yeah, you would've said, no. >> Steve: This is cloud bottle, let's go. >> Super cloud again. Did you see the Berkeley paper, sky computing I think they call it? Down at Berkeley, yep Dave Linthicum from Deloitte. He's talking about, I think he calls it meta cloud. It's happening. >> Yeah, yeah, yeah. >> It's happening. >> No, and because customers, customers want that. They... >> And talk about some customer example or two that you think really articulates the value of why it's happening and the outcomes that it's generating. >> I mean, I was just talking to Lamb Weston last night. So we had a reception, Lamb Weston, huge, frozen potatoes. They serve like, I dunno, some ungodly percentage of all the french fries to all the fast food. It's unbelievable what they do. Do you know, they have special chemicals they put on the french fries. So when you get your DoorDash, they stay crispy longer. They've invented that patented it. But anyway, it's all these businesses you've never heard of and they do all the, and again, they're moving to SAP or they're actually SAP in the cloud, they're one of the first ones. They did it through Accenture. They're pulling it back off from Accenture. They're not happy with the service they're getting. They're going to use us for their networking and network security because they're going to get that visibility and control back. And they're going to repatriate it back from a managed service and bring it back and run it in-house. And the SAP basis engineers want it to happen because they see the visibility and control that the infrastructure guy's going to get because of us, which leads to, all they care about is uptime and performance. That's it. And they're going to say the infrastructure team's going to lead to better uptime and better performance if it's running on Aviatrix. >> And business performance and uptime, business critical >> That is the business. That is the business. >> It is. So what are some of the things next coming down the pike from Aviatrix? Any secret sauce you can share? >> Lot of secrets. So, two secrets. One, the next thing people really want to do, embedded network security into the network. We've kind of talked about this. You're going to be seeing some things from us. Where does network security belong? In the network. Embedded in the fabric of the network, not as this dumb device called the next-gen firewall that you steer traffic to. It has to be into the fabric of what we do, what we call airspace. You're going to see us talk about that. And then the next thing, back to the maturity of the cloud, as they build out the core, guess what they're doing? It's this thing called edge, Dave, right? And guess what they're going to do? It's not about connecting the cloud to the edge to the cloud with dumb things like SD-WAN, right? Or SaaS. It's actually the other way around. Go into the cloud, turn around, look out at the edge and say, how do I extend the cloud out to the edge, and make it look like a VPC. That's what people are doing. Why, 'cause I want the operational model. I want all the things that I can do in the cloud out at the edge. And everyone knows it's been in networking. I've been in networking for 37 years. He who wins the core does what? Wins the edge, 'cause that's what happens. You do it first in the core and then you want one architecture, one common architecture, one consistent way of doing everything. And that's going to go out to the edge and it's going to look like a VPC from an operational model. >> And Amazon's going to support that, no doubt. >> Yeah, I mean every, you know, every, and then it's just how do you want to go do that? And us as the networking and network security provider, we're getting dragged to the edge by our customer. Because you're my networking provider. And that means, end to end. And they're trying to drag us into on-prem too, yeah. >> Lot's going on, you're going to have to come back- >> Because they want one networking vendor. >> But wait, and you say what? >> We will never do like switches and any of the keep Arista, the Cisco, and all that kind of stuff. But we will start sucking in net flow. We will start doing, from an operational perspective, we will integrate a lot of the things that are happening in on-prem into our- >> No halfway house. >> Copilot. >> No halfway house, no two architectures. But you'll take the data in. >> You want one architecture. >> Yeah. >> Yeah, totally. >> Right play. >> Amazing stuff. >> And he who wins the core, guess what's more strategic to them? What's more strategic on-prem or cloud? Cloud. >> It flipped three years ago. >> Dave: Yeah. >> So he who wins in the clouds going to win everywhere. >> Got it, We'll keep our eyes on that. >> Steve: Cause and effect. >> Thank you so much for joining us. We've got your bumper sticker already. It's been a great pleasure having you on the program. You got to come back, there's so, we've- >> You posting the bumper sticker somewhere? >> Lisa: It's going to be our Instagram. >> Oh really, okay. >> And an Instagram sto- This is new for you guys. Always coming up with new ideas. >> Raising the bar. >> It is, it is. >> Me advance, I mean, come on. >> I love it. >> All right, for our guest Steve Mullaney and Dave Vellante, I'm Lisa Martin. You're watching theCUBE, the leader in live enterprise and emerging tech coverage.

>>Hello everyone. Welcome to the Cube's coverage of AWS Reinvent 22. I'm John Ferer, host of the Cube. Got some great coverage here talking about software supply chain and sustainability in the cloud. We've got a great conversation. Gunner Helickson, Vice President and general manager at Red Hat Enterprise Linux and Business Unit of Red Hat. Thanks for coming on. And Edon Eja Director, Product Management of commercial software services aws. Gentlemen, thanks for joining me today. >>Oh, it's a pleasure. >>You know, the hottest topic coming out of Cloudnative developer communities is slide chain software sustainability. This is a huge issue. As open source continues to power away and fund and grow this next generation modern development environment, you know, supply chain, you know, sustainability is a huge discussion because you gotta check things out where, what's in the code. Okay, open source is great, but now we gotta commercialize it. This is the topic, Gunner, let's get in, get with you. What, what are you seeing here and what's some of the things that you're seeing around the sustainability piece of it? Because, you know, containers, Kubernetes, we're seeing that that run time really dominate this new abstraction layer, cloud scale. What's your thoughts? >>Yeah, so I, it's interesting that the, you know, so Red Hat's been doing this for 20 years, right? Making open source safe to consume in the enterprise. And there was a time when in order to do that you needed to have a, a long term life cycle and you needed to be very good at remediating security vulnerabilities. And that was kind of, that was the bar that you had that you had to climb over. Nowadays with the number of vulnerabilities coming through, what people are most worried about is, is kind of the providence of the software and making sure that it has been vetted and it's been safe, and that that things that you get from your vendor should be more secure than things that you've just downloaded off of GitHub, for example. Right? And that's, that's a, that's a place where Red Hat's very comfortable living, right? >>Because we've been doing it for, for 20 years. I think there, there's another, there's another aspect to this, to this supply chain question as well, especially with the pandemic. You know, we've got these, these supply chains have been jammed up. The actual physical supply chains have been jammed up. And, and the two of these issues actually come together, right? Because as we've been go, as we go through the pandemic, we've had these digital transformation efforts, which are in large part people creating software in order to manage better their physical supply chain problems. And so as part of that digital transformation, you have another supply chain problem, which is the software supply chain problem, right? And so these two things kind of merge on these as people are trying to improve the performance of transportation systems, logistics, et cetera. Ultimately it all boils down to it all. Both supply chain problems actually boil down to a software problem. It's very >>Interesting that, Well, that is interesting. I wanna just follow up on that real quick if you don't mind. Because if you think about the convergence of the software and physical world, you know, that's, you know, IOT and also hybrid cloud kind of plays into that at scale, this opens up more surface area for attacks, especially when you're under a lot of pressure. This is where, you know, you can, you have a service area in the physical side and you have constraints there. And obviously the pandemic causes problems, but now you've got the software side. Can you, how are you guys handling that? Can you just share a little bit more of how you guys are looking at that with Red Hat? What's, what's the customer challenge? Obviously, you know, skills gaps is one, but like that's a convergence at the same time. More security problems. >>Yeah, yeah, that's right. And certainly the volume of, if we just look at security vulnerabilities themselves, just the volume of security vulnerabilities has gone up considerably as more people begin using the software. And as the software becomes more important to kind of critical infrastructure, more eyeballs are on it. And so we're uncovering more problems, which is kind of, that's, that's okay. That's how the world works. And so certainly the, the number of remediations required every year has gone up. But also the customer expectations, as I've mentioned before, the customer expectations have changed, right? People want to be able to show to their auditors and to their regulators that no, we, we, in fact, I can show the providence of the software that I'm using. I didn't just download something random off the internet. I actually have, like you, you know, adults paying attention to the, how the software gets put together. >>And it's still, honestly, it's still very early days. We can, I think the, in as an industry, I think we're very good at managing, identifying remediating vulnerabilities in the aggregate. We're pretty good at that. I think things are less clear when we talk about kind of the management of that supply chain, proving the provenance, proving the, and creating a resilient supply chain for software. We have lots of tools, but we don't really have lots of shared expectations. Yeah. And so it's gonna be interesting over the next few years, I think we're gonna have more rules are gonna come out. I see NIST has already, has already published some of them. And as these new rules come out, the whole industry is gonna have to kind of pull together and, and really and really rally around some of this shared understanding so we can all have shared expectations and we can all speak the same language when we're talking about this >>Problem. That's awesome. A and Amazon web service is obviously the largest cloud platform out there, you know, the pandemic, even post pandemic, some of these supply chain issues, whether it's physical or software, you're also an outlet for that. So if someone can't buy hardware or, or something physical, they can always get the cloud. You guys have great network compute and whatnot and you got thousands of ISVs across the globe. How are you helping customers with this supply chain problem? Because whether it's, you know, I need to get in my networking gears delayed, I'm gonna go to the cloud and get help there. Or whether it's knowing the workloads and, and what's going on inside them with respect open source. Cause you've got open source, which is kind of an external forcing function. You got AWS and you got, you know, physical compute stores, networking, et cetera. How are you guys helping customers with the supply chain challenge, which could be an opportunity? >>Yeah, thanks John. I think there, there are multiple layers to that. At, at the most basic level we are helping customers buy abstracting away all these data central constructs that they would have to worry about if they were running their own data centers. They would have to figure out how the networking gear, you talk about, you know, having the right compute, right physical hardware. So by moving to the cloud, at least they're delegating that problem to AWS and letting us manage and making sure that we have an instance available for them whenever they want it. And if they wanna scale it, the, the, the capacity is there for them to use now then that, so we kind of give them space to work on the second part of the problem, which is building their own supply chain solutions. And we work with all kinds of customers here at AWS from all different industry segments, automotive, retail, manufacturing. >>And you know, you see that the complexity of the supply chain with all those moving pieces, like hundreds and thousands of moving pieces, it's very daunting. So cus and then on the other hand, customers need more better services. So you need to move fast. So you need to build, build your agility in the supply chain itself. And that is where, you know, Red Hat and AWS come together where we can build, we can enable customers to build their supply chain solutions on platform like Red Hat Enterprise, Linux Rail or Red Hat OpenShift on, on aws. We call it Rosa. And the benefit there is that you can actually use the services that we, that are relevant for the supply chain solutions like Amazon managed blockchain, you know, SageMaker. So you can actually build predictive and s you can improve forecasting, you can make sure that you have solutions that help you identify where you can cut costs. And so those are some of the ways we are helping customers, you know, figure out how they actually wanna deal with the supply chain challenges that we're running into in today's world. >>Yeah, and you know, you mentioned sustainability outside of software su sustainability, you know, as people move to the cloud, we've reported on silicon angle here in the cube that it's better to have the sustainability with the cloud because then the data centers aren't using all that energy too. So there's also all kinds of sustainability advantages, Gunner, because this is, this is kind of how your relationship with Amazon's expanded. You mentioned Rosa, which is Red Hat on, you know, on OpenShift, on aws. This is interesting because one of the biggest discussions is skills gap, but we were also talking about the fact that the humans are huge part of the talent value. In other words, the, the humans still need to be involved and having that relationship with managed services and Red Hat, this piece becomes one of those things that's not talked about much, which is the talent is increasing in value the humans, and now you got managed services on the cloud, has got scale and human interactions. Can you share, you know, how you guys are working together on this piece? Cuz this is interesting cuz this kind of brings up the relationship of that operator or developer. >>Yeah, Yeah. So I think there's, so I think about this in a few dimensions. First is that the kind of the, I it's difficult to find a customer who is not talking about automation at some level right now. And obviously you can automate the processes and, and the physical infrastructure that you already have that's using tools like Ansible, right? But I think that the, combining it with the, the elasticity of a solution like aws, so you combine the automation with kind of elastic and, and converting a lot of the capital expenses into operating expenses, that's a great way actually to save labor, right? So instead of like racking hard drives, you can have somebody who's somebody do something a little more like, you know, more valuable work, right? And so, so okay, but that gives you a platform and then what do you do with that platform? >>And if you've got your systems automated and you've got this kind of elastic infrastructure underneath you, what you do on top of it is really interesting. So a great example of this is the collaboration that, that we had with running the rel workstation on aws. So you might think like, well why would anybody wanna run a workstation on, on a cloud? That doesn't make a whole lot of sense unless you consider how complex it is to set up, if you have the, the use case here is like industrial workstations, right? So it's animators, people doing computational fluid dynamics, things like this. So these are industries that are extremely data heavy. They have workstations have very large hardware requirements, often with accelerated GPUs and things like this. That is an extremely expensive thing to install on premise anywhere. And if the pandemic taught us anything, it's, if you have a bunch of very expensive talent and they all have to work from a home, it is very difficult to go provide them with, you know, several tens of thousands of dollars worth of worth of worth of workstation equipment. >>And so combine the rail workstation with the AWS infrastructure and now all that workstation computational infrastructure is available on demand and on and available right next to the considerable amount of data that they're analyzing or animating or, or, or working on. So it's a really interesting, it's, it was actually, this is an idea that I was actually born with the pandemic. Yeah. And, and it's kind of a combination of everything that we're talking about, right? It's the supply chain challenges of the customer, It's the lack of lack of talent, making sure that people are being put their best and highest use. And it's also having this kind of elastic, I think, opex heavy infrastructure as opposed to a CapEx heavy infrastructure. >>That's a great example. I think that's illustrates to me what I love about cloud right now is that you can put stuff in, in the cloud and then flex what you need when you need it at in the cloud rather than either ingress or egress data. You, you just more, you get more versatility around the workload needs, whether it's more compute or more storage or other high level services. This is kind of where this NextGen cloud is going. This is where, where, where customers want to go once their workloads are up and running. How do you simplify all this and how do you guys look at this from a joint customer perspective? Because that example I think will be something that all companies will be working on, which is put it in the cloud and flex to the, whatever the workload needs and put it closer to the work compute. I wanna put it there. If I wanna leverage more storage and networking, Well, I'll do that too. It's not one thing. It's gotta flex around what's, how are you guys simplifying this? >>Yeah, I think so for, I'll, I'll just give my point of view and then I'm, I'm very curious to hear what a not has to say about it, but the, I think and think about it in a few dimensions, right? So there's, there is a, technically like any solution that aan a nun's team and my team wanna put together needs to be kind of technically coherent, right? The things need to work well together, but that's not the, that's not even most of the job. Most of the job is actually the ensuring and operational consistency and operational simplicity so that everything is the day-to-day operations of these things kind of work well together. And then also all the way to things like support and even acquisition, right? Making sure that all the contracts work together, right? It's a really in what, So when Aon and I think about places of working together, it's very rare that we're just looking at a technical collaboration. It's actually a holistic collaboration across support acquisition as well as all the engineering that we have to do. >>And on your, your view on how you're simplifying it with Red Hat for your joint customers making Collabo >>Yeah. Gun, Yeah. Gunner covered it. Well I think the, the benefit here is that Red Hat has been the leading Linux distribution provider. So they have a lot of experience. AWS has been the leading cloud provider. So we have both our own point of views, our own learning from our respective set of customers. So the way we try to simplify and bring these things together is working closely. In fact, I sometimes joke internally that if you see Ghana and my team talking to each other on a call, you cannot really tell who who belongs to which team. Because we're always figuring out, okay, how do we simplify discount experience? How do we simplify programs? How do we simplify go to market? How do we simplify the product pieces? So it's really bringing our, our learning and share our perspective to the table and then really figure out how do we actually help customers make progress. Rosa that we talked about is a great example of that, you know, you know, we, together we figured out, hey, there is a need for customers to have this capability in AWS and we went out and built it. So those are just some of the examples in how both teams are working together to simplify the experience, make it complete, make it more coherent. >>Great. That's awesome. That next question is really around how you help organizations with the sustainability piece, how to support them, simplifying it. But first, before we get into that, what is the core problem around this sustainability discussion we're talking about here, supply chain sustainability, What is the core challenge? Can you both share your thoughts on what that problem is and what the solution looks like and then we can get into advice? >>Yeah. Well from my point of view, it's, I think, you know, one of the lessons of the last three years is every organization is kind of taking a careful look at how resilient it is. Or ever I should say, every organization learned exactly how resilient it was, right? And that comes from both the, the physical challenges and the logistics challenges that everyone had. The talent challenges you mentioned earlier. And of course the, the software challenges, you know, as everyone kind of embarks on this, this digital transformation journey that, that we've all been talking about. And I think, so I really frame it as, as resilience, right? And and resilience is at bottom is really about ensuring that you have options and that you have choices. The more choices you have, the more options you have, the more resilient you, you and your organization is going to be. And so I know that that's how, that's how I approach the market. I'm pretty sure that's exact, that's how AON is, has approaching the market, is ensuring that we are providing as many options as possible to customers so that they can assemble the right, assemble the right pieces to create a, a solution that works for their particular set of challenges or their unique set of challenges and and unique context. Aon, is that, does that sound about right to you? Yeah, >>I think you covered it well. I, I can speak to another aspect of sustainability, which is becoming increasingly top of mind for our customer is like how do they build products and services and solutions and whether it's supply chain or anything else which is sustainable, which is for the long term good of the, the planet. And I think that is where we have been also being very intentional and focused in how we design our data center. How we actually build our cooling system so that we, those are energy efficient. You know, we, we are on track to power all our operations with renewable energy by 2025, which is five years ahead of our initial commitment. And perhaps the most obvious example of all of this is our work with arm processors Graviton three, where, you know, we are building our own chip to make sure that we are designing energy efficiency into the process. And you know, we, there's the arm graviton, three arm processor chips, there are about 60% more energy efficient compared to some of the CD six comparable. So all those things that are also we are working on in making sure that whatever our customers build on our platform is long term sustainable. So that's another dimension of how we are working that into our >>Platform. That's awesome. This is a great conversation. You know, the supply chain is on both sides, physical and software. You're starting to see them come together in great conversations and certainly moving workloads to the cloud running in more efficiently will help on the sustainability side, in my opinion. Of course, you guys talked about that and we've covered it, but now you start getting into how to refactor, and this is a big conversation we've been having lately, is as you not just lift and ship but re-platform and refactor, customers are seeing great advantages on this. So I have to ask you guys, how are you helping customers and organizations support sustainability and, and simplify the complex environment that has a lot of potential integrations? Obviously API's help of course, but that's the kind of baseline, what's the, what's the advice that you give customers? Cause you know, it can look complex and it becomes complex, but there's an answer here. What's your thoughts? >>Yeah, I think so. Whenever, when, when I get questions like this from from customers, the, the first thing I guide them to is, we talked earlier about this notion of consistency and how important that is. It's one thing, it it, it is one way to solve the problem is to create an entirely new operational model, an entirely new acquisition model and an entirely new stack of technologies in order to be more sustainable. That is probably not in the cards for most folks. What they want to do is have their existing estate and they're trying to introduce sustainability into the work that they are already doing. They don't need to build another silo in order to create sustainability, right? And so there have to be, there has to be some common threads, there has to be some common platforms across the existing estate and your more sustainable estate, right? >>And, and so things like Red Hat enterprise Linux, which can provide this kind of common, not just a technical substrate, but a common operational substrate on which you can build these solutions if you have a common platform on which you are building solutions, whether it's RHEL or whether it's OpenShift or any of our other platforms that creates options for you underneath. So that in some cases maybe you need to run things on premise, some things you need to run in the cloud, but you don't have to profoundly change how you work when you're moving from one place to another. >>And that, what's your thoughts on, on the simplification? >>Yeah, I mean think that when you talk about replatforming and refactoring, it is a daunting undertaking, you know, in today's, in the, especially in today's fast paced work. So, but the good news is you don't have to do it by yourself. Customers don't have to do it on their own. You know, together AWS and Red Hat, we have our rich partner ecosystem, you know AWS over AWS has over a hundred thousand partners that can help you take that journey, the transformation journey. And within AWS and working with our partners like Red Hat, we make sure that we have all in, in my mind there are really three big pillars that you have to have to make sure that customers can successfully re-platform refactor their applications to the modern cloud architecture. You need to have the rich set of services and tools that meet their different scenarios, different use cases. Because no one size fits all. You have to have the right programs because sometimes customers need those incentives, they need those, you know, that help in the first step and last but no needs, they need training. So all of that, we try to cover that as we work with our customers, work with our partners and that is where, you know, together we try to help customers take that step, which is, which is a challenging step to take. >>Yeah. You know, it's great to talk to you guys, both leaders in your field. Obviously Red hats, well story history. I remember the days back when I was provisioning, loading OSS on hardware with, with CDs, if you remember, that was days gunner. But now with high level services, if you look at this year's reinvent, and this is like kind of my final question for the segment is then we'll get your reaction to is last year we talked about higher level services. I sat down with Adam Celski, we talked about that. If you look at what's happened this year, you're starting to see people talk about their environment as their cloud. So Amazon has the gift of the CapEx, the all that, all that investment and people can operate on top of it. They're calling that environment their cloud. Okay, For the first time we're seeing this new dynamic where it's like they have a cloud, but they're Amazon's the CapEx, they're operating. So you're starting to see the operational visibility gun around how to operate this environment. And it's not hybrid this, that it's just, it's cloud. This is kind of an inflection point. Do you guys agree with that or, or having a reaction to that statement? Because I, I think this is kind of the next gen super cloud-like capability. It's, it's, we're going, we're building the cloud. It's now an environment. It's not talking about private cloud, this cloud, it's, it's all cloud. What's your reaction? >>Yeah, I think, well I think it's a very natural, I mean we used words like hybrid cloud, multi-cloud, if, I guess super cloud is what the kids are saying now, right? It's, it's all, it's all describing the same phenomena, right? Which is, which is being able to take advantage of lots of different infrastructure options, but still having something that creates some commonality among them so that you can, so that you can manage them effectively, right? So that you can have kind of uniform compliance across your estate so that you can have kind of, you can make the best use of your talent across the estate. I mean this is a, this is, it's a very natural thing. >>They're calling it cloud, the estate is the cloud. >>Yeah. So yeah, so, so fine if it, if it means that we no longer have to argue about what's multi-cloud and what's hybrid cloud, I think that's great. Let's just call it cloud. >>And what's your reaction, cuz this is kind of the next gen benefits of, of higher level services combined with amazing, you know, compute and, and resource at the infrastructure level. What's your, what's your view on that? >>Yeah, I think the construct of a unified environment makes sense for customers who have all these use cases which require, like for instance, if you are doing some edge computing and you're running it WS outpost or you know, wave lent and these things. So, and, and it is, it is fear for customer to say, think that hey, this is one environment, same set of tooling that they wanna build that works across all their different environments. That is why we work with partners like Red Hat so that customers who are running Red Hat Enterprise Linux on premises and who are running in AWS get the same level of support, get the same level of security features, all of that. So from that sense, it actually makes sense for us to build these capabilities in a way that customers don't have to worry about, Okay, now I'm actually in the AWS data center versus I'm running outpost on premises. It is all one. They, they just use the same set of cli command line APIs and all of that. So in that sense, it's actually helps customers have that unification so that that consistency of experience helps their workforce and be more productive versus figuring out, okay, what do I do, which tool I use? Where >>And on you just nailed it. This is about supply chain sustainability, moving the workloads into a cloud environment. You mentioned wavelength, this conversation's gonna continue. We haven't even talked about the edge yet. This is something that's gonna be all about operating these workloads at scale and all the, with the cloud services. So thanks for sharing that and we'll pick up that edge piece later. But for reinvent right now, this is really the key conversation. How to bake the sustained supply chain work in a complex environment, making it simpler. And so thanks for sharing your insights here on the cube. >>Thanks. Thanks for having >>Us. Okay, this is the cube's coverage of ados Reinvent 22. I'm John Fur, your host. Thanks for watching.