(bright music) >> Hello everyone. Welcome to theCUBE's coverage of AWS re:Invent 22. I'm John Furrier, host of theCUBE. Got some great coverage here talking about software supply chain and sustainability in the cloud. We've got a great conversation. Gunnar Hellekson, vice president and general manager at Red Hat Enterprise Linux and Business Unit of Red Hat. Thanks for coming on. And Adnan Ijaz, director of product management of commercial software services, AWS. Gentlemen, thanks for joining me today. >> It's a pleasure. (Adnan speaks indistinctly) >> You know, the hottest topic coming out of Cloud Native 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 got to check things out, what's in the code. Okay, open source is great, but now we got to commercialize it. This is the topic, Gunnar, let's get in with you. 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 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 to climb over. Nowadays with the number of vulnerabilities coming through, what people are most worried about is, kind of, the providence of the software and making sure that it has been vetted and it's been safe, and 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 a place where Red Hat's very comfortable living, right? Because we've been doing it for 20 years. I think there's another aspect to this supply chain question as well, especially with the pandemic. You know, we've got these supply chains have been jammed up. The actual physical supply chains have been jammed up. And the two of these issues actually come together, right? Because as we go through the pandemic, we've got 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, both supply chain problems actually boil down to a software problem. It's very interesting. >> Well, that is interesting. I want to 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 hybridcloud 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 have a service area on the physical side and you have constraints there. And obviously the pandemic causes problems. But now you've got the software side. How are you guys handling that? Can you just share a little bit more of how you guys looking at that with Red Hat? 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 around it and so we're uncovering more problems, which is kind of, that's okay, that's how the world works. And so certainly the number of remediations required every year has gone up. But also the customer expectations, as I mentioned before, the customer expectations have changed, right? People want to be able to show to their auditors and to their regulators that no, 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 know, adults paying attention to how the software gets put together. And it's still, honestly, it's still very early days. I think 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 providence, and creating a resilient supply chain for software. We have lots of tools, but we don't really have lots of shared expectations. And so it's going to be interesting over the next few years, I think we're going to have more rules are going to come out. I see NIST has already published some of them. And as these new rules come out, the whole industry is going to have to kind of pull together 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. Adnan, 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 something physical, they can always get to 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 and delay, I'm going to go to the cloud and get help there. Or whether it's knowing the workloads and what's going on inside them with respect to open source. 'Cause you've got open source, which is kind of an external forcing function. You've 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 are multiple layers to that. At the most basic level, we are helping customers by abstracting away all these data center 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 want to scale it, the capacity is there for them to use. Now then, 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 the complexity of the supply chain with all those moving pieces, like hundreds and thousands of moving pieces, it's very daunting. And then on the other hand, customers need more better services. So you need to move fast. So you need to build your agility in the supply chain itself. And that is where, you know, Red Hat and AWS come together. Where we can enable customers to build their supply chain solutions on platforms like Red Hat Enterprise Linux RHEL or Red Hat OpenShift on AWS, we call it ROSA. And the benefit there is that you can actually use the services that are relevant for the supply chain solutions like Amazon managed blockchain, you know, SageMaker. So you can actually build predictive analytics, 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're helping customers, you know, figure out how they actually want to 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 sustainability, you know, as people move to the cloud, we've reported on SiliconANGLE here in theCUBE, 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. Gunnar, because this is kind of how your relationship with Amazon's expanded. You mentioned ROSA, which is Red Hat, 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 a huge part of the talent value. In other words, 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. So we'll look at scale and human interaction. Can you share, you know, how you guys are working together on this piece? 'Cause this is interesting, 'cause 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 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 the physical infrastructure that you already have, that's using tools like Ansible, right? But I think that combining it with the elasticity of a solution like AWS, so you combine the automation with kind of elastic 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 do something a little more like, you know, more valuable work, right? And so, okay, but that gives you a platform. And then what do you do with that platform? You know, 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 we had with running the RHEL workstation on AWS. So you might think, like, well why would anybody want to run a workstation 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 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. 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 home, it is very difficult to go provide them with, you know, several tens of thousands of dollars worth of workstation equipment. And so combine the RHEL workstation with the AWS infrastructure and now all that workstation computational infrastructure is available on demand and available right next to the considerable amount of data that they're analyzing or animating or working on. So it's a really interesting, it was actually, this is an idea that was actually born with the pandemic. >> Yeah. >> 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 talent, making sure that people are being put to 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 illustrates to me what I love about cloud right now is that you can put stuff in the cloud and then flex what you need, when you need it, in the cloud rather than either ingress or egress of data. You just 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 next gen cloud is going. This is 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 whatever the workload needs and put it closer to the compute. I want to put it there. If I want to leverage more storage and networking, well, I'll do that too. It's not one thing, it's got to flex around. How are you guys simplifying this? >> Yeah, I think, so, I'll give my point of view and then I'm very curious to hear what Adnan has to say about it. But I think about it in a few dimensions, right? So there is a technically, like, any solution that Adnan's team and my team want to put together needs to be kind of technically coherent, right? Things need to work well together. But that's not even most of the job. Most of the job is actually ensuring an 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... So when Adnan 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. >> Adnan, your view on how you're simplifying it with Red Hat for your joint customers making collaborations? >> Yeah, Gunnar covered it well. I think 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 points of view, 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 Gunnar and my team talking to each other on a call, you cannot really tell 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 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, 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. 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 I should say, every organization learned exactly how resilient it was, right? And that comes from both the physical challenges and the logistics challenges that everyone had, the talent challenges you mentioned earlier. And of course the software challenges, you know, as everyone kind of embarks on this digital transformation journey that we've all been talking about. And I think, so I really frame it as resilience, right? And resilience 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 and your organization is going to be. And so I know that's how I approach the market. I'm pretty sure that's how Adnan is approaching the market, is ensuring that we are providing as many options as possible to customers so that they can assemble the right pieces to create a solution that works for their particular set of challenges or their unique set of challenges and unique context. Adnan, does that sound about right to you? >> Yeah, I think you covered it well. I can speak to another aspect of sustainability, which is becoming increasingly top of mind for our customers. 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 planet. And I think that is where we have also been very intentional and focused in how we design our data center, how we actually build our cooling system so that those are energy efficient. You know, 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, Graviton3, where, you know, we are building our own chip to make sure that we are designing energy efficiency into the process. And you know, the ARM Graviton3 processor chips, they are about 60% more energy efficient compared to some of the CD6 comparable. So all those things that 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 and running them 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 shift, but replatform it 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 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 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 I get questions like this from customers, the first thing I guide them to is, we talked earlier about this notion of consistency and how important that 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 has to be some common threads, there has to be some common platforms across the existing estate and your more sustainable estate, right? 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-premises, 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. >> Adnan, what's your thoughts on the simplification? >> Yeah, I mean, when you talk about replatforming and refactoring, it is a daunting undertaking, you know, especially in today's fast paced world. 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 has over 100,000 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- 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 not least, 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 a challenging step to take. >> Yeah, you know, it's great to talk to you guys, both leaders in your field. Obviously Red Hats, I remember the days back when I was provisioning and loading OSs on hardware with CDs, if you remember those days, Gunnar. But now with the high level services, if you look at this year's reinvent, and this is kind of my final question for the segment is, that we'll get your reaction to, last year we talked about higher level service. I sat down with Adam Saleski, 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, 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 Amazon's the CapEx, they're operating. So, you're starting to see the operational visibility, Gunnar, 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 have a reaction to that statement? Because I think this is, kind of, the next gen supercloud-like capability. We're going, we're building the cloud. It's now an environment. It's not talking about private cloud, this cloud, it's all cloud. What's your reaction? >> Yeah, I think, well, I think it's very natural. I mean, we use words like hybridcloud, multicloud, I guess supercloud is what the kids are saying now, right? It's all describing the same phenomena, right? 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 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, it's a very natural thing. >> John: They're calling it cloud, the estate is the cloud. >> Yeah. So yeah, so fine, if it means that we no longer have to argue about what's multicloud and what's hybridcloud, I think that's great. Let's just call it cloud. >> Adnan, what's your reaction, 'cause this is kind of the next gen benefits of higher level services combined with amazing, you know, compute and resource at the infrastructure level. 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 WS outpost or you know, wavelength and these things. So, and it is fair for customer to think that, hey, this is one environment, same set of tooling that they want to 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 just use the same set of CLI, command line APIs and all of that. So in that sense it actually helps customers have that unification so that consistency of experience helps their workforce and be more productive versus figuring out, okay, what do I do, which tool I use where? >> Adnan, you just nailed it. This is about supply chain sustainability, moving the workloads into a cloud environment. You mentioned wavelength, this conversation's going to continue. We haven't even talked about the edge yet. This is something that's going to be all about operating these workloads at scale and all with the cloud services. So thanks for sharing that and we'll pick up that edge piece later. But for re:Invent right now, this is really the key conversation. How to make the sustained supply chain work in a complex environment, making it simpler. And so thanks you for sharing your insights here on theCUBE. >> Thanks, thanks for having us. >> Okay, this is theCUBE's coverage of AWS re:Invent 22. I'm John Furrier, your host. Thanks for watching. (bright music)

(corporate electronic xylophone jingle intro) >> Good afternoon everyone. Welcome back to theCUBE's live coverage of AWS re:Invent 22 from Vegas. We're at the Venetian Expo Hall with 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 Furrier, 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 another, I think, partner friendly cloud. This next gen wave that's coming, it's really next segment I think speaks to, 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's an alumni, Reza Honarmand SVP Global Cloud at TD SYNNEX. Great to have you back. >> Hello. >> 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. It's a great experience. >> Amazing. The energy here has been hot at the highest levels since we came here Monday, 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 your 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 TD Synnex as a new merger between Tech Data and Synnex Corporation. Now, we are the largest distributor basically, across the world, with more than 62 billion dollar in a business. And, Amazon is obviously a strategic partner with a hyper growth and, we has been very focused to working with them to expand that partner ecosystem across solution ISVs and service providers. There has been very nice experience combine these two company and now have the reach and a scale that enable more than 140,000 partners across the world. >> Wow. >> And, the partner's message here is changing too. The new leader, Aruba 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 is going to be stronger too and, more money making of course. But, the new Amazon's posture with partners. What's your reaction? >> We were at Aruba just an hour ago. Fantastic. 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, I can only see that accelerating now in terms of what Amazon is doing and actually with the channel and what Aruba is doing. I think this is exactly the right direction. >> John: 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 and the challenging economic times that we've had. What are some of 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 an industrial company etcetera and, those frontiers are blending right now. Then, as a consequence we has been investing in several elements. One 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 competency in the government sector where we expand drastically our capabilities around specifically the federal and non federal business. But, not only in US but, across the world with those elements. Then, I would say that 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 the Iotly 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, ISV 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 certification. Is how you transform either a partner that is born in the cloud or a partner that is still in the on-premise 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 distribute, it's great distribution. It's 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 their partners and the customers that Sergio was referring to. >> Let me ask you guys a question. Where's the growth going to come from? You mentioned ecosystem, more growth, Aruba mentioned that's where the growth is. They are serious. So, you 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. >> John: The wave is still coming. Yeah, the wave is still there. When you see still the amount of platform that need to be migrated to the cloud then, we have been investing in a significant way in enable capabilities of migration programs from the on-premise to the 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. There's 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 playing together to bring those solutions to market. >> So if I build on that. If we look at the growth in the public cloud last year, was around 40 billion dollars. 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 skill sets. What we are seeing is the partners with the skill sets who can participate in that 40 billion dollar 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 hyperscalers. Then somebody need to put all those pieces together. That is our role in the market. >> John: 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 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've 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 strength in the relationship what those awards are coming from. >> Yeah, the other critical factor here is again, how we bring more capability in terms of the serve to the market to Amazon. And, that has been another component of data where 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 partner serve to the market. >> Reza, Sergio. I want to 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 is 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? Could you just take a minute to 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, and again, for more than 40 years we has been building this ecosystem. We has 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 get in opposition to our customers and, we enable those customers in a consistent way. Then, I think that trust is something that you earn not something that you ask for. And, that is what we are doing day basis. >> Well, congratulations. It's been great chatting with you. Challenge time for the challenge >> Lisa: Challenge Time, all right guys. >> A new challenge on theCUBE, new format. We usually say... >> Yes at the end of the interview. What's the 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 Iotly economy. We are here in 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... >> 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 the set >> Thank you. >> Thank you for the time. >> All right, our pleasure. For our guests and for John Furrier, I'm Lisa Martin. You're watching theCUBE, the leader at live tech coverage. (corporate electronic xylophone jingle outro)

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

(bright upbeat music) >> Hello, wonderful Cloud community and welcome back to our wall-to-wall coverage of AWS re:Invent here in Las Vegas, Nevada. I'm Savannah Peterson, joined by the brilliant John Furrier. John, how you doing this afternoon? >> Doing great, feeling good. We've got day three here, another day tomorrow. Wall-to-wall coverage we're already over a hundred something videos, live getting up. >> You're holding up well. >> And then Cloud show is just popping. It's back to pre-pandemic levels. The audience is here, what recession? But there is one coming but apparently doesn't seem to be an unnoticed with the Cloud community. >> I think, we'll be talking a little bit about that in our next interview in the state of the union. Not just our union, but the the general global economy and the climate there with some fabulous guests from Software One. Please welcome Neil and Bernd, welcome to the show, guys. How you doing? >> Great, thank you. >> Really good. >> Yeah, like you said, just getting over the jet lag. >> Yeah, yeah. Pretty good today, yeah, (laughing loudly) glad we did it today. >> I love that Neil, set your smiling and I can feel your energy. Tell us a little bit about Software One and what you all do. >> Yeah, so Software One we're a software and Cloud solutions provider. We're in 90 countries. We have 65,000 customers. >> Savannah: Just a few. >> Yeah, and we really focus on being close to the customers and helping customers through their software and Cloud journey. So we transact, we sell software in Cloud, 10,000 different ISVs. And then on top of that we a lot of services around the spend optimization FinOps we'll talk about as well, and lots of other areas. But yeah, we're really a large scale partner in this space. >> That's awesome. FinOps, cost optimization, pretty much all we've been talking about here on the give. It's very much a hot topic. I'm actually excited about this and Bernd I'm going to throw this one to you first. We haven't actually done a proper definition of what FinOps is at the show yet. What is FinOps? >> Well, largely speaking it's Cloud cost optimization but for us it's a lot more than for others. That's our superpower. We do it all. We do the technology side but we also do the licensing side. So, we have a differentiated offering. If you would look at the six Rs of application migration we do it all, not even an Accenture as it all. And that is our differentiation. >> You know, yesterday Adams left was on the Keynote. He's like waving his hands around. It's like, "Hey, we got if you want to tighten your belt, come to the Cloud." I'm like, wait a minute. In 2008 when the last recession, Amazon wasn't a factor. They were small. Now they're massive, they're huge. They're a big part of the economic equation. What does belt tightening mean? Like what does that mean? Like do customers just go to the marketplace? Do they go, do you guys, so a lot of moving parts now on how they're buying software and they're fine tuning their Cloud too. It's not just eliminate budget, it's fine tune the machine if you will... >> 'make a smarter Cloud. >> Explain this phenomenon, how people are tackling this cost optimization, Cloud optimization. 'Cause they're not going to stop building. >> No. >> This is right sizing and tuning and cutting. >> Yeah, we see, of course with so many customers in so many countries, we have a lot of different views on maturity and we see customers taking the FinOps journey at different paces. But fundamentally what we see is that it's more of an afterthought and coming in at a panic stage rather than building it and engaging with it from the beginning and doing it continuously. And really that's the huge opportunity and AWS is a big believer in this of continued optimization of the Cloud is a confident Cloud. A confident Cloud means you'll do more with it. If you lose confidence in that bill in what how much it's costing you, you're going to retract. And so it's really about making sure all customers know exactly what's in there, how it's optimized, restocking, reformatting applications, getting more out of the microservices and getting more value out the Cloud and that will help them tighten that belt. >> So the euphoric enthusiasm of previous years of building water just fallen the pipes leaving the lights on when you go to bed. I mean that's kind of the mentality. People were not literally I won't say they weren't not paying attention but there was some just keep going we're all good now it's like whoa, whoa. We turn that service off and no one's using it or do automation. So there's a lot more of that mindset emerging. We're hearing that for the first time price performance being mindful of what's on and off common sense basically. >> Yeah, but it's not just that the lights are on and the faucets are open it's also the air condition is running. So the FinOps foundation is estimating that about a third of Cloud spend is waste and that's where FinOps comes in. We can help customers be more efficient in the Cloud and lower their Cloud spend while doing the same or more. >> So, let's dig in a little bit there. How do you apply FinOps when migrating to the Cloud? >> Well, you start with the business case and you're not just looking at infrastructure costs like most people do you ought look at software licensing costs. For example, if you run SQL on-premise you have an enterprise agreement. But if you move it to the Cloud you may actually take a different more favorable licensing agreement and save a lot of money. And these things are hidden. They're not to be seen but they need to be part of the business case. >> When you look at the modernization trend we had an analyst on our session with David Vellante and Zs (indistinct) from ZK Consulting. He had an interesting comment. He said, "Spend more in Cloud to save more." Which is a mindset that doesn't come across right. Wait a minute, spend more, save more. You can do bet right now with the Clouds kind of the the thesis of FinOps, you don't have to cut. Just kind of cut the waste out but still spend and build if you're smart, there's a lot more of that going on. What does that mean? >> I mean, yeah I've got a good example of this is, we're the largest Microsoft provider in the world. And when of course when you move Microsoft workloads to the Cloud, you don't... Maybe you don't want a server, you can go serverless, right? So you may not win a server. Bernd said SQL, right? So, it's not just about putting applications in the Cloud and workloads in the Cloud. It's about modernizing them and then really taking advantage of what you can really do in the Cloud. And I think that's where the customers are still pretty immature. They're still on that journey of throwing stuff in there and then realizing actually they can take way more advantage of what services are in there to reduce the amount and get even more in there. >> Yeah, and so the... You want to say, something? >> How much, just building on the stereotypical image of Cloud customer is the marketing person with a credit card, right? And there are many of them and they all buy their own Cloud and companies have a hard time consolidating the spend pulling it together, even within a country. But across countries across the globe, it's really, really hard. If you pull it all together, you get a better discount. You spend more to save more. >> Yeah, and also there's a human piece. We had an intern two summers ago playing with our Cloud. We're on a Cloud with our media plus stack left a service was playing around doing some tinkering and like, where's this bill? What is this extra $20,000 came from. It just, we left a service on... >> It's a really good point actually. It's something that we see almost every day right now which is customers also not understanding what they've put in the Cloud and what the implications of spikes are. And also therefore having really robust monitoring and processes and having a partner that can look after that for them. Otherwise we've got customers where they've been really shocked about not doing things the right way because they've empowered the business but also not with the maturity that the business needs to have that responsibility. >> And that's a great point. New people coming in and or people being platooned through new jobs are getting used to the Cloud. That's a great point. I got that brings up my security question 'cause this comes up a lot. So that's what's a lot of spend of people dialing up more security. Obviously people try everything with security, every tool, every platform, and throw everything at the problem. How does that impact the FinOps equation? 'Cause Dev SecOps is now part of everything. Okay, moving security at the CICD pipeline, that's cool. Check Cloud native applications, microservices event-based services check. But now you've got more security. How does that factor into the cost side? What you guys look at that can you share your thoughts on how your customers are managing their security posture without getting kind of over the barrel, if you will? >> Since we are at AWS re:Invent, right? We can talk about the well architected framework of AWS and there's six components to it. And there's reliability, there's security cost, performance quality, operational quality and sustainability. And so when we think about migrating apps to the Cloud or modernizing them in the Cloud security is always a table stakes. >> And it has to be, yeah, go ahead. >> I really like what AWS is doing with us on that. We partner very closely on that area. And to give you a parallel example of Microsoft I don't feel very good about that at the moment. We see a lot of customers right now that get hacked and normally it's... >> 'yeah that's such a topic. >> You mean on Azure? >> Yeah, and what happens is that they normally it's a crypto mining script that the customer comes in they come in as the customer get hacked and then they... We saw an incident the other day where we had 2,100 security incidents in a minute where it all like exploded on the customer side. And so that's also really important is that the customer's understanding that security element also who they're letting in and out of their organization and also the responsibility they have if things go bad. And that's also not aware, like when they get hacked, are they responsible for that? Are they not responsible? Is the provider... >> 'shared responsibility? >> Yeah. >> 'well that security data lake the open cybersecurity schema framework. That's going to be very interesting to see how that plays out to your point. >> Absolutely, absolutely. >> Yeah, it is fascinating and it does require a lot of collaboration. What other trends, what other big challenges are you seeing? You're obviously working with customers at incredible scale. What are some of the other problems you're helping them tackle? >> I think we work with customers from SMB all the way up to enterprise and public sector. But what we see is more in the enterprise space. So we see a lot of customers willing to commit a lot to the Cloud based on all the themes that we've set but not commit financially for all the PNLs that they run in all the business units of all the different companies that they may own in different countries. So it's like, how can I commit but not be responsible on the hook for the bill that comes in. And we see this all the time right now and we are working closely with AWS on this. And we see the ability for customers to commit centrally but decentralized billing, decentralized optimization and decentralized FinOps. So that's that educational layer within the business units who owns the PNL where they get that fitness and they own what they're spending but the company is alone can commit to AWS. And I think that's a big trend that we are seeing is centralized commitment but decentralized ownership in that model. >> And that's where the marketplaces kind of fit in as well. >> Absolutely. >> Yeah, yeah. Do you want to add some more on that? >> I mean the marketplace, if you're going to cut your bill you go to the marketplace right there you want single dashboard or your marketplace what's the customer going to do when they're going to tighten their belts? What do they do? What's their workflow, marketplace? What's the process? >> Well, on marketplaces, the larger companies will have a private marketplace with dedicated pricing managed service they can call off. But that's for the software of the shelf. They still have the data centers they still have all the legacy and they need to do the which ones are we going to keep which ones are we going to retire, we repurchase, we license, rehouse, relocate, all of those things. >> That's your wheelhouse. >> It's a three, yes is our wheelhouse. It's a three to five year process for most companies. >> This could be a tailwind for you guys. This is like a good time. >> I mean FinOps is super cool and super hot right now. >> Not that you're biased? (all laughing loudly) >> But look, it's great to see it because well we are the magic quadrant leader in software asset management, which is a pedigree of ours. But we always had to convince customers to do that because they're always worried, oh what you're going to find do I have an audit? Do I have to give Oracles some more money or SAP some more money? So there's always like, you know... >> 'don't, (indistinct). >> How compliant do I really want? >> Is anyone paying attention to this? >> Well FinOps it's all upside. Like it's all upside. And so it's completely flipped. And now we speak to most customers that are building FinOps internally and then they're like, hold on a minute I'm a bank. Why do I have hundred people doing FinOps? And so that's the trend that we've seen because they just get more and more value out of it all the time. >> Well also the key mindset is that the consumption based model of Cloud you mentioned Oracle 'cause they're stuck in that whoa, whoa, whoa, how many servers license and they're stuck in that extortion. And now they got Cloud once you're on a variable, what's the downside? >> Exactly and then you can look at all the applications, see where you can go serverless see where you can go native services all that sort of stuff is all upside. >> And for the major workloads like SAP and Oracle and Microsoft defined that customers save in the millions. >> Well just on that point, those VMware, SAP, these workloads they're being rolled and encapsulated into containers and Kubernetes run times moved into the Cloud, they're being refactored. So that's a whole nother ballgame. >> Yes. Lift and shift usually doesn't save you any money. So that's relocation with containers may save you money but in some cases you have to... >> 'it's more in the Cloud now than ever before. >> Yeah >> Yeah, yeah. >> Before we take him to the challenge portion we have a little quiz for you, or not a quiz, but a little prop for you in a second. I want to talk about your role. You have a very important role at the FinOps Foundation and why don't you tell me more about that? You, why don't you go. >> All right, so yeah I mean we are a founding member of the Finops organization. You can tell I'm super passionate about it as well. >> I wanted to keep that club like a poster boy for FinOps right now. It's great, I love the energy. >> You have some VA down that is going to go up on the table and dance, (all laughing loudly) >> We're ready for it. We're waiting for that performance here on theCUBE this week. I promise I would keep everyone up an alert... >> 'and it's on the post. And our value to the foundation is first of all the feedback we get from all our customers, right? We can bring that back as an organization to that also as one of the founding members. We're one of the only ones that really deliver services and platforms. So we'll work with Cloud health, Cloud ability our own platform as well, and we'll do that. And we have over 200 practitioners completely dedicated to FinOps as well. So, it's a great foundation, they're doing an amazing job and we're super proud to be part of that. >> Yeah, I love that you're contributing to the community as well as supporting it, looking after your customers. All right, so our new tradition here on theCUBE at re:Invent 'cause we're looking for your 32nd Instagram reel hot take sizzle of thought leadership on the number one takeaway most important theme of the show this year Bernd do you want to go first? >> Of the re:Invent show or whatever? >> You can interpret that however you want. We've gotten some unique interpretations throughout the week, so we're probing. >> Everybody's looking for the superpower to do more with less in the Cloud. That will be the theme of 2023. >> Perfect, I love that. 10 seconds, your mic very efficient. You're clearly providing an efficient solution based on that answer. >> I won't that much. That's... (laughing loudly) >> It's the quiz. And what about you Neil? Give us your, (indistinct) >> I'm going to steal your comment. It's exactly what I was thinking earlier. Tech is super resilient and tech is there for customers when they want to invest and modernize and do fun stuff and they're also there for when they want to save money. So we are always like a constant and you see that here. It's like this is... It's always happening here, always happening. >> It is always happening. It really can feel the energy. I hope that the show is just as energetic and fun for you guys. As the last few minutes here on theCUBE has been thank you both for joining us. >> Thanks. >> Thank you very much. >> And thank you all so much for tuning in. I hope you enjoyed this conversation about FinOps, Cloud confidence and all things AWS re:Invent. We're here in Las Vegas, Nevada with John Furrier, my name is Savannah Peterson. You're watching theCUBE, the leader in high tech coverage. (bright upbeat music)

