Hello and welcome back to Supercloud 2 where we examine the intersection of cloud and data in the 2020s. My name is Dave Vellante. Our Supercloud panel, our power panel is back. Maribel Lopez is the founder and principal analyst at Lopez Research. Sanjeev Mohan is former Gartner analyst and principal at Sanjeev Mohan. And Keith Townsend is the CTO advisor. Folks, welcome back and thanks for your participation today. Good to see you. >> Okay, great. >> Great to see you. >> Thanks. Let me start, Maribel, with you. Bob Muglia, we had a conversation as part of Supercloud the other day. And he said, "Dave, I like the work, you got to simplify this a little bit." So he said, quote, "A Supercloud is a platform." He said, "Think of it as a platform that provides programmatically consistent services hosted on heterogeneous cloud providers." And then Nelu Mihai said, "Well, wait a minute. This is just going to create more stove pipes. We need more standards in an architecture," which is kind of what Berkeley Sky Computing initiative is all about. So there's a sort of a debate going on. Is supercloud an architecture, a platform? Or maybe it's just another buzzword. Maribel, do you have a thought on this? >> Well, the easy answer would be to say it's just a buzzword. And then we could just kill the conversation and be done with it. But I think the term, it's more than that, right? The term actually isn't new. You can go back to at least 2016 and find references to supercloud in Cornell University or assist in other documents. So, having said this, I think we've been talking about Supercloud for a while, so I assume it's more than just a fancy buzzword. But I think it really speaks to that undeniable trend of moving towards an abstraction layer to deal with the chaos of what we consider managing multiple public and private clouds today, right? So one definition of the technology platform speaks to a set of services that allows companies to build and run that technology smoothly without worrying about the underlying infrastructure, which really gets back to something that Bob said. And some of the question is where that lives. And you could call that an abstraction layer. You could call it cross-cloud services, hybrid cloud management. So I see momentum there, like legitimate momentum with enterprise IT buyers that are trying to deal with the fact that they have multiple clouds now. So where I think we're moving is trying to define what are the specific attributes and frameworks of that that would make it so that it could be consistent across clouds. What is that layer? And maybe that's what the supercloud is. But one of the things I struggle with with supercloud is. What are we really trying to do here? Are we trying to create differentiated services in the supercloud layer? Is a supercloud just another variant of what AWS, GCP, or others do? You spoken to Walmart about its cloud native platform, and that's an example of somebody deciding to do it themselves because they need to deal with this today and not wait for some big standards thing to happen. So whatever it is, I do think it's something. I think we're trying to maybe create an architecture out of it would be a better way of saying it so that it does get to those set of principles, but it also needs to be edge aware. I think whenever we talk about supercloud, we're always talking about like the big centralized cloud. And I think we need to think about all the distributed clouds that we're looking at in edge as well. So that might be one of the ways that supercloud evolves. >> So thank you, Maribel. Keith, Brian Gracely, Gracely's law, things kind of repeat themselves. We've seen it all before. And so what Muglia brought to the forefront is this idea of a platform where the platform provider is really responsible for the architecture. Of course, the drawback is then you get a a bunch of stove pipes architectures. But practically speaking, that's kind of the way the industry has always evolved, right? >> So if we look at this from the practitioner's perspective and we talk about platforms, traditionally vendors have provided the platforms for us, whether it's distribution of lineage managed by or provided by Red Hat, Windows, servers, .NET, databases, Oracle. We think of those as platforms, things that are fundamental we can build on top. Supercloud isn't today that. It is a framework or idea, kind of a visionary goal to get to a point that we can have a platform or a framework. But what we're seeing repeated throughout the industry in customers, whether it's the Walmarts that's kind of supersized the idea of supercloud, or if it's regular end user organizations that are coming out with platform groups, groups who normalize cloud native infrastructure, AWS multi-cloud, VMware resources to look like one thing internally to their developers. We're seeing this trend that there's a desire for a platform that provides the capabilities of a supercloud. >> Thank you for that. Sanjeev, we often use Snowflake as a supercloud example, and now would presumably would be a platform with an architecture that's determined by the vendor. Maybe Databricks is pushing for a more open architecture, maybe more of that nirvana that we were talking about before to solve for supercloud. But regardless, the practitioner discussions show. At least currently, there's not a lot of cross-cloud data sharing. I think it could be a killer use case, egress charges or a barrier. But how do you see it? Will that change? Will we hide that underlying complexity and start sharing data across cloud? Is that something that you think Snowflake or others will be able to achieve? >> So I think we are already starting to see some of that happen. Snowflake is definitely one example that gets cited a lot. But even we don't talk about MongoDB in this like, but you could have a MongoDB cluster, for instance, with nodes sitting in different cloud providers. So there are companies that are starting to do it. The advantage that these companies have, let's take Snowflake as an example, it's a centralized proprietary platform. And they are building the capabilities that are needed for supercloud. So they're building things like you can push down your data transformations. They have the entire security and privacy suite. Data ops, they're adding those capabilities. And if I'm not mistaken, it'll be very soon, we will see them offer data observability. So it's all works great as long as you are in one platform. And if you want resilience, then Snowflake, Supercloud, great example. But if your primary goal is to choose the most cost-effective service irrespective of which cloud it sits in, then things start falling sideways. For example, I may be a very big Snowflake user. And I like Snowflake's resilience. I can move from one cloud to another cloud. Snowflake does it for me. But what if I want to train a very large model? Maybe Databricks is a better platform for that. So how do I do move my workload from one platform to another platform? That tooling does not exist. So we need server hybrid, cross-cloud, data ops platform. Walmart has done a great job, but they built it by themselves. Not every company is Walmart. Like Maribel and Keith said, we need standards, we need reference architectures, we need some sort of a cost control. I was just reading recently, Accenture has been public about their AWS bill. Every time they get the bill is tens of millions of lines, tens of millions 'cause there are over thousand teams using AWS. If we have not been able to corral a usage of a single cloud, now we're talking about supercloud, we've got multiple clouds, and hybrid, on-prem, and edge. So till we've got some cross-platform tooling in place, I think this will still take quite some time for it to take shape. >> It's interesting. Maribel, Walmart would tell you that their on-prem infrastructure is cheaper to run than the stuff in the cloud. but at the same time, they want the flexibility and the resiliency of their three-legged stool model. So the point as Sanjeev was making about hybrid. It's an interesting balance, isn't it, between getting your lowest cost and at the same time having best of breed and scale? >> It's basically what you're trying to optimize for, as you said, right? And by the way, to the earlier point, not everybody is at Walmart's scale, so it's not actually cheaper for everybody to have the purchasing power to make the cloud cheaper to have it on-prem. But I think what you see almost every company, large or small, moving towards is this concept of like, where do I find the agility? And is the agility in building the infrastructure for me? And typically, the thing that gives you outside advantage as an organization is not how you constructed your cloud computing infrastructure. It might be how you structured your data analytics as an example, which cloud is related to that. But how do you marry those two things? And getting back to sort of Sanjeev's point. We're in a real struggle now where one hand we want to have best of breed services and on the other hand we want it to be really easy to manage, secure, do data governance. And those two things are really at odds with each other right now. So if you want all the knobs and switches of a service like geospatial analytics and big query, you're going to have to use Google tools, right? Whereas if you want visibility across all the clouds for your application of state and understand the security and governance of that, you're kind of looking for something that's more cross-cloud tooling at that point. But whenever you talk to somebody about cross-cloud tooling, they look at you like that's not really possible. So it's a very interesting time in the market. Now, we're kind of layering this concept of supercloud on it. And some people think supercloud's about basically multi-cloud tooling, and some people think it's about a whole new architectural stack. So we're just not there yet. But it's not all about cost. I mean, cloud has not been about cost for a very, very long time. Cloud has been about how do you really make the most of your data. And this gets back to cross-cloud services like Snowflake. Why did they even exist? They existed because we had data everywhere, but we need to treat data as a unified object so that we can analyze it and get insight from it. And so that's where some of the benefit of these cross-cloud services are moving today. Still a long way to go, though, Dave. >> Keith, I reached out to my friends at ETR given the macro headwinds, And you're right, Maribel, cloud hasn't really been about just about cost savings. But I reached out to the ETR, guys, what's your data show in terms of how customers are dealing with the economic headwinds? And they said, by far, their number one strategy to cut cost is consolidating redundant vendors. And a distant second, but still notable was optimizing cloud costs. Maybe using reserve instances, or using more volume buying. Nowhere in there. And I asked them to, "Could you go look and see if you can find it?" Do we see repatriation? And you hear this a lot. You hear people whispering as analysts, "You better look into that repatriation trend." It's pretty big. You can't find it. But some of the Walmarts in the world, maybe even not repatriating, but they maybe have better cost structure on-prem. Keith, what are you seeing from the practitioners that you talk to in terms of how they're dealing with these headwinds? >> Yeah, I just got into a conversation about this just this morning with (indistinct) who is an analyst over at GigaHome. He's reading the same headlines. Repatriation is happening at large scale. I think this is kind of, we have these quiet terms now. We have quiet quitting, we have quiet hiring. I think we have quiet repatriation. Most people haven't done away with their data centers. They're still there. Whether they're completely on-premises data centers, and they own assets, or they're partnerships with QTX, Equinix, et cetera, they have these private cloud resources. What I'm seeing practically is a rebalancing of workloads. Do I really need to pay AWS for this instance of SAP that's on 24 hours a day versus just having it on-prem, moving it back to my data center? I've talked to quite a few customers who were early on to moving their static SAP workloads onto the public cloud, and they simply moved them back. Surprising, I was at VMware Explore. And we can talk about this a little bit later on. But our customers, net new, not a lot that were born in the cloud. And they get to this point where their workloads are static. And they look at something like a Kubernetes, or a OpenShift, or VMware Tanzu. And they ask the question, "Do I need the scalability of cloud?" I might consider being a net new VMware customer to deliver this base capability. So are we seeing repatriation as the number one reason? No, I think internal IT operations are just naturally come to this realization. Hey, I have these resources on premises. The private cloud technologies have moved far along enough that I can just simply move this workload back. I'm not calling it repatriation, I'm calling it rightsizing for the operating model that I have. >> Makes sense. Yeah. >> Go ahead. >> If I missed something, Dave, why we are on this topic of repatriation. I'm actually surprised that we are talking about repatriation as a very big thing. I think repatriation is happening, no doubt, but it's such a small percentage of cloud migration that to me it's a rounding error in my opinion. I think there's a bigger problem. The problem is that people don't know where the cost is. If they knew where the cost was being wasted in the cloud, they could do something about it. But if you don't know, then the easy answer is cloud costs a lot and moving it back to on-premises. I mean, take like Capital One as an example. They got rid of all the data centers. Where are they going to repatriate to? They're all in the cloud at this point. So I think my point is that data observability is one of the places that has seen a lot of traction is because of cost. Data observability, when it first came into existence, it was all about data quality. Then it was all about data pipeline reliability. And now, the number one killer use case is FinOps. >> Maribel, you had a comment? >> Yeah, I'm kind of in violent agreement with both Sanjeev and Keith. So what are we seeing here? So the first thing that we see is that many people wildly overspent in the big public cloud. They had stranded cloud credits, so to speak. The second thing is, some of them still had infrastructure that was useful. So why not use it if you find the right workloads to what Keith was talking about, if they were more static workloads, if it was already there? So there is a balancing that's going on. And then I think fundamentally, from a trend standpoint, these things aren't binary. Everybody, for a while, everything was going to go to the public cloud and then people are like, "Oh, it's kind of expensive." Then they're like, "Oh no, they're going to bring it all on-prem 'cause it's really expensive." And it's like, "Well, that doesn't necessarily get me some of the new features and functionalities I might want for some of my new workloads." So I'm going to put the workloads that have a certain set of characteristics that require cloud in the cloud. And if I have enough capability on-prem and enough IT resources to manage certain things on site, then I'm going to do that there 'cause that's a more cost-effective thing for me to do. It's not binary. That's why we went to hybrid. And then we went to multi just to describe the fact that people added multiple public clouds. And now we're talking about super, right? So I don't look at it as a one-size-fits-all for any of this. >> A a number of practitioners leading up to Supercloud2 have told us that they're solving their cloud complexity by going in monocloud. So they're putting on the blinders. Even though across the organization, there's other groups using other clouds. You're like, "In my group, we use AWS, or my group, we use Azure. And those guys over there, they use Google. We just kind of keep it separate." Are you guys hearing this in your view? Is that risky? Are they missing out on some potential to tap best of breed? What do you guys think about that? >> Everybody thinks they're monocloud. Is anybody really monocloud? It's like a group is monocloud, right? >> Right. >> This genie is out of the bottle. We're not putting the genie back in the bottle. You might think your monocloud and you go like three doors down and figure out the guy or gal is on a fundamentally different cloud, running some analytics workload that you didn't know about. So, to Sanjeev's earlier point, they don't even know where their cloud spend is. So I think the concept of monocloud, how that's actually really realized by practitioners is primary and then secondary sources. So they have a primary cloud that they run most of their stuff on, and that they try to optimize. And we still have forked workloads. Somebody decides, "Okay, this SAP runs really well on this, or these analytics workloads run really well on that cloud." And maybe that's how they parse it. But if you really looked at it, there's very few companies, if you really peaked under the hood and did an analysis that you could find an actual monocloud structure. They just want to pull it back in and make it more manageable. And I respect that. You want to do what you can to try to streamline the complexity of that. >> Yeah, we're- >> Sorry, go ahead, Keith. >> Yeah, we're doing this thing where we review AWS service every day. Just in your inbox, learn about a new AWS service cursory. There's 238 AWS products just on the AWS cloud itself. Some of them are redundant, but you get the idea. So the concept of monocloud, I'm in filing agreement with Maribel on this that, yes, a group might say I want a primary cloud. And that primary cloud may be the AWS. But have you tried the licensed Oracle database on AWS? It is really tempting to license Oracle on Oracle Cloud, Microsoft on Microsoft. And I can't get RDS anywhere but Amazon. So while I'm driven to desire the simplicity, the reality is whether be it M&A, licensing, data sovereignty. I am forced into a multi-cloud management style. But I do agree most people kind of do this one, this primary cloud, secondary cloud. And I guarantee you're going to have a third cloud or a fourth cloud whether you want to or not via shadow IT, latency, technical reasons, et cetera. >> Thank you. Sanjeev, you had a comment? >> Yeah, so I just wanted to mention, as an organization, I'm complete agreement, no organization is monocloud, at least if it's a large organization. Large organizations use all kinds of combinations of cloud providers. But when you talk about a single workload, that's where the program arises. As Keith said, the 238 services in AWS. How in the world am I going to be an expert in AWS, but then say let me bring GCP or Azure into a single workload? And that's where I think we probably will still see monocloud as being predominant because the team has developed its expertise on a particular cloud provider, and they just don't have the time of the day to go learn yet another stack. However, there are some interesting things that are happening. For example, if you look at a multi-cloud example where Oracle and Microsoft Azure have that interconnect, so that's a beautiful thing that they've done because now in the newest iteration, it's literally a few clicks. And then behind the scene, your .NET application and your Oracle database in OCI will be configured, the identities in active directory are federated. And you can just start using a database in one cloud, which is OCI, and an application, your .NET in Azure. So till we see this kind of a solution coming out of the providers, I think it's is unrealistic to expect the end users to be able to figure out multiple clouds. >> Well, I have to share with you. I can't remember if he said this on camera or if it was off camera so I'll hold off. I won't tell you who it is, but this individual was sort of complaining a little bit saying, "With AWS, I can take their best AI tools like SageMaker and I can run them on my Snowflake." He said, "I can't do that in Google. Google forces me to go to BigQuery if I want their excellent AI tools." So he was sort of pushing, kind of tweaking a little bit. Some of the vendor talked that, "Oh yeah, we're so customer-focused." Not to pick on Google, but I mean everybody will say that. And then you say, "If you're so customer-focused, why wouldn't you do a ABC?" So it's going to be interesting to see who leads that integration and how broadly it's applied. But I digress. Keith, at our first supercloud event, that was on August 9th. And it was only a few months after Broadcom announced the VMware acquisition. A lot of people, myself included said, "All right, cuts are coming." Generally, Tanzu is probably going to be under the radar, but it's Supercloud 22 and presumably VMware Explore, the company really... Well, certainly the US touted its Tanzu capabilities. I wasn't at VMware Explore Europe, but I bet you heard similar things. Hawk Tan has been blogging and very vocal about cross-cloud services and multi-cloud, which doesn't happen without Tanzu. So what did you hear, Keith, in Europe? What's your latest thinking on VMware's prospects in cross-cloud services/supercloud? >> So I think our friend and Cube, along host still be even more offended at this statement than he was when I sat in the Cube. This was maybe five years ago. There's no company better suited to help industries or companies, cross-cloud chasm than VMware. That's not a compliment. That's a reality of the industry. This is a very difficult, almost intractable problem. What I heard that VMware Europe were customers serious about this problem, even more so than the US data sovereignty is a real problem in the EU. Try being a company in Switzerland and having the Swiss data solvency issues. And there's no local cloud presence there large enough to accommodate your data needs. They had very serious questions about this. I talked to open source project leaders. Open source project leaders were asking me, why should I use the public cloud to host Kubernetes-based workloads, my projects that are building around Kubernetes, and the CNCF infrastructure? Why should I use AWS, Google, or even Azure to host these projects when that's undifferentiated? I know how to run Kubernetes, so why not run it on-premises? I don't want to deal with the hardware problems. So again, really great questions. And then there was always the specter of the problem, I think, we all had with the acquisition of VMware by Broadcom potentially. 4.5 billion in increased profitability in three years is a unbelievable amount of money when you look at the size of the problem. So a lot of the conversation in Europe was about industry at large. How do we do what regulators are asking us to do in a practical way from a true technology sense? Is VMware cross-cloud great? >> Yeah. So, VMware, obviously, to your point. OpenStack is another way of it. Actually, OpenStack, uptake is still alive and well, especially in those regions where there may not be a public cloud, or there's public policy dictating that. Walmart's using OpenStack. As you know in IT, some things never die. Question for Sanjeev. And it relates to this new breed of data apps. And Bob Muglia and Tristan Handy from DBT Labs who are participating in this program really got us thinking about this. You got data that resides in different clouds, it maybe even on-prem. And the machine polls data from different systems. No humans involved, e-commerce, ERP, et cetera. It creates a plan, outcomes. No human involvement. Today, you're on a CRM system, you're inputting, you're doing forms, you're, you're automating processes. We're talking about a new breed of apps. What are your thoughts on this? Is it real? Is it just way off in the distance? How does machine intelligence fit in? And how does supercloud fit? >> So great point. In fact, the data apps that you're talking about, I call them data products. Data products first came into limelight in the last couple of years when Jamal Duggan started talking about data mesh. I am taking data products out of the data mesh concept because data mesh, whether data mesh happens or not is analogous to data products. Data products, basically, are taking a product management view of bringing data from different sources based on what the consumer needs. We were talking earlier today about maybe it's my vacation rentals, or it may be a retail data product, it may be an investment data product. So it's a pre-packaged extraction of data from different sources. But now I have a product that has a whole lifecycle. I can version it. I have new features that get added. And it's a very business data consumer centric. It uses machine learning. For instance, I may be able to tell whether this data product has stale data. Who is using that data? Based on the usage of the data, I may have a new data products that get allocated. I may even have the ability to take existing data products, mash them up into something that I need. So if I'm going to have that kind of power to create a data product, then having a common substrate underneath, it can be very useful. And that could be supercloud where I am making API calls. I don't care where the ERP, the CRM, the survey data, the pricing engine where they sit. For me, there's a logical abstraction. And then I'm building my data product on top of that. So I see a new breed of data products coming out. To answer your question, how early we are or is this even possible? My prediction is that in 2023, we will start seeing more of data products. And then it'll take maybe two to three years for data products to become mainstream. But it's starting this year. >> A subprime mortgages were a data product, definitely were humans involved. All right, let's talk about some of the supercloud, multi-cloud players and what their future looks like. You can kind of pick your favorites. VMware, Snowflake, Databricks, Red Hat, Cisco, Dell, HP, Hashi, IBM, CloudFlare. There's many others. cohesive rubric. Keith, I wanted to start with CloudFlare because they actually use the term supercloud. and just simplifying what they said. They look at it as taking serverless to the max. You write your code and then you can deploy it in seconds worldwide, of course, across the CloudFlare infrastructure. You don't have to spin up containers, you don't go to provision instances. CloudFlare worries about all that infrastructure. What are your thoughts on CloudFlare this approach and their chances to disrupt the current cloud landscape? >> As Larry Ellison said famously once before, the network is the computer, right? I thought that was Scott McNeley. >> It wasn't Scott McNeley. I knew it was on Oracle Align. >> Oracle owns that now, owns that line. >> By purpose or acquisition. >> They should have just called it cloud. >> Yeah, they should have just called it cloud. >> Easier. >> Get ahead. >> But if you think about the CloudFlare capability, CloudFlare in its own right is becoming a decent sized cloud provider. If you have compute out at the edge, when we talk about edge in the sense of CloudFlare and points of presence, literally across the globe, you have all of this excess computer, what do you do with it? First offering, let's disrupt data in the cloud. We can't start the conversation talking about data. When they say we're going to give you object-oriented or object storage in the cloud without egress charges, that's disruptive. That we can start to think about supercloud capability of having compute EC2 run in AWS, pushing and pulling data from CloudFlare. And now, I've disrupted this roach motel data structure, and that I'm freely giving away bandwidth, basically. Well, the next layer is not that much more difficult. And I think part of CloudFlare's serverless approach or supercloud approaches so that they don't have to commit to a certain type of compute. It is advantageous. It is a feature for me to be able to go to EC2 and pick a memory heavy model, or a compute heavy model, or a network heavy model, CloudFlare is taken away those knobs. and I'm just giving code and allowing that to run. CloudFlare has a massive network. If I can put the code closest using the CloudFlare workers, if I can put that code closest to where the data is at or residing, super compelling observation. The question is, does it scale? I don't get the 238 services. While Server List is great, I have to know what I'm going to build. I don't have a Cognito, or RDS, or all these other services that make AWS, GCP, and Azure appealing from a builder's perspective. So it is a very interesting nascent start. It's great because now they can hide compute. If they don't have the capacity, they can outsource that maybe at a cost to one of the other cloud providers, but kind of hiding the compute behind the surplus architecture is a really unique approach. >> Yeah. And they're dipping their toe in the water. And they've announced an object store and a database platform and more to come. We got to wrap. So I wonder, Sanjeev and Maribel, if you could maybe pick some of your favorites from a competitive standpoint. Sanjeev, I felt like just watching Snowflake, I said, okay, in my opinion, they had the right strategy, which was to run on all the clouds, and then try to create that abstraction layer and data sharing across clouds. Even though, let's face it, most of it might be happening across regions if it's happening, but certainly outside of an individual account. But I felt like just observing them that anybody who's traditional on-prem player moving into the clouds or anybody who's a cloud native, it just makes total sense to write to the various clouds. And to the extent that you can simplify that for users, it seems to be a logical strategy. Maybe as I said before, what multi-cloud should have been. But are there companies that you're watching that you think are ahead in the game , or ones that you think are a good model for the future? >> Yes, Snowflake, definitely. In fact, one of the things we have not touched upon very much, and Keith mentioned a little bit, was data sovereignty. Data residency rules can require that certain data should be written into certain region of a certain cloud. And if my cloud provider can abstract that or my database provider, then that's perfect for me. So right now, I see Snowflake is way ahead of this pack. I would not put MongoDB too far behind. They don't really talk about this thing. They are in a different space, but now they have a lakehouse, and they've got all of these other SQL access and new capabilities that they're announcing. So I think they would be quite good with that. Oracle is always a dark forest. Oracle seems to have revived its Cloud Mojo to some extent. And it's doing some interesting stuff. Databricks is the other one. I have not seen Databricks. They've been very focused on lakehouse, unity, data catalog, and some of those pieces. But they would be the obvious challenger. And if they come into this space of supercloud, then they may bring some open source technologies that others can rely on like Delta Lake as a table format. >> Yeah. One of these infrastructure players, Dell, HPE, Cisco, even IBM. I mean, I would be making my infrastructure as programmable and cloud friendly as possible. That seems like table stakes. But Maribel, any companies that stand out to you that we should be paying attention to? >> Well, we already mentioned a bunch of them, so maybe I'll go a slightly different route. I'm watching two companies pretty closely to see what kind of traction they get in their established companies. One we already talked about, which is VMware. And the thing that's interesting about VMware is they're everywhere. And they also have the benefit of having a foot in both camps. If you want to do it the old way, the way you've always done it with VMware, they got all that going on. If you want to try to do a more cross-cloud, multi-cloud native style thing, they're really trying to build tools for that. So I think they have really good access to buyers. And that's one of the reasons why I'm interested in them to see how they progress. The other thing, I think, could be a sleeping horse oddly enough is Google Cloud. They've spent a lot of work and time on Anthos. They really need to create a certain set of differentiators. Well, it's not necessarily in their best interest to be the best multi-cloud player. If they decide that they want to differentiate on a different layer of the stack, let's say they want to be like the person that is really transformative, they talk about transformation cloud with analytics workloads, then maybe they do spend a good deal of time trying to help people abstract all of the other underlying infrastructure and make sure that they get the sexiest, most meaningful workloads into their cloud. So those are two people that you might not have expected me to go with, but I think it's interesting to see not just on the things that might be considered, either startups or more established independent companies, but how some of the traditional providers are trying to reinvent themselves as well. >> I'm glad you brought that up because if you think about what Google's done with Kubernetes. I mean, would Google even be relevant in the cloud without Kubernetes? I could argue both sides of that. But it was quite a gift to the industry. And there's a motivation there to do something unique and different from maybe the other cloud providers. And I'd throw in Red Hat as well. They're obviously a key player and Kubernetes. And Hashi Corp seems to be becoming the standard for application deployment, and terraform, or cross-clouds, and there are many, many others. I know we're leaving lots out, but we're out of time. Folks, I got to thank you so much for your insights and your participation in Supercloud2. Really appreciate it. >> Thank you. >> Thank you. >> Thank you. >> This is Dave Vellante for John Furrier and the entire Cube community. Keep it right there for more content from Supercloud2.

