>>from around the globe. It's the Cube with digital coverage of aws reinvent 2024 sponsored by Intel and AWS. Yeah. >>Welcome back here to our coverage here on the Cube of AWS reinvent 2020. It's now pleasure. Welcome. Sean. Vice to the program was the vice president of databases at AWS and Sean. Good day to you. How you doing, sir? >>I'm doing great. Thank you for having me. >>You bet. You bet. Thanks for carving out time. I know it was a very a busy couple of weeks for the A. W s team on DSO certainly was kicked off key notes today. We heard right away that there's some fairly significant announcements that I know certainly affect your world at AWS. Tell us a little bit about those announcements, and then we'll do a little deeper divers. You you go through >>sure, you know. And he made three big announcements this morning as it relates to databases, one of whom was around Aurora serverless V two on. Do you could just think of that as, uh um, no infrastructure whatsoever to manage and Aurora server list that can scale for, you know, from zero to hundreds of thousands of transactions in a fraction of a second, literally with no infrastructure to manage. So it's a really easy way to build applications in the cloud. Eso excited about that? Another big announcement WAAS related to a lot of our customers today are really they're using the right tool for the right job. In other words, they're not trying toe GM all of their data into one database management systems. They're breaking app down into smaller parts. They pick the right tool for the right job. And with that context, we announce glue elastic views, which just allows you to very easily write a sequel. Query most. There's a lot of developers that understand sequel. So if I could easily write a sequel query to reach out to the source databases and then materialize, um, that data into a different target, Um, that's a really simple way toe. Build new customer experiences and make the most of the databases you have. Aan den. The third big announcement remained today was called Babble Eso Babel. Babel Fish is really a a compatibility or a sequel server compatibility layer on Aurora post grass. So if you have ah sequel server application. You've been trying to migrate it to post grass, and you've been wishing for an easier way to get that done. Babel Fish allows you to take your T sequel or your Microsoft sequel server application connected to post grass. Using your same client drivers with little to no code change eso That's a big deal for those that are trying to migrate from commercial systems to open source. And then finally, we didn't stop there as we thought about Babel, Um, and talked to a lot of customers about it. We actually are open sourcing the technology, so it will be available later in 21. All the development will be done open transparently hosted on get hub and licensed under Apache 20 so those that's kind of one lap around the track, if you will, of the big announcements from today How big >>the open source announcement to me. I mean, that's fairly significant that that you're opening up this new opportunity thio the entire community, um, that you're willing to open it up, and I'm sure you're gonna have you know, I mean, this is this is gonna be I would imagine Ah, very popular destination for a lot of folks. >>Yeah, I think so, too. You know, I'm I'm personally, I'm a believer that every customer can use data to build a foundation for future innovation. And to me, a lot of things start and end with data. As we know, data really is a foundational component of at a swell A systems and, you know, and you know, what we found is not every customer can plan for every contingency that happens. But what they can do is build a strong foundation. So, you know, and with a strong foundation, you really stand the best chance to overcome whatever that next unexpected thing is or innovate new ways. And with that is a backdrop. We think this open source piece is a big deal. Why? I'll tell you, you know, it's just us right now. But if I told you the story behind the story, I have met so many customers over the last few years that you know, John, if you and I were sitting down with them, it kind of sounds like this. You sit down, you talk to somebody and they'll say things like, Hey, I've built, you know, we've built years and years and years of application development against sequel server. We really don't like the punitive commercial licensing and, you know, we're trying to get over Thio open source, but we need an easier way and, you know, and we thought about that long and hard and, you know, we came up with the team, came up with a wonderful solution for this, But to tell you the truth, as we were building Babel fish and talking to customers, what became really clear with the community enterprises in I S V s and s eyes is they all basically said, Hey, if there was a way where we could go and extend this, um for, you know, like it could be Boy, if this thing supported to more features, that would be awesome. But if it was open source, that would be even better, because then we could we could take things under our own control so that that's what truly motivated this decision to go open source and based on conversations we've had in the decisions we made, we actually think it's it's really big. It's really big for everybody who has been trying to move off of commercial systems and over toe open source. You. >>Let's talk about transforming your kind of your database mindset in general right now from a client's perspective, especially for somebody who was considering, you know, substantial moves, you know, a major reconfigurations off their processes. What's the process that you go through with them to evaluate their needs, to evaluate their capabilities, to evaluate their storage? All that, you know, that comes into play here and help them to get thio kind of the end of the rainbow >>because it z absolutely, you know, so it really depends on who you're talking Thio and no, at this stage of the game, the clouds been around now for 10, 14 years. I think it is something in that range, you know? So a lot of the early cloud adopters, you know, they've been here and they've been building in a certain way. Um and you know, you and I know early cloud adopters by way of watching streaming media, ordering rideshare, taking a selfie, you know, and you know, we have these great application experiences and we expect them to work all the time at Super Low. Leighton See, they should always be available. So you know, the single biggest thing we learned from Early Cloud builders was there's no such thing as one size football. There's one thing doesn't fit anything at all. Um, that's kind of the way data was, you know, 20 years ago. But today, if you take the learning from these early cloud builders, the journey that we go on with, let's say a mid to late stage cloud a doctor. We're all excited on, you know, sort of. If they can start now today, where Early Cloud Wilders have done a bunch of pioneering, they get excited. So So what happens is, um, there's usually to kind of conversations. One is how do we you know, we've got all these databases that we self managed on premise. How do we bring those into the cloud? And then how do we stop doing undifferentiated heavy lifting? In other words, what they're saying is, we don't want to do patching and back up and monitoring that Z instead, our precious resources should be working on innovations for the business. So in that context, you and I would end up talking to somebody about moving to fully managed services like an already s, for example, um and then the other conversation we have with customers is is the one about breaking free, which is hey, a burn on commercial. I wanna move for open source. And in that context, there are a lot of customers today that they'll move to the cloud. And then and then when they get there as a first step, their second step is to is to migrate over toe open source. And then that third piece is folks that are trying to build for the cloud, these modern APS. And in that context, they follow the playbook of these early cloud builders, which is what you take this big app. You break it into smaller parts and then they pick the right tool for the right job. So that's that's kind of the conversation that we go through there. And finally, what I would say is, most customers say that they'll say to me, What do you mean by picking the right tool for the right job? And the mindset is very different than the one that we all grew up in from 20 years ago. 20 years ago, you just bought a database platform. And then whatever the business was trying to do, you you you would try to support that access pattern on on that database choice. But today, the new world that we live in, it really is. Let's start with the business use case first, understand the access pattern and then pick the best optimized database storage for that. So that's that's kind of how those conversations go. >>You've got what, 15, 14, 15 different data based instruments, you know, like in your tool chest? Um, how how is that evolution occurred? Um because I'm sure, you know one, but got another big at another big at another, looking at different capabilities, different needs. So I mean, >>kind of walked me >>through that a little bit and how you've gotten to the point that you've got 15 >>Tonto eso. So one of the things that you know I'd start off with here, like the question is, Well, if there's 15 today, is there gonna be 100 tomorrow? The real answer is, I don't know, you know, And but what I do know is there's really a handful of categories around data models and access patterns that if you will kind of fill out the portfolio if you will. Um, the first one is around relation. Also, relational databases have been around for a long time. It has a certain set of characteristics that people have come to appreciate and understand and, you know, and we provide a set of services that provide fully managed relational services. Let it be for things like Oracle or sequel, server or open source, like Maria DB or my sequel or Post Press and even Aurora, which provides commercial grade performance availability and scale it about 1/10 the cost of commercial. So you know, there's a handful of different services in that context. But there's new services in this key value. And think of a key value access pattern along the lines of you. Imagine. We order you order a ride share and you're trying to track a vehicle every second. So on your phone you can see it moving across your phone. And now imagine if you were building that at our a million people going to do that all at the same time or 10. So in that kind of access pattern, a product like dynamodb is excellent because It's designed for basically unlimited scale, really high throughput. So developer doesn't have toe really worry about a million people. 10 million people are one. This thing can just scale inevitably. Yeah, it's just not an issue. And, you know, I'll give you one other example like, um, in Neptune, which is a graph database. So you and I would know graph databases by way of seeing a product recommendation, for example, Um, and you know, grab the beauty of a graph databases. It's optimized for highly connected data. In other words, as a developer, I can what I can do with a few lines of code and a graph database because it's optimized for all these different relationships. I might try to do that in a different system that I might write 1500 lines of codes and because it was never designed for something like highly connect the data like graph. So that's kind of the evolution of how things there's just these different categories that have to do with access patterns and data models. And our strategy is simple. In each category, we wanna have the very best AP is available for our customers. Let's >>talk about security here for a moment because you have, you know, these just these tremendous reservoirs now, right that you've built up in capabilities got, you know, new data centers going up every day. It seems like around around the country and around the world, security or securing data nevermore important on dnep ver mawr, I guess on the radar of the bad actors to at the same time because of the value of that data. So just if you would paint the picture in terms of security awareness three encryption devices that you're now deploying the stuff that's keeping you up at night, I would think probably falls into this category a little bit. Eso Let's just take it on security and the level of concern. And then what you at a w s are doing about that? >>Yeah. So, you know, when I talked to customers, I always remind people security is a shared responsibility on De So Amazon's piece of that is the infrastructure that we build the processes that we have, you know, from how people you know can enter a building toe, what they can do in an environment. The auditing to the encryption systems that rebuild. Um, there's there's three infrastructure responsibility, which, you know, we think about every second of every day. Um, Andi, it's, you know, yes, it's one of those things that keeps you up at night. But you have to kind of have this level of paranoia, if you will. There's bad actors everywhere. And, you know, that mindset is kind of, you know, kind of helps you stay focused on Ben. There's the customers responsibility to in in terms of how they think about security. So, you know, um and what that means is, uh, you know, best practices around how they how they integrate identity and access management into their solution. Um, you know how they use how they rotate encryption keys, how they apply encryption and all the safeguards that you would expect the customer do so together, you know, we work with our customers to ensure that our systems are are secure. Um, and the only other thing that I would add to this is that, you know, kind of in the old world. And I keep bringing up the old world because security in the old world was sort of one of those things. Like if you go back 20 years ago. You know, security sometimes is one of those things that you think about a little bit later in the cycle. And I've met a lot of customers that tryto bolt on security and it never works. It's just hard to just bolt it into an app. But the really nice thing about thes fully managed services in the cloud they have security built right in. So security, performance and availability is built right into these fully managed A p I s eso customer doesn't have to think about Well, how do I add this capability onto it? You know, in some sense, it could be a simple is turning a feature on or something like encryption being turned on by default, and they don't have to do anything. So, you know, there it's just a completely different world that we live in today, and we try to improve it every second of every day. >>Well, Sean, it's nice to know that you're experiencing the paranoia for all your customers. That Zaveri very gracious yesterday There. Hey, thanks for the time. I appreciate it. I know you're very busy the next couple of weeks with the number of leadership sessions and intermediate sessions as well with AWS reinvent. So thanks again for carving a little bit of time for us here today on the Cube. >>You bet, John. Thank you. I really appreciate it. >>Take care.