(upbeat music) >> Welcome back everyone to The Cubes coverage here in Seattle, Washington. For AWS's Marketplace Seller Conference. It's the big news within the Amazon partner network, combining with marketplace, forming the Amazon partner organization. Part of a big reorg as they grow to the next level, NextGen cloud, mid-game on the chessboard. Cube's got it covered. I'm John Furry, your host at Cube. Great guests here from Data bricks. Both cube alumni's. Jack Anderson, GM and VP of the Databricks partnership team for AWS. You handle that relationship and Joel Minick vice president of product and partner marketing. You guys have the keys to the kingdom with Databricks and AWS. Thanks for joining. Good to see you again. >> Thanks for having us back. >> Yeah, John, great to be here. >> So I feel like we're at Reinvent 2013. Small event, no stage, but there's a real shift happening with procurement. Obviously it's a no brainer on the micro, you know, people should be buying online. Self-service, Cloud Scale. But Amazon's got billions being sold through their marketplace. They've reorganized their partner network. You can see kind of what's going on. They've kind of figured it out. Like let's put everything together and simplify and make it less of a website, marketplace. Merge our partner organizations, have more synergy and frictionless experiences so everyone can make more money and customer's are going to be happier. >> Yeah, that's right. >> I mean, you're running relationship. You're in the middle of it. >> Well, Amazon's mental model here is that they want the world's best ISVs to operate on AWS so that we can collaborate and co architect on behalf of customers. And that's exactly what the APO and marketplace allow us to do, is to work with Amazon on these really, you know, unique use cases. >> You know, I interviewed Ali many times over the years. I remember many years ago, maybe six, seven years ago, we were talking. He's like, "we're all in on AWS." Obviously now the success of Databricks, you've got multiple clouds, see that. Customers have choice. But I remember the strategy early on. It was like, we're going to be deep. So this is, speaks volumes to the relationship you have. Years. Jack, take us through the relationship that Databricks has with AWS from a partner perspective. Joel, and from a product perspective. Because it's not like you guys are Johnny come lately, new to the scene. >> Right. >> You've been there, almost president creation of this wave. What's the relationship and how does it relate to what's going on today? >> So most people may not know that Databricks was born on AWS. We actually did our first $100 million of revenue on Amazon. And today we're obviously available on multiple clouds. But we're very fond of our Amazon relationship. And when you look at what the APN allows us to do, you know, we're able to expand our reach and co-sell with Amazon, and marketplace broadens our reach. And so, we think of marketplace in three different aspects. We've got the marketplace private offer business, which we've been doing for a number of years. Matter of fact, we were driving well over a hundred percent year over year growth in private offers. And we have a nine figure business. So it's a very significant business. And when a customer uses a private offer, that private offer counts against their private pricing agreement with AWS. So they get pricing power against their private pricing. So it's really important it goes on their Amazon bill. In may we launched our pay as you go, on demand offering. And in five short months, we have well over a thousand subscribers. And what this does, is it really reduces the barriers to entry. It's low friction. So anybody in an enterprise or startup or public sector company can start to use Databricks on AWS, in a consumption based model, and have it go against their monthly bill. And so we see customers, you know, doing rapid experimentation, pilots, POCs. They're really learning the value of that first, use case. And then we see rapid use case expansion. And the third aspect is the consulting partner, private offer, CPPO. Super important in how we involve our partner ecosystem of our consulting partners and our resellers that are able to work with Databricks on behalf of customers. >> So you got the big contracts with the private offer. You got the product market fit, kind of people iterating with data, coming in with the buyers you get. And obviously the integration piece all fitting in there. >> Exactly. >> Okay, so those are the offers, that's current, what's in marketplace today. Is that the products... What are people buying? >> Yeah. >> I mean, I guess what's the... Joel, what are people buying in the marketplace? And what does it mean for them? >> So fundamentally what they're buying is the ability to take silos out of their organization. And that is the problem that Databricks is out there to solve. Which is, when you look across your data landscape today, you've got unstructured data, you've got structured data, you've got real time streaming data. And your teams are trying to use all of this data to solve really complicated problems. And as Databricks, as the Lakehouse Company, what we're helping customers do is, how do they get into the new world? How do they move to a place where they can use all of that data across all of their teams? And so we allow them to begin to find, through the marketplace, those rapid adoption use cases where they can get rid of these data warehousing, data lake silos they've had in the past. Get their unstructured and structured data onto one data platform, an open data platform, that is no longer adherent to any proprietary formats and standards and something they can, very much, very easily, integrate into the rest of their data environment. Apply one common data governance layer on top of that. So that from the time they ingest that data, to the time they use that data, to the time they share that data, inside and outside of their organization, they know exactly how it's flowing. They know where it came from. They know who's using it. They know who has access to it. They know how it's changing. And then with that common data platform, with that common governance solution, they'd being able to bring all of those use cases together. Across their real time streaming, their data engineering, their BI, their AI. All of their teams working on one set of data. And that lets them move really, really fast. And it also lets them solve challenges they just couldn't solve before. A good example of this, you know, one of the world's now largest data streaming platforms runs on Databricks with AWS. And if you think about what does it take to set that up? Well, they've got all this customer data that was historically inside of data warehouses. That they have to understand who their customers are. They have all this unstructured data, they've built their data science model, so they can do the right kinds of recommendation engines and forecasting around. And then they've got all this streaming data going back and forth between click stream data, from what the customers are doing with their platform and the recommendations they want to push back out. And if those teams were all working in individual silos, building these kinds of platforms would be extraordinarily slow and complex. But by building it on Databricks, they were able to release it in record time and have grown at a record pace to now be the number one platform. >> And this product, it's impacting product development. >> Absolutely. >> I mean, this is like the difference between lagging months of product development, to like days. >> Yes. >> Pretty much what you're getting at. >> Yes. >> So total agility. >> Mm-hmm. >> I got that. Okay, now, I'm a customer I want to buy in the marketplace, but you got direct Salesforce up there. So how do you guys look at this? Is there channel conflict? Are there comp programs? Because one of the things I heard today in on the stage from AWS's leadership, Chris, was up there speaking, and Mona was, "Hey, he's a CRO conference chief revenue officer" conversation. Which means someone's getting compensated. So, if I'm the sales rep at Databricks, what's my motion to the customer? Do I get paid? Does Amazon sell it? Take us through that. Is there channel conflict? Or, how do you handle it? >> Well, I'd add what Joel just talked about with, you know, with the solution, the value of the solution our entire offering is available on AWS marketplace. So it's not a subset, it's the entire Data Bricks offering. And- >> The flagship, all the, the top stuff. >> Everything, the flagship, the complete offering. So it's not segmented. It's not a sub segment. >> Okay. >> It's, you know, you can use all of our different offerings. Now when it comes to seller compensation, we view this two different ways, right? One is that AWS is also incented, right? Versus selling a native service to recommend Databricks for the right situation. Same thing with Databricks, our sales force wants to do the right thing for the customer. If the customer wants to use marketplace as their procurement vehicle. And that really helps customers because if you get Databricks and five other ISVs together, and let's say each ISV is spending, you're spending a million dollars. You have $5 million of spend. You put that spend through the flywheel with AWS marketplace, and then you can use that in your negotiations with AWS to get better pricing overall. So that's how we view it. >> So customers are driving. This sounds like. >> Correct. For sure. >> So they're looking at this as saying, Hey, I'm going to just get purchasing power with all my relationships. Because it's a solution architectural market, right? >> Yeah. It makes sense. Because if most customers will have a primary and secondary cloud provider. If they can consolidate, you know, multiple ISV spend through that same primary provider, you get pricing power. >> Okay, Joel, we're going to date ourselves. At least I will. So back in the old days, (group laughter) It used to be, do a Barney deal with someone, Hey, let's go to market together. You got to get paper, you do a biz dev deal. And then you got to say, okay, now let's coordinate our sales teams, a lot of moving parts. So what you're getting at here is that the alternative for Databricks, or any company is, to go find those partners and do deals, versus now Amazon is the center point for the customer. So you can still do those joint deals, but this seems to be flipping the script a little bit. >> Well, it is, but we still have vars and consulting partners that are doing implementation work. Very valuable work, advisory work, that can actually work with marketplace through the CPPO offering. So the marketplace allows multiple ways to procure your solution. >> So it doesn't change your business structure. It just makes it more efficient. >> That's correct. >> That's a great way to say it. >> Yeah, that's great. >> Okay. So, that's it. So that's just makes it more efficient. So you guys are actually incented to point customers to the marketplace. >> Yes. >> Absolutely. >> Economically. >> Economically, it's the right thing to do for the customer. It's the right thing to do for our relationship with Amazon. Especially when it comes back to co-selling, right? Because Amazon now is leaning in with ISVs and making recommendations for, you know, an ISV solution. And our teams are working backwards from those use cases, you know, to collaborate and land them. >> Yeah. I want to get that out there. Go ahead, Joel. >> So one of the other things I might add to that too, you know, and why this is advantageous for companies like Databricks to work through the marketplace. Is it makes it so much easier for customers to deploy a solution. It's very, literally, one click through the marketplace to get Databricks stood up inside of your environment. And so if you're looking at how do I help customers most rapidly adopt these solutions in the AWS cloud, the marketplace is a fantastic accelerator to that. >> You know, it's interesting. I want to bring this up and get your reaction to it because to me, I think this is the future of procurement. So from a procurement standpoint, I mean, again, dating myself, EDI back in the old days, you know, all that craziness. Now this is all the internet, basically through the console. I get the infrastructure side, you know, spin up and provision some servers, all been good. You guys have played well there in the marketplace. But now as we get into more of what I call the business apps, and they brought this up on stage. A little nuanced. Most enterprises aren't yet there of integrating tech, on the business apps, into the stack. This is where I think you guys are a use case of success where you guys have been successful with data integration. It's an integrators dilemma, not an innovator's dilemma. So like, I want to integrate. So now I have integration points with Databricks, but I want to put an app in there. I want to provision an application, but it has to be built. It's not, you don't buy it. You build, you got to build stuff. And this is the nuance. What's your reaction to that? Am I getting this right? Or am I off because, no one's going to be buying software like they used to. They buy software to integrate it. >> Yeah, no- >> Because everything's integrated. >> I think AWS has done a great job at creating a partner ecosystem, right? To give customers the right tools for the right jobs. And those might be with third parties. Databricks is doing the same thing with our partner connect program, right? We've got customer partners like Five Tran and DBT that, you know, augment and enhance our platform. And so you're looking at multi ISV architectures and all of that can be procured through the AWS marketplace. >> Yeah. It's almost like, you know, bundling and un bundling. I was talking about this with, with Dave Alante about Supercloud. Which is why wouldn't a customer want the best solution in their architecture? Period. In its class. If someone's got API security or an API gateway. Well, you know, I don't want to be forced to buy something because it's part of a suite. And that's where you see things get sub optimized. Where someone dominates a category and they have, oh, you got to buy my version of this. >> Joel and I were talking, we were actually saying, what's really important about Databricks, is that customers control the data, right? You want to comment on that? >> Yeah. I was going to say, you know, what you're pushing on there, we think is extraordinarily, you know, the way the market is going to go. Is that customers want a lot of control over how they build their data stack. And everyone's unique in what tools are the right ones for them. And so one of the, you know, philosophically, I think, really strong places, Databricks and AWS have lined up, is we both take an approach that you should be able to have maximum flexibility on the platform. And as we think about the Lakehouse, one thing we've always been extremely committed to, as a company, is building the data platform on an open foundation. And we do that primarily through Delta Lake and making sure that, to Jack's point, with Databricks, the data is always in your control. And then it's always stored in a completely open format. And that is one of the things that's allowed Databricks to have the breadth of integrations that it has with all the other data tools out there. Because you're not tied into any proprietary format, but instead are able to take advantage of all the innovation that's happening out there in the open source ecosystem. >> When you see other solutions out there that aren't as open as you guys, you guys are very open by the way, we love that too. We think that's a great strategy, but what am I foreclosing if I go with something else that's not as open? What's the customer's downside as you think about what's around the corner in the industry? Because if you believe it's going to be open, open source, which I think open source software is the software industry, and integration is a big deal. Because software's going to be plentiful. >> Sure. >> Let's face it. It's a good time to be in software business. But Cloud's booming. So what's the downside, from your Databricks perspective? You see a buyer clicking on Databricks versus that alternative. What's potentially should they be a nervous about, down the road, if they go with a more proprietary or locked in approach? >> Yeah. >> Well, I think the challenge with proprietary ecosystems is you become beholden to the ability of that provider to both build relationships and convince other vendors that they should invest in that format. But you're also, then, beholden to the pace at which that provider is able to innovate. >> Mm-hmm. >> And I think we've seen lots of times over history where, you know, a proprietary format may run ahead, for a while, on a lot of innovation. But as that market control begins to solidify, that desire to innovate begins to degrade. Whereas in the open formats- >> So extract rents versus innovation. (John laughs) >> Exactly. Yeah, exactly. >> I'll say it. >> But in the open world, you know, you have to continue to innovate. >> Yeah. >> And the open source world is always innovating. If you look at the last 10 to 15 years, I challenge you to find, you know, an example where the innovation in the data and AI world is not coming from open source. And so by investing in open ecosystems, that means you are always going to be at the forefront of what is the latest. >> You know, again, not to date myself again, but you look back at the eighties and nineties, the protocol stacked with proprietary. >> Yeah. >> You know, SNA and IBM, deck net was digital. You know the rest. And then TCPIP was part of the open systems interconnect. >> Mm-hmm. >> Revolutionary (indistinct) a big part of that, as well as my school did. And so like, you know, that was, but it didn't standardize the whole stack. It stopped at IP and TCP. >> Yeah. >> But that helped inter operate, that created a nice defacto. So this is a big part of this mid game. I call it the chessboard, you know, you got opening game and mid-game, then you get the end game. You're not there at the end game yet at Cloud. But Cloud- >> There's, always some form of lock in, right? Andy Jazzy will address it, you know, when making a decision. But if you're going to make a decision you want to reduce- You don't want to be limited, right? So I would advise a customer that there could be limitations with a proprietary architecture. And if you look at what every customer's trying to become right now, is an AI driven business, right? And so it has to do with, can you get that data out of silos? Can you organize it and secure it? And then can you work with data scientists to feed those models? >> Yeah. >> In a very consistent manner. And so the tools of tomorrow will, to Joel's point, will be open and we want interoperability with those tools. >> And choice is a matter too. And I would say that, you know, the argument for why I think Amazon is not as locked in as maybe some other clouds, is that they have to compete directly too. Redshift competes directly with a lot of other stuff. But they can't play the bundling game because the customers are getting savvy to the fact that if you try to bundle an inferior product with something else, it may not work great at all. And they're going to be, they're onto it. This is the- >> To Amazon's credit by having these solutions that may compete with native services in marketplace, they are providing customers with choice, low price- >> And access to the core value. Which is the hardware- >> Exactly. >> Which is their platform. Okay. So I want to get you guys thought on something else I see emerging. This is, again, kind of Cube rumination moment. So on stage, Chris unpacked a lot of stuff. I mean this marketplace, they're touching a lot of hot buttons here, you know, pricing, compensation, workflows, services behind the curtain. And one of those things he mentioned was, they talk about resellers or channel partners, depending upon what you talk about. We believe, Dave and I believe on the Cube, that the entire indirect sales channel of the industry is going to be disrupted radically. Because those players were selling hardware in the old days and software. That game is going to change. You mentioned you guys have a program, let me get your thoughts on this. We believe that once this gets set up, they can play in this game and bring their services in. Which means that the old reseller channels are going to be rewritten. They're going to be refactored with this new kinds of access. Because you've got scale, you've got money and you've got product. And you got customers coming into the marketplace. So if you're like a reseller that sold computers to data centers or software, you know, a value added reseller or VAB or business. >> You've got to evolve. >> You got to, you got to be here. >> Yes. >> Yeah. >> How are you guys working with those partners? Because you say you have a product in your marketplace there. How do I make money if I'm a reseller with Databricks, with Amazon? Take me through that use case. >> Well I'll let Joel comment, but I think it's pretty straightforward, right? Customers need expertise. They need knowhow. When we're seeing customers do mass migrations to the cloud or Hadoop specific migrations or data transformation implementations. They need expertise from consulting and SI partners. If those consulting and SI partners happen to resell the solution as well. Well, that's another aspect of their business. But I really think it is the expertise that the partners bring to help customers get outcomes. >> Joel, channel big opportunity for Amazon to reimagine this. >> For sure. Yeah. And I think, you know, to your comment about how do resellers take advantage of that, I think what Jack was pushing on is spot on. Which is, it's becoming more and more about the expertise you bring to the table. And not just transacting the software. But now actually helping customers make the right choices. And we're seeing, you know, both SIs begin to be able to resell solutions and finding a lot of opportunity in that. >> Yeah. And I think we're seeing traditional resellers begin to move into that SI model as well. And that's going to be the evolution that this goes. >> At the end of the day, it's about services, right? >> For sure. Yeah. >> I mean... >> You've got a great service. You're going to have high gross profits. >> Yeah >> Managed service provider business is alive and well, right? Because there are a number of customers that want that type of a service. >> I think that's going to be a really hot, hot button for you guys. I think being the way you guys are open, this channel, partner services model coming in, to the fold, really kind of makes for kind of that Supercloud like experience, where you guys now have an ecosystem. And that's my next question. You guys have an ecosystem going on, within Databricks. >> For sure. >> On top of this ecosystem. How does that work? This is kind of like, hasn't been written up in business school and case studies yet. This is new. What is this? >> I think, you know, what it comes down to is, you're seeing ecosystems begin to evolve around the data platforms. And that's going to be one of the big, kind of, new horizons for us as we think about what drives ecosystems. It's going to be around, well, what's the data platform that I'm using? And then all the tools that have to encircle that to get my business done. And so I think there's, you know, absolutely ecosystems inside of the AWS business on all of AWS's services, across data analytics and AI. And then to your point, you are seeing ecosystems now arise around Databricks in its Lakehouse platform as well. As customers are looking at well, if I'm standing these Lakehouses up and I'm beginning to invest in this, then I need a whole set of tools that help me get that done as well. >> I mean you think about ecosystem theory, we're living a whole nother dream. And I'm not kidding. It hasn't yet been written up and for business school case studies is that, we're now in a whole nother connective tissue, ecology thing happening. Where you have dependencies and value proposition. Economics, connectedness. So you have relationships in these ecosystems. >> And I think one of the great things about the relationships with these ecosystems, is that there's a high degree of overlap. >> Yeah. >> So you're seeing that, you know, the way that the cloud business is evolving, the ecosystem partners of Databricks, are the same ecosystem partners of AWS. And so as you build these platforms out into the cloud, you're able to really take advantage of best of breed, the broadest set of solutions out there for you. >> Joel, Jack, I love it because you know what it means? The best ecosystem will win, if you keep it open. >> Sure, sure. >> You can see everything. If you're going to do it in the dark, you know, you don't know the outcome. I mean, this is really kind of what we're talking about. >> And John, can I just add that when I was at Amazon, we had a theory that there's buyers and builders, right? There's very innovative companies that want to build things themselves. We're seeing now that that builders want to buy a platform. Right? >> Yeah. >> And so there's a platform decision being made and that ecosystem is going to evolve around the platform. >> Yeah, and I totally agree. And the word innovation gets kicked around. That's why, you know, when we had our Supercloud panel, it was called the innovators dilemma, with a slash through it, called the integrater's dilemma. Innovation is the digital transformation. So- >> Absolutely. >> Like that becomes cliche in a way, but it really becomes more of a, are you open? Are you integrating? If APIs are connective tissue, what's automation, what's the service messages look like? I mean, a whole nother set of, kind of thinking, goes on in these new ecosystems and these new products. >> And that thinking is, has been born in Delta Sharing, right? So the idea that you can have a multi-cloud implementation of Databricks, and actually share data between those two different clouds, that is the next layer on top of the native cloud solution. >> Well, Databricks has done a good job of building on top of the goodness of, and the CapEx gift from AWS. But you guys have done a great job taking that building differentiation into the product. You guys have great customer base, great growing ecosystem. And again, I think a shining example of what every enterprise is going to do. Build on top of something, operating model, get that operating model, driving revenue. >> Mm-hmm. >> Yeah. >> Whether, you're Goldman Sachs or capital one or XYZ corporation. >> S and P global, NASDAQ. >> Yeah. >> We've got, you know, the biggest verticals in the world are solving tough problems with Databricks. I think we'd be remiss because if Ali was here, he would really want to thank Amazon for all of the investments across all of the different functions. Whether it's the relationship we have with our engineering and service teams. Our marketing teams, you know, product development. And we're going to be at Reinvent. A big presence at Reinvent. We're looking forward to seeing you there, again. >> Yeah. We'll see you guys there. Yeah. Again, good ecosystem. I love the ecosystem evolutions happening. This NextGen Cloud is here. We're seeing this evolve, kind of new economics, new value propositions kind of scaling up. Producing more. So you guys are doing a great job. Thanks for coming on the Cube and taking the time. Joel, great to see you at the check. >> Thanks for having us, John. >> Okay. Cube coverage here. The world's changing as APN comes together with the marketplace for a new partner organization at Amazon web services. The Cube's got it covered. This should be a very big, growing ecosystem as this continues. Billions of being sold through the marketplace. And of course the buyers are happy as well. So we've got it all covered. I'm John Furry. your host of the cube. Thanks for watching. (upbeat music)

>>Welcome back everyone to the cubes coverage here in Seattle, Washington, AWS's marketplace seller conference. It's the big news within the Amazon partner network, combining with marketplaces, forming the Amazon partner organization, part of a big reorg as they grow the next level NextGen cloud mid-game on the chessboard. Cube's got cover. I'm John fur, host of Cub, a great guests here from data bricks, both cube alumnis, Jack Anderson, GM of the and VP of the data bricks partnership team. For ADOS, you handle that relationship and Joel Minick vice president of product and partner marketing. You guys are the, have the keys to the kingdom with data, bricks, and AWS. Thanks for joining. Thanks for good to see you again. Thanks for >>Having us back. Yeah, John, great to be here. >>So I feel like we're at reinvent 2013 small event, no stage, but there's a real shift happening with procurement. Obviously it makes it's a no brainer on the micro, you know, people should be buying online self-service cloud scale, but Amazon's got billions being sold to their marketplace. They've reorganized their partner network. You can see kind of what's going on. They've kind of figured it out. Like let's put everything together and simplify and make it less of a website marketplace merge our partner to have more synergy and friction, less experiences so everyone can make more money and customer's gonna be happier. >>Yeah, that's right. >>I mean, you're run relationship. You're in the middle of it. >>Well, Amazon's mental model here is that they want the world's best ISVs to operate on AWS so that we can collaborate and co architect on behalf of customers. And that's exactly what the APO and marketplace allow us to do is to work with Amazon on these really, you know, unique use cases. >>You know, I interviewed Ali many times over the years. I remember many years ago, I think six, maybe six, seven years ago, we were talking. He's like, we're all in ons. Obviously. Now the success of data bricks, you've got multiple clouds. See that customers have choice, but I remember the strategy early on. It was like, we're gonna be deep. So this is speaks volumes to the, the relationship you have years. Jack take us through the relationship that data bricks has with AWS from a, from a partner perspective, Joel, and from a product perspective, because it's not like you got to Johnny come lately new to the new, to the scene, right? We've been there almost president creation of this wave. What's the relationship and has it relate to what's going on today? >>So, so most people may not know that data bricks was born on AWS. We actually did our first 100 million of revenue on Amazon. And today we're obviously available on multiple clouds, but we're very fond of our Amazon relationship. And when you look at what the APN allows us to do, you know, we're able to expand our reach and co-sell with Amazon and marketplace broadens our reach. And so we think of marketplace in three different aspects. We've got the marketplace, private offer business, which we've been doing for a number of years. Matter of fact, we we're driving well over a hundred percent year over year growth in private offers and we have a nine figure business. So it's a very significant business. And when a customer uses a private offer that private offer counts against their private pricing agreement with AWS. So they get pricing power against their, their private pricing. >>So it's really important. It goes on their Amazon bill in may. We launched our pay as you go on demand offering. And in five short months, we have well over a thousand subscribers. And what this does is it really reduces the barriers to entry it's low friction. So anybody in an enterprise or startup or public sector company can start to use data bricks on AWS and pay consumption based model and have it go against their monthly bill. And so we see customers, you know, doing rapid experimentation pilots, POCs, they're, they're really learning the value of that first use case. And then we see rapid use case expansion. And the third aspect is the consulting partner, private offers C P O super important in how we involve our partner ecosystem of our consulting partners and our resellers that are able to work with data bricks on behalf of customers. >>So you got the big contracts with the private offer. You got the product market fit, kind of people iterating with data coming in with, with the buyers you go. And obviously the integration piece all fitting in there. Exactly. Exactly. Okay. So that's that those are the offers that's current and what's in marketplace today. Is that the products, what are, what are people buying? I mean, I guess what's the Joel, what are, what are people buying in the marketplace and what does it mean for >>Them? So fundamentally what they're buying is the ability to take silos out of their organization. And that's, that is the problem that data bricks is out there to solve, which is when you look across your data landscape today, you've got unstructured data, you've got structured data, you've got real time streaming data, and your teams are trying to use all of this data to solve really complicated problems. And as data bricks as the lake house company, what we're helping customers do is how do they get into the new world? How do they move to a place where they can use all of that data across all of their teams? And so we allow them to begin to find through the marketplace, those rapid adoption use cases where they can get rid of these data, warehousing data lake silos they've had in the past, get their unstructured and structured data onto one data platform and open data platform that is no longer adherent to any proprietary formats and standards and something. >>They can very much, very easily integrate into the rest of their data environment, apply one common data governance layer on top of that. So that from the time they ingest that data to the time they use that data to the time they share that data inside and outside of their organization, they know exactly how it's flowing. They know where it came from. They know who's using it. They know who has access to it. They know how it's changing. And then with that common data platform with that common governance solution, they'd being able to bring all of those use cases together across their real time, streaming their data engineering, their BI, their AI, all of their teams working on one set of data. And that lets them move really, really fast. And it also lets them solve challenges. They just couldn't solve before a good example of this, you know, one of the world's now largest data streaming platforms runs on data bricks with AWS. >>And if you think about what does it take to set that up? Well, they've got all this customer data that was historically inside of data warehouses, that they have to understand who their customers are. They have all this unstructured data, they've built their data science model, so they can do the right kinds of recommendation engines and forecasting around. And then they've got all this streaming data going back and forth between click stream data from what the customers are doing with their platform and the recommendations they wanna push back out. And if those teams were all working in individual silos, building these kinds of platforms would be extraordinarily slow and complex, but by building it on data bricks, they were able to release it in record time and have grown at, at record pace >>To not be that's product platform that's impacting product development. Absolutely. I mean, this is like the difference between lagging months of product development to like days. Yes. Pretty much what you're getting at. Yeah. So total agility. I got that. Okay. Now I'm a customer I wanna buy in the marketplace, but I also, you got direct Salesforce up there. So how do you guys look at this? Is there channel conflict? Are there comp programs? Because one of the things I heard today in on the stage from a Davis's leadership, Chris was up there speaking and, and, and moment I was, Hey, he's a CRO conference, chief revenue officer conversation, which means someone's getting compensated. So if I'm the sales rep at data bricks, what's my motion to the customer. Do I get paid? Does Amazon sell it? Take us through that. Is there channel conflict? Is there or an audio lift? >>Well, I I'd add what Joel just talked about with, with, you know, what the solution, the value of the solution our entire offering is available on AWS marketplace. So it's not a subset, the entire data bricks offering and >>The flagship, all the, the top, >>Everything, the flagship, the complete offering. So it's not, it's not segmented. It's not a sub segment. It's it's, you know, you can use all of our different offerings. Now when it comes to seller compensation, we, we, we view this two, two different ways, right? One is that AWS is also incented, right? Versus selling a native service to recommend data bricks for the right situation. Same thing with data bricks. Our Salesforce wants to do the right thing for the customer. If the customer wants to use marketplace as their procurement vehicle. And that really helps customers because if you get data bricks and five other ISVs together, and let's say each ISV is spending, you're spending a million dollars, you have $5 million of spend, you put that spend through the flywheel with AWS marketplace. And then you can use that in your negotiations with AWS to get better pricing overall. So that's how we, >>We do it. So customers are driving. This sounds like, correct. For sure. So they're looking at this as saying, Hey, I'm gonna just get purchasing power with all my relationships because it's a solution architectural market, right? >>Yeah. It makes sense. Because if most customers will have a primary and secondary cloud provider, if they can consolidate, you know, multiple ISV spend through that same primary provider, you get pricing >>Power, okay, Jill, we're gonna date ourselves. At least I will. So back in the old days, it used to be, do a Barney deal with someone, Hey, let's go to market together. You gotta get paper, you do a biz dev deal. And then you gotta say, okay, now let's coordinate our sales teams, a lot of moving parts. So what you're getting at here is that the alternative for data bricks or any company is to go find those partners and do deals versus now Amazon is the center point for the customer so that you can still do those joint deals. But this seems to be flipping the script a little bit. >>Well, it is, but we still have VAs and consulting partners that are doing implementation work very valuable work advisory work that can actually work with marketplace through the C PPO offering. So the marketplace allows multiple ways to procure your >>Solution. So it doesn't change your business structure. It just makes it more efficient. That's >>Correct. >>That's a great way to say it. Yeah, >>That's great. So that's so that's it. So that's just makes it more efficient. So you guys are actually incented to point customers to the marketplace. >>Yes, >>Absolutely. Economically. Yeah. >>E economically it's the right thing to do for the customer. It's the right thing to do for our relationship with Amazon, especially when it comes back to co-selling right? Because Amazon now is leaning in with ISVs and making recommendations for, you know, an ISV solution and our teams are working backwards from those use cases, you know, to collaborate, land them. >>Yeah. I want, I wanna get that out there. Go ahead, Joel. >>So one of the other things I might add to that too, you know, and why this is advantageous for, for companies like data bricks to, to work through the marketplace, is it makes it so much easier for customers to deploy a solution. It's, it's very, literally one click through the marketplace to get data bricks stood up inside of your environment. And so if you're looking at how do I help customers most rapidly adopt these solutions in the AWS cloud, the marketplace is a fantastic accelerator to that. You >>Know, it's interesting. I wanna bring this up and get your reaction to it because to me, I think this is the future of procurement. So from a procurement standpoint, I mean, again, dating myself EDI back in the old days, you know, all that craziness. Now this is all the, all the internet, basically through the console, I get the infrastructure side, you know, spin up and provision. Some servers, all been good. You guys have played well there in the marketplace. But now as we get into more of what I call the business apps, and they brought this up on stage little nuance, most enterprises aren't yet there of integrating tech on the business apps, into the stack. This is where I think you guys are a use case of success where you guys have been successful with data integration. It's an integrator's dilemma, not an innovator's dilemma. So like, I want to integrate, so now I have integration points with data bricks, but I want to put an app in there. I want to provision an application, but it has to be built. It's not, you don't buy it. You build, you gotta build stuff. And this is the nuance. What's your reaction to that? Am I getting this right? Or, or am I off because no, one's gonna be buying software. Like they used to, they buy software to integrate it. >>Yeah, >>No, I, cause everything's integrated. >>I think AWS has done a great job at creating a partner ecosystem, right. To give customers the right tools for the right jobs. And those might be with third parties, data bricks is doing the same thing with our partner connect program. Right. We've got customer, customer partners like five tra and D V T that, you know, augment and enhance our platform. And so you, you're looking at multi ISV architectures and all of that can be procured through the AWS marketplace. >>Yeah. It's almost like, you know, bundling and unbundling. I was talking about this with, with Dave ante about Supercloud, which is why wouldn't a customer want the best solution in their architecture period. And it's class. If someone's got API security or an API gateway. Well, you know, I don't wanna be forced to buy something because it's part of a suite and that's where you see things get suboptimized where someone dominates a category and they have, oh, you gotta buy my version of this. Yeah. >>Joel, Joel. And that's Joel and I were talking, we're actually saying what what's really important about Databricks is that customers control the data. Right? You wanna comment on that? >>Yeah. I was say the, you know what you're pushing on there we think is extraordinarily, you know, the way the market is gonna go is that customers want a lot of control over how they build their data stack. And everyone's unique in what tools are the right ones for them. And so one of the, you know, philosophically I think really strong places, data, bricks, and AWS have lined up is we both take an approach that you should be able to have maximum flexibility on the platform. And as we think about the lake house, one thing we've always been extremely committed to as a company is building the data platform on an open foundation. And we do that primarily through Delta lake and making sure that to Jack's point with data bricks, the data is always in your control. And then it's always stored in a completely open format. And that is one of the things that's allowed data bricks to have the breadth of integrations that it has with all the other data tools out there, because you're not tied into any proprietary format, but instead are able to take advantage of all the innovation that's happening out there in the open source ecosystem. >>When you see other solutions out there that aren't as open as you guys, you guys are very open by the way, we love that too. We think that's a great strategy, but what's the, what am I foreclosing? If I go with something else that's not as open what what's the customer's downside as you think about what's around the corner in the industry. Cuz if you believe it's gonna be open, open source, which I think opens our software is the software industry and integration is a big deal, cuz software's gonna be plentiful. Let's face it. It's a good time to be in software business, but cloud's booming. So what's the downside from your data bricks perspective, you see a buyer clicking on data bricks versus that alternative what's potentially is should they be a nervous about down the road if they go with a more proprietary or locked in approach? Well, >>I think the challenge with proprietary ecosystems is you become beholden to the ability of that provider to both build relationships and convince other vendors that they should invest in that format. But you're also then beholden to the pace at which that provider is able to innovate. And I think we've seen lots of times over history where, you know, a proprietary format may run ahead for a while on a lot of innovation. But as that market control begins to solidify that desire to innovate begins to, to degrade, whereas in the open format. So >>Extract rents versus innovation. Exactly. >>Yeah, exactly. >>But >>I'll say it in the open world, you know, you have to continue to innovate. Yeah. And the open source world is always innovating. If you look at the last 10 to 15 years, I challenge you to find, you know, an example where the innovation in the data and AI world is not coming from open source. And so by investing in open ecosystems, that means you were always going to be at the forefront of what is the >>Latest, you know, again, not to date myself again, but you look back at the eighties and nineties, the protocol stacked for proprietary. Yeah. You know, SNA at IBM deck net was digital, you know, the rest is, and then TCP, I P was part of the open systems, interconnect, revolutionary Oly, a big part of that as well as my school did. And so like, you know, that was, but it didn't standardize the whole stack. It stopped at IP and TCP. Yeah. But that helped interoperate, that created a nice defacto. So this is a big part of this mid game. I call it the chessboard, you know, you got opening game and mid game. Then you got the end game and we're not there. The end game yet cloud the cloud. >>There's, there's always some form of lock in, right. Andy jazzy will, will address it, you know, when making a decision. But if you're gonna make a decision you want to reduce as you don't wanna be limited. Right. So I would advise a customer that there could be limitations with a proprietary architecture. And if you look at what every customer's trying to become right now is an AI driven business. Right? And so it has to do with, can you get that data outta silos? Can you, can you organize it and secure it? And then can you work with data scientists to feed those models? Yeah. In a, in a very consistent manner. And so the tools of tomorrow will to Joel's point will be open and we want interoperability with those >>Tools and, and choice is a matter too. And I would say that, you know, the argument for why I think Amazon is not as locked in as maybe some other clouds is that they have to compete directly too. Redshift competes directly with a lot of other stuff, but they can't play the bundling game because the customers are getting savvy to the fact that if you try to bundle an inferior product with something else, it may not work great at all. And they're gonna be they're onto it. This is >>The Amazon's credit by having these, these solutions that may compete with native services in marketplace, they are providing customers with choice, low >>Price and access to the S and access to the core value. Exactly. Which the >>Hardware, which is their platform. Okay. So I wanna get you guys thought on something else. I, I see emerging, this is again kind of cube rumination moment. So on stage Chris unpacked, a lot of stuff. I mean this marketplace, they're touching a lot of hot buttons here, you know, pricing compensation, workflows services behind the curtain. And one of the things he mentioned was they talk about resellers or channel partners, depending upon what you talk about. We believe Dave and I believe on the cube that the entire indirect sales channel of the industry is gonna be disrupted radically because those players were selling hardware in the old days and software, that game is gonna change. You know, you mentioned you guys have a program, want to get your thoughts on this. We believe that once this gets set up, they can play in this game and bring their services in which means that the old reseller channels are gonna be rewritten. They're gonna be refactored with this new kinds of access. Cuz you've got scale, you've got money and you've got product and you got customers coming into the marketplace. So if you're like a reseller that sold computers to data centers or software, you know, value added reseller or V or business, >>You've gotta evolve. >>You gotta, you gotta be here. Yes. How are you guys working with those partners? Cuz you say you have a part in your marketplace there. How do I make money? If I'm a reseller with data bricks with eight Amazon, take me through that use case. >>Well I'll let Joel comment, but I think it's, it's, it's pretty straightforward, right? Customers need expertise. They need knowhow. When we're seeing customers do mass migrations to the cloud or Hadoop specific migrations or data transformation implementations, they need expertise from consulting and SI partners. If those consulting SI partners happen to resell the solution as well. Well, that's another aspect of their business, but I really think it is the expertise that the partners bring to help customers get outcomes. >>Joel, channel big opportunity for re re Amazon to reimagine this. >>For sure. Yeah. And I think, you know, to your comment about how to resellers take advantage of that, I think what Jack was pushing on is spot on, which is it's becoming more about more and more about the expertise you bring to the table and not just transacting the software, but now actually helping customers make the right choices. And we're seeing, you know, both SI begin to be able to resell solutions and finding a lot of opportunity in that. Yeah. And I think we're seeing traditional resellers begin to move into that SI model as well. And that's gonna be the evolution that >>This gets at the end of the day. It's about services for sure, for sure. You've got a great service. You're gonna have high gross profits. And >>I think that the managed service provider business is alive and well, right? Because there are a number of customers that want that, that type of a service. >>I think that's gonna be a really hot, hot button for you guys. I think being the way you guys are open this channel partner services model coming in to the fold really kind of makes for kind of that super cloudlike experience where you guys now have an ecosystem. And that's my next question. You guys have an ecosystem going on within data bricks for sure. On top of this ecosystem, how does that work? This is kinda like hasn't been written up in business school and case studies yet this is new. What is this? >>I think, you know, what it comes down to is you're seeing ecosystems begin to evolve around the data platforms and that's gonna be one of the big kind of new horizons for us as we think about what drives ecosystems it's going to be around. Well, what is the, what's the data platform that I'm using and then all the tools that have to encircle that to get my business done. And so I think there's, you know, absolutely ecosystems inside of the AWS business on all of AWS's services, across data analytics and AI. And then to your point, you are seeing ecosystems now arise around data bricks in its Lakehouse platform, as well as customers are looking at well, if I'm standing these Lakehouse up and I'm beginning to invest in this, then I need a whole set of tools that help me get that done as well. >>I mean you think about ecosystem theory, we're living a whole nother dream and I'm, and I'm not kidding. It hasn't yet been written up and for business school case studies is that we're now in a whole nother connective tissue ecology thing happening where you have dependencies and value proposition economics connectedness. So you have relationships in these ecosystems. >>And I think one of the great things about relationships with these ecosystems is that there's a high degree of overlap. Yeah. So you're seeing that, you know, the way that the cloud business is evolving, the, the ecosystem partners of data bricks are the same ecosystem partners of AWS. And so as you build these platforms out into the cloud, you're able to really take advantage of best of breed, the broadest set of solutions out there for >>You. Joel, Jack, I love it because you know what it means the best ecosystem will win. If you keep it open. Sure. You can see everything. If you're gonna do it in the dark, you know, you don't know the outcome. I mean, this is really kind we're talking about. >>And John, can I just add that when I was in Amazon, we had a, a theory that there's buyers and builders, right? There's very innovative companies that want to build things themselves. We're seeing now that that builders want to buy a platform. Right? Yeah. And so there's a platform decision being made and that ecosystem gonna evolve around the >>Platform. Yeah. And I totally agree. And, and, and the word innovation get kicks around. That's why, you know, when we had our super cloud panel was called the innovators dilemma with a slash through it called the integrated dilemma, innovation is the digital transformation. So absolutely like that becomes cliche in a way, but it really becomes more of a, are you open? Are you integrating if APIs are the connective tissue, what's automation, what's the service message look like. I mean, a whole nother set of kind of thinking goes on and these new ecosystems and these new products >>And that, and that thinking is, has been born in Delta sharing. Right? So the idea that you can have a multi-cloud implementation of data bricks, and actually share data between those two different clouds, that is the next layer on top of the native cloud >>Solution. Well, data bricks has done a good job of building on top of the goodness of, and the CapEx gift from AWS. But you guys have done a great job taking that building differentiation into the product. You guys have great customer base, great grow ecosystem. And again, I think in a shining example of what every enterprise is going to do, build on top of something operating model, get that operating model, driving revenue. >>Yeah. >>Well we, whether whether you're Goldman Sachs or capital one or XYZ corporation >>S and P global NASDAQ, right. We've got, you know, these, the biggest verticals in the world are solving tough problems with data breaks. I think we'd be remiss cuz if Ali was here, he would really want to thank Amazon for all of the investments across all of the different functions, whether it's the relationship we have with our engineering and service teams. Yeah. Our marketing teams, you know, product development and we're gonna be at reinvent the big presence of reinvent. We're looking forward to seeing you there again. >>Yeah. We'll see you guys there. Yeah. Again, good ecosystem. I love the ecosystem evolutions happening this next gen cloud is here. We're seeing this evolve kind of new economics, new value propositions kind of scaling up, producing more so you guys are doing a great job. Thanks for coming on the Cuban, taking time. Chill. Great to see you at the check. Thanks for having us. Thanks. Going. Okay. Cube coverage here. The world's changing as APN comes to give the marketplace for a new partner organization at Amazon web services, the Cube's got a covered. This should be a very big growing ecosystem as this continues, billions of being sold through the marketplace. Of course the buyers are happy as well. So we've got it all covered. I'm John furry, your host of the cube. Thanks for watching.