>>Hey everyone. Welcome back to Las Vegas. It's the Cube live at AWS Reinvent 2022. This is our fourth day of coverage. Lisa Martin here with Paul Gillen. Paul, we started Monday night, we filmed and streamed for about three hours. We have had shammed pack days, Tuesday, Wednesday, Thursday. What's your takeaway? >>We're routed final turn as we, as we head into the home stretch. Yeah. This is as it has been since the beginning, this show with a lot of energy. I'm amazed for the fourth day of a conference, how many people are still here I am too. And how, and how active they are and how full the sessions are. Huge. Proud for the keynote this morning. You don't see that at most of the day four conferences. Everyone's on their way home. So, so people come here to learn and they're, and they're still >>Learning. They are still learning. And we're gonna help continue that learning path. We have an alumni back with us, Toron joins us, the CPO and co-founder of Dremeo. Tomer, it's great to have you back on the program. >>Yeah, thanks for, for having me here. And thanks for keeping the, the best session for the fourth day. >>Yeah, you're right. I like that. That's a good mojo to come into this interview with Tomer. So last year, last time I saw you was a year ago here in Vegas at Reinvent 21. We talked about the growth of data lakes and the data lake houses. We talked about the need for open data architectures as opposed to data warehouses. And the headline of the Silicon Angle's article on the interview we did with you was, Dremio Predicts 2022 will be the year open data architectures replace the data warehouse. We're almost done with 2022. Has that prediction come true? >>Yeah, I think, I think we're seeing almost every company out there, certainly in the enterprise, adopting data lake, data lakehouse technology, embracing open source kind of file and table formats. And, and so I think that's definitely happening. Of course, nothing goes away. So, you know, data warehouses don't go away in, in a year and actually don't go away ever. We still have mainframes around, but certainly the trends are, are all pointing in that direction. >>Describe the data lakehouse for anybody who may not be really familiar with that and, and what it's, what it really means for organizations. >>Yeah. I think you could think of the data lakehouse as the evolution of the data lake, right? And so, you know, for, for, you know, the last decade we've had kind of these two options, data lakes and data warehouses and, you know, warehouses, you know, having good SQL support, but, and good performance. But you had to spend a lot of time and effort getting data into the warehouse. You got locked into them, very, very expensive. That's a big problem now. And data lakes, you know, more open, more scalable, but had all sorts of kind of limitations. And what we've done now as an industry with the Lake House, and especially with, you know, technologies like Apache Iceberg, is we've unlocked all the capabilities of the warehouse directly on object storage like s3. So you can insert and update and delete individual records. You can do transactions, you can do all the things you could do with a, a database directly in kind of open formats without getting locked in at a much lower cost. >>But you're still dealing with semi-structured data as opposed to structured data. And there's, there's work that has to be done to get that into a usable form. That's where Drio excels. What, what has been happening in that area to, to make, I mean, is it formats like j s o that are, are enabling this to happen? How, how we advancing the cause of making semi-structured data usable? Yeah, >>Well, I think first of all, you know, I think that's all changed. I think that was maybe true for the original data lakes, but now with the Lake house, you know, our bread and butter is actually structured data. It's all, it's all tables with the schema. And, you know, you can, you know, create table insert records. You know, it's, it's, it's really everything you can do with a data warehouse you can now do in the lakehouse. Now, that's not to say that there aren't like very advanced capabilities when it comes to, you know, j s O and nested data and kind of sparse data. You know, we excel in that as well. But we're really seeing kind of the lakehouse take over the, the bread and butter data warehouse use cases. >>You mentioned open a minute ago. Talk about why it's, why open is important and the value that it can deliver for customers. >>Yeah, well, I think if you look back in time and you see all the challenges that companies have had with kind of traditional data architectures, right? The, the, the, a lot of that comes from the, the, the problems with data warehouses. The fact that they are, you know, they're very expensive. The data is, you have to ingest it into the data warehouse in order to query it. And then it's almost impossible to get off of these systems, right? It takes an enormous effort, tremendous cost to get off of them. And so you're kinda locked in and that's a big problem, right? You also, you're dependent on that one data warehouse vendor, right? You can only do things with that data that the warehouse vendor supports. And if you contrast that to data lakehouse and open architectures where the data is stored in entirely open formats. >>So things like par files and Apache iceberg tables, that means you can use any engine on that data. You can use s SQL Query Engine, you can use Spark, you can use flin. You know, there's a dozen different engines that you can use on that, both at the same time. But also in the future, if you ever wanted to try something new that comes out, some new open source innovation, some new startup, you just take it and point out the same data. So that data's now at the core, at the center of the architecture as opposed to some, you know, vendors logo. Yeah. >>Amazon seems to be bought into the Lakehouse concept. It has big announcements on day two about eliminating the ETL stage between RDS and Redshift. Do you see the cloud vendors as pushing this concept forward? >>Yeah, a hundred percent. I mean, I'm, I'm Amazon's a great, great partner of ours. We work with, you know, probably 10 different teams there. Everything from, you know, the S3 team, the, the glue team, the click site team, you know, everything in between. And, you know, their embracement of the, the, the lake house architecture, the fact that they adopted Iceberg as their primary table format. I think that's exciting as an industry. We're all coming together around standard, standard ways to represent data so that at the end of the day, companies have this benefit of being able to, you know, have their own data in their own S3 account in open formats and be able to use all these different engines without losing any of the functionality that they need, right? The ability to do all these interactions with data that maybe in the past you would have to move the data into a database or, or warehouse in order to do, you just don't have to do that anymore. Speaking >>Of functionality, talk about what's new this year with drio since we've seen you last. >>Yeah, there's a lot of, a lot of new things with, with Drio. So yeah, we now have full Apache iceberg support, you know, with DML commands, you can do inserts, updates, deletes, you know, copy into all, all that kind of stuff is now, you know, fully supported native part of the platform. We, we now offer kind of two flavors of dr. We have, you know, Dr. Cloud, which is our SaaS version fully hosted. You sign up with your Google or, you know, Azure account and, and, and you're up in, you're up and running in, in, in a minute. And then dral software, which you can self host usually in the cloud, but even, even even outside of the cloud. And then we're also very excited about this new idea of data as code. And so we've introduced a new product that's now in preview called Dr. >>Arctic. And the idea there is to bring the concepts of GI or GitHub to the world of data. So things like being able to create a branch and work in isolation. If you're a data scientist, you wanna experiment on your own without impacting other people, or you're a data engineer and you're ingesting data, you want to transform it and test it before you expose it to others. You can do that in a branch. So all these ideas that, you know, we take for granted now in the world of source code and software development, we're bringing to the world of data with Jamar. And when you think about data mesh, a lot of people talking about data mesh now and wanting to kind of take advantage of, of those concepts and ideas, you know, thinking of data as a product. Well, when you think about data as a product, we think you have to manage it like code, right? You have to, and that's why we call it data as code, right? The, all those reasons that we use things like GI have to build products, you know, if we wanna think of data as a product, we need all those capabilities also with data. You know, also the ability to go back in time. The ability to undo mistakes, to see who changed my data and when did they change that table. All of those are, are part of this, this new catalog that we've created. >>Are you talk about data as a product that's sort of intrinsic to the data mesh concept. Are you, what's your opinion of data mesh? Is the, is the world ready for that radically different approach to data ownership? >>You know, we are now in dozens of, dozens of our customers that are using drio for to implement enterprise-wide kind of data mesh solutions. And at the end of the day, I think it's just, you know, what most people would consider common sense, right? In a large organization, it is very hard for a centralized single team to understand every piece of data, to manage all the data themselves, to, you know, make sure the quality is correct to make it accessible. And so what data mesh is first and foremost about is being able to kind of federate the, or distribute the, the ownership of data, the governance of the data still has to happen, right? And so that is, I think at the heart of the data mesh, but thinking of data as kind of allowing different teams, different domains to own their own data to really manage it like a product with all the best practices that that we have with that super important. >>So we we're doing a lot with data mesh, you know, the way that cloud has multiple projects and the way that Jamar allows you to have multiple catalogs and different groups can kind of interact and share data among each other. You know, the fact that we can connect to all these different data sources, even outside your data lake, you know, with Redshift, Oracle SQL Server, you know, all the different databases that are out there and join across different databases in addition to your data lake, that that's all stuff that companies want with their data mesh. >>What are some of your favorite customer stories that where you've really helped them accelerate that data mesh and drive business value from it so that more people in the organization kind of access to data so they can really make those data driven decisions that everybody wants to make? >>I mean, there's, there's so many of them, but, you know, one of the largest tech companies in the world creating a, a data mesh where you have all the different departments in the company that, you know, they, they, they were a big data warehouse user and it kinda hit the wall, right? The costs were so high and the ability for people to kind of use it for just experimentation, to try new things out to collaborate, they couldn't do it because it was so prohibitively expensive and difficult to use. And so what they said, well, we need a platform that different people can, they can collaborate, they can ex, they can experiment with the data, they can share data with others. And so at a big organization like that, the, their ability to kind of have a centralized platform but allow different groups to manage their own data, you know, several of the largest banks in the world are, are also doing data meshes with Dr you know, one of them has over over a dozen different business units that are using, using Dremio and that ability to have thousands of people on a platform and to be able to collaborate and share among each other that, that's super important to these >>Guys. Can you contrast your approach to the market, the snowflakes? Cause they have some of those same concepts. >>Snowflake's >>A very closed system at the end of the day, right? Closed and very expensive. Right? I think they, if I remember seeing, you know, a quarter ago in, in, in one of their earnings reports that the average customer spends 70% more every year, right? Well that's not sustainable. If you think about that in a decade, that's your cost is gonna increase 200 x, most companies not gonna be able to swallow that, right? So companies need, first of all, they need more cost efficient solutions that are, you know, just more approachable, right? And the second thing is, you know, you know, we talked about the open data architecture. I think most companies now realize that the, if you want to build a platform for the future, you need to have the data and open formats and not be locked into one vendor, right? And so that's kind of another important aspect beyond that's ability to connect to all your data, even outside the lake to your different databases, no sequel databases, relational databases, and drs semantic layer where we can accelerate queries. And so typically what you have, what happens with data warehouses and other data lake query engines is that because you can't get the performance that you want, you end up creating lots and lots of copies of data. You, for every use case, you're creating a, you know, a pre-joy copy of that data, a pre aggregated version of that data. And you know, then you have to redirect all your data. >>You've got a >>Governance problem, individual things. It's expensive. It's expensive, it's hard to secure that cuz permissions don't travel with the data. So you have all sorts of problems with that, right? And so what we've done because of our semantic layer that makes it easy to kind of expose data in a logical way. And then our query acceleration technology, which we call reflections, which transparently accelerates queries and gives you subsecond response times without data copies and also without extracts into the BI tools. Cause if you start doing bi extracts or imports, again, you have lots of copies of data in the organization, all sorts of refresh problems, security problems, it's, it's a nightmare, right? And that just collapsing all those copies and having a, a simple solution where data's stored in open formats and we can give you fast access to any of that data that's very different from what you get with like a snowflake or, or any of these other >>Companies. Right. That, that's a great explanation. I wanna ask you, early this year you announced that your Dr. Cloud service would be a free forever, the basic DR. Cloud service. How has that offer gone over? What's been the uptake on that offer? >>Yeah, it, I mean it is, and thousands of people have signed up and, and it's, I think it's a great service. It's, you know, it's very, very simple. People can go on the website, try it out. We now have a test drive as well. If, if you want to get started with just some sample public sample data sets and like a tutorial, we've made that increasingly easy as well. But yeah, we continue to, you know, take that approach of, you know, making it, you know, making it easy, democratizing these kind of cloud data platforms and, and kinda lowering the barriers to >>Adoption. How, how effective has it been in driving sales of the enterprise version? >>Yeah, a lot of, a lot of, a lot of business with, you know, that, that we do like when it comes to, to selling is, you know, folks that, you know, have educated themselves, right? They've started off, they've followed some tutorials. I think generally developers, they prefer the first interaction to be with a product, not with a salesperson. And so that's, that's basically the reason we did that. >>Before we ask you the last question, I wanna just, can you give us a speak peek into the product roadmap as we enter 2023? What can you share with us that we should be paying attention to where Drum is concerned? >>Yeah. You know, actually a couple, couple days ago here at the conference, we, we had a press release with all sorts of new capabilities that we, we we just released. And there's a lot more for, for the coming year. You know, we will shortly be releasing a variety of different performance enhancements. So we'll be in the next quarter or two. We'll be, you know, probably twice as fast just in terms of rock qu speed, you know, that's in addition to our reflections and our career acceleration, you know, support for all the major clouds is coming. You know, just a lot of capabilities in Inre that make it easier and easier to use the platform. >>Awesome. Tomer, thank you so much for joining us. My last question to you is, if you had a billboard in your desired location and it was going to really just be like a mic drop about why customers should be looking at Drio, what would that billboard say? >>Well, DRIO is the easy and open data lake house and, you know, open architectures. It's just a lot, a lot better, a lot more f a lot more future proof, a lot easier and a lot just a much safer choice for the future for, for companies. And so hard to argue with those people to take a look. Exactly. That wasn't the best. That wasn't the best, you know, billboards. >>Okay. I think it's a great billboard. Awesome. And thank you so much for joining Poly Me on the program, sharing with us what's new, what some of the exciting things are that are coming down the pipe. Quite soon we're gonna be keeping our eye Ono. >>Awesome. Always happy to be here. >>Thank you. Right. For our guest and for Paul Gillin, I'm Lisa Martin. You're watching The Cube, the leader in live and emerging tech coverage.

(upbeat music) >> Hey, everyone, welcome back to Las Vegas, "theCube" is on our fourth day of covering AWS re:Invent, live from the Venetian Expo Center. This week has been amazing. We've created a ton of content, as you know, 'cause you've been watching. But, there's been north of 55,000 people here, hundreds of thousands online. We've had amazing conversations across the AWS ecosystem. Lisa Martin, Paul Gillan. Paul, what's your, kind of, take on day four of the conference? It's still highly packed. >> Oh, there's lots of people here. (laughs) >> Yep. Unusual for the final day of a conference. I think Werner Vogels, if I'm pronouncing it right kicked things off today when he talked about asymmetry and how the world is, you know, asymmetric. We build symmetric software, because it's convenient to do so, but asymmetric software actually scales and evolves much better. And I think that that was a conversation starter for a lot of what people are talking about here today, which is how the cloud changes the way we think about building software. >> Absolutely does. >> Our next guest, Holger Mueller, that's one of his key areas of focus. And Holger, welcome, thanks for joining us on the "theCube". >> Thanks for having me. >> What did you take away from the keynote this morning? >> Well, how do you feel on the final day of the marathon, right? We're like 23, 24 miles. Hit the ball yesterday, right? >> We are going strong Holger. And, of course, >> Yeah. >> you guys, we can either talk about business transformation with cloud or the World Cup. >> Or we can do both. >> The World Cup, hands down. World Cup. (Lisa laughs) Germany's out, I'm unbiased now. They just got eliminated. >> Spain is out now. >> What will the U.S. do against Netherlands tomorrow? >> They're going to win. What's your forecast? U.S. will win? >> They're going to win 2 to 1. >> What do you say, 2:1? >> I'm optimistic, but realistic. >> 3? >> I think Netherlands. >> Netherlands will win? >> 2 to nothing. >> Okay, I'll vote for the U.S.. >> Okay, okay >> 3:1 for the U.S.. >> Be optimistic. >> Root for the U.S.. >> Okay, I like that. >> Hope for the best wherever you work. >> Tomorrow you'll see how much soccer experts we are. >> If your prediction was right. (laughs) >> (laughs) Ja, ja. Or yours was right, right, so. Cool, no, but the event, I think the event is great to have 50,000 people. Biggest event of the year again, right? Not yet the 70,000 we had in 2019. But it's great to have the energy. I've never seen the show floor going all the way down like this, right? >> I haven't either. >> I've never seen that. I think it's a record. Often vendors get the space here and they have the keynote area, and the entertainment area, >> Yeah. >> and the food area, and then there's an exposition, right? This is packed. >> It's packed. >> Maybe it'll pay off. >> You don't see the big empty booths that you often see. >> Oh no. >> Exactly, exactly. You know, the white spaces and so on. >> No. >> Right. >> Which is a good thing. >> There's lots of energy, which is great. And today's, of course, the developer day, like you said before, right now Vogels' a rockstar in the developer community, right. Revered visionary on what has been built, right? And he's becoming a little professorial is my feeling, right. He had these moments before too, when it was justifying how AWS moved off the Oracle database about the importance of data warehouses and structures and why DynamoDB is better and so on. But, he had a large part of this too, and this coming right across the keynotes, right? Adam Selipsky talking about Antarctica, right? Scott against almonds and what went wrong. He didn't tell us, by the way, which often the tech winners forget. Scott banked on technology. He had motorized sleds, which failed after three miles. So, that's not the story to tell the technology. Let everything down. Everybody went back to ponies and horses and dogs. >> Maybe goes back to these asynchronous behavior. >> Yeah. >> The way of nature. >> And, yesterday, Swami talking about the bridges, right? The root bridges, right? >> Right. >> So, how could Werner pick up with his video at the beginning. >> Yeah. >> And then talk about space and other things? So I think it's important to educate about event-based architecture, right? And we see this massive transformation. Modern software has to be event based, right? Because, that's how things work and we didn't think like this before. I see this massive transformation in my other research area in other platforms about the HR space, where payrolls are being rebuilt completely. And payroll used to be one of the three peaks of ERP, right? You would size your ERP machine before the cloud to financial close, to run the payroll, and to do an MRP manufacturing run if you're manufacturing. God forbid you run those three at the same time. Your machine wouldn't be able to do that, right? So it was like start the engine, start the boosters, we are running payroll. And now the modern payroll designs like you see from ADP or from Ceridian, they're taking every payroll relevant event. You check in time wise, right? You go overtime, you take a day of vacation and right away they trigger and run the payroll, so it's up to date for you, up to date for you, which, in this economy, is super important, because we have more gig workers, we have more contractors, we have employees who are leaving suddenly, right? The great resignation, which is happening. So, from that perspective, it's the modern way of building software. So it's great to see Werner showing that. The dirty little secrets though is that is more efficient software for the cloud platform vendor too. Takes less resources, gets less committed things, so it's a much more scalable architecture. You can move the events, you can work asynchronously much better. And the biggest showcase, right? What's the biggest transactional showcase for an eventually consistent asynchronous transactional application? I know it's a mouthful, but we at Amazon, AWS, Amazon, right? You buy something on Amazon they tell you it's going to come tomorrow. >> Yep. >> They don't know it's going to come tomorrow by that time, because it's not transactionally consistent, right? We're just making every ERP vendor, who lives in transactional work, having nightmares of course, (Lisa laughs) but for them it's like, yes we have the delivery to promise, a promise to do that, right? But they come back to you and say, "Sorry, we couldn't make it, delivery didn't work and so on. It's going to be a new date. We are out of the product.", right? So these kind of event base asynchronous things are more and more what's going to scale around the world. It's going to be efficient for everybody, it's going to be better customer experience, better employee experience, ultimately better user experience, it's going to be better for the enterprise to build, but we have to learn to build it. So big announcement was to build our environment to build better eventful applications from today. >> Talk about... This is the first re:Invent... Well, actually, I'm sorry, it's the second re:Invent under Adam Selipsky. >> Right. Adam Selipsky, yep. >> But his first year. >> Right >> We're hearing a lot of momentum. What's your takeaway with what he delivered with the direction Amazon is going, their vision? >> Ja, I think compared to the Jassy times, right, we didn't see the hockey stick slide, right? With a number of innovations and releases. That was done in 2019 too, right? So I think it's a more pedestrian pace, which, ultimately, is good for everybody, because it means that when software vendors go slower, they do less width, but more depth. >> Yeah. >> And depth is what customers need. So Amazon's building more on the depth side, which is good news. I also think, and that's not official, right, but Adam Selipsky came from Tableau, right? >> Yeah. So he is a BI analytics guy. So it's no surprise we have three data lake offerings, right? Security data lake, we have a healthcare data lake and we have a supply chain data lake, right? Where all, again, the epigonos mentioned them I was like, "Oh, my god, Amazon's coming to supply chain.", but it's actually data lakes, which is an interesting part. But, I think it's not a surprise that someone who comes heavily out of the analytics BI world, it's off ringside, if I was pitching internally to him maybe I'd do something which he's is familiar with and I think that's what we see in the major announcement of his keynote on Tuesday. >> I mean, speaking of analytics, one of the big announcements early on was Amazon is trying to bridge the gap between Aurora. >> Yep. >> And Redshift. >> Right. >> And setting up for continuous pipelines, continuous integration. >> Right. >> Seems to be a trend that is common to all database players. I mean, Oracle is doing the same thing. SAP is doing the same thing. MariaDB. Do you see the distinction between transactional and analytical databases going away? >> It's coming together, right? Certainly coming together, from that perspective, but there's a fundamental different starting point, right? And with the big idea part, right? The universal database, which does everything for you in one system, whereas the suite of specialized databases, right? Oracle is in the classic Oracle database in the universal database camp. On the other side you have Amazon, which built a database. This is one of the first few Amazon re:Invents. It's my 10th where there was no new database announced. Right? >> No. >> So it was always add another one specially- >> I think they have enough. >> It's a great approach. They have enough, right? So it's a great approach to build something quick, which Amazon is all about. It's not so great when customers want to leverage things. And, ultimately, which I think with Selipsky, AWS is waking up to the enterprise saying, "I have all this different database and what is in them matters to me." >> Yeah. >> "So how can I get this better?" So no surprise between the two most popular database, Aurora and RDS. They're bring together the data with some out of the box parts. I think it's kind of, like, silly when Swami's saying, "Hey, no ETL.". (chuckles) Right? >> Yeah. >> There shouldn't be an ETL from the same vendor, right? There should be data pipes from that perspective anyway. So it looks like, on the overall value proposition database side, AWS is moving closer to the universal database on the Oracle side, right? Because, if you lift, of course, the universal database, under the hood, you see, well, there's different database there, different part there, you do something there, you have to configure stuff, which is also the case but it's one part of it, right, so. >> With that shift, talk about the value that's going to be in it for customers regardless of industry. >> Well, the value for customers is great, because when software vendors, or platform vendors, go in depth, you get more functionality, you get more maturity you get easier ways of setting up the whole things. You get ways of maintaining things. And you, ultimately, get lower TCO to build them, which is super important for enterprise. Because, here, this is the developer cloud, right? Developers love AWS. Developers are scarce, expensive. Might not be want to work for you, right? So developer velocity getting more done with same amount of developers, getting less done, less developers getting more done, is super crucial, super important. So this is all good news for enterprise banking on AWS and then providing them more efficiency, more automation, out of the box. >> Some of your customer conversations this week, talk to us about some of the feedback. What's the common denominator amongst customers right now? >> Customers are excited. First of all, like, first event, again in person, large, right? >> Yeah. >> People can travel, people meet each other, meet in person. They have a good handle around the complexity, which used to be a huge challenge in the past, because people say, "Do I do this?" I know so many CXOs saying, "Yeah, I want to build, say, something in IoT with AWS. The first reference built it like this, the next reference built it completely different. The third one built it completely different again. So now I'm doubting if my team has the skills to build things successfully, because will they be smart enough, like your teams, because there's no repetitiveness and that repetitiveness is going to be very important for AWS to come up with some higher packaging and version numbers.", right? But customers like that message. They like that things are working better together. They're not missing the big announcement, right? One of the traditional things of AWS would be, and they made it even proud, as a system, Jassy was saying, "If we look at the IT spend and we see something which is, like, high margin for us and not served well and we announced something there, right?" So Quick Start, Workspaces, where all liaisons where AWS went after traditional IT spend and had an offering. We haven't had this in 2019, we don't have them in 2020. Last year and didn't have it now. So something is changing on the AWS side. It's a little bit too early to figure out what, but they're not chewing off as many big things as they used in the past. >> Right. >> Yep. >> Did you get the sense that... Keith Townsend, from "The CTO Advisor", was on earlier. >> Yep. >> And he said he's been to many re:Invents, as you have, and he said that he got the sense that this is Amazon's chance to do a victory lap, as he called it. That this is a way for Amazon to reinforce the leadership cloud. >> Ja. >> And really, kind of, establish that nobody can come close to them, nobody can compete with them. >> You don't think that- >> I don't think that's at all... I mean, love Keith, he's a great guy, but I don't think that's the mindset at all, right? So, I mean, Jassy was always saying, "It's still the morning of the day in the cloud.", right? They're far away from being done. They're obsessed over being right. They do more work with the analysts. We think we got something right. And I like the passion, from that perspective. So I think Amazon's far from being complacent and the area, which is the biggest bit, right, the biggest. The only thing where Amazon truly has floundered, always floundered, is the AI space, right? So, 2018, Werner Vogels was doing more technical stuff that "Oh, this is all about linear regression.", right? And Amazon didn't start to put algorithms on silicon, right? And they have a three four trail and they didn't announce anything new here, behind Google who's been doing this for much, much longer than TPU platform, so. >> But they have now. >> They're keen aware. >> Yep. >> They now have three, or they own two of their own hardware platforms for AI. >> Right. >> They support the Intel platform. They seem to be catching up in that area. >> It's very hard to catch up on hardware, right? Because, there's release cycles, right? And just the volume that, just talking about the largest models that we have right now, to do with the language models, and Google is just doing a side note of saying, "Oh, we supported 50 less or 30 less, not little spoken languages, which I've never even heard of, because they're under banked and under supported and here's the language model, right? And I think it's all about little bit the organizational DNA of a company. I'm a strong believer in that. And, you have to remember AWS comes from the retail side, right? >> Yeah. >> Their roll out of data centers follows their retail strategy. Open secret, right? But, the same thing as the scale of the AI is very very different than if you take a look over at Google where it makes sense of the internet, right? The scale right away >> Right. >> is a solution, which is a good solution for some of the DNA of AWS. Also, Microsoft Azure is good. There has no chance to even get off the ship of that at Google, right? And these leaders with Google and it's not getting smaller, right? We didn't hear anything. I mean so much focused on data. Why do they focus so much on data? Because, data is the first step for AI. If AWS was doing a victory lap, data would've been done. They would own data, right? They would have a competitor to BigQuery Omni from the Google side to get data from the different clouds. There's crickets on that topic, right? So I think they know that they're catching up on the AI side, but it's really, really hard. It's not like in software where you can't acquire someone they could acquire in video. >> Not at Core Donovan. >> Might play a game, but that's not a good idea, right? So you can't, there's no shortcuts on the hardware side. As much as I'm a software guy and love software and don't like hardware, it's always a pain, right? There's no shortcuts there and there's nothing, which I think, has a new Artanium instance, of course, certainly, but they're not catching up. The distance is the same, yep. >> One of the things is funny, one of our guests, I think it was Tuesday, it was, it was right after Adam's keynote. >> Sure. >> Said that Adam Selipsky stood up on stage and talked about data for 52 minutes. >> Yeah. Right. >> It was timed, 52 minutes. >> Right. >> Huge emphasis on that. One of the things that Adam said to John Furrier when they were able to sit down >> Yeah >> a week or so ago at an event preview, was that CIOs and CEOs are not coming to Adam to talk about technology. They want to talk about transformation. They want to talk about business transformation. >> Sure, yes, yes. >> Talk to me in our last couple of minutes about what CEOs and CIOs are coming to you saying, "Holger, help us figure this out. We have to transform the business." >> Right. So we advise, I'm going quote our friends at Gartner, once the type A company. So we'll use technology aggressively, right? So take everything in the audience with a grain of salt, followers are the laggards, and so on. So for them, it's really the cusp of doing AI, right? Getting that data together. It has to be in the cloud. We live in the air of infinite computing. The cloud makes computing infinite, both from a storage, from a compute perspective, from an AI perspective, and then define new business models and create new best practices on top of that. Because, in the past, everything was fine out on premise, right? We talked about the (indistinct) size. Now in the cloud, it's just the business model to say, "Do I want to have a little more AI? Do I want a to run a little more? Will it give me the insight in the business?". So, that's the transformation that is happening, really. So, bringing your data together, this live conversation data, but not for bringing the data together. There's often the big win for the business for the first time to see the data. AWS is banking on that. The supply chain product, as an example. So many disparate systems, bring them them together. Big win for the business. But, the win for the business, ultimately, is when you change the paradigm from the user showing up to do something, to software doing stuff for us, right? >> Right. >> We have too much in this operator paradigm. If the user doesn't show up, doesn't find the click, doesn't find where to go, nothing happens. It can't be done in the 21st century, right? Software has to look over your shoulder. >> Good point. >> Understand one for you, autonomous self-driving systems. That's what CXOs, who're future looking, will be talked to come to AWS and all the other cloud vendors. >> Got it, last question for you. We're making a sizzle reel on Instagram. >> Yeah. >> If you had, like, a phrase, like, or a 30 second pitch that would describe re:Invent 2022 in the direction the company's going. What would that elevator pitch say? >> 30 second pitch? >> Yeah. >> All right, just timing. AWS is doing well. It's providing more depth, less breadth. Making things work together. It's catching up in some areas, has some interesting offerings, like the healthcare offering, the security data lake offering, which might change some things in the industry. It's staying the course and it's going strong. >> Ah, beautifully said, Holger. Thank you so much for joining Paul and me. >> Might have been too short. I don't know. (laughs) >> About 10 seconds left over. >> It was perfect, absolutely perfect. >> Thanks for having me. >> Perfect sizzle reel. >> Appreciate it. >> We appreciate your insights, what you're seeing this week, and the direction the company is going. We can't wait to see what happens in the next year. And, yeah. >> Thanks for having me. >> And of course, we've been on so many times. We know we're going to have you back. (laughs) >> Looking forward to it, thank you. >> All right, for Holger Mueller and Paul Gillan, I'm Lisa Martin. You're watching "theCube", the leader in live enterprise and emerging tech coverage. (upbeat music)

(bright music) >> Hello cloud computing friends and welcome back to theCUBE, where we are live from Las Vegas, Nevada, here at AWS re:Invent all week. My name is Savannah Peterson, very excited to be joined by Paul Gillan today. How are you doing? >> I'm doing great, Savannah. It's my first re:Invent. >> I was just going to ask you >> So it's quite an experience. >> If you've ever been to re:Invent. >> It's dazzling much like the sequins on your top. It's dazzling. >> Yes. >> It's a jam packed affair. I came to the COMDEX Conference for many years in Las Vegas, which was huge event and this really rivals it in terms of these crowd sizes. But I think there's more intensity here. There's more excitement. People are just jazzed about being here to the extent that I never saw at other computer conferences. >> I thought I would agree with you. It's my first re:Invent as well. I'm glad we could share this experience together. And the vibe, the pulse, I think being back in person is really contagious as well. Ooh, maybe the wrong word to use, but in a great way. The energy is definitely radiating between people here. I'll watch my words a little bit better. >> And in person we have with us Samuel Nicholls, the director of public cloud at Global Product Marketing at Veeam Software. Sam, is it Sam or Samuel? >> Depends if I'm in trouble, Paul. >> Savannah: But it depends on who's saying it out loud. >> Yeah, yeah. It's typically, Samuel is usually reserved for my mother, so- >> Yeah. >> (laughs) Well, Sam, thanks for joining us. >> We'll stick with Sam on the show. >> Yeah. >> So Veeam been a red hot company for several years. Really made its, uh, its reputation in the VMware world. Now you've got this whole-sail shift to the cloud, not that VMware is not important still, but how is that affecting, you're shifting with it, how is that affecting your role as a product manager and the business overall? >> Yeah, it's a fantastic question. Obviously Veeam was pioneered in terms of being the purpose-built backup and recovery company for VMware. And as these workloads are being transitioned from the data center into the cloud or just net new workloads being created in the cloud, there is that equal need for backup and recovery there. So it's incredibly important that we were able to provide a purpose-built backup and recovery solution for workloads that live in AWS as well. >> Paul: And how different is it backing up an AWS workload compared to a VMware workload? >> I think it depends on what kind of service a user is, is, is utilizing, right? There's infrastructure as a service, platform as a service, software as a service. And given the differences in what is exposed to that customer that can make backup and recovery quite challenging. So I would say that the primary thing that we want to look at is utilizing native snapshots is our first line of defense when it comes to backup and recovery, irrespective of what workload that right might be whether it's a virtual machine, Amazon EC2, some sort of database on Amazon RDS, a file share, so on. >> Savannah: I bet you're seeing a lot across verticals and across the industry given the support that you're giving customers. What are you seeing in the market and in customer environments? What are some of those trends? >> So I think the major trends that we highlight in our data protection trend support, which is a new update is coming very shortly in the new year, is- >> Savannah: We have to check that out. >> Yeah, absolutely. The physical server is on a decline within the data center. Virtualized workloads, namely VMware is relatively static, kind of flat. The real hockey stick is with the cloud workloads. And as I mentioned before, that is partially because workloads are being transitioned from physical to virtual machines to being cloud hosted but also we're creating more applications and the cloud has become lead de facto standard for new workloads. So you hear about cloud first initiatives, digital transformation, the cloud is central to that. >> You mentioned snapshotting, which is a relatively new phenomenon, although it's taken a hold rapidly, how does snapshotting work in the cloud versus in on your on-prem environment? >> Samuel: It's not wildly different at all. I think the snapshots is again, a great first line of defense for helping users achieve very low recovery point objectives. So the frequency that they can protect their data as well as very low recovery time objectives, how quickly that I can recover the data. Because that's why we're backing up, right? We need the ability to recover. However, snapshots certainly have their limitations as well. They are not independent of the workload that is being protected. So if there were to be some sort of cybersecurity event like ransomware that is prolific throughout pretty much every business, every vertical. When that snapshot is not independent, if the production system becomes compromised that snapshot's likely to be compromised as well. And then going back to the recovery piece, not going to have something to recover from. >> And it's not a one and done with ransomware. >> No. >> It's, yeah. So how, so what is the role that backup plays? I mean a lot of people, I feel like security is such a hot topic here in the show and just in general, attacks are coming in unique form factors for everyone. I mean, I feel like backup is, no pun intended, the backbone of a system here. How does that affect what you're creating, I mean? >> Yeah, absolutely. I think, like you say the backup is core to any comprehensive security strategy, right? I think when we talk about security, everyone tends to focus on the preventative, the proactive piece, stopping the bad guys from getting in. However, there is that remediative aspect as well because like you say, ransomware is relentless, right? You, you as a good guy have to pretty much fend off each and every single attack that comes your way. And that can be an infinite number of attacks. We're all human beings, we're fallible, right? And sometimes we can't defend against everything. So having a secure backup strategy is part of that remediative recovery component for a cybersecurity strategy is critical. And that includes things like encryption, immutability, logical separation of data and so forth. >> Paul: We know that ransomware is a scourge on-premises, typically begins with the end users, end user workstation. How does ransomware work in the cloud? And do the cloud providers have adequate protections against ransomware? Or can they? >> Samuel: Yeah, it's a, it's a fantastic question as well. I think when we look at the cloud, one of the common misconceptions is as we transition workloads to the cloud, we are transitioning responsibility to that cloud provider. And again, it's a misconception, right? It is a shared responsibility between the cloud provider in this case, AWS and the user. So as we transition these workloads across varying different services, infrastructure, platform, software as a service, we're always, always transitioning varying degrees of responsibility. But we always own our data and it is our responsibility to protect and secure that data, for the actual infrastructure components, the hardware that is on the onus of the cloud provider, so I'd say that's the major difference. >> Is ransomware as big a threat in the cloud as it is on-prem? >> Absolutely. There's no difference between a ransomware attack on-premises or in the cloud. Irrespective of where you are choosing to run your workloads, you need to have that comprehensive cybersecurity strategy in order to defend against that and ultimately recover as well if there's a successful attempt. >> Yeah, it's, ooh, okay. Let's get us out at the dark shadows real quick (laughs) and bring us back to a little bit of the business use case here. A lot of people using AWS. What do you think are some of the considerations, they should have when they're thinking about this, thinking about growing their (indistinct)? >> Well, if we're going to stick down the dark shadows, the cybersecurity piece. >> We can be the darkness. >> You and me kind of dark shadows business. >> Yeah, yeah. >> We can go rainbows and unicorns, nice and happy if you like. I think there's a number of considerations they need to keep up. Security is, is, is number one. The next piece is around the recovery as well. I think folks, when they, when we talk about backup and recovery, the focus is always on the backup piece of it. But again, we need to focus on why we're doing the backup. It's the recovery, it's the recovery component. So making sure that we have a clean verifiable backup that we're able to restore data from. Can we do that in a, in efficient and timely manner? And I think the other major consideration is looking at the entirety of our environments as well. Very few companies are a hundred percent sole sourced on a single cloud provider. It is typically hybrid cloud. It's around 80% of organizations are hybrid, right? So they have their on-premises data and they also have workloads running in one or multiple clouds. And when it comes to backup and recovery of all of these different infrastructures and environments, the way that we approach it is very different. And that often leads to multiple different point products from multiple different vendors. The average company utilizes three different backup products, sometimes as many as seven and that can introduce a management nightmare that's very complex, very resource intensive, expensive. So looking at the entirety of the environment and looking to utilize a backup provider that can cover the entirety of that environment while centralizing everything under a single management console helps folks be a lot more efficient, a lot more cost effective and ultimately better when it comes to data protection. >> Amazon and all cloud providers really are increasingly making regions transparent. Just at this conference, Amazon introduced failover controls from multiple multi-region access points. So you can, you can failover from one access from one region to another. What kind of challenges does that present to you as a backup provider? >> I don't think it represents any challenges. When we look at the native durability of the cloud, we look at availability zones, we look at multi-region failover. That is, that durability is ultimately founded on, on replication. And I wouldn't say that replication and backup, you would use one or the other. I would say that they are complimentary. So for replication, that is going to help with the failover scenario, that durability component. But then backup again is that independent copy. Because if we look at replication, if let's say the source data were to be compromised by ransomware or there was accidental deletion or corruption, that's simply going to be copied over to the target destination as well. Having that backup as an independent copy, again compliments that strategy as well. >> Paul: You need it in either, in any scenario. >> Samuel: In any scenario. >> I think the average person would probably say that backup is not the most exciting technology aspect of this industry. But, but you guys certainly made, build a great business on it. What excites you about what's coming in backup? What are the new technologies, new advancements that perhaps we haven't seen and productized yet that you think are going to change the game? >> I think actually what we offer right now is the most exciting piece which is just choice flexibility. So Veeam again is synonymous with VMware backup but we cover a multitude of environments including AWS, containerized workloads, Kubernetes physical systems and the mobility pieces is critical because as organizations look to act on their digital transformation, cloud first initiatives, they need to be able to mobilize their workloads across different infrastructures, maybe from on-premises into the cloud, one cloud to another, maybe it's cloud back to on-premises, 'cause we do also see that. That flexibility of choice is what excites me about Veeam because it's ultimately giving the users best in class data protection tool sets without any prescriptive approach from us in terms of where you should be running your workloads. That is the choice that you use. >> Yeah, Veeam is definitely more than VMware. We actually had a chance to chat with you all like KubeCon and CloudNativeCon in Detroit. So we, we've seen the multitude of things that you touch. I want to bring it back to something and something kind of fun because you talked a lot about the community and being able to serve them. It's very clear, actually I shouldn't say this, I shouldn't say it's very clear, but to me it appears clear that community is a big priority for Veeam. I just want to call this out 'cause this was one of the cooler pieces of swag. You all gave out a hundred massage guns. Okay, very hot topic. Hot Christmas gift for 2022. I feel like Vanna White right now. And, but I thought that I was actually really compelled by this because we do a swag segment on theCUBE but it's not just about the objects or getting stuff. It's really about who's looking out for their community and how are they saying thanks. I mean, swag is a brand activation but it's also a thank you and I loved that you were giving out massage guns to the AWS Heroes and Community Builders. >> Yep. >> What role does community play in the culture and the product development at Veeam? >> So community has always been at the heart of Veeam. If you have a look at pretty much every single development across all of our versions, across all of our products it's always did by the community, right? We have a wonderful Veeam forum where we got 400,000 plus users actively providing feedback on the product what they would like to see. And that is ultimately what steers the direction of the product. Of course market trends and technology chain. >> A couple other factors, I'm sure. >> A couple of other factors, but community is huge for us. And the same goes for AWS. So, you know, talking with the AWS Heroes, the Community Builders helps Veeam reach further into that, into that community and the AWS user base and empower those folks with data protection tools and massage guns, when your feet are tired from, you know, being standing on them all day in Vegas. >> (laughs) Yeah, well, I mean, everybody, everybody's working hard and it's nice to say, it's nice to say, thank you. So I love, I love to hear that and it's, it's clear from the breadth of products that you're creating, the ways that you're supporting your customers that you already, they care a lot about community. We have a new challenge on theCUBE this year at AWS re:Invent. Think of it as an Instagram reel of your thought leadership, your hot take on the show, key themes as we look into 2023. What do you think is the most important story or trend or thing going on here at the show? >> I think it's just the continuation of cybersecurity and the importance of backup as a comprehensive cybersecurity strategy. You know, some folks might say that secure backup is your last line of defense. Again, ransomware is relentless. These folks are going to keep coming and even if they're successful, it's not a one and done thing. It's going to happen again and again and again. So, you know, we have a look around the show floor, the presentations there is a huge cybersecurity focus and really just what folks should be doing as their best practice to secure their AWS environments. >> That's awesome. Well, Paul, any final, any final thoughts or questions? >> I just quickly, you've mentioned data security, you mentioned data protection and backup sort of interchangeably but they're not really the same thing, are they? I mean, what businesses do you see Veeam as being here? >> I would say that we are a data protection company because of, yes, there is backup, but there's also the replication component. There's the continuous data protection component where we've got, you know, near-zero RTOs and then we again look at the cybersecurity components of that. What can we do to really protect that data? So I would say that the two are different. Backup is a subset of data protection. >> Sam, thank you so much for being here with us on theCUBE. It's been a super insightful conversation. Hopefully we'll get you back soon and more of the teams, there seem to be celebrities here with us on theCUBE. Paul Gillan, thank you so much for being here with me. >> Pleasure Savannah. >> And I'm glad we get to celebrate our first re:Invent and most importantly, thank you to the audience for tuning in. Without you, we don't get to hang out here in fabulous Las Vegas, Nevada, where we're live from the show floor at AWS re:Invent. My name is Savannah Peterson with Paul Gillan. We're theCUBE and we are the leading source for high-tech coverage. (bright music)

(upbeat intro music) >> Good afternoon, fellow tech nerds. My name is Savannah Peterson, coming to you from theCube's Remote Studio here in Motown, Detroit, Michigan where we are at KubeCon. John, this is our 12th interview of the day. How are you feeling? >> I'm feeling fresh as the first interview. (Savannah laughs) As always. >> That delivery really implied a level of freshness. >> Let's go! No, this is only Day 1. In three days, reinvent. We go hardcore. These are great events. We get so much great content. The conversations are amazing. The guests are awesome. They're technical, they're smart, and they're making the difference in the future. So, this next segment about Scale MySQL should be awesome. >> I am very excited to introduce our next guest who actually has a Twitter handle that I think most people, at least of my gender in this industry would love to have. She is @ATechGirl. So you can go ahead and tweet her and tell her how great this interview is while we're live. Please welcome Deepthi Sigireddi. Thank you so much for being here with us. >> Thank you for having me. >> You're feeding us in. You've got two talks you're giving while we're here. >> Yes, yes. So tomorrow we will be talking about VTR, myself and one of the other maintainers of Vitess and on Friday we have the Vitess Maintainer Talk. All graduated projects get a maintainer talk. >> Wow, so you are like KubeCon VIP celebrity. >> Well, I hope so. >> Well, you're a maintainer and technical lead, also software engineer at the PlanetScale. But talk about the graduation process where that means to the project and the people involved. >> So Vitess graduated in 2019 and there are strict criteria for graduation and you don't just have to meet the minimum, you sort of have to over perform on the graduation criteria. Some of which are like there must be at least two large production deploys and people from those companies have to go in front of the CNCF committee that approves these things and say that, "Yes, this project is critical to our business." >> A lot of peer review, a lot of deployment success. >> Yes. >> Good consistency in the code. >> Deepthi: Community diversity. >> All that. >> All those things. >> Talk about the importance of this project. What is the top story that people should know about around the project? Why it exists, why it's important, why it's relevant, why it's cool. How would you answer that? >> So MySQL is now 30 years old and yet they are still- >> Makes me feel a little sidebar. (Deepthi laughs) Yeah. >> And yet even though there are many other newer databases, it continues to be used at many of the largest internet scale companies. And some of them, for example, Slack, GitHub, Square, they have grown to a level where they could not have if they had tried to do it with Vanilla MySQL that they started with, and the only reason they are where they are is Vitess. So that is I think the number one thing people should know about Vitess. >> And the origination story on notes say "Came from YouTube." >> Yes. So the way Vitess started was that YouTube was having problems with their MySQL deployment and they got tired of dealing with the site being down. So the founders of Vitess decided that they had to do something about it and they started building Vitess which started as a pretty small, relatively code-based with limited features, and over time they built charting and all of the other things that we have today. >> Well, this is exciting Savannah because we've seen this industry. Like with Facebook, when they started, everyone built their own stuff. MySQL was a great- >> Oh gosh, and everyone wanted to build it their way, reinventing the wheel. >> And MySQL was great. And then as it kind of broke when it grew, it got retrofitted. So, it was constantly being scaled up to the point where now you guys, if I get this right, said, "Hey, we're going to work on this. We're going to make it next-gen." So it's kind of like next-gen MySQL. Almost. >> Yes, yes. I would say that's pretty accurate, yeah. So there are still large companies which run their own MySQL and they have scaled it in their own way, but Vitess happens to be an open source way of scaling MySQL that people can adopt without having to build all of their own tooling around it. >> Speaking of that and growing, you just announced a new version today. >> Yes, yes. >> Tell us about that. >> The focus in this version was to make Vitess easier to use and to deploy. So in the past, there was one glaring gap in Vitess which was that Vitess did not automatically detect and repair MySQL level failures. With this release, we've actually closed that gap. And what that means for people using Vitess is that they will actually spend less time dealing with outages manually, or less human intervention, More automated recovery is what it means. The other thing we've released today is a new web UI. Vitess had a very old web UI, ugly, hard to maintain. Nobody liked it. But it was functional, except we couldn't add anything new to it because it was so old. So, the backend functionality kept advancing but the front end was kind of frozen. Now we have a next generation UI to which in upcoming releases we can add more and more functionality. >> So, it's extensible. They add things in. >> Deepthi: Oh yes, of course. Yeah. >> Awesome. What's the biggest thing that you like about the new situation? Is it more contributors are on board the UI? What's the fresh new impact that's happening in the community? What's getting you excited about with the current project? And the UI's great 'cause usability is important. >> Deepthi: Right. >> Scalability is important. >> I think Vitess solved the scalability problem way early and only now we are really grappling with the usability problem. So the hope and the desire is to make Vitess autopilot so that you reduce human intervention to a minimum once you deploy it. Obviously, you have to go through the process of deploying it. But once you've deployed it, it should just run itself. >> Runs at scale. So, the scale's huge? >> Deepthi: Yes. >> How many contributors are involved in the project? Can you give some numbers? Do you have any handy that you can speak to? >> Right. So, CNCF actually tracks these statistics for all the projects and we consolidated some numbers for the last two full calendar years, 2020 and 2021. We had over 400 contributors and 200 plus of them contributed code and the others contributed documentation issues, website changes, and things like that. So that gives- >> How about downloads? Download's good? >> Oh, okay. So we started publishing the current official Vitess Docker Image in 2018. And by October of 2020, we had about 3.8 million downloads. And by August of 2021, we had 5.2 million. And today, we have had over 10 million downloads- >> Wow! >> Of the main image. >> Starting to see a minute of that hockey stick that we all like to see. Seems like you're very clearly a community-first leader and it seems like that's in the PlanetScale and the test's DNA. Is that how the whole company culture views it? Would you say it's community-first business? >> PlanetScale is very much committed to Vitess as an open source project and to serving the Vitess community. So as part of my role at PlanetScale, some of the things I do are helping new contributors whether they are from PlanetScale or from outside PlanetScale. A number of PlanetScale engineers who don't work full-time on Vitess still contribute bug fixes and features to Vitess. We spend a significant amount of our energy helping users in our community Slack. The releases we do are mainly for the benefit of the community and PlanetScale is making those releases because for Planet Scale... Within PlanetScale, we actually do separate releases versus the public ones. >> One of the things that's coming up here at the show is deploying on Kubernetes. How does that look like? Everyone wants ease of use. Are you guys easy to use? >> Yes, yes. So PlanetScale also open sourced a Kubernetes operator for Vitess that people outside PlanetScale are using to run their production deployments of Vitess. Prior to that, there were Vitess users who actually built their own Kubernetes deployments of Vitess and they are still running those, but new users and new adopters of Vitess tend to use the Kubernetes operator that we are publishing. >> And you guys are the managed service for Vitess for the people that that's the business model for PlanetScale. >> Correct. So PlanetScale has a serverless database on demand which is built on Vitess. So if someone's starting something new and they just need a database, you sign up. It takes 30 seconds to get a database. Connect to it and start doing things with it. Versus if you are a large enterprise and you have a huge database deployment, you can migrate to PlanetScale, import all of your existing data, cut over with minimal downtime and then go, and then PlanetScale manages that. >> And why would they do that? What's the use case for that? Save time new development team or refactoring? >> Save time not being able to hire people with the skills to run it in-house. Not wanting to invest engineering resources in what businesses think is not their core competency. They want to focus on their business value. >> So, this database is a service in their whatever they're doing without adding more costs. >> Right. >> And speed. Okay, cool. How's that going? >> It's going well. >> Any feedback from customers in terms of why that there are any benefit statements you seek popping out? What are the big... What's the big aha when they... When people realize what they have here, what's the aha moment for them? Do they go, "Wow, this is awesome. It's so easy. Push a button. Migrate." Or is it... >> All of those. And people have actually seen cost savings when they've migrated from Amazon RDS to PlanetScale and we have testimonials from people who've said that, "It was so easy to use PlanetScale. Why would we try to do it ourselves?" >> It's the best thing a customer could say, right? We're all about being painkillers and solving some sort of problem. I think that that's a great opportunity to let you show off some of your customers. So, who is receiving this benefit? 'Cause I know PlanetScale specifically is for a certain style of business. >> Hmm. We have a list of customers on the website. >> Savannah: I was going to say you have a really- >> John: She's a software engineer. She's not marketing. >> You did sexy. >> You're doing a great job as much as marketing. >> So the reason I am bringing this up is because it's clear this is a solution for companies like Square, SoundCloud, Etsy, Jordan, and other exciting brands. So when you're talking about companies at scale, these companies are very much at scale, which is awesome. >> Yeah. >> What's next? What do you guys see the future for the project? >> I think we talked about that a little bit already. So, usability is a big thing. We did the new UI. It's not complete, right? Because over the last four years we've built more features into the backend which you can't yet access from the UI. So we want to be able for people to use things like online schema changes which is a big feature of Vitess. Doing schema changes without downtime from the UI. So, schema management from the UI. Vitess has something called VReplication which is the core technology that enables charting. And right now you can from the UI monitor your charting status, but you can't actually start charting from the UI. So more of the administrative functions we want to enable from the UI. >> John: Awesome. >> Last question. What are you personally most excited about this week being here with our wonderful community? >> I always enjoy being at KubeCon. This is my fifth or sixth in-person and I've done a couple of virtual ones. >> Savannah: Awesome. >> Because of the energy, because you get to meet people in person whom previously you've only met in Slack or maybe in a monthly community Zoom calls. We always have people come to our project booth. We have a project booth here for Vitess. People come to the company booth. PlanetScale has a booth. People come to our talks, ask questions. We end up having design discussions, architecture discussions. We get feedback on what is important to the people who show up here. That always informs what we do with the project in future releases. >> Perfect answer. I already mentioned that you can get a hold and in touch with Deepthi through her wonderful Twitter handle. Is there any other website or anything you want to shout out here before I do our close? >> vitess.io. V-I-T-E-S-S dot I-O is the Vitess website and planetscale.com is the PlanetScale website. >> Deepthi Sigireddi, thank you so much for being on the show with us today. John, thanks for keeping me company as always. >> You're welcome. >> And thank all of you for tuning into theCUBE. We will be here in Detroit, Michigan all week live from KubeCon and we hope to see you there. (gentle upbeat music)