>>Okay, welcome back to everyone. Cube's live coverage of VMware Explorer, 2022. I'm John fur, host of the cube. Two sets three days of live coverage. Dave Ante's here. Lisa Martin, Dave Nicholson, all host of the cube 12 interviews today, just we're with Rocklin and rolling, getting down to the end of the show. As we wind down and look back and look at the future. We've got Steven Jones. Here's the general manager of the VMware cloud on AWS. He's with Amazon web service. Steven Jones. Welcome to the cube. >>Thanks John. >>Welcome back cube alumni. I've been on many times going back to 2015. Yeah. >>Pleasure to be here. Great >>To see you again. Thanks for coming on. Obviously 10 years at AWS, what a ride is that's been, come on. That's fantastic. Tell me it's been crazy. >>Wow. Learned a lot of stuff along the way, right? I mean, we, we, we knew that there was a lot of opportunity, right? Customers wanting the agility and flexibility of, of the cloud and, and we, we still think it's early days, right? I mean, you'll hear Andy say that animals say that, but it really is. Right. If you look at even just the amount of spend that's being spent on, on clouds, it's in the billions, right. And the amount of, of spend in it is still in the trillion. So there's, there's a long way to go and customers are pushing us hard. Obviously >>It's been interesting a lot going on with VM. We're obviously around with them, obviously changing the strategy with their, their third generation and their narrative. Obviously the Broadcom thing is going on around them. And 10 years at abs, we've been, we've been, this'll be our ninth year, no 10th year at reinvent coming up for us. So, but it's 10 years of everything at Amazon, 10 years of S three, 10 years of C two. So if you look at the, the marks of time, now, the history books are starting to be written about Amazon web services. You know, it's about 10 years of full throttle cube hyperscaler in action. I mean, I'm talking about real growth, like >>Hardcore, for sure. I'll give you just one anecdote. So when I first joined, I think we had maybe two EC two instances back in the day and the maximum amount of memory you could conversion into one of these machines was I think 128 gig of Ram fast forward to today. You literally can get a machine with 24 terabytes of Ram just in insane amounts. Right? My, my son who's a gamer tells me he's got 16 gig in his, in his PC. You need to, he thinks that's a lot. >>Yeah. >>That's >>Excited about that. That's not even on his graphics card. I mean, he's, I know it's coming next. The GPU, I mean, just all >>The it's like, right? >>I mean, all the hardware innovation that you guys have done, I mean, look at every it's changed. Everyone's changed their strategy to copy AWS nitro, Dave ante. And I talk about this all the time, especially with James Hamilton and the team over there, Peter DeSantos, these guys have, are constantly going at the atoms and innovating at the, at the level. I mean that, that's how hardcore it is over there right now. I mean, and the advances on the Silicon graviton performance wise is crazy. I mean, so what does that enabling? So given that's continuing, you guys are continuing to do great work there on the CapEx side, we think that's enabling another set of new net new applications because we're starting to see new things emerge. We saw snowflake come on, customer of AWS refactor, the data warehouse, they call it a data cloud. You're starting to see Goldman Sachs. You see capital one, you see enterprise customers building on top of AWS and building a cloud business without spending the CapEx >>Is exactly right. And Ziggy mentioned graviton. So graviton is one of our fastest growing compute families now. And you know, you mentioned a couple of ISVs and partners of ours who are leaning in heavily on porting their own software. Every event Adam announced that we're working with SAP to, to help them port their HANA cloud, which is a, a database of service offering HANA flagship to graviton as well. So it's, it's definitely changing. >>And I think, you know, one of the, and we're gonna circle back to VMware is kind of a point to this. This conversation is that, is that if you look at the trends, right, okay. VMware really tried hard to do cloud and they had a good shot at it V cloud air, but it just, they didn't have the momentum that you guys had at AWS. We saw a lot, lot of other stragglers try to do cloud. They fell off the road, OpenStack, HP, and the list goes on and on. I don't wanna get into that, but the point is, as you guys become more powerful and you're open, right? So you have open ecosystem, you have people now coming back, taking advantage and refactoring and picking up where they left off. VMware was the one of the first companies that actually said, you know what pat Gelsinger said? And I was there, let's clear up the positioning. Let's go all in with AWS. That's >>Right >>At that time, 2016. >>Yeah. This was new for us, for >>Sure. And then now that's set the standard. Now everybody else is kind of doing it. Where is the VMware cloud relationship right now? How is that going out? State's worked. >>It's working well very well. It's I mean, we're celebrating, I think we made the announcement what, five years ago at this conference. Yeah. 2016. So, I mean, it's, it's been a tremendous ride. The best part are the customers who were coming and adopting and proving to us that our vision back then was the right vision. And, and, and what's been different. I think about this relationship. And it was new for us was that we, we purposely went after a jointly engineered solution. This wasn't a, we've got a, a customer or a partner that's just going to run and build something on us. This is something where we both bring muscle and we actually build a, a joint offering together. Talk about, about the main difference. >>Yeah. And that, and that's been working, but now here at this show, if you look at, if you squint through the multi-cloud thing, which is like just, I think positioning for, you know, what could happen in, in a post broad Broadcom world, the cloud native has traction they're Tansu where, where customers were leaning in. So their enterprise customer is what I call the classic. It, you know, mainstream enterprise, which you guys have been doing a lot of business with. They're now thinking, okay, I'm gonna go on continu, accelerate on, in the public cloud, but I'm gonna have hybrid on premise as well. You guys have that solution. Now they're gonna need cloud native. And we were speculating that VMware is probably not gonna be able to get 'em all of it. And, and that there's a lot more cloud native options as customers want more cloud native. How do you see that piece on Amazon side? Because there's a lot of benefits between the VMware cloud on AWS and the services that you guys have natively in your cloud. So we see customers really taking advantage of the AWS goodness, as well as expanding the cloud side at VMware cloud on AWS. >>Yeah. There's probably two ways I would look at this. Right? So, so one is the combination of VMware cloud on AWS. And then both native services just generally brings more options to customers. And so typically what we're seeing now is customers are just able to move much faster, especially as it comes to data center, evacuations, migrating all their assets, right? So it used to be that, and still some customers they're like, I I've gotta think through my entire portfolio of applications and decide what to refactor. And the only way I can move it to cloud is to actually refactor it into some net new application, more and more. We're actually seeing customers. They've got their assets. A lot of them are still on premises in a VMware state, right. They can move those super quick and then modernize those. And so I think where you'll see VMware and AWS very aligned is on this, this idea of migrate. Now you need to get the benefits of TCO and, and the agility that comes with being in the cloud and then modernize. We took a step further, which is, and I think VMware would agree here too, but all of the, the myriad of services, I think it's 200 plus now AWS native services are for use right alongside any that a customer wants to run in VMware. And so we have examples of customers that are doing just, >>And that's, that's how you guys see the native and, and VMware cloud integrating in. Yeah, that's, that's important because this, I mean, if I always joke about, you know, we've been here 12 years listening in the hallways and stuff, you know, on the bus to the event last night, walking the parties and whatnot, listening in the streets, there's kind of two conversations that rise right to the top. And I wanna get your reaction to this Steven, because this seems to be representative of this demographic here at VMware conference, there's conversations around ransomware and storage and D dub and recovery. It's all, a lot of those happen. Yeah. Clearly a big crowd here that care about, you know, Veeam and NetApp and storage and like making sure stuff's secure and air gapped. And a lot of that kind of, I call nerdy conversations and then the other one is, okay, I gotta get the cloud story. >>Right. So there's kind of the operational security. And then there's like, okay, what's my path to true cloud. I need to get this moving. I need to have better applications. My company is the application now not it serves some sort of back office function. Yeah. It's like, my company is completely using technology as its business. So the app is the business. So that means everything's technology driven, not departmental siloed. So there's a, that's what I call the true cloud conversation. How do you, how do you see that evolving because VMware customers are now going there. And I won't say, I won't say they're behind, but they're certainly going there faster than ever before. >>I think, I think, I mean, it's an interesting con it's an interesting way to put it and I, I would completely agree. I think it's, it's very clear that I think a lot of customer companies are actually being disrupted. Right. And they have to move fast and reinvent themselves. You said the app is now becoming the company. Right. I mean, if, if you look at where not too many years back, there were, you know, big companies like Netflix that were born in the cloud. Right. Airbnb they're disruptors. >>There's, that's the >>App, right? That's the app. Yeah. So I, I would exactly agree. And, and that's who other companies are competing with. And so they have to move quickly. You talked about some, some technology that allows them to do that, right? So this week we announced the general availability of a NetApp on tap solution. It's been available on AWS for some time as a fully managed FSX storage solution. But now customers can actually leverage it with, with VMC. Now, why is that important? Well, there's tens of thousands of customers running VMware. On-premises still, there's thousands of them that are actually using NetApp filers, right? NetApp, NetApp filers, and the same enterprise features like replication. D do you were talking about and Snapp and clone. Those types of things can be done. Now within the V VMware state on AWS, what's even better is they can actually move faster. So consider replicating all this, you know, petabytes and petabytes of data that are in these S from on-premises into AWS, this, this NetApp service, and then connected connecting that up to the BMC option. So it just allows customers much, much. >>You guys, you guys have always been customer focus. Every time I sat down with the Andy jazzy and then last year with Adam, same thing we worked back from, I know it's kind of a canned answer on some of the questions from media, but, but they do really care. I've had those conversations. You guys do work backwards from the customer, actually have documents called working backwards. But one of the things that I observed, we talked about here yesterday on the cube was the observations of reinvent versus say, VM world. Now explore is VM world's ecosystem was very partner-centric in the sense of the partners needed to rely on VMware. And the customers came here for both more of the partners, not so much VMware in the sense there wasn't as much, many, many announcements can compare that to the past, say eight years of reinvent, where there's so much Amazon action going on the partners, I won't say take as a second, has a backseat to Amazon, but the, the attendees go there generally for what's going on with AWS, because there's always new stuff coming out. >>And it's, it's amazing. But this year it starts to see that there's an overlap or, or change between like the VMware ecosystem. And now Amazon there's, a lot of our interviews are like, they're on both ecosystems. They're at Amazon's show they're here. So you start to see what I call the naturalization of partners. You guys are continuing to grow, and you'll probably still have thousands of announcements at the event this year, as you always do, but the partners are much more part of the AWS equation, not just we're leasing all these new services and, and oh, for sure. Look at us, look at Amazon. We're growing. Cause you guys were building out and look, the growth has been great. But now as you guys get to this next level, the partners are integral to the ecosystem. How do you look at that? How has Amazon thinking about that? I know there's been some, some, a lot of active reorgs around AWS around solving this problem or no solve the problem, addressing the need and this next level of growth. What's your reaction to >>That? Well, I mean, it's, it's a, it's a good point. So I have to be honest with you, John. I, I, I spent eight of my 10 years so far at AWS within the partner organization. So partners are very near and dear to my heart. We've got tens of thousands of partners and you are you're right. You're starting to see some overlap now between the VMware partner ecosystem and what we've built now in AWS and partners are big >>By the way, you sell out every reinvent. So it's, you have a lot of partners. I'm not suggesting that you, that there's no partner network there, but >>Partners are critical. I mean, absolutely naturally we want a relationship with a customer, but in order to scale the way we need to do to meet the, the needs of customers, we need partners. Right. We, we can't, we can't interact with every single customer as much as we would like to. Right. And so partners have long built teams and expertise that, that caters to even niche workloads or opportunity areas. And, and we love partners >>For that. Yeah. I know you guys do. And also we'll point out just to kind of give props to you guys on the partner side, you don't, you keep that top of the stack open on Amazon. You've done some stuff for end to end where customers want all Amazon, but for the most part, you let competition come in, even on, so you guys are definitely partner friendly. I'm just observing more the maturization of partners within the reinvent ecosystem, cuz we're there every year. I mean, it's, I mean, first of all, they're all buzzing. I mean, it's not like there's no action. There's a lot of customers there it's sold out as big numbers, but it just seems that the partners are much more integrated into the value proposition of at a AWS because of the, the rising tide and, and now their enablement, cuz now they're part of the, of the value proposition. Even more than ever before >>They, they really are. And they, and they're building a lot of capabilities and services on us. And so their customers are our customers. And like you say, it's rising tide, right. We, we all do better together. >>Okay. So let's talk about the VMware cloud here. What's the update here in terms of the show, what's your, what's your main focus cuz a lot of people here are doing, doing sessions. What's been some of the con content that you guys are producing here. >>Yeah. So the best part obviously is a always the customer conversations to partner conversations. So a, a lot of, a lot of sessions there, we did keynote yesterday in Ryan and I, where we talked about a number of announcements that are, I think pretty material now to the offering a joint announcement with NetApp yesterday as well around the storage solution I was talking about. And then some, some really good technical deep dives on how the offering works. Customers are still interested in like how, how do I take what I've got on premises and easily move into AWS and technology like HSX H CX solution with VMware makes it really easy without having to re IP applications. I mean, you know, it is super difficult sometimes to, to move an application. If you've got figure out where all the firewall rules are and re iPing those, those things source. But yeah, it's, it's been fantastic. >>A lot of migrations to the cloud too. A lot of cloud action, new cloud action. You guys have probably seen an uptake on services right on the native side. >>Yes. Yes. For sure. So maybe I just outlined some of the, some of the assets we made this week. So absolutely >>Go ahead. >>We, we announced a new instance family as a, a major workhorse underneath the VMware cloud offering called I, I, you mentioned nitro earlier, this is on, based on our latest generation of nitro, which allows us to offer as you know, bare metal instances, which is, which is what VMware actually VMware was our first partnership and customer that I would say actually drove us to really get Nira done and out the door. And we've continued to iterate on that. And so this I four, I instance, it's based on the, the latest Intel isolate processor with more than double the Ram double the compute, a whopping 75 gigabytes per second network. So it's a real powerhouse. The cool thing is that with the, with the NetApp storage solution that we, we discussed, we're now disaggregating the need to provision, compute and storage at the same time. It used to be, if you wanted to add more storage to your VSAN array, that was on a V VMware cloud. Yeah. You'd add another note. You might not need more compute for memory. You'd have to add another note. And so now customers can simply start adding chunks of storage. And so this opens up customers. I had a customer come to me yesterday and said, there's no reason for us not to move. Now. We were waiting for something that like this, that allowed us to move our data heavy workloads yeah. Into VMware cloud. It's >>Like, it's like the, the alignment. You mentioned alignment earlier. You know, I would say that VMware customers are lined up now almost perfectly with the hybrid story that's that's seamless or somewhat seems it's never truly seamless. But if you look at like what Deepak's doing with Kubernetes and open source, you, you guys have that there talking that big here, you got vs a eight vSphere, eight out it's all cloud native. So that's lined up with what you guys are doing on your services and the horsepower. They have their stuff, you have yours that works better together. So it seems like it's more lined up than ever before. What's your take on that? Do you agree? And, and if so, what folks watching here that are VMware customers, what's, what's the motivation now to go faster? >>Look, it is, it is absolutely lined up. We are, as, as I mentioned earlier, we are jointly engineering and developing this thing together. And so that includes not just the nuts and bolts underneath, but kind of the vision of where it's going. And so we're, we're collectively bringing in customer feedback. >>What is that vision real quick? >>So that vision has to actually help an under help meet even the most demanding customer workloads. Okay. So you've got customer workloads that are still locked in on premises. And why is that? Well, it used to be, there was big for data and migration, right? And the speed. And so we continue to iterate this and that again is a joint thing. Instead of say, VMware, just building on AWS, it really is a, a tight partnership. >>Yeah. The lift and shift is a, an easy thing to do. And, and, and by the way, that could be a hassle too. But I hear most people say the reason holding us back on the workloads is it's just a lot of work, a hassle making it easier is what they want. And you guys are doing that. >>We are doing that. Absolutely. And by the way, we've got not just engineering teams, but we've got customer support teams on both sides working together. We also have flexible commercial options, right? If a customer wants to buy from AWS because they've negotiated some kind of deal with us, they can do that. They wanna buy from VMware for a similar reason. They could buy from VMware. So are >>They in the marketplace? >>They are in the market. There, there are some things in the marketplace. So you talked about Tansu, there's a Tansu offering in the marketplace. So yes. Customers can >>Contract. Yeah. Marketplaces. I'm telling you that's very disruptive. I'm Billy bullish on the market AIOS marketplace. I think that's gonna be a transformative way. People have what they procure and fully agree, deploy and how, and channel relationships are gonna shift. I think that's gonna be a disruptive enabler to the partner equation and, and we haven't even seen it yet. We're gonna be up there in September for their inaugural event. I think it's a small group, but we're gonna be documenting that. So even final question for you, what's next for you? What's on the agenda. You got reinvent right around the corner. Your P ones are done. Right? I know. Assuming all that, I turn that general joke. That's an internal Amazon joke. FYI. You've got your plan. What's next for the world. Obviously they're gonna go this, take this, explore global. No matter what happens with Broadcom, this is gonna be a growth wave with hybrid. What's next for you and your team with AWS and VMware's relationship? >>Yeah. So both of us are hyper focused on adding additional options, both from a, an instance compute perspective. You know, VMware announced some, some, some additional offerings that we've got. We've got a fully complete, like, so they're, they announce things like VMware flex compute V VMware flex storage. You mentioned earlier, there was a conversation around ransomware. There's a new ransomware based offering. So we're hyper focused on rounding out, continuing to round out the offering and giving customers even more choice >>Real quick. Jonathan made me think about the ransomware we were at reinforce Steven Schmidtz now the CSO. Now you got a CSO. AJ's the CSO. You got a whole focus, huge emphasis on security right now. I know you always have, but now it's much more public. It's PO more positive, I think, than some of the other events I've been to. It's been more Lum and doom. What's the security tie in here with VMware. Can you share a little bit real quick on the security piece update around this relationship? >>Yeah, you bet. So as you know, security for us is job zero. Like you don't have anything of security. And so what are the things that, that we're excited about specifically with VMware is, is the latest offering that, that we put together and it's called this, this ransomware offering. And it's, it's a little bit different than other ransomware. I mean, a lot of people have ransomware offerings today, just >>Air gap. >>Right, right, right. Exactly. No, that's easy. No, this one is different. So on the back end, so within VMC, there's this, this option where CU we can be to be taking iterative snapshots of a customer environment. Now, if an event were to occur, right. And a customer is like, I have to know if I'm compromised, we can actually spin up super easy. This is cloud. Remember? Yeah. We can spin up a, a copy of this environment, throw a switch, pick a snapshot with NSX. So VMware NSX firewall it off and then use some custom tooling from VMware to actually see if it's been compromised or not. And then iterate through that until you actually know you're clean. And that's different than just tools that do maybe a >>Little bit of scam. We had Tom gills on yesterday and, and one of the things Dave ante had to leave is taking the sun to college is last one in the house and B nester now, but Tom Gill was on. We were talking about how good their security story is ware. And they really weren't showboating it as much as they could have here. I thought they could have done a better job, but this is an example of kind of them really leaning in with you guys. That's the key part of the relationship. >>Yeah, it really is. And I think this is something is materially different than what you can get elsewhere. And it's exciting for, >>Okay. Now the, the real question I want to know is what's your plans for AWS reinvent the blockbuster end of the year, Amazon surf show that gets bigger and bigger. I know it's still hybrid now, but it's looking be hybrid, but people are back in person last year. You guys were the first event really come back and still had massive numbers. AWS summit, New York at 19,000. I heard last week in Chicago, big numbers. So we're expecting reinvent to be pretty large this year. What are you, what are you gonna do there? What's your role there? >>We are expecting, well, I'll be there. I cover multiple businesses. Obviously. We're, we're planning on some additional announcements, obviously in the VMware space as well. And one of the other businesses I run is around SAP. And you should look for some things there as well. Yeah. Really looking forward to reinvent, except for the fact that it's right after Thanksgiving. But I think it >>Always ruins my, I always get an article out. I like, why are you we're having, we're having Thanksgiving dinner. I gotta write this article. It's gotta get Adam, Adam. Leski exclusive. We, every year we do a, a CEO sit down with Andy was the CEO and then now Adam. But yeah, it's a great event to me. I think it sets the tone. And it's gonna be very interesting to see the big clouds are coming to the big cloud. You guys, and you guys are now called hyperscalers. Now, multiple words. It's interesting. You guys are providing the CapEx goodness for everybody else now. And that relationship seems to be the new, the new industry standard of you guys provide the enablement and then everyone you get paid, cuz it's a service. A whole nother level of cloud is emerging in the partner network, GSI other companies. Yeah. >>Yeah. I mean we're really scaling. I mean we continue to iterate and release regions at a fast clip. We just announced support for VMware in Hong Kong. Yeah. So now we're up to 21 regions for this service, >>The sovereign clouds right around the corner. Let's we'll talk about that soon. Steven. Thanks for coming. I know you gotta go. Thank you for your valuable time. Coming in. Put Steven Jones. Who's the general manager of the VMware cloud on AWS business. Four AWS here inside the cube day. Three of cube coverage. I'm John furrier. Thanks for watching. We'll be right back.