>>Hello, everyone. Welcome to the cubes coverage here. New York city for AWS Amazon web services summit 2022. I'm John furrier, host of the cube with Dave ante. My co-host. We are breaking it down, getting an update on the ecosystem. As the GDP drops, inflations up gas prices up the enterprise continues to grow. We're seeing exceptional growth. We're here on the ground floor. Live at the Summit's packed house, 10,000 people. Eric Bradley's here. Chief STR at ETR, one of the premier enterprise research firms out there, partners with the cube and powers are breaking analysis that Dave does check that out as the hottest podcast in enterprise. Eric. Great to have you on the cube. Thanks for coming on. >>Thank you so much, John. I really appreciate the collaboration always. >>Yeah. Great stuff. Your data's amazing ETR folks watching check out ETR. They have a unique formula, very accurate. We love it. It's been moving the market. Congratulations. Let's talk about the market right now. This market is booming. Enterprise is the hottest thing, consumers kind of in the toilet. Okay. I said that all right, back out devices and, and, and consumer enterprise is still growing. And by the way, this first downturn, the history of the world where hyperscalers are on full pumping on all cylinders, which means they're still powering the revolution. >>Yeah, it's true. The hyperscalers were basically at this two sun system when Microsoft and an AWS first came around and everything was orbiting around it. And we're starting to see that sun cool off a little bit, but we're talking about a gradient here, right? When we say cool off, we're not talking to shutdown, it's still burning hot. That's for sure. And I can get it to some of the macro data in a minute, if that's all right. Or do you want me to go right? No, go go. Right. Yeah. So right now we just closed our most recent survey and that's macro and vendor specific. We had 1200 people talk to us on the macro side. And what we're seeing here is a cool down in spending. We originally had about 8.5% increase in budgets. That's cool down is 6.5 now, but I'll say with the doom and gloom and the headlines that we're seeing every day, 6.5% growth coming off of what we just did the last couple of years is still pretty fantastic as a backdrop. >>Okay. So you, you started to see John mentioned consumer. We saw that in Snowflake's earnings. For example, we, we certainly saw, you know, Walmart, other retailers, the FA Facebooks of the world where consumption was being dialed down, certain snowflake customers. Not necessarily, they didn't have mentioned any customers, but they were able to say, all right, we're gonna dial down, consumption this quarter, hold on until we saw some of that in snowflake results and other results. But at the same time, the rest of the industry is booming. But your data is showing softness within the fortune 500 for AWS, >>Not only AWS, but fortune 500 across the board. Okay. So going back to that larger macro data, the biggest drop in spending that we captured is fortune 500, which is surprising. But at the same time, these companies have a better purview into the economy. In general, they tend to see things further in advance. And we often remember they spend a lot of money, so they don't need to play catch up. They'll easily more easily be able to pump the brakes a little bit in the fortune 500. But to your point, when we get into the AWS data, the fortune 500 decrease seems to be hitting them a little bit more than it is Azure and GCP. I >>Mean, we're still talking about a huge business, right? >>I mean, they're catching up. I mean, Amazon has been transforming from owning the developer cloud startup cloud decade ago to really putting a dent on the enterprise as being number one cloud. And I still contest that they're number one by a long ways, but Azure kicking ass and catching up. Okay. You seeing people move to Azure, you got Charlie bell over there, Sean, by former Amazonians, Theresa Carlson, people are going over there, there there's lift over at Azure. >>There certainly is. >>Is there kinks in the arm or for AWS? There's >>A couple of kinks, but I think your point is really good. We need to take a second there. If you're talking about true pass or infrastructure is a service true cloud compute. I think AWS still is the powerhouse. And a lot of times the, the data gets a little muddied because Azure is really a hosted platform for applications. And you're not really sure where that line is drawn. And I think that's an important caveat to make, but based on the data, yes, we are seeing some kinks in the armor for AWS. Yes. Explain. So right now, a first of all caveat, 40% net score, which is our proprietary spending metric across the board. So we're not like raising any alarms here. It's still strong that said there are declines and there are declines pretty much across the board. The only spot we're not seeing a decline at all is in container, spend everything else is coming down specifically. We're seeing it come down in data analytics, data warehousing, and M I, which is a little bit of a concern because that, that rate of decline is not the same with Azure. >>Okay. So I gotta ask macro, I see the headwinds on the macro side, you pointed that out. Is there any insight into any underlying conditions that might be there on AWS or just a chronic kind of situational thing >>Right now? It seems situational. Other than that correlation between their big fortune 500, you know, audience and that being our biggest decline. The other aspect of the macro survey is we ask people, if you are planning to decline spend, how do you plan on doing it? And the number two answer is taking a look at our cloud spend and auditing it. So they're kind say, all right, you know, for the last 10 years it's been drunken, sail or spend, I >>Was gonna use that same line, you know, >>Cloud spend, just spend and we'll figure it out later, who cares? And then right now it's time to tighten the belts a little bit, >>But this is part of the allure of cloud at some point. Yeah. You, you could say, I'm gonna, I'm gonna dial it down. I'm gonna rein it in. So that's part of the reason why people go to the cloud. I want to, I wanna focus in on the data side of things and specifically the database. Let, just to give some context if, and correct me if I'm, I'm a little off here, but snowflake, which hot company, you know, on the planet, their net score was up around 80% consistently. It it's dropped down the last, you know, quarter, last survey to 60%. Yeah. So still highly, highly elevated, but that's relative to where Amazon is much larger, but you're saying they're coming down to the 40% level. Is that right? >>Yeah, they are. And I remember, you know, when I first started doing this 10 years ago, AWS at a 70%, you know, net score as well. So what's gonna happen over time is those adoptions are gonna get less and you're gonna see more flattening of spend, which ultimately is going to lower the score because we're looking for expansion rates. We wanna see adoption and increase. And when you see flattening a spend, it starts to contract a little bit. And you're right. Snowflake also was in the stratosphere that cooled off a little bit, but still, you know, very strong and AWS is coming down. I think the reason why it's so concerning is because a it's within the fortune 500 and their rate of decline is more than Azure right >>Now. Well, and, and one of the big trends you're seeing in database is this idea of converging function. In other words, bringing transaction and analytics right together at snowflake summit, they added the capability to handle transaction data, Mongo DB, which is largely mostly transactions added the capability in June to bring in analytic data. You see data bricks going from data engineering and data science now getting into snowflake space and analytics. So you're seeing that convergence Oracle is converging with my SQL heat wave and their core databases, couch base couch base is doing the same. Maria do virtually all these database companies are, are converging their platforms with the exception of AWS. AWS is still the right tool for the right job. So they've got Aurora, they've got RDS, they've got, you know, a dynamo DV, they've got red, they've got, you know, going on and on and on. And so the question everybody's asking is will that change? Will they start to sort of cross those swim lanes? We haven't seen it thus far. How is that affecting the data >>Performance? I mean, that's fantastic analysis. I think that's why we're seeing it because you have to be in the AWS ecosystem and they're really not playing nicely with others in the sandbox right now that now I will say, oh, Amazon's not playing nicely. Well, no, no. Simply to your point though, that there, the other ones are actually bringing in others at consolidating other different vendor types. And they're really not. You know, if you're in AWS, you need to stay within AWS. Now I will say their tools are fantastic. So if you do stay within AWS, they have a tool for every job they're advanced. And they're incredible. I think sometimes the complexity of their tools hurts them a little bit. Cause to your point earlier, AWS started as a developer-centric type of cloud. They have moved on to enterprise cloud and it's a little bit more business oriented, but their still roots are still DevOps friendly. And unless you're truly trained, AWS can be a little scary. >>So a common use case is I'm gonna be using Aurora for my transaction system and then I'm gonna ETL it into Redshift. Right. And, and I, now I have two data stores and I have two different sets of APIs and primitives two different teams of skills. And so that is probably causing some friction and complexity in the customer base that again, the question is, will they begin to expand some of those platforms to minimize some of that friction? >>Well, yeah, this is the question I wanted to ask on that point. So I've heard from people inside Amazon don't count out Redshift, we're making, we're catching up. I think that's my word, but they were kind of saying that right. Cuz Redshift is good, good database, but they're adding a lot more. So you got snowflake success. I think it's a little bit of a jealousy factor going on there within Redshift team, but then you got Azure synapse with the Synap product synapse. Yep. And then you got big query from Google big >>Query. Yep. >>What's the differentiation. What are you seeing for the data for the data warehouse or the data clouds that are out there for the customers? What's the data say, say to us? >>Yeah, unfortunately the data's showing that they're dropping a little bit whose day AWS is dropping a little bit now of their data products, Redshift and RDS are still the two highest of them, but they are starting to decline. Now I think one of the great data points that we have, we just closed the survey is we took a comparison of the legacy data. Now please forgive me for the word legacy. We're gonna anger a few people, but we Gotter data Oracle on-prem, we've got IBM. Some of those more legacy data warehouse type of names. When we look at our art survey takers that have them where their spend is going, that spends going to snowflake first, and then it's going to Google and then it's going to Microsoft Azure and, and AWS is actually declining in there. So when you talk about who's taking that legacy market share, it's not AWS right now. >>So legacy goes to legacy. So Microsoft, >>So, so let's work through in a little context because Redshift really was the first to take, you know, take the database to the cloud. And they did that by doing a one time license deal with par XL, which was an on-prem database. And then they re-engineered it, they did a fantastic job, but it was still engineered for on-prem. Then you along comes snowflake a couple years later and true cloud native, same thing with big query. Yep. True cloud native architecture. So they get a lot of props. Now what, what Amazon did, they took a page outta of the snowflake, for example, separating compute from storage. Now of course what's what, what Amazon did is actually not really completely separating like snowflake did they couldn't because of the architecture, they created a tearing system that you could dial down the compute. So little nuances like that. I understand. But at the end of the day, what we're seeing from snowflake is the gathering of an ecosystem in this true data cloud, bringing in different data types, they got to the public markets, data bricks was not able to get to the public markets. Yeah. And think is, is struggling >>And a 25 billion evaluation. >>Right. And so that's, that's gonna be dialed down, struggling somewhat from a go to market standpoint where snowflake has no troubles from a go to market. They are the masters at go to market. And so now they've got momentum. We talked to Frank sluman at the snowflake. He basically said, I'm not taking the foot off the gas, no way. Yeah. We, few of our large, you know, consumer customers dialed things down, but we're going balls to the >>Wall. Well, if you look at their show before you get in the numbers, you look at the two shows. Snowflake had their summit in person in Vegas. Data bricks has had their show in San Francisco. And if you compare the two shows, it's clear, who's winning snowflake is blew away from a, from a market standpoint. And we were at snowflake, but we weren't at data bricks, but there was really nothing online. I heard from sources that it was like less than 3000 people. So >>Snowflake was 1900 people in 2019, nearly 10,000. Yeah. In 2020, >>It's gonna be fun to sort of track that as a, as an odd caveat to say, okay, let's see what that growth is. Because in fairness, data, bricks, you know, a little bit younger, Snowflake's had a couple more years. So I'd be curious to see where they are. Their, their Lakehouse paradigm is interesting. >>Yeah. And I think it's >>And their product first company, yes. Their go to market might be a little bit weak from our analysis, but that, but they'll figure it out. >>CEO's pretty smart. But I think it's worth pointing out. It's like two different philosophies, right? It is. Snowflake is come into our data cloud. That's their proprietary environment. They're the, they think of the iPhone, right? End to end. We, we guarantee it's all gonna work. And we're in control. Snowflake is like, Hey, open source, no, bring in data bricks. I mean data bricks, open source, bring in this tool that too, now you are seeing snowflake capitulate a little bit. They announce, for instance, Apache iceberg support at their, at the snowflake summit. So they're tipping their cap to open source. But at the end of the day, they're gonna market and sell the fact that it's gonna run better in native snowflake. Whereas data bricks, they're coming at it from much more of an open source, a mantra. So that's gonna, you know, we'll see who look at, you had windows and you had apple, >>You got, they both want, you got Cal and you got Stanford. >>They both >>Consider, I don't think it's actually there yet. I, I find the more interesting dynamic right now is between AWS and snowflake. It's really a fun tit for tat, right? I mean, AWS has the S three and then, you know, snowflake comes right on top of it and announces R two, we're gonna do one letter, one number better than you. They just seem to have this really interesting dynamic. And I, and it is SLT and no one's betting against him. I mean, this guy's fantastic. So, and he hasn't used his war chest yet. He's still sitting on all that money that he raised to your point, that data bricks five, their timing just was a little off >>5 billion in >>Capital when Slootman hasn't used that money yet. So what's he gonna do? What can he do when he turns that on? He finds the right. >>They're making some acquisitions. They did the stream lit acquisitions stream. >>Fantastic >>Problem. With data bricks, their valuation is underwater. Yes. So they're recruiting and their MNAs. Yes. In the toilet, they cannot make the moves because they don't have the currency until they refactor the multiple, let the, this market settle. I I'm, I'm really nervous that they have to over factor the >>Valuation. Having said that to your point, Eric, the lake house architecture is definitely gaining traction. When you talk to practitioners, they're all saying, yeah, we're building data lakes, we're building lake houses. You know, it's a much, much smaller market than the enterprise data warehouse. But nonetheless, when you talk to practitioners that are actually doing things like self serve data, they're building data lakes and you know, snow. I mean, data bricks is right there. And as a clear leader in, in ML and AI and they're ahead of snowflake, right. >>And I was gonna say, that's the thing with data bricks. You know, you're getting that analytics at M I built into it. >>You know, what's ironic is I remember talking to Matt Carroll, who's CEO of auDA like four or five years ago. He came into the office in ma bro. And we were in temporary space and we were talking about how there's this new workload emerging, which combines AWS for cloud infrastructure, snowflake for the simple data warehouse and data bricks for the ML AI, and then all now all of a sudden you see data bricks yeah. And snowflake going at it. I think, you know, to your point about the competition between AWS and snowflake, here's what I think, I think the Redshift team is, you know, doesn't like snowflake, right. But I think the EC two team loves it. Loves it. Exactly. So, so I think snowflake is driving a lot of, >>Yeah. To John's point, there is plenty to go around. And I think I saw just the other day, I saw somebody say less than 40% of true global 2000 organizations believe that they're at real time data analytics right now. They're not really there yet. Yeah. Think about how much runway is left and how many tools you need to get to real time streaming use cases. It's complex. It's not easy. >>It's gonna be a product value market to me, snowflake in data bricks. They're not going away. Right. They're winning architectures. Yeah. In the cloud, what data bricks did would spark and took over the Haddo market. Yeah. To your point. Now that big data, market's got two players, in my opinion, snow flicking data, bricks converging. Well, Redshift is sitting there behind the curtain, their wild card. Yeah. They're wild card, Dave. >>Okay. I'm gonna give one more wild card, which is the edge. Sure. Okay. And that's something that when you talk about real time analytics and AI referencing at the edge, there aren't a lot of database companies in a position to do that. You know, Amazon trying to put outposts out there. I think it runs RDS. I don't think it runs any other database. Right. Snowflake really doesn't have a strong edge strategy when I'm talking the far edge, the tiny edge. >>I think, I think that's gonna be HPE or Dell's gonna own the outpost market. >>I think you're right. I'll come back to that. Couch base is an interesting company to watch with Capella Mongo. DB really doesn't have a far edge strategy at this point, but couch base does. And that's one to watch. They're doing some really interesting things there. And I think >>That, but they have to leapfrog bongo in my >>Opinion. Yeah. But there's a new architecture emerging at the edge and it's gonna take a number of years to develop, but it could eventually from an economic standpoint, seep back into the enterprise arm base, low end, take a look at what couch base is >>Doing. They hired an Amazon guard system. They have to leapfrog though. They need to, they can't incrementally who's they who >>Couch >>Base needs to needs to make a big move in >>Leap frog. Well, think they're trying to, that's what Capella is all about was not only, you know, their version of Atlas bringing to the cloud couch base, but it's also stretching it out to the edge and bringing converged database analytics >>Real quick on the numbers. Any data on CloudFlare, >>I was, I've been sitting here trying to get the word CloudFlare out my mouth the whole time you guys were talking, >>Is this another that's innovated in the ecosystem. So >>Platform, it was really simple for them early on, right? They're gonna get that edge network out there and they're gonna steal share from Akamai. Then they started doing exactly what Akamai did. We're gonna start rolling out some security. Their security is fantastic. Maybe some practitioners are saying a little bit too much, cuz they're not focused on one thing or another, but they are doing extremely well. And now they're out there in the cloud as well. You >>Got S3 compare. They got two, they got an S3 competitor. >>Exactly. So when I'm listening to you guys talk about, you know, a, a couch base I'm like, wow, those two would just be an absolute fantastic, you know, combination between the two of them. You mean >>CloudFlare >>Couch base. Yeah. >>I mean you got S3 alternative, right? You got a Mongo alternative basically in my >>Opinion. And you're going and you got the edge and you got the edge >>Network with security security, interesting dynamic. This brings up the super cloud date. I wanna talk about Supercloud because we're seeing a trend on we're reporting this since last year that basically people don't have to spend the CapEx to be cloud scale. And you're seeing Amazon enable that, but snowflake has become a super cloud. They're on AWS. Now they're on Azure. Why not tan expansion expand the market? Why not get that? And then it'll be on Google next, all these marketplaces. So the emergence of this super cloud, and then the ability to make that across a substrate across multiple clouds is a strategy we're seeing. What do you, what do you think? >>Well, honestly, I'm gonna be really Frank here. The, everything I know about the super cloud I know from this guy. So I've been following his lead on this and I'm looking forward to you guys doing that conference and that summit coming up from a data perspective. I think what you're saying is spot on though, cuz those are the areas we're seeing expansion in without a doubt. >>I think, you know, when you talk about things like super cloud and you talk about things like metaverse, there's, there's a, there, there look every 15 or 20 years or so this industry reinvents itself and a new disruption comes out and you've got the internet, you've got the cloud, you've got an AI and VR layer. You've got, you've got machine intelligence. You've got now gaming. There's a new matrix, emerging, super cloud. Metaverse there's something happening out there here. That's not just your, your father's SAS or is or pass. Well, >>No, it's also the spend too. Right? So if I'm a company like say capital one or Goldman Sachs, my it spend has traditionally been massive every year. Yes. It's basically like tons of CapEx comes the cloud. It's an operating expense. Wait a minute, Amazon has all the CapEx. So I'm not gonna dial down my budget. I want a competitive advantage. So next thing they know they have a super cloud by default because they just pivoted their, it spend into new capabilities that they then can sell to the market in FinTech makes total sense. >>Right? They're building out a digital platform >>That would, that was not possible. Pre-cloud >>No, it wasn't cause you weren't gonna go put all that money into CapEx expenditure to build that out. Not knowing whether or not the market was there, but the scalability, the ability to spend, reduce and be flexible with it really changes that paradigm entire. >>So we're looking at this market now thinking about, okay, it might be Greenfield in every vertical. It might have a power law where you have a head of the long tail. That's a player like a capital one, an insurance. It could be Liberty mutual or mass mutual that has so much it and capital that they're now gonna scale it into a super cloud >>And they have data >>And they have the data tools >>And the tools. And they're gonna bring that to their constituents. Yes, yes. And scale it using >>Cloud. So that means they can then service the entire vertical as a service provider. >>And the industry cloud is becoming bigger and bigger and bigger. I mean, that's really a way that people are delivering to market. So >>Remember in the early days of cloud, all the banks thought they could build their own cloud. Yeah. Yep. Well actually it's come full circle. They're like, we can actually build a cloud on top of the cloud. >>Right. And by the way, they can have a private cloud in their super cloud. Exactly. >>And you know, it's interesting cause we're talking about financial services insurance, all the people we know spend money in our macro survey. Do you know the, the sector that's spending the most right now? It's gonna shock you energy utilities. Oh yeah. I was gonna, the energy utilities industry right now is the one spending the most money I saw largely cuz they're playing ketchup. But also because they don't have these type of things for their consumers, they need the consumer app. They need to be able to do that delivery. They need to be able to do metrics. And they're the they're, they're the one spending right >>Now it's an arms race, but the, the vector shifts to value creation. So >>It's it just goes back to your post when it was a 2012, the trillion dollar baby. Yeah. It's a multi-trillion dollar baby that they, >>The world was going my chassis post on Forbes, headline trillion dollar baby 2012. You know, I should add it's happening. That's >>On the end. Yeah, exactly. >>Trillions of babies, Eric. Great to have you on the key. >>Thank you so much guys. >>Great to bring the data. Thanks for sharing. Check out ETR. If you're into the enterprise, want to know what's going on. They have a unique approach, very accurate in their survey data. They got a great market basket of, of, of, of, of data questions and people and community. Check it out. Thanks for coming on and sharing with. >>Thank you guys. Always enjoy. >>We'll be back with more coverage here in the cube in New York city live at summit 22. I'm John fur with Dave ante. We'll be right back.

(calm music) >> Hi everybody. We're here at VeeamON 2022. This is day two of the CUBE's continuous coverage. I'm Dave Vellante. My co-host is Dave Nicholson. A ton of energy. The keynotes, day two keynotes are all about products at Veeam. Veeam, the color of green, same color as money. And so, and it flows in this ecosystem. I'll tell you right now, Michael Cade is here. He's the senior technologist for product strategy at Veeam. Michael, fresh off the keynotes. >> Yeah, yeah. >> Welcome. Danny Allen's keynote was fantastic. I mean, that story he told blew me away. I can't wait to have him back. Stay tuned for that one. But we're going to talk about protecting containers, Kasten. You guys got announcements of Kasten by Veeam, you call it K10 version five, I think? >> Yeah. So just rolled into 5.0 release this week. Now, it's a bit different to what we see from a VBR release cycle kind of thing, cause we're constantly working on a two week sprint cycle. So as much as 5.0's been launched and announced, we're going to see that trickling out over the next couple of months until we get round to Cube (indistinct) and we do all of this again, right? >> So let's back up. I first bumped into Kasten, gosh, it was several years ago at VeeamON. Like, wow this is a really interesting company. I had deep conversations with them. They had a sheer, sheer cat grin, like something was going on and okay finally you acquire them, but go back a little bit of history. Like why the need for this? Containers used to be ephemeral. You know, you didn't have to persist them. That changed, but you guys are way ahead of that trend. Talk a little bit more about the history there and then we'll get into current day. >> Yeah, I think the need for stateful workloads within Kubernetes is absolutely grown. I think we just saw 1.24 of Kubernetes get released last week or a couple of weeks ago now. And really the focus there, you can see, at least three of the big ticket items in that release are focused around storage and data. So it just encourages that the community is wanting to put these data services within that. But it's also common, right? It's great to think about a stateless... If you've got stateless application but even a web server's got some state, right? There's always going to be some data associated to an application. And if there isn't then like, great but that doesn't really work- >> You're right. Where'd they click, where'd they go? I mean little things like that, right? >> Yeah. Yeah, exactly. So one of the things that we are seeing from that is like obviously the requirement to back up and put in a lot of data services in there, and taking full like exposure of the Kubernetes ecosystem, HA, and very tiny containers versus these large like virtual machines that we've always had the story at Veeam around the portability and being able to move them left, right, here, there, and everywhere. But from a K10 point of view, the ability to not only protect them, but also move those applications or move that data wherever they need to be. >> Okay. So, and Kubernetes of course has evolved. I mean the early days of Kubernetes, they kept it simple, kind of like Veeam actually. Right? >> Yeah. >> And then, you know, even though Mesosphere and even Docker Swarm, they were trying to do more sophisticated cluster management. Kubernetes has now got projects getting much more complicated. So more complicated workloads mean more data, more critical data means more protection. Okay, so you acquire Kasten, we know that's a small part of your business today but it's going to be growing. We know this cause everybody's developing applications. So what's different about protecting containers? Danny talks about modern data protection. Okay, when I first heard that, I'm like, eh, nice tagline, but then he peel the onion. He explains how in virtualization, you went from agents to backing up of VMware instance, a virtual instance. What's different about containers? What constitutes modern data protection for containers? >> Yeah, so I think the story that Danny tells as well, is so when we had our physical agents and virtualization came along and a lot of... And this is really where Veeam was born, right, we went into the virtualization API, the VMware API, and we started leveraging that to be more storage efficient. The admin overhead around those agents weren't there then, we could just back up using the API. Whereas obviously a lot of our competition would use agents still and put that resource overhead on top of that. So that's where Veeam initially got the kickstart in that world. I think it's very similar to when it comes to Kubernetes because K10 is deployed within the Kubernetes cluster and it leverages the Kubernetes API to pull out that data in a more efficient way. You could use image based backups or traditional NAS based backups to protect some of the data, and backup's kind of the... It's only one of the ticks in the boxes, right? You have to be able to restore and know what that data is. >> But wait, your competitors aren't as fat, dumb and happy today as they were back then, right? So it can't... They use the same APIs and- >> Yeah. >> So what makes you guys different? >> So I think that's testament to the Kubernetes and the community behind that and things like the CSI driver, which enables the storage vendors to take that CSI abstraction layer and then integrate their storage components, their snapshot technologies, and other efficiency models in there, and be able to leverage that as part of a universal data protection API. So really that's one tick in the box and you're absolutely right, there's open source tools that can do exactly what we're doing to a degree on that backup and recovery. Where it gets really interesting is the mobility of data and how we're protecting that. Because as much as stateful workloads are seen within the Kubernetes environments now, they're also seen outside. So things like Amazon RDS, but the front end lives in Kubernetes going to that stateless point. But being able to protect the whole application and being very application aware means that we can capture everything and restore wherever we want that to go as well. Like, so the demo that I just did was actually a Postgres database in AWS, and us being able to clone or migrate that out into an EKS cluster as a staple set. So again, we're not leveraging RDS at that point, but it gives us the freedom of movement of that data. >> Yeah, I want to talk about that, what you actually demoed. One of the interesting things, we were talking earlier, I didn't see any CLI when you were going through the integration of K10 V5 and V12. >> Yeah. >> That was very interesting, but I'm more skeptical of this concept, of the single pane of glass and how useful that is. Who is this integration targeting? Are you targeting the sort of traditional Veeam user who is now adding as a responsibility, the management of protecting these Kubernetes environments? Or are you at the same time targeting the current owners of those environments? Cause I know you talk about shift left and- >> Yeah. >> You know, nobody needs Kubernetes if you only have one container and one thing you're doing. So at some point it's all about automation, it's about blueprints, it's about getting those things in early. So you get up, you talk about this integration, who cares about that kind of integration? >> Yeah, so I think it's a bit of both, right? So we're definitely focused around the DevOps focused engineer. Let's just call it that. And under an umbrella, the cloud engineer that's looking after Kubernetes, from an application delivery perspective. But I think more and more as we get further up the mountain, CIS admin, obviously who we speak to the tech decision makers, the solutions architects systems engineers, they're going to inherit and be that platform operator around the Kubernetes clusters. And they're probably going to land with the requirement around data management as well. So the specific VBR centralized management is very much for the backup admin, the infrastructure admin or the cloud based engineer that's looking after the Kubernetes cluster and the data within that. Still we speak to app developers who are conscious of what their database looks like, because that's an external data service. And the biggest question that we have or the biggest conversation we have with them is that the source code, the GitHub or the source repository, that's fine, that will get your... That'll get some of the way back up and running, but when it comes to a Postgres database or some sort of data service, oh, that's out of the CI/CD pipeline. So it's whether they're interested in that or whether that gets farmed out into another pre-operations, the traditional operations team. >> So I want to unpack your press release a little bit. It's full of all the acronyms, so maybe you can help us- >> Sure. >> Cipher. You got security everywhere enhance platform hardening, including KMS. That's key- >> Yeah, key management service, yeah. >> System, okay. With AWS, KMS and HashiCorp vault. Awesome, love to see HashiCorp company. >> Yeah. >> RBAC objects in UI dashboards, ransomware attacks, AWS S3. So anyway, security everywhere. What do you mean by that? >> So I think traditionally at Veeam, and continue that, right? From a security perspective, if you think about the failure scenario and ransomware's, the hot topic, right, when it comes to security, but we can think about security as, if we think about that as the bang, right, the bang is something bad's happen, fire, flood, blood, type stuff. And we tend to be that right hand side of that, we tend to be the remediation. We're definitely the one, the last line of defense to get stuff back when something really bad happens. And I think what we've done from a K10 point of view, is not only enhance that, so with the likes of being able to... We're not going to reinvent the wheel, let's use the services that HashiCorp have done from a HashiCorp vault point of view and integrate from a key management system. But then also things like S3 or ransomware prevention. So I want to know if something bad's happened and Kasten actually did something more generic from a Veeam ONE perspective, but one of the pieces that we've seen since we've then started to send our backups to an immutable object storage, is let's be more of that left as well and start looking at the preventative tasks that we can help with. Now, we're not going to be a security company, but you heard all the way through Danny's like keynote, and probably when he is been on here, is that it's always, we're always mindful of that security focus. >> On that point, what was being looked for? A spike in CPU utilization that would be associated with encryption? >> Yeah, exactly that. >> Is that what was being looked- >> That could be... Yeah, exactly that. So that could be from a virtual machine point of view but from a K10, and it specifically is that we're going to look at the S3 bucket or the object storage, we're going to see if there's a rate of change that's out of the normal. It's an abnormal rate. And then with that, we can say, okay, that doesn't look right, alert us through observability tools, again, around the cloud native ecosystem, Prometheus Grafana. And then we're going to get insight into that before the bang happens, hopefully before the bang. >> So that's an interesting when we talk about adjacencies and moving into this area of security- >> We're talking to Zeus about that too. >> Exactly. That's that sort of creep where you can actually add value. It's interesting. >> So, okay. So we talked about shift left, get that, and then expanded ecosystem, industry leading technologies. By the way, one of them is the Red Hat Marketplace. And I think, I heard Anton's... Anton was amazing. He is the head of product management at Veeam. Is been to every VeeamON. He's got family in Ukraine. He's based in Switzerland. >> Yeah. >> But he chose not to come here because he's obviously supporting, you know, the carnage that's going on in Ukraine. But anyway, I think he said the Red Hat team is actually in Ukraine developing, you know, while the bombs are dropping. That's amazing. But anyway, back to our interview here, expanded ecosystem, Red Hat, SUSE with Rancher, they've got some momentum. vSphere with Tanzu, they're in the game. Talk about that ecosystem and its importance. >> Yeah, and I think, and it goes back to your point around the CLI, right? Is that it feels like the next stage of Kubernetes is going to be very much focused towards the operator or the operations team. The CIS admin of today is going to have to look after that. And at the moment it's all very command line, it's all CLI driven. And I think the marketplace is OpenShift, being our biggest foothold around our customer base, is definitely around OpenShift. But things like, obviously we are a longstanding alliance partner with VMware as well. So their Tanzu operations actually there's support for TKGS, so vSphere Tanzu grid services is another part of the big release of 5.0. But all three of those and the common marketplace gives us a UI, gives us a way of being able to see and visualize that rather than having to go and hunt down the commands and get our information through some- >> Oh, some people are going to be unhappy about that. >> Yeah. >> But I contend the human eye has evolved to see in color for a very good reason. So I want to see things in red, yellow, and green at times. >> There you go, yeah. >> So when we hear a company like Veeam talk about, look we have no platform agenda, we don't care which cloud it's in. We don't care if it's on-prem or Google Azure, AWS. We had Wasabi on, we have... Great, they got an S3 compatible, you know, target, and others as well. When we hear them, companies like you, talk about that consistent experience, single pane of glass that you're skeptical of, maybe cause it's technically challenging, one of the things, we call it super cloud, right, that's come up. Danny and I were riffing on that the other day and we'll do that more this afternoon. But it brings up something that we were talking about with Zeus, Dave, which is the edge, right? And it seems like Kubernetes, and we think about OpenShift. >> Yeah. >> We were there last week at Red Hat Summit. It's like 50% of the conversation, if not more, was the edge. Right, and really true edge, worst cases, use cases. Two weeks ago we were at Dell Tech, there was a lot of edge talk, but it was retail stores, like Lowe's. Okay, that's kind of near edge, but the far edge, we're talking space, right? So seems like Kubernetes fits there and OpenShift, you know, particularly, as well as some of the others that we mentioned. What about edge? How much of what you're doing with container data protection do you see as informing you about the edge opportunity? Are you seeing any patterns there? Nobody's really talking about it in data protection yet. >> So yeah, large scale numbers of these very small clusters that are out there on farms or in wind turbines, and that is definitely something that is being spoken about. There's not much mention actually in this 5.0 release because we actually support things like K3s,(indistinct), that all came in 4.5, but I think, to your first point as well, David, is that, look, we don't really care what that Kubernetes distribution is. So you've got K3s lightweight Kubernetes distribution, we support it, because it uses the same native Kubernetes APIs, and we get deployed inside of that. I think where we've got these large scale and large numbers of edge deployments of Kubernetes and that you require potentially some data management down there, and they might want to send everything into a centralized location or a more centralized location than a farm shed out in the country. I think we're going to see a big number of that. But then we also have our multi cluster dashboard that gives us the ability to centralize all of the control plane. So we don't have to go into each individual K10 deployment to manage those policies. We can have one big centralized management multi cluster dashboard, and we can set global policies there. So if you're running a database and maybe it's the same one across all of your different edge locations, where you could just set one policy to say I want to protect that data on an hourly basis, a daily basis, whatever that needs to be, rather than having to go into each individual one. >> And then send it back to that central repository. So that's the model that you see, you don't see the opportunity, at least at this point in time, of actually persisting it at the edge? >> So I think it depends. I think we see both, but again, that's the footprint. And maybe like you mentioned about up in space having a Kubernetes cluster up there. You don't really want to be sending up a NAS device or a storage device, right, to have to sit alongside it. So it's probably, but then equally, what's the art of the possible to get that back down to our planet, like as part of a consistent copy of data? >> Or even a farm or other remote locations. The question is, I mean, EVs, you know, we believe there's going to be tons of data, we just don't.. You think about Tesla as a use case, they don't persist a ton of their data. Maybe if a deer runs across, you know, the front of the car, oh, persist that, send that back to the cloud. >> I don't want anyone knowing my Tesla data. I'll tell you that right now. (all laughing) >> Well, there you go, that one too. All right, well, that's future discussion, we're still trying to squint through those patterns. I got so many questions for you, Michael, but we got to go. Thanks so much for coming to theCUBE. >> Always. >> Great job on the keynote today and good luck. >> Thank you. Thanks for having me. >> All right, keep it right there. We got a ton of product talk today. As I said, Danny Allan's coming back, we got the ecosystem coming, a bunch of the cloud providers. We have, well, iland was up on stage. They were just recently acquired by 11:11 Systems. They were an example today of a cloud service provider. We're going to unpack it all here on theCUBE at VeeamON 2022 from Las Vegas at the Aria. Keep it right there. (calm music)

(upbeat music) >> Oracle is in the midst of an acceleration of its product cycles. It really has pushed new capabilities across its database, the database platforms, and of course the cloud in an effort to really maintain its position as the gold standard for cloud database. We've reported pretty extensively on Exadata, most recently the X9M that increased database IOPS and throughput. Organizations running mission critical OLTP, analytics and mix workloads tell us that they've seen meaningfully improved performance and lower costs, which you expect in a technology cycle. I often say if Oracle calls you out by name it's a compliment and it means you've succeeded. So just a couple of weeks ago, Oracle turned up the heat on MongoDB with a Mongo compatible API, in an effort to persuade developers to run applications in a autonomous database and on OCI, Oracle cloud infrastructure. There was a big emphasis by Oracle on acid compliance transactions and automatic scaling as well as access to multiple data types. This caught my attention because in the early days of no SQL, there was a lot of chatter from folks about not needing acid capability in the database anymore. Funny how that comes around. And anyway, you see Oracle investing, they spend money in R&D We've always said that`, they're protecting their moat. Now in social I've seen some criticisms like Oracle still is not adding enough new logos, and Oracle of course will dispute that and give you some examples. But to me what's most impressive is the big name customers that Oracle gets to talk in public. Deutsche Bank, Telephonic, Experian, FedEx, I mean dozens and dozens and dozens. I work with a lot of companies and the quality of the customers Oracle puts in front of analysts like myself is very very high. At the top of the list I would say. And they're big spending customers. And as we said many times when it comes to mission critical workloads, Oracle is the king. And one of the executives behind the success is a longtime Cube alum, Juan Loaiza who's executive vice president of mission critical technologies at Oracle. And we've invited him back on today to talk about some news and Oracle's latest developments and database, Juan welcome back to the show and thanks for coming on today and talking about today's announcement. >> I'm very happy to be here today with you. >> Okay, so what are you announcing and how does this help organizations particularly with those existing Exadata cloud at customer installations? >> Yeah, the big thing we're announcing is our very successful cloud at customer platform. We're extending the capabilities of our autonomous database running on it. And specifically we're allowing much smaller configurations so customers can start small and grow with our autonomous database on our cloud customer platform. >> So let's get into granularity a little bit and double click on this. Can you go over how customers, carve up VM clusters for different workloads? What's the tangible benefit to them? >> Yeah, so it's pretty straightforward. We deploy our Cloud@Customer system anywhere the customer wants it, let's say in their data center. And then through our cloud APIs and GUIs they can carve up into pieces into basically VMs. They can say, Hey, I want a VM with eight CPUs to do this, I want a VM with 20 CPUs to that, I want a 500 CPUVM to do something else. And that's what we call a VM cluster because in Cloud@Customer, it is a highly available environment. So you don't just get one VM, you get a cluster of highly available VMs. So you carve it up. You hand it out to different aspects of a company. You might have development on one, testing on another one, some production sales on one VM, marketing on a different VM. And then you run your databases in there and that's kind of how it works and it's all done completely through our GUI and it's very, very simple 'cause they use it the same cloud APIs and GUIs that we use in the public cloud. It is the same APIs and GUIs that we use in the public cloud. >> Yeah, I was going to say sounds like cloud. So what about prerequisites? What do customers have to do to take advantage of the new capabilities? Can they run it on an Exadata cloud a customer that they installed a couple years ago? Do they have to upgrade the hardware? What migration pain is involved? >> Yeah, there's no pain, so it's just, (coughs) excuse me. I can take their existing system, they get our free software update and they can just deploy autonomous database as a VM in their existing Exadata cloud system. >> Oh nice okay what's the bottom line dollars? Our audience are always interested in cutting costs. It's one of the reasons they're moving to the cloud for example. So how does autonomous database on VM clusters, on Exadata Cloud at Customer? How does it help cut their cost? >> Well, it's pretty straightforward. So previous to this a customer would have to have dedicated a system to either autonomous database or to non autonomous data. So you have to choose one together. So on a system by system basis, you chose I want this thing autonomous, or I don't want it autonomous. Now you carve in the VMs and say for this VM I want that autonomous for that VM I want to run a regular database managed database on there. So lets customers now start small with any size they want. They could start with two CPUs and run an autonomous database and that's all they pay for is the two CPUs that they use. >> Let's talk a little about traction. I mean, I remember we covered the original Exadata announcement quite a long time ago and it's obviously evolved and taken many forms. Look, it's hard to argue that it hasn't been a big success. It has for Oracle and your target customers. Does this announcement make Exadata cloud a customer more attractive for smaller companies. In other words, does it expand the team for ADB? And if so, how? >> Yeah, absolutely. I mean our Exadata cloud platform is extremely successful. We have thousands of deployments, we have on our data platform we have about almost 90% of the global fortune 100 and thousands of smaller customers. In the cloud we have now up to 40% of the global 100 a hundred biggest companies in the world running on that. So it's been extremely successful platform and cloud a customer is super key. A lot of customers can't move their data to the public cloud. So we bring the public cloud to them with our cloud customer offering. And so that's the big customer is the fortune hundred but we have thousands of smaller customers also. And the nice thing about this offering is we can start with literally two CPUs. So we can be a very small customer and still run our autonomous data based on our cloud customer platform. >> Well, everybody cares about security and governance. I mean, especially the big guys, but the little guys that in many ways as well they want the capabilities of the large companies but they can't necessarily afford it. So I want to talk about security in particular governance and it's especially important for mission-critical apps. So how does this all change the security in governance paradigm? What do customers need to know there? >> Yeah, so the beauty of autonomous database which is the thing that we're talking about today is Oracle deals with all the security. So the OS, the hardware, firmware, VMs, the database itself all the interfaces to the VM, to the database all that is it's all done by Oracle. So, which is incredibly important because there's a constant stream of security alerts that are coming out and it's very difficult for customers to keep up with this stuff. I mean, it's hard for us and we have thousands of engineers. And so we take that whole burden away from customers. And you just don't have to think about it, we deal with it. So once you deploy an autonomous database it is always secure because anytime a security alert comes out, we will apply that and we do it in an online fashion also. So it's really, particularly for smaller customers it's even harder because to keep up with all the security that you you need a giant team of security experts and even the biggest customers struggle with that and a small customer's going to really struggle. There's just two, you have to look at the entire stack, all the different components switches, firmware, OS, VMs, database, everything. It's just very difficult to keep up. So we do it all and for small cut, they just can't do it. So really they really need to partner with a company like Oracle that has thousands of engineers that can keep up with this stuff. >> It's true what you say, even large customers this CSOs will tell you that lack of talent, lack of skill sets. They just don't have enough people and so even the big guys can't keep up. Okay, I want you to pitch me as though I'm a developer, which I'm not, but we got a lot of developers in our community. We'll be Cube con next month in Valencia, sell me on why a developer should lean into ADB on Exadata cloud as a customer? >> Yeah, it's very straightforward. So Oracle has the most advanced database in the industry and that's widely recognized by database analysts and experts in the field. Traditionally, it's been hard for a developer to use it because it's been hard to manage. It's been hard to set up, install, configure, patch, back up all that kind of stuff. Autonomous database does it all for you. So as a developer, you can just go into our console, click on creating a database. We ask you four questions, how big, how many CPUs how much storage and say, give your password. And within minutes you have a database. And at that point you can go crazy and just develop. And you don't have to worry about managing the database, patching the database, maintaining the security and the database backing up to all that stuff. You can instantly scale it. You can say, Hey, I want to grow it, you just click a button, take, grow it to much any size you want and you get all the mission critical capabilities. So it works for tiny databases but it is a stock exchange quality in terms of performance, availability, security it's a rock solid database that's super trivial. So what used to be a very complex thing is now completely trivial for a developer. So they get the best of both worlds, they get everything on the database side and it it's trivial for them to use. >> Wow, if you're doing all that stuff for 'em are they going to do on their weekends? Code? (chuckles) >> They should be developing their application and add value to their company that's kind of what they should focus on. And they can be looking at all sorts of new technologies like JSON and the database machine learning in the database graph in the database. So you can build very sophisticated applications because you don't have to worry about the database anymore. >> All right, let's talk about the competition. So it's always a topic I like to bring up with you. From a competitive perspective how is this latest and instantiation of Exadata cloud a customer X9M how's this different from running an AWS database service for instance on outpost, or let's say I want to run SQL server on Azure Stack or whatever Microsoft's calling it these days. Give us the competitive angle here. >> Yeah, there kind of is no real competition. So both Amazon and Microsoft have an at customer solution but they're very primitive. I mean, just to give you an example like Amazon doesn't run any of their premier database offerings at customers. So whether it's Aurora Redshift, doesn't run just plane does not run. It's not that it runs badly or it's got limited, just does not run. They can't run Oracle RDS on premise and same thing with Microsoft. They can't run Azure SQL, which is their premier database on their act customer platform. So that kind of tells you how limited that platform is when even their own premier offerings doesn't run on it. In contrast, we're running Exadata with our premier autonomous database. So it's our premier platform that's in use today by most of the biggest, banks, telecom to retailers et cetera in the world, thousands of smaller customers. So it's super mission critical, super proven with our premier cloud database, which is autonomous theory. So it couldn't be more black and white, this is a case where it's there really is no competition in the cloud of customer space on the database side. >> Okay, but let me follow up on that, Juan, if I may, so, okay. So it took you guys a while to get to the cloud, it's taken them a while to figure it on-prem. I mean, aren't they going to eventually sort of get there? What gives you confidence that you'll be able to to keep ahead? >> Well, there's two things, right? One is we've been doing this for a long time. I mean, that's what Oracle initially started as an on-prem and our Exadata platform has been available for over a decade. And we have a ton of experience on this. We run the biggest banks in the world already, it's not some hope for the future. This is what runs today. And our focus has always been a combination of cloud and on-prem their heart's not really in the on-prem stuff they really like. Amazon's really a public cloud only vendor and you can see from the result, it's not you can say, they can say whatever they want but you can see the results. Their outpost platform has been available for several years now and it still doesn't even run their own products. So you can kind of see how hard they're trying and how much they really care about this market. >> All right, boil it down if you just had a few things that you'd tell someone about why they should run ADB on Exadata cloud at customer, what would you say? >> It's pretty simple, which is it's the world's most sophisticated database made completely simple, that's it? So you get a stock exchange level database, you can start really small and grow and it's completely trivial to run because Oracle is automated everything within our autonomous data we use machine learning and a lot of automation to automate everything around the database. So it's kind of the best of both worlds. The best possible database starts as small as you want and is the simplest database in the world. >> So I probably should have asked you this while I was pushing the competitive question but this may be my last question, I promise. It's the age old debate It rages on, you got specialized databases kind of a right tool for the right job approach. That's clearly where Amazon is headed or what Oracle refers to is converge database. Oracle says its approach is more complete and "simpler." Take us through your thinking on this and the latest positioning so the audience can understand it a bit better. >> Yeah, so apps aren't what they used to business apps, data driven apps aren't what they used to be. They used to be kind of green screens where you just entered data. Now everyone's a very sophisticated app, they want to be have location, they want to have maps, they want to have graph in there. They want to have machine learning, they want machine learning built into the app. So they want JSON they want text, they want text search. So all these capabilities are what a modern app has to support. And so what Oracle's done is we provided a single solution that provides everything you need to build a modern app and it's all integrated together. It's all transactional. You have analytics built into the same thing. You have reporting built into the same thing. So it has everything you need to build a modern app. In contrast, what most of our competitors do is they give you these little solutions, say, okay here you do machine learning over here, you do analytics over there, you do JSON over here, you do spatial over here you do graph over there. And then it's left a developer to put an app together from all these pieces. So it's like getting the pieces of a card and having to assemble it yourself and then maintain it for the rest of your life, which is the even harder part. So one part upgrades, you got to test that. So of other piece upgrade or changes, you got to test that, you got to deal with all the security problems of all these different systems. You have to convert the data, you have to move the data back and forth it's extraordinarily complicated. Our converge database, the data sits in one place and all the algorithms come to the data. It's very simple, it is dramatically simpler. And then autonomous database is what makes managing it trivial. You don't really have to manage anything more because Oracle's automated the whole thing. >> So, Juan, we got a pretty good Cadence going here. I mean I really appreciate you coming on and giving us these little video exclusives. You can tell by again, that Cadence how frequently you guys are making new announcements. So that's great, congrats on yet another announcement. Thanks for coming back in the program appreciate it. >> Yeah, of course we invest heavily in data management. That's our core and we will continue to do that. I mean, we're investing billions of dollars a year and we intend to stay the leaders in this market. >> Great stuff and thank you for watching the Cube, your leader in enterprise tech coverage, this is Dave Vellante we'll see you next time.

>>Hello and welcome to the AWS partners showcase season one, episode two. I'm your host of the cube John ferry. We're here with two great guests who John Kumar, CEO of and Sabina Joseph, the general manager of AWS. Welcome to the show. Welcome to welcome to the cube, >>John. Good to see you >>Again. Great to see both of you both cube. Alumna's great to see how the businesses is going, going very well. Cloud scale, continuing to dominate Columbia is doing extremely well. Tell us more about what's going on in Columbia. What's your mission? What kinds of use cases are you seeing? Napa John, that's helping you guys keep your growth trajectory and solve your customer problems. >>Yeah. Firstly, thank you, John. Thank you, Sabina. Great to be here is a backup as a service platform. That's built natively on AWS for AWS, and we do support other use cases beyond AWS. But our primary mission is to basically deliver, you know, a ransomware data protection solution, you know, on AWS for AWS customers. Right? So if we think about it, you know, one of the things that's, you know, typically holding back any company to put mission critical workloads on a fantastic platform, a public cloud platform like AWS is to make sure that the data is protected in the event of any attack. And it's also done with extreme amount of simplicity, right? So that nobody is doing the heavy lift of doing backup themselves, right? So that's what really drew me or provides. It's a service. It's a turnkey service that provides, you know, data protection on AWS, whatever. >>Well, you're a frequent cube alumni. We're always talking about the importance of that, but I want to ask you this year more than ever, you're seeing it at the center of the conversation built in from day one, you're seeing a lot more threats, certainly mentioned ransomware and more there's more and more online attacks that's impacting this particular area more than ever before. Can you comment on what your focus has been this year around that? >>Yeah, I see it. If you think about tumor's evolution, our primary mission has been to go and protect every data source, but guess what? Right with more and more move to the public cloud and you look just AWS is journey and that pioneer in public cloud going from, you know, whatever 3 billion in revenues, 10 years ago to north of 70 billion run rate today, there's so much of data that is in the public cloud and the, and the most important thing that customers need is they want to free themselves from going and protecting this data themselves. Right? And, and there's a lot of scale in these environments, right? If you look at customers running hundreds of thousands of AWS accounts across every region on AWS, and if you give them that kind of flexibility and that kind of scale, what they want is give me a turnkey solution that just allows me to go and protect all of these workloads running across all of these regions in a service that takes the data out of my accounts separately in an air gap fashion, right. And that's really what we basically provide. And that's what we focused on over the last 12 months. Right? So if you look at what we have done is we've gone after every important service on AWS TC to EBS RDS, S3, dynamo, sequel databases, and other databases running on top of BC too. So now that becomes the comprehensive set of things that somebody needs to use to really deliver an application on top of the public cloud. And that's where we want for, >>And the growth has been there and the results on Amazon because of the refactoring has been huge. Can you share any examples of some successes that you've had with, with the AWS refactoring and all that good stuff going on? >>Yeah. I mean, I think that what we have seen is, you know, customers that basically told us that before you guys existed, we had to go and build these things ourselves, right. Again, you know, they had all the, the, the blocks to go and do it themselves, but it was so much of a heavy lift to go and do it themselves. And again, they didn't want to be in a, you know, in that business. So, so what we have done essentially for, and we have, you know, we have some joint customers at a pretty massive scale that basically have said that, okay, let me just use your solution to protect my critical assets. Like, you know, things, you know, sitting in S3 and really, you know, we'll use gloomy as a, as a >>Yeah, I think that's a great example of the refactoring Sabina. Gotta, I gotta ask you, you obviously you're at the center of this. You have your hand on the wheel of the partnerships and all the innovators out there. The growth of AWS just has been spectacular because there's value being created. Again, companies are refactoring their business on the cloud and you're at the center of it. So talk about the partnership with Clooney. Can you tell us how it all started and where it's going? >>Yeah, thanks for having me here, John, and good to see you again, Fujian, if I'm not mistaken for John, we met each other at the San Francisco summit, the AWS San Francisco summit, actually I believe it was in 2016 or 2017. You can correct me if I'm wrong here, but yes, I think so. It was, it was in the 8% a month of April. I still remember it. And that's when, you know, you kind of mentioned to me about and this modern backup as a service solution that you were creating, you're still in stealth mode. So you couldn't talk a lot about it. And B started to engage deeply on the partnership, right from 2017. And initially we were kind of focused around helping Colombia build a solution using our well-architected review. And then as soon as we all came out of stealth mode, we started to engage more deeply around deeper integrations and also on go to market activities. >>As you know, AWS has a very prescriptive approach to our partnerships. So we started to work with around the five pillars of security, reliability, cost optimization, performance, and operational excellence to really help them tune the solution on AWS. And we also started to engage with our service teams and I have to thank Paul John and his team here. They really embraced those deeper and broader integrations, many services that Pooja mentioned, but also specifically want to mention S3 EBS. And our Columbia was also a launch partner for AWS outpost when AWS in fact, launched outpost. So I want to kind of commend CLU, CLU MEO, and the entire team kind of embracing this technology and innovation and this modern backup as a service approach. And also also embracing how we want to focus on the five key pillars that I mentioned. >>And that's a great example of success when you ride the wave, which I talk about the ACLU, Colombia trends in the data protection, because one of the things that you pointed out earlier is the ransomware. Okay. That's a big one, right? That's a big, hot area. How, how is the cloud, first of all, how is that going? And then how has the cloud equation changed the ransomware defense and protection piece of it? >>Yeah. Now I just, I wonder I had a little bit on what Sabina mentioned before I answered the question, John, if you don't mind. Sure. I think that collaboration is where is the reason why we are here today, right? Like if you think about it, like we were the first design partners to go and build, you know, the EBS direct API, right. And we work closely with the EBS teams, not just for the API, but the cost structure of it. How would somebody like us use it? So we are at the bleeding edge of some of these services that we are using and that has enabled us, you know, to be where we are today. So again, thank you very much to be enough for this fantastic partnership. And again, there's so much to go and do to really go and nail this in a, in a, in a, in a great way on, on the public cloud. >>So now coming back to your question, John, you know, fundamentally, if you see right, you know, what happened is when, when, when customers move to the public cloud, you know, right there, you know, the ease of use with which, you know, AWS provides these services, right? And the consumption of these services actually drives some amazing behavior, right? Where people actually want to go and build, build, build, and build. But then it comes a time where somebody comes in and says, okay, you know, are you compliant? Right. You know, do you have the right compliance in place? You have all these accounts that you have, but what is running in each of these accounts, you have visibility in those accounts. And are these accounts that the data in these accounts is this gap, right? This is getting air gap in the same region, or does it need to be across regions? >>Right. You know, I'm in the east, do I need to, you know, have an air gap in the west and so on and so forth. Right? So all of these, you know, confluence of all these things come in and by the, all these problems existed in on-premise world, they get translated in, in the public cloud, where do I need to replicate my data, doing it to back it up? Do I need air gapped in a, like an on-prem world? You had a data domain of plans, which was separate from your primary storage for a reason, same similar something similar now needs to happen here for compliance reasons and for ransomware reason. So a lot of parallels here is just that here we are, it almost feels like, you know, as they say, right, the more things changed. The more they remain the same. That's what it is in the public cloud again. >>Well, that's a good point. I mean, let's take that example of on premises versus the cloud. Also, the clouds got more scale too, by the way. So now you've got regions, this is a common problem that customers are having, you can build your own and, or use solutions, but if you don't get ahead of it, the compliance question can bite you in the, you know what, because you then got to go back and retrofit everything. So, so that's kind of what I hear a lot on my end is like, okay, I want to be compliant from day one. I want to have an answer when asked, I don't want to have to go to old techniques that don't fit the cloud. That comes up a lot. What's your answer to that? >>Yeah, no, no. We were pretty much right. I think it's like, you know, when it, when it comes to compliance and all of these things, you know, people at the end of the day are looking for that same foundation of, of things. The same questions are asked for an encryption. You know, you know, I is my data where it needs to be when it needs to be right. What is my recovery point? Objective? What is my recovery time objective? All of these things basically come together. And now, as you said, it's just the scale that you're dealing is, is extremely different in the cloud and the, and the services, right? The easier it is that, you know, it is to use these services. And especially what AWS does, it makes it so easy. So compelling that same ease of use needs to get translated with a SAS service, like what we are doing with data protection, right? That that ease of use is very important. You have to preserve that sanctity >>Sabina. Let's get back to you. You mentioned earlier about the design partner, that benefits for Colombia. Now let's take it to the next level. As customers really realize they have a problem, they need solutions and you're on the AWS side. So you gotta have the answers for the customers. You've got to put people together, make things work. There's a variety of things that you guys offer. What are some of the different facets of the ISV or the partner programs that you offer to partners like Clooney, you know, that they can benefit from? >>Absolutely John, we believe in a win-win approach to the partnerships because that's what makes partnerships durable over time. We're always striving to do better here. And we continue to broaden our investments. As you know, John, the AWS management team, right from Adam Phillipsky, our CEO down firmly believe that partners are critical to our success, our longterm success, and as partners like CLU MEO work to lean in with us with more investment resources, our technology innovation. We also ensure that we are doing our part by providing value back to Cleo about a few years ago, as you might recall, right. We really did a lot of investment in our sales team on the AWS side. Well, one of the tanks me and also our partners observed is while we were making investments in the AWS sales team, I don't think we were doing a great job at helping our partners with reaching out to those customers. >>What we call as co-sale and partners gave us feedback on this. We are very partner and customer feedback driven, and we introduced in fact, a new role called the ISP success manager, ISS, who are basically embedded in our field. And they work with partners to help them close opportunities. And also net new opportunities are we've also in 2020. I believe that re-invent, we launched the ISB accelerate program whereby we offer incentives to the AWS field team to work with our partners to close existing opportunities and also bring in net new opportunities. So all of this has led to closer collaboration in the field between both our field teams, Muir's field team and our field team, but also accelerated mutual customer wins. I'm not saying that we are doing everything great. We still have a long ways to go. And we are constantly getting feedback from cluneal and also some of our other key partners, and we'll continue to get better at it. But I think the role of the ISV success manager and also the ISP accelerate program has been key to bringing in cold cell success. >>Well, John, what's your take on, is this a good partnership for you? I mean, see, the wave of Vegas has got the growth numbers. You mentioned that, but from a partnership standpoint, you're closing business, they got scale. Is it working? How do you organize your company to take advantage of these benefits? Can you share your thoughts? >>Absolutely not. We have embraced the ecosystem wholeheartedly 100%, but if you think about it, what we have done is look at our offering on AWS marketplace. There's an example, right? We are the only company I would say in our domain, obviously that routes our entire business through AWS marketplace. Whether obviously we get a lot of organic benefit from AWS marketplace, people go and search for a solution and from your shows up, and obviously they go and onboard self onboard themselves, and guess what? We let them self onboard themselves. And we rely on AWS's billing automatically. So you don't need to talk to us. You can just get billed automatically in your AWS bill and you get your data protection solution. Or if you directly reached out to us, guess what we do. We actually route you through AWS marketplace. All the onboarding is just to one place and it's a fantastic experience. >>So we have gone like all in, on that experience and completely like, you know, internalized that that's the right way to do things. And of course, thanks to, you know, Sabina's team and the marketplace team to create that platform so that we could actually plug it into it. But that's the kind of benefits that we have that we have, you know, taken advantage of a DWI. That's one example, another example that Sabina mentioned, right, which is the whole ACE program. We put a ton of registrations on AIS and with all the wins that we get on AWS, they could broadcast it to the sellers. So that creates its own vicious cycle in terms of more coming into the pipeline and more closing in. So, so these are just two small examples, but there's other examples that we look at our recent press release, where AWS, you know, when we, when we launched yesterday data protection and backup, the GM of AWSs three supported us in the press release. So there's things like that, that it's a, it's a fantastic collaboration. That's working really well for our joint customers. Sorry. >>And tell us something about the partnership between 80 of us, including, you know, that people might not be aware of some of the things that Poojan said that they're different out there that, that are, co-selling go marketing, that you guys offer people you guys work together on. >>Yeah. The, the ISV accelerate program that was created, it was really created with partners like Klunier in mind, our SAS partners. I think that that is something very, very unique between our partnership and, you know, I, I want to double click on what Poojan said, which is riding their opportunities through marketplace, right? All of their opportunities. That is something pretty unique. They understand the richness of the platform and also how customers are procuring software today in this world. And they've embraced that. And we really appreciate that. And I want to say, you know, another thing about Qumulo is they're all in on AWS, which is another unique thing. There are not a lot of, I would say all in partnerships in my world and I manage infrastructure, business apps, applications, and industry partnerships from the Americas globally. And all of those things are very, very unique in our partnership, which has led to success. Right. We started very, very early stage when Columbia was in stealth mode in 2017 and look where we've come today. And it's really kudos to Paul, John and his entire team for believing in the partnership for leaning in with us and for placing that trust with us. >>Awesome. Pooja, any final words you'd like to share for folks out there about the conversation and what's going on in Columbia? >>Yeah, no, absolutely. You know, as I said, I think we have been fortunate to be very early adopters of all these technologies and go and really build what a true cloud native solution has to be. Right. And, and again, right, you know, this is what customers are really looking for. And people are looking for, you know, at least on the data protection side, you know, ransomware air gap solution, people are looking for a solution natively built on the cloud because that's the only way a solution can deliver something at the scale and the cost structure that is needed to have, you know, a data protection solution in the public cloud. So, so this has been just a fantastic thing end to end, you know, for us overall. And we really look forward to, you know, going, you know, doing much more with AWS as we essentially go and scale, >>I have to ask, but before we, before we go, cause you're the CEO of the company and founder having all that backend infrastructure from Amazon, just on the resources, great. It creates a market for your product, but also the sales piece, you know, they got the marketplace, you mentioned, that's a big expense that you don't have to carry, you know, and you get revenue and top line. I mean, that's an impact for startups out there and growing companies. That's a pretty big deal. What's your, what's your advice to folks out there who are trying to think about the buy versus use the leverage of the, of the marketplace, which is, which is at large scale, because as a CEO, you're, you've got to make these decisions. What's your opinion on that? >>It's not, it's not as, as easy as I make it sound to do your own part. You know, AWS is, is, is, is huge, right? It's huge. And so we have to do our part to educate everybody within the, you know, even the AWS seller base to make sure that they internalize the fact that this is the right solution for the customers, for our joint customers, right? So we have to do that all day long. So there's no running away the no shortcut to everything, but obviously AWS does its part to make it very, as easy as possible, but there's a lot of heavy lifting we still have to do. And I think that'll only become easier and easier over the next few years >>And Sabina your takeout at AVS. You've got a great job. You were with all the hot growth companies. This is the big wave we're on right now with the cloud next generation clouds here, a lot of opportunities. >>Absolutely. And it's, and it's thanks to Pooja and, and partners like Lumeo that really understand what it takes to build a cloud native solution because it's part of it is building. And part of it is the co-selling go-to-market engine and embracing both of that is critical to success. >>Well, thank you both for coming on this journey here on the cube, as part of the showcase, push on. Great to see you to being a great to see you as well. And thanks for sharing that insight. Appreciate it. >>Thank you very much. >>Okay. AWS partners showcase speeding innovation with AWS. I'm John Ford, your host of the cube. Thanks for watching.