>> From the theCUBE studios in Palo Alto in Boston, bringing you data driven insights from theCUBE and ETR. This is "Breaking Analysis" with Dave Vellante. >> Welcome to this week's Wikibon, theCUBE's insights powered by ETR. As we exited the isolation economy last year, supercloud is a term that we introduced to describe something new that was happening in the world of cloud. In this Breaking Analysis, we address the 10 most frequently asked questions we get around supercloud. Okay, let's review these frequently asked questions on supercloud that we're going to try to answer today. Look at an industry that's full of hype and buzzwords. Why the hell does anyone need a new term? Aren't hyperscalers building out superclouds? We'll try to answer why the term supercloud connotes something different from hyperscale clouds. And we'll talk about the problems that superclouds solve specifically. And we'll further define the critical aspects of a supercloud architecture. We often get asked, isn't this just multi-cloud? Well, we don't think so, and we'll explain why in this Breaking Analysis. Now in an earlier episode, we introduced the notion of super PaaS. Well, isn't a plain vanilla PaaS already a super PaaS? Again, we don't think so, and we'll explain why. Who will actually build and who are the players currently building superclouds? What workloads and services will run on superclouds? And 8-A or number nine, what are some examples that we can share of supercloud? And finally, we'll answer what you can expect next from us on supercloud? Okay, let's get started. Why do we need another buzzword? Well, late last year, ahead of re:Invent, we were inspired by a post from Jerry Chen called "Castles in the Cloud." Now in that blog post, he introduced the idea that there were sub-markets emerging in cloud that presented opportunities for investors and entrepreneurs that the cloud wasn't going to suck the hyperscalers. Weren't going to suck all the value out of the industry. And so we introduced this notion of supercloud to describe what we saw as a value layer emerging above the hyperscalers CAPEX gift, we sometimes call it. Now it turns out, that we weren't the only ones using the term as both Cornell and MIT have used the phrase in somewhat similar, but different contexts. The point is something new was happening in the AWS and other ecosystems. It was more than IaaS and PaaS, and wasn't just SaaS running in the cloud. It was a new architecture that integrates infrastructure, platform and software as services to solve new problems that the cloud vendors in our view, weren't addressing by themselves. It seemed to us that the ecosystem was pursuing opportunities across clouds that went beyond conventional implementations of multi-cloud. And we felt there was a structural change going on at the industry level, the supercloud, metaphorically was highlighting. So that's the background on why we felt a new catch phrase was warranted, love it or hate it. It's memorable and it's what we chose. Now to that last point about structural industry transformation. Andy Rappaport is sometimes and often credited with identifying the shift from the vertically integrated IBM mainframe era to the fragmented PC microprocesor-based era in his HBR article in 1991. In fact, it was David Moschella, who at the time was an IDC Analyst who first introduced the concept in 1987, four years before Rappaport's article was published. Moschella saw that it was clear that Intel, Microsoft, Seagate and others would replace the system vendors, and put that forth in a graphic that looked similar to the first two on this chart. We don't have to review the shift from IBM as the center of the industry to Wintel, that's well understood. What isn't as well known or accepted is what Moschella put out in his 2018 book called "Seeing Digital" which introduced the idea of "The Matrix" that's shown on the right hand side of this chart. Moschella posited that new services were emerging built on top of the internet and hyperscale clouds that would integrate other innovations and would define the next era of computing. He used the term Matrix because the conceptual depiction included not only horizontal technology rose like the cloud and the internet, but for the first time included connected industry verticals, the columns in this chart. Moschella pointed out that whereas historically, industry verticals had a closed value chain or stack and ecosystem of R&D, and production, and manufacturing, and distribution. And if you were in that industry, the expertise within that vertical generally stayed within that vertical and was critical to success. But because of digital and data, for the first time, companies were able to traverse industries, jump across industries and compete because data enabled them to do that. Examples, Amazon and content, payments, groceries, Apple, and payments, and content, and so forth. There are many examples. Data was now this unifying enabler and this marked a change in the structure of the technology landscape. And supercloud is meant to imply more than running in hyperscale clouds, rather it's the combination of multiple technologies enabled by CloudScale with new industry participants from those verticals, financial services and healthcare, manufacturing, energy, media, and virtually all in any industry. Kind of an extension of every company is a software company. Basically, every company now has the opportunity to build their own cloud or supercloud. And we'll come back to that. Let's first address what's different about superclouds relative to hyperscale clouds? You know, this one's pretty straightforward and obvious, I think. Hyperscale clouds, they're walled gardens where they want your data in their cloud and they want to keep you there. Sure, every cloud player realizes that not all data will go to their particular cloud so they're meeting customers where their data lives with initiatives like Amazon Outposts and Azure Arc, and Google Anthos. But at the end of the day, the more homogeneous they can make their environments, the better control, security, cost, and performance they can deliver. The more complex the environment, the more difficult it is to deliver on their brand promises. And of course, the lesser margin that's left for them to capture. Will the hyperscalers get more serious about cross-cloud services? Maybe, but they have plenty of work to do within their own clouds and within enabling their own ecosystems. They had a long way to go a lot of runway. So let's talk about specifically, what problems superclouds solve? We've all seen the stats from IDC or Gartner, or whomever the customers on average use more than one cloud. You know, two clouds, three clouds, five clouds, 20 clouds. And we know these clouds operate in disconnected silos for the most part. And that's a problem because each cloud requires different skills because the development environment is different as is the operating environment. They have different APIs, different primitives, and different management tools that are optimized for each respective hyperscale cloud. Their functions and value props don't extend to their competitors' clouds for the most part. Why would they? As a result, there's friction when moving between different clouds. It's hard to share data, it's hard to move work. It's hard to secure and govern data. It's hard to enforce organizational edicts and policies across these clouds, and on-prem. Supercloud is an architecture designed to create a single environment that enables management of workloads and data across clouds in an effort to take out complexity, accelerate application development, streamline operations and share data safely, irrespective of location. It's pretty straightforward, but non-trivial, which is why I always ask a company's CEO and executives if stock buybacks and dividends will yield as much return as building out superclouds that solve really specific and hard problems, and create differential value. Okay, let's dig a bit more into the architectural aspects of supercloud. In other words, what are the salient attributes of supercloud? So first and foremost, a supercloud runs a set of specific services designed to solve a unique problem and it can do so in more than one cloud. Superclouds leverage the underlying cloud native tooling of a hyperscale cloud, but they're optimized for a specific objective that aligns with the problem that they're trying to solve. For example, supercloud might be optimized for lowest cost or lowest latency, or sharing data, or governing, or securing that data, or higher performance for networking, for example. But the point is, the collection of services that is being delivered is focused on a unique value proposition that is not being delivered by the hyperscalers across clouds. A supercloud abstracts the underlying and siloed primitives of the native PaaS layer from the hyperscale cloud and then using its own specific platform as a service tooling, creates a common experience across clouds for developers and users. And it does so in a most efficient manner, meaning it has the metadata knowledge and management capabilities that can optimize for latency, bandwidth, or recovery, or data sovereignty, or whatever unique value that supercloud is delivering for the specific use case in their domain. And a supercloud comprises a super PaaS capability that allows ecosystem partners through APIs to add incremental value on top of the supercloud platform to fill gaps, accelerate features, and of course innovate. The services can be infrastructure-related, they could be application services, they could be data services, security services, user services, et cetera, designed and packaged to bring unique value to customers. Again, that hyperscalers are not delivering across clouds or on-premises. Okay, so another common question we get is, isn't that just multi-cloud? And what we'd say to that is yes, but no. You can call it multi-cloud 2.0, if you want, if you want to use it, it's kind of a commonly used rubric. But as Dell's Chuck Whitten proclaimed at Dell Technologies World this year, multi-cloud by design, is different than multi-cloud by default. Meaning to date, multi-cloud has largely been a symptom of what we've called multi-vendor or of M&A, you buy a company and they happen to use Google Cloud, and so you bring it in. And when you look at most so-called, multi-cloud implementations, you see things like an on-prem stack, which is wrapped in a container and hosted on a specific cloud or increasingly a technology vendor has done the work of building a cloud native version of their stack and running it on a specific cloud. But historically, it's been a unique experience within each cloud with virtually no connection between the cloud silos. Supercloud sets out to build incremental value across clouds and above hyperscale CAPEX that goes beyond cloud compatibility within each cloud. So if you want to call it multi-cloud 2.0, that's fine, but we chose to call it supercloud. Okay, so at this point you may be asking, well isn't PaaS already a version of supercloud? And again, we would say no, that supercloud and its corresponding superPaaS layer which is a prerequisite, gives the freedom to store, process and manage, and secure, and connect islands of data across a continuum with a common experience across clouds. And the services offered are specific to that supercloud and will vary by each offering. Your OpenShift, for example, can be used to construct a superPaaS, but in and of itself, isn't a superPaaS, it's generic. A superPaaS might be developed to support, for instance, ultra low latency database work. It would unlikely again, taking the OpenShift example, it's unlikely that off-the-shelf OpenShift would be used to develop such a low latency superPaaS layer for ultra low latency database work. The point is supercloud and its inherent superPaaS will be optimized to solve specific problems like that low latency example for distributed databases or fast backup and recovery for data protection, and ransomware, or data sharing, or data governance. Highly specific use cases that the supercloud is designed to solve for. Okay, another question we often get is who has a supercloud today and who's building a supercloud, and who are the contenders? Well, most companies that consider themselves cloud players will, we believe, be building or are building superclouds. Here's a common ETR graphic that we like to show with Net Score or spending momentum on the Y axis and overlap or pervasiveness in the ETR surveys on the X axis. And we've randomly chosen a number of players that we think are in the supercloud mix, and we've included the hyperscalers because they are enablers. Now remember, this is a spectrum of maturity it's a maturity model and we've added some of those industry players that we see building superclouds like CapitalOne, Goldman Sachs, Walmart. This is in deference to Moschella's observation around The Matrix and the industry structural changes that are going on. This goes back to every company, being a software company and rather than pattern match an outdated SaaS model, we see new industry structures emerging where software and data, and tools, specific to an industry will lead the next wave of innovation and bring in new value that traditional technology companies aren't going to solve, and the hyperscalers aren't going to solve. You know, we've talked a lot about Snowflake's data cloud as an example of supercloud. After being at Snowflake Summit, we're more convinced than ever that they're headed in this direction. VMware is clearly going after cross-cloud services you know, perhaps creating a new category. Basically, every large company we see either pursuing supercloud initiatives or thinking about it. Dell showed project Alpine at Dell Tech World, that's a supercloud. Snowflake introducing a new application development capability based on their superPaaS, our term of course, they don't use the phrase. Mongo, Couchbase, Nutanix, Pure Storage, Veeam, CrowdStrike, Okta, Zscaler. Yeah, all of those guys. Yes, Cisco and HPE. Even though on theCUBE at HPE Discover, Fidelma Russo said on theCUBE, she wasn't a fan of cloaking mechanisms, but then we talked to HPE's Head of Storage Services, Omer Asad is clearly headed in the direction that we would consider supercloud. Again, those cross-cloud services, of course, their emphasis is connecting as well on-prem. That single experience, which traditionally has not existed with multi-cloud or hybrid. And we're seeing the emergence of companies, smaller companies like Aviatrix and Starburst, and Clumio and others that are building versions of superclouds that solve for a specific problem for their customers. Even ISVs like Adobe, ADP, we've talked to UiPath. They seem to be looking at new ways to go beyond the SaaS model and add value within their cloud ecosystem specifically, around data as part of their and their customers digital transformations. So yeah, pretty much every tech vendor with any size or momentum and new industry players are coming out of hiding, and competing. Building superclouds that look a lot like Moschella's Matrix, with machine intelligence and blockchains, and virtual realities, and gaming, all enabled by the internet and hyperscale cloud CAPEX. So it's moving fast and it's the future in our opinion. So don't get too caught up in the past or you'll be left behind. Okay, what about examples? We've given a number in the past, but let's try to be a little bit more specific. Here are a few we've selected and we're going to answer the two questions in one section here. What workloads and services will run in superclouds and what are some examples? Let's start with analytics. Our favorite example is Snowflake, it's one of the furthest along with its data cloud, in our view. It's a supercloud optimized for data sharing and governance, query performance, and security, and ecosystem enablement. When you do things inside of that data cloud, what we call a super data cloud. Again, our term, not theirs. You can do things that you could not do in a single cloud. You can't do this with Redshift, You can't do this with SQL server and they're bringing new data types now with merging analytics or at least accommodate analytics and transaction type data, and bringing open source tooling with things like Apache Iceberg. And so it ticks the boxes we laid out earlier. I would say that a company like Databricks is also in that mix doing it, coming at it from a data science perspective, trying to create that consistent experience for data scientists and data engineering across clouds. Converge databases, running transaction and analytic workloads is another example. Take a look at what Couchbase is doing with Capella and how it's enabling stretching the cloud to the edge with ARM-based platforms and optimizing for low latency across clouds, and even out to the edge. Document database workloads, look at MongoDB, a very developer-friendly platform that with the Atlas is moving toward a supercloud model running document databases very, very efficiently. How about general purpose workloads? This is where VMware comes into to play. Very clearly, there's a need to create a common operating environment across clouds and on-prem, and out to the edge. And I say VMware is hard at work on that. Managing and moving workloads, and balancing workloads, and being able to recover very quickly across clouds for everyday applications. Network routing, take a look at what Aviatrix is doing across clouds, industry workloads. We see CapitalOne, it announced its cost optimization platform for Snowflake, piggybacking on Snowflake supercloud or super data cloud. And in our view, it's very clearly going to go after other markets is going to test it out with Snowflake, running, optimizing on AWS and it's going to expand to other clouds as Snowflake's business and those other clouds grows. Walmart working with Microsoft to create an on-premed Azure experience that's seamless. Yes, that counts, on-prem counts. If you can create that seamless and continuous experience, identical experience from on-prem to a hyperscale cloud, we would include that as a supercloud. You know, we've written about what Goldman is doing. Again, connecting its on-prem data and software tooling, and other capabilities to AWS for scale. And we can bet dollars to donuts that Oracle will be building a supercloud in healthcare with its Cerner acquisition. Supercloud is everywhere you look. So I'm sorry, naysayers it's happening all around us. So what's next? Well, with all the industry buzz and debate about the future, John Furrier and I, have decided to host an event in Palo Alto, we're motivated and inspired to further this conversation. And we welcome all points of view, positive, negative, multi-cloud, supercloud, hypercloud, all welcome. So theCUBE on Supercloud is coming on August 9th, out of our Palo Alto studios, we'll be running a live program on the topic. We've reached out to a number of industry participants, VMware, Snowflake, Confluent, Sky High Security, Gee Rittenhouse's new company, HashiCorp, CloudFlare. We've hit up Red Hat and we expect many of these folks will be in our studios on August 9th. And we've invited a number of industry participants as well that we're excited to have on. From industry, from financial services, from healthcare, from retail, we're inviting analysts, thought leaders, investors. We're going to have more detail in the coming weeks, but for now, if you're interested, please reach out to me or John with how you think you can advance the discussion and we'll see if we can fit you in. So mark your calendars, stay tuned for more information. Okay, that's it for today. Thanks to Alex Myerson who handles production and manages the podcast for Breaking Analysis. And I want to thank Kristen Martin and Cheryl Knight, they help get the word out on social and in our newsletters. And Rob Hof is our editor in chief over at SiliconANGLE, who does a lot of editing and appreciate you posting on SiliconANGLE, Rob. Thanks to all of you. Remember, all these episodes are available as podcasts wherever you listen. All you got to do is search Breaking Analysis podcast. It publish each week on wikibon.com and siliconangle.com. You can email me directly at david.vellante@siliconangle.com or DM me @DVellante, or comment on my LinkedIn post. And please do check out ETR.ai for the best survey data. And the enterprise tech business will be at AWS NYC Summit next Tuesday, July 12th. So if you're there, please do stop by and say hello to theCUBE, it's at the Javits Center. This is Dave Vellante for theCUBE insights powered by ETR. Thanks for watching. And we'll see you next time on "Breaking Analysis." (bright music)

>> From theCUBE Studios in Palo Alto and Boston, bringing you data-driven insights from theCUBE and ETR. This is "Breaking Analysis" with Dave Vallante. >> Welcome to this week's Wikibon CUBE Insights powered by ETR. As we exited the isolation economy last year, Supercloud is a term that we introduced to describe something new that was happening in the world of cloud. In this "Breaking Analysis," we address the 10 most frequently asked questions we get around Supercloud. Okay, let's review these frequently asked questions on Supercloud that we're going to try to answer today. Look at an industry that's full of hype and buzzwords. Why the hell does anyone need a new term? Aren't hyperscalers building out Superclouds? We'll try to answer why the term Supercloud connotes something different from hyperscale clouds. And we'll talk about the problems that Superclouds solve specifically, and we'll further define the critical aspects of a Supercloud architecture. We often get asked, "Isn't this just multi-cloud?" Well, we don't think so, and we'll explain why in this "Breaking Analysis." Now, in an earlier episode, we introduced the notion of super PaaS. Well, isn't a plain vanilla PaaS already a super PaaS? Again, we don't think so, and we'll explain why. Who will actually build and who are the players currently building Superclouds? What workloads and services will run on Superclouds? And eight A or number nine, what are some examples that we can share of Supercloud? And finally, we'll answer what you can expect next from us on Supercloud. Okay, let's get started. Why do we need another buzzword? Well, late last year ahead of re:Invent, we were inspired by a post from Jerry Chen called castles in the cloud. Now, in that blog post, he introduced the idea that there were submarkets emerging in cloud that presented opportunities for investors and entrepreneurs. That the cloud wasn't going to suck the hyperscalers, weren't going to suck all the value out of the industry. And so we introduced this notion of Supercloud to describe what we saw as a value layer emerging above the hyperscalers CAPEX gift, we sometimes call it. Now, it turns out that we weren't the only ones using the term, as both Cornell and MIT, have used the phrase in somewhat similar, but different contexts. The point is, something new was happening in the AWS and other ecosystems. It was more than IS and PaaS, and wasn't just SaaS running in the cloud. It was a new architecture that integrates infrastructure, platform and software as services, to solve new problems that the cloud vendors, in our view, weren't addressing by themselves. It seemed to us that the ecosystem was pursuing opportunities across clouds that went beyond conventional implementations of multi-cloud. And we felt there was a structural change going on at the industry level. The Supercloud metaphorically was highlighting. So that's the background on why we felt a new catch phrase was warranted. Love it or hate it, it's memorable and it's what we chose. Now, to that last point about structural industry transformation. Andy Rapaport is sometimes and often credited with identifying the shift from the vertically integrated IBM mainframe era to the fragmented PC microprocesor based era in his HBR article in 1991. In fact, it was David Moschella, who at the time was an IDC analyst who first introduced the concept in 1987, four years before Rapaport's article was published. Moschella saw that it was clear that Intel, Microsoft, Seagate and others would replace the system vendors and put that forth in a graphic that looked similar to the first two on this chart. We don't have to review the shift from IBM as the center of the industry to Wintel. That's well understood. What isn't as well known or accepted is what Moschella put out in his 2018 book called "Seeing Digital" which introduced the idea of the matrix that's shown on the right hand side of this chart. Moschella posited that new services were emerging, built on top of the internet and hyperscale clouds that would integrate other innovations and would define the next era of computing. He used the term matrix, because the conceptual depiction included, not only horizontal technology rows, like the cloud and the internet, but for the first time included connected industry verticals, the columns in this chart. Moschella pointed out that, whereas historically, industry verticals had a closed value chain or stack and ecosystem of R&D and production and manufacturing and distribution. And if you were in that industry, the expertise within that vertical generally stayed within that vertical and was critical to success. But because of digital and data, for the first time, companies were able to traverse industries jump across industries and compete because data enabled them to do that. Examples, Amazon and content, payments, groceries, Apple and payments, and content and so forth. There are many examples. Data was now this unifying enabler and this marked a change in the structure of the technology landscape. And Supercloud is meant to imply more than running in hyperscale clouds. Rather, it's the combination of multiple technologies, enabled by cloud scale with new industry participants from those verticals; financial services, and healthcare, and manufacturing, energy, media, and virtually all and any industry. Kind of an extension of every company is a software company. Basically, every company now has the opportunity to build their own cloud or Supercloud. And we'll come back to that. Let's first address what's different about Superclouds relative to hyperscale clouds. Now, this one's pretty straightforward and obvious, I think. Hyperscale clouds, they're walled gardens where they want your data in their cloud and they want to keep you there. Sure, every cloud player realizes that not all data will go to their particular cloud. So they're meeting customers where their data lives with initiatives like Amazon Outposts and Azure Arc and Google Antos. But at the end of the day, the more homogeneous they can make their environments, the better control, security, costs, and performance they can deliver. The more complex the environment, the more difficult it is to deliver on their brand promises. And, of course, the less margin that's left for them to capture. Will the hyperscalers get more serious about cross cloud services? Maybe, but they have plenty of work to do within their own clouds and within enabling their own ecosystems. They have a long way to go, a lot of runway. So let's talk about specifically, what problems Superclouds solve. We've all seen the stats from IDC or Gartner or whomever, that customers on average use more than one cloud, two clouds, three clouds, five clouds, 20 clouds. And we know these clouds operate in disconnected silos for the most part. And that's a problem, because each cloud requires different skills, because the development environment is different as is the operating environment. They have different APIs, different primitives, and different management tools that are optimized for each respective hyperscale cloud. Their functions and value props don't extend to their competitors' clouds for the most part. Why would they? As a result, there's friction when moving between different clouds. It's hard to share data. It's hard to move work. It's hard to secure and govern data. It's hard to enforce organizational edicts and policies across these clouds and on-prem. Supercloud is an architecture designed to create a single environment that enables management of workloads and data across clouds in an effort to take out complexity, accelerate application development, streamline operations, and share data safely, irrespective of location. It's pretty straightforward, but non-trivial, which is why I always ask a company's CEO and executives if stock buybacks and dividends will yield as much return as building out Superclouds that solve really specific and hard problems and create differential value. Okay, let's dig a bit more into the architectural aspects of Supercloud. In other words, what are the salient attributes of Supercloud? So, first and foremost, a Supercloud runs a set of specific services designed to solve a unique problem, and it can do so in more than one cloud. Superclouds leverage the underlying cloud native tooling of a hyperscale cloud, but they're optimized for a specific objective that aligns with the problem that they're trying to solve. For example, Supercloud might be optimized for lowest cost or lowest latency or sharing data or governing or securing that data or higher performance for networking, for example. But the point is, the collection of services that is being delivered is focused on a unique value proposition that is not being delivered by the hyperscalers across clouds. A Supercloud abstracts the underlying and siloed primitives of the native PaaS layer from the hyperscale cloud, and then using its own specific platform as a service tooling, creates a common experience across clouds for developers and users. And it does so in the most efficient manner, meaning it has the metadata knowledge and management capabilities that can optimize for latency, bandwidth, or recovery or data sovereignty, or whatever unique value that Supercloud is delivering for the specific use case in their domain. And a Supercloud comprises a super PaaS capability that allows ecosystem partners through APIs to add incremental value on top of the Supercloud platform to fill gaps, accelerate features, and of course, innovate. The services can be infrastructure related, they could be application services, they could be data services, security services, user services, et cetera, designed and packaged to bring unique value to customers. Again, that hyperscalers are not delivering across clouds or on premises. Okay, so another common question we get is, "Isn't that just multi-cloud?" And what we'd say to that is yeah, "Yes, but no." You can call it multi-cloud 2.0, if you want. If you want to use, it's kind of a commonly used rubric. But as Dell's Chuck Whitten proclaimed at Dell Technologies World this year, multi-cloud, by design, is different than multi-cloud by default. Meaning, to date, multi-cloud has largely been a symptom of what we've called multi-vendor or of M&A. You buy a company and they happen to use Google cloud. And so you bring it in. And when you look at most so-called multi-cloud implementations, you see things like an on-prem stack, which is wrapped in a container and hosted on a specific cloud. Or increasingly, a technology vendor has done the work of building a cloud native version of their stack and running it on a specific cloud. But historically, it's been a unique experience within each cloud, with virtually no connection between the cloud silos. Supercloud sets out to build incremental value across clouds and above hyperscale CAPEX that goes beyond cloud compatibility within each cloud. So, if you want to call it multi-cloud 2.0, that's fine, but we chose to call it Supercloud. Okay, so at this point you may be asking, "Well isn't PaaS already a version of Supercloud?" And again, we would say, "No." That Supercloud and its corresponding super PaaS layer, which is a prerequisite, gives the freedom to store, process, and manage and secure and connect islands of data across a continuum with a common experience across clouds. And the services offered are specific to that Supercloud and will vary by each offering. OpenShift, for example, can be used to construct a super PaaS, but in and of itself, isn't a super PaaS, it's generic. A super PaaS might be developed to support, for instance, ultra low latency database work. It would unlikely, again, taking the OpenShift example, it's unlikely that off the shelf OpenShift would be used to develop such a low latency, super PaaS layer for ultra low latency database work. The point is, Supercloud and its inherent super PaaS will be optimized to solve specific problems like that low latency example for distributed databases or fast backup in recovery for data protection and ransomware, or data sharing or data governance. Highly specific use cases that the Supercloud is designed to solve for. Okay, another question we often get is, "Who has a Supercloud today and who's building a Supercloud and who are the contenders?" Well, most companies that consider themselves cloud players will, we believe, be building or are building Superclouds. Here's a common ETR graphic that we like to show with net score or spending momentum on the Y axis, and overlap or pervasiveness in the ETR surveys on the X axis. And we've randomly chosen a number of players that we think are in the Supercloud mix. And we've included the hyperscalers because they are enablers. Now, remember, this is a spectrum of maturity. It's a maturity model. And we've added some of those industry players that we see building Superclouds like Capital One, Goldman Sachs, Walmart. This is in deference to Moschella's observation around the matrix and the industry structural changes that are going on. This goes back to every company being a software company. And rather than pattern match and outdated SaaS model, we see new industry structures emerging where software and data and tools specific to an industry will lead the next wave of innovation and bring in new value that traditional technology companies aren't going to solve. And the hyperscalers aren't going to solve. We've talked a lot about Snowflake's data cloud as an example of Supercloud. After being at Snowflake Summit, we're more convinced than ever that they're headed in this direction. VMware is clearly going after cross cloud services, perhaps creating a new category. Basically, every large company we see either pursuing Supercloud initiatives or thinking about it. Dell showed Project Alpine at Dell Tech World. That's a Supercloud. Snowflake introducing a new application development capability based on their super PaaS, our term, of course. They don't use the phrase. Mongo, Couchbase, Nutanix, Pure Storage, Veeam, CrowdStrike, Okta, Zscaler. Yeah, all of those guys. Yes, Cisco and HPE. Even though on theCUBE at HPE Discover, Fidelma Russo said on theCUBE, she wasn't a fan of cloaking mechanisms. (Dave laughing) But then we talked to HPE's head of storage services, Omer Asad, and he's clearly headed in the direction that we would consider Supercloud. Again, those cross cloud services, of course, their emphasis is connecting as well on-prem. That single experience, which traditionally has not existed with multi-cloud or hybrid. And we're seeing the emergence of smaller companies like Aviatrix and Starburst and Clumio and others that are building versions of Superclouds that solve for a specific problem for their customers. Even ISVs like Adobe, ADP, we've talked to UiPath. They seem to be looking at new ways to go beyond the SaaS model and add value within their cloud ecosystem, specifically around data as part of their and their customer's digital transformations. So yeah, pretty much every tech vendor with any size or momentum, and new industry players are coming out of hiding and competing, building Superclouds that look a lot like Moschella's matrix, with machine intelligence and blockchains and virtual realities and gaming, all enabled by the internet and hyperscale cloud CAPEX. So it's moving fast and it's the future in our opinion. So don't get too caught up in the past or you'll be left behind. Okay, what about examples? We've given a number in the past but let's try to be a little bit more specific. Here are a few we've selected and we're going to answer the two questions in one section here. What workloads and services will run in Superclouds and what are some examples? Let's start with analytics. Our favorite example of Snowflake. It's one of the furthest along with its data cloud, in our view. It's a Supercloud optimized for data sharing and governance, and query performance, and security, and ecosystem enablement. When you do things inside of that data cloud, what we call a super data cloud. Again, our term, not theirs. You can do things that you could not do in a single cloud. You can't do this with Redshift. You can't do this with SQL server. And they're bringing new data types now with merging analytics or at least accommodate analytics and transaction type data and bringing open source tooling with things like Apache Iceberg. And so, it ticks the boxes we laid out earlier. I would say that a company like Databricks is also in that mix, doing it, coming at it from a data science perspective trying to create that consistent experience for data scientists and data engineering across clouds. Converge databases, running transaction and analytic workloads is another example. Take a look at what Couchbase is doing with Capella and how it's enabling stretching the cloud to the edge with arm based platforms and optimizing for low latency across clouds, and even out to the edge. Document database workloads, look at Mongo DB. A very developer friendly platform that where the Atlas is moving toward a Supercloud model, running document databases very, very efficiently. How about general purpose workloads? This is where VMware comes into play. Very clearly, there's a need to create a common operating environment across clouds and on-prem and out to the edge. And I say, VMware is hard at work on that, managing and moving workloads and balancing workloads, and being able to recover very quickly across clouds for everyday applications. Network routing, take a look at what Aviatrix is doing across clouds. Industry workloads, we see Capital One. It announced its cost optimization platform for Snowflake, piggybacking on Snowflake's Supercloud or super data cloud. And in our view, it's very clearly going to go after other markets. It's going to test it out with Snowflake, optimizing on AWS, and it's going to expand to other clouds as Snowflake's business and those other clouds grows. Walmart working with Microsoft to create an on-premed Azure experience that's seamless. Yes, that counts, on-prem counts. If you can create that seamless and continuous experience, identical experience from on-prem to a hyperscale cloud, we would include that as a Supercloud. We've written about what Goldman is doing. Again, connecting its on-prem data and software tooling, and other capabilities to AWS for scale. And you can bet dollars to donuts that Oracle will be building a Supercloud in healthcare with its Cerner acquisition. Supercloud is everywhere you look. So I'm sorry, naysayers, it's happening all around us. So what's next? Well, with all the industry buzz and debate about the future, John Furrier and I have decided to host an event in Palo Alto. We're motivated and inspired to further this conversation. And we welcome all points of view, positive, negative, multi-cloud, Supercloud, HyperCloud, all welcome. So theCUBE on Supercloud is coming on August 9th out of our Palo Alto studios. We'll be running a live program on the topic. We've reached out to a number of industry participants; VMware, Snowflake, Confluent, Skyhigh Security, G. Written House's new company, HashiCorp, CloudFlare. We've hit up Red Hat and we expect many of these folks will be in our studios on August 9th. And we've invited a number of industry participants as well that we're excited to have on. From industry, from financial services, from healthcare, from retail, we're inviting analysts, thought leaders, investors. We're going to have more detail in the coming weeks, but for now, if you're interested, please reach out to me or John with how you think you can advance the discussion, and we'll see if we can fit you in. So mark your calendars, stay tuned for more information. Okay, that's it for today. Thanks to Alex Myerson who handles production and manages the podcast for "Breaking Analysis." And I want to thank Kristen Martin and Cheryl Knight. They help get the word out on social and in our newsletters. And Rob Hof is our editor in chief over at SiliconANGLE, who does a lot of editing and appreciate you posting on SiliconANGLE, Rob. Thanks to all of you. Remember, all these episodes are available as podcasts wherever you listen. All you got to do is search, breaking analysis podcast. I publish each week on wikibon.com and siliconangle.com. Or you can email me directly at david.vellante@siliconangle.com. Or DM me @DVallante, or comment on my LinkedIn post. And please, do check out etr.ai for the best survey data in the enterprise tech business. We'll be at AWS NYC summit next Tuesday, July 12th. So if you're there, please do stop by and say hello to theCUBE. It's at the Javits Center. This is Dave Vallante for theCUBE Insights, powered by ETR. Thanks for watching. And we'll see you next time on "Breaking Analysis." (slow music)