>>Hello, everyone. Welcome to the cubes presentation of the AWS partner showcase. This is season one, episode two. I'm your host, John furry with the cube. I'm joined by two cube alumni as Andy Langston, SVP and GM at Veem and Sabina Joseph, the general manager of technology partners at AWS. We're here talking about speeding the innovation with AWS. Welcome to the show. >>Ready to meet you >>And good to see you, Andy again. >>Great to have you guys back on. I hope you guys are doing well. Great to see both of you Veem. Obviously we've been covering you guys for a long time. You got your VIMANA event coming up in person, which is great. Congrats on the continued success of the company and the product you guys have always been all in on AWS. We've been covering for many, many years. Andy, what's the innovation going on now at Veem? Lots of lots happening, lots going on. What's the new innovation. >>Well, I think, you know, clearly people are in, you know, when we talk to people they're interested in, in ransomware, so ransomware protection, we they're interested in a hybrid cloud hybrid. Um, you know, AWS in particular, we get a lot of interest there. Um, clearly modern data protection, uh, what we're doing in office 365, people are looking at all those things >>And what's the, the platform, uh, approach that you guys have with AWS. You guys have a broad range. It's not just the classic. I call it the green classic solution. That's also a good product. What's some of the new platform advantages you guys got going on with the cloud native with AWS. >>Well, you know, look we are, our strategy is to protect as many AWS services as possible, you know, and, and, you know, from the ECE to EBS, S3, RDS, uh, VMC, and many of the services that they're coming out with. And in many times they come to us and say, Hey, you know, these are important to us. We'd like you to, to support these. So clearly we're, um, we're focused on those, uh, Kubernetes workloads is, is a newer set of workloads on AWS. That we're a very interested, we made an acquisition and have a product called, uh, Kasten that we've been investing in and working with AWS with their, uh, uh, EKS anywhere. So very excited. >>Great. So being on the partnership, you guys, it's growing a lot's going on. Can you tell us more about how Veeam and abs AWS are jointly helping customers? >>Yeah. As, um, as both of, you know, right. Data is exploding. And, uh, that means, you know, we have to keep backing up this data and finding new ways to back up this data because people are stepping away from the traditional backup methods, tape libraries, secondary storage sites and things like that. And they're backing up data into the cloud. And we AWS offers a number of different storage services, data transfer methods and networking solutions, which provide unmatched your ability, reliability, security. And of course, uh, AWS and Veem have been partnering together enough for quite a number of years and the cost effective. And so you mentioned that Veem has on AWS really enables customers to have offsite storage solutions, providing that physical separation between their on premises, primary data, and also utilizing the pay as you go cloud economics. So we have a great collaboration and, you know, beam has a great solution on AWS and they're constantly innovating and providing capabilities for our customers. Just like Andy said, providing as many capabilities for our services to back up, >>Andy, the volume of data I'll say is always the story. Every year, the volume is tsunami of data. It's getting worse it's every day. Um, and as you got more cloud scale, you guys have been doing a lot integration. You guys always have, you have demanding customers, you have a lot of customers actually. So as you leverage Amazon for data protection, the security conversation is front and center these days. Can you give us an update on how you guys are doing, uh, the data protection security in the cloud with AWS? That's, that's, um, that's hot with your customers, >>You know, it's a great, it's a great comment. You know, you've talked about a lot of customers. Veem has over 400,000 customers now it's, it's truly extraordinary when you think about the size and scope and scale. And if you think, uh, my belief is a majority, almost all of them will tear up two and move their data up into the cloud at some point in our, in the next few years. And so we've just, I think we've described the surface and we're moving hack, you know, hundreds of petabytes or more per year up to the cloud at the same time when I make customer executive calls. It's kind of interesting. A lot of times you think they're going to want to talk about backup and disaster recovery. They want to talk about security. And when this first started happening, I thought, Hey, why don't you talk to your security vendor now? >>And what I realized was that data protection is front and center because of the, we just, we just published a study where a number jumped out at me, 71% of the thousands of people that responded said that they had already been a victim of, or had had a ransomware attack. It's a staggering number. And, um, so, you know, when we look at our relationship with Amazon and we look at the integration we've done around what we call cloud during that's moving, are moving data up to object storage. AWS has a capability called immutable data sets. And so that allows you affords you some great protection against ransomware as an example. And that's one of the areas that we're investing in very heavily. And by the way, our mutual customers are backing up and restoring with Veem and we're doing it on AWS and, and, uh, the data volumes are exploding, I think, because of that. Yeah. >>You know, it's interesting. And you made me have a throwback for, you know, 10 years ago, we used to talk about backup and recovery. And you know, the big thing back then was, was the conversation was don't think of backup as a, as a last minute thing, think of it at the front end, it was always kind of an afterthought and a, of the it decision makers. And you mentioned that security comment about call your security vendor. It's almost the scripts has flipped backup and recovery is the security solution. And so it's not, it's not an afterthought. This is 10 years ago. It was the primary message. It's the primary thought. So when you talk about automated tiering, that's kind of a networking thing. It's like, policy-based hearing. I mean, I mean, if you go back 10 years and we're talking, policy-based hearing, you were like, what? So this is a really different dynamic. And I want you guys to comment because this is the, this is the market right now. This is with the flip, the script has flipped. >>Yeah. Sabina. What do you, what, what do you from y'all's perspective kind of in, in your technology, partnerships, storage vendors, Veem security, what, what do you w what do you see? >>Well, I think that there is an interplay here because I think customers are looking at various ways, right? When I look at those five cybersecurity framework, right? First is identifying what you need to protect, protecting it. And then that's a very important step of, out of those five steps is recovery, right? How do you get your business back to normal? But you cannot do that if you are not protecting and backing up your data. And that's where our partnership comes in. Right? So I believe that all of those five stages in the NIST cybersecurity framework kind of go together and be in place nicely into the very critical phase of recovery. Would you agree, Andy? >>I would. You know, and, and I look at, um, you know, when you're doing a recovery and your gut, your secure backups and AWS, it's, it's like your last line of defense, you know, beam and AWS deliver a mutable backups and has three tiers through S3 object lock integration. And I think that's, that's pretty much, you know, even if a ransomware attack is successful, we can, we can ensure that the backup data hadn't been changed and encrypted or deleted. And, uh, that's pretty exciting, you know, for customers and prospects, they're really worried about this. And I think the teamwork and the, the, the partnership between the two companies to build a solution like this is pretty awesome. >>Yeah. Let me, let me just double, double click on that for a second. You mentioned it got a lot of customers. Ransomware does not discriminate with the size of the company. It could be, it could be a hospital school. It could be a big company. Ransomware is bad, and we see that, and it's a great conversation. And how do you take that solution out to the customers? You got hundreds of thousands of customers. So Sabine, I guess the question is, how is this 80 of us in Veem work together? There's this channel first concept you guys are talking about, tell us about how you guys work together, because there's millions of customers who want this, and you guys actually have hundreds of thousands of customers that Veem, how do you get the customers to leverage that, the relationship and what can you bring to them? >>Yeah, I'll give you like four numbers, right? So AWS has millions of customers and we have, um, hundred thousand partners across 150 countries. Now Veem has, as Andy mentioned, right, has over 400,000 customers and 35,000 partners worldwide. So somewhere in these four numbers, we all intersect both of us intersect both on those customers and also on those partners. And one of the initiatives that my team is heavily focused on is triangulating between the partners that Veeam has. We have, and also our technology partnership. And how can we provide value to our customers by bringing together these partners together with AWS Veeam and Veeam is a V it's a hundred percent channel driven business, and they know how to do this. That is why we are heavily partnered with them to see what we can do for our customers through our mutual partner. >>And he wants you to weigh in here, you know, the channel business, it's gotta be easy, it's got to add value. And I got to wrap services around it. That's what partners love. Well, how does this work? How does that work? >>Well, I, I think to extend beyond what, what did take, what Sabina had said is, you know, we have kind of been subsetted. Our partners are the ones that, that do business with AWS and, and which is a exploding number of partners. And so they have a relationship database. We have a relationship at S and we have this solution set that have, are of interest to our customers through these partners. And AWS has customers through these partners. And so a lot of times we'll share, um, information and customers, uh, information on, around, um, how we can kind of go to these customers who are both AWS customers and Veem customers and market, this joint solution protect them from ransomware. >>And how's it been going so far? What's your, what's your assessment? >>It's been fantastic. I think the, I think one of the, the, the real proof points is that we've moved, uh, over a half a petabyte of data, you know, uh, recently up into their cloud. And, uh, you know, that says that people not only are using the solution, but they're, uh, they're actually delivering on it. >>Well, why got you here, Andy, I want to ask you for the, all the people watching the customers, what's the biggest change that's happening in this market right now. Again, I love this shift that we're seeing backup and recovery. Isn't a point solution anymore. It's the solution it's baked in, and everyone's talking about this, it's integrated in, it's not, it's, it's totally front and center. What's the big change that customers should be thinking about now as they move forward. And, uh, obviously ransomware is still front and center. That's not going away anytime soon. What's the big thing to focus on for customers? >>Well, I think, you know, I always say, you know, listen to the customer and focus on what their specific needs are, right? You can assume, obviously in the business war and everybody, everybody has a backup solution. And, uh, so you're not trying to create a market there, but like I said, you know, people are very focused on security. They're focused on cost, they're focus on skillset or lack of skill sets, right? I mean, we have a shortage of skills in the industry. So we try to make our products easy to use. We try to work with our partners, putting AWS to deliver the best solution we can for our customers. And, uh, you know, I think we have the broadest invest, you know, ransomware protection, uh, and recovery in the storage space. And so we're very focused on that, leveraging all of our technologies across the platforms, physical, virtual Kubernetes, uh, type environments. >>And you have this and you get the beam on event coming up and that's going to be good in person. Right. That's a confirmed, >>It's a, it's a, it's a hybrid yet. In-person and virtual. >>Awesome. Great to see you guys in person. So being a, for the folks, watching the Amazon partnerships, as you guys scale up these, these partnerships and take it the next level, what's your, what's your closing comment. Yes. >>Yeah. I also want to say, write something that I should mention, right. We miss also invested in AWS marketplace. So it's not just the direct consulting partners and the partners that I mentioned, the a hundred thousand and 35,000, right. They, customers can also purchase beam on AWS marketplace through consulting partner, private offers. And that's why Viva's embraced many of these aspects to try to help our customers and continue to grow that 400,000 customer base, which is a pretty phenomenal number. >>Yeah. I've always been impressed with beam's customer base and they've got a very loyal base as well. I point that out and give props to the VM team. Andy closing comments for you, the V natives relationship, how would you summarize that? >>I'd say it's fantastic. You know, years ago it started as just a normal technology partnership. You know, now we're an advanced technology partner with storage competency, numerous programs like APN, uh, customer engagement. We're a marketplace seller. And I would say that it's not only that, but, but customers can take advantages of their, um, EDP with AWS to purchase on the marketplace and get credits against that. And our partners can as well. That's a, that's a very important thing because we're seeing more and more interest in that today. Uh, we're a public sector partner with them. We're an ISV accelerate SAS revenue recognition program. We're, we're, uh, I think we're checking a lot of boxes, but really taking advantage of it. The last thing I would say is, uh, I've known Sabina for quite a few years now. And I think it's the people relationships in the two companies that make this work. >>We have a lot of people, a lot smarter than me on the, on the speeds and feeds here. But at the end of the day, um, Sabina has a team of people that work with us on a, on a, almost a daily basis to solve customer problems. Right. We get people calling in all the time. How do I make Veem work on AWS? How do I get AWS solutions to work with theme? And our job is to make it as easy as possible because we both believe, uh, that customers, they say customer first. I always say, customer always are always right, but, but, but, but you know, at the end of the day, that's what makes this >>Yeah. Customer is always right. Customer obsession, working backwards from the customer fucking customer first Sabina. This is really interesting. This is a good point. I just come quick, go back to you real quick. This integration of relationships and also cloud technology integration is a big theme this year, post re-invent. Your thoughts >>Absolutely means, um, uh, to be candid. Uh, one of the goals that me and my team take is how do we bring technology partners together to add more value to our customers in end to end solutions, along with technology partners and consulting partners. So that is a huge focus for us because we need to do that in order to scale, not just for each other, but also for our customers and bring that, bring together meaningful, comprehensive end to end solutions. >>That's awesome. Andy, great to see you. We'll see at Veem on as well, coming up for the Veem show and your conference. You've been conference hybrid conference in person and virtual and digital to be in a great to see you again. Thanks for sharing all the great updates. And this is the season two. It's all about the data and the innovations with AWS. I'm John for your host of the cube season one episode, two of the AWS partner showcase. Thanks for watching.

>>And welcome to this special cube conversation. I'm John for a, your host of the cube. We're here in Palo Alto, California, and I'm here with a very special guest coming down from Seattle remotely into the cube studios is the leader at AWS Amazon web services, the vice president of database analytics and machine learning Swami. Great to see you cube alumni recently taking over the database business at AWS as a leader. Congratulations. And thanks for coming on the cube. >>Hey, my pleasure to be here, John, very excited to talk to you. >>Yeah. We've had many conversations on the cube and also in person and also online around all the major mega trends. You've had your hand in all the action, going back to your days when you were in school learning and, and writing papers. And 10 years ago, Amazon web services launched AWS dynamo, DB, fast, flexible, no SQL database that everyone loves today, which has inspired a generation of what I would call database distributing cloud scale, single digit millisecond performance at scale. And again, the key scale. And again, this is 10 years ago, so it seems like yesterday, but you guys are celebrating and your name was on the original paper with CTO Verner. Vogel's your celebrity. Congratulations. >>Thank you. Not sure about the celebrating part, but I'm very excited. At least I played a hand in building such an amazing technology that has enabled so many amazing customers along the way as well. So >>Trivia on the, on the paper as you were an intern at AWS, so you're getting your PhD. And then since, since rising through the ranks and involved in a lot of products over the years, and then leading the machine learning and AI, which is now changing the game at the industry level, but I got to ask you getting back to the story here. A lot of customers have built amazing things on top of dynamo DB, not to mention lots of other AWS and Amazon tech riding on it. Can you share some of the highlights that came out of the original paper? And so with some examples, because I think this is a point in time, 10 years ago, where you start to, so the KickUp of cloud scale, not just, just for developers and building startups, you're really starting to see the scale rise. >>Yeah, I actually, I mean, as you probably know, based on what he read to explain the Genesis of dynamo DB itself had to explain the Genesis of how Amazon got into building the original dynamo, right? And this was during the time when miner, I joined Ron esteem as an intern and, and Amazon was one of the pioneers in pushing the boundary of scale. And a year over year, our Q4 holiday season tends to be really, really bad for all the right reasons. We all want our holiday shopping done during that time. And you want to be able to scale your website, arters fulfillment centers, all of them at that time. And those are the times around 2005. And the answer is when people think our database, they think of a single database server that actually runs on a box and has a certain characteristics and does a scale and availability and whatnot. >>And it's usually relational. And then when we had a major disruption during Q4 that's when yeah, ask ourselves the question, why are we actually using a relational database for some of these things when they really didn't need the data model complexity of relational database. And normally I would say most companies where to actually ask an intern or a few engineers who are early in the career saying like, what the hell are you suggesting? Just go away. But Amazon being enabling Buddhists to build what they want. And they actually let us start reimagining what a database or our scale could look like. And that led to dynamo. And since she unstained mine, then we migrated from an traditional relational database stair this one for some of the amazon.com services. And then I moved on to actually start building some butts off our storage service and then our managed relational database service, I explicitly remember. >>And one of our customer advisory board, we're just the set off some of our leading customers who actually give us feedback on roadmap. Another son, Don, who's the CEO and chief geek of spunk bargain faker. And him actually looking at the Trinity me, I was starting in the corner and saying like you all, both tomorrow and why do I need to keep shotting my, my sequel database and reshooting assigned scaling. And this is the time when the state of the art in most databases were around. Like, you start sharding your relational database and constantly reshaping. And this is when most websites are starting to experience the kind of scale which we consider a normal month. During those times it was mostly, most companies used to have a single relational database backend and start scaling that way. And that conversation led entirely under duress, unaided read, lot of AWS leaders and myself saying like, Hey, what is a cloud database reimagined without the hampering SQL look like? And that led us to start building dynamo DB, but just a key value database at that time. Now we support document might've too, but that single digit millisecond latency at any scale imagine. So >>I think about that time at that time, 10 years ago, when you were having this conversation and I know the smug mug and I, he said, he's in totally geek and he's, he's good to point that out. You also have Netflix as customers too. I'd like to hear how that's evolved, but, but I think back at the time, if you look back then I got to ask you most people we've talked about this before. No one database rules, a world that's now standard people now don't see one database back then it was a one database kind of mindset back then. Yeah. And then you had that big data movement happening with Hadoop. You had the object store developing. So you're in you're you're circling around that area. What was it like then? I mean, take, take us through that because there was obvious visibility that, Hey, let's just store this. Now you see data lakes and that's all happening. But back then object store was kind of new. Yeah. >>Ah, it's a great question. Now, one of the things I realized early on, especially when I was working with binary, when you're saying amazon.com itself as an example, that the access patterns for various applications and Amazon, but let alone AWS customers tend to be very, very, very, some of them really just needed an object store. Some of them needed a relational database. Some of them really wanted a key value store within a fast latency. Some of them really needed a durable cash. And, but it so happens when you have a giant hammer. You use that for everything looks like a map, which is essentially the story at that time. And so everyone kept using the same database, irrespective of what the problem was because nobody else, I mean, thought about like, what else can we build that is better? So this let us do, literally I remember writing a paper with Bernard internally that is widely used in Amazon explaining what are all the menu of booklets that access. >>And then how do we go about actually solving for each of these things so that they can actually grow and innovate faster. And, and this was led to actually the Genesis of not only building IDs and so forth, but also dynamo and various other non-relational data. There's a still let alone not so storage access patterns and what not. So, and this was one of the big revelations he had just that there is not a single database that is going to meet the customer, needs us. The diversity of workloads in the internet is growing. And this was a key pivotal moment because with cloud now applications can scale very more instantly than before now. Building an application for Superbowl is very easier than before. That means that on, I mean, everybody is pushing the boundaries of what scale means, and they are expecting more from their obligations. That's when you need technologies like dynamo, DB, and that's exactly what dynamo already be set out to do. And since then, we are continuing to innovate on behalf of our customers and the purpose of the database story as well. And this concept has resonated well across the board. If you see that the database industry has also embraced this method, >>It's natural that you obviously evolved into the machine learning side of it because that's data is big part of that. And you see back then you, you bringing up kind of like flashes for me where it's like those, the data conversations back then and the data movement was just beginning. So the idea that you can have diversity in access methods of the kind of databases was a use case driven by the application, not so much database saying, this is how you have to work, that the script was flipped. It it's changed from infrastructure dictating to the applications, what to do. Now, the applications are going to the infrastructure and saying, give me what I want. I want to access something here in an office store, something here in no SQL that became the Genesis of infrastructure as code at a, at a global level. And so your paper kind of set the, the, the wave, the influence for this, no SQL did big data movement. It's created tons of value, maybe a third Mongo might've been influenced by this other people have been influenced. Can you share some stories of how people adopted the concept of dynamo DB and how that's changed in the industry and how has that helped the industry evolve? >>I mean, plus file data. Most share our experience of building and dynamo style data store. Very, it is a non-relational API and showing what are some of the experiences that the Venter in building such an paper and these set out early on itself, that it is should not be just a design paper, but it should be something that we shared our experiences. So even now, when I talked to my friends and colleagues and various other companies, one thing they always tell me is they appreciated the openness with which we were sharing. Some of the examples and learnings that we learned to not optimizing for percentile latencies, and what are some of the scalability challenges, how we solved and some of the techniques around things like sloppy Cora or various other stuff. We invented a lot of towns along the way too, but people really appreciated several of some of our findings and as talking about it. >>And since then I met so many other innovations are happening in the industry and the AWS, but also across the entire academia and industry in this space, the databases I've been going through what I call as a period of Renaissance, where one of the things, if you see our own arc, when Roger and I started on the database, front Disney started over the promo saying like, if you were to build a database where cloud is the new normal, this is again in 2008, we asked ourselves that question and what the belt that led us to start building things like dynamo, DB, RDS star. I know that alone, we reimagined data viruses with Redshift and several, and then several other databases like time stream for time series workloads started running Neptune for graph and whatnot. But at the moment we started actually asking that question and working backwards from customers. Then you will start being able to innovate accordingly. And this has worked really well. Then more than a hundred thousand AWS customers have chosen dynamo DB for mobile gaming tech IOT. Many of these are fast growing businesses, such as ledge, Darryl BNB, red fan, as soon as enterprises like Samsung Toyota, capital one and so far. So these are like really some meaningful clouds, let alone amazon.com. I run this. >>We have an internal customer is always good to have that entire inside customer. You know, I really find this a really profound use case because you're just talking, you know, in Amazonian terms, I'll just translate for the audience working backwards from the customer, which is the customer obsession you guys have. So here's, what's going on off the way I see it. You got dynamo, DB, paper, you and Verner, and the team Paul was a great as a great video on your blog posts that goes into the, to the talk he gave at around that time, which is fun to watch if you look back, but you have a radical enabler here, that's disrupting and changing S3 RDS, Aurora. These are game-changing concepts inside the, the landscape of AWS at the same time, you're working backwards from the customer. So the question I have for you as a leader and as a builder, how did you balance the working backwards from the customer while bringing something brand new and radical at that time to the market? >>Yeah, this is one of the S I mean hardest things to be, as leaders need to balance on. If you see many times, then we actually worked backwards from customers. The literal later translated this, literally do what customers are asking for, which is true nine out of 10 times, but there is one or a 10 times, you got to read between the lines on what they are asking. Because many times customers when are articulate that they need to go fast. If in the right way, they might say, Hey, I wish my heart storage goes faster, but they're not going to tell you they need a car, but you need to know and be able to translate and read between the lines we call it under the bucket of innovate on behalf of customers. And that is exactly the kind of a mantra we had when we were thinking about concepts like dynamo DB, because essentially at that time, almost everybody would, if I asked, they would just say, I wish a relational database could actually be able to scale from not just like a hundred gigabyte to one terabyte are, it can take up to like 2 million transactions, a second and so forth and still be cheap and made in reality as relational databases, the way they were engineered at that time, those are not going to meet the scale needs. >>So this is fair. We hunted read between the lines on what are some of the key Mustang needs from customers and then work backwards and then innovate on behalf of these workloads, be enabled by the sun oh four, which are some of the reasons that led to us launching some of the initial sets on dynamo on a single digit millisecond latency and seamless scale. At that time, databases didn't have the elasticity to go from like 10 requests, a second to like a hundred thousand or 1 million requests a second, and then scaled right back in an hour. So that was not possible. And we kind of enabled that. And that was an, a pretty big game changer that showed the elasticity of the cloud to a database. Well, >>Yeah, I think also just to, not to nerd out on this, but it enables a lot of other kind of cool scaled concepts, like queuing storage. It's all kind of together. This database piece of that you guys are solving. And again, props to you guys on the team. Congratulations. I have to ask, you know, more generally, how has your thinking changed since the paper? I'll see, you've got more experience under your belt. You don't yet have the gray hairs yet, but we'll see those soon come in, but you know, you're, you got a lot more experience. You're running teams, you're launching a lot of products. How has your thinking changed in the industry since the paper what's happening now? What's the big evolution. What are those new things now that are in the innovate on behalf of the customer? What's between the lines now, how do you see this happening? >>I mean, now since wanting dynamo via a victim, I had the opportunity to work on various problems in the big data space. There we've worked on some are fire things that you might be aware of in the analytics all the way from Redshift to quick side, too. Then I moved on to start some of our efforts, having built systems that enabled customer to store process and credit, and then analyze them. One of the realizations, I had this, the in around 2015 or 2016, I kinda had that machine learning was hitting a critical point where now it is ready for being scaled at option. Their cloud has basically enabled limitless compute and limitless storage, which are the factors that are holding back machine learning technology. Then I realized that now we have a unique opportunity to bring machine learning BI to everybody, not just folks with PhD in machine learning. >>And that's when I moved on from database and analytics areas, they started machine learning. We're just a descent area because machine learning is powered by data and then started building capabilities like SageMaker, which is our end to end ML platform to build, train and deploy them on models. And this, what does the leading enterprise platform by several gaggled users and then also a bunch of our AI services since then, I view the reason I'm giving all this historical context is one of the biggest realization I had early on itself. And 2016 as first machine learning is one of the most disruptive technologies. She will then country in our generation. This is right after cloud. I think these still are the most amazing combination that is going to revolutionize how we build applications and how we actually reason about that. Now, the second thing is that at the end of the day, when you look at the ANC and journey, it is not just about one database or one data Varroa. >>So one data lake product, or even 1:00 AM out platform. It is about the end to end journey where a customer is storing their order database. And then they are actually building a data lake that test customer history and order history. And they want to be able to personalize. And for their viewer experience are actually forecast what products to staff in their fulfillment center, but then all these things need to work and to handle. And that view is one of the big things that struck me for the past five years. And I've been on this journey in addition to building this Emma building blocks to connect the dots so that customers can go on this modern end to end data strategy as I call it, right. It goes beyond a single database technology or data technology, but putting now all of these end to end together so that customers don't end up spending six months connecting the dots, which has been the state of the down for the last couple of years. And we are bringing it down to matter of the Sundays. Now >>He's incredible Swami. Thank you so much for spending the time with us here in the, >>Yeah, my pleasure. Thanks again, Sean. Thanks for having me.

(upbeat music) >> Okay, we're back at AWS re:Invent 2021. You're watching theCUBE. My name is Dave Vellante, and we're here with Jay Theodore who's the CTO of Enterprise and AI at Esri and he's joined by Dave Cardella, who's the Principal Product Manager for Developer Technologies also at Esri. Guys, thanks for coming on. Welcome to theCUBE. >> Thanks, Dave. >> Thanks, Dave. >> Jay, maybe you could give us a little background on Esri. What do you guys do? What are you all about? >> Sure. Esri is an old timer, we are a 50-year old software company. We are the pioneers in GIS and the world leader in GIS - geographic information system. We build geospatial infrastructure that's built for the cloud, built for the edge, built for the field also, you can say. So, we do mapping and analytics. We help our customers solve very complex challenges by bringing location intelligence into the mix. Our customers sort of like run the world, transform the world and we sort of like empower them with the technology we have. So, that's what we do. >> The original edge, and now of course, AWS is coming to you. >> Yeah. (both interviewees chuckling) >> Who are your customers, your main customers? Maybe share that. >> Yeah. We've got over 350,000 customers in... (Dave Cardella chuckling) Yeah. We're all- >> Dave Vellante: Scale. >> Yeah. (Dave Vellante laughing) In the public sector, especially, commercial businesses, non-profit organizations, and that really represents tens of millions of users globally. >> So, let's talk a little bit more about how things are changing. As they say, the edge is coming to you. Maybe AI, you know, 50 years ago... Actually, 50 years ago is probably a lot of talk about AI. When I came into the business, you know, it was a lot of chatter about it. But now, it's real. All this data that we have and the compute power, the cost is coming down. So, AI is in your title? >> Jay: Yes. >> Tell us more about that. >> I think that AI's come to age. When I went to grad school, AI was still in theory because we didn't have the compute and of course we didn't have all the data that was collected, right? Now, there's a lot of observation data coming in through IOT and many senses and so on. So, what do you do with that? Like, human interpretation is pretty challenged, I would say. So, that's where AI comes in, to augment the intelligence that we have in terms of extracting information. So, geospatial AI, specifically which we focus on, is to try to take location that's embedded with this kind of information and sort of like extract knowledge and information out of them, right? Intelligence out of them. So, that's what we focus on: to compliment location intelligence with AI, which we call geospatial AI. >> So, you can observe how things are changing, maybe report on that and that's got to be a huge thing that we can talk about. So, maybe talk about some of the big trends that are driving your business. What are those? >> Yeah, that's a great question. So, I was listening to Sandy Carter's 'Keynote' yesterday and she really emphasized the importance of data. And, data is crucial to what we do as a technology company, and we curate data globally and we get our data from best of breed sources, and that includes commercial data providers, it includes natural mapping agencies, and also a community maps program where we get data from our customers, from our global network of distributors and partners, and we take that data, we curate it, we host it and we deliver it back. And so, just recently for example, we're really excited 'cause we released the 2020 Global Land Cover. And so, Esri is the first company to release this data at 10 meter resolution for the entire planet, and it's made up of well over 400,000 earth observations from various satellites. So, you know data is a... It's not only a nice-to-have anymore, it's actually a must-have. And so, so is location when we talk about data. They go hand in hand. >> 10 meters so I can look at the hole in the roof of my barn... >> Well... (Dave Cardella chuckling) >> Dave Vellante: Pretty much. >> It depends on what you're trying to do, right? So, I think you know, to talk about it, it's within context. GIS is all about context, right? It's bringing location into context in your decision-making process. It's sort of like the where along with the when, what, how and why. That's what GIS brings in. So, a lot of problems are challenging because we need to bring these things together. It's sort of like you're tearing various layers of data that you have and then bringing them within context. Very often, the context that human minds understand and reflected in the physical world is geographic location, right? So, that's what you bring in. And I would say that there's various kinds of data, also. Various types of data, formats of data: structured data, unstructured data, data captured from extraterrestrial, you know, like, you can say, satellite imagery from drones, from IOT. So, it's like on the ground, above the ground, under the ground. All these sensors are bringing in data, right? So, what GIS does is try of map that data to a place on the earth at very high precision, if you're looking at it locally, or at a certain position if it's regionally, trying to find patterns, trying to understand what's emerging, and then, as you take this and infuse geospatial layer into this, you can even predict what is going to happen based on the past. So, that's sort of like... You could say GIS being used for real world problems, like if you take some examples, COVID... The pandemic is one example. Being able to first discover where it happened, where it's spreading, you know, that's the tracking aspect and then how you respond to that and then how you recover, you know, recovering as humans, as businesses and so on. So, we have widespread use of that. The most popular would be the John Hopkins' Dashboard, >> Dave Vellante: Board, yeah. >> that everyone's seen. >> Vellante: We all use it... >> It's gotten trillions of hits and so on, right? That's one example. Another example is addressing racial equity by using location information. Similarly, social justice. Now, these are all problems that we face today, right? So, GIS is extensively used by our customers to solve such problems. And then of course, you have the climate change challenge itself, right? Where you're hovering all kinds of complex data that we can't comprehend because you have to go back decades and try to bring all that together to compute. So, all of this together comes in the form of a geospatial cloud that we have as an offering. >> So, okay. That's amazing. I mean, you're building a super cloud, we call it. You know, and... So, how do you deal with... How do you work with AWS? What's the relationship there? Where do developers fit in? Maybe you can talk about a little bit. >> Yeah. Yeah, that's a great question. So, we've got two main integration points with AWS. A lot of our location services that we expose data and capabilities through are built on AWS. So, we use storage, we use cloud caching and AWS's various data sets across the world quite heavily. So, that's one integration point. The other is a relatively new product that Amazon has released called Amazon Location Service. And so, what it does is it brings location and spatial intelligence directly into a developer's AWS dashboard. So, the experience that they're already used to, they now get the power of Esri services and location intelligence right at their fingertips. >> So, you're .. We started talking about the edge, your data architecture is very distributed, right? But, of course, you're bringing it back. So, how does that all work? You process it locally and then sending some data back? Are you sending all data back? What does that flow look like? >> I think the key thing is that our customers work with data of all kinds, all formats, all sizes and some are in real-time, some are big data and archive, right? So, most recently, just to illustrate that point, this year, we released RGS Enterprise on Kubernetes. It's the entire geospatial cloud made available for enterprise customers, and that's made available on AWS, on EKS. Now, when it's available on EKS, that means all these capabilities are microservices, so, they can be massively scaled. They're DevOps friendly and you've got the full mapping and analytics system that's made available for this. >> Dave Vellante: Oh. >> And we sort of like built it, you know, cloud native from the ground up and the more important thing that we have now is connectivity with Redshift. Why is that important? Because a lot of our customers have geospatial data in these cloud data warehouses. Redshift is very important for them. And so, you can connect to that, you can discover these massive petabytes of data sets and then you can set up what we call the query layer. It's basically pushing analytics into Redshift and being able to bring out that data for mapping, visualization, for AI workflows and so on. It's pretty amazing and it's pretty exciting at this time. >> And, I mean... So much data. And then... What, do you tear it down into glacier of just to save some cost, or is it going to all stay in S3 or is it... >> So, we already work with S3, we've worked with RDS, we support Amazon Aurora, our customers are very happy with that. So, Redshift is a new offering for us to connect to Redshift. >> Dave Vellante: AOK. >> So, the way the query layer works is all of your observation data is in Redshift, your other kinds of data... Your authoritative data sets could come from various other sources including in Amazon Aurora, for example, okay? And then, you overlay them and use them. Now, the data in Redshift is usually massive, so, when you run the analytic query, we let you cache that as a materialized view or as a snapshot that you can refresh and you can work against that. This is really good because it compliments our ability to actually take that data, to put it on a map image which we render service side, it's got very complex cartographic ready symbology and rendering and everything in there. And you get these beautiful rendering of maps that comes out of Redshift data. >> And you're pushing AI throughout your stack, is that, you know? >> Yeah. AI is just like infused, right? I mean, it's... I would say, human intelligence augmented for data scientists, for everyone, you know. Whether you're using it through notebooks or whether you're using it through applications that we have or the developer APIs themselves. >> So, what are some of the big initiatives you're working on near-term, mid-term? >> Yeah. So, you mentioned what's really driving innovation and it's related to the question that you just asked right now and I really believe developers drive innovation. They're force multipliers in the solutions that they build. And so, that's really the integration point that Esri has with AWS, it's developers. And earlier this year, we released the RGS platform which is our platform as a service offering that exposes these powerful location services that Jay just explained. There's a set of on-demand services that developers can bring in their applications as they want and they can bring in one, they can bring in two or three, whatever they need, but they're there when they need them. And also, developers have their client API of choice. So, we have our own client APIs that we offer but you're not pigeonholed into that when you're working with RGS platform. A developer can bring their own API. >> Okay, so he called the platform as a service. Are you making your data available as well? Your data, your tooling and then selling that as a service? >> Our data has always been available as a service, I would say. >> Okay, yeah. >> Everything that we do, our GIS tools, are accessible as a web service. >> Vellante: Is that new, or... that's always been the way? >> No, that's always been there. That's always been that way. The difference now is everything is built from the ground up to be cloud native. >> Dave Vellante: Okay. >> From the ground up to be connected to every data set that's available on AWS, every compute that can be exploited from small to massive in terms of compute, and also reaching out to bring all the apps and the developer experiences, pushing out to customers. >> So, 50 years ago, you weren't obviously using the cloud, but so, you were running everything on-prem now you're all in the cloud, or you're kind of got a mix? What is the clearer picture of that? >> So, we have two major offerings. There's RGS Online, where obviously it's offered as a service and it's GIS as a service provider for everyone. And that's available everywhere. The other offering we have is actually RGS Enterprise where some customers run them on premises, some run it in the cloud, especially AWS. Many run it on the edge, some in the field and there's connectivity between this. A lot of our customers are hybrid. So, they make the best of both. Depending on the kinds of data- >> Dave Vellante: You give them a choice. >> the kinds of workflows... Giving them the choice, exactly. And I would say, you know, taking Werner's 'Keynote' this morning, he talked about what's the next frontier, right? The next frontier could very well be when AWS gets to space and makes compute available there. It's sitting alongside the data that's captured and we've always, like I said, for 50 years, worked with satellite imagery, >> Dave Vellante: Yeah. >> or worked with IOT, or worked with drone data. It's just getting GIS closer to where the data is. >> So, the ultimate edge space. >> Yes. >> All right, I'll give you guys... Give us a quick wrap if you would. Final thoughts. >> I think its... Go ahead. >> Go, ahead Dave. >> Yeah. I really resonate with data and content. We're a technology company- there's no doubt about that- but without good data, not only supplied by ourselves, but our customers, Jay mentioned it earlier, our customers bring their own data to our platform and that's really what drives the analytics and the accuracy in the answers to the problems that people are trying to solve. >> Bring their first-party data with your data and then one plus one is... >> Yes. Yeah, and the key thing about that (Cardella chuckling) is not some of the data, it's all of the data that you have. You don't more need to be constrained. >> Yeah, you're not sampling. >> Yes, exactly. >> Yeah. >> All right, guys. Thanks so much. Really interesting story. Congratulations. >> Thank you, Dave. >> Dave, thank you. >> Nice meeting you. >> Thank you for watching. This is Dave Vellante for theCUBE, the leader in global tech coverage. We'll be right back. (upbeat music)

(upbeat music) >> Welcome back to re:Invent 2021. You're watching theCUBE. My name is Dave Vellante. We're really excited to have Anthony Lye here. He's the Executive Vice President and General Manager of Public Cloud at NetApp. And Jonsi Stefansson as the CTO and VP of cloud at NetApp. Guys, good to see you. >> Same to you. >> Likewise. >> It's great to be back. >> You know, Anthony. Well so, we saw each other virtually at the AWS Storage Day, the big announcement, we're going to talk about that. But I go back and I said this to you several years ago, we were sitting, you know, some after party and you said "We are going to transform NetApp. We are going all in on cloud." We've seen NetApp transform many, many times. This is probably the biggest in history. >> No, I think you're absolutely right. I think, you know, I can't believe it, but you know, it will be five years for me in February. And in those five years, I think we really have done things that nobody expected. And I think we've proven to our existing customers, to our competitors, and now with Amazon, to a whole new set of customers that our intellectual property that we build and the acquisitions that we've done have made a lot of sense. I think we've demonstrated this wonderful concept of symmetry. Customers now understand and believe that a dollar invested in an App, wherever it is on premise or in the cloud is a dollar that moves wherever they want it to move and progresses as their own businesses progress. >> So Jonsi, for the latest announcement that you guys made to integrate ONTAP into the AWS cloud, you had to do some deeper integration, right? It wasn't just wrap your stack and Kubernetes and shove it into the cloud. But can you just talk about what you had to do? What the collaboration was like? >> The collaboration with AWS has been fantastic. It literally took two and a half years, you know, from the point where we decided to agree on the design principles, how we were actually going to deliver this as a service, the integration into every single aspect of AWS, you know, whether it's the console, the FSx, API, the integrations, to all the additional services that AWS has, like RDS, like Aurora, like the SageMaker, like EKS and ECS. And I mean, we are just getting started with the integration points and the collaboration and the teamwork. I would call it teamwork more than a collaboration. The teamwork with all these teams and maybe especially at name who was the leader of the storage sort of a unit in AWS has been fantastic. >> Dave: Yeah. Well so, this is the 10th re:Invent. This is the 9th year we've been here. We've seen a dramatically different cloud than 10 years ago, 15 years ago, and a different storage business. I'm not even sure. I mean, I don't know. I didn't even think about it as the old storage business anymore. Essentially, you're building a cloud on top of clouds. A super cloud if you will. >> Anthony: Yeah, I mean. I think, look, the strategy was, as I said, very, very simple to us, which was, you know, fundamentally companies, you know, run their applications on the basic primitives of compute storage and networking. And the gold standard for file was always ONTAP. And I think what we did, which I think was unique was we didn't just, as you said, throw it onto a cloud, stick it in a virtual machine and tell you, the customer "There. It's ONTAP just as you remember it." We reimagined it. And we architected it to be a cloud service. So it's elastic, it goes up and down. You can change the performance at runtime. And what we really did with Amazon was we wanted to make it a fully managed service. We didn't want people to think about versioning and patching. We wanted to remove all of that and we wanted people to take as much or as little as they needed. And we, and Amazon, we chose that we should own the responsibility for the availability of the service. And we should maintain the service ourselves so that customers of ONTAP can benefit from the solution. But in many ways, customers who've never been ONTAP customers can now take advantage of an enterprise grade file system and all the great things that it does without having to understand how it works. >> And explain why that's important for customers because people, they go, "Wow, you got S3." but it's very simple. Get, put, right? You don't have the full stack of a mature ONTAP. Please explain what that means to customers a little bit. >> You know, file systems are very important things. You know, we basically use them in our work environments every single day, you know. Within your sort of, you know, your Mac book, you have a home directory and sub-directories and files, very elegantly layout applications and layout infrastructures in ways that object repositories cannot. You know, aside from block and file. Sorry, from file and object, you of course, have block storage. And so, file plays a very important role. IDC has file growing at almost twice the pace of object now on the public cloud systems and, you know, file has about 13% of the overall storage market and it's growing. And I don't see any reason why file won't be as big on the Amazon cloud as the S3 has been. >> Dave: So you guys, go ahead, please. >> Yeah. I mean, you also have to take into account that the S3 object storage offerings of AWS is an integrated PaaS in our solution. So that's how we are actually doing automatic tiering. So you actually reap the best of both worlds, where you get the cost management of putting it in object storage, but you get the performance and the data management capabilities that is pretty unprecedented. You know, we are the first store that's offering that can actually do cross-region replication seamlessly by retaining deduplication and compression. But we also play a lot with, you know, block and object storage. So when Anthony was talking about how we've actually delivered this as a service, and this is sort of from our design principles, we are basically delivering this as a software, as a service, because more than an infrastructure as a service, because the stock that we are actually deploying, or the secret sauce of ONTAP, it's a very vast software stack that we are delivering, on top of AWS infrastructure. So I would always call it or categorize it a little bit more than software as a service, rather than infrastructure as a service. >> But it's even more than that, if I'm right, because it's cloud pricing, right? >> Jonsi: Yes. >> So it's not, you're not preying. I mean, when I buy Salesforce, I got to sign up for three-year deal. That's not a consumption-based model. >> Yeah. >> Oh, I think Amazon, you know what Amazon did uniquely and brilliantly was, it retailed technology and it's what makes Amazon so good, is that they choose to sort of simplify things. And when they find benefits as a retailer, they pass them on to the customer and, you know, there's this sort of pay-as-you-go business model, it's really good for the customer. It makes us work harder because, you know, you have to retain your customer sort of every 10 minutes. And that's something that, you know, as you said, with enterprise software and even some of the early SaaS vendors, that's not how it works. And so Amazon has forced us all to be very, very attentive to our customers. >> Dave: And I'd love to talk about what that means for the on-prem business, but if we have time. But you guys won Design Partner of the Year, what's that all about? First of all, congratulations. >> Anthony: Thank you. There's a lot of ISV design partners. You guys came out number one so congratulations on that. What's that all about? Explain what that entailed and how you got that. >> Yeah, I'll say a few words. Maybe Jonsi can add. I mean, the first thing of course is, you know, I S V stands for Independent Software Vendor. So, you know, it's always great because most people would say, "Well, NetApp is on-premise storage hardware." >> Dave: Of course, yeah. >> Which really, we've not really ever been an increasingly with demonstrating that we are a software company and we operate at cloud speed. You know, I can't really take the credit. I would give it to Jonsi and the engineering team. Maybe Jonsi, you can explain, you know, what moral about the award and why I think we were selected. >> So, I mean, I think it says a lot that this is the first time AWS has ever allowed a third party company to be this integrated into their console, into a support ability systems. You know, we make fun of this, me and Anthony all the time, because when we started this, down this path, everybody at NetApp said, "Guys, you're wasting your time." This is why AWS has the marketplace, but we didn't want to go. We already had the marketplace and we wanted to be able to connect to all these associated services and do it in the manner that, you know, this was a true collaboration of engineering teams for a long time to actually deliver the service on both sides so the credit, of course, will always go to the engineers on both sides, even though I designed it, I didn't code it. So, I think that, that alone, being the first to do it in AWS ever. I think we deserve that award. >> So just for our audience, to be clear, we're talking about FSx, ONTAP in the cloud, in the AWS cloud and kind of dance around that. But so that was announced, I guess, in September? >> Anthony: Yes. >> Right? >> Anthony: September, 2nd. >> What's the uptake been like? What's the reaction? >> Unbelievable. >> I'll bet. (laughing) >> No, no, I mean. >> No, I believe it. >> Better than we ever dreamed of. >> Yeah. >> The number of customers, I'm sure I'm not allowed to say the number of customers, but we asked and the fact that, you know, 60% of those customers have never been NetApp customers before, but they see the value in the data management capabilities that we are bringing to the market. >> Dave: So it exceeded expectations and your expectations were probably pretty enthusiastic. >> They were high. >> Yeah. >> I mean, Amazon is on the record. I was with Ed earlier on today, recording a piece and Ed, you know, was very clear that it's one of the fastest growing services now on AWS. You know, it turns out that, you know, the customer base, I think recognizes the, not just the need for a file system, but the uniqueness and capabilities that ONTAP provides, you know, to those customers in how they manage their business and transformations. And so, you know, to be sort of behind the console, to be sort of behind the Amazon CLI and the Amazon API, you see the world very, very differently, you know. I think the Amazon marketplace is a fantastic capability, but I'll tell you, you know, being a core part of the AWS service itself that they sell, that they support, that they bill for. It's a nice place to be. >> So, SaaS company. You're talking to the language of application development, Kubernetes, right? What do you think this means for the future of NetApp specifically, but also generally the on-prem storage business and the storage business in general? >> Well, we just announced our second quarter earnings today and what's happening is our cloud business is growing like crazy. We generated $388 million of ARR and the growth rates are, you know, astronomically high. That is increasingly helping our on-premise business to grow. You know, the nice thing about being in primarily, in the storage and data business is people aren't deleting many things. And the rate at which they're generating information is just accelerating. So, actually the confidence that we give the customer by demonstrating a sort of a cloud first, a sort of principles of all the cloud is actually giving customers to buy more on premise. So, we really don't mind. We are, our job much like Amazon's, is to have this customer obsession and you can't really go wrong, if you just keep asking them what they want. >> Yeah, if you can do so profitably, you're going to be reinvest in your business. Guys, we've got to go. >> Yeah. >> Love to have you back. >> Thank you. >> And you been quite a transformation. You said you're going to do it. You're doing it. So, well done to you. Five years in the making. Okay. This is Dave Vellante for theCUBE, the leader in high-tech coverage. Keep it right there. We'll be right back from AWS re:Invent 21. (upbeat music)

(upbeat music) >> Welcome back to re:Invent 2021. You're watching theCUBE. My name is Dave Vellante. We're really excited to have Anthony Lye here. He's the Executive Vice President and General Manager of Public Cloud at NetApp. And Jonsi Stefansson as the CTO and VP of cloud at NetApp. Guys, good to see you. >> Same to you. >> Likewise. >> It's great to be back. >> You know, Anthony. Well so, we saw each other virtually at the AWS Storage Day, the big announcement, we're going to talk about that. But I go back and I said this to you several years ago, we were sitting, you know, some after party and you said "We are going to transform NetApp. We are going all in on cloud." We've seen NetApp transform many, many times. This is probably the biggest in history. >> No, I think you're absolutely right. I think, you know, I can't believe it, but you know, it will be five years for me in February. And in those five years, I think we really have done things that nobody expected. And I think we've proven to our existing customers, to our competitors, and now with Amazon, to a whole new set of customers that our intellectual property that we build and the acquisitions that we've done have made a lot of sense. I think we've demonstrated this wonderful concept of symmetry. Customers now understand and believe that a dollar invested in an App, wherever it is on premise or in the cloud is a dollar that moves wherever they want it to move and progresses as their own businesses progress. >> So Jonsi, for the latest announcement that you guys made to integrate ONTAP into the AWS cloud, you had to do some deeper integration, right? It wasn't just wrap your stack and Kubernetes and shove it into the cloud. But can you just talk about what you had to do? What the collaboration was like? >> The collaboration with AWS has been fantastic. It literally took two and a half years, you know, from the point where we decided to agree on the design principles, how we were actually going to deliver this as a service, the integration into every single aspect of AWS, you know, whether it's the console, the FSx, API, the integrations, to all the additional services that AWS has, like RDS, like Aurora, like the SageMaker, like EKS and ECS. And I mean, we are just getting started with the integration points and the collaboration and the teamwork. I would call it teamwork more than a collaboration. The teamwork with all these teams and maybe especially at name who was the leader of the storage sort of a unit in AWS has been fantastic. >> Dave: Yeah. Well so, this is the 10th re:Invent. This is the 9th year we've been here. We've seen a dramatically different cloud than 10 years ago, 15 years ago, and a different storage business. I'm not even sure. I mean, I don't know. I didn't even think about it as the old storage business anymore. Essentially, you're building a cloud on top of clouds. A super cloud if you will. >> Anthony: Yeah, I mean. I think, look, the strategy was, as I said, very, very simple to us, which was, you know, fundamentally companies, you know, run their applications on the basic primitives of compute storage and networking. And the gold standard for file was always ONTAP. And I think what we did, which I think was unique was we didn't just, as you said, throw it onto a cloud, stick it in a virtual machine and tell you, the customer "There. It's ONTAP just as you remember it." We reimagined it. And we architected it to be a cloud service. So it's elastic, it goes up and down. You can change the performance at runtime. And what we really did with Amazon was we wanted to make it a fully managed service. We didn't want people to think about versioning and patching. We wanted to remove all of that and we wanted people to take as much or as little as they needed. And we, and Amazon, we chose that we should own the responsibility for the availability of the service. And we should maintain the service ourselves so that customers of ONTAP can benefit from the solution. But in many ways, customers who've never been ONTAP customers can now take advantage of an enterprise grade file system and all the great things that it does without having to understand how it works. >> And explain why that's important for customers because people, they go, "Wow, you got S3." but it's very simple. Get, put, right? You don't have the full stack of a mature ONTAP. Please explain what that means to customers a little bit. >> You know, file systems are very important things. You know, we basically use them in our work environments every single day, you know. Within your sort of, you know, your Mac book, you have a home directory and sub-directories and files, very elegantly layout applications and layout infrastructures in ways that object repositories cannot. You know, aside from block and file. Sorry, from file and object, you of course, have block storage. And so, file plays a very important role. IDC has file growing at almost twice the pace of object now on the public cloud systems and, you know, file has about 13% of the overall storage market and it's growing. And I don't see any reason why file won't be as big on the Amazon cloud as the S3 has been. >> Dave: So you guys, go ahead, please. >> Yeah. I mean, you also have to take into account that the S3 object storage offerings of AWS is an integrated PaaS in our solution. So that's how we are actually doing automatic tiering. So you actually reap the best of both worlds, where you get the cost management of putting it in object storage, but you get the performance and the data management capabilities that is pretty unprecedented. You know, we are the first store that's offering that can actually do cross-region replication seamlessly by retaining deduplication and compression. But we also play a lot with, you know, block and object storage. So when Anthony was talking about how we've actually delivered this as a service, and this is sort of from our design principles, we are basically delivering this as a software, as a service, because more than an infrastructure as a service, because the stock that we are actually deploying, or the secret sauce of ONTAP, it's a very vast software stack that we are delivering, on top of AWS infrastructure. So I would always call it or categorize it a little bit more than software as a service, rather than infrastructure as a service. >> But it's even more than that, if I'm right, because it's cloud pricing, right? >> Jonsi: Yes. >> So it's not, you're not preying. I mean, when I buy Salesforce, I got to sign up for three-year deal. That's not a consumption-based model. >> Yeah. >> Oh, I think Amazon, you know what Amazon did uniquely and brilliantly was, it retailed technology and it's what makes Amazon so good, is that they choose to sort of simplify things. And when they find benefits as a retailer, they pass them on to the customer and, you know, there's this sort of pay-as-you-go business model, it's really good for the customer. It makes us work harder because, you know, you have to retain your customer sort of every 10 minutes. And that's something that, you know, as you said, with enterprise software and even some of the early SaaS vendors, that's not how it works. And so Amazon has forced us all to be very, very attentive to our customers. >> Dave: And I'd love to talk about what that means for the on-prem business, but if we have time. But you guys won Design Partner of the Year, what's that all about? First of all, congratulations. >> Anthony: Thank you. There's a lot of ISV design partners. You guys came out number one so congratulations on that. What's that all about? Explain what that entailed and how you got that. >> Yeah, I'll say a few words. Maybe Jonsi can add. I mean, the first thing of course is, you know, I S V stands for Independent Software Vendor. So, you know, it's always great because most people would say, "Well, NetApp is on-premise storage hardware." >> Dave: Of course, yeah. >> Which really, we've not really ever been an increasingly with demonstrating that we are a software company and we operate at cloud speed. You know, I can't really take the credit. I would give it to Jonsi and the engineering team. Maybe Jonsi, you can explain, you know, what moral about the award and why I think we were selected. >> So, I mean, I think it says a lot that this is the first time AWS has ever allowed a third party company to be this integrated into their console, into a support ability systems. You know, we make fun of this, me and Anthony all the time, because when we started this, down this path, everybody at NetApp said, "Guys, you're wasting your time." This is why AWS has the marketplace, but we didn't want to go. We already had the marketplace and we wanted to be able to connect to all these associated services and do within the manner that, you know, this was a true collaboration of engineering teams for a long time to actually deliver the service on both sides so the credit, of course, will always go to the engineers on both sides, even though I designed it, I didn't coat it. So, I think that, that alone, being the first to do it in AWS ever. I think we deserve that award. >> So just for our audience, to be clear, we're talking about FSx, ONTAP in the cloud, in the AWS cloud and kind of dance around that. But so that was announced, I guess, in September? >> Anthony: Yes. >> Right? >> Anthony: September, 2nd. >> What's the uptake been like? What's the reaction? >> Unbelievable. >> I'll bet. (laughing) >> No, no, I mean. >> No, I believe it. >> Better than we ever dreamed of. >> Yeah. >> The number of customers, I'm sure I'm not allowed to say the number of customers, but we asked and the fact that, you know, 60% of those customers have never been NetApp customers before, but they see the value in the data management capabilities that we are bringing to the market. >> Dave: So it exceeded expectations and your expectations were probably pretty enthusiastic. >> They were high. >> Yeah. >> I mean, Amazon is on the record. I was with Ed earlier on today, recording a piece and Ed, you know, was very clear that it's one of the fastest growing services now on AWS. You know, it turns out that, you know, the customer base, I think recognizes the, not just the need for a file system, but the uniqueness and capabilities that ONTAP provides, you know, to those customers in how they manage their business and transformations. And so, you know, to be sort of behind the console, to be sort of behind the Amazon CLI and the Amazon API, you see the world very, very differently, you know. I think the Amazon marketplace is a fantastic capability, but I'll tell you, you know, being a core part of the AWS service itself that they sell, that they support, that they bill for. It's a nice place to be. >> So, SaaS company. You're talking to the language of application development, Kubernetes, right? What do you think this means for the future of NetApp specifically, but also generally the on-prem storage business and the storage business in general? >> Well, we just announced our second quarter earnings today and what's happening is our cloud business is growing like crazy. We generated $388 million of ARR and the growth rates are, you know, astronomically high. That is increasingly helping our on-premise business to grow. You know, the nice thing about being in primarily, in the storage and data business is people aren't deleting many things. And the rate at which they're generating information is just accelerating. So, actually the confidence that we give the customer by demonstrating a sort of a cloud first, a sort of principles of all the cloud is actually giving customers to buy more on premise. So, we really don't mind. We are, our job much like Amazon's, is to have this customer obsession and you can't really go wrong, if you just keep asking them what they want. >> Yeah, if you can do so profitably, you're going to be reinvest in your business. Guys, we've got to go. >> Yeah. >> Love to have you back. >> Thank you. >> And you been quite a transformation. You said you're going to do it. You're doing it. So, well done to you. Five years in the making. Okay. This is Dave Vellante for theCUBE, the leader in high-tech coverage. Keep it right there. We'll be right back from AWS re:Invent 21. (upbeat music)