(upbeat music) >> Welcome back to the Seaport in Boston. This is day two of theCUBES's coverage of Red Hat Summit 2022 different format this year for Red Hat Summit. You know we are used to the eight to 9,000 people big conferences, but this is definitely and a lot of developers this is definitely a smaller, more intimate, more abbreviated keynotes which I love that new style they've really catering to the virtual audience as well as the physical audience, a lot of good stuff going on last night in the Seaport, which a lot of fun Stephanie Chiras is here is the Senior Vice President of Partner Ecosystem Success at Red Hat. >> Yeah. >> On the move again, Stephanie love to see you. >> yeah. Thank you. It's great to be here with you and now in a little different bit of a role. >> Yeah, I'm happy that we're actually in Boston and we can meet face to face. >> Yes. >> We don't have to get in a plane, but you know we'll be on a lot of planes in the next few months. >> Yeah. >> But look, a new role for you in ecosystems. You are interviewing all the partners, which is very cool. So you get a big observation space as my friend Jeff Jonas would like to say. And so, but I'd like to observe the partner ecosystem in this new era is different. >> It's very different. >> I mean just press release is going back it's really deep engineering and really interesting flywheel approaches. How is the cloud and the hybrid cloud ecosystem and partner ecosystem different today? >> I think there's a couple of things, I think first of all cloud accelerating all the innovation, the whole cloud motion pulls in a cloud partner in addition to many of the other partners that you need to deploy a solution. So this makes almost every deployment a multi-partner deployment. So that creates the need not just for one on one partnerships between companies and vendors but really for a multi-partner experience. Right, how does an ISV work with a distributor work with a cloud vendor? How do you pull all of that together and I think at Red Hat, our view of being a platform company, we want to be able to span that and bring all of those folks together. So I see this transition going from a world of partnerships into a world of a networked ecosystem. And the real benefit is when you can pull together one ecosystem with another ecosystem, build that up and it really becomes an ecosystem of ecosystems. >> Well and I'm a fan, you're a multi tool star, so it may kind of makes you dangerous because you can talk tech in your technical roles. You've been a GM so you understand the business and that's really what it takes in the part of ecosystem. It can't be just technology and just engineering integration, it's got to be a business model associated with that. Talk about those two dimensions. >> And I think what we're seeing in the ecosystem is there are partners that you build with there are partners you service with, there are partners you sell with some do all three, some do two out of three. How do you work those relationships at the end of the day every partner in the ecosystem wants to bring their value to the customer. And their real goal is how do you merge those values together and I think as you know, right, I come from the technology and the product space. I love moving into this space where you look for those value and that synergy of value to bring better technology, a better procurement experience is often really important and simplicity of deployment to customers, but partners span everything we do. We develop with them, we build with them, we deploy with them, we service with them and all has to come together. >> So how do you make this simple for customers? I mean you're describing an increasingly complex environment. How do you simplify this? >> So a couple of things one, spot onto your point Paul, I think customer expectations now are more aggressive than they've ever been that the ecosystem has done pre-work before they show up. The customer doesn't want to be the one who's pulling together this from one vendor, this from another vendor and stitching it together themselves. So there's a number of things I think we've stepped in to try and do digital engagement for certification and deployment, the creation of operators on OpenShift is one way that technology from partners can be done and enabled more easily and quickly with Red Hat platforms. I think in addition, you've seen. >> Can you go a little deeper on that? >> Sure. >> Explain that a little bit more what does that mean? Yeah, First off, we have a digital experience where partners can come in, they can certify and test their applications to run it on Red Hat platforms themselves. So it's a bit of a come one, come all. We also have an engineering team and a developer team to work side by side with them to build those into solutions. We've done things again to supplement that with capabilities of what we call validated patterns things we've done in the market with customers, with partners, we pull together a validated pattern, we put it onto GitHub so anyone can get access to it. It becomes kind of a recipe for deployment that's available for partners to come in and augment on top of that or customers can come in and pull it up GitHub and build off of it. So I feel like there's different layers in the sort of build model that we work with partners and you want to be able to on-ramp any partner wherever they want to influence their value. It could be at the base certification level, it could be even with RHEL 9 was a good one, right. RHEL 9 was the first version of RHEL that we deployed based upon the CentOS Stream model. CentOS Stream is an upstream version of RHEL very tightly tied into the development model but it allowed partners to engage with that code prior to deployment everything from hardware partners to ISV partners, it becomes a much more open way for them to collaborate with us, so there's so much we can do. >> What's the pitch to partners. I mean I know hybrid cloud is fundamental to your value proposition. I mean most people want hybrid cloud even though the cloud guys might not admit it, right, but so what's the pitch, how do you approach partners there's got to be a common theme there pitch me. >> I think one of the things when it comes to the Red Hat ecosystem is the ecosystem itself has to bring value. Yes, we at Red Hat want to bring value, we want to come in and make it easy and simple for you to access our technology when want to make it easy and simple to engage side by side in front of a customer. But at the end of the day the value of the Red Hat ecosystem is not only Red Hat, it's our partnerships with others. It's our partnerships with the hyperscalers, it's our partnerships with ISVs, it's our work in open source communities. So it's not about Red Hat being this sort of epicenter of the ecosystem. The value comes from the collective ecosystem as it stands, and I think we've made a number of changes here at the beginning of the year in order to create a end to end team within Red Hat that does everything from the build to the sell with all the way from end to end. And I think that's bringing a new layer of simplicity for our engagement with their partners, and it's allowing us to stitch together and introduce partners to partners. >> But you are a dot connector in a sense. >> Absolutely. >> And you can't do it all, I mean nobody can. >> Yeah. But especially Red Hat your strategy is not to do it all by design, so where's the big white spaces where you feel as though your strengths need to be complimented by the partners? >> Oh, I think you caught it spot on. We don't think we can do it all, we're a platform company, we know the value of hybrid cloud is all about bringing a flexibility of an ecosystem together. I think the places where we're really doubling down on is simplicity. So the Ansible announcement that we did right with Ansible automation platform on Azure. With that announcement, it brings in certified collections of ecosystem partners on that deployment. We do the work with Azure in order to do that deployment of Ansible automation platform, and then it comes with a set of certified collections that have been done with other partners. And I think those are the pieces where we can really double down on bringing simplicity. Right, so if I look at areas of focus, that's a great space, and I think it is all about connecting the dots, right, it's about connecting our work with Azure with our work with other ISV partners to pull that together and show up to a customer with something that's fast time to value. >> With so many partners to manage, how do you make sure you're not playing favorites. I guess how do you treat all partners equally or do you even try? >> We absolutely try. I think any partnership is a relationship, right, so it is what Red Hat brings to the table, it's also what the partner brings to the table. Our goal is to understand what the value is the partner wants to deliver to the customer. We focus on that and bringing that to the forefront of what we deploy. We absolutely in a hybrid world it's about choice and flexibility. Certainly there are partners and we made some announcements of course, this week, right yesterday and today with some we're continued to deepen our partnerships with those folks who are doubling down with us where their strategy is very well aligned with us. But our goal is to bring a broad ecosystem that offers customers choice. That's what hybrid cloud's all about. >> I remember years ago, your colleague Bob Pitino, I went down and met him in his office and he schooled me, he was awesome and we did a white board on alternative processors. >> Yeah. >> You guys were doing combat duty in the power division at the time. But basically he helped me understand the trend that is absolutely come true which is alternative processors. It's not just about the CPU anymore, it's about all the CPU and GPU and NPU and accelerators and all these other connected parts. You guys obviously are in the middle of that, you've got relationships with ARM, NVIDIA, Intel, we saw on stage today. Explain the importance and the trends that you see of these alternative processors and accelerators and what that means for customers in terms of the applications that they're now going to be able to tap. >> Yeah, so you know I love this topic when it comes. So one of the spaces is edge, right, we talked about edge today. Edge to me is the epitome of kind of a white space and an opportunity where ecosystem is essential. Edge is pulling together unique hardware capabilities from an accelerator all the way out to new network capabilities and then to AI applications. I mean the number of ISVs building AI applications is just expanding. So it's really that top to bottom ecosystem story, and our work with the telco comes in, our work with the ARM partners, the NVIDIA of the world, the accelerators of the world comes in edge. And then you pull it up to the applications as well. And then to touch in, we're seeing edge be deployed a lot in industries and industry verticals, right. A lot of edge deployments are tailored for a retail market or for a financial services sector. Again, for us, we rely very much on the ecosystem to go into industry verticals where platform companies. So our goal is to find those key partners in those industry verticals who speak the speak, talk the language, and we partner with them in order to support them and so this whole edge space pulls all of that together I think even out to the go to market with industry alignment. >> It's interesting to partner, so we're talking about Silicon, we could talk about that all day long. >> Yes. >> And then it spans and that we had Accenture on we had Raj yesterday. And it was interesting 'cause you think Accenture's like deep vertical industry expertise which it is but Raj's role is really cross industry, and then to tap into that industry expertise you guys had an announcement yesterday with those guys and obviously the GSIs are a key player. >> Absolutely. >> We saw a bunch of 'em last night out and about. >> Yeah. >> So talk about the importance of those relationships. >> I think we are in the announcement with Accenture is a great one, right. We're really doubling down because customers are looking to them, they're looking to the Accentures of the world to help them move into this hybrid world. It's not simple, it's not simple to deploy and get that value of the flexibility. So Accenture has built a number of tools in order to help customers on that journey which we talked about yesterday it really is a continuum of how customers adopt for their cloud space. And so us partnering with them offers a platform underneath, give them technology capabilities and Accenture is able to help customers and guide them along that journey and add a new layer of simplicity. So I think the GSI are critical in this space. >> Yeah. >> You talked about the number of companies developing AI, new AI tools right now. And it seems like there's just the pace of innovation is amazing, the number of startups is unprecedented. How do you decide who makes it into your partner system? What bars do they have to jump over to become a Red Hat partner? >> I think our whole partner structure is layered out quite honestly a bit in tiering, depending upon how much the partner is moving forward with Red Hat, how strategically we aligned our et cetera. But there is definitely a tier that is a come one come all, get your technology to work with Red Hat. We do that digitally now in the world of digital it's much easier to do that to give accessibility but there is definitely a tier that is a come one come all and participate. And then above that, it comes into tierings. How deeply do we go to do joint building to do co-creation and how do we sort of partner even on things like we have ARO and ROSA as you know which is OpenShift built with AWS with Azure those provide very deep technical engagements to bring that level of simplicity, but I would say it spans all the layers, right. We do have a dedicated engineering team to work with the ecosystem partners. We have a dedicated digital team to reach out and proactively right, invite folks to participate and encourage them through the thing and through the whole path. And we've done some things on enablement, we just made early March, we made enablement free for all our partners in order to learn more and get more skilled in Red Hat. Skills and skill creation is just critical for partners, and we want to start there right. >> So we started this conversation with how cloud ecosystems are different. And I think AWS as the mother of all ecosystems, so does Microsoft too but they've had it for a while. And I got felt like last decade partners were kind of afraid, all right, we're going to partner with a cloud vendor, but they're going to eat our lunch. I noticed last year at Reinvent that whole dynamic is changing and I think the industry's realizing this is not a zero sum game. That there's just so much opportunity especially when you start thinking about the edge. So you guys use the term hybrid, right, and John and I wrote a piece prior to Reinvent last year, we said there's something new brewing, we've got on-prem connecting to the clouds, it's going across clouds. People call that multi-cloud, but multi-cloud has been like multi-vendor. It really hasn't been a sort of strategy or a technical layer. And now you're talking the edge and we see the hyperscaler spending a hundred billion dollars a year on infrastructure. And now we see companies like yours and your ecosystem building on top of that. They're not afraid of it anymore, they're actually looking at it as a gift and so we coined this term called Supercloud which is a abstraction layer, and it rises above highs all the complexity of the underlying primitives and APIs and people kind of wince at the term Ashesh called it Metacloud which I like it's kind of fun. But do you feel like that's happening in the ecosystem? Is that a real trend or is that just my imagination? >> I think it's definitely a real trend and it's coming from customers, right, that's what customers want. So customers want the ability to choose are they going to self-manage their applications within a public cloud. There's much more than just technology in the public cloud too right. There's a procurement experience that they provide a simplicity of our relationship. They may choose one of the hyperscalers. They pick a procurement experience, they deepen that relationship, they leverage the services. And I think now what you're seeing is customers are demanding it. They want to be a part of that, they want to run on multiple clouds. And now we're looking at cloud services you've seen our strategy double down on cloud services. I think that kind of comes back together to a customer wants simplicity. They expect the ecosystem to work together behind the scenes. That's what capabilities like ARO are or OpenShift on Azure and OpenShift on AWS. That's what we can provide. We have an SRV team, we jointly support it with those partners behind the scenes but as you said, it's no longer that fear, right. We've rolled up our sleeves together specifically because we wanted to show up to the customer as one. >> Yeah, and by the way, it's not just traditional technology vendors, it's insurance companies, it's banks, it's manufacturers who are building out these so-called super clouds. And to have a super cloud, you got to have a super PaaS and OpenShift is the supers of all PaaS So Stephanie cheers, thanks so much for coming back to theCUBE, >> Oh it's my pleasure. it great to see you again. >> Thank you for the time. >> All right, and thank you for watching keep it right there this is day two of Red Hat Summit 2022 from the Seaport in Boston. You're watching theCUBE. (upbeat music)

(upbeat music) >> Hello, welcome to the AWS Partner Showcase presented by theCUBE. I'm John Furrier, your host. This is Showcase season one, episode two. I've got Danielle Greshock, Worldwide Director of ISV Partner Solutions Architects At AWS. Welcome to the kickoff, Speeding Innovation with AWS. Good to see you. >> Good to see you as well. Thanks, John. >> Okay, we've got some great companies we're presenting with this week, talking about kind of speeding innovation, really with the cloud. And obviously Amazon, you guys are number one and doing this has been the big theme from Reinvent, this past conference. A lot of people are refactoring in the cloud, from observability to new ways to counter ransomware, to even back up and recover. These were once point solutions, now they're not point solutions, they're part of the cloud platform that's powering new modern application. You know, from DS city pipelining, cloud native, it's out there now, it's now well known, people are looking at this and going, "okay, this is cloud next level," or "super cloud," or whatever we want to call it. It's happening, and people are having solutions and you're in the middle of it. So what's your take on this? Because you know, Veeam, Splunk Clumio and others, they're all doing great business and now refactoring in the cloud with AWS. >> Yeah, well I think that what a lot of companies are finding now is that moving to the cloud is really speeding their innovation. And of course there's been a faster move to the cloud because they realize the benefits that they can get from that movement. And, you know, companies like Veeam, like Clumio, they are building on top of AWS and coming up with new ways to solve customer problems. And then of course the other thing is that there's so much much access to data and insights that you weren't able to have before. But now that you can retain that data with the scale of the cloud, lots of companies are finding new and exciting things to do and innovate with that data that they are able to hang onto. >> You know, it's interesting, you see the entrepreneurial activity. I mean, I was reading- >> Yeah >> This is what I do on the weekends. I go back to 2006 and I look at the early Amazon posts of EC2 and S3. And that was a real great startup movement and that changed the game. Now, even today, the startups are out there. You look at Clumio, right? Poojan over there, he's been doing great stuff. He came from Nutanix, a hyperscale, and now he's got a startup that's growing like a weed out there and Amazon's powering that. You got Cohesity, they're almost going to go public, I believe. They've announced that, they're about to go public so they're going to be a public company. And you have Veeam, which has been in the ecosystems for many, many years, a decade. So these are a good mix of companies, and this is the makeup of the kind of customers you have. What's the thing that they have in common? Why should people pay attention to these companies and the relationship with Amazon web services? >> I mean, I think the thing that these companies really have in common is thinking about the cloud as this new paradigm that they are building for. You know, if I think about Veeam, you know we have really amped up a lot of, both our building and co-selling with Veeam and they're having a lot of success with small companies, medium companies big companies as well, just with their product. And so that is what I think is the difference is they are looking at us as an opportunity to innovate with their product and take advantage to what the opportunities the cloud provides there. >> What are you guys seeing as solution architects in your customer base? Look at AWS from a partnership standpoint. It used to be you get into the marketplace, you have some programs, okay, all good. You guys have shifted that. Can you give us an update on what you guys are doing with respect to offering new kinds of value as your customers change and grow? >> Yeah, I mean, definitely we've seen a lot of success with our SaaS factory program that is looking to, you know help companies make the transformation to SaaS. Also our workload migration program, helping ISVs to move even faster, their on premises business into AWS for sure. But I also just think that, you know, what our customers demand actually at this point is, they're really looking for full blown solutions. So us working with them on solutions, working closely with systems integrators who can help execute on those solutions. Those are all things that our successful ISVs are really leaning into. >> This month's featured companies all have one thing in common, they're all using data at scale and data as part of the developer process. You're seeing data being available, and they have to be available for machine learning and other things cause you have to be more agile. And the scale. So you got more flow and also scalable in terms of users and whatnot. So this is a common theme. What's happening from a customer standpoint as they start to rearchitect? Because you guys have to provide that now next level headroom. >> Yeah. I mean, I think that, you know, again we're seeing a lot of companies wanting to do different things with the volume of data that they actually have, and things that they were never even considering in on-prem. So we talk about refactoring, it's not simply a lift and shift, they're looking to get some technology benefit out of the move, right? So just kind of having a net net from on-prem into the cloud is not going to be good enough. And so we're looking to add that value when they go and make that investment. >> You know, we've been always writing about and covering Snowflake as an example, bring them up. You know you have Redshift that's also, you know competing I guess, with Redshift. But they're a partner, they're growing. They built on AWS and became valuable because they did it differently in the cloud. We're using that, there's many other examples like that, they're companies are coming in and building and taking advantage of the gift called scale. CapEx gift from AWS. And also you got Silicon coming, so more and more goodness on the Amazon side, enabling the partners. So I have to ask you, and that's all kind of documenting that's happening in real time, but what it's teasing out is that the integrations are changing, right? So you're seeing a lot more tightly coupled engineering or solutions with AWS and your top partners. Can you share insight into what that looks like and how you guys think about that? >> Yeah, and definitely a lot of our top partnerships really do start with integrations. That's where we're able to, you know, find the value, that differentiated solution on AWS. So, you know, Snowflake, as an example, just talked about how their integration with private link and some of their serverless integrations were really the cornerstones of the new partnership that they've built with us. And same thing with other ISVs, they've really looked at the integrations to be core, building the value with AWS, with our services and for our AWS customers. Of course these are very bespoke, you know? What's going to be important to a data company isn't going to be the same thing that's important to a storage based company, but still being able to bring the full value of the innovation that AWS makes and have that better together story is really where we find a lot of value there. >> Yeah, and you're in the middle of it too. You have the keys to the kingdom. Solution architects are all where the action is right now. Everyone's looking, okay I got to build on what I got and also I got to build the architecture in real time. And build on top, it's not a tear down, it's a continuation of what they had. >> Yeah, and even our most mature solutions and partnerships, those that are full SaaS solutions, the companies that are innovating and continuing to bring new features to market are the ones that we end up finding to have the most success with. And that is really what my team does is building those integrations and new solutions on AWS. It is our core reason we exist and you know, what we feel is the cornerstone to great partnerships >> You know, Dave Vellante and I on our team, we're always commenting about how the cloud scale is a real benefit to anyone, whether it's leveling up talent, bias, and you know women in tech is coming up, international women's day coming up around the corner. >> Yeah. >> That's happening, so it's all good, right? So, whether you're a startup or a big company if you get that one feature right in the cloud you can and really change your business. And I think this always used to be elusive for the product marketing teams of the old way things were built. You know, you got to test it out and put it out there. Now you got real time information, and for companies that are ISVs out there, they really can be nimble. >> Well, and that's the thing too, is we try very hard to make sure our ISVs have access to customers, our customers, and that's how they can figure out like what is the right thing to build for them. >> Whether you're big or small, the cloud's great. So I got to ask you, this is season one of the AWS partner showcase, we're proud to present that with you guys. It's been a great partnership, we love getting the stories out there. Episode two is about this theme about, you got little data here, you got backup recovery you got ransomware, you know, old point solutions. We've had a great conversation. Why should people pay attention to this episode in your opinion? What's the big aha going on here in this episode? >> I mean, for me, I think ISVs ask me all the time, how can I innovate with AWS? How can I have a successful partnership? This series will give you that answer. You can see real world examples of what other companies are doing to be successful. So I mean, that is reason enough when it's a very competitive tech technology market. So, you know, lots of good ideas there to see. >> Great stuff, and of course, again, these are big ISVs, they're doing great stuff. They're software developers, they're building the next modern applications. Danielle, thanks for coming out. You're the worldwide director of the ISV Partner Solution Architects at AWS, you're in the middle of all the great action. Must be fun, isn't it? >> It's a lot of fun. I couldn't ask for a better job. >> Alright, well thanks for coming on this keynote kickoff. Appreciate it. I'm John Furrier with theCUBE, you're watching, and we've got the whole series coming up, but this is the AWS Partner Showcase presented by theCUBE. Showcase season one, episode two, enjoy the great presentations. Thanks for watching. (upbeat music)