(gentle music) >> Hello everyone, and welcome back to day two of AWS re:Invent 2021, theCUBE's continuous coverage. My name is Dave Vellante, I'm here with my co-host, David Nicholson. We've got two sets. We had two remote sets prior to the show. We're running all kinds of activities and we've got AWS executives, partners, ecosystem technologists, Scott Weber is here as the director and an AWS partner, ambassador from PwC. Scott, good to see you. >> Nice to meet you guys. Thanks for letting me be here. >> Well, so your expertise is around application modernization. It's a hot theme these days. If you're a company with a lot of legacy debt, you've got a big complex application portfolio. I would think, especially with the forced match to digital over the last year and a half, two years. Now is really a time when you're probably too late to really start thinking about rationalizing your portfolio. What are you seeing in this space? >> Definitely, we're seeing the customers that have reached that point. I view modernization as sort of the second wave of cloud that's coming. So you had your first wave, the early adopters that lifted and shifted into the cloud. We still have people looking at getting into the cloud, but for those that went early, now, they're saying, "How do I get more out of the cloud? How do I get closer to cloud native?" And that's what we're starting to see around this modernization move is, I want to start to utilize those higher level services from AWS and the cloud providers. I want to get a better return, I want to stop worrying about running infrastructure and hardware. >> So when you think about, I go back all the way back to Y2K, that was like a boondoggle for IT to spend a bunch of doh and do some cool stuff. And then of course the .com crashed, but today it's different. It's really about the business impact the business outcome that you can drive in transforming your digital business. So how do you as a technology agnostic consultant help a company understand what they should leave alone or sunset? What they should aggressively migrate? What's the process that you use to do that? >> In some ways we go back, we can reuse sort of those 6Rs that maybe got a customer to the cloud, or as they're on that cloud journey, right? And you really want to focus on where can you optimize ROI. And you're going to come across those things that are going to be like, look, maybe it's a vendor COTS solution. There's not a lot we can do there. You're just going to have to continue down that path. Unless we can look to move that to a SaaS service. Maybe the vendor has gone to a SaaS offering. Or we get into looking at they've done development in house, but that development is still monolithic running on virtual machines, either in the data center or in AWS, but it's a critical system to that business. It's maybe it's become fragile. How can we now modernize that? Because that's where there's going to be a great return on investment for that customer, and it's also going to allow business agility for those customers. As we can get them to microservices and Lambda and function as a service, the blast radius for changes become smaller, allows the customer to move faster than what they're doing. So it's the rationalization becomes what's driving the business forward? What's critical to the business? But what's holding them back as well? So that the customers can start to move faster. >> So it's a formula of okay, what's the business value of those applications essentially? You can kind of rank that, but then it's a formula there's a cost equation. That's pretty straightforward to figure out the s is and the 2b but then there's a speed. Like an ongoing time to value from a developer standpoint and then I guess there's risk. Have you got your core jewels? Maybe you don't want to touch those yet. Is that kind of your algorithm? >> It is and on that sort of cost and value piece, that's where we can really see some interesting things happen, where as we get customers away from licensed OSS proprietary databases, that return on investment can be huge. So we've helped customers migrate from running .net applications on top of a typical Microsoft Windows stack and SQL server stack. All the way to taking those workloads, all the way, either to Linux containers or all the way to serverless if we're going to take all the steps to rewrite, you can drive 60, 70, 80% of the cost of operating at that platform out of it, then you start this flywheel effect of reinvesting that money back into the next project to help the customer move forward. >> And it's quick follow up, but I know you want to jump in. >> Yeah, yeah. >> Why wouldn't a customer, that's a Microsoft customer just run that on Azure? Why AWS? >> I mean, that's a good question and that sort of gets into a lot of philosophical, like discussion we talk about for a long time. The fact of the matter is the majority of your Windows workloads still run on top of AWS today. I would argue AWS has some pretty superior things in their underlying architecture, they're nitro architectures and things like that. But I think it's also choice. And, the whole move of .net to Linux, Microsoft started that they put the ability to, you can run SQL server on top of Linux. Well, if I run SQL server on top of Linux, I take out 20% of my costs right there. They put the support in for .net core to be able to run on Linux or on containers, but that's to help the developers move faster, that's to help us get to microservices. So that cloud provider choice, I think is becomes a bigger discussion, but a lot of people are choosing AWS because they're not just doing Microsoft workloads . Again, we could get very deep into like, trade-offs on why one over the other, but customers are choosing AWS for a lot of these words. >> Diversity and better cloud, better infrastructure. >> Yeah, and philosophical is an interesting way to look at it when it becomes a hostage negotiation. I'm not sure there was a lot of philosophy involved when server and SQL 2008 were being end of support life. And people were told, move it to Azure and we'll take care of you. Don't move it to Azure, you're on your own. But something on the subject of ROI. ROI is typically measured over time. How do you rectify and address the sort of CIO dilemma, which is that if ROI is being delivered fantastically in four years, but the average tenure of a CIO is 2.7 years, how do you address that? What is the sweet spot for timeframes that you're seeing for people to actually implement when you consider as was mentioned today, the keynote that somewhere around 15% of IT spend is in cloud today, which leaves 85% of it on premises. So what do we do about that? >> Yeah, that's a great question. So, I think, I like to get small wins. So find a very big pain point for that customer. How can we start to get them some small wins and start that flywheel effect going of like you saved money here, now, can we reinvest and start to show some wins, but we've engaged in projects where we've completely rewritten a whole application stack that was the core service for a business in a year and a half, and we took them from a run rate of somewhere between 40 and $60,000 a month. Had they been running that in AWS, they were running it in a data center today. So that was our estimate to less than $5,000 a month to run that application on a serverless platform inside of AWS. >> So when you talk about modernizing an application environment, that's typically not thought of as low hanging fruit. So does that mean that all the low hanging fruit has been consumed? Are all the net new things that are developed in a cloud native format, have they already been done? Is this the only frontier for opportunity now? >> No, it's not the only frontier. I mean, there's a lot of customers that are still just trying to get into the cloud. >> Lots of applications out there? >> Yeah, and you look at things like mainframe as well. That's I think a coming area where customers are finally starting to say, "Enough with the mainframe, we saw it in the keynote today of a new sort of service offering around helping customers rationalize how to do, to start to do things with the mainframe." So, but sometimes you can get those easy wins. Like we find a scalability issue. And we can inject scalability and pull back costs very rapidly. 'Cause you run in that scenario, there provision for max capacity that may happen 10% of the year. Now they're vastly overpaying. So we can still get some easy wins with slight tweaks to the platform while we help them rationalize those longer built times. I think the other thing we're starting to see is a shift in CIOs that are coming more from a software background too. That aren't from the pure infrastructure background and as we see those software dBase CIO start to come in. They're starting to understand the game that can be had of making the investment in the software and those upgrades to the software. >> And their tenure is elongating 'cause, CIO career is over was the joke. Now you're losing CIO, is cause they're going onto a bigger and better. They getting more options. I mean, they're becoming rockstars again. I want to ask you just as a side about that mainframe compatible runtime that they announced 'cause it sounds like you've got some experience in converting mainframe. >> Yeah. >> 'Cause I've always been a skeptic. We've seen this movie before where people have to freeze code, they've got to freeze code for 18 months. It takes 24 months, but now it's cloud, Adam Selipsky said, we can cut migration time, which is critical here by two-thirds 'cause that's the key. If you can reduce the time of which you have to freeze the code or maybe not even freeze the code. Again, I'm a skeptic, but what are you seeing with practical experience? >> So at PwC, we're seeing a lot of customers, start down this path and the ROI is pretty amazing when once you get in and you really start to dig in of what it can be if to go down this path. And there's a lot of tools out there, there's a gentleman on our team that's a real genius with this and he's helped multiple customers go down this path. There's tools that can start to do code conversion for you. I mean, we all get a little skeptical on those things cause we never know what the machine is going to try to make the code look like, but it's the starting point. But there is more. >> Like a prewash? >> Yeah, (Dave laughs) there's more and more design patterns coming out to help us down those pathways. But it goes back to agility for the business cause a lot of these customers running mainframes today are looking at a six month release cycle if they want to make any changes to their environment. If we can get them into an agile mindset to a microservice, they can get to two weeks or less for release cycles. So it's a big win for the company overall. Yes, there's a risk, but I think you can take, you can try to de-risk it as much as you can, you don't take the core, the absolute core critical piece of that mainframe. You start to pick away around the edges and you get comfortable with what you're doing. >> And going back to the concept of ROI, specifically in the mainframe space, there have been some not so subtle nudges from the marketplace that changed the dynamics associated with staying on your mainframe. Because if I tell you that the tax to stay on your mainframe is going to triple or quadruple over the next several years, that changes the balance. So you have the old guard in the software business who will remain nameless, jacking up the prices because they feel like, you know what, "What are you going to do? What are you going to do other than write me a cheque?" And the answer is, "Well move," right?. >> Yep, it's reached a point like the companies are moving. And what I think companies start to see too is, when we talk about purpose-driven databases, Adam was talking about that in the keynote today too. And we've seen that with customers when we've done builds, what's the right database for this data? And now you can start to get things moving even faster. And you unleash new ways of thinking. And I mean, some of the vendors are doing things like that and the companies aren't happy about it. >> Well, yes, but look, you're talking about Oracle in particular. (group chattering) That's one of them, but Oracle invests in its database and it's two different theories. Adam, today's the right tool for the right job, API and primitives and Oracle takes the kind of Swiss army knife approach. But they do invest if you have hard core mission critical, recovery is everything. There's a risk factor involved there, but if you want to go fast and you're a developer, you're not going to necessarily knock on Oracle's door, you're going to go to get an AWS. But it gets to my question, having done a lot of TCO analysis, it used to be labor, was always two-thirds of the cost. Now with automation, especially in Oracle environments, software license costs are the dominant component and it's maybe less true for SQL server, certainly true for Db2. I remember the early days of the flash, we used to tell customers, install flash. You're going to be able to consolidate, reduce your Oracle licenses when they come up. So that was a preferred strategy, but what are you seeing in terms of the ability? First of all is that a correct premise that software licenses is still a big component or an increasingly large component, and how do you unshackle from that? >> Yeah, so definitely software licensing costs for the OSS and for the databases are huge. I mean, there's numbers out there that like for SQL server enterprise, if you can get somebody off the SQL server enterprise and get them to an open solution like Aurora Postgres or something like that, it's a 90% ROI, and the numbers are similar for Oracle. And I talked to a lot of customers are like, "But we don't know Postgres," but it's not really that different. It's still data modeling. And when you get to these managed services platforms like RDS and Aurora, you free up those DBS to do the higher value things. The ROI of a DBA is not managing memory and desk and babysitting the servers, it's helping the developers build better data models. And those sorts of things that are higher value. So it is a big thing and we're seeing customers saying like, "Help us reduce this licensing cost," and help us be more efficient because the open platforms now, especially in the relational database area, are on par in a lot of ways with the Oracles and the SQL servers. So then you start to say, "Well, what am I gaining by paying and being sort of held hostage to these numbers?" So we definitely see customers making this transition. >> I mean, the point about Postgres is a good one because you're going to get enterprise class recoverability but even EDB would say okay, don't start with your mission critical core, pick around the edges just what he's saying over and over time, you're going to become more cloud native and get to the point, can you get to that point where everything's cloud native, everything is a service, maybe not a 100%, but a large part of your application portfolio can get there, right? >> Yeah, you're going to find those, that goes back to doing that application tiering and evaluation and ROI. So, we have a case study that we did with Constellation Brands, where they really needed a B2B type ordering portal solution. And they looked at sort of the typical vendors in a packaged solution if you will, a cottage type solution. And we proposed doing a full custom solution, soup to nuts and building it natively in AWS. And it was built completely on top of platform services. There was no servers in that environment and we were done. We were using AWS Fargate to run their containers on top of, we were using RDS Postgres, we were using Lambda and in some places we were using DynamoDB for holding inflate orders. And so the whole environment is deployable from one cloud formation template. So it completely changed how we even went through the testing of the thing. 'Cause you ran the same cloud formation template to deploy to a different environment. And you knew you were getting the same exact thing. And so they went from, they no longer had to worry about securing underlying compute, secure the containers, run on top of Fargate, use a platform service for your databases, and it was a beautiful solution for them. >> Yeah, you got to taste of that and your eyes open up and say, "Wow, what's possible?" >> Yeah, its a game changer. >> We heard that from NASDAQ this morning. An amazing story. She said, our first Amazon bill was 20 bucks. I bet it's higher now, but first hits free kind of thing. But the point is when people talk about the AWS bill, et cetera, no question, you should try to optimize that. But at the end of the day, it's about the business value Scott, isn't it? >> Scott: Yeah, it is. >> Hey, thanks so much for coming to theCUBE. It was great perspectives, >> No, thank you guys. I appreciate having you guys on. >> Thank you very much. >> Keep it right there, Dave Nicholson and I will be right back. You're watching theCUBE's coverage of AWS re:Invent 2021. (gentle music)

(innovative music) >> Welcome back to theCUBE's continuous coverage of AWS re:Invent 2021. My name is Dave Vellante, and we are running one of the industry's most important and largest hybrid tech events of the year. Hybrid as in physical, not a lot of that going on this year. But we're here with the AWS ecosystem, AWS, and special thanks to AMD for supporting this year's editorial coverage of the event. We've got two live sets, two remote studios, more than a hundred guests on the program. We're going really deep, as we enter the next decade of Cloud innovation. We're super excited to be joined by Danny Allan, who's the Chief Technology Officer at Veeam, and James Kirschner who's the Engineering Director for Amazon S3. Guys, great to see you. >> Great to see you as well, Dave. >> Thanks for having me. >> So let's kick things off. Veeam and AWS, you guys have been partnering for a long time. Danny, where's the focus at this point in time? What are customers telling you they want you to solve for? And then maybe James, you can weigh in on the problems that customers are facing, and the opportunities that they see ahead. But Danny, why don't you start us off? >> Sure. So we hear from our customers a lot that they certainly want the solutions that Veeam is bringing to market, in terms of data protection. But one of the things that we're hearing is they want to move to Cloud. And so there's a number of capabilities that they're asking us for help with. Things like S3, things like EC2, and RDS. And so over the last, I'll say four or five years, we've been doing more and more together with AWS in, I'll say, two big categories. One is, how do we help them send their data to the Cloud? And we've done that in a very significant way. We support obviously tiering data into S3, but not just S3. We support S3, and S3 Glacier, and S3 Glacier Deep Archive. And more importantly than ever, we do it with immutability because customers are asking for security. So a big category of what we're working on is making sure that we can store data and we can do it securely. Second big category that we get asked about is "Help us to protect the Cloud-Native Workloads." So they have workloads running in EC2 and RDS, and EFS, and EKS, and all these different services knowing Cloud-Native Data Protection. So we're very focused on solving those problems for our customers. >> You know, James, it's interesting. I was out at the 15th anniversary of S3 in Seattle, in September. I was talking to Mai-Lan. Remember we used to talk about gigabytes and terabytes, but things have changed quite dramatically, haven't they? What's your take on this topic? >> Well, they sure have. We've seen the exponential growth data worldwide and that's made managing backups more difficult than ever before. We're seeing traditional methods like tape libraries and secondary sites fall behind, and many organizations are moving more and more of their workloads to the Cloud. They're extending backup targets to the Cloud as well. AWS offers the most storage services, data transfer methods and networking options with unmatched durability, security and affordability. And customers who are moving their Veeam Backups to AWS, they get all those benefits with a cost-effective offsite storage platform. Providing physical separation from on-premises primary data with pay-as-you-go economics, no upfront fees or capital investments, and near zero overhead to manage. AWS and APM partners like Veeam are helping to build secure, efficient, cost-effective backup, and restore solutions using the products you know and trust with the scale and reliability of the AWS Cloud. >> So thank you for that. Danny, I remember I was way back in the old days, it was a VeeamON physical event. And I remember kicking around and seeing this company called Kasten. And I was really interested in like, "You protect the containers, aren't they ephemeral?" And we started to sort of chit-chat about how that's going to change and what their vision was. Well, back in 2020, you purchased Kasten, you formed the Veeam KBU- the Kubernetes Business Unit. What was the rationale behind that acquisition? And then James, I'm going to get you to talk a little bit about modern apps. But Danny, start with the rationale behind the Kasten acquisition. >> Well, one of the things that we certainly believe is that the next generation of infrastructure is going to be based on containers, and there's a whole number of reasons for that. Things like scalability and portability. And there's a number of significant value-adds. So back in October of last year in 2020, as you mentioned, we acquired Kasten. And since that time we've been working through Kasten and from Veeam to add more capabilities and services around AWS. For example, we supported the Bottlerocket launch they just did and actually EKS anywhere. And so we're very focused on making sure that our customers can protect their data no matter whether it's a Kubernetes cluster, or whether it's on-premises in a data center, or if it's running up in the Cloud in EC2. We give this consistent data management experience and including, of course, the next generation of infrastructure that we believe will be based on containers. >> Yeah. You know, James, I've always noted to our audience that, "Hey AWS, they provide rich set of primitives and API's that ISV's like Veeam can take advantage of it." But I wonder if you could talk about your perspective, maybe what you're seeing in the ecosystem, maybe comment on what Veeam's doing. Specifically containers, app modernization in the Cloud, the evolution of S3 to support all these trends. >> Yeah. Well, it's been great to see Veeam expands for more and more AWS services to help joint customers protect their data. Especially since Veeam stores their data in Amazon S3 storage classes. And over the last 15 years, S3 has helped companies around the world optimize their work, so I'd be happy to share some insights into that with you today. When you think about S3 well, you can find virtually every use case across all industries running on S3. That ranges from backup, to (indistinct) data, to machine learning models, the list goes on and on. And one of the reasons is because S3 provides industry leading scalability, availability, durability, security, and performance. Those are characteristics customers want. To give you some examples, S3 stores exabytes the data across millions of hard drives, trillions of objects around the world and regularly peaks at millions of requests per second. S3 can process in a single region over 60 terabytes a second. So in summary, it's a very powerful storage offering. >> Yeah, indeed. So you guys always talking about, you know, working backwards, the customer centricity. I think frankly that AWS sort of change the culture of the entire industry. So, let's talk about customers. Danny do you have an example of a joint customer? Maybe how you're partnering with AWS to try to address some of the challenges in data protection. What are customers is seeing today? >> Well, we're certainly seeing that migration towards the Cloud as James alluded today. And actually, if we're talking about Kubernetes, actually there's a customer that I know of right now, Leidos. They're a fortune 500 Information Technology Company. They deal in the engineering and technology services space, and focus on highly regulated industry. Things like defense and intelligence in the civil space. And healthcare in these very regulated industries. Anyway, they decided to make a big investment in continuous integration, continuous development. There's a segment of the industry called portable DevSecOps, and they wanted to build infrastructure as code that they could deploy services, not in days or weeks or months, but they literally wanted to deploy their services in hours. And so they came to us, and with Kasten K10 actually around Kubernetes, they created a service that could enable them to do that. So they could be fully compliant, and they could deliver the services in, like I say, hours, not days or months. And they did that all while delivering the same security that they need in a cost-effective way. So it's been a great partnership, and that's just one example. We see these all the time, customers who want to combine the power of Kubernetes with the scale of the Cloud from AWS, with the data protection that comes from Veeam. >> Yes, so James, you know at AWS you don't get dinner if you don't have a customer example. So maybe you could share one with us. >> Yeah. We do love working backwards from customers and Danny, I loved hearing that story. One customer leveraging Veeam and AWS is Maritz. Maritz provides business performance solutions that connect people to results, ensuring brands deliver on their customer promises and drive growth. Recently Maritz moved over a thousand VM's and petabytes of data into AWS, using Veeam. Veeam Backup for AWS enables Maritz to protect their Amazon EC2 instances with the backup of the data in the Amazon S3 for highly available, cost-effective, long-term storage. >> You know, one of the hallmarks of Cloud is strong ecosystem. I see a lot of companies doing sort of their own version of Cloud. I always ask "What's the partner ecosystem look like?" Because that is a fundamental requirement, in my view anyway, and attribute. And so, a big part of that, Danny, is channel partners. And you have a 100 percent channel model. And I wonder if we could talk about your strategy in that regard. Why is it important to be all channel? How to consulting partners fit into the strategy? And then James, I'm going to ask you what's the fit with the AWS ecosystem. But Danny, let's start with you. >> Sure, so one of the things that we've learned, we're 15 years old as well, actually. I think we're about two months older, or younger I should say than AWS. I think their birthday was in August, ours was in October. But over that 15 years, we've learned that our customers enjoy the services, and support, and expertise that comes from the channel. And so we've always been a 100 percent channel company. And so one of the things that we've done with AWS is to make sure that our customers can purchase both how and when they want through the AWS marketplace. They have a program called Consulting Partners Private Agreements, or CPPO, I think is what it's known as. And that allows our customers to consume through the channel, but with the terms and bill that they associate with AWS. And so it's a new route-to-market for us, but we continue to partner with AWS in the channel programs as well. >> Yeah. The marketplace is really impressive. James, I wonder if you could maybe add in a little bit. >> Yeah. I think Danny said it well, AWS marketplace is a sales channel for ISV's and consulting partners. It lets them sell their solutions to AWS customers. And we focus on making it really easy for customers to find, buy, deploy, and manage software solutions, including software as a service in just a matter of minutes. >> Danny, you mentioned you're 15 years old. The first time I mean, the name Veeam. The brilliance of tying it to virtualization and VMware. I was at a VMUG when I first met you guys and saw your ascendancy tied to virtualization. And now you're obviously leaning heavily into the Cloud. You and I have talked a lot about the difference between just wrapping your stack in a container and hosting it in the Cloud versus actually taking advantage of Cloud-Native Services to drive further innovation. So my question to you is, where does Veeam fit on that spectrum, and specifically what Cloud-Native Services are you leveraging on AWS? And maybe what have been some outcomes of those efforts, if in fact that's what you're doing? And then James, I have a follow-up for you. >> Sure. So the, the outcomes clearly are just more success, more scale, more security. All the things that James is alluding to, that's true for Veeam it's true for our customers. And so if you look at the Cloud-Native capabilities that we protect today, certainly it began with EC2. So we run things in the Cloud in EC2, and we wanted to protect that. But we've gone well beyond that today, we protect RDS, we protect EFS- Elastic File Services. We talked about EKS- Elastic Kubernetes Services, ECS. So there's a number of these different services that we protect, and we're going to continue to expand on that. But the interesting thing is in all of these, Dave, when we do data protection, we're sending it to S3, and we're doing all of that management, and tiering, and security that our customers know and love and expect from Veeam. And so you'll continue to see these types of capabilities coming from Veeam as we go forward. >> Thank you for that. So James, as we know S3- very first service offered in 2006 on the AWS' Cloud. As I said, theCUBE was out in Seattle, September. It was a great, you know, a little semi-hybrid event. But so over the decade and a half, you really expanded the offerings quite dramatically. Including a number of, you got on-premise services things, like Outposts. You got other services with "Wintery" names. How have you seen partners take advantage of those services? Is there anything you can highlight maybe that Veeam is doing that's notable? What can you share? >> Yeah, I think you're right to call out that growth. We have a very broad and rich set of features and services, and we keep growing that. Almost every day there's a new release coming out, so it can be hard to keep up with. And Veeam has really been listening and innovating to support our joint customers. Like Danny called out a number of the ways in which they've expanded their support. Within Amazon S3, I want to call out their support for our infrequent access, infrequent access One-Zone, Glacier, and Glacier Deep Archive Storage Classes. And they also support other AWS storage services like AWS Outposts, AWS Storage Gateway, AWS Snowball Edge, and the Cold-themed storage offerings. So absolutely a broad set of support there. >> Yeah. There's those, winter is coming. Okay, great guys, we're going to leave it there. Danny, James, thanks so much for coming to theCUBE. Really good to see you guys. >> Good to see you as well, thank you. >> All right >> Thanks for having us. >> You're very welcome. You're watching theCUBE's coverage of 2021 AWS re:Invent, keep it right there for more action on theCUBE, your leader in hybrid tech event coverage, right back. (uplifting music)

(upbeat music) >> Welcome back to "The Cube's" continuous coverage of AWS re:Invent 2021. We're running one of the industry's most important and largest hybrid tech events of the year with AWS and its ecosystem partners. And of course, special thanks to AMD for supporting this year's editorial coverage at the event. We got two live sets. We had two remote sets, one in Boston and one in Palo Alto. We got more than 100 guests coming on the program, and we're looking deep into the next decade of cloud innovation. We're super excited to be joined by Ali Zafar, who's the senior director of platform strategy and operations at Dropbox. Ali, great to see you. Thanks for coming on. >> Awesome, it's a pleasure to be here with you, Dave. >> So hey, what's your day job like at Dropbox and what's your role? >> Got it. So I actually oversee the global supply chain at Dropbox. Also all of the capacity planning, which entails both our budget and also capacity requirements at Dropbox. And then I also focus on the platform product management side, which is basically building our build versus buy and our overall roadmap for our platform in the long run. >> Great, thank you. So, everybody knows Dropbox, but maybe you could talk a little bit about your business, your mission, and how that's evolved over the past several years. >> Got it. So Dropbox is a global collaboration platform and our mission at Dropbox is to help design a more enlightened way of working. Dropbox has over 700 million registered users and over 550 billion pieces of content. So taking a step back Dave, Dropbox helps with all of your content. Think of this as videos as music, even your tax returns, allows you to organize all of this content and then you can share this content with anybody at any time. You can also take Dropbox to work and actually it makes you even more productive in the workplace. Integrating all of your tools seamlessly, also allowing you to collaborate with all of your teams internally and also externally. >> Thank you, Ali. When Dropbox was founded, the cloud was really nascent, right? So it was early days, and so a lot has changed since the mid last decade. And of course with remote work and hybrid work, that's had to be a real tailwind to your business, but maybe you could explain your cloud and your hybrid cloud strategy. >> Got it, you're spot on Dave. So Dropbox has always been hybrid since its inception in 2007. And when I say hybrid, I mean we have our own on-prem infrastructure and then we also leverage public cloud. Now public cloud still to these days, remains absolutely critical for Dropbox to serve all of its customer needs. And when we talk about the decision between public or private, we think about three or four key things. One is the total cost of ownership, we look at go-to-market, we also look at our customer requirements and the latest technology that's available in the market. And then any international data storage requirements to make the decision of going towards public or private for that specific use case. >> So, I wonder if we could follow up on that. Maybe you could talk about the key business considerations as an SAS storage provider. What are the real drivers and in your business framework? >> Got it. At the end of the day, what really matters for us Dave, is to actually think about our customers and delight them. And what better than to focus on performance, reliability and also security, right? So we want to make sure that the infrastructure that we have today, allows Dropbox to actually solve for this specific use case for our customers. You know, what do they care about? While also doing this in a very efficient, managed way. So to summarize that, looking at performance, looking at liability, looking at scalability, looking at efficiency, and then also compliance. >> So that leads me to my next question, is about the EC2 instances that you use. I know you make heavy use of AMD compute. How did you come to that decision? Was it these factors? Was it all performance? How did you migrate to really enable that capability? How complex was that? >> Got it. So AMD has always been our key strategic partners partners. The partnership is well over four to five years right now, and we've been leveraging them on our on-prem infrastructure for compute. So we've always had AMD in our infrastructure and when the time came where AWS was also leveraging some of the AMD instances, we wanted to see how we can expand the partnership with AMD and AWS and also experiment with these instances. So we looked at some of the tooling updates that were required. We also looked at specific instances, which are either compute optimized and memory optimized instances, and then we actually built our footprint on AMD. And what we saw is that the overall performance improvement and also cost improvements that we got per specific workloads was actually extremely, was overall awesome results for Dropbox and our end customers. And we have been using them ever since. >> What kind of business impact did that make? Did it make a difference to your business that was noticeable? >> On the business side, I think primarily it was more on the TCO side, which is where we got most of the benefits on the cost side. And then also for some of our internal workloads, we also saw benefit to our internal developers that are using some of those workloads. >> So, you guys have become the poster child for hybrid and a lot has been talked about about you all, but I wonder if you could help us understand what part of your infrastructure is going to be better served by public cloud versus doing your own I T on-prem. What are some of the value drivers that are making you push workloads into the public cloud? Help us understand that better and squint through that. >> Got it, I get asked that question a lot. So public cloud in general allows for faster go-to-market. Think about this as like product launches, feature launches, also international expansion. It allows us to scale and then also leveraging some of the existing technologies out there in the market for some of the common workloads. So just taking a step back and thinking about Dropbox, we keep on evaluating also the criteria and then also specific workloads on what makes sense on private or public cloud. And AWS had some instances like S3 RDS and EC2 that when we started looking at, we knew that some of our key services like data platform, some parts of the MLN A I, and even paper platform would make more sense for us to actually leverage some of these in a public cloud for that. >> So what are the characteristics of the workload that are better suited to be an AWS? What's the ideal workload profile? You know, we talk about ideal customer profile. What's the ideal workload profile for the AWS cloud? >> Got it, so the way we think about it, at least, we call it the rule of three at Dropbox. And that means we look at scale first, we look at technology and innovation and what I mean by that is, is there a faster innovation in the public cloud and is that workload common enough that there's already a lot of work going on in public cloud, then there's no reason for us to actually innovate faster than that, we probably can't. And if the scale is not large enough. So when we talk about our storage side, like magic pocket, the scale is large enough where innovating there makes sense and it's better for the end customer. So we would probably go towards private cloud there. But then when we talk about international expansion, when we talk about faster go-to-market or some of the innovation in the MLN A I space, it really makes sense to use public cloud because of all of the advancements that we've seen there. >> So let me circle back to the business benefits and impact of the AMD based compute specifically, but you talked about TCO before, so there's certain things you mentioned on-prem you sometimes use. If the thing's hardened, you don't want to necessarily rip and replace it, but if you can accelerate go-to-market and you spin up things in the cloud, that makes sense. You mentioned customer requirements, so that just kind of depends. And then the international expansion and scale. So it comes down to those whatever four or five factors, right? The TCO, those other factors that I mentioned. Kind of the high level benefits, if you wouldn't mind summarizing for us, Ali. >> Yeah, I think you're spot on there. So there's looking at the overall TCO, right? The cost of serving the overall cloud, looking at go-to-market in general, can we leverage public cloud and go-to-market faster, obviously meeting our end customer requirements. We also looked at international expansion, any of the customer's data that is stored outside of the U S is all on public cloud for Dropbox. No plans in the short term to do something different there. And then also just looking at, like I mentioned, anything in the technology space that is ongoing, that we can leverage feature side or the product side for our customers, like A I or M L, we are going to leverage public cloud there. >> So of course you know, we've followed the progression of semiconductor technology for decades. This industry is marched to the cadence of performance improvements. What do the futures hold from a technology roadmap standpoint, and particularly as it relates to leveraging AMD EC2 instances, Ali? >> Got it. So Dropbox is in a very unique position where we actually leverage AMD both on-prem and for public cloud, leveraging some of the AWS EC2 instances like you mentioned. And EPYC processors from AMD are what we're using today, both on the hybrid infrastructure side and the performance. And also the TCO benefits are real and something that we are observing on a day-to-day basis. So we are going to be leveraging that technology even in the future, and the partnership with the AMD continues to be very, very strong for Dropbox. >> Well, Ali, I really appreciate you coming on "The Cube" as part of our coverage. It's great to have you. Love to have you back sometime. >> Awesome, thank you. And also just last thing we wanted to also call out that we are also going to be experimenting with probably Milan that is coming out. Rome is the current processors from AMD that we have been leveraging and as Milan comes available, we do want to continue to evaluate it and see how we can fit it in our infrastructure. >> So their are generations are city-based. Are they all Italian city-based, or are we going to run out of cities soon? (both laughing) >> Got it. Again, the partnership with both AWS and AMD is something that I'm very proud of. >> Excellent. >> Thank you so much. Thank you, Dave. >> Great to have you Ali, and really appreciate you watching. Keep it right there for more action on "The Cube", your leader in hybrid tech event coverage. (calm music)