(gentle music) >> Hello, welcome to theCUBE's presentation of the AWS Showcase season one, episode two with the ISV Startups partners. I'm John Furrier, your host of theCUBE. We're joined by Morgan McLean, director of product management at Splunk, and Danielle Greshock, who is the director of ISVs solution architects at AWS. Welcome to the show. Thanks for coming on. >> Thanks for having us. >> And great. Thanks for having us. >> Great to see both of you, both theCUBE alumni, but the Splunk-AWS relationship has been going very, very well. You guys are doing great business enabling this app revolution. And cloud scale has been going extremely well. So let's get into it. You guys are involved in a lot of action around application revolution, around OpenTelemetry and open source. So let's get into it. What's the latest? >> Danielle, you go ahead. >> Well, I'll just jump in first. Obviously last year, not last year, but in 2020, we launched the AWS Distro for OpenTelemetry. The idea being essentially, we're able to bring in data from partners, from infrastructure running on AWS, from apps running on AWS, to really be able to increase observability across all cloud assets at your entire cloud platform. So, Morgan, if you want to chime in on how Splunk >> Morgan: Certainly. >> has worked out OpenTelemetry. >> Yeah. I mean, OpenTelemetry is super exciting. Obviously, there's a lot of partnership points between Amazon and Splunk, but OpenTelemetry is probably one of them that's the most visible to people who aren't already maybe using these two products together. And so, as Danielle mentioned, Amazon has their own distribution of OpenTelemetry, Splunk has their own, as well, and of course there's the main open source distribution that everybody knows and loves. Just for our viewers, just for clarity's sake, the separate distributions are fundamentally very similar to, almost identical to what's offered in the open source space, but they come preconfigured and they come with support guarantees from each company, meaning that you can actually get paid full support for an open source project, which is really fantastic for customers. And as Danielle mentioned, it's a great demonstration of the alliance between Splunk and Amazon Web Services. For example, the AWS Distro, when you use it, can export data to Amazon CloudWatch, various Amazon backed open source initiatives like Prometheus and others, and to Splunk Observability Cloud and to Splunk Enterprise. So it's a place that we've worked very closely together, and it's something that we're very excited about. >> So, Morgan, I want to get your take on the on the product management side and also how product are built these days. >> One of the big things we're seeing in cloud is that open source has been the big enabler for a lot of refactoring. And you got multiple distributions, but the innovations on top of that, can you talk about how you see the productization of new innovations with open source as you guys go into this market, because this is the new dynamic with cloud. We're seeing examples all over the place. Obviously, Amazon's going next level with what they're doing, and that open source, it's not a one game for all of it. You can have mix and match. Take us through the product angle. >> And in many ways, this is just another wave of the same thing, right? Like, if you think back in time, we all used and still use in many cases, virtual machines, most of those are based on Linux, right? Another large open source project. And so, open source software has been accelerating innovation in the cloud space and in the computing space generally for a very long time, which is fantastic. Our excitement with something like OpenTelemetry comes from both the project's capabilities but also what we can do with it. So for those who aren't already familiar with OpenTelemetry, OpenTelemetry allows you to extract really critical system telemetry, application signals and everything else you need from your own applications, from new services, from your infrastructure, from everything that you're running in a cloud environment. You can then send that data to another location for processing. And so John, you ask like, how does this accelerate innovation? What does it unlock? Well, the insight you can gain from this data means you can become so much more efficient as a development organization. You can make your applications so much more effective because when you send that data to something like Splunk Observability Cloud, to something like Amazon CloudWatch, to various other solutions on the market, they can give you deep, deep insight into your application's performance, to its structure, they can help you reduce outages. And so, it's very, very powerful because it allows organizations to use tools like Splunk, like Amazon, like other things to innovate so much more effectively. >> Danielle, can you comment >> If I could... >> on the AWS side because this is again on the big point. You guys are going next level, and you're starting to see patterns in the ISV world, certainly on the architecture side of partners doing things differently now on top of what they've already done. Could you share how AWS is helping customers accelerate? >> Well, just as Morgan was talking about what OpenTelemetry provides, you can see how from a partnership perspective, this is so valuable, right? What the partner team here at AWS is in the business of doing, is really enabling customer choice, right? And having that ability to plug in and pull data from different sources, post it to different sources, make it available for visibility across all of your resources is very powerful and it's something from the partner community that we really value because we want customers to be able to select best of breed solutions, what works for their business, which businesses are different and they may have different needs, and that also fosters that true innovation. A small company is going to develop and release software a lot differently than a large enterprise. And so, being able to support something like OpenTelemetry just enables that for all different kinds of customers. >> Morgan, add to that because the velocity of releases, certainly operational, stability, is key every predominant security, uptime, these are top concerns. And, you mention data too, >> And you mention challenges. >> You got the data in here. So you got a lot of data moving around, a lot of value. What's your take? >> Yeah. So, I'll speak with some specifics. So a challenge that developers have had for years when you're developing large services, which you can now do with platforms like AWS. So, it's very easy to go develop huge deployments. But a challenge they have is you go and build a mess, right? And like, I've worked earlier in my career in Web Services. And I remember in one of the first orgs I was in, I was one of the five people who really understood our ecommerce stack. Right? And so like, I would get dragged into all these meetings and I'd have to go draw like the 50 services we had, and how they interacted, and the changes that were made in the last week. And without observability tools like Splunk Observability Cloud, like the ones offered by Amazon, like the ones that are backed by the data that comes with OpenTelemetry, organizations basically rely on people like this, to go draw out their deployments so they understand what it is they've built. Well, as you can imagine, this crimps your development velocity, because most of your engineers, most of your tech leads, most of everyone else don't actually understand what it is they've built what it is they're running, because they need that global context. You get something like OpenTelemetry and the solutions that consume the data from it, and suddenly now, all your developers have that context, all of them when they're adding functionality to a service or they're updating their infrastructure, can actually understand how it interacts with the rest of the broader application. This lets you speed up your time to development, this lets you ship more safely, more securely. And finally, when things do go wrong, which will be less frequent, but when they do go wrong, you can fix them super rapidly. >> If I'm a customer, let me ask a question. I'm a customer and I say, "Okay, I love AWS, I love Splunk, I love OpenTelemetry. I got to have open sources, technology innovation is happening." What's the integration? What are some of the standards? Can you take us through how that's working together with you guys as a shared platform? >> Yeah. So let's take the Amazon distribution for OpenTelemetry or even the Splunk one. One of the first things they do is they include all of the receivers, all of the sort of data capture components that you need, out of box for platforms like AWS, right? And so, right away, you get that power and flexibility where you're getting access to all of these data sources, right? And so, that's part of that partnership. And additionally, once the data comes into OpenTelemetry, you can now send that to various different data sources, including, as Danielle mentioned, to multiple at the same time. So you can use whatever tools you want. And so when you talk about like what the partnership is actually providing to you as a customer and still, this is just within the context of OpenTelemetry, obviously there's a much broader partnership between these two companies than just that. But within the context of OpenTelemetry means you can download one of these distributions. It's fully supported. It works with both solutions and everything is just great, right? You don't need to go fiddle with that out of the box. To be clear, OpenTelemetry is a batteries included project, right? This means that even the standard distributions of OpenTelemetry include the components you need. You have to go directly, reference them and ensure that they're packaged in there, but they exist, right. But the nice thing about these distributions is that it's done, it's out of the box, you don't even have to worry about is something missing or do I need to include new exporters or new receivers? It's all there. It's preconfigured. It just works. And if something goes wrong and you have a support contact, you pick up the phone, you talk to someone to get it fixed. >> Danielle, what's the Amazon side 'cause agility and scale is one of the highlights you guys are seeing. How does this tie into that and how are you guys working backwards from the customers to support the partners? >> Well, I think just to add on essentially to what Morgan said, I think that AWS is a cloud platform, has always really had a focus on developers. And, we talk a lot about how AWS and Amazon as a whole really embraces this continuous integration and continuous deployment methods inside of our organization. And we talk about services, and observability is a huge part of that. The only way that you're actually able to release hundreds, thousands of times a day like Amazon does, is by having an observability platform, to be able to measure metrics, see changes in the environment, to be able to roll back if you need to, and to be able to quickly mitigate any challenges or anything that goes wrong at any part of the process. And so, when we preach that to our customers, I think it's something that we do that because we live it and breathe it. And so, things such as OpenTelemetry and such as the products that Splunk builds, those are also ways in which we believe our customers can achieve that. >> Yeah. And we can... I mean, as I mentioned before, this partnership goes well beyond OpenTelemetry, right? And so, if you go use like Splunk Enterprise, Enterprise Cloud, Splunk Observability Cloud, and you're running on AWS, you have excellent support and excellent visibility into your Amazon infrastructure, into the services and applications you've deployed on top of that infrastructure. We try and give you, and I think we do succeed in this. We give you the best possible experience, the deepest possible visibility, into what it is you've deployed on AWS, so that you can be even more successful as a business, and so that you can be even more successful on AWS as a platform. >> Yeah. This is a great conversation, Morgan. You mentioned the early days of Web Services. AWS stands for Amazon Web Services built on web services. So interesting throwback there, but made me think about the days of the early days of web services. And if you look at data, what's going on now, the top partners in AWS, you're seeing a lot of people thinking about data differently, they're refactoring, a lot of machine learning, a lot of AI going on at scale. So then, you got cloud native, things like Kubernetes and these new services being stood up and teared down with automation. A whole new operating model's coming. And so when you think about observability, the importance of it, I mean, can you share your perspective on this whole 'nother level? I mean, I always say that whole another level sounds cliche, but it is next level. I mean, this is completely different. What's your reaction? >> Yeah. There there's a ton of factors here, right? So as you point out, companies are totally shifting how they use their cloud infrastructure. And part of this you see during their cloud migrations, a part of it you see after, and they're shifting from their sort of stateful VMs that they may have had in the past to infrastructure that they tear down and put up regularly. And there's a lot more automation. With this, comes as I mentioned before, complexity, right? And also, with this comes more and more businesses becoming even more reliant on their digital infrastructure. And so, not having observability into your applications, into your services, into your infrastructure, to me, is akin to running a business, say running a large warehousing or distribution company, but not having any idea where you're shipping products or where things are, or not having any accounting or CFO, right? Like, business has become so digital. Business is so reliant on technology, and that's unlocked a ton of new things. It's great. But not having visibility into how that technology works or what it is that's deployed or how to fix it is akin to having no visibility to anything else in your business. It's nuts. And so, observability is super, super critical, particularly for customers who are adopting this new wave of cloud technologies on platforms like AWS. >> Danielle, on your side too, you're enabling this new capability so that businesses can do it, the partners do it, we're calling it super cloud. We've been calling it super cloud kind of dynamic where new things are happening with the data. And you guys are evolving with that. Can you share what you're seeing on your side as your partners start to go to the next level? What are you guys doing? How does it all come together? >> Well, we always talk about what has happened with data in the last couple of years, which the cloud has really enabled around, you know, variety and velocity and there's one other "V" that's escaping me right now, but essentially, all of this data is coming in and providing the ability for us to make better decisions, to build better products, to provide better experiences for customers. And so, I just think, the OpenTelemetry project, as well as what Splunk is doing is just another example of how we're taking this massive amount of data and being able to provide better experiences and outcomes for customers. >> And you guys have been working along together for long time, Splunk, and, it's been a great partners, if we're going back with that been covering it on theCUBE and SiliconANGLE. So, we know that, the change is key observability. Can you imagine a company without a CFO, Morgan? That's just boggles your mind, but that's what it's like right now. So... >> It is, yeah. >> And the people who take advantage of that are winning, right? So it's like, that's the key. >> Yeah, I know. I mean, even in my own career, right, I've moved between different companies. And I remember, when I joined Google in particular, which is where I worked at previously, I was very impressed with their internal observability tools. And I'm certain, I haven't worked at Amazon. I'm certainly, I just assume inside of Amazon they're excellent as well, so a lot of the large cloud firms these days. But it was so refreshing going from an organization where if we had some outage or something went wrong, there were like a very small set of people who could actually understand what was going on. And then you would just have to manually dive through logs and correlate requests manually between services. It's very challenging. And so, when things went wrong, they went wrong for a long, long time. And so, the companies that understood this even in the past are already very successful as a result. I think now, the rest of the industry is really in the midst of adopting these observability practices and the tools that are required to implement them, because you're right. Otherwise your development velocity slows down. Now you're getting out competed by your competition. And then, when you have a problem, it blows up for ages. And once again, your competition can take advantage of it. >> And, can you just summarize the observability piece relative to the OpenTelemetry? Where is that going to go? Where do you see that evolving? >> Sure. >> I see open source is growing like crazy, we all know that. >> Of course. >> But OpenTelemetry in particular and open source, 'cause this is a big hot area. >> Yes. So to set the stage for people, OpenTelemetry, unlocks observability in many ways. As I mentioned earlier, OpenTelemetry is how you capture data out of your application. It doesn't process it. It's not a replacement for something like Amazon CloudWatch or any Splunk's products, but it's how we get the data out of your system, which is a remarkably difficult problem. I won't dive into it today, but, those who work in this space are very aware. That's why this project exists and it's so big, that actually extracting information, metrics, logs, distributed traces, profiles, everything else, from your applications and from your infrastructure is very, very difficult. So for OpenTelemetry, where it's going is just continually getting better at extracting more types of data from more sources, and doing that more effectively for people in a more standardized way. That will unlock firms like Splunk, firms, like Amazon and others to better process this data. In terms of where that's going, the sky's the limit, right? Like, everyone's familiar with APM, people are familiar with infrastructure monitoring, but there's a lot more capabilities coming there for security analytics, for network performance monitoring, for getting down all the way to single lines of coding your application, how they impact everything. There's just so much power that's coming to the industry right now. I'm really excited to see where things go in the next few years. >> And Danielle, you're in the middle of all the action as a solution architect, really set the stage for their companies and the ISVs, and this is a big, hot area. What are the patterns you're seeing and what are some of the best practices that you're doing will help companies? >> Right. So I think, summarizing our entire conversation, the big things that we're seeing in the market is essentially more and more companies are looking to move to a continuous deployment and a continuous integration environment. And they're looking to innovate faster and spend less time hot patching or hot fixing their environments and they want to spend more time innovating. And so, that you know, the patterns that we're seeing is... What I see and what I actually experience firsthand at re:Invent when I talk to probably over 40 or 50 ISVs, is customers want to know in their environment, where are their changes? Where are their security vulnerabilities? Where are their data changes, and what are customers really experiencing, whether it's latency, poor experience throughout their products, those types of things? So security, data, and observability are just key to all of that experience and that's what we're definitely seeing as patterns, what we're seeing with our customers and also what value our ISVs are providing in that space. >> That's awesome. And the other thing I would observe is that there's more of an integration story going on around joint projects, whether it's open source. >> Absolutely. >> Because this is where we want to get that services connected. And it's mutual beneficial. I mean, this is really >> Exactly. >> whole 'nother, new kind of interoperable cloud scale. >> Yeah, if I could say one thing else there, I think that, a lot of the customers who are trying to move into the cloud now are, maybe not technology forward companies and they really need that solution. And that's very important. I think COVID has pushed a lot of companies into the cloud maybe very quickly. And, that has been something else we've observed in the market. So, solutions and full solutions between ISVs and ISVs, or ISVs and AWS is just becoming more and more common thing that we see. >> And, you mentioned John, in the open source space as well. Like, we're certainly from Amazon to Splunk. So we're talking a lot about those, but there's a lot of other firms involved in projects like OpenTelemetry. And I think it's very endearing, very heartening to see how well they cooperate in this community and how, when their interests are aligned, how effective they can be. And it's been very exciting to work in the space and very pleasant, honestly, to see everything come together with this huge set of customers and partners. >> Yeah. The pleasant surprise of the pandemic has been that people come into the cloud and they like it and they, "Hey, this works," and they double down on it. Then they realize, there's more there and they refactor. So, you're seeing real examples of that. So, this is a great discussion, great success story. Congratulations Morgan, Danielle. >> Thank you. >> Great partnership between Splunk and AWS. We've been following for a long time. And again, this highlights this whole another level of integrating super cloud kind of experience where people are getting more capabilities and doing more together, so great stuff. >> And this is just one facet of that, right? Like, there's all the other connections of Splunk Enterprise, Splunk security analytics products, and others. It's a deep, deep partnership between these firms. >> Yeah. And the companies that innovate and get that new capability are going to have an advantage. And you're seeing... >> Yes. >> Right? >> Agreed. >> And this is awesome, and great stuff, thank you for coming on and sharing that insight. >> Thank you. >> Congratulations Morgan over there at Splunk, great stuff. And Danielle, thanks for coming on and sharing the AWS perspective. >> Thanks for having me. >> And you guys are going to the next level. You moving up to stack as they say, all good stuff for customers. Thanks. >> Thank you. >> Okay. >> Thank you. >> This is season one, episode two of the AWS Partner Showcase. I'm John Furrier with theCUBE. Thanks for watching. (gentle music)

(gentle music) >> Hello, welcome to theCUBE's presentation of the AWS Showcase season one, episode two with the ISV Startups partners. I'm John Furrier, your host of theCUBE. We're joined by Morgan McLean, director of product management at Splunk, and Danielle Greshock, who is the director of ISVs solution architects at AWS. Welcome to the show. Thanks for coming on. >> Thanks for having us. >> And great. Thanks for having us. >> Great to see both of you, both theCUBE alumni, but the Splunk-AWS relationship has been going very, very well. You guys are doing great business enabling this app revolution. And cloud scale has been going extremely well. So let's get into it. You guys are involved in a lot of action around application revolution, around OpenTelemetry and open source. So let's get into it. What's the latest? >> Danielle, you go ahead. >> Well, I'll just jump in first. Obviously last year, not last year, but in 2020, we launched the AWS Distro for OpenTelemetry. The idea being essentially, we're able to bring in data from partners, from infrastructure running on AWS, from apps running on AWS, to really be able to increase observability across all cloud assets at your entire cloud platform. So, Morgan, if you want to chime in on how Splunk >> Morgan: Certainly. >> has worked out OpenTelemetry. >> Yeah. I mean, OpenTelemetry is super exciting. Obviously, there's a lot of partnership points between Amazon and Splunk, but OpenTelemetry is probably one of them that's the most visible to people who aren't already maybe using these two products together. And so, as Danielle mentioned, Amazon has their own distribution of OpenTelemetry, Splunk has their own, as well, and of course there's the main open source distribution that everybody knows and loves. Just for our viewers, just for clarity's sake, the separate distributions are fundamentally very similar to, almost identical to what's offered in the open source space, but they come preconfigured and they come with support guarantees from each company, meaning that you can actually get paid full support for an open source project, which is really fantastic for customers. And as Danielle mentioned, it's a great demonstration of the alliance between Splunk and Amazon Web Services. For example, the AWS Distro, when you use it, can export data to Amazon CloudWatch, various Amazon backed open source initiatives like Prometheus and others, and to Splunk Observability Cloud and to Splunk Enterprise. So it's a place that we've worked very closely together, and it's something that we're very excited about. >> So, Morgan, I want to get your take on the on the product management side and also how product are built these days. >> One of the big things we're seeing in cloud is that open source has been the big enabler for a lot of refactoring. And you got multiple distributions, but the innovations on top of that, can you talk about how you see the productization of new innovations with open source as you guys go into this market, because this is the new dynamic with cloud. We're seeing examples all over the place. Obviously, Amazon's going next level with what they're doing, and that open source, it's not a one game for all of it. You can have mix and match. Take us through the product angle. >> And in many ways, this is just another wave of the same thing, right? Like, if you think back in time, we all used and still use in many cases, virtual machines, most of those are based on Linux, right? Another large open source project. And so, open source software has been accelerating innovation in the cloud space and in the computing space generally for a very long time, which is fantastic. Our excitement with something like OpenTelemetry comes from both the project's capabilities but also what we can do with it. So for those who aren't already familiar with OpenTelemetry, OpenTelemetry allows you to extract really critical system telemetry, application signals and everything else you need from your own applications, from new services, from your infrastructure, from everything that you're running in a cloud environment. You can then send that data to another location for processing. And so John, you ask like, how does this accelerate innovation? What does it unlock? Well, the insight you can gain from this data means you can become so much more efficient as a development organization. You can make your applications so much more effective because when you send that data to something like Splunk Observability Cloud, to something like Amazon CloudWatch, to various other solutions on the market, they can give you deep, deep insight into your application's performance, to its structure, they can help you reduce outages. And so, it's very, very powerful because it allows organizations to use tools like Splunk, like Amazon, like other things to innovate so much more effectively. >> Danielle, can you comment >> If I could... >> on the AWS side because this is again on the big point. You guys are going next level, and you're starting to see patterns in the ISV world, certainly on the architecture side of partners doing things differently now on top of what they've already done. Could you share how AWS is helping customers accelerate? >> Well, just as Morgan was talking about what OpenTelemetry provides, you can see how from a partnership perspective, this is so valuable, right? What the partner team here at AWS is in the business of doing, is really enabling customer choice, right? And having that ability to plug in and pull data from different sources, post it to different sources, make it available for visibility across all of your resources is very powerful and it's something from the partner community that we really value because we want customers to be able to select best of breed solutions, what works for their business, which businesses are different and they may have different needs, and that also fosters that true innovation. A small company is going to develop and release software a lot differently than a large enterprise. And so, being able to support something like OpenTelemetry just enables that for all different kinds of customers. >> Morgan, add to that because the velocity of releases, certainly operational, stability, is key every predominant security, uptime, these are top concerns. And, you mention data too, >> And you mention challenges. >> You got the data in here. So you got a lot of data moving around, a lot of value. What's your take? >> Yeah. So, I'll speak with some specifics. So a challenge that developers have had for years when you're developing large services, which you can now do with platforms like AWS. So, it's very easy to go develop huge deployments. But a challenge they have is you go and build a mess, right? And like, I've worked earlier in my career in Web Services. And I remember in one of the first orgs I was in, I was one of the five people who really understood our ecommerce stack. Right? And so like, I would get dragged into all these meetings and I'd have to go draw like the 50 services we had, and how they interacted, and the changes that were made in the last week. And without observability tools like Splunk Observability Cloud, like the ones offered by Amazon, like the ones that are backed by the data that comes with OpenTelemetry, organizations basically rely on people like this, to go draw out their deployments so they understand what it is they've built. Well, as you can imagine, this crimps your development velocity, because most of your engineers, most of your tech leads, most of everyone else don't actually understand what it is they've built what it is they're running, because they need that global context. You get something like OpenTelemetry and the solutions that consume the data from it, and suddenly now, all your developers have that context, all of them when they're adding functionality to a service or they're updating their infrastructure, can actually understand how it interacts with the rest of the broader application. This lets you speed up your time to development, this lets you ship more safely, more securely. And finally, when things do go wrong, which will be less frequent, but when they do go wrong, you can fix them super rapidly. >> If I'm a customer, let me ask a question. I'm a customer and I say, "Okay, I love AWS, I love Splunk, I love OpenTelemetry. I got to have open sources, technology innovation is happening." What's the integration? What are some of the standards? Can you take us through how that's working together with you guys as a shared platform? >> Yeah. So let's take the Amazon distribution for OpenTelemetry or even the Splunk one. One of the first things they do is they include all of the receivers, all of the sort of data capture components that you need, out of box for platforms like AWS, right? And so, right away, you get that power and flexibility where you're getting access to all of these data sources, right? And so, that's part of that partnership. And additionally, once the data comes into OpenTelemetry, you can now send that to various different data sources, including, as Danielle mentioned, to multiple at the same time. So you can use whatever tools you want. And so when you talk about like what the partnership is actually providing to you as a customer and still, this is just within the context of OpenTelemetry, obviously there's a much broader partnership between these two companies than just that. But within the context of OpenTelemetry means you can download one of these distributions. It's fully supported. It works with both solutions and everything is just great, right? You don't need to go fiddle with that out of the box. To be clear, OpenTelemetry is a batteries included project, right? This means that even the standard distributions of OpenTelemetry include the components you need. You have to go directly, reference them and ensure that they're packaged in there, but they exist, right. But the nice thing about these distributions is that it's done, it's out of the box, you don't even have to worry about is something missing or do I need to include new exporters or new receivers? It's all there. It's preconfigured. It just works. And if something goes wrong and you have a support contact, you pick up the phone, you talk to someone to get it fixed. >> Danielle, what's the Amazon side 'cause agility and scale is one of the highlights you guys are seeing. How does this tie into that and how are you guys working backwards from the customers to support the partners? >> Well, I think just to add on essentially to what Morgan said, I think that AWS is a cloud platform, has always really had a focus on developers. And, we talk a lot about how AWS and Amazon as a whole really embraces this continuous integration and continuous deployment methods inside of our organization. And we talk about services, and observability is a huge part of that. The only way that you're actually able to release hundreds, thousands of times a day like Amazon does, is by having an observability platform, to be able to measure metrics, see changes in the environment, to be able to roll back if you need to, and to be able to quickly mitigate any challenges or anything that goes wrong at any part of the process. And so, when we preach that to our customers, I think it's something that we do that because we live it and breathe it. And so, things such as OpenTelemetry and such as the products that Splunk builds, those are also ways in which we believe our customers can achieve that. >> Yeah. And we can... I mean, as I mentioned before, this partnership goes well beyond OpenTelemetry, right? And so, if you go use like Splunk Enterprise, Enterprise Cloud, Splunk Observability Cloud, and you're running on AWS, you have excellent support and excellent visibility into your Amazon infrastructure, into the services and applications you've deployed on top of that infrastructure. We try and give you, and I think we do succeed in this. We give you the best possible experience, the deepest possible visibility, into what it is you've deployed on AWS, so that you can be even more successful as a business, and so that you can be even more successful on AWS as a platform. >> Yeah. This is a great conversation, Morgan. You mentioned the early days of Web Services. AWS stands for Amazon Web Services built on web services. So interesting throwback there, but made me think about the days of the early days of web services. And if you look at data, what's going on now, the top partners in AWS, you're seeing a lot of people thinking about data differently, they're refactoring, a lot of machine learning, a lot of AI going on at scale. So then, you got cloud native, things like Kubernetes and these new services being stood up and teared down with automation. A whole new operating model's coming. And so when you think about observability, the importance of it, I mean, can you share your perspective on this whole 'nother level? I mean, I always say that whole another level sounds cliche, but it is next level. I mean, this is completely different. What's your reaction? >> Yeah. There there's a ton of factors here, right? So as you point out, companies are totally shifting how they use their cloud infrastructure. And part of this you see during their cloud migrations, a part of it you see after, and they're shifting from their sort of stateful VMs that they may have had in the past to infrastructure that they tear down and put up regularly. And there's a lot more automation. With this, comes as I mentioned before, complexity, right? And also, with this comes more and more businesses becoming even more reliant on their digital infrastructure. And so, not having observability into your applications, into your services, into your infrastructure, to me, is akin to running a business, say running a large warehousing or distribution company, but not having any idea where you're shipping products or where things are, or not having any accounting or CFO, right? Like, business has become so digital. Business is so reliant on technology, and that's unlocked a ton of new things. It's great. But not having visibility into how that technology works or what it is that's deployed or how to fix it is akin to having no visibility to anything else in your business. It's nuts. And so, observability is super, super critical, particularly for customers who are adopting this new wave of cloud technologies on platforms like AWS. >> Danielle, on your side too, you're enabling this new capability so that businesses can do it, the partners do it, we're calling it super cloud. We've been calling it super cloud kind of dynamic where new things are happening with the data. And you guys are evolving with that. Can you share what you're seeing on your side as your partners start to go to the next level? What are you guys doing? How does it all come together? >> Well, we always talk about what has happened with data in the last couple of years, which the cloud has really enabled around, you know, variety and velocity and there's one other "V" that's escaping me right now, but essentially, all of this data is coming in and providing the ability for us to make better decisions, to build better products, to provide better experiences for customers. And so, I just think, the OpenTelemetry project, as well as what Splunk is doing is just another example of how we're taking this massive amount of data and being able to provide better experiences and outcomes for customers. >> And you guys have been working along together for long time, Splunk, and, it's been a great partners, if we're going back with that been covering it on theCUBE and SiliconANGLE. So, we know that, the change is key observability. Can you imagine a company without a CFO, Morgan? That's just boggles your mind, but that's what it's like right now. So... >> It is, yeah. >> And the people who take advantage of that are winning, right? So it's like, that's the key. >> Yeah, I know. I mean, even in my own career, right, I've moved between different companies. And I remember, when I joined Google in particular, which is where I worked at previously, I was very impressed with their internal observability tools. And I'm certain, I haven't worked at Amazon. I'm certainly, I just assume inside of Amazon they're excellent as well, so a lot of the large cloud firms these days. But it was so refreshing going from an organization where if we had some outage or something went wrong, there were like a very small set of people who could actually understand what was going on. And then you would just have to manually dive through logs and correlate requests manually between services. It's very challenging. And so, when things went wrong, they went wrong for a long, long time. And so, the companies that understood this even in the past are already very successful as a result. I think now, the rest of the industry is really in the midst of adopting these observability practices and the tools that are required to implement them, because you're right. Otherwise your development velocity slows down. Now you're getting out competed by your competition. And then, when you have a problem, it blows up for ages. And once again, your competition can take advantage of it. >> And, can you just summarize the observability piece relative to the OpenTelemetry? Where is that going to go? Where do you see that evolving? >> Sure. >> I see open source is growing like crazy, we all know that. >> Of course. >> But OpenTelemetry in particular and open source, 'cause this is a big hot area. >> Yes. So to set the stage for people, OpenTelemetry, unlocks observability in many ways. As I mentioned earlier, OpenTelemetry is how you capture data out of your application. It doesn't process it. It's not a replacement for something like Amazon CloudWatch or any Splunk's products, but it's how we get the data out of your system, which is a remarkably difficult problem. I won't dive into it today, but, those who work in this space are very aware. That's why this project exists and it's so big, that actually extracting information, metrics, logs, distributed traces, profiles, everything else, from your applications and from your infrastructure is very, very difficult. So for OpenTelemetry, where it's going is just continually getting better at extracting more types of data from more sources, and doing that more effectively for people in a more standardized way. That will unlock firms like Splunk, firms, like Amazon and others to better process this data. In terms of where that's going, the sky's the limit, right? Like, everyone's familiar with APM, people are familiar with infrastructure monitoring, but there's a lot more capabilities coming there for security analytics, for network performance monitoring, for getting down all the way to single lines of coding your application, how they impact everything. There's just so much power that's coming to the industry right now. I'm really excited to see where things go in the next few years. >> And Danielle, you're in the middle of all the action as a solution architect, really set the stage for their companies and the ISVs, and this is a big, hot area. What are the patterns you're seeing and what are some of the best practices that you're doing will help companies? >> Right. So I think, summarizing our entire conversation, the big things that we're seeing in the market is essentially more and more companies are looking to move to a continuous deployment and a continuous integration environment. And they're looking to innovate faster and spend less time hot patching or hot fixing their environments and they want to spend more time innovating. And so, that you know, the patterns that we're seeing is... What I see and what I actually experience firsthand at re:Invent when I talk to probably over 40 or 50 ISVs, is customers want to know in their environment, where are their changes? Where are their security vulnerabilities? Where are their data changes, and what are customers really experiencing, whether it's latency, poor experience throughout their products, those types of things? So security, data, and observability are just key to all of that experience and that's what we're definitely seeing as patterns, what we're seeing with our customers and also what value our ISVs are providing in that space. >> That's awesome. And the other thing I would observe is that there's more of an integration story going on around joint projects, whether it's open source. >> Absolutely. >> Because this is where we want to get that services connected. And it's mutual beneficial. I mean, this is really >> Exactly. >> whole 'nother, new kind of interoperable cloud scale. >> Yeah, if I could say one thing else there, I think that, a lot of the customers who are trying to move into the cloud now are, maybe not technology forward companies and they really need that solution. And that's very important. I think COVID has pushed a lot of companies into the cloud maybe very quickly. And, that has been something else we've observed in the market. So, solutions and full solutions between ISVs and ISVs, or ISVs and AWS is just becoming more and more common thing that we see. >> And, you mentioned John, in the open source space as well. Like, we're certainly from Amazon to Splunk. So we're talking a lot about those, but there's a lot of other firms involved in projects like OpenTelemetry. And I think it's very endearing, very heartening to see how well they cooperate in this community and how, when their interests are aligned, how effective they can be. And it's been very exciting to work in the space and very pleasant, honestly, to see everything come together with this huge set of customers and partners. >> Yeah. The pleasant surprise of the pandemic has been that people come into the cloud and they like it and they, "Hey, this works," and they double down on it. Then they realize, there's more there and they refactor. So, you're seeing real examples of that. So, this is a great discussion, great success story. Congratulations Morgan, Danielle. >> Thank you. >> Great partnership between Splunk and AWS. We've been following for a long time. And again, this highlights this whole another level of integrating super cloud kind of experience where people are getting more capabilities and doing more together, so great stuff. >> And this is just one facet of that, right? Like, there's all the other connections of Splunk Enterprise, Splunk security analytics products, and others. It's a deep, deep partnership between these firms. >> Yeah. And the companies that innovate and get that new capability are going to have an advantage. And you're seeing... >> Yes. >> Right? >> Agreed. >> And this is awesome, and great stuff, thank you for coming on and sharing that insight. >> Thank you. >> Congratulations Morgan over there at Splunk, great stuff. And Danielle, thanks for coming on and sharing the AWS perspective. >> Thanks for having me. >> And you guys are going to the next level. You moving up to stack as they say, all good stuff for customers. Thanks. >> Thank you. >> Okay. >> Thank you. >> This is season one, episode two of the AWS Partner Showcase. I'm John Furrier with theCUBE. Thanks for watching. (gentle music)

(bright music) >> Welcome back everyone to theCUBE's coverage of AWS re:Invent 2021 in person. So a live event, physical in-person, also virtual hybrid. So a lot of great action online, check out the website. All the videos are there on theCUBE, as well as what's going on all of the actions on site and theCUBE's here. I'm John Furrier, your host with Dave Vellante, my cohost. Finally, we've got David Brown, VP of Elastic Compute Cloud. EC2, the bread and butter. Our favorite part of Amazon. David, great to have you back on theCUBE in person. >> John, it's great to be back. It's the first time I'd been on theCUBE in person as well. A lot of virtual events with you guys, but it's amazing to be back at re:Invent. >> We're so excited for you. I know, Matt Garman and I've talked in the past. We've talked in the past. EC2 is just an amazing product. It's always been the core block of AWS. More and more action happening and developers are now getting more action and there's well, we wrote a big piece about it. What's going on? The Silicon's really paying off. You've got to also general purpose Intel and AMD, and you've got the custom silicon, all working together. What's the new update? Give us a scoop. >> Well, John, it's actually 15 years of EC2 this year and I've been lucky to be on that team for 14 years and so incredible to see the growth. It's been an amazing journey. The thing that's really driven us, two things. One is supporting new workloads. And so what are the workloads that customers have available out there trying to do on the cloud that we don't support and launch new instance types. And that's the first thing. The second one is price performance. How do we give customers more performance at a continuously decreasing price year-over-year? And that's just driven innovation across EC2 over the years with things like Graviton. All of our inferential chips are custom silicon, but also instance types with the latest Intel Ice Lake CPU's, latest Milan. We just announced the AMD Milan instance. It's just constantly innovation across the ever-increasing list of instances. So super exciting. >> So instances become the new thing. Provision an instance, spin up an instance. Instance becomes, and you can get instances, flavors, almost like flavors, right? >> David: Yeah. >> Take us through the difference between an instance and then the EC2 itself. >> That's correct, yeah. So we actually have, by end of the year, right now we have over 475 different instances available to you whether it's GPU accelerators, high-performance computing instances, memory optimized, just enormous number. We'll actually hit 500 by the end of the year, but that is it. I mean, customers are looking for different types of machines and those are the instances. >> So the Custom Silicon, it's one of the most interesting developments. We've written about it. AWS secret weapon is one of them. I wonder if you could take us back to the decision points and the journey. The Annapurna acquisition, you started working with them as a partner, then you said, all right, let's just buy the company. >> David: Yeah. >> And then now, you're seeing the acceleration, your time to tapeout is way, way compressed. Maybe what was the catalyst and maybe we can get into where it's going. >> Yeah, absolutely. Super interesting story 'cause it actually starts all the way back in 2008. In 2008, EC2 had actually been around for just a little under two years. And if you remember back then, everybody was like, will virtualize and hypervisors, specialization would never really get you the same performances, what they were calling bare metal back then. Everybody's looking at the cloud. And so we took a look at that. And I mean, network latencies, in some cases with hypervisors were as high as 200 or 300 milliseconds. And it was a number of real challenges. And so we knew that we would have to change the way that virtualization works and get into hardware. And so in 2010, 2011, we started to look at how could I offload my network processing, my IO processing to additional hardware. And that's what we delivered our first Nitro card in 2012 and 2013. We actually offloaded all of the processing of network to a Nitro card. And that Nitro card actually had a Annapurna arm chip on it. Our Nitro 1 chip. >> For the offload? >> The offload card, yeah. And so that's when my team started to code for Arm. We started to work on our Linux works for Arm. We actually had to write our own operating system initially 'cause there weren't any operating systems available we could use. And so that's what we started this journey. And over the years, when we saw how well it worked for networking, we said, let's do it for storage as well. And then we said, Hey, we could actually improve security significantly. And by 2017, we'd actually offloaded 100% of everything we did on that server to our offload cards Leaving a 100% of the server available for customers. And we're still actually the only cloud provider that does that today. >> Just to interject, in the data center today, probably 30% of the general purpose cores are used for offloads. You're saying 0% in the cloud. >> On our nitro instances, so every instance we've launched since 2017, our C5. We use 0% of that central core. And you can actually see that in our instance types. If you look at our largest instance type, you can see that we're giving you 96 cores and we're giving you, and our largest instance, 24 terabytes of memory. We're not giving you 23.6 terabytes 'cause we need some. It's all given to you as the customer. >> So much more efficient, >> Much, much more efficient, much better, better price performance as well. But then ultimately those Nitro chips, we went through Nitro 1, Nitro 2, Nitro 3, Nitro 4. We said, Hey, could we build a general purpose server chip? Could we actually bring Arm into the cloud? And in 2018, we launched the A1 instance, which was our Graviton1 instance. And what we didn't tell people at the time is that it was actually the same chip we were using on our network card. So essentially, it was a network card that we were giving to you as a server. But what it did is it sparked the ecosystem. That's why we put it out there. And I remember before launch, some was saying, is this just going to be a university project? Are we going to see people from big universities using Arm in the cloud? Was it really going to take off? And the response was amazing. The ecosystem just grew. We had customers move to it and immediately begin to see improvements. And we knew that a year later, Graviton2 was going to come out. And Graviton2 was just an amazing chip. It continues to see incredible adoption, 40% price performance improvement over other instances. >> So this is worth calling out because I think that example of the network card, I mean, innovation can come from anywhere. This is what Jassy always would say is do the experiments. Think about the impact of what's going on here. You're focused on a mission. Let's get that processing of the lowest cost, pick up some workloads. So you're constantly tinkering with tuning the engine. New discovery comes in. Nitro is born. The chip comes in. But I think the fundamental thing, and I want to get your reaction to this 'cause we've put this out there on our post on Sunday. And I said, in every inflection point, I'm old enough, my birthday was yesterday. I'm old enough to know that. >> David: I saw that. >> I'm old enough to know that in the eighties, the client server shifts. Every inflection point where development changed, the methodology, the mindset or platforms change, all the apps went to the better platform. Who wants to run their application on a slower platform? And so, and those inflects. So now that's happening now, I believe. So you got better performance and I'm imagining that the app developers are coding for it. Take us through how you see that because okay, you're offering up great performance for workloads. Now it's cloud workloads. That's almost all apps. Can you comment on that? >> Well, it has been really interesting to see. I mean, as I said, we were unsure who was going to use it when we initially launched and the adoption has been amazing. Initially, obviously it's always, a lot of the startups, a lot of the more agile companies that can move a lot faster, typically a little bit smaller. They started experimenting, but the data got out there. That 40% price performance was a reality. And not only for specific workloads, it was broadly successful across a number of workloads. And so we actually just had SAP who obviously is an enormous enterprise, supporting enterprises all over the world, announced that they are going to be moving the S/4 HANA Cloud to run on Graviton2. It's just phenomenal. And we've seen enterprises of that scale and game developers, every single vertical looking to move to Graviton2 and get that 40% price performance. >> Now we have to, as analysts, we have to say, okay, how did you get to that 40%? And you have to make some assumptions obviously. And it feels like you still have some dry powder when you looked at Graviton2. I think you were running, I don't know, it's speculated anyway. I don't know if you guys, it's your data, two and a half, 2.5 gigahertz. >> David: Yeah. >> I don't know if we can share what's going on with Graviton3, but my point is you had some dry powder and now with Graviton3, quite a range of performance, 'cause it really depends on the workload. >> David: That's right. >> Maybe you could give some insight as to that. What can you share about how you tuned Graviton3? >> When we look at benchmarking, we don't want to be trying to find that benchmark that's highly tuned and then put out something that is, Hey, this is the absolute best we can get it to and that's 40%. So that 40% is actually just on average. So we just went and ran real world workloads. And we saw some that were 55%. We saw some that were 25. It depends on what it was, but on average, it was around the 35, 45%, and we said 40%. And the great thing about that is customers come back and say, Hey, we saw 40% in this workload. It wasn't that I had to tune it. And so with Graviton3, launching this week. Available in our C7g instance, we said 25%. And that is just a very standard benchmark in what we're seeing. And as we start to see more customer workloads, I think it's going to be incredible to see what that range looks like. Graviton2 for single-threaded applications, it didn't give you that much of a performance. That's what we meant by cloud applications, generally, multi-threaded. In Graviton3, that's no longer the case. So we've had some customers report up to 80% performance improvements of Graviton2 to Graviton3 when the application was more of a single-threaded application. So we started to see. (group chattering) >> You have to keep going, the time to market is compressing. So you have that, go ahead, sorry. >> No, no, I always want to add one thing on the difference between single and multi-threaded applications. A lot of legacy, you're single threaded. So this is kind of an interesting thing. So the mainframe, migration stuff, you start to see that. Is that where that comes in the whole? >> Well, a lot of the legacy apps, but also even some of the new apps, like single threading like video transcoding, for example, is all done on a single core. It's very difficult. I mean, almost impossible to do that multi-threaded way. A lot of the crypto algorithms as well, encryption and cryptography is often single core. So with Graviton3, we've seen a significant performance boost for video encoding, cryptographic algorithms, that sort of thing, which really impacts even the most modern applications. >> So that's an interesting point because now single threaded is where the vertical use cases come in. It's not like more general purpose OS kind of things. >> Yeah, and Graviton has already been very broad. I think we're just knocking down the last few verticals where maybe it didn't support it and now it absolutely does. >> And if an ISV then ports, like an SAP's ports to Graviton, then the customer doesn't see any, I mean, they're going to see the performance difference, but they don't have to think about it. >> David: Yeah. >> They just say, I choose that instance and I'm going to get better price performance. >> Exactly, so we've seen that from our ISVs. We've also been doing that with our AWS services. So services like EMR, RDS, Elastic Cache, it will be moving and making Graviton2 available for customers, which means the customer doesn't have to do the migration at all. It's all done for them. They just pick the instance and get the price performance benefits, and so yeah. >> I think, oh, no, that was serverless. Sorry. >> Well, Lambda actually just did launch on Graviton2. And I think they were talking about a 35% price performance improvement. >> Who was that? >> Lambda, a couple of months ago. >> So what does an ISV have to do to port to Graviton. >> It's relatively straightforward, and this is actually one of the things that has slowed customers down is the, wow, that must be a big migration. And that ecosystem that I spoke about is the important part. And today, with all the Linux operating systems being available for Arm running on Graviton2, with all of the container runtimes being available, and then slowly open source applications in ISV is being available. It's actually really, really easy. And we just ran the Graviton2 four-day challenge. And we did that because we actually had an enterprise migrate one of the largest production applications in just four days. Now, I probably wouldn't recommend that to most enterprises that we see is a little too fast, but they could actually do that. >> But just from a numbers standpoint, that's insanely amazing. I mean, when you think about four days. >> Yeah. >> And when we talked on virtually last year, this year, I can't remember now. You said, we'll just try it. >> David: That's right. >> And see what happens, so I presume a lot of people have tried it. >> Well, that's my advice. It's the unknown, it's the what will it take? So take a single engineer, tell them and give them a time. Say you have one week, get this running on Graviton2, and I think the results are pretty amazing, very surprised. >> We were one of the first, if not the first to say that Arm is going to be dominant in the enterprise. We know it's dominant in the Edge. And when you look at the performance curves and the time to tape out, it's just astounding. And I don't know if people appreciate that relative to the traditional Moore's law curve. I mean, it's a style. And then when you combine the power of the CPU, the GPU, the NPU, kind of what Apple does in the iPhone, it blows away the historical performance curves. And you're on that curve. >> That's right. >> I wonder if you could sort of explain that. >> So with Graviton, we're optimizing just across every single part of AWS. So one of the nice things is we actually own that end-to-end. So when it starts with the early design of Graviton2 and Graviton3, and we obviously working on other chips right now. We're actually using the cloud to do all of the electronic design automation. So we're able to test with AWS how that Graviton3 chip is going to work long before we've even started taping it out. And so those workloads are running on high-frequency CPU's on Graviton. Actually we're using Graviton to build Graviton now in the cloud. The other thing we're doing is we're making sure that the Annapurna team that's building those CPUs is deeply engaged with my team and we're going to ultimately go and build those instances so that when that chip arrives from tapeout. I'm not waiting nine months or two years, like would normally be the case, but I actually had an instance up and running within a week or two on somebody's desk studying to do the integration. And that's something we've optimized significantly to get done. And so it allows us to get that iteration time. It also allows us to be very, very accurate with our tapeouts. We're not having to go back with Graviton. They're all A1 chips. We're not having to go back and do multiple runs of these things because we can do so much validation and performance testing in the cloud ahead of time. >> This is the epiphany of the Arm model. >> It really is. >> It's a standard. When you send it to the fab, they know what's going to work. You hit volume and it's just no fab. >> Well, this is a great thread. We'll stay on this 'cause Adam told us when we met with them for re:Invent that they're seeing a lot more visibility into use cases at the scale. So the scale gives you an advantage on what instances might work. >> And makes the economics works. >> Makes the economics work, hence the timing, the shrinking time to market, not there, but also for the apps. Talk about the scale advantage you guys have. >> Absolutely. I mean, the scale advantage of AWS plays out in a number of ways for our customers. The first thing is being able to deliver highly optimized hardware. So we don't just look at the Graviton3 CPU, you were speaking about the core count and the frequency and Peter spoke about a lot of that in his keynote yesterday. But we look at how does the Graviton3 CPU work with the rest of the instance. What is the right balance between the CPU and memory? The CPU and the Hydro. What's the performance and the drive? We just launched the Nitro SSD, which is now we've actually building our own custom SSDs for Nitro getting better performance, being able to do updates, better security, making it more cloudy. We're just saying, we've been challenged with the SSD in the parts. The other place that scales really helping is in capacity. Being able to make sure that we can absorb things like the COVID spike, or the stuff you see in the financial industry with just enormous demand for compute. We can do that because of our scale. We are able to scale. And the final area is actually in quality because I have such an enormous fleet. I'm actually able to drive down AFR. So annual failure rates, are we well below what the mathematical theoretical tenant or possibility is? So if you look at what's put on that actual sticker on the box that says you should be able to get a full percent AFR. At scale and with focus, we're actually able to get that down to significantly below what the mathematical entitlement was actually be. >> Yeah, it's incredible. I've got a great, and this is the advantage, and that's why I believe anyone who's writing applications that has includes a database, data transfer, any kind of execution of code will use the stack. >> Why would they? Really, why? We've seen this, like you said before, whether it was PC, then the fastest Pentium or somebody. >> Why would you want your app to run slower? >> Unix box, right? ISVS want it to run as fast and as cheaply as possible. Now power plays into it as well. >> Yeah, well, we do have, I agree with what you're saying. We do have a number of customers that are still looking to run on x86, but obviously customers that want windows. Windows isn't available for Arm and so that's a challenge. They'll continue to do that. And you know the way we do look at it is most law kind of died out on us in 2002, 2003. And what I'm hoping is, not necessarily bringing wars a little back, but then we say, let's not accept the 10%, 15% improvement year-over-year. There's absolutely more we can all be doing. And so I'm excited to see where the x86 world's going and they doing a lot of great stuff. Intel Ice Lakes looking amazing. Milan is really great to have an AWS as well. >> Well, I'm thinking it's fair point 'cause we certainly look what Pat's doing it at Intel and he's remaking the company. I've said he's going to follow on the Arm playbook in my mind a little bit, and which is the right thing to do. So competition is a good thing. >> David: Absolutely. >> We're excited for you and a great to see Graviton and you guys have this kind of inflection point. We've been tracking for a while, but now the world's starting to see it. So congratulations to your team. >> David: Thank you. >> Just a couple of things. You guys have some news on instances. Talk about the deprecation issue and how you guys are keeping instances alive real quick. >> Yeah, we're super customer obsessed at Amazon. And so that really drives us. And one of the worst things for us to do is to have to tell a customer that we no longer supporting a service. We recently actually just deprecated the ECG classic network. I'm not sure if you saw that and that's actually off the 10 years of continuing to support it. And the only reason we did it is we have a tiny percentage of customers still using that from back in 2012. But one of the challenges is obviously instance hardware eventually will ultimately time out and fail and have hardware issues as it gets older and older. And so we didn't want to be in a place, in EC2, where we would have to constantly go to customers and say that M1 small, that C3, whatever you were running, it's no longer supported, please move. That's just a text that customers shouldn't have to do. And if they still getting value out of an older instance, let them keep using it. So we actually just announced at re:Invent, in my keynote on Tuesday, the longevity support for EC2 instances, which means we will never come back to you again and ask you to please get off an instance, because we can actually emulate all those instances on our Nitro system. And so all of these instances are starting to migrate to Nitro. You're getting all the benefits of Nitro for now some of our older zen instances, but also you don't have to worry about that work. That's just not something you need to do to get off in all the instance. >> That's great. That's a great test service. Stay on as long as you want. When you're ready to move, move. Okay, final question for you. I know we've got time, I want to get this in. The global network, you guys are known for AWS cloud WAN serve. Gives you updates on what's going on with that. >> So Werner just announced that in his keynote and over the last two to three years or so, we've seen a lot of customers starting to use the AWS backbone, which is extensive. I mean, you've seen the slides in Werner's keynote. It really does span the world. I think it's probably one of the largest networks out there. Customers starting to use that for actually their branch office communication. So instead of going and provisioning the own international MPLS networks and that sort of thing, they say, let me onboard to AWS with VPN or direct connect, and I can actually run the AWS backbone around the world. Now doing that actually has some complexity. You got to think about transit gateways. You got to think about those inter-region peering. And AWS cloud when takes all of that complexity away, you essentially create a cloud WAN, connecting to it to VPN or direct connect, and you can even go and actually set up network segments. So essentially VLANs for different parts of the organization. So super excited to get out that out of there. >> So the ease of use is the key there. >> Massively easy to use. and we have 26 SD-WAN partners. We even partnering with folks like Verizon and Swisscom in Switzerland to telco to actually allow them to use it for their customers as well. >> We'll probably use your service someday when we have a global rollout date. >> Let's do that, CUBE Global. And then the other was the M1 EC2 instance, which got a lot of applause. >> David: Absolutely. >> M1, I think it was based on A15. >> Yeah, that's for Mac. We've got to be careful 'cause M1 is our first instance as well. >> Yeah right, it's a little confusion there. >> So it's a Mac. The EC2 Mac is with M1 silicon from Apple, which super excited to put out there. >> Awesome. >> David Brown, great to see you in person. Congratulations to you and the team and all the work you guys have done over the years. And now that people starting to realize the cloud platform, the compute just gets better and better. It's a key part of the system. >> Thanks John, it's great to be here. >> Thanks for sharing. >> The SiliconANGLE is here. We're talking about custom silicon here on AWS. I'm John Furrier with Dave Vellante. You're watching theCUBE. The global leader in tech coverage. We'll be right back with more covers from re:Invent after this break. (bright music)

(cheery music) >> Thanks, Adam. Thanks for everyone in the studio. Dave, we've got some great main stage CUBE interviews. Normally we'll sit at the desk, and do a remote, but since it's a virtual event, and a physical event, it's a hybrid event. We've got two amazing Google leaders to talk with us. I had a chance to sit down with Amol who was gone yesterday during our breaking news segment. They had the big news. We had two great guests, Amol Phadke. He's our first interview. He's the head of Google's telecom industry. Again, he came in, broke into our segment yesterday with breaking news. Obviously released with Ericsson, and the O-RAN Alliance. I had a great chance to chat with him. A wide ranging conversation for 13 minutes. Enjoy my interview with Amol, right now. (cheery music) Well welcome to the CUBE's coverage for Mobile World Congress, 2021. I'm John Furrier, your host of the CUBE. We're here in person as well as remote. It's a hybrid event. We're on the ground at Mobile World Congress, bringing all the action here. We're remote with Amol Phadke, who's the Managing Director of the Telecom Industry Solutions team at Google Cloud, a big leader, and driving a lot of the change. Amol, thank you for coming on theCUBE here in the hybrid event from Mobile World Congress. >> Thank you, John. Thank you, John. Thank you for having me, So, hybrid event, which means it's in person, we're on the floor, as well as doing remote interviews and people are virtual. This is the new normal. Kind of highlights where we are in this telecom world, because the last time, Mobile World Congress actually had a physical event was winter of 2019. A ton has changed in the industry. Look at the momentum at the Edge. Hybrid cloud is now standard. Multi-cloud is being set up as we speak. This is all now the new normal, what is your take? And so it's pretty active in your industry. Tell us your opinion. >> Yes, John I mean the last two years have been seismic to say the least, right? I mean, in terms of the change that the CSP industries had had to do. You know, John, in the last two years, the importance of a CSP infrastructure has never become so important, right? The infrastructure is paramount. I'm talking to you remotely over the CSP infrastructure right now, and everything that we are doing in the last two years, whether it's working, or studying, or entertaining ourselves, all on that CSP infrastructure. So from that perspective, they are really becoming a critical national global information fabric on which the society is actually depending on. And that we see at Google as well, in the sense that we have seen up to 60% increase in demand, John, in the last two years, for that infrastructure. And then when we look at the industry itself, unfortunately all of that huge demand is not translating into revenue, because as an industry, the revenue is still flat-lining. In fact, the forecasted revenue for globally, for all the industry over the next 12 months is three to five per cent negative on revenue, right? So one starts to think, how come there is so much demand over the last two years, post-pandemic, and that's not translating to revenue? Having said that, the other thing that's happening is this demand is driving significant CapEx and OPEX investments in the infrastructure, as much as eight to $900 billion over the next decade is going to get spent in this infrastructure, from our perspective, Which means it's really a perfect storm. John, We have massive demand, massive need to invest to meet that demand, yet not translating to revenue, and the crux of all this is customer experience, because ultimately all of that translates into not having that kind of radically disruptive or transformational customer experience, right? So that's a backdrop that we find ourselves in the industry, and that really sets the stage for us to look at these challenges in terms of how does the CSP industry as a whole, grow top line, radically transform CSPCO, at the same time, reinventing the customer experience and finding those capital efficiencies. It's almost an impossible problem to find solution. >> It's a perfect storm. The waves are kind of coming together to form one big wave. You mentioned CapEx and OPEX. That's obviously changing the investments of their post-pandemic growth, and change in user behavior and expectations. The modern applications are being built on top of the infrastructure, that's changing. All of this is being driven by Cloud Native, and that's clear. You're seeing a lot more open kind of approaches, IT and OT coming together, whatever you want to do, this is just, it's a collision, right? It's a collision of many things. And this positive innovation coming out of it. So I have to ask you, what are you seeing as a solution that are showing the most promise for these telco industry leaders, because they're digitally transforming, so they got to re-factor their platforms while enabling innovation, which is a key growth for the revenue. >> Yes. So John, from a solution standpoint, what we actually did first and foremost as Google Cloud, was look at ourselves. So just like the transformation we just talked about in the CSP industry, we are seeing Google being transformed over the last two decades or so, right. And it's important to understand that there's a lot Google data over the last two decades that we can actually not externalize all of that innovation, all of that open source, all of that multicloud, was originally built for all the Google applications that all of us use daily, whether it's YouTube, or email or maps, you know. Same infrastructure, same open source, same multicloud. And we decided to sort of use the same paradigm to build the telecom solutions that I'm going to talk about next, right. So that's important to bear in mind, that those assets were there, and we wanted to externalize those assets, right. There are really four big solutions that are resonating really well with our CSP partners, John. You know, number one to your point, is how can they monetize the Edge? All of this happens at the Edge. All of this gets converged at the Edge. We believe with 5G acting as the brilliant catalyst to really drive this Edge deployment. CSPs would be in a very strong position, partnering with Cloud players like ourselves to drive growth, not just for their top line, but also to add value to the actual end enterprises that are seeking to use that Edge. Let me give you a couple of examples. We've been working with industries like retail and manufacturing, to create end solutions in a post-pandemic world. Solutions like contact-less shopping, or visual inspection of an assembly line in a manufacturing plant, without the need for having a human there, because of the digitalization of workforce. Which meant these kinds of solutions, can actually work well at the Edge driven by 5G. But of course they can't be done in isolation. So what we do is we partner with CSPs. We bring our set of solutions, and we actually launch in December 30 partners that are already on our Google Cloud Solutions. And then we partner with the CSPs based on our infrastructure, and their infrastructure to ultimately bring this all to life at the end customer, which often tends to be an enterprise, whether it's a manufacturing, plant, or a retail chain. >> Yeah, you guys got some great examples there. I love that Edge story. I think it's huge. I think it's only going to get bigger. I got to ask you while I got you here, because again, you're in the industry, you're the managing director, so you have to oversee this whole telecom industry. But it's bigger, it's beyond Telecom, where it's now Telecom's just one other Edge network, piece of the pie of the surety computing, as we say. So I got to ask you, one of the big things that Google brings to the table is the developer mojo, and opensource, and scale obviously. Scale's unprecedented, everyone knows that. But ecosystems are super important, and Telco's kind of really aren't good at that, right? So, you know, the Telco ecosystem was, I mean, okay, I'd say, okay, but mostly driven by carriers and moving bits from point A to point B. But now you've got a developer mindset, public cloud, developer ecosystem. How is this changing the landscape of the CSPs and how is it changing this cloud service provider's ability to execute, because that's the key in this new world? What's your opinion? >> Absolutely, John. So, there are two things, there are two dimensions to look at. One is when we came to market a couple of years ago with AnToks, we recognized exactly what you said, John, which is the world is moving to multi-cloud, hybrid cloud. We needed to provide a common platform that the developer community can utilize through microservices and API. And that platform had to by definition, work not just from Google Cloud, but any cloud. It could work on any public cloud, can work on CSP's private cloud. And of course, supports on some Google Cloud, right? The reason was, once you deploy and cause, once as a seamless application development platform, you could put all kinds of developer apps on top. So I just talked about 5G Edge John, a minute ago, those apps can sit on Antoks, but at the same time, IT to your point, John, IT apps could also sit on the same AnToks paradigm, and network apps. So as networks start becoming Cloud Native, whether it's SRAN, whether it's O-Ran, whether it's 5G core, same principle. And that's why we believe when we partner with CSPs, we are saying, "Hey, you give this AnToks to an ecosystem of community, whether that community is network, whether that community is IT, whether the communities Edge apps, all of those can reside seamlessly on this sort of AnToks fabric, John. >> Yeah, and that's going to set the table for multicloud, which is basically cloud words for multi-vendor, multi app. Amol, I've got to ask you while I have you here, first of all, thank you for coming on and sharing your insights. It's really great industry perspective. And obviously Google Cloud's got huge scale, and great leadership. And again, you know, the big, cloud players are moving in and helping out, and enabling a lot of value. I got to ask you, if you don't mind sharing, if someone asked you, "Amol, tell me about the impact that public cloud is having on the Telco industry." What would you say? What's the answer to that? Because a lot of people are like, okay, public cloud, I get it. I know what it looks like, but now everyone's knows it's going hybrid. So everyone will ask you the question, "What is public cloud doing for the telecom sector?" >> Yeah, I think it's doing three things, John, and great question by the way. Number one, we are actually providing unprecedented amount of insights on data that the CSPs traditionally already had, but have never looked at it from the angle we have looked at it. Whether that insights are at the network layer, whether those insights are to personalize customer experiences on the front-end systems. Or whether those insights are to drive care solutions in contact centers, and so on, and so forth. So it's a massive uplift of customer experience that we can help with, right. So that's a very important point, because we do have a significant amount of leadership, John at Google Cloud on analytics and data and insights, right? So, and we offer those roads to these people. Number two, is really what I talked about, which is helping them build an ecosystem, because let's take retail as an example. As a minimum, there are five constituents in that ecosystem, John. There is a CSP, there is Google Cloud, there's an actual retail store. There is a hardware supplier, there's a software developer. All of them as a minimum, have to work together to build that ecosystem, which is where we give those solutions, right? So that's the second part. And then the third part is, as they move towards Cloud Native, we are really helping them change their business model to become a DevOps, a Cloud Native mindset, not just a Cloud Native network or IP. But a Cloud Native mindset that creates unparalleled agility and flexibility in how they work as a business. So those are the three things I would say, as a response to that question. >> And also the retail's a great vertical for Google to go in there, given the Amazon fear out there. People want this for certainly low hanging fruit. I think the DevOps piece is going to be a big, winning opportunity to see how the developers get driven into the landscape. I think that's a huge point. Amol, that's really great insight. A final question for you, while I got you here. If someone says, "Hey, what's happened in the industry since 2019?" Last time we had Mobile World Congress, they were talking speeds and feeds. Now the world has changed. We're coming out of the pandemic. California is opening up. There's going to be a physical event. The world's going hybrid, certainly on the event, and certainly cloud. What's different in the telecom industry, from, you know, many, many months ago, over a year and a half ago, from 2019? >> I would say primarily, it's the adoption of digital everywhere, which previously, you know, there were all these inhibitions and oh, would this work? Would my customer systems become fully digital? Would I be able to offer AR VR experiences? Ah, that's a futuristic thing, you know. And suddenly the pandemic has created this acceleration that says, "Oh, even post-pandemic, half my customers are always going to talk to me, via our digital channel only." Which means the way they experience us, has to be through these new experiences whether it's AR VR, whether it's some other thing or applications. So that has been accelerated John, and the CSPs have therefore really started to go to the application, and to the services. Which is why you are seeing less on, you know, speeds and feeds because 5G is here, 5G's been deployed. Now, how do we monetize 5G? How can we leverage that biggest number? So that's the biggest- >> There's down stack, and then there's a top of the stack for applications. And certainly there's a lot of assets in the telecom landscape, a lot of value, a lot of refactoring going on, and new opportunities that are out there. Great, great conversation. Well, thank you, Amol Phadka, Managing Director, Telecom Industry Solutions. Thanks for comin' on the CUBE, appreciate it. >> Thank you, John. Thank you having me. >> Okay, Mobile World Congress here, in person, and hybrid, and remote. I'm John Furrier, host of theCUBE. Thank you for watching. We are here in person at the Cloud City Expo Community Area. Thanks for watching. Okay, that was us. That was me, online. Now, I'm here in person, as you can see Dave. That's a lot of fun. I love doing those interviews. So we had a chance to grab Google's top people when we could. They're not here, obviously. Amazon Web Services, Microsoft, and Google, the three hyperscalers, Dave, didn't make it out here. They didn't have a booth, but we had a chance to grab them. And that was head of the industry marketing, and I mean the industry group. So he's like the managing door. He runs the business side. >> It's an important sector for Google. You know, Amazon was really first, with that push into telco. Thomas Curran last March, laid out Google strategy for Telco. It's a huge sector. They know it. They understand how the cloud can disrupt it, and play a massive role there. >> Yeah. >> And Google, of course. >> They're not going to object to the public cloud narrative that Danielle Royston- >> No. >> I think they like it open source, Android coming to telco. Who knows what it's going to look like? >> That's what we call digital- >> So the next interview I did was with Shailesh Shukla. He is the Senior Vice-president. He's the Senior Leader at Google Cloud for Networking. And if you know, Google, Dave, Google's networking is really well known in the industry for being really awesome, because they power obviously Google Search, and a variety of other things. They pioneered the concept of SRE, Site Reliability Engineer, which is now a de facto position for DevOps, which is a cloud now persona inside almost every company, and certainly a very important position. And so- >> Probably the biggest global network, right? Undersea cables, and- >> I mean, Microsoft's got a big hyper-scale, because they've had MSN, and bunch of other stuff, infrastructure globally. But Amazon, Google and Microsoft all have massive scale, and Google again, very well engineered. They're total, and they're as we know, I live in Palo Alto, so I can attest that they're very strong. So this next interview is really from a networking perspective, because as infrastructure, as code gets more prolific and more penetrated, it's going to be programmable. And that's really going to be a key new enabler. So let's hear from Shailesh, Head of Networking at Google Cloud, and my interview with him. (cheery music) Welcome to theCUBE's coverage of Mobile World Congress, 2021. We are here in person in Barcelona, as well as remote. It's a hybrid event. You're going to have the physical space, in Barcelona for the first time, since 2019, and virtual worlds connecting. I've got a great guest here from Google, Shailesh Shukla, Vice-president and General Manager of the Networking Team, Google Cloud. Shailesh, it's great to see you. Thank you for coming on theCUBE for the special presentation from Mobile World Congress. Obviously, the Edge networking core, Edge human devices, all coming together. Thanks for coming on. >> Thank you so much, John. It's great to see you again. And it's always a pleasure talking to theCUBE. And I want to say hello to everybody, from, you know, in Mobile World Congress. >> Yeah, and people don't know your background. You have a great history in networking. You've been there, many ways of innovation. You've been part of directly, big companies that were now known. Big names are all there. But now we haven't had a Mobile World Congress, since 2019. Think about that. That's, you know, many months, 20 something months gone by, since the world has changed in telco. I got to ask you, what is the disruption happening? Because think about that. Since 2019, a lot's changed in telco. Cloud-scale has happened. You've got the Edge developing. It's IT like now. What's your take? Shailesh, tell us. >> Yeah, John, as you correctly pointed out the last 18 months have been very difficult. And you know, I'll acknowledge that right up front, for a number of people around the world. I empathize with that. Now in the telecom, and kind of the broader Edge world, I would say that the last 18, 24 months have actually been transformative. O-RAN, it turns out was a very interesting sort of, you know, driver of completely new ways of both living, as well as working, right, as we all have experienced. I don't think that I've had a chance to see you live in 24 months. So, what we are seeing is the following. Number one, a number of telecom carriers around the world have started the investment process for 5G, right, and deployment process. And that actually changes the game, as you know, due to latency, due to all of the capabilities around kind of incalculable bandwidth, right. Much lower latency, as well as, much higher kind of enterprise oriented capabilities, right? So network's licensing, as an example, quality of service, you know, by a traffic type, and for a given enterprise. So that's number one. Number two, I would say that the cloud is becoming a lot more kind of mainstream in the world, broader world of telecom. What we are seeing is an incredible amount of partnerships between telecom carriers and cloud providers, right? So instead of thinking of those two as separate universes, those are starting to come together. So I believe that over a period of time, you will see the notion of kind of Cloud Native capability for both the IT side of the house, as well as the network side of the house is becoming, you know, kind of mainstream, right. And then the third thing is that increasingly it's a lot more about enabling new markets, new applications, in the enterprise world, right. So certainly it opens up a new kind of revenue stream for service providers and carriers around the world. But it also does something unique, which is brings together the cloud capabilities right, around elasticity, flexibility, intelligence, and so on, with the enterprise customer base that most of the cloud providers already have. And with the combination of 5G, brings it to the telecom world. And those, you know, I started to call it, as a kind of the triad, right? The triad of an enterprise, the telecom service provider, and the cloud provider, all working together to solve real business problems. >> Yeah, and it's totally a great call out there on the pandemic. I think the pandemic has shown us, coming out of it now, that cloud-scale matters. And you look at all the successes between work, play, and how we've all kind of adjusted, the cloud technologies were a big part of that, those solutions that got us through it. Now you've got the Edge developing with 5G. And I got to ask you this question, because when we have CUBE interviews with all the leaders of engineering teams, whether it's in the industry, or customers in the enterprise, and even in the telcos, the modern application teams have end-to-end visibility into the workload. You're starting to see more and more of that. You starting to see more open source in everything, right. So okay, I buy that. You got an SRE on the team, you got some modern developers, you're shifting left, you've got Devs set up. All good, all cloud. However, you're a networking guy. You know this. Routing packets across multiple networks is difficult. So if you're going to have end-to-end visibility, you got to have end-to-end intelligence on the networking. How is that being solved? Because this is a critical discussion here at Mobile World Congress. Okay, I buy Cloud Native, I buy observability, I buy open source, but I got to have end-to-end visibility for security, and workload management and managing all the data. What's the answer on the network side? >> Yeah, so that's a great question. And the simple way to think about this, is first and foremost, you need kind of global infrastructure, right? So that's a given, and of course, you know, Google with its kind of global infrastructure, and some of the largest networks in the world, we have that present, right. So that's important. Second is, to be able to abstract a way that underlying infrastructure, and make it available to applications, to a set of APIs. Right, so I'll give an analogy here. Just as you know, say 10 years ago, around 10 years ago, Android came into the market from Google, in the following way. What it did, was that it abstracted away the underlying devices with a simple kind of layer on top of operating system, which exposed APIs northbound. So then application developers can write new applications. And that actually unleashed, you know, a ton of kind of creativity right, around the world. And that's precisely what we believe is kind of the next step, as you said, on an end-to-end observability basis, right? If you can do an abstraction away from all of the underlying kind of core infrastructure, provide the right APIs, the right kind of information around observability, around telemetric, instead of making, you know, cloud and the infrastructure, the black box. Make it open, make it kind of visible to the applications. Bring that to the applications, and let the thousand flowers bloom, right? The creativity in each vertical area is so significant, because there are independent software vendors. There are systems integrators. There are individual developers. So one of the things that we are doing right now, is utilizing open source technologies, such as Kubernetes, right? Which is something that Google actually brought into the market. And it has become kind of the de facto standard for all of the container and modernization of applications. So by leveraging those open technologies, creating this common control plane, exposing APIs, right, for everything from application development, to observability, you certainly have the ability to solve business problems through a large number of entities in the systems integrator and the ISC and the developer community. So that's the approach that we are taking, John. >> I love the Android analogy of the abstraction layer, because at that time, the iPhone was closed. It still is. And they got their own little strategy there. Android went the other way. They went open, went open abstraction. Now abstraction layers are good. And now I want to get your thoughts on this, because anyone in operating systems knows abstractions are great for innovation. How does that apply to the real world on telco? Because I get how it could add some programmability in there. I get the control plane piece. Putting it into the operator's hands, how do you guys see, and how do you guys talk about the Edge service offering? What does it mean for the telco? Because if they get this right, this is going to be in telco cloud developer play. It's going to be a telco cloud ecosystem play. It's an opportunity for a new kind of telco system. How do you see that rolling out in real world? >> Great question, John. So the way I look at it, actually even we should take a step back, right? So the confluence of 5G, the kind of cloud capabilities and the Edge is, you know, very clear to me that it's going to unleash a significant amount of innovation. We are in early stages, no question, but it's going to drive innovation. So one almost has to start by saying what exactly is Edge, right? So the way I look at it, is that the Edge can be a continuum all the way from kind of an IOT device in automobiles, right? Or an enterprise Edge, like a factory location, or a retail store, or kind of a bank branch. To the telecom Edge, which is where the service providers have, not only their points of presence, and central offices, but increasingly a very large amount of intelligent RAN sites as well, right. And then the, kind of public cloud Edge, right. Where, for example, Google has, you know, 25 plus kind of regions around the world. 144, you know, PoPS, lots of CDN locations. We have, you know, few thousand nodes deployed deep inside service provider networks for caching of content, and so on. So if you think about these as different places in the network that you can deploy, compute, storage and intelligence act, right. And do that in a smart way, right? For example, if you were to run the learning algorithms in the cloud with its flexibility and elasticity, and run the inferencing at the Edge, very Edge, at the point of sort of a sale, or a point, a very consumer standing. Now you suddenly have the ability to create a variety of Edge applications. So going back to the new question, what have we seen, right? So what we are seeing, is depending on the vertical, there are different types of Edge applications, okay. So let's take a few examples. And I'll give you some, a favorite example of mine, which is in the sports arena, right? So in baseball, when you are in a stadium, and soon there are people sort of starting to be in stadiums, right? And a pitcher is throwing the pitch, right, the trajectory of the ball, the speed of the pitch, where the batter is, you know, what the strike zone is, and all of these things, if they can be in a stadium in real time, analyzed, and presented to the consumer as additional intelligence, and additional insight, suddenly it actually creates kind of a immersive experience. Even though you may be in the stadium, looking at the real thing, you are also seeing an immersive experience. And of course at home, you get a completely different experience, right? So the idea is that in sports, in media and entertainment, the power of Edge compute, and the power of AI ML, right, can be utilized to create completely new immersive experiences. Similarly, in a factory or an automotive environment, you have the ability to use AI ML, and the power of the Edge and 5G coming together, to find where the defects are, in a manufacturing environment, right? So every vertical, what we're finding is, there are very specific applications, which you can call as kind of killer apps, right in the Edge world, that over time will become prevalent and mainstream. And they will drive the innovation. They will drive deployment, and they also will drive ultimately, kind of the economics of all of this. >> You're laying out, essentially the role of the public cloud in the telco market. I'd love to get your thoughts, because a lot of people are saying, "Oh, the cloud, it's all Edge now. It's going back to on-premises." This is not the case. I mean, I've been really vocal on this. The public cloud and cloud operations is now the new normal. So developers are there. So I want you to explain real quick, the role of the public cloud in the telecom market and the Telecom Edge, because now they're working together. You've got abstraction, you mentioned that Android-like environment coming, there's going to be an Android-like effect, that abstraction. You got O-RAN out there, creating these connection points, for interoperability, for radio signals, and the End Transceivers or the Edge of the radios. All of this is happening. How is Google powering this? What is the role of public cloud in this? >> Yeah, so let me first talk about genetically the role of public cloud. Then I'll talk about Google, okay, in particular. So, if at the end of the day, the goal here is to create applications in a very simple and efficient manner, right? So what do you like, if you look for that as the goal, then the public cloud brings, you know, three fundamental things. Number one, is what I would call as elasticity and flexibility, right? So why is this important? Because as we discussed earlier, Edge is not one place, it's a variety of kind of different locations. If there is a mechanism to create this common control plane, and have the ability to kind of have elastic compute, elastic networking, elastic storage, and have this deployed in a flexible manner. Literally if you think, think about it like an effortless Edge is what we are starting to call it. You can move workload and capability, and run it precisely where it makes sense, right? Like I said, earlier, training and learning algorithms in the deep cloud. Inferencing, at the very edge, right? So if you can make that decision, then it becomes very powerful. So that's the first point, you know, elasticity and flexibility that cloud can bring. Second is, intelligence. The whole notion of leveraging the power of data, and the power of AI and ML is extremely crucial for creation of new services. So that's something that the public cloud brings. And the third is this notion of, write once, deploy anywhere, right? This notion of kind of a full stack capability that when open, kind of developer ecosystem can be brought in, right? Like we talked about Kubernetes earlier. So if there's a way in which you can bring in those developer and ISV ecosystem, which is already present in the world of public cloud, that's something that is the third thing that public cloud brings. And Google strategy very simply, is to play on all of these, right? Because we, you know, Google has incredibly rich deployment experience around the world for some of the largest services on the planet, right? With some of the biggest infrastructure in the networking world. Second, is we have a very open and flexible approach, right? So open as you know, we not only leverage kind of the Kubernetes environment, but also there are many other areas, Key Native, and so on where Google has brought a lot of open kind of capabilities to the broader market. And the third, is the enablement of the ecosystem. So last year we actually announced 200 applications, you know, from 30 ISVs in multiple verticals that we're now going to be deployed on Google Cloud, in order to solve specific business pain points, right. And building out that ecosystem, working with telecom service providers, with systems integrators, with equipment players, is the way that we believe Google Cloud can make a difference in this world of developing Edge applications. We are seeing great traction, John, you know, whether it is in the carrier world. Carrier such as Orange, Telecom Italia, TELUS, SK Telecom, Vodafone. These have all publicly announced their work with Google Cloud, leveraging the power of data, analytics, AI ML, and our very flexible infrastructure. And then a variety of kind of partners and OEM players, in the industry. As an example, Nokia, right, Amdocs, and Netcracker, and many others. So we are really excited in the traction that we are getting. And we believe that public cloud is going to be a key part of the evolution of the telecom industry. >> Shailesh, it's great to have you on. Shailesh Shukla, VP and GM of Networking at Google Cloud. And I would just add to that final point there, that open and this Android-like open environment is going to create a thousand flowers to bloom. Those are new applications, new modern applications, new companies, a new ecosystem in the Telco Cloud. So congratulations. Thanks for coming on and sharing your insights. Google Cloud, you guys are about the data, and being open. Thanks for comin' on. >> Thank you, John. Good to talk to you. >> Okay, so keeps coverage of Mobile World Congress. Google Cloud, featured interview here on theCUBE. Really a big part of the public cloud is going to be a big driver. Call it public cloud, hybrid cloud, whatever you want to call it. It's the cloud, cloud and Edge with 5G, making a big difference and changing the landscape, and trying innovation for the telco space. I'm John Furrier, your CUBE host. Thanks for watching. Okay, Dave, that's the Google support. They are obviously singing the same song as Danielle Royston, every vertical. >> Two great interviews, John. Really nice job. We can see the tech. The strategy is becoming more clear. You know, one of the big four. >> Yeah, I just love, these guys are so smart. Every vertical is going to be impacted by elastic infrastructure, AI, machine learning, and this new code deployment, write once, deploy anywhere. That's theCUBE. We love being here it's a cloud show now. Mobile World Congress, back to the studio for more awesome Cloud City content.

(bright music) >> Announcer: From around the globe, it's theCUBE, with digital coverage of AWS re:Invent 2020. Special coverage sponsored by AWS Global Partner Network. >> Okay, welcome back everyone to theCUBE Virtual Experience here for re:Invent coverage 2020 virtual. Normally we're in person doing interviews face to face, but we're remote this year because of the pandemic. We're here for the APN partner experience, kickoff coverage with two great guests, Rima Olinger, of global lead for VMware cloud on AWS. And Aarthi Raju, Senior Manager Solutions Architecture for Amazon Web Services. Thanks for coming on, appreciate it. >> Good to be with you John, thank you. >> So I got, want to get it out there this partner network experience, it's really about the ecosystem. And VMware has been one of the biggest success stories. They've been around for a long time, and not one of the earliest ecosystem partners, but a big success. 2016, when that announcement happened, a lot of people were like, whoa, we VMware is giving into Amazon. And Amazon was like, no, that's not how it works. So turns out everyone was been proven wrong, it's been hugely successful beneficial to both. What's the momentum, share an update this year on the AWS VMware momentum. >> So John, as you know, we're into our third anniversary, and the relationship cannot be any stronger. We see customers are leaning into the service very heavily. We see great adoption across multiple industries. As some data points for you, if we look at October of this year to October prior year, we're seeing the number of active nodes, or the number of consuming host and active VMS, nearly doubled year over year. we also continue to see greater partner interest in the solution, we have over 300 ISVs that have validated the services on VMC. And we see over 600 plus partners that continue to take the competencies and build practices around it. So the momentum is very strong, for years still today. >> One of the comments I made when the naysayers were like kind of pooh-poohing the deal, I was like, no, no, the cloud growth is going to be a factor at that time, then, the trendy thing was software's eating the world, was a big trend there. If you look at the growth of cloud scale, and software innovation, and the operating side of it, 'cause VMware runs IT, they let operators running IT. There's no conflict because Amazon's growing and now the operator roles growing and changing. So you have two dynamics going on. I think this is a really nuanced point for the VMware, AWS relationship around, how they both fit together. Because it's a win win better together scenario, and it is on AWS, which is a distinction. Can you guys share your reaction to kind of that dynamic of operating software at scale, and how this translates for customers? >> Absolutely, we see a lot of benefits that this service is bringing to the customers. Because what it's doing is providing them with this consistent infrastructure and operations across hybrid cloud environments. And in this way, they have the choice of where to place their applications on-prem or in the cloud, specifically. And this is one of the reasons why AWS is a VMware's preferred cloud provider for all vSphere workloads. We see the customers gravitate towards it and be receptive to it specifically because they say I accelerate my path towards migrating and modernizing my application. It provides me with consistent as I mentioned, operations and infrastructure. And it also helps them with factoring, and helps us scale their business and very fast, very seamless fashion. Aarthi what is your perspective, maybe additional things. >> Yeah. >> Yeah, from a technical innovation perspective, the momentum, John has been very strong, especially, listening to what customers have been asking us the past couple of years. 2020 has been a big year for us in terms of launching some giant innovations. A couple of things to call out is, we launched the VMware Transit Connect. This was announced during VMworld this year and customers have been telling us, hey, we are migrating workloads from on premises to the cloud, we need a simplified way of connecting all these resources on-prem resources, resources on VMware cloud on AWS, and their AWS native resources as well. So, the VMware Transit Connect, uses the AWS transit gateway that we launched at re:Invent two years back to provide that simplified connectivity model for our customers. The next big thing this year was, we introduced a new instance type i3en.metal, So customers have been telling us they want denser nodes for especially storage heavy workload. So we launched this i3en, that comes with approximately, like 45 terabytes of storage per node. So that's a lot of storage for individual nodes. So customers have been taking advantage of these dense nodes as well. There was other areas that we kind of focused on from a lower entry point for our customers. When we initially started the service, John, you know that we had, the minimum entry point as four nodes, we've scaled that down to three, and now we've come to two nodes, giving the same production SLA for customers. The other big launch this year was the acquisition of Datrium by VMware and how we introduce the VMware cloud disaster recovery. Datrium uses the eight native AWS services like S3 and EC2, providing customers this low cost TR options. We're talking about the APN here and for partners, we launched the VMware cloud Director Service, which delivers multi-tenancy to our managed service providers, so that they can cater to small, to medium sized enterprises. >> What are some of the other use cases that are the key in these migrations, because this becomes a big benefit we're hearing, certainly, during the partner day, here at re:Invent, is, migration, cloud SaaSification, getting to a SaaS, but not losing the business model. Either was on premises or born in the cloud, this done new operating models, the key thing, what are some of the key use cases for partners? >> The most widely adopted use case that John, which you rightfully touched on, is really the cloud migration. We see around 41% of customers use the service just for cloud migrations. Now, this could be an application migration, like SAP, SQL server or Oracle Applications, or it could be a complete data center evacuation. And we see that with some customers who have a cloud mandate, or they have refresh cycles that are coming up, or maybe they're in a colo, and they're not happy with their SLA. I could use the example of William Hill, is one of the customers largest betting and gaming companies that are in the UK. And what's the use case was, a combination of a data center extension as well as a capacity expansion specifically. And what William Hill was able to do is, move 800 on-premise servers, and they decommission them in the first 12 months. And they also migrated 3000 VM. So that is cloud migrations is a big use case. The second big use case, as I mentioned earlier, is the data center extension that includes also VDI, the combination of both is around 42% of the use cases, with around 26%, I would say for data center extension and 16% for VDI. Why, customers want to expand their footprint, they want to go to a new region, and they want to meet on demand, cyclical capacity needs, or sometimes temporary needs for some events or some seasonal spikes. So we see that as a second big use case. A third one equally important, tend to be disaster recovery. Now, this is either to augment an existing DR. Replace a DR that is already in place, or start a new DR, and that constitutes around 17% of the use cases that we see. Because customers want to reduce their DR, avert some cost by moving to the cloud. And one example that comes to mind is Pennsylvania Lumbers Men's Mutual Insurance, it was a DR use Case. They worked with an external storage partner of ours faction in order to put that in place. So overall a great use cases across the board. And I know a big one is application modernization, Aarthi, I know you work with your teams on that, if there's any feedback from you on that. >> Yeah, the next generation applications or application modernization comes a lot. We talk to like AWS customers who are migrating from on-premises to the cloud using VMware cloud on AWS. And three or four years back as we were building the service and architecting, one thing was very evident, like we wanted to make sure that as we were building the service, we wanted to ensure that customers can take advantage of the native AWS services. We've got 175 plus services and new services launching at re:Invent, So we wanted to make sure that there is this, seamless mechanism and seamless path for customers to modernize using native AWS services. So what we've done as part of like onboarding for customers and as customers built on VMware cloud on AWS, is provide them both the network path and data path. So they can as your into the same availability zone or region, they're like, hey, I can use S3 for backups. I can use EFS, for file shares, etcetera. So we're seeing a wide range of next generation application use cases that customers are building on. >> Why would I get at the reasons why customers are continuing to adopt VMware cloud on AWS? Can you guys share an update, I'll show you the obvious reasons, the beginning was nice strategy for VMware, it's proven to be clear. But where's the innovation coming from? What's the key drivers for the adoption of VMware cloud on AWS? >> So one of the key patterns that we are seeing is, customers who used to be risk averse, customers will be invested a lot in VMware. And at the point, they did not want to move their workloads or applications to the cloud because of the risk involved, or sometimes they didn't want to refactor, or they were worried about the investment in tools, resources, they tend to gravitate towards this solution. The fact that you could provide your customers with this consistent infrastructure and operations across on premise, as well as on the cloud environment. The fact that you do not need to do an application refactoring. You could optimize your workload placement, based on your business needs, you could move your workloads bidirectionally, you could either leave it on-prem, or move it to the cloud, and vice versa. We've also noticed that there is a lower TCO associated with the use of the service. We know from a study that VMware commissioned Forrester in 2019, for that study, that 59%, there is a recurring savings in terms of infrastructure, and operational savings that is related to that. Customers tell us that, this consistency in infrastructure is translating it, into zero refactoring. This consistency in operations, is leading them to use their existing skill sets. And with the ability to relocate the workload skill into the environment that best suits them, that is providing customers with maximum flexibility. So I would say it is delivering on the promise of accelerating the migration and the modernization of our customers applications so that they can continue to respond to their business needs and continue to be competitive in the marketplace. >> Aarthi I want you to weigh in and get reaction to that. Because again, I've talked publicly and also privately with Ragu, for instance, at VMware, when this was all going down. It's a joint integration, so there's a lot of things going on under the hood that are important, what are the most important things that people should pay attention to around this partnership? Could you share your opinion? >> Yeah, sure, John. So one of the most common questions that we get from customers is, hey, this is giant integration, we can take use of make use of native AWS services, but what are some of the use cases that we should be targeting, right? As we talk to customers, some of the common use cases to think about is, it also depends on the audience. Remember, admin scoring example, who might not be familiar with the AWS side of services, they can start with something simple like backing up. So S3, which is our simple storage service, we see that use case way more often with our VMware cloud on AWS customers. This also ties with that Datrium integration that I talked about with the VCD or the VMware cloud disaster recovery, providing that low cost TR option. We are also starting to see customers offload database management, for example, with Amazon RDS, and taking advantage of the manage database service. As we talk to more customers, some of the use cases that comes up are like, hey, how do I build this data lake architecture? I've migrated to the cloud, I want to make use of the data that I have in the cloud now, how do I build my data lake architecture or perform analytics or build this operation resiliency across both these environments, their VMware cloud on AWS, as well as their native AWS environments? So we've got that seamless connectivity that they can take advantage of with VMware Transit Connect, we've got the cross account ENI model that we built, that they can take advantage of. And he talks about this one, and talks about the security is always job zero for us. And we're also seeing customers that take advantage of the AWS services like the web application firewall or shield, and integrating it with the VMware cloud on AWS environment. And that provides a seamless access right? You now have all these security services that AWS provides, that allows you to build a secure environment on VMware cloud on AWS. So providing customers the choice has always been a priority, right? We're talking about like infrastructure level services. As we move up the stack, and as customers are going through this modernization journey, like VMware provides containerization option using VMware Tanzu, that came out at VMworld. And then they also have the native options, we provide a EKS, which is our Kubernetes as a managed service. And then we also have other services that enables customers to take that jump into that modernization journey. One customer we've been working very recently with is PennyMac. They migrated their VDI infrastructure into VMware cloud on AWS. And that's allowed them to scale their environment for the remote workers. But what they are doing as part of their modernization journey, is now we're helping them build this completely serverless architecture, using Lambda on the AWS cloud. >> Yeah, that's really where they see that, the value is high level services, the old expression prima, they use the hockey from Wayne Gretzky skate to where the puck is going to be, or, get to where the ball will be in the field. This is kind of what's happening, and I'm kind of smiling, when Aarthi was talking because, I've been saying it's been, going to, IT operations, and IT serviceman's is going to change radically so years ago. But you're really talking about here is the operating side of IT coming together with cloud. VMware, I think is a leading indicator of, you still got to operate IT, you still got to operate stuff. Software needs to be operated apps need to be operated. So this new operating model is being shown here with cloud, this is the theme with and without IT. With automation, this is the big trend from re:Invent this year. Obviously AI machine learning, you still got to operate the stuff. It's IT, depends on, we got lammed in automation doesn't go away, the game is still the same, isn't it what's happening here? >> Absolutely, so what we're saying is, once there's that you're absolutely right about the fact that they needed to, worry about the operations, once they migrate their workloads, they're taking their data, they're saying, how do I make sure that I put in place operational excellence, and this is where, AWS comes in, and we provide them with the tools needed to do that. And then step number two, say, what can I do with this data? How do I translate it into a business benefit? And this is where the AI ML tools come in place, and so forth. And then the third step, which is all right, what can I do to modernize these applications further. So you're spot on, John, in saying that this is like a transformation, it is no longer a discussion about, migration anymore, it is more of a discussion about modernizing what you have in place. And this is, again, where this brilliancy between the collaboration, between VMware and AWS, is bringing to the table, sets of tools and framework for customers, whether it's security framework or networking framework, to make the pieces fit together. So I'm very excited about this partnership. And we continue to innovate, as you heard in prior discussions with our executives on behalf of our customers, we spoke about the RDS Amazon, relational database service on vSphere. We spoke about how to post on VMware cloud on AWS, to bring the cloud to the customers data center for specific needs that they have in spite. And we're not stopping here. We are continuing not to make more joint engineering and more announcements, hopefully in the future to come. >> That's great insight. And a lot of people who were commenting, three, four years ago, when this is all going down, they're on the wrong side of history, that the data is undeniable, refutable, it's a success. Aarthi give us the final word, modern applications, modern infrastructure, what does that mean, these days? What's the bottom line when you talk to people out there? When you're at a party or friends or on zoom, or a Jime, in conference? What do you tell people when they say, what's a modern application infrastructure look like? >> Yes, the word modern application, the good or bad thing is it's going to, what I said yesterday could be different from what I'm saying today. But in general, I think modern application is where we enable our customers to focus more on their business priorities using our services, versus worrying about the infrastructure or worrying about like, hey, should I be worrying about capacity? Should I be worrying about my operational needs or monitoring? I think we want to abstract all that. We want to take that heavy lifting off of customers and help them focus on their business. >> Horizontally scalable and leveraging software in the application, can't go wrong with that formula in the cloud. Thanks for coming on, and thanks for the awesome conversation. Thanks for coming on. >> Thank you John. >> Thank you >> Okay, it's theCUBE Virtual for re:Invent Experience 2020, this is virtual, not in person this year. I'm John Furrier, your host from the theCUBE, thanks for watching. (bright music)