>>Hello friends and welcome back to Fabulous Las Vegas, Nevada, where we are live from the show floor at AWS Reinvent. My name is Savannah Peterson, joined by my fabulous co-host John Furrier. John, how was your lunch? >>My lunch was great. Wasn't very complex like it is today, so it was very easy, >>Appropriate for the conversation we're about >>To have. Great, great guests coming up Cube alumni and great question around complexity and how is wellbeing teams be good? >>Yes. And, and and on that note, let's welcome John from DeWit as well as Danny from Inox. I swear I'll be able to say that right by the end of this. Thank you guys so much for being here. How's the show going for you? >>Excellent so far. It's been a great, a great event. You know, back back to pre Covid days, >>You're still smiling day three. That's an awesome sign. John, what about you? >>Fantastic. It's, it's been busier than ever >>That that's exciting. I, I think we certainly feel that way here on the cube. We're doing dozens of videos, it's absolutely awesome. Just in case. So we can dig in a little deeper throughout the rest of the segment just in case the audience isn't familiar, let's get them acquainted with your companies. Let's start with do it John. >>Yeah, thanks Savannah. So do it as a global technology company and we're partnering with deleted cloud providers around the world and digital native companies to provide value and solve complexity. John, to your, to your introductory point with all of the complexities associated with operating in the cloud, scaling a business in the cloud, a lot of companies are just looking to sort of have somebody else take care of that problem for them or have somebody they can call when they run into, you know, into problems scaling. And so with a combination of tech, advanced technology, some of the best cloud experts in the world and unlimited tech support or we're offloading a lot of those problems for our customers and we're doing that on a global basis. So it's, it's an exciting time. >>I can imagine pretty much everyone here on the show floor is dealing with that challenge of complexity. So a couple customers for you in the house. What about you Danny? >>I, I come from a company which operates in a financial industry market. So we essentially a global broker, financial trading broker. Which what this means for those people who don't really understand, essentially we allow clients to be able to trade digitally and speculate with different pricing, pricing tools online. We offer a different products for different type of clients. We have institutional clients, we've got our affiliates, partners programs and we've got a retail clients and this is where AWS and Doit comes handy allows us to offer our products digitally across the globe. And one of the key values for us here is that we can actually offer a product in regions where other people don't. So for example, we don't compete in North America, we don't compete in EME in Europe, but we just do it in AWS to solve our complex challenges in regions that naturally by, depending on where they base, they have like issues and that's how we deliver our product. >>And which regions, Latin >>America, Latin, the entire Africa, subcontinent, middle East, southeast Asia, the culture is just demographic is different. And what you used to have here is not exactly what you have over there. And obviously that brings a lot of challenges with onboarding and clients, deposit, trading activities, CDN latency, all of >>That stuff. It's interesting how each region's different in their, their posture with the cloud. Someone roll their own, someone outta the box. So again, this brings up this theme this year guys, which is about end to end seeing purpose built like specialty solutions. A lot of solutions going end to end with data makes kind of makes it more complicated. So again, we got more complexity coming, but the greatest the cloud is, you can abstract that away. So we are seeing this is a big opportunity for partners to innovate. You're seeing a lot of joint engineering, a lot more complexities coming still, but still end to end is the end game so to speak. >>A absolutely John, I mean one, one of the sort of ways we describe what we try to do for our customers like Equinox is to be your co-pilot in the cloud, which essentially means, you know, >>What an apt analogy. >>I think so, yeah, >>Well, well >>Done there. I think it works. Yvanna. Yeah, so, so as I mentioned, these are the majority or almost all of our customers are pretty sophisticated tech savvy companies. So they don't, you know, they know for most, for the most part what they're trying to achieve. They're approaching scale, they're at scale or they're, or they're through that scale point and they, they just wanna have somebody they can call, right? They need technology to help abstract away the complex problem. So they're not doing so much manual cloud operational work or sometimes they just need help picking the next tech right to solve the end to end use case that that they're, that they're dealing with >>In business. And Danny, you're rolling out solutions so you're on, you're on the front lines, you gotta make it easier. You didn't want to get in the weeds on something that should be taken care of. >>Correct. I mean one of the reasons we go do it is you need to, in order to involve do it, you need to know your problems, understand your challenges, also like a self review only. And you have to be one way halfway through the cloud journey. You need to know your problems, what you want to achieve, where you want to end up a roadmap for the next five years, what you want to achieve. Are we fixing or developing a building? And then involve those guys to come and help you because they cannot just come with magic one and fix all your problems. You need to do that yourself. It's not like starting the journey by yourself. >>Yeah. One thing that's not played up in this event, I will say they may, I don't, they missed, maybe Verner will hit it tomorrow, but I think they kind of missed it a little bit. But the developer productivity's been a big issue. We've seen that this year. One of the big themes on the cube is developer productivity, more velocity on the development side to keep pace with what's on, what solutions are rolling out the customers. And the other one is skills gap. So, and people like, and people have old skills, like we see VMware being bought by Broadcom for instance, got a lot of IT operators at VMware, they gotta go cloud somewhere. So you got new talent, existing talent, skill gaps, people are comfortable, yet the new stuff's there, developers gotta be more productive. How do you guys see that? Cuz that's gonna be how that plays now, it's gonna impact the channel, the partnership relationship, your ability to deliver. >>What's your reaction to that first? Well I think we obviously have a tech savvy team. We've got developers, we've got dev, we've got infrastructure guys, but we only got so much resource that we can afford. And essentially by evolving due it, I've doubled our staff. So we got a tech savvy senior solution architects which comes to do the sexy stuff, actually develop and design a new better offering, better product that makes us competitive. And this is where we involved, essentially we use the due IT staff as an staff employees that our demand is richly army of qualified people. We can actually cherry pick who we want for the call to do X, Y, and Z. And they're there to, to support you. We just have to ask for help. And this is how we fill our gap from technical skills or budget constrained within, you know, within recruitment. >>And I think, I think what, what Danny is touching on, John, what you mentioned is, is really the, the sort of the core family principle of the company, right? It's hard enough for companies like Equinox to hire staff that can help them build their business and deliver the value proposition that they're, that they see, right? And so our reason for existence is to sort of take care of the rest, right? We can help, you know, operate your cloud, show you the most effective way to do that. Whether they're finops problems, whether they're DevOps problems, whether dev SEC ops problems, all of these sort of classic operational problems that get 'em the way of the core business mission. You're not in the business of running the cloud, you're in the business of delivering customer value. We can help you, you know, manage your cloud >>And it's your job to do it. >>It is to do it >>Can, couldn't raise this upon there. How long have y'all been working together? >>I would say 15 months. We took, we took a bit of a conservative approach. We hope for the baseball, prepare for the worst. So I didn't trust do it. I give them one account, start with DEF U A C because you cannot, you just have to learn the journey yourself. So I think I would, my advice for clients is give it the six months. Once you establish a relationship, build a relationship, give them one by one start slowly. You actually understand by yourself the skills, the capacity that they have. And also the, for me consultants is really important And after that just opens up and we are now involving them. We've got new project, we've got problem statement. The first thing we do, we don't Google it, we just say do it. Log a ticket, we got the team. You're >>A verb. >>Yeah. So >>In this case we have >>The puns are on list here on the Cuban general. But with something like that, it's great. >>I gotta ask you a question cuz this is interesting John. You know, we talked last year on the cube and, and again this is an example of how innovations playing out. If you look at the announcements, Adam Celski did and then sw, he had 13 or so announcements. I won't say it's getting boring, but when you hear boring, boring is good. When you start getting into these, these gaps in the platforms as it grows. I won't say they was boring cause that really wasn't boring. I like the data >>Itself. It's all fascinating, John, >>But it, but it's a lot of gap filling, you know, 50 connectors you got, you know, yeah. All glue layers being built in AI's critical. The match cloud is there. What's the innovation? You got a lot of gaps being filled, boring is good. Like Kubernetes, we say there boring means, it's being invisible. That means it's going away. What's the exciting things from your perspective in cloud here? >>Well, I think, I mean, boring is an interesting word to use cuz a company with the heritage of AWS is constantly evolving. I mean, at the core of that company's culture is innovation, technology, development and innovation. And they're building for builders as, as you know, just as well as I do. Yeah. And so, but what we find across our customer base is that companies that are scaling or at scale are using maybe a smaller set of those services, but they're really leveraging them in interesting ways. And there is a very long tail of deeper, more sophisticated fit for purpose, more specific services. And Adam announced, you know, who knows him another 20 or 30 services and it's happening year after year after year. And I think one of the things that, that Danny might attest to is, I, I spoke about the reason we exist and the reason we form the company is we hold it very, a very critical part of our mission is to stay abreast of all of those developments as they emerge so that Danny and and his crew don't have to, right? And so when they have a, a, a question about SageMaker or they have a question about sort of the new big data service that Adam has announced, we take it very seriously. Our job is to be able to answer that question quickly and >>Accurately. And I notice your shirt, if you could just give a little shirt there, ops, cloud ops, DevOps do it. The intersection of the finance, the tuning is now we're hearing a lot of price performance, cost recovery, not cost recovery, but cost management. Yeah. Optimizing. So we're seeing building scale, but now, now tuning almost a craft, the craft of the cloud is here. What's your reaction to that? It, >>It absolutely is. And this is a story as old as the cloud, honestly. And companies, you know, they'll, they'll, companies tend to follow the same sort of maturity journey when they first start, whether they're migrating to the cloud or they were born in the cloud as most of our customers are. There's a, there's a, there's an, there's an access to visibility and understanding and optimization to tuning a craft to use your term. And, and cost management truly is a 10 year old problem that is as prevalent and relevant today as it was, you know, 10 years ago. And there's a lot of talk about the economics associated with the cloud and it's not, certainly not always cheaper to run. In fact, it rarely is cheaper to run your business from any of the public cloud providers. The key is to do it and right size it and make sure it's operating in accordance and alignment with your business, right? It's okay for cloud process to go up so long as your top line is also >>Selling your proportion. You spend more cloud to save cloud. That's it's >>Penny wise, pound full. It's always a little bit, always a little bit of a, of a >>Dilemma on, on the cost saving. We didn't want to just save money. If you want to save money, just shut down your services, right? So it's about making money. So this is where do it comes, like we actually start making, okay, we spend a bit more now, but in about six months time I will be making more money. And we've just did that. We roll out the new application for all the new product offering host to AWS fully with the guys support, a lot of long, boring, boring, boring calls, but they're productive because we actually now have a better product, competitive, it's tailored for our clients, it's cost effective. And we are actually making money >>When something's invisible. It's working, you know, talking about it means it's, it's, it's operational. >>It's exactly, it's, >>Well to that point, John, one of the things we're most proud of in, you know, know this year was, was the launch of our product we called Flex Save, which essentially does exactly what you've described. It's, it's looking for automation and, and, and, and automatic ways of, yes. Saving money, but offering the opportunities to, to to improve the economics associated with your cloud infrastructure. >>Yeah. And improving the efficiency across the board. A hundred percent. It, it's, oh, it's awesome. Let's, and, and it's, it's my understanding there's some reporting and insights that you're able to then translate through from do it to your CTO and across the company. Denny, what's that like? What do you get to see working >>With them? Well, the problem is, like the CTO asked me to do all of that. It is funny he thinks that he's doing it, but essentially they have a excellent portal that basically looks up all of our instances on the one place. You got like good analytics on your cost, cost, anomalies, budget, costal location. But I didn't want to do that either. So what I have done is taken the next step. I actually sold this to the, to my company completely. So my finance teams goes there, they do it themselves, they log in, check, check, all the billing, the costal location. I actually has zero iteration with them if I don't hear anything from them, which is one of the benefits. But also there is lot of other products like the Flexe is virtually like you just click a finger and you start saving money just like that. Easy >>Is that easy button we've been talking about on >>The show? Yeah, exactly, exactly how it is. But there is obviously outside of the cost management, you actually can look at what is the resource you using do actually need it, how often you use it, think about the long term goal, what you're trying to achieve, and use the analytics to, and actually I have to say the analytics much better than AWS in, in, in, in cmp. It's, it's just more user friendly, more interactive as opposed to, you know, building the one in aws. >>It's good business model. Make things easy for your customers. Easy, simple >>To use. >>It's gotta be nice to hear John. >>Well, so first of all, thank you daddy. >>We, we work, but in all seriousness, you know, we, we work, Danny mentioned the trust word earlier. This is at the core of if we don't, if we're not able to build trust with our clients, our business is dead. It, it just doesn't exist. It can't scale. In fact, it'll go the opposite direction. And so we're, we work very, very hard to earn that trust and we're willing to start small to Danny's example, start small and grow. And that's why we're very, one of the things we're most proud of is, is how few customers tend to leave us year over year. We have customers that have been with us for 10 years. >>You know, Andy, Jesse always has, I just saw an interview, he was on the New York Times event in New York today as a CEO of Amazon. But he's always said in these build out phases, you gotta work backwards from the customer and innovate on behalf of the customer. Cause that's the answer that will always be a good answer for the outcome versus optimizing for just profit, you know what I'm saying? Or other things. So we're still in build out mode, >>You know, as a, as a, as a core fundamental sort of product concept. If you're not solving important problems for our customer, what are you, why, why are you investing? It just >>Doesn't make it. This is the beauty we do it. We actually, they wait for you to come to do the next step. They don't sell me anything. They don't bug me with emails. They're ready. When you're ready to make that journey, you just log a ticket and then come and help you. And this is the beauty. You just, it's just not your, your journey. >>I love it. That's a, that's a beautiful note to lead us to our new tradition on the cube. We have a little bit of a challenge for the both of you. We're looking for your 32nd Instagram real thought leadership sizzle anecdote. Either one of you wanna go first. John looks a little nauseous. Danny, you wanna give it a go? >>Well, we've got a few expressions, but we don't Google it. We just do it. And the key take, that's what we do now at, at, and also what we do is actually using their stuff as an influence employees richly. Like that's what we do. >>Well done, well done. Didn't even need the 30 seconds. Fantastic work, Danny. I love that. All right, John, now you do have to go. Okay, >>I'll goodness. You know, I'll, I'll, I'll, I'll I'll go back to what I mentioned earlier, if that's okay. I think we, you know, we exist as a company to sort of help our customers get back to focusing on why they started the business in the first place, which is innovating and delivering value to customers. And we'll help you take care of the rest. It's as simple as that. Awesome. >>Well done. You absolutely nailed it. I wanna just acknowledge your fan club over there watching. Hello everyone from the doit team. Good job team. I love, it's very cute when guests show up with an entourage to the cube. We like to see it. You obviously deserve the entourage. You're, you're both wonderful. Thanks again for being here on the show with Oh yeah, go ahead >>John. Well, I would just like to thank Danny for, for agreeing to >>Discern, thankfully >>Great to spend time with you. Absolutely. Let's do it. >>Thank you. Yeah, >>Yeah. Fantastic gentlemen. Well thank you all for tuning into this wonderful start to the afternoon here from AWS Reinvent. We are in Las Vegas, Nevada with John Furier. My name's Savannah Peterson, you're watching The Cube, the leader in high tech coverage.

>>Hello everyone. Welcome back to the Cube's Live coverage. I'm John Fur, host of the Cube. We got two sets here, three sets total. Another one in the executive center. It's our 10th year covering AWS Reinvent. I remember 2013 like it was yesterday. You know, now it's a massive of people buying out restaurants. 35,000 people now it's 55,000, soon to be 70,000 back. Great event. Continuing to set the standard in the industry. We had an amazing guest here, Leah Bibo, vice President of Product Marketing. She's in charge of the messaging, the product, overseeing how these products gonna market. Leah, great to see you. Thanks for joining me on the Cube today. >>Absolutely. It's great to be here. It's also my 10 reinvent, so it's, it's been a wild ride. >>Absolutely. Yeah. You and I were talking before we came on camera, how much we love products and yes, this is a product-centric company, has been from day one and you know, over the years watching the announcements, the tsunami of announcements, just all the innovation that's come out from AWS over the years has been staggering to say the least. Everyone always jokes about, oh my God, 5,000 new announcements, over 200 services you're managing and you're marketing them. It's pretty crazy right now. And Adam, as he comes on, as I called them, the solutions CEO on my piece I wrote on Friday, we're in an era where solutions, the products are enabling more solutions. Unpack the messaging around this cuz this is really big moment for aws. >>Absolutely. Well, I'll say first of all that we are a customer focused company that happens to be really good at innovating incredible products and services for our customers. So today the, the energy in the room and what Adam talked about, I think is focused on a few great things for customers that are really important for transformation. So we talked a lot about best price performance for workloads and we talked about extreme workloads, but if you think about the work that we've been doing to innovate on the silicon side, we're really talking about with Graviton all your workloads and getting really great price performance for all of them. You know, we came out with graviton three 25% faster than graviton two, also 60% more energy efficient. We talked about something that is emerging that I think is gonna be really big, which is simulation and really the ability to model these complex worlds and all the little interactions, which I think, you know, in the future as we have more complex environments like 3D simulation is gonna be a bigger part of every, every business's >>Business. You know, just as an aside, we were talking on the analyst segment that speeds and feeds are back and the old days and the data center days was like, we don't wanna talk about speeds and feeds about solutions and you know, the outcomes when you get the cloud, it was like, okay, get the workloads over there, but people want faster and lower cost performance workloads gotta be running at at high performance. And, and there's a real discussion around those. Let's unpack security data performance. What, what does that mean for customers? Because again, I get the workloads run fast. That's great. What else is behind the curtain, so to speak from a customer standpoint? >>Absolutely. Well I think if you're gonna move all your workloads to the cloud, you know, security is a really big area that's important. It's important to every one of our enterprise companies customers. Actually it's important to all of our customers and we've been working, you know, since the beginning of AWS to really create and build the most secure global infrastructure. And you know, as our customers have moved mission critical workloads, we've built out a lot more capabilities and now we have a whole portfolio of security services. And what we announced today is kind of game changing. The service called Security Lake, which brings together, you know, an ecosystem of security data in a format that's open. So you can share data between all of these sources and it's gonna give folks the opportunity to really be able to analyze data, find threats faster, and just kind of know their security posture. And I think, you know, as we talked about today, you don't wanna think about the cloud as unfathomable, the unfathomable, you really need to know that security. And I think that like a lot of things we discussed, security is a data opportunity, right? And I think we, we had a section on on data, but really if you look at the keynote across security, across solutions, across the purpose built things we made, it's all, it all comes down to data and it's really the, the transformational element that our customers >>Are. I mean the data secured is very integral part good call out there. And I, I wanna just double down on that real quick because I remember in 2014 I interviewed Steven Schmidt when he was the CSOs and back then in 2014, if you remember the conversation was this, the clouds not secure, gotta be on premises. Now in today's keynote, Adam says, and he laid out the whole global security footprint. There's a lot going on that Amazon has now become more secure than on-prem. He actually made that statement. So, and then plus you got thousands of security partners, third party partners, you got the open cyber security framework which you guys co-found with all the other, so you got securities not as a team sport, this is what they, they said yes, yes. What does that mean for customers? Because now this is a big deal. >>Well I think for customers, I mean it means nothing but goodness, right? But all of these thousands of security partners have really innovated and created solutions that our customers are using. But they all have different types of data in different silos. And to really get a full picture bringing all that data together is really important. And it's not easy today. You know, log data from different sources, data from detection services and really what customers want is an easier way to get it all together. Which is why we have the open OCS F and really analyze using the tools of their choice. And whether that's AWS tools for analytics or it's tools from our partners, customers need to be able to make that choice so that they can feel like their applications and their workloads are the most secure on aws. >>You know, I've been very impressed with guard duty and I've been following Merit Bear's blogs on online. She's in the security team, she's amazing. Shout out to her. She's been pushing guard duty for a long time now there's big news around guard duty. So you got EKS protection, you know, at Coan this was the biggest cloud native issue, the runtime of Kubernetes and inside the container and outside the container detection of threats, right? As a real software supply chain concern. How are you guys marketing that? This is a huge announcement. EKS protection I know is very nuanced but it's pretty big deal. >>It is a big deal. It is a big deal. And guard duty has been kind of like a quiet service that maybe you don't hear a lot about, but has been really, really popular with our customers. Adam mentioned that 85% of, you know, our top 2000 customers are using guard duty today. And it was a big moment. We launched EKS protection, you know, a little bit earlier and the customer uptake on that has been really incredible. And it is because you can protect your Kubernetes cluster, which is really important because so many customers are, you know, part of their migration to the cloud is containers. Yeah. And so we're pretty excited that now we can answer that question of what's going on inside the container. And so you have both, yeah, right. You know that your Kubernetes pluses are good and you know what's going on inside the container and it's just more threats that you can detect and protect >>Yourself from. You know, as an aside, I'm sure you're watching this, but you know, we go to a lot of events, you know, the C I C D pipeline as developers are getting higher velocity coding, it has moved in because of DevOps on the cloud into the C I C D pipeline. So you're seeing that developer takes some of those IT roles in the coding workflow, hence the, the shift left and or container security, which you guys now, now and are driving towards. But the security and the data teams are emerging as a very key element inside the organizational structure. When I sat down with Adam, one of the things he was very adamant about in my conversation was not just digital transformation, business transformation, structural organizational moves are making where it's not a department anymore, it is the company, a technology is the company when you transform. Absolutely. So digital is the process, business is the outcome. This is a really huge message. What's your reaction to that? What's, what can you share extra cuz that's, this is a big part of the thing. He hit it right outta the gate on the front end of the keynote. >>Absolutely. Absolutely. I mean I think, you know, companies have been migrating to the cloud for a while, but I think that this time that we're going through has really accelerated that migration And as part of that, you know, digital transformation has become real for a lot of companies. And it is true what Adam said there is technology transformation involved, there's data transformation involved, but it, it is transforming businesses. And I think if you look at some of the things that Adam talked about, you know, aws, supply chain, security Lake, aws clean rooms, and Omic, aws, omic, you know, those are all examples of data and the ability to work with data transforming different lines of business within a company, transforming horizontal processes like contact centers and like supply chain and also, you know, going into vertical specific solutions. So what it means is that as technology becomes more pervasive, as data becomes more pervasive, businesses are transforming and that means that a lot more people are going to use the cloud and interact with the cloud and they might not want to or be able to kind of use our building blocks. And so what's really exciting that what we're able to do is make cloud more accessible to lines of business folks to analysts, to security folks. So >>It's, yeah, and that's, and that's why I was calling my this this new trend I see as Amazon Classic, my words, not your words, I call the, hey there was classic cloud and then you got the next gen clown, the new next generation. And I was talking with Adrian Cockcroft, former aws, so he's now retired, he's gonna come on later today. He and I were talking, he use this thing of you got a bag of Legos aka primitives or a toy that's been assembled for you glued together, ones out of the box, but they're not mutually exclusive. You can build a durable application and foundation with the building blocks more durable. You can manage it, refine it, but you got the solution that breaks. You don't have as much flexibility but you gotta replace it. That's okay too. So like this is now kind of a new portfolio approach to the cloud. It's very interesting and I think, I think, I think that's what I took away from the keynote is that you can have both. >>Yes, absolutely. You can do both. I mean, we're gonna go full throttle on releasing innovations and pushing the envelope on compute and storage and databases and our core services because they matter. And having, you know, the choice to choose from a wide range of options. I mean that's what, that's what customers need. You know, if you're gonna run hpc, you're gonna run machine learning and you're gonna run your SAP applications or your Windows applications, you need choice of what you know, specific type of instance and compute capabilities. You need to get the price performance. It's, it's definitely not a one size fits all. It's a 600 instance type. Size fits all maybe. >>Exactly. And you got a lot of instance and we'll get to that in a second. Yeah, I love the themes. I love this keynote themes you had like at first space, but I get the whole data, then you look at it, you can look at it differently. Really good metaphor, the ocean one I love with the security because he mentioned you can have the confidence to explore go deep snorkeling versus scuba and knowing how much oxygen you have. I mean, so really cool metaphor made me think very provocative. So again, this is kind of why people go to AWS because you now have these, these abilities to do things differently, depend on the context of what products you're working with. Yes. Explain why that was the core theme. Was there any rationale behind that? Was it just how you guys saw it? I mean that was pretty clever. >>Well, I think that, you know, we're, we're talking about environments and I think in this world, you know, there's uncertainty in a lot of places and we really feel like all of us need to be prepared for different types of environments. And so we wanted to explore what that could look like. And I think, you know, we're fascinated by space and the vastness and it is very much like the world of data. I don't know about you, but I actually scuba dive. So I love the depths of the ocean. I loved working on that part. There's extremes, extreme workloads like hpc, extreme workloads like machine learning with the growing models and there's an imagination, which is also one of my favorite areas to explore. >>Yeah. And you use the Antarctica one for about the whole environment and extreme conditions. That's good in the performance. And I love that piece of it. And I want to get into the, some of the things I love the speeds and fee. I think the, the big innovation with the silicon we've been covering as, you know, like a blanket. The, he's got the GRAVITON three 25% faster than GRAVITON two, the C seven GN network intense workloads. This is kind of a big deal. I mean this is one of those things where it might not get picked up in the major press, but the network use cases are significant. Nira has been successful. Share your thoughts on these kinds of innovations because they look kind of small, but they're not, they're >>Big, they're not small for sure, especially at the scale that our customers are, are, are running their applications. Like every little optimization that you can get really makes a huge difference. And I think it's exciting. I mean you hit on, you kind of hit on it when we've been working on silicon for a while now we know that, you know, if we're gonna keep pushing the element, the envelope in these areas, we had to, we had to go down to the silicon. And I think that Nitro has really been what's kind of been a breakthrough for us. You know, reinventing that virtualization layer, offloading security and storage and networking to special purpose chips. And I think that it's not just in the area of network optimization, right? You saw training optimized instances and inference optimized instances and HPC optimized instances. So yeah, we are kind of looking at all the extremes of, of what customers want to do. >>I know you can't talk about the future, but I can almost connect the dots as you're talking. It's like, hmm, specialized instances, specialized chips, maybe programmability of workload, smart intelligence, generative AI, weaving in there. A lot of kind of cool things I can see around the corner around generative AI automation. Hey, go to this instance with that go here. This is kind of what I see kind of coming around the corner. >>And we have some of that with our instance optimizers, our cost optimizer products where, you know, we wanna help customers find the best instance for their workload, get the best utilization they possibly can, you know, cut costs, but still have the great performance. So I don't, I don't know about your future, John, it sounds great, but we have, you know, we're taking steps in that direction today. >>Still look in this code that's gonna be on this code. Okay. Any, okay, I wanna give you one final question. Well, well two questions. One was a comment Adam made, I'd love to get your reaction if you want to tighten your bell, come to the cloud. I thought that was a very interesting nuance. A lot of economic pressure. Cloud is an opportunity to get agile, time to value faster. We had Zs carve cube analyst who's with us earlier said, the more you spend on the cloud, the more you save. That was his line, which I thought was very smart. Spending more doesn't mean you're gonna lose money, means you can save money too. So a lot of cost optimization discussions. Absolutely. Hey, your belt come to the cloud. What does he mean by that? >>Well I think that in, in times where, you know, there's uncertainty and economic conditions, it is, it's really, you know, you sometimes wanna pull back kind of, you know, batten down the hatches. But the cloud really, and we saw this with C you know, if you, if you move to the cloud, not only can you cut costs, but you put yourself in this position where you can continue to innovate and you can be agile and you can be prepared for whatever environment you're in so that you know when things go back or you have a customer needs that and innovation that goes off like you, you can accelerate back up really, really quickly. And I think we talked about Airbnb, that example of how, you know, in, in that really tough time of covid when travel industry wasn't happening so much, you know, they were able to scale back and save money. And then at the same time when, you know, Airbnb's kind of once again travel came back, they were in a position to really, really quickly change with the, the customer needs. >>You know, Lee, it's always great talking with you. You got a lot of energy, you're so smart and we both love products and you're leading the product marketing. We have an Instagram challenge here on the cube. I'm gonna put you on the spot here. Oh my gosh. It's called Instagram. We called a bumper sticker section. We used to call it what's the bumper sticker for reinvent. But we kind of modernized that. If you were gonna do an Instagram reel right now, what would be the Instagram reel for reinvent Keynote day one. As we look for, we got Verner, we'll probably talk about productivity with developers. What's the Instagram reel for reinvent? >>Wow. That means I have to get short with it, right? I am, I'm not always, that's still wrong answer. Yeah, well I think, you know, this is really big day one, so it's excitement, it's, we're glad to be here. We have a lot coming for you. We're super excited. And if you think about it, it's price, performance, it's data, it's security and it's solutions for purpose-built use cases. >>Great job. Congratulations. I love the message. I love how you guys had the theme. I thought it was great. And it's great to see Amazon continue to innovate with, with the, with the, with the innovation on the product side. But as we get into transformation, starting to see these solutions and the ecosystem is thriving and looking forward to hearing the, the new partner, chief Aruba tomorrow. Absolutely. See what she's got a new plan apparently unveiling. So exciting. Everyone's pretty excited. Thanks for coming >>On. Great. Great. Thanks for having >>Me. All right. Leah, here in the cube. You are the cube, the leader in tech coverage. I'm John Fur, your host. More live coverage after the short break. We'll be right back here. Day two of the cube, day one of reinvent. Lot of great action. Three, four days of wall to wall coverage. We'll be right back.

>>Good morning fellow nerds and welcome back to AWS Reinvent. We are live from the show floor here in Las Vegas, Nevada. My name is Savannah Peterson, joined with my fabulous co-host John Furrier. Day two keynotes are rolling. >>Yeah. What do you thinking this? This is the day where everything comes, so the core gets popped off the bottle, all the announcements start flowing out tomorrow. You hear machine learning from swee lot more in depth around AI probably. And then developers with Verner Vos, the CTO who wrote the seminal paper in in early two thousands around web service that becames. So again, just another great year of next level cloud. Big discussion of data in the keynote bulk of the time was talking about data and business intelligence, business transformation easier. Is that what people want? They want the easy button and we're gonna talk a lot about that in this segment. I'm really looking forward to this interview. >>Easy button. We all want the >>Easy, we want the easy button. >>I love that you brought up champagne. It really feels like a champagne moment for the AWS community as a whole. Being here on the floor feels a bit like the before times. I don't want to jinx it. Our next guest, Scott Castle, from Si Sense. Thank you so much for joining us. How are you feeling? How's the show for you going so far? Oh, >>This is exciting. It's really great to see the changes that are coming in aws. It's great to see the, the excitement and the activity around how we can do so much more with data, with compute, with visualization, with reporting. It's fun. >>It is very fun. I just got a note. I think you have the coolest last name of anyone we've had on the show so far, castle. Oh, thank you. I'm here for it. I'm sure no one's ever said that before, but I'm so just in case our audience isn't familiar, tell us about >>Soy Sense is an embedded analytics platform. So we're used to take the queries and the analysis that you can power off of Aurora and Redshift and everything else and bring it to the end user in the applications they already know how to use. So it's all about embedding insights into tools. >>Embedded has been a, a real theme. Nobody wants to, it's I, I keep using the analogy of multiple tabs. Nobody wants to have to leave where they are. They want it all to come in there. Yep. Now this space is older than I think everyone at this table bis been around since 1958. Yep. How do you see Siente playing a role in the evolution there of we're in a different generation of analytics? >>Yeah, I mean, BI started, as you said, 58 with Peter Lu's paper that he wrote for IBM kind of get became popular in the late eighties and early nineties. And that was Gen one bi, that was Cognos and Business Objects and Lotus 1 23 think like green and black screen days. And the way things worked back then is if you ran a business and you wanted to get insights about that business, you went to it with a big check in your hand and said, Hey, can I have a report? And they'd come back and here's a report. And it wasn't quite right. You'd go back and cycle, cycle, cycle and eventually you'd get something. And it wasn't great. It wasn't all that accurate, but it's what we had. And then that whole thing changed in about two, 2004 when self-service BI became a thing. And the whole idea was instead of going to it with a big check in your hand, how about you make your own charts? >>And that was totally transformative. Everybody started doing this and it was great. And it was all built on semantic modeling and having very fast databases and data warehouses. Here's the problem, the tools to get to those insights needed to serve both business users like you and me and also power users who could do a lot more complex analysis and transformation. And as the tools got more complicated, the barrier to entry for everyday users got higher and higher and higher to the point where now you look, look at Gartner and Forester and IDC this year. They're all reporting in the same statistic. Between 10 and 20% of knowledge workers have learned business intelligence and everybody else is just waiting in line for a data analyst or a BI analyst to get a report for them. And that's why the focus on embedded is suddenly showing up so strong because little startups have been putting analytics into their products. People are seeing, oh my, this doesn't have to be hard. It can be easy, it can be intuitive, it can be native. Well why don't I have that for my whole business? So suddenly there's a lot of focus on how do we embed analytics seamlessly? How do we embed the investments people make in machine learning in data science? How do we bring those back to the users who can actually operationalize that? Yeah. And that's what Tysons does. Yeah. >>Yeah. It's interesting. Savannah, you know, data processing used to be what the IT department used to be called back in the day data processing. Now data processing is what everyone wants to do. There's a ton of data we got, we saw the keynote this morning at Adam Lesky. There was almost a standing of vision, big applause for his announcement around ML powered forecasting with Quick Site Cube. My point is people want automation. They want to have this embedded semantic layer in where they are not having all the process of ETL or all the muck that goes on with aligning the data. All this like a lot of stuff that goes on. How do you make it easier? >>Well, to be honest, I, I would argue that they don't want that. I think they, they think they want that, cuz that feels easier. But what users actually want is they want the insight, right? When they are about to make a decision. If you have a, you have an ML powered forecast, Andy Sense has had that built in for years, now you have an ML powered forecast. You don't need it two weeks before or a week after in a report somewhere. You need it when you're about to decide do I hire more salespeople or do I put a hundred grand into a marketing program? It's putting that insight at the point of decision that's important. And you don't wanna be waiting to dig through a lot of infrastructure to find it. You just want it when you need it. What's >>The alternative from a time standpoint? So real time insight, which is what you're saying. Yep. What's the alternative? If they don't have that, what's >>The alternative? Is what we are currently seeing in the market. You hire a bunch of BI analysts and data analysts to do the work for you and you hire enough that your business users can ask questions and get answers in a timely fashion. And by the way, if you're paying attention, there's not enough data analysts in the whole world to do that. Good luck. I am >>Time to get it. I really empathize with when I, I used to work for a 3D printing startup and I can, I have just, I mean, I would call it PTSD flashbacks of standing behind our BI guy with my list of queries and things that I wanted to learn more about our e-commerce platform in our, in our marketplace and community. And it would take weeks and I mean this was only in 2012. We're not talking 1958 here. We're talking, we're talking, well, a decade in, in startup years is, is a hundred years in the rest of the world life. But I think it's really interesting. So talk to us a little bit about infused and composable analytics. Sure. And how does this relate to embedded? Yeah. >>So embedded analytics for a long time was I want to take a dashboard I built in a BI environment. I wanna lift it and shift it into some other application so it's close to the user and that is the right direction to go. But going back to that statistic about how, hey, 10 to 20% of users know how to do something with that dashboard. Well how do you reach the rest of users? Yeah. When you think about breaking that up and making it more personalized so that instead of getting a dashboard embedded in a tool, you get individual insights, you get data visualizations, you get controls, maybe it's not even actually a visualization at all. Maybe it's just a query result that influences the ordering of a list. So like if you're a csm, you have a list of accounts in your book of business, you wanna rank those by who's priorities the most likely to churn. >>Yeah. You get that. How do you get that most likely to churn? You get it from your BI system. So how, but then the question is, how do I insert that back into the application that CSM is using? So that's what we talk about when we talk about Infusion. And SI started the infusion term about two years ago and now it's being used everywhere. We see it in marketing from Click and Tableau and from Looker just recently did a whole launch on infusion. The idea is you break this up into very small digestible pieces. You put those pieces into user experiences where they're relevant and when you need them. And to do that, you need a set of APIs, SDKs, to program it. But you also need a lot of very solid building blocks so that you're not building this from scratch, you're, you're assembling it from big pieces. >>And so what we do aty sense is we've got machine learning built in. We have an LQ built in. We have a whole bunch of AI powered features, including a knowledge graph that helps users find what else they need to know. And we, we provide those to our customers as building blocks so that they can put those into their own products, make them look and feel native and get that experience. In fact, one of the things that was most interesting this last couple of couple of quarters is that we built a technology demo. We integrated SI sensee with Office 365 with Google apps for business with Slack and MS teams. We literally just threw an Nlq box into Excel and now users can go in and say, Hey, which of my sales people in the northwest region are on track to meet their quota? And they just get the table back in Excel. They can build charts of it and PowerPoint. And then when they go to their q do their QBR next week or week after that, they just hit refresh to get live data. It makes it so much more digestible. And that's the whole point of infusion. It's bigger than just, yeah. The iframe based embedding or the JavaScript embedding we used to talk about four or five years >>Ago. APIs are very key. You brought that up. That's gonna be more of the integration piece. How does embedable and composable work as more people start getting on board? It's kind of like a Yeah. A flywheel. Yes. What, how do you guys see that progression? Cause everyone's copying you. We see that, but this is a, this means it's standard. People want this. Yeah. What's next? What's the, what's that next flywheel benefit that you guys coming out with >>Composability, fundamentally, if you read the Gartner analysis, right, they, when they talk about composable, they're talking about building pre-built analytics pieces in different business units for, for different purposes. And being able to plug those together. Think of like containers and services that can, that can talk to each other. You have a composition platform that can pull it into a presentation layer. Well, the presentation layer is where I focus. And so the, so for us, composable means I'm gonna have formulas and queries and widgets and charts and everything else that my, that my end users are gonna wanna say almost minority report style. If I'm not dating myself with that, I can put this card here, I can put that chart here. I can set these filters here and I get my own personalized view. But based on all the investments my organization's made in data and governance and quality so that all that infrastructure is supporting me without me worrying much about it. >>Well that's productivity on the user side. Talk about the software angle development. Yeah. Is your low code, no code? Is there coding involved? APIs are certainly the connective tissue. What's the impact to Yeah, the >>Developer. Oh. So if you were working on a traditional legacy BI platform, it's virtually impossible because this is an architectural thing that you have to be able to do. Every single tool that can make a chart has an API to embed that chart somewhere. But that's not the point. You need the life cycle automation to create models, to modify models, to create new dashboards and charts and queries on the fly. And be able to manage the whole life cycle of that. So that in your composable application, when you say, well I want chart and I want it to go here and I want it to do this and I want it to be filtered this way you can interact with the underlying platform. And most importantly, when you want to use big pieces like, Hey, I wanna forecast revenue for the next six months. You don't want it popping down into Python and writing that yourself. >>You wanna be able to say, okay, here's my forecasting algorithm. Here are the inputs, here's the dimensions, and then go and just put it somewhere for me. And so that's what you get withy sense. And there aren't any other analytics platforms that were built to do that. We were built that way because of our architecture. We're an API first product. But more importantly, most of the legacy BI tools are legacy. They're coming from that desktop single user, self-service, BI environment. And it's a small use case for them to go embedding. And so composable is kind of out of reach without a complete rebuild. Right? But with SI senses, because our bread and butter has always been embedding, it's all architected to be API first. It's integrated for software developers with gi, but it also has all those low code and no code capabilities for business users to do the minority report style thing. And it's assemble endless components into a workable digital workspace application. >>Talk about the strategy with aws. You're here at the ecosystem, you're in the ecosystem, you're leading product and they have a strategy. We know their strategy, they have some stuff, but then the ecosystem goes faster and ends up making a better product in most of the cases. If you compare, I know they'll take me to school on that, but I, that's pretty much what we report on. Mongo's doing a great job. They have databases. So you kind of see this balance. How are you guys playing in the ecosystem? What's the, what's the feedback? What's it like? What's going on? >>AWS is actually really our best partner. And the reason why is because AWS has been clear for many, many years. They build componentry, they build services, they build infrastructure, they build Redshift, they build all these different things, but they need, they need vendors to pull it all together into something usable. And fundamentally, that's what Cient does. I mean, we didn't invent sequel, right? We didn't invent jackal or dle. These are not, these are underlying analytics technologies, but we're taking the bricks out of the briefcase. We're assembling it into something that users can actually deploy for their use cases. And so for us, AWS is perfect because they focus on the hard bits. The the underlying technologies we assemble those make them usable for customers. And we get the distribution. And of course AWS loves that. Cause it drives more compute and it drives more, more consumption. >>How much do they pay you to say that >>Keynote, >>That was a wonderful pitch. That's >>Absolutely, we always say, hey, they got a lot of, they got a lot of great goodness in the cloud, but they're not always the best at the solutions and that they're trying to bring out, and you guys are making these solutions for customers. Yeah. That resonates with what they got with Amazon. For >>Example, we, last year we did a, a technology demo with Comprehend where we put comprehend inside of a semantic model and we would compile it and then send it back to Redshift. And it takes comprehend, which is a very cool service, but you kind of gotta be a coder to use it. >>I've been hear a lot of hype about the semantic layer. What is, what is going on with that >>Semantec layer is what connects the actual data, the tables in your database with how they're connected and what they mean so that a user like you or me who's saying I wanna bar chart with revenue over time can just work with revenue and time. And the semantic layer translates between what we did and what the database knows >>About. So it speaks English and then they converts it to data language. It's >>Exactly >>Right. >>Yeah. It's facilitating the exchange of information. And, and I love this. So I like that you actually talked about it in the beginning, the knowledge map and helping people figure out what they might not know. Yeah. I, I am not a bi analyst by trade and I, I don't always know what's possible to know. Yeah. And I think it's really great that you're doing that education piece. I'm sure, especially working with AWS companies, depending on their scale, that's gotta be a big part of it. How much is the community play a role in your product development? >>It's huge because I'll tell you, one of the challenges in embedding is someone who sees an amazing experience in outreach or in seismic. And to say, I want that. And I want it to be exactly the way my product is built, but I don't wanna learn a lot. And so you, what you want do is you want to have a community of people who have already built things who can help lead the way. And our community, we launched a new version of the SES community in early 2022 and we've seen a 450% growth in the c in that community. And we've gone from an average of one response, >>450%. I just wanna put a little exclamation point on that. Yeah, yeah. That's awesome. We, >>We've tripled our organic activity. So now if you post this Tysons community, it used to be, you'd get one response maybe from us, maybe from from a customer. Now it's up to three. And it's continuing to trend up. So we're, it's >>Amazing how much people are willing to help each other. If you just get in the platform, >>Do it. It's great. I mean, business is so >>Competitive. I think it's time for the, it's time. I think it's time. Instagram challenge. The reels on John. So we have a new thing. We're gonna run by you. Okay. We just call it the bumper sticker for reinvent. Instead of calling it the Instagram reels. If we're gonna do an Instagram reel for 30 seconds, what would be your take on what's going on this year at Reinvent? What you guys are doing? What's the most important story that you would share with folks on Instagram? >>You know, I think it's really what, what's been interesting to me is the, the story with Redshift composable, sorry. No, composable, Redshift Serverless. Yeah. One of the things I've been >>Seeing, we know you're thinking about composable a lot. Yes. Right? It's, it's just, it's in there, it's in your mouth. Yeah. >>So the fact that Redshift Serverless is now kind becoming the defacto standard, it changes something for, for my customers. Cuz one of the challenges with Redshift that I've seen in, in production is if as people use it more, you gotta get more boxes. You have to manage that. The fact that serverless is now available, it's, it's the default means it now people are just seeing Redshift as a very fast, very responsive repository. And that plays right into the story I'm telling cuz I'm telling them it's not that hard to put some analysis on top of things. So for me it's, it's a, maybe it's a narrow Instagram reel, but it's an >>Important one. Yeah. And that makes it better for you because you get to embed that. Yeah. And you get access to better data. Faster data. Yeah. Higher quality, relevant, updated. >>Yep. Awesome. As it goes into that 80% of knowledge workers, they have a consumer great expectation of experience. They're expecting that five ms response time. They're not waiting 2, 3, 4, 5, 10 seconds. They're not trained on theola expectations. And so it's, it matters a lot. >>Final question for you. Five years out from now, if things progress the way they're going with more innovation around data, this front end being very usable, semantic layer kicks in, you got the Lambda and you got serverless kind of coming in, helping out along the way. What's the experience gonna look like for a user? What's it in your mind's eye? What's that user look like? What's their experience? >>I, I think it shifts almost every role in a business towards being a quantitative one. Talking about, Hey, this is what I saw. This is my hypothesis and this is what came out of it. So here's what we should do next. I, I'm really excited to see that sort of scientific method move into more functions in the business. Cuz for decades it's been the domain of a few people like me doing strategy, but now I'm seeing it in CSMs, in support people and sales engineers and line engineers. That's gonna be a big shift. Awesome. >>Thank >>You Scott. Thank you so much. This has been a fantastic session. We wish you the best at si sense. John, always pleasure to share the, the stage with you. Thank you to everybody who's attuning in, tell us your thoughts. We're always eager to hear what, what features have got you most excited. And as you know, we will be live here from Las Vegas at reinvent from the show floor 10 to six all week except for Friday. We'll give you Friday off with John Furrier. My name's Savannah Peterson. We're the cube, the the, the leader in high tech coverage.

>>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) >> Hello, welcome to theCUBE studios of Palo Alto California for RSA conference keynote coverage and conference coverage. I'm Sean for your host of theCUBE. We're breaking down the keynote of RSA day one kickoff. We had Mark Nunnikhoven, who's the distinguished cloud strategist at Lacework. Mark former cube alumni and expert and security has been on many times before, Mark great to see you. Thanks for coming on and helping me break down RSA conference 2021 virtual this year. Thanks for joining. >> Happy to be here. Thanks for having me John. >> You know, one of the things Mark about these security conferences is that interesting, RSA was the last conference we actually did interviews physically face to face and then the pandemic went down and it was a huge shutdown. So we're still virtual coming back to real life. So and they're virtual this year, so kind of a turn of events, but that was kind of the theme this year in the keynote. Changing the game on security, the script has been flipped, connectivity everywhere, security from day one being reinvented. Some people were holding onto the old way some people trying to get on there, on the future wave. Clearly you got the laggards and you've got the innovators all trying to kind of, you know, find their position. This has been obvious in this keynote. What's your take? >> Yeah and that was exactly it. They use that situation of being that last physical security conference, somewhat to their advantage to weave this theme of resiliency. And it's a message that we heard throughout the keynote. It's a message we're going to hear throughout the week. There's a number of talks that are tying back to this and it really hits at the core of what security aims to do. And I think aims is really the right word for it because we're not quite there yet. But it's about making sure that our technology is flexible that it expands and adapts to the situations because as we all know this year, you know basically upended everything we assumed about how our businesses were running, how our communities and society was running and we've all had to adapt. And that's what we saw at the keynote today was they acknowledged that and then woven into the message to drive that home for security providers. >> Yeah and to me one of the most notable backdrops to the entire thing was the fact that the RSA continues to operate from the sell out when Dell sold them for alright $2 billion to a consortium, private privately private equity company, Symphony Technology Group. So there they're operating now on their own. They're out in the wild, as you said, cybersecurity threats are ever increasing, the surface area has changed with cloud native. Basically RSA is a 3000 person startup basically now. So they've got secure ID, the old token business we all have anyone's had those IDs you know it's pretty solid, but now they've got to kind of put this event back together and mobile world Congress is right around the corner. They're going to try to actually have a physical event. So you have this pandemic problem of trying to get the word out and it's weird. It's kind of, I found it. It's hard to get your hands around all the news. >> It is. And it's, you know, we're definitely missing that element. You know, we've seen that throughout the year people have tried to adapt these events into a virtual format. We're missing those elements of those sorts of happenstance run-ins I know we've run into each other at a number of events just sort of in the hall, you get to catch up, but you know as part of those interactions, they're not just social but you also get a little more insight into the conference. Hey, you know, did you catch this great talk or are you going to go catch this thing later? And we're definitely missing that. And I don't think anyone's really nailed this virtual format yet. It's very difficult to wrap your head around like you said, I saw a tweet online from one InfoSec analyst today. It was pointed out, you know, there were 17 talks happening at the same time, which you know, in a physical thing you'd pick one and go to it in a virtual there's that temptation to kind of click across the channels. So even if you know what's going on it's hard to focus in these events. >> Yeah the one conference has got a really good I think virtual platform is Docker con, they have 48 panels, a lot of great stuff there. So that's one of more watching closest coming up on May 27. Check that one out. Let's get into this, let's get into the analysis. I really want to get your thoughts on this because you know, I thought the keynote was very upbeat. Clearly the realities are presenting it. Chuck Robbins, the CEO of Cisco there and you had a bunch of industry legends in there. So let's start with, let's start with what you thought of Rowan's keynote and then we'll jump into what Chuck Robbins was saying. >> Sure yeah. And I thought, Rohit, you know, at first I questioned cause he brought up and he said, I'm going to talk about tigers, airplanes and sewing machines. And you know, as a speaker myself, I said, okay, this is either really going to work out well or it's not going to work out at all. Unfortunately, you know, Rohit head is a professional he's a great speaker and it worked out. And so he tied these three examples. So it was tiger king for Netflix, at World War II, analyzing airplane damage and a great organization in India that pivoted from sewing into creating masks and other supplies for the pandemic. He wove those three examples through with resiliency and showed adaptation. And I thought it was really really well done first of all. But as a cloud guy, I was really excited as well that that first example was Netflix. And he was referencing a chaos monkey, which is a chaos engineering tool, which I don't think a lot of security people are exposed to. So we use it very often in cloud building where essentially this tool will purposely blow up things in your environment. So it will down services. It will cut your communications off because the idea is you need to figure out how to react to these things before they happen for real. And so getting keynote time for a tool like that a very modern cloud tool, I thought was absolutely fantastic. Even if that's, you know, not so well known or not a secret in the cloud world anymore, it's very commonly understood, but getting a security audience exposure to that was great. And so you know, Rohit is a pro and it was a good kickoff and yeah, very upbeat, a lot of high energy which was great for virtual keynote. Cause sometimes that's what's really missing is that energy. >> Yeah, we like Rohit too. He's got some, he's got charisma. He also has his hand on the pulse. I think the chaos monkey point you're making is as a great call out because it's been around the DevOps community. But what that really shows I think and puts an exclamation point around this industry right now is that DevSecOps is here and it's never going away and cloud native and certainly the pandemic has shown that cloud scale speed data and now distributed computing with the edge, 5G has been mentioned, as you said, this is a real deal. So this is DevOps. This is infrastructure as code and security is being reinvented in it. This is a killer theme and it's kind of a wake-up call. What's your reaction to that? what's your take? >> Yeah, it absolutely is a wake-up call and it actually blended really well into a Rohit second point, which was around using data. And I think, you know, having these messages put out to the, you know, what is the security conference for the year always, is really important because the rest of the business has moved forward and security teams have been a little hesitant there, we're a little behind the times compared to the rest of the business who are taking advantage of these cloud services, taking advantage of data being everywhere. So for security professionals to realize like hey there are tools that can make us better at our jobs and make us, you know, keep or help us keep pace with the business is absolutely critical because like you said, as much as you know I always cringe when I hear the term DevSecOps, it's important because security needs to be there. The reason I cringe is because I think security should be built into everything. But the challenge we have is that security teams are still a lot of us are still stuck in the past to sort of put our arms around something. And you know, if it's in that box, I'm good with it. And that just doesn't work in the cloud. We have better tools, we have better data. And that was really Rohit's key message was those tools and that data can help you be resilient, can help your organization be resilient and whether that's the situation like a pandemic or a major cyber attack, you need to be flexible. You need to be able to bounce back. >> You know, when we actually have infrastructure as code and no one ever talks about DevOps or DevSecOps you know, we've, it's over, it's in the right place, but I want to get your thoughts and seeing if you heard anything about automation because one of the things that you bring up about not liking the word DevSecOps is really around, having this new team formation, how people are organizing their developers and their operations teams. And it really is becoming programmable and that's kind of the word, but automation scales it. So that's been a big theme this year. What are you hearing? What did you hear on the keynote? Any signs of reality around automation, machine learning you mentioned data, did they dig into automation? >> Automation was on the periphery. So a lot of what they're talking about only works with automation. So, you know, the Netflix shout out for chaos monkey absolutely as an automated tool to take advantage of this data, you absolutely need to be automated but the keynote mainly focused on sort of the connectivity and the differences in how we view an organization over the last year versus moving forward. And I think that was actually a bit of a miss because as you rightfully point out, John, you need automation. The thing that baffles me as a builder, as a security guy, is that cyber criminals have been automated for years. That's how they scale. That's how they make their money. Yet we still primarily defend manually. And I don't know if you've ever tried to beat, you know the robots that are everything or really complicated video games. We don't tend to win well when we're fighting automation. So security absolutely needs to step up. The good news is looking at the agenda for the week, taking in some talks today, while it was a bit of a miss and the keynote, there is a good theme of automation throughout some of the deeper dive sessions. So it is a topic that people are aware of and moving forward. But again, I always want to see us move fast. >> Was there a reason Chuck Robbins headlines or is that simply because there are a big 800 pound gorilla in the networking space? You know, why Cisco? Are they relevant security? Is that signaling that networking is more important? As of 5G at the edge, but is Cisco the player? >> Obviously Cisco has a massive business and they are a huge player in the security industry but I think they're also representative of, you know and this was definitely Chuck's message. They were representative of this idea that security needs to be built in at every layer. So even though, you know I live on primarily the cloud technologies dealing with organizations that are built in the cloud, there is, you know, the reality of that we are all connected through a multitude of networks. And we've seen that with work from home which is a huge theme this year at the conference and the improvements in mobility with 5G and other connectivity areas like Edge and WiFi six. So having a big network player and security player like Cisco in the keynote I think is important just because their message was not just about inclusion and diversity for skills which was a theme we saw repeated in the keynote actually but it was about building security in from the start to the finish throughout. And I think that's a really important message. We can't just pick one place and say this is where we're going to build security. It needs to be built throughout all of our systems. >> If you were a Cicso listening today what was your take on that? Were you impressed? Were you blown away? Did you fall out of your chair or was it just right down the middle? >> I mean, you might fall out of your chair just cause you're sitting in it for so long taken in a virtual event. And I mean, I know that's the big downside of virtual is that your step counter is way down compared to where it should be for these conferences but there was nothing revolutionary in the opening parts of the keynote. It was just, you know sort of beating the drum that has been talked about, has been simmering in the background from sort of the more progressive side of security. So if you've been focusing on primarily traditional techniques and the on-premise world, then perhaps this was a little a bit of an eye-opener and something where you go, wow, there's, you know there's something else out here and we can move things forward. For people who are, you know, more cloud native or more into that automation space, that data space this is really just sort of a head nodding going, yeap, I agree with this. This makes sense. This is where we all should be at this point. But as we know, you know there's a very long tail insecurity and insecurity organizations. So to have that message, you know repeated from a large stage like the keynote I think was very important. >> Well you know, we're going to be, theCUBE will be onsite and virtual with our virtual platform for Amazon web services reinforced coming up in Houston. So that's going to be interesting to see and you compare contrast like an AWS reinforce which is kind of the I there I think they had the first conference two years ago so it's kind of a new conference. And then you got the old kind of RSA conference. The question I have for you, is it a just a position of almost two conferences, right? You got the cloud native AWS, which is really about, oh shared responsibility, et cetera, et cetera a lot more action happening there. And you got this conference here seem come the old school legacy players. So I want to get your thoughts on that. And I want to get your take on just just the cryptographers panel, because, you know, as I'm not saying this as a state-of-the-art that the old guys saying get off my lawn, you know crypto, we're the crypto purists, they were trashing NFTs which as you know, is all the rage. So I, and Ron rivers who wrote new co-create RSA public key technology, which is isn't everything these days. Is this a sign of just get off my lawn? Or is it a sign of the times trashing the NFTs? What's your take? >> Yeah, well, so let's tackle the NFTs then we'll do the contrast between the two conferences. But I thought the NFT, you know Ron and Addie both had really interesting ways of explaining what an NFT was, because that's most of the discussion around the NFT is exactly what are we buying or what are we investing in? And so I think it was Addie who said, you know it was basically you have a tulip then you could have a picture of a tulip and then you could have something explaining the picture of the tulip and that's what an NFT is. So I think, you know, but at the same time he recognized the value of potential for artists. So I think there was some definitely, you know get off my lawn, but also sort of the the cryptographer panels is always sort of very pragmatic, very evidence-based as shown today when they actually were talking about a paper by Schnorr who debates, whether RSA or if he has new math that he thinks can debunk RSA or at least break the algorithm. And so they had a very logical and intelligent discussion about that. But the cryptographers panel in contrast to the rest of the keynote, it's not about the hype. It's not about what's going on in the industry. It's really is truly a cryptographers panel talking about the math, talking about the fundamental underpinnings of our security things as a big nerd, I'm a huge fan but a lot of people watch that and just kind of go, okay now's a great time to grab a snack and maybe move those legs a little bit. But if you're interested in the more technical deeper dive side, it's definitely worth taking in. >> Super fascinating and I think, you know, it's funny, they said it's not even a picture of a tulip it's s pointer to a picture of a tulip. Which is technically it. >> That was it. >> It's interesting how, again, this is all fun. NFTs are, I mean, you can't help, but get an Amber by decentralization. And that, that wave is coming. It's very interesting how you got a decentralization wave coming, yet a lot of people want to hang on to the centralized view. Okay, this is an architectural conflict. Is there a balance in your mind as a techie, we look at security, certainly as the perimeter is gone that's not even debate anymore, but as we have much more of a distributed computing environment, is there a need for some sensuality and or is it going to be all decentralized in your opinion? >> Yeah that's actually a really interesting question. It's a great set up to connect both of these points of sort of the cryptographers panel and that contrast between newer conferences and RSA because the cryptographers panel brought up the fact that you can't have resilient systems unless you're going for a distributed systems, unless you're spreading things out because otherwise you're creating a central point of failure, even if it's at hyper-scale which is not resilient by definition. So that was a very interesting and very valid point. I think the reality is it's a combination of the two is that we want resilient systems that are distributed that scale up independently of other factors. You know, so if you're sitting in the cloud you're going multi-region or maybe even multicloud, you know you want this distributed area just for that as Verner from AWS calls it, you know, the reduced blast radius. So if something breaks, not everything does but then the challenge from a security and from an operational point of view, is you need that central visibility. And I think this is where automation, where machine learning and really viewing security as a data problem, comes into play. If you have the systems distributed but you can provide visibility centrally which is something we can achieve with modern cloud technologies, you kind of hit that sweet spot. You've got resilient underpinnings in your systems but you as a team can actually understand what's going on because that was a, yet another point from Carmela and from Ross on the cryptographers panel when it comes to AI and machine learning, we're at the point where we don't really understand a lot of what's going on in the algorithm we kind of understand the output and the input. So again, it tied back to that resiliency. So I think that key is distributed systems are great but you need that central visibility and you only get there through viewing things as a data problem, heavy automation and modern tooling. >> Great great insight, Mark. Great, great call out there. And great point tied in there. Let me ask you a question on your take on the keynote in the conference in general as first day gets going. Do you see this evolving from the classic enterprise kind of buyer supplier relationship to much more of a CSO driven or CXO driven? I need to start building about my teams. I got to start hiring developers, not so much in operation side. I mean, I see InfoSec is these industries are not going away. People are still buying tools and stacking up the tool shed but there's been a big trend towards platforms and shifting left from a developer CICB pipeline standpoint which speaks to scale on the cloud native side and that distributed side. So is this conference hitting that Mark, or you still think there are more hardware and service systems people? What's the makeup? What's the take? >> I think we're definitely starting to a shift. So a great example of that is the CSA. The Cloud Security Alliance always runs a day one or day zero summit at RSA. And this year it was a CSO executive summit. And whereas in previous years it's been practitioners. So that is a good sign I think, that's a positive sign to start to look at a long ignored area of security, which is how do we train the next generation of security professionals. We've always taken this traditional view. We've, you know, people go through the standard you get your CISSP, you hold onto it forever. You know, you do your time on the firewall, you go through the standard thing but I think we really need to adjust and look for people with that automation capability, with development, with better business skills and definitely better communication skills, because really as we integrate as we leave our sort of protected little cave of security, we need to be better business people and better team players. >> Well Mark, I really appreciate you coming on here. A cube alumni and a trusted resource and verified, trusted contributor. Thank you for coming on and sharing your thoughts on the RSA conference and breaking down the keynote analysis, the RSA conference. Thanks for coming on. >> Thank you. >> Well, what we got you here to take a minute to plug what you're doing at Lacework, what you're excited about. What's going on over there? >> Sure, I appreciate that. So I just joined Lacework, I'm a weekend. So I'm drinking from the fire hose of knowledge and what I've found so far, fantastic platform, fantastic teams. It's got me wrapped up and excited again because we're approaching, you know security from the data point of view. We're really, we're born in the cloud, built for the cloud and we're trying to help teams really gather context. And the thing that appealed to me about that was that it's not just targeting the security team. It's targeting builders, it's targeting the business, it's giving them that visibility into what's going on so that they can make informed decision. And for me, that's really what security is all about. >> Well, I appreciate you coming on. Thanks so much for sharing. >> Thank you. >> Okay CUBE coverage of RSA conference here with Lacework, I'm John Furrier. Thanks for watching. (upbeat music)

>>From around the globe. It's the cube with digital coverage of AWS reinvent 2020 sponsored by Intel, AWS, and our community partners. >>Hi, everyone. Welcome back to the cubes. Live coverage of AWS reinvent 2020 I'm John Farrow, your hosts. We've got the cube virtual. We're not there in person with remote this year, and we're excited to cover three weeks of wall-to-wall coverage. It's virtual events, so they don't over three weeks. We're in week three, day two. Um, and if you're watching this live on the platform tomorrow, Thursday at two o'clock Andy Jassy, we'll be live here on the cube with one-on-one with me to address all the hard questions, but here we're doing a day two of week three analysis with Jeremy Burton industry legend entrepreneur. Now the CEO of observe Inc, um, formerly the CMO of Dell technologies before that EMC has done a variety of ventures, seeing many ways of innovation, friend of the cube. Jeremy, thank you for coming on. >>Yeah, my pleasure. Great. Always great to be on the cube. >>Uh, great to have you on in particularly because, um, yesterday Verner, Vogel's talked a lot about observability and I noticed you got your observed shirt on, uh, observe Inc is your company's name, which is one of the many, uh, hot startups around observability, where you're making a business out of basically what he talked about yesterday. Um, and today's keynote. You had the extended cloud, uh, edge applications. You had bill Vass who leads up both edge and quantum. And then you had Rudy Valdez who, who talked a lot about, uh, evolution of cloud architecture. And of course you finally had, um, David Richardson, who is the VP of serverless. So you got edge. Quantum serverless architecture speaks to the sea change, Jeremy, and you have a good read on these big waves. When you look at serverless and then quantum, you look at, uh, edge, which is data, and you look at, um, all this coming together and on their architecture, Verner's keynote yesterday kind of makes sense. It's a systems architecture and this new observability trend, isn't like a point product. It's a broader concepts. You have a complete rethinking of distributed computing in the cloud. This is kinda what this Amazon feels like. What's your, what's your take? >>Yeah, it's a, it's a good observation. You know, the, the, the, the sort of punchline is, is that people are building applications differently. Um, so the, the, the, the, the technologies that people are using to build apps are different, um, the way in which they build applications is different. Um, the way folks released codes into production is different, and it stands to reason. Therefore, you're going to need a different approach, uh, when you want to troubleshoot these applications. So, uh, when you find, uh, you know, w w what is show when you want to find out what issues customers are having? So what, what we fell a couple of three years ago when we started to observe was that, um, uh, a new approach was required, what you're going to need to monitor your application. And, you know, 2020 is not the same as what you needed in 2015 or 2010. >>And we felt very strongly that this new wave was, was going to be called observability. It, it brings a tear to my eye to hear a Verner, talk about it, because as much as we observe, you know, believe that we can do big things in future. It's the big vendors today that can move markets. And so the Amazon and vulnerable particular talk about observability, I think it lends more credence to the topic. Um, we think that organizations should have observability teams. We think there should be a head of observability. And again, you know, Amazon and Dawson this, uh, I think means that there's a much stronger chance that that's going to happen. And they're going to start, start to shine a light on, I think, a topic that almost everybody needs to pay attention to as they build their next generation of applications. >>When you guys, I know you guys are launched and you have couple of campaign customers now and growing rapidly, um, well-funded, um, uh, get some great investors have found that the investors of snowflake also, um, invested in you guys. So they see this cloud trend LC snowflake when public, and I know you're on the board of snowflake as well. So, uh, you, you, you know, a little bit about what's going on with Amazon and the opportunity when you look at observability, okay, you're building a business around it. And again, you think about head of observability. That's not like a small thing when you make, put someone in charge of something. So why do you say that? I mean, what, I mean, you know, some would say, you know, Hey, it's a feature, not a company. I mean, this is two mindsets that are different. How do you address that? >>Yeah, the, the, the, the thing I'd say is, look, the number one job in America is, um, is a software engineer is writing code. The number two job is fixing it. And so, you know, th th the job think about that for a second. The job of fixing our applications is almost as big as the job of creating our applications. Uh, something has to change, right? I know the job of fixing cars is not as big as the auto industry. Why, because over time that industry has matured and there are better tools to diagnose cars. Uh, and so they're, they, they become easy to fix over time. We've, we've not made that leap with our applications. Um, the tools that the engineering team use to debug and troubleshoot their application are often still very different to what the dev ops team is using, um, which is very different to what maybe the SRE team is using. >>And so it's a huge problem in our industry. Um, really not being able to diagnose troubleshoot issues when they arise. It, it costs the industry, a fortune, it costs, you know, sort of in indirect wasted productivity of development teams, but it also costs in terms of customer experience. Um, I mean, you know, you and I both know is, look, if we're, if we're having a bad experience with maybe a new service that we're trying out online, w w we're probably going to go somewhere else. And so the there's never been like a more important time for people to invest in observing the entire environment, the entire customer experience, not only will you have happier customers, you might actually reduce the costs and improve the productivity in your engineering team as well. So I feel like the opportunity there is, is, is, is, is vast. Um, I also think longer term, um, it doesn't just apply to troubleshooting distributed applications. >>Um, I think the security systems are very related to the way we build software. Um, I mean, I think in, in, in the news in recent days, we've, we've come attuned, uh, uh, to, to software defects, um, or malware in software causing breaches and government agencies. Um, Hey, that, that could be anybody's software right there. Yeah. And so security has got a role to play in observability and the customer experience. It doesn't stop when they have a bad experience on the website. What if they complain? You know, what if a help desk ticket get, how do you track that? >>Yeah, I'm going to, I have a lot of questions for chassis tomorrow. One of them I'm going to ask him, and I want to get your thoughts on it. Cause you brought that up. And I think it's a key point, you know, building applications and supporting them and fixing them. It kind of reminds me of the old adage of, um, you know, you know, you gotta run it running the operation, 70% of the budget using to running it. If you look at what's happening and if you talk to customers and this is what I'm going to ask chassis tomorrow, Verner actually talked about, I on day two operations in his keynote. Yeah. I mean, this is Amazon they're, they're targeting builders. And so I talked to, um, a few other entrepreneurs, um, who were growing companies and some CIA CIOs and CEOs and the basic enterprises. >>They don't want to be building things like they, that's not their DNA. They don't build things like, that's not what they do. I mean, first of all, I love the builder mentality and with Amazon. Um, but they might be at a time where there might not be enough builders, Jeremy right out there. So you've got skill shortages and then ultimately are enterprises really builders. Yeah. They'll build something, but then they just run it it's. So, so at what point do they stop building or they build their own thing in the cloud and then they got to run it. So I think Amazon is going to shift quickly to day two operations, get bill, bill, bill run, run, run. >>Yeah. That's a great topic of conversation. I think what you sort of poking out is, is sort of the maturation of this digital age in the state that we're at. Um, I mean, if you, if you go back, you, you know, to, you know, 10, 10, 20 years, um, I mean, look at the mid nineties, um, there were a lot of people building custom applications, right? I mean, you know, it was innovation, it was all about building custom apps. And I think that golden era of application development whack that now, um, and, and customers in order to get competitive advantage, they are building their own applications. When you talk about digital transformation, what does that mean? Well, it means, you know, often a traditional company building a new digital experience for services that they've potentially offered in a physical way, uh, in the past. So make no mistake, P people are builders or they are writing code, they are becoming digital. >>I think what you'll find at some point as the industry's mature, some of these digital experience is become packaged. And so you can buy those off the shelf. And so there's less building required. But I think as we sit today, um, that there's probably more code been written in anger by more organizations that at any point in the last 30 years. And, and I think this is another reason why observability is so important, um, as you're building that code and as you're developing that customer experience, you want to be able to understand, um, where the issues are and, and, um, uh, like along the way, you don't want to wait until there's a, a big customer disaster on the day of you roll that, something to production before you start investigate. And you want to do that as you go. >>Yeah. And I think that's a kill. I do agree with you, by the way. I think the, there is a builder mentality, but it's probably right. But remember those days back in it, if you want to put our, our time machine hat on and go through the time machine is, you know, that was during the mainframe client server transition. And it was called spaghetti code. You know, it's like the monoliths were built and then it had to be supported and that became legacy. So I kind of see that happening today, where, um, people are moving to the cloud, they are building, but at some point you got to build your thing in the cloud. If I'm a company. And again, this isn't some dots trying to connect in real time. I got serverless, which is totally cool. I'm gonna have quantum has headroom for compute. >>I'm going to have, um, kind of a S a SOA service oriented architecture with web services, with observability. I'm gonna have all these modern apps great that, or run them. And I'm now I'm gonna shift them. Multiple clouds is so, you know, maybe the private cloud waves coming back, you're seeing telco clouds. You start to see these new tier. I won't say tier two clouds, but I mean, people will build their own cloud environment. There's no doubt as going to the cloud. And Steve Malania, Aviatrix kind of made this point yesterday in his analysis where he's like, he thinks private cloud will be back. I was just, it'll just be public cloud. People will build their own clouds and run them. >>Yeah. I feel well, what happens over time is, is the, the sort of line above which you would add value rises. So I kind of feel like, look, cloud is just going to the infrastructure. We can debate, you know, private cloud, public cloud. Is it a public cloud, or is it a private cloud served up by a public cloud provider? My view is, is look, all of that is, is, um, just going to be commodity, right? Um, it's going to be served up for an ever decreasing cost. And so then it's incumbent on organizations to innovate above that line. And, you know, 20 years ago, you know, we, we built our own data centers. Um, and now increasingly that, that seeming like a crazy idea. Um, and you know, now you can get almost all of your infrastructure from the cloud. The great thing is, I mean, look at observe. >>We have no people running data center operations, none, right? We have no people building a database, non, you know, we use snowflake in the cloud. It runs on AWS. We have, we have one dev ops, uh, engineer. And so all the people in the company right now, we're focused on adding value, helping people understand and analyze data, uh, above that line. And we just pay for a service level and, and look, uh, as time goes by, there's going to be more and more services and that line's going to rise. And so, you know, what, what I care about and what I think a lot of CEOs care about is are most of my resources innovating above that sort of value creation line, um, because that's what people are going to pay for in our business. And I think that's, what's going to represent you, you know, sort of value add for you, you know, organizations big and small. >>Yeah. That's a good point. I want to shift to the next topic and then we'll get into some observability questions I have for you and update on your company. Um, complexity has been a big theme. That's come out of all the conversations with analysts that have come on the cube, as you hear it with Amazon, a lot of undifferentiated, heavy lifting, being extracted away to your point about value layers and competing on value. Amazon continues to do that all great stuff, but some are saying, and we had said on the cube, yes, two days ago you put them complexity behind the curtain. It's still complexity, right? So, so complexity with the edge is highlighted. Uh, even though they got green, uh, I, um, edge core Greengrass, which has core thing, IOT core, a lot of cool things happening, but it's still not yet super easy. So complexity tends to slow things down became striction, what's your view on this? Because taming, the complexity seems to be a post COVID pandemic mandate for cloud journeys. What's your thing. >>Yeah, I totally agree. I think, I think in certainly you look organizations that have been in existence, but you know, 30, 40 years, or maybe even 10 years look at there's an amount of technical debt and complexity that you build up over time. Um, but even newer companies, um, the way that people are building modern distributed applications and in some respects is, is more complex than in days gone by, you know, microservices. Um, some of which maybe you own some of which maybe you don't, and what you've gotta be able to do is, is see the big picture, you know, w w when, when there's something in my code, but then when am I making a call out to maybe a third party microservice and, and that microservices bailing out on me, like people have got to see the big picture. And I think what hasn't been available as people have changed the architecture and their applications, there hasn't been an equivalent set of innovation or evolution in the tools that they use to manage that environment. And so you, you, you, you've got this sort of dichotomy of, uh, a better way for software developers to write code and deploy it into production microservices. But at the same time, you don't have good information and good tools to make sense of that complexity. >>That's great stuff. Jeremy Burton is here. He's the CEO of observe Inc cube, alumni, VIP cube alumni, by the way, has been on the cube every year, since the Q has been around 2010, when he took the new job as the CMO of EMC prior to being bought by Dell, Jeremy, you're a legend in the industry, certainly on as an executive and a marketer. And as an entrepreneur, um, I gotta ask you observe Inc, your company now, um, you're right in the middle of all this, you, you got a big bet going on. Could you share, in your opinion, your words, what is the big bet that you're making with observing? Uh, what are you betting on? How do you see the preferred future unfolding and where are you guys going to capture that value? >>Yes, I I'll big bat. Hey, uh, really is to take a new approach, um, in, in, in, in terms of enabling people to observe their systems, that the term observability actually goes back, uh, to a guy in control systems theory in the sixties. And then it's got quite a simple definition, which is, you know, being able to determine the, uh, I've been able to diagnose a system by the telemetry data that it emits. So let's look at the external outputs. And then based on that, can I determine the internal state of the application? And so from the get-go, we felt like observability was not about building another tool, right? We're not, you know, it's not about building another monitoring tool, a logging tool. Um, it's about analyzing data. And I, I was struck many years ago. Uh, I spent a bit of time with, with Andy McAfee, uh, from the sea sail lab at MIT. >>And he made a statement that I thought at the time was quite profound, which he said, look, everything's a matter of data. If you have enough data, you can solve any problem. And that stuck with me for a long time. And, um, you know, observe really what we do is we ingest vast quantities of telemetry data. We treat everything as events and we try and make sense of it. And the economics of the infrastructure now is such, that is you truly can ingest all the Alltel telemetry data and it's affordable, right? I mean, one of the wonderful things that Amazon has done is they've brought you, you know, very cheap, affordable storage. You can ingest all your data and keep it forever. Um, but, but now can you make sense of it? Well, you know, compute is pretty cheap these days and you've got amazing processing engines like snowflake. >>And so I was sense was that if we could allow folks to ingest all of this telemetry data process, that data and help people easily analyze that data, then they could find almost any problem that existed, uh, in their applications or in their infrastructure. So we really set out to create a data company, which I think is fundamentally different to, to really what everybody else is doing. And today we're troubleshooting distributed applications, but I think in future, we, my hope is that we can, we can help people analyze almost anything around their applications or infrastructure. >>And what's the use case problem statement that you're entering the market on? Is it just making sure microservices can be deployed as a Kubernetes? Is it managing containers? Is there a specific, um, customer adoption use case that you're focused on right now? >>Yeah, we've tried to target our ideal customer if you like has been the three or 4,000, uh, uh, SAS companies. Uh, we're, we're really focused on the U S right now, but three to 5,000 SAS companies, um, predominantly, uh, obviously running on AWS often, uh, Kubernetes infrastructure, but, you know, people who, uh, having a hard time, uh, understanding the complexity of the application that they've created, and they're having a hard time understanding, uh, the experience that their customers are having and tracking that back to root cause. So, you know, really helping those SAS companies troubleshoot their applications and having a better customer experience that's where the early customers are. And if we can do a good job in that area, I think we can, you know, over time, you know, start to take on some of the bigger companies and maybe some of the more established companies that are moving in this, this digital direction. >>Jeremy, thanks for sharing that. And I got one last set of questions for you around the industry, but before I get there, give a quick plug for observe. What are you guys looking to do hire, I mean, give a quick, uh, a PSA on what's going on with observed. >>Yeah, so we're, uh, the company is now what a rough and tough. About three years old, we got about 40 people. Uh we're well-funded by sort of Hill ventures. Uh, they were the original investors in, in snowflake. Um, and, um, yeah, I mean, we we've, we've well, more than doubled in size since the COVID lockdown began. We had about 15 people when that began. We've got almost 40 now. Um, and I would anticipate in the next year we're, we're probably going to double in size again, but, um, yeah, really the core focus in the company is, is understanding and analyzing vast quantities of data. And so anybody who is interested in, uh, that space look us up >>Mainly any areas, obviously engineering and the other areas okay. >>Near in all over. I mean, we, you know, w w w as you'll see, if you go to observing.com, we've got a pretty slick front end. Uh, we invested very early on in design and UX design. So we believe that you are, can be a differentiator. So we've got some amazing engineers on the front end. Uh, so going to can always do with the help there, but obviously, um, you know, there's a data processing platform here as well. Um, we, uh, we do run on top of snowflake. We, we do have a number of folks here who are very familiar, uh, you know, with the snowflake database and, and how to write efficiency equals. So, so front and backend. Um, we very soon, I think we'll be starting to expand the sales team. Um, we're really starting to get our initial set of customers and the feedback loop rule in rolling into engineering. And my hope would be, you know, probably early part of next year, we re we really start to nail the product market fit. Um, and we've got a huge release coming in the early part of next year where that the metrics and alerting functionality will be in the product. So, yeah, it's, it's sort of all systems go right now. >>Congratulations. Love to see the entrepreneurial journey. We'll keep an eye out for you and you're in a hot space. So we'll be riding, you'll be riding that wave, uh, question for you on the, um, just kind of the industry, uh, you're in the heart of Silicon Valley. Like I am honestly, I'm fellow Alto, you're up in the Hillsborough area. Um, I think you're in Hillsborough, right? That's where you, where you live. Um, San Francisco, the Valley, the pandemic pretty hard hit right now. People are sheltering in place, but still a lot of activity. Um, what are you hearing in, um, in, in the VC circles, startup circles, as everyone looks at coming out of the pandemic and you look at Amazon and you look at what snowflake has done. I mean, snowflake was built on top of Amazon competing against Redshift. Um, okay. They were hugely successful at doing that. So there's kind of this new playbook emerging. What are, what are people talking about? What's the scuttlebutt. >>Yeah. I mean, clearly TAC has done very well throughout what has been, you know, like just a terrible environment. Um, I think both kind of socially and economically, and I think what's going on in the stock market right now is probably not reflective of the, of the economic situation. And I think a lot of the indices are dominated by tech companies. So you, if you're not careful, you can get a little bit of a false read. Um, but look, what is undisputed is, is that the world is going to become more digital, more tech centric than, than less. Um, so I think there is a very, very bright future, you know, for tech, um, that there is certainly plenty of VC money, um, available. Um, you know, that is not really changed materially in the last year. Um, so if you have a good idea, if you're on one of these major trends, I think that there is a very good chance that you can get the company funded. >>Um, and you know, our, our expectation is that, you know, next year, obviously industries are going to return to work that have been dominant maybe for the last six, nine months. And so some parts of the economy should pick up again, but I would also tell you, I think certain, uh, sort of habits are not going to die. I mean, I think more things are going to be done online and we've gotten used to that way of working and, and you know, what, not, some of it is measurable. I don't know about cocktails over zoom, but working with customers, um, in some respects is easier because they're not traveling, we're not traveling. So we both have more time. Uh, it's sometimes easy to get meetings with people that you would never get. Now. Now, can you do an efficient sales process, education proof of concept? You know, those processes maybe have to grow up a little bit to be taken online, but I think the certain parts of the last, maybe six to nine months that we don't want to throw away and go back to the way we were doing it, because I think, you know, maybe this way of doing it is, is more efficient. >>What do you think about the, uh, entrepreneurial journeys out there? Obviously, um, Amazon we're here covering re-invent is really kind of, you know, building a massive compute engine. They've got higher level services and, you know, I've been speculating for years. I think snowflake is the first kind of big sign. That points to kind of what I said five years ago, which is there's going to be an opportunity for these other clouds as specialty clouds. I called them might be the wrong word, but snowflake basically built on top of Amazon, you know, most valuable company ever on wall street, uh, IPO on someone else's cloud. So is that a playbook? I mean, is that a move? I mean, this is kind of like a new thing. >>Yeah. I mean, that's, I mean, I, I feel like on databases, I've got a lot of history on management, Oracle almost 10 years. And you know, what snowflake does they did was they, they rearchitected the database explicitly for the cloud. I mean, you can run Oracle on the cloud, but, but it, but it doesn't do things the way that snowflake does it. Right. I mean, snowflake uses commodity storage. It uses S3 it's elastic. And so when you're not using it, you're not paying it. And these things sound very simple and very obvious now, which is I think what, what, what the genius of the founders, you know, Ben Warren and Tre, uh, work, and, and I think there will be other costs, you know, categories of infrastructure that will get rearchitected and reinvented for the cloud. And, you know, I've got equally big opportunities. Um, and so, yeah, I mean, I think the model, I believe firmly that the model is if you're a startup, you don't need to waste a lot of time, like reinventing the wheel on data center, infrastructure and databases, and a lot of the services that you would use to construct an application. >>You, you, you can start, you know, if, if the building that you're trying to build is like 12 floors, you can start at the eighth or ninth floor. Um, you know, I've, I've got like what three or 400 quality engineers at snowflake that are building our database. I don't, I don't need to do that. I can just piggyback on top of what they've done and add value. And, you know, the, the, the beautiful thing, you know, now, if you're a business out there thinking of, of, of, of becoming digital and reinventing yourself, or you're a startup just getting going, there's a lot of stuff you just don't have to build anymore. You just don't even have to think about it. >>Yeah. This is the new program of bull internet. It's internet, truly 2.0 or 3.0, whatever 4.0, a complete reset of online. And I think the pandemic, as you pointed out on many cube interviews and Andy Jassy send his keynote is on full display right now. And I think the smart money and smart entrepreneurs are going to see the opportunities. Okay. >>Yeah. It comes back to ideas and a great, I mean, I've always been a product person. Um, but look at great idea, a great product idea and a great product idea that, that capitalizes on the big trends in the industry. I think there's always going to be funding for those kinds of things. I don't know a lot about the consumer world I've always worked in, in B2B, but, um, you know, the kind of things that you're going to be able to do in future. I mean, think about it. If storage is essentially free and compute is essentially free. Just imagine what you could do, right. Jeremy, >>This is the new consumer. Get out. Let's understand that. Finally, B2B is the new consumer enterprise is hot. I was, again, it was riffing on this all week. All the things going on in enterprise is complex is now the new consumers now all connected. It's all one thing. The consumerization of it, the condition of computing has happened. It's going on. So you're a leader. Thank you for coming on. Great to see you as always, um, say hi to your family and stay safe. >>Yeah, you too. Thanks for the invite. Always, always a pleasure. >>Jeremy Burton breaking down the analysis of day two of week three of re-invent coverage. I'm John furry with the cube virtual. We're not in person anymore. Virtualization has allowed us to do more interviews over 110 interviews so far for re-invent and tomorrow, Thursday at two o'clock, Andy Jassy will spend 30 minutes with me here on the cube, looking back at re-invent the highs, the lows, and what's next for Amazon web services. I'm chef Aria. Thanks for watching.

>>From around the globe. It's the queue with digital coverage of AWS reinvent 2020 sponsored by Intel, AWS and our community partners. >>Welcome back to the cubes. Live coverage for ADFS reinvent 2020 I'm John Ford with the cube, your host. We are the cube virtual. We're not there in person this year. We're remote with the pandemic and we're here for the keynote analysis for Verner Vogels, and we've got some great analysts on and friends of the cube cube alumni is Rob Hirschfeld is the founder and CEO of Rakin a pioneer in the dev ops space, as well as early on on the bare metal, getting on the whole on-premise he's seen the vision and I can tell you, I've talked to him many times over the years. He's been on the same track. He's on the right wave frog. Great to have you on. I'm going to have to start Veatch, come on. Y'all come on as well, but great to see you. Thanks, pleasure to be here. Um, so the keynote with Verna was, you know, he's like takes you on a journey, you know, and, and virtual is actually a little bit different vibe, but I thought he did an exceptional job of stage layout and some of the virtual stage craft. Um, but what I really enjoyed the most was really this next level, thinking around systems thinking, right, which is my favorite topic, because, you know, we've been saying, going back 10 years, the cloud is just, here's a computer, right. It's operating system. And so, um, this is the big thing. This is, what's your reaction to the keynote. >>Wow. So I think you're right. This is one of the challenges with what Amazon has been building is it's, you know, it is a lock box, it's a service. So you don't, you don't get to see behind the scenes. You don't really get to know how they run these services. And what, what I see happening out of all of those pieces is they've really come back and said, we need to help people operate this platform. And, and that shouldn't be surprising to anyone. Right? Last couple of years, they've been rolling out service, service service, all these new things. This talk was really different for Verner's con normal ones, because he wasn't talking about whizzbang new technologies. Um, he was really talking about operations, um, you know, died in the wool. How do we make the system easier to use? How do we expose things? What assistance can we have in, in building applications? Uh, in some cases it felt like, uh, an application performance monitoring or management APM talk from five or even 10 years ago, um, canaries, um, you know, Canary deployments, chaos engineering, observability, uh, sort of bread and butter, operational things. >>We have Savi Joel, who's a influencer cloud computing Xtrordinair dev ops guru. Uh, we don't need dev ops guru from Amazon. We got Sarpy and prop here. So it'd be great to see you. Um, you guys had a watch party. Um, tell me what the reaction was, um, with, of the influencers in the cloud or ADI out there that were looking at Vernon's announcement, because it does attract a tech crowd. What was your take and what was the conversation like? >>Yeah, we kinda geeked out. Um, we had a watch party and we were commenting back and forth, like when we were watching it. I think that the general consensus is that the complexity of AWS stack itself is, is increasing. Right. And they have been focused on developers a lot, I think a lot longer than they needed to be a little bit. I think, uh, now they need to focus on the operations. Like we, we are, we all love dev ops talks and it's very fancy and it's very modern way of building software. But if you think deep down that, like once we developed software traditionally and, and also going forward, I think we need to have that separation. Once you develop something in production, it's, it's, it's operating right. Once you build a car, you're operating car, you're not building car all the time. Right? >>So same with the software. Once you build a system, it should have some stability where you're running it, operating it for, for a while, at least before you touch it or refactoring all that stuff. So I think like building and operating at the same time, it's very good for companies like Amazon, AWS, especially, uh, and, and Google and, and, and Facebook and all those folks who are building technology because they are purely high-tech companies, but not for GM Ford Chrysler or Kaiser Permanente, which is healthcare or a school district. The, they, they need, need to operate that stuff once it's built. So I think, uh, the operationalization of cloud, uh, well, I think take focus going forward a lot more than it has and absorbable Deanna, on a funny note, I said, observability is one of those things. I, now these days, like, like, you know, and the beauty pageants that every contestant say is like, whatever question you asked, is it Dora and the answer and say at the end world peace, right? >>And that's a world peace term, which is the absorbability. Like you can talk about all the tech stuff and all that stuff. And at the end you say observability and you'll be fine. So, um, what I'm making is like observability is, and was very important. And when I was talking today about like how we can enable the building of absorbability into this new paradigm, which is a microservices, like where you pass a service ID, uh, all across all the functions from beginning to the end. Right. And so, so you can trace stuff. So I think he was talking, uh, at that level. Yeah. >>Let me, let's take an observer Billy real quick. I have a couple of other points. I want to get your opinions on. He said, quote, this three, enabling major enabling technologies, powering observability metrics, logging and tracing here. We know that it would, that is of course, but he didn't take a position. If you look at all the startups out there that are sitting there, the next observability, there's at least six that I know of. I mean, that are saying, and then you got ones that are kind of come in. I think signal effects was one. I liked, like I got bought by Splunk and then is observability, um, a feature, um, or is it a company? I mean, this is something that kind of gets talked about, right? I mean, it's, I mean, is it really something you can build a business on or is it a white space? That's a feature that gets pulled in what'd you guys react to that? >>So this is a platform conversation and, and, you know, one of the things that we've been having conversations around recently is this idea of platforms. And, and, you know, I've been doing a lot of work on infrastructure as code and distributed infrastructure and how people want infrastructure to be more code, like, which is very much what, what Verna was, was saying, right? How do we bring development process capabilities into our infrastructure operations? Um, and these are platform challenges. W what you're asking about from, uh, observability is perspective is if I'm running my code in a platform, if I'm running my infrastructure as a platform, I actually need to understand what that platform is doing and how it's making actions. Um, but today we haven't really built the platforms to be very transparent to the users. And observability becomes this necessary component to fix all the platforms that we have, whether they're Kubernetes or AWS, or, you know, even going back to VMware or bare metal, if you can't see what's going on, then you're operating in the blind. And that is an increasingly big problem. As we get more and more sophisticated infrastructure, right? Amazon's outage was based on systems can being very connected together, and we keep connecting systems together. And so we have to be able to diagnose and troubleshoot when those connections break or for using containers or Lambdas. The code that's running is ephemeral. It's only around for short periods of time. And if something's going wrong in it, it's incredibly hard to fix it, >>You know? And, and also he, you know, he reiterated his whole notion of log everything, right? He kept on banging on the drum on that one, like log everything, which is actually a good practice. You got to log everything. Why wouldn't you, >>I mean, how you do, but they don't make it easy. Right? Amazon has not made it easy to cross, cross, and, uh, connect all the data across all of those platforms. Right? People think of Amazon as one thing, but you know, the people who are using it understand it's actually a collection of services. And some of those are not particularly that tied together. So figuring out something that's going on across, across all of your service bundles, and this isn't an Amazon problem, this is an industry challenge. Especially as we go towards microservices, I have to be able to figure out what happened, even if I used 10 services, >>Horizontal, scalability argument. Sorry. Do you want to get your thoughts on this? So the observability, uh, he also mentioned theory kind of couched it before he went into the talk about systems theory. I'm like, okay. Let's, I mean, I love systems, and I think that's going to be the big wake up call here for the next 10 years. That's a systems mindset. And I think, you know, um, Rob's right. It's a platform conversation. When you're thinking about an operating system or a system, it has consequences when things change, but he talked about controllability versus, uh, observability and kinda T that teed up the, well, you can control systems controls, or you can have observability, uh, what's he getting at in all of this? What's he trying to say, keep, you know, is it a cover story? Is it this, is it a feature? What was the, what was the burner getting at with all this? >>Uh, I, I, I believe they, they understand that, that, uh, that all these services are very sort of micro in nature from Amazon itself. Right. And then they are not tied together as Rob said earlier. And they, he addressed that. He, uh, he, uh, announced that service. I don't know the name of that right now of problem ahead that we will gather all the data from all the different places. And then you can take a look at all the data coming from different services at this at one place where you have the service ID passed on to all the servers services. You have to do that. It's a discipline as a software developer, you have to sort of adhere to even in traditional world, like, like, you know, like how you do logging and monitoring and tracing, um, it's, it's your creativity at play, right? >>So that's what software is like, if you can pass on, I was treating what they gave an example of Citrix, uh, when, when, when you are using like tons of applications with George stream to your desktop, through Citrix, they had app ID concept, right? So you can trace what you're using and all that stuff, and you can trace the usage and all that stuff, and they can, they can map that log to that application, to that user. So you need that. So I think he w he was talking about, I think that's what he's getting too. Like we have to, we have to sort of rethink how we write software in this new Microsoft, uh, sort of a paradigm, which I believe it, it's a beautiful thing. Uh, as long as we can manage it, because Microsoft is, are spread across like, um, small and a smaller piece of software is everywhere, right? So the state, how do we keep the state intact? How do we, um, sort of trace things? Uh, it becomes a huge problem if we don't do it right? So it it's, um, it's a little, this is some learning curve for most of the developers out there. So 60 dash 70% >>Rob was bringing this up, get into this whole crash. And what is it kind of breakdown? Because, you know, there's a point where you don't have the Nirvana of true horizontal scalability, where you might have microservices that need to traverse boundaries or systems, boundaries, where, or silos. So to Rob's point earlier, if you don't see it, you can't measure it or you can't get through it. How do you wire services across boundaries? Is that containers, is that, I mean, how does this all work? How do you guys see that working? I just see a train wreck there. >>It's, it's a really hard problem. And I don't think we should underestimate it because everything we toast talked about sounds great. If you're in a single AWS region, we're talking about distributed infrastructure, right? If you think about what we've been seeing, even more generally about, you know, edge sites, uh, colo on prem, you know, in cloud multi-region cloud, all these things are actually taking this one concept and you're like, Oh, I just want to store all the log data. Now, you're not going to store all your log data in one central location anymore. That in itself, as a distributed infrastructure problem, where I have to be able to troubleshoot what's going on, you know, and know that the logs are going to the right place and capture the data, that's really important. Um, and one of the innovations in this that I think is going to impact the industry over the next couple of years is the addition of more artificial intelligence and machine learning, into understanding operations patterns and practices. >>And I think that that's a really significant industry trend where Amazon has a distinct advantage because it's their systems and it's captive. They can analyze and collect a lot of data across very many customers and learn from those things and program systems that learn from those things. Um, and so the way you're going to keep up with this is not by logging more and more data, but by doing exactly what we're talking through, which was how do I analyze the patterns with machine learning so that I can get predictive analysis so that I can understand something that looks wrong and then put people on checking it before it goes wrong. >>All right, I gotta, I gotta bring up something controversial. I can't hold back any longer. Um, you know, Mark Zuckerberg said many, many years ago, all the old people, they can do startups, they're too old and you gotta be young and hungry. You gotta do that stuff. If we're talking systems theory, uh, automated meta reasoning, evolvable systems, resilience, distributed computing, isn't that us old guys that have actually have systems experience. I mean, if you're under the age of 30, you probably don't even know what a system is. Um, and, or co coded to the level of systems that we use to code. And I'm putting my quote old man kind of theory, only kidding, by the way on the 30. But my point is there is a generation of us that had done computer science in the, in the eighties and seventies, late seventies, maybe eighties and nineties, it's all it was, was systems. It was a systems world. Now, when you have a software world, the aperture is increasing in terms of software, are the younger generation of developers system thinkers, or have we lost that art, uh, or is it doesn't matter? What do you guys think? >>I, I think systems thinking comes with age. I mean, that's, that's sort of how I think, I mean, like I take the systems thinking a greater sort of, >>Um, world, like state as a system country, as a system and everything is a system, your body's a system family system, so it's the same way. And then what impacts the system when you operated internal things, which happened within the system and external, right. And we usually don't talk about the economics and geopolitics. There's a lot of the technology. Sometimes we do, like we have, I think we need to talk more about that, the data sovereignty and all that stuff. But, but even within the system, I think the younger people appreciate it less because they don't have the, they don't see, um, software taught like that in the universities. And, and, and, and by these micro micro universities now online trainings and stuff like sweaty, like, okay, you learn this thing and you're good at it saying, no, no, it's not like that. So you've got to understand the basics and how the systems operate. >>Uh, I'll give you an example. So like we were doing the, the, the client server in early nineties, and then gradually we moved more towards like having ESB enterprise services, bus where you pass a state, uh, from one object to another, and we can bring in the heterogeneous, uh, languages. This thing is written in Java. This is in.net. This is in Python. And then you can pass it through that. Uh, you're gonna make a state for, right. And that, that was contained environment. Like ESBs were contained environment. We were, I, I wrote software for ESPs myself at commerce one. And so like, we, what we need today is the ESP equallant in the cloud. We don't have that. >>Rob, is there a reverse ageism developers? I mean, if you're young, you might not have systems. What do you think? I, I don't agree with that. I actually think that the nature of the systems that we're programming forces people into more distributed infrastructure thinking the platforms we have today are much better than they were, you know, 20 years ago, 30 years ago, um, in the sense that I can do distributed infrastructure programming without thinking about it very much anymore, but you know, people know, they know how to use cloud. They know how to use a big platform. They know how to break things into microservices. I, I think that these are inherent skills that people need to think about that you're you're right. There is a challenge in that, you know, you get very used to the platform doing the work for you, and that you need to break through it, but that's an experiential thing, right? >>The more experienced developers are going to have to understand what the platforms do. Just like, you know, we used to have to understand how registers worked inside of a CPU, something I haven't worried about for a long, long time. So I, I don't think it's that big of a problem. Um, from, from that perspective, I do think that the thing that's really hard is collaboration. And so, you know, it's, it's hard people to people it's hard inside of a platform. It's hard when you're an Amazon size and you've been rolling out services all over the place and now have to figure out how to fit them all together. Um, and that to me is, is a design problem. And it's more about being patient and letting things, uh, mature. If anything might take away from this keynote is, you know, everybody asked Amazon to take a breath and work on usability and, and cross cross services synchronizations rather than, than adding more services into the mix. And that's, >>That's a good point. I mean, again, I bring up the conversation because it's kind of the elephant in the room and I make it being controversial to make a point there. So our view, because, you know, I interviewed Judy Estrin who helped found the internet with Vince Cerf. She's well-known for her contributions for the TCP IP protocol. Andy Besta Stein. Who's the, who's the Rembrandt of motherboards. But as Pat Gelsinger, CEO of VMware, I would say both said to me on the cube that without systems thinking, you don't understand consequences of when things change. And we start thinking about this microservices conversation, you start to hear a little bit of that pattern emerging, where those systems, uh, designs matter. And then you have, on the other hand, you have this modern application framework where serverless takes over. So, you know, Rob back to your infrastructure as code, it really isn't an either, or they're not mutually exclusive. You're going to have a set of nerds and geeks engineering systems to make them better and easier and scalable. And then you're going to have application developers that need to just make it work. So you start to see the formation of kind of the, I won't say swim lanes, but I mean, what do you guys think about that? Because you know, Judy and, um, Andy better sign up. They're kind of right. Uh, >>Th th the enemy here, and we're seeing this over and over again is complexity. And, and the challenge has been, and serverless is like, those people like, Oh, I don't have to worry about servers anymore because I'm dealing with serverless, which is not true. What you're doing is you're not worrying about infrastructure as much, but you, the complexity, especially in a serverless infrastructure where you're pulling, you know, events from all sorts of things, and you have one, one action, one piece of code, you know, triggering a whole bunch of other pieces of code in a decoupled way. We are, we are bringing so much complexity into these systems, um, that they're very hard to conceive of. Um, and AIML is not gonna not gonna address that. Um, I think one of the things that was wonderful about the setting, uh, in the sugar factory and at all of that, you know, sort of very mechanical viewpoint, you know, when you're actually connecting all things together, you can see it. A lot of what we've been building today is almost impossible to observe. And so the complexity price that we're paying in infrastructure is going up exponentially and we can't sustain infrastructures like that. We have to start leveling that in, right? >>Your point on the keynote, by the way, great call out on, on the, on the setting. I thought that was very clever. So what do you think about this? Because as enterprises go through this transformation, one of the big conversations is the solution architecture, the architecture of, um, how you lay all this out. It's complexity involved. Now you've got on premise system, you've got cloud, you've got edge, which you're hearing more and more local processing, disconnected systems, managing it at the edge with visualization. We're going to hear more about that, uh, with Dirk, when he comes on the queue, but you know, just in general as a practitioner out there, what, what's, what's your, what do you see people getting their arms around, around this, this keynote? What do they, what's your thoughts? >>Yeah, I, I think, uh, the, the pattern I see emerging is like, or in the whole industry, regardless, like if you put, when does your sign is that like, we will write less and less software in-house I believe that SAS will emerge. Uh, and it has to, I mean, that is the solution to kill the complexity. I believe, like we always talk about software all the time and we, we try to put this in the one band, like it's, everybody's dining, same kind of software, and they have, I'm going to complexity and they have the end years and all that stuff. That's not true. Right. If you are Facebook, you're writing totally different kind of software that needs to scale differently. You needs a lot of cash and all that stuff, right. Gash like this and cash. Well, I ain't both gases, but when you are a mid size enterprise out there in the middle, like fly over America, what, uh, my friend Wayne says, like, we need to think about those people too. >>Like, how do they drive software? What kind of software do they write? Like how many components they have in there? Like they have three tiers of four tiers. So I think they're a little more simpler software for internal use. We have to distinguish these applications. I always talk about this, like the systems of record systems of differentiation, the system of innovation. And I think cloud will do great. And the newer breed of applications, because you're doing a lot of, a lot of experimentation. You're doing a lot of DevOps. You have two pizza teams and all that stuff, which is good stuff we talk about, well, when you go to systems of record, you need stability. You need, you need some things which is operational. You don't want to touch it again, once it's in production. Right? And so the, in between that, that thing is, I think that's, that's where the complexity lies the systems are, which are in between those systems of record and system or innovation, which are very new Greenfield. That, that's what I think that's where we need to focus, uh, our, um, platform development, um, platform as a service development sort of, uh, dollars, if you will, as an industry, I think Amazon is doing that right. And, and Azura is doing that right to a certain extent too. I, I, I, I worry a little bit about, uh, uh, Google because they're more tilted towards the data science, uh, sort of side of things right now. >>Well, Microsoft has the most visibility into kind of the legacy world, but Rob, you're shaking your head there. Um, on his comment, >>You know, I, I, you know, I, I watched the complexity of all these systems and, and, you know, I'm not sure that sass suffocation of everything that we're doing is leading to less is pushing the complexity behind a curtain so that you, you, you can ignore the man behind the curtain. Um, but at the end of the day, you know what we're really driving towards. And I think Amazon is accelerating this. The cloud is accelerating. This is a new set of standard operating processes and procedures based on automation, based on API APIs, based on platforms, uh, that ultimately, I think people could own and could come back to how we want to operate it. When I look at what we w we were just shown with the keynote, you know, it was an, is things that application performance management and monitoring do. It's, it's not really Amazon specific stuff. There's no magic beans that Amazon is growing operational knowledge, you know, in Amazon, greenhouses that only they know how to consume. This is actually pretty block and tackle stuff. Yeah. And most people don't need to operate it at that type of scale to be successful. >>It's a great point. I mean, let's, let's pick up on that for the last couple of minutes we have left. Cause I think that's a great, great double-down because you're thinking about the mantra, Hey, everything is a service, you know, that's great for business model. You know, you hand it over to the techies. They go, wait a minute. What does that actually mean? It's harder. But when I talk to people out there and you hear people talking about everything is a service or sanctification, I do agree. I think you're putting complexity behind the curtain, but it's kind of the depends answer. So if you're going to have everything as a service, the common thesis is it has to have support automation everywhere. You got to automate things to make things sassiphy specified, which means you need five nines, like factory type environments. They're not true factories, but Rob, to your point, if you're going to make something a SAS, it better be Bulletproof. Because if you're, if you're automating something, it better be automated, right? You can measure things all you want, but if it's not automated, like a, like a, >>And you have no idea what's going on behind the curtains with some of these, these things, right. Especially, you know, I know our business and you know, our customers' businesses, they're, they're reliant on more and more services and you have no idea, you know, the persistence that service, if they're going to break an API, if they're going to change things, a lot of the stuff that Amazon is adding here defensively is because they're constantly changing the wheels on the bus. Um, and that is not bad operational practice. You should be resilient to that. You should have processes that are able to be constantly updated and CICB pipelines and, you know, continuous deployments, you shouldn't expect to, to, you know, fossilize your it environment in Amber, and then hope it doesn't have to change for 10 years. But at the same time, we'll work control your house. >>That's angle about better dev ops hypothetical, like a factory, almost metaphor. Do you care if the cars are being shipped down the assembly line and the output works and the output, if you have self-healing and you have these kinds of mechanisms, you know, you could have do care. The services are being terminated and stood up and reformed as long as the factory works. Right? So again, it's a complexity level of how much it, or you want to bite off and chew or make work. So to me, if it's automated, it's simple, did it work or not? And then the cost of work to be, what's your, what's your angle on this? Yeah. >>I believe if you believe in systems thinking, right. You have to believe in, um, um, the concept of, um, um, Oh gosh, I'm losing over minor. Um, abstraction. Right? So abstraction is your friend in software. Abstraction is your friend anyways, right? That's how we, humans pieces actually make a lot more progress than any other sort of living things here in this world. So that's why we are smart. We can abstract complexity behind the curtains, right? We, we can, we can keep improving, like from the, the, you know, wooden cart to the car, to the, to the plane, to the other, like, we, we, we have this, like when, when we see we are flying these airplanes, like 90% of the time they're on autopilot, like that's >>Hi, hiding my attractions is, is about evolution. Evolvable software term. He said, it's true. All right, guys, we have one minute left. Um, let's close this out real quick. Each of you give a closing statement on what you thought of the keynote and Verner's talk prop, we'll start with you. >>Uh, you know, as always, it's a perf keynote, uh, very different this year because it was so operationally focused and using the platform and, and helping people run their, their, off their applications and software better. And I think it's an interesting turn that we've been waiting for for Amazon, uh, to look at, you know, helping people use their own platform more. Um, so, uh, refreshing change and I think really powerful and well delivered. I really did like the setting >>Great shopping. And when we found, I found out today, that's Teresa Carlson is now running training and certification. So I'm expecting that to be highly awesomely accelerated a success there. Sorry, what's your take real quick on burners talk, walk away. Keynote thoughts. >>I, I, I think it was what I expected it to be like, he focused on the more like a software architecture kind of discussion. And he focused this time a little more on the ops side and the dev side, which I think they, they are pivoting a little bit, um, because they, they want to sell more AWS stuff to us, uh, to the existing enterprises. So I think, um, that was, um, good. Uh, I wish at the end, he said, not only like, go, go build, but also go build and operate. So can, you know, they all say, go build, build, build, but like, who's going to operate this stuff. Right. So I think, um, uh, I will see a little shift, I think, going forward, but we were talking earlier, uh, during or watch party that I think, uh, going forward, uh, AWS will open start open sourcing the commoditized version of their cloud, which have been commoditized by other vendors and gradually they will open source it so they can keep the hold onto the enterprises. I think that's what my take is. That's my prediction is >>Awesome and want, I'll make sure I'm at your watch party next time. Sorry. I missed it. Nobody's taking notes. Try and prepare. Sorry, Rob. Thanks for coming on and sharing awesome insight and expertise to experts in cloud and dev ops. I know them. And can firstly vouch for their awesomeness? Thanks for coming on. I think Verner can verify what I thought already was reporting Amazon everywhere. And if you connect the dots, this idea of reasoning, are we going to have smarter cloud? That's the next conversation? I'm John for your host of the cube here, trying to get smarter with Aus coverage. Thanks to Robin. Sarvi becoming on. Thanks for watching.

>>From around the globe. It's the cube with digital coverage of AWS reinvent 2020 sponsored by Intel, AWS, and our community partners. >>Hello, everyone. Welcome back to the cubes. Virtual coverage of AWS reinvent 2020 it's virtual this year because of the pandemic. We're not there in person and in real life, we're remote. I'm John for a year hosting the cube or the cube virtual. Um, as we continue to cover the three weeks of AWS reinvent and analyze the keynotes, we bring it in, uh, from our Cuban alumni, uh, network experts. And we have here great guest, Steve Malaney, CEO of Ava Trex, industry executive legend, former entrepreneur had done startups, um, been very, very successful with luminary and Silicon Valley, um, Palo Alto networks and the Sierra Cisco, I me, all the companies you've worked for. Um, Steve, great to see you again. >>Oh yeah. Hey awesome. Even if it's just virtual, John's great to be back in the cube. >>Okay, Steve, what's up? Am I muted? I got you. Okay. >>Gotcha. Oh, okay. I just said it's great. They're great to be back in the cube. >>I had to shut up my volume, got to love live cube TV. Um, I wanted to bring you on, because one, we've been talking with you guys and your company that you're now heading. You came off the board to take the helm of Ava tricks. You really saw the vision early on before the pandemic. We were actually, we did a hybrid event with you guys, a digital hybrid and your vision of multi-cloud and hybrid was pretty much in line with what Andy Jassy. And Amazon's now rolling out, except they're not calling it. Multi-cloud, they're just saying hybrid. But when you factor in the edge, the complexity there, you're really talking multiple environments. So I want to get your take, as you look at what Amazon has done in their announcements, they're continuing to power long. What's your analysis. What's your industry take? >>Yeah, I, I think it's, uh, you know, I think it's great. I think, you know, when we were a year ago, it was just a little over a year ago, we were at a multi-cloud conference and I think people kind of thought, wow, is multicloud something that the vendors are wanting to happen because they don't want to be killed by AWS. And you know, I mean, I saw this two years ago, I call it the Cambridge and explosion to cloud where every enterprise to we are now going to move to cloud. And they had been talking about it for six or seven years, but they didn't really mean it. And two years ago I saw they meant it and I knew what was going to happen. It was going to go multi-cloud they we're going to care about day two operations, visibility, control, security, all the things that enterprises care about. And I think, um, you know, what we've seen really over the last year is AWS and all the other cloud providers recognizing this, that the world is going multicloud. Um, and day two operations matter. You've gotta be able to operationalize this and enterprises. Can't just, it's not just about wiring it and building it up. You got do, you can operate it. And so that's, I think the thing that's really interesting is the maturity of the messaging. I would say from AWS to recognize, um, where enterprises are in their journey. >>You know, Steve, I want to just reflect on something. When I was 19 years old in my first job, uh, in New York, it was on a prime mini computer, my first exposure to the enterprise office and then went and worked for IBM and HP and others. I've been in the, around the enterprise. Let me just go back 10 years in Silicon Valley, you could literally count on one or two hands. The number of enterprise experts out there that you knew of that were out circulating that weren't retired. Um, because it went through this kind of commodity stage of outsource everything kind of down to the bone, you know, just keeping the lights on there. Wasn't really a lot of innovation in the enterprise. Now it's the hottest thing in the world. And you, and you look at what's happening with cloud. They're redefining the enterprise in Andy Jassy said to me, and I'm going to interview him, uh, later this week. And you know, he said, we're done with eyes and pads. We checked that's anything. I say anyone, but he's kind of implying that we did. I, as in pass, we're targeting global it. >>Yeah. Well, you know, >>Now enterprise is super hot and you know, it's, it's a whole nother ball game to restructuring on G >>Yeah, I mean, so I, uh, the AWS is marketing slogan, Mark. My words I'll bet you a hundred bucks within the next year is going to change. They are not going to say go build anymore. Right? Because that's what they're going to say. Go consume because no enterprise wants to build and Oh, by the way, here's the other thing that they're now also figuring out. Cause I know Andy Jassy analysis, there's a skills shortage of cloud, so they don't have the skills at the aptitude, but there's also a people shortage. It's not just the skills, it's the amount of people. They don't have the ability to go deploy this. And they're going to, you're going to need solutions like ABA tricks, abstract the way a lot of the complexities of the underlying clouds and deliver this architecture for people to be able to actually deploy. >>Where is the skill gaps in your opinion, where do you see them? >>You know, I was just talking to a customer yesterday and he said most of my, most of my team are CLI jockeys. And so for networking, that means the CLI the command line interface that a human manipulates to control the Cisco router. That's the old operational model. The model of this, these days are Terraform. You're going to infrastructure is code everything. You need scriptures. You need, you need developers that are going to be driving your infrastructure. And, and, but I can't, I can't fire all these people that I've had in my enterprise for the last 30 years. I got to bring them along. I got to bring them along and the tools and the platforms to be able to go, to go do that. >>Andy's argument and Amazon's position is we eliminate the undifferentiated heavy lifting and we have all this training and content to bring everyone along. Okay. By that. >>Well, I mean, here's, here's the thing that I think AWS and all the, all the cloud providers are figuring out is the enterprise is a different beast. You know, when you go to a company as AWS and say, Hey, you can get it as long as it's any color you want, as long as it's black. And so guess what, I'm a service. And the beautiful thing is you don't need to know anything about how we do anything and just trust me, it's all going to work that does not go over well with an enterprise because they say, I'm the guy that needs to know I will get fired. If this infrastructure goes down, you know, you saw us East one go down two weeks ago, Google had a outage to two days ago or whatever it was, shit happens. I don't know if I can say that on the cube. >>We're not going to actually see regulated at this point, but who's going to know. >>Um, and you know what? I've got to have that visibility in controls and enterprise, and I need the granular controls and the visibility to troubleshoot and the security controls and the performance controls that I used to have on prem, because I'm a regulated enterprise. I need that visibility and control. And the cloud providers just say, look, I deliver a service and I deliver it to everybody. And it's the same service. And you don't need to know that does not fly with the >>Well, certainly you're seeing more regulated industries. It used to be just public sector. I just talked with Teresa Carlson. She now took over all the industries. So FinTech is regulated. Energy is regulated. Telecom's regulated. The only thing that's not regulated is a VC and startup sectors, right? So there's a >>Well, and, and, and every, every good CIO of an enterprise knows nothing good comes from your, from your infrastructure that gets outsourced. We tried that it doesn't work. Now, maybe in 20 years, I can outsource my infrastructure if I'm the CIO of a major enterprise corporation. But right now I am not outsourcing that I have to have control. Now, am I going to leverage services and basic infrastructure from the cloud providers? Absolutely. I'm not going to build it on my own data centers. That world is over, but what I'm going to maintain is the visibility and control. >>Yeah. And that's what we heard from Verner. Vogel's around observability systems, thinking control versus observability, um, evolvable systems, things like reasoning, um, you know, these are, these are innovations, right? So, so let's get back to that builders thing, because you mentioned that earlier, I think there might be an opportunity. And I think this is where I think Jassy will either look brilliant or it might not pan out. So go big or go home moment. Can Amazon create a market for companies to say, instead of bringing along everybody, I'm going to bring along some people and hire more builders because there's rewards as spoils to be had for those builders. At this point in time, given the pandemic, it's kind of put everything on full display in terms of what to do. What's your thoughts on that? >>I think, I think outside in meaning I, I look at the customer and I, and I sit at the same side of the table as a customer. I think, what did they want? And every enterprise customer right now is building out their PRI it's just like in 1992, when they built out their private infrastructures, global infrastructure, and they did it with on-prem and data centers. I bought my stories, my compute, my networking, my MPLS, and I built my infrastructure. And it was my infrastructure. They're doing the same thing. It's just, they're architecting on top of cloud and they're doing it in a multi-cloud world because they're not going to be locked in to just one cloud. And they're going to have some applications that run better on GCP. Some have better in AWS and some on Oracle, and all of our customers are doing this. And what they want though, is a common infrastructure. That's their architecture and their infrastructure, not an AWS architecture and a Google architecture and an Azure architecture. What architecture, abstracted away above the clouds. That's my architecture. And it's common for my global network that that's what enterprises want to do. And I think each of the individual clouds are going to have to understand that they are a piece of the puzzle. They are not the puzzle. And I think you're going to have to come to that realization. >>I appreciate your expertise and insight into the commentary real quick, last 30 seconds, give a quick plug for Ava tricks. What are you guys doing? What's new cause the quick update. >>I mean, it's, it's, it's crazy just since, uh, I've been the CEO for two years and you know, the, the logos of large enterprise that we're getting right now. My, my Cambrian explosion that I saw two years ago is real, um, more executing on that strategy. It's a, who's who of logos right now. We've got 450 customers now we're, uh, exploding and more importantly, enterprises are now getting that deployment phase. They have, they're done with the architecture phase of, Hey, let me check this whole thing out in cloud. And now they're pushing the button and they're, they're accelerating, which my guess is it's not a coincidence that AWS is now talking about operations. And what Aviatrix does is, is, is, does gives that visibility and control cloud networking, but in a very cloud native way with Terraform simplicity, agility, because agility is part of mission critical infrastructure. Now can't be like it was in 1994 with a Cisco infrastructure where it said, what year do you want your, your, your infrastructure, Mr. Customer? >>Great. And the biggest thing people should pay attention to this year, uh, for around the enterprise dynamics with cloud and scale what's what should people be watching >>In your opinion? Just the continued movement of big enterprises, uh, all into cloud. The center of gravity is now into cloud and, uh, they're going to be completely running away from everything on prem. >>All right. Steven Landy, CEO of VBA tricks, a proven success entrepreneur CEO, back in the two years of the helm, the VBA tricks. Great to see you. I wish we were in person. One of our last events was your altitude event. It's on YouTube. If anyone was interested in watching, we had a great time. Steve, thank you so much for your candid commentary. Yeah. Thanks, John. Okay. I'm Jennifer with the cube. You're watching the cube virtual here on the cube. Thanks for watching..

>>From around the globe. It's the cube with digital coverage of AWS reinvent 2020, sponsored by Intel and AWS. >>Welcome back to the queue. It's virtual coverage of Avis reinvent 2020 I'm John furry, your host. Um, this is a cute virtual we're here. Not in, in remote. We're not in person this year, so we're doing the remote interviews. And then this segment is going to build on the quantum conversation we had last year, Richard moles, general manager of Amazon bracket and aid was quantum computing and Fernando Brandao head of quantum algorithms at AWS and Brent professor of theoretical physics at Caltech. Fernando, thanks for coming on, Richard. Thanks for joining us. >>You're welcome to be here. >>So, Fernando, first of all, love your title, quantum algorithms. That's the coolest title I've heard so far and you're pretty smart because you're a theoretical professor of physics at Caltech. So, um, which I'd never be able to get into, but I wish I could get into there someday, but, uh, thanks for coming on. Um, quantum has been quite the rage and you know, there's a lot of people talking about it. Um, it's not ready for prime time. Some say it's moving faster than others, but where are we on quantum right now? What are, what are you, what are you seeing Fernanda where the quantum, where are peg us in the evolution of, of, uh, where we are? >>Um, yeah, what quantum, uh, it's an emerging and rapidly developing fields. Uh, but we are see where are you on, uh, both in terms of, uh, hardware development and in terms of identifying the most impactful use cases of one company. Uh, so, so it's, it's, it's early days for everyone and, and we have like, uh, different players and different technologies that are being sport. And I think it's, it's, it's early, but it's exciting time to be doing quantum computing. And, uh, and it's very interesting to see the interest in industry growing and, and customers. Uh, for example, Casa from AWS, uh, being, uh, being willing to take part in this journey with us in developmental technology. >>Awesome. Richard, last year we talked to bill Vass about this and he was, you know, he set expectations really well, I thought, but it was pretty much in classic Amazonian way. You know, it makes the announcement a lot of progress then makes me give us the update on your end. You guys now are shipping brackets available. What's the update on your end and Verner mentioned in his keynote this week >> as well. Yeah, it was a, it was great until I was really looking at your interview with bill. It was, uh, that was when we launched the launch the service a year ago, almost exactly a year ago this week. And we've come a long way. So as you mentioned, we've, uh, we've, uh, we've gone to general availability with the service now that that happened in August. So now a customer can kind of look into the, uh, to the bracket console and, uh, installed programming concept computers. You know, there's, uh, there's tremendous excitement obviously, as, as you mentioned, and Fernando mentioned, you know, quantum computers, uh, we think >>Have the potential to solve problems that are currently, uh, uh, unsolvable. Um, the goal of bracket is to fundamentally give customers the ability to, uh, to go test, uh, some of those notions to explore the technology and to just start planning for the future. You know, our goal was always to try and solve some of the problems that customers have had for, you know, gee, a decade or so now, you know, they tell us from a variety of different industries, whether it's drug discovery or financial services, whether it's energy or there's chemical engineering, machine learning, you know, th the potential for quantum computer impacts may industries could potentially be disruptive to those industries. And, uh, it's, it's essential that customers can can plan for the future, you know, build their own internal resources, become experts, hire the right staff, figure out where it might impact their business and, uh, and potentially disrupt. >>So, uh, you know, in the past they're finding it hard to, to get involved. You know, these machines are very different, different technologies building in different ways of different characteristics. Uh, the tooling is very disparate, very fragmented. Historically, it's hard for companies to get access to the machines. These tend to be, you know, owned by startups or in, you know, physics labs or universities, very difficult to get access to these things, very different commercial models. Um, and, uh, as you, as you suggested, a lot of interests, a lot of hype, a lot of claims in the industry, customers want to cut through all that. They want to understand what's real, uh, what they can do today, uh, how they can experiment and, uh, and get started. So, you know, we see bracket as a catalyst for innovation. We want to bring together end-users, um, consultants, uh, software developers, um, providers that want to host services on top of bracket, try and get the industry, you know, rubbing along them. You spoke to lots of Amazonians. I'm sure you've heard the phrase innovation flywheel, plenty of times. Um, we see the same approach that we've used successfully in IOT and robotics and machine learning and apply that same approach to content, machine learning software, to quantum computing, and to learn, to bring it together. And, uh, if we get the tooling right, and we make it easy, um, then we don't see any reason why we can't, uh, you know, rapidly try and move this industry forward. And >>It was fun areas where there's a lot of, you know, intellectual computer science, um, technology science involved in super exciting. And Amazon's supposed to some of that undifferentiated heavy. >>That's what I am, you know, it's like, >>There's a Maslow hierarchy of needs in the tech industry. You know, people say, Oh, why five people freak out when there's no wifi? You know, you can't get enough compute. Right. So, you know, um, compute is one of those things with machine learning is seeing the benefits and quantum there's so much benefits there. Um, and you guys made some announcements at, at re-invent, uh, around BRACA. Can you share just quickly share some of those updates, Richard? >>Sure. I mean, it's the way we innovate at AWS. You know, we, we start simple and we, and we build up features. We listen to customers and we learn as we go along, we try and move as quickly as possible. So since going public in, uh, in, in August, we've actually had a string of releases, uh, pretty consistent, um, delivering new features. So we try to tie not the integration with the platform. Customers have told us really very early on that they, they don't just want to play with the technology. They want to figure out how to, how to envisage a production quantum computing service, how it might look, you know, in the context of a broad cloud platform with AWS. So we've, uh, we launched some integration with, uh, other AWS capabilities around security, managing limits, quotas, tagging resources, that type of thing, things that are familiar to, uh, to, to, to current AWS users. >>Uh, we launched some new hardware. Uh, all of our partners D-Wave launched some, uh, uh, you know, a 5,000 cubit machine, uh, just in September. Uh, so we made that available on bracket the same day that they launched that hardware, which was very cool. Um, you know, we've made it, uh, we've, we've made it easier for researchers. We've been, you know, impressed how many academics and researchers have used the service, not just large corporations. Um, they want to have really deep access to these machines. They want to program these things at a low level. So we launched some features, uh, to enable them to do their research, but reinvent, we were really focused on two things, um, simulators and making it much easier to use, uh, hybrid systems systems that, uh, incorporate classical compute, traditional digital computing with quantum machinery, um, in the vein that follow some of the liens that we've seen, uh, in machine learning. >>So, uh, simulators are important. They're a very important part of, uh, learning how to use concepts, computers. They're always available 24, seven they're super convenient to use. And of course they're critical in verifying the accuracy of the results that we get from quantum hardware. When we launched the service behind free simulator for customers to help debug their circuits and experiments quickly, um, but simulating large experiments and large systems is a real challenge on classical computers. You know, it, wasn't hard on classical. Uh, then you wouldn't need a quantum computer. That's the whole point. So running large simulations, you know, is expensive in terms of resources. It's complicated. Uh, we launched a pretty powerful simulator, uh, back in August, which we thought at the time was always powerful managed. Quantum stimulates circuit handled 34 cubits, and it reinvented last week, we launched a new simulator, which actually the first managed simulator to use tensor network technology. >>And it can run up to 50 cubits. So we think is, we think is probably the most powerful, uh, managed quantum simulator on the market today. And customers can flip easily between either using real quantum hardware or either of our, uh, stimulators just by changing a line of code. Um, the other thing we launched was the ability to run these hybrid systems. You know, quantum computers will get more, no don't get onto in a moment is, uh, today's computers are very imperfect, you know, lots of errors. Um, we working, obviously the industry towards fault-tolerant machines and Fernando can talk about some research papers that were published in that area, but right now the machines are far from perfect. And, uh, and the way that we can try to squeeze as much value out of these devices today is to run them in tandem with classical systems. >>We think of the notion of a self-learning quantum algorithm, where you use a classical optimization techniques, such as we see machine learning to tweak and tune the parameters of a quantum algorithm to try and iterate and converge on the best answer and try and overcome some of these issues surrounding errors. That's a lot of moving parts to orchestrate for customers, a lot of different systems, a lot of different programming techniques. And we wanted to make that much easier. We've been impressed with a, a, an open projects, been around for a couple of years, uh, called penny lane after the Beatles song. And, um, so we wanted to double down on that. We were getting a lot of positive feedback from customers about the penny lane talk it, so we decided to, uh, uh, make it a first class citizen on bracket, make it available as a native feature, uh, in our, uh, in our Jupiter notebooks and our tutorials learning examples, um, that open source project has very similar, um, guiding principles that we do, you know, it's open, it's cross platform, it's technology agnostic, and we thought he was a great fit to the service. >>So we, uh, we announced that and made it available to customers and, uh, and, and, uh, already getting great feedback. So, uh, you know, finishing the finishing the year strongly, I think, um, looking forward to 2021, you know, looking forward to some really cool technology it's on the horizon, uh, from a hardware point of view, making it easy to use, um, you know, and always, obviously trying to work back from customer problems. And so congratulations on the success. I'm sure it's not hard to hire people interested, at least finding qualified people it'd be different, but, you know, sign me up. I love quantum great people, Fernando real quick, understanding the relationship with Caltech unique to Amazon. Um, tell us how that fits into the, into this, >>Uh, right. John S no, as I was saying, it's it's early days, uh, for, for quantum computing, uh, and to make progress, uh, in abreast, uh, put together a team of experts, right. To work both on, on find new use cases of quantum computing and also, uh, building more powerful, uh, quantum hardware. Uh, so the AWS center for quantum computing is based at Caltech. Uh, and, and this comes from the belief of AWS that, uh, in quantum computing is key to, uh, to keep close, to stay close of like fresh ideas and to the latest scientific developments. Right. And Caltech is if you're near one computing. So what's the ideal place for doing that? Uh, so in the center, we, we put together researchers and engineers, uh, from computer science, physics, and other subjects, uh, from Amazon, but also from all the academic institutions, uh, of course some context, but we also have Stanford and university of Chicago, uh, among others. So we broke wrongs, uh, in the beauty for AWS and for quantum computer in the summer, uh, and under construction right now. Uh, but, uh, as we speak, John, the team is busy, uh, uh, you know, getting stuff in, in temporary lab space that we have at cottage. >>Awesome. Great. And real quick, I know we've got some time pressure here, but you published some new research, give a quick a plug for the new research. Tell us about that. >>Um, right. So, so, you know, as part of the effort or the integration for one company, uh, we are developing a new cubix, uh, which we choose a combination of acoustic and electric components. So this kind of hybrid Aquacel execute, it has the promise for a much smaller footprint, think about like a few microliters and much longer storage times, like up to settlements, uh, which, which is a big improvement over the scale of the arts sort of writing all export based cubits, but that's not the whole story, right? On six, if you have a good security should make good use of it. Uh, so what we did in this paper, they were just put out, uh, is, is a proposal for an architecture of how to build a scalable quantum computer using these cubits. So we found from our analysis that we can get more than a 10 X overheads in the resources required from URI, a universal thought around quantum computer. >>Uh, so what are these resources? This is like a smaller number of physical cubits. Uh, this is a smaller footprint is, uh, fewer control lines in like a smaller approach and a consistent, right. And, and these are all like, uh, I think this is a solid contribution. Uh, no, it's a theoretical analysis, right? So, so the, uh, the experimental development has to come, but I think this is a solid contribution in the big challenge of scaling up this quantum systems. Uh, so, so, so John, as we speak like, uh, data blessed in the, for quantum computing is, uh, working on the experimental development of this, uh, a highly adequacy architecture, but we also keep exploring other promising ways of doing scalable quantum computers and eventually, uh, to bring a more powerful computer resources to AWS customers. >>It's kind of like machine learning and data science, the smartest people work on it. Then you democratize that. I can see where this is going. Um, Richard real quick, um, for people who want to get involved and participate or consume, what do they do? Give us the playbook real quick. Uh, so simple, just go to the AWS console and kind of log onto the, to the bracket, uh, bracket console, jump in, you know, uh, create, um, create a Jupiter notebook, pull down some of our sample, uh, applications run through the notebook and program a quantum computer. It's literally that simple. There's plenty of tutorials. It's easy to get started, you know, classic cloud style right now from commitment. Jump in, start simple, get going. We want you to go quantum. You can't go back, go quantum. You can't go back to regular computing. I think people will be running concert classical systems in parallel for quite some time. So yeah, this is the, this is definitely not a one way door. You know, you go explore quantum computing and see how it fits into, uh, >>You know, into the, into solving some of the problems that you wanted to solve in the future. But definitely this is not a replacement technology. This is a complimentary technology. >>It's great. It's a great innovation. It's kind of intoxicating technically to get, think about the benefits Fernando, Richard, thanks for coming on. It's really exciting. I'm looking forward to keeping up keeping track of the progress. Thanks for coming on the cube coverage of reinvent, quantum computing going the next level coexisting building on top of the shoulders of other giant technologies. This is where the computing wave is going. It's different. It's impacting people's lives. This is the cube coverage of re-invent. Thanks for watching.

la from Las Vegas it's the cube covering AWS reinvent 2019 brought to you by Amazon Web Services and in care along with its ecosystem partners hey welcome back everyone cubes live coverage of eight of us reinvent 2019 this is the cube seventh year covering Amazon reinvent it's their eighth year of the conference and want to just shout out to Intel for their sponsorship for these two amazing sets without their support we would be able to bring our mission of great content to you I'm John Force to many men we're here with the chief of AWS the chief executive officer Andy chassis tech athlete and himself three our keynotes welcome to the cube again great to see you great to be here thanks for having me guys congratulations on a great show a lot of great buzz thank you a lot of good stuff your keynote was phenomenal you get right into you giddy up right into as you say three hours 30 announcements you guys do a lot but what I liked the new addition in the last year and this year is the band house man yeah they're pretty good they hit the Queen note so that keeps it balanced so we're going to work on getting a band for the cube awesome so if I have to ask you what's your walk-up song what would it be there's so many choices depends what kind of mood I'm in but maybe times like these by the Foo Fighters these are unusual times right now Foo Fighters playing at the Amazon intersect show they are Gandy well congratulations on the intersect you got a lot going on intersect is the music festival I'll get that in a second but I think the big news for me is two things obviously we had a one-on-one exclusive interview and you laid out essentially what looks like was gonna be your keynote it was transformation key for the practice I'm glad to practice use me anytime yeah and I like to appreciate the comments on Jedi on the record that was great but I think the transformation story is a very real one but the NFL news you guys just announced to me was so much fun and relevant you had the Commissioner of NFL on stage with you talking about a strategic partnership that is as top-down aggressive goals you could get yeah I have Roger Goodell fly to a tech conference to sit with you and then bring his team talk about the deal well you know we've been partners with the NFL for a while with the next-gen stats are they using all their telecasts and one of the things I really like about Roger is that he's very curious and very interested in technology in the first couple times I spoke with him he asked me so many questions about ways the NFL might be able to use the cloud and digital transformation to transform their various experiences and he's always said if you have a creative idea or something you think that could change the world for us just call me is it or text me or email me and I'll call you back within 24 hours and so we've spent the better part of the last year talking about a lot of really interesting strategic ways that they can evolve their experience both for fans as well as their players and the player health and safe safety initiative it's so important in sports and particularly important with the NFL given the nature of the sport and they've always had a focus on it but what you can do with computer vision and machine learning algorithms and then building a digital athlete which is really like a digital twin of each athlete so you understand what does it look like when they're healthy what and compare that when it looks like they may not be healthy and be able to simulate all kinds of different combinations of player hits and angles and different plays so that you can try to predict injuries and predict the right equipment you need before there's a problem can be really transformational so it was super excited about it did you guys come up with the idea it was the collaboration between there's really a collaboration I mean they look they are very focused on player's safety and health and it's it's a big deal for their you know they have two main constituents that the players and fans and they care deeply about the players and it's a it's a hard problem in a sport like football but you watch it yeah I gotta say it does point out the use cases of what you guys are promoting heavily at the show here of the stage maker studio which is a big part of your keynote where they have all this data right and they're dated hoarders they've the hoard data but they're the manual process of going through the data it was a killer problem this is consistent with a lot of the enterprises that are out there they have more data than they even know so this seems to be a big part of the strategy how do you get the customers to actually a wake up to the fact that they got data and how do you tie that together I think in almost every company they know they have a lot of data and there are always pockets of people who want to do something with it but when you're gonna make these really big leaps forward these transformations so things like Volkswagen is doing with they're reinventing their factories in their manufacturing process or the NFL where they're gonna radically transform how they do players health and safety it starts top-down and if they if the senior leader isn't convicted about wanting to take that leap forward and trying something different and organizing the data differently and organizing the team differently and using machine learning and getting help from us and building algorithms and building some muscle inside the company it just doesn't happen because it's not in the normal machinery of what most companies do and so it all wait almost always starts top-down sometimes it can be the commissioner or the CEO sometimes it can be the CIO but it has to be senior level conviction or it does get off the ground and the business model impact has to be real for NFL they know concussions hurting their youth pipelining this is a huge issue for them is their business model they they lose even more players to lower extremity injuries and so just the notion of trying to be able to predict injuries and you know the impact it can have on rules the impact it can have on the equipment they use it's a huge game changer when they look at the next 10 to 20 years all right love geeking out on the NFL but no more do you know off camera a 10 man is here defeated season so everybody's a Patriots fan now it's fascinating to watch you and your three-hour keynote Vernor in his you know architectural discussion really showed how AWS is really extending its reach you know it's not just a place for a few years people have been talking about you know cloud as an operation operational model it's not a destination or a location but I felt that really was laid out is you talked about breadth and depth and Verna really talked about you know architectural differentiation people talk about cloud but there are very there are a lot of differences between the vision for where things are going help us understand and why I mean Amazon's vision is still a bit different from what other people talk about where this whole cloud expansion journey but put over what tagger label you want on it but you know the control plane and the technology that you're building and where you see that going well I think that we've talked about this a couple times we we have two macro types of customers we have those that really want to get at the load level building blocks and stitch them together creatively and however they see fit to create whatever is in there in their heads and then we have this second segment of customers who say look I'm willing to give up some of that flexibility in exchange for getting 80% of the way they're much faster in an abstraction that's different from those low level building blocks in both segments of builders we want to serve and serve well and so we built very significant offerings in both areas I think when you look at micro services you know some of it has to do with the fact that we have this very strongly held belief born out of several years at Amazon where you know the first seven or eight years of Amazon's consumer business we basically jumbled together all of the parts of our technology and moving really quickly and when we wanted to move quickly where you had to impact multiple internal development teams it was so long because it was this big ball this big monolithic piece and we got religion about that and trying to move faster in the consumer business and having to tease those pieces apart and it really was a lot of the impetus behind conceiving AWS where it was these low-level very flexible building blocks that don't try and make all the decisions for customers they get to make them themselves and some of the micro services that you saw Verner talking about just you know for instance what we what we did with nitro or even what we do with firecracker those are very much about us relentlessly working to continue to to tease apart the different components and even things that look like low-level building blocks over time you build more and more features and all of a sudden you realize they have a lot of things that are they were combined together that you wished weren't that slowed you down and so nitro was a completely reimagining of our hypervisor and virtualization layer to allow us both to let customers have better performance but also to let us move faster and have a better security story for our customers I got to ask you the question around transformation because I think it all points to that all the data points you got all the references goldman-sachs on stage at the keynote Cerner and the healthcare just an amazing example because I mean this demonstrating real value there there's no excuse I talked to someone who wouldn't be named last night and then around the area said the CIA has a cost bar like this cost up on a budget like this but the demand for mission based apps is going up exponentially so there's need for the cloud and so seeing more and more of that what is your top-down aggressive goals to fill that solution base because you're also very transformational thinker what is your what is your aggressive top-down goals for your organization because you're serving a market with trillions of dollars of span that's shifting that's on the table a lot of competition now sees it too they're gonna go after it but at the end of the day you have customers that have that demand for things apps yeah and not a lot of budget increase at the same time this is a huge dynamic what's your goals you know I think that at a high level are top-down aggressive goals so that we want every single customer who uses our platform to have an outstanding customer experience and we want that outstanding customer experience in part is that their operational performance and their security are outstanding but also that it allows them to build and it build projects and initiatives that change their customer experience and allow them to be a sustainable successful business over a long period of time and then we also really want to be the technology infrastructure platform under all the applications that people build and they were realistic we know that that you know the market segments we address with infrastructure software hardware and data center services globally are trillions of dollars in the long term it won't only be us but we have that goal of wanting to serve every application and that requires not just the security operational performance but also a lot of functionality a lot of capability we have by far the most amount of capability out there and yet I would tell you we have three to five years of items on our roadmap that customers want us to add and that's just what we know today well and any underneath the covers you've been going through some transformation when we talked a couple years ago about how serverless is impacting things I've heard that that's actually in many ways glue behind the two pizza teams to work between organizations talk about how the internal transformations are happening how that impacts your discussions with customers that are going through that transformation well I mean there's a lot of a lot of the technology we build comes from things that we're doing ourselves you know and that we're learning ourselves it's kind of how we started thinking about microservices serverless - we saw the need we know we would have we would build all these functions that when some kind of object came into an object store we would spin up compute all those tasks would take like three or four hundred milliseconds then we spin it back down and yet we'd have to keep a cluster up in multiple availability zones because we needed that fault tolerance and it was we just said this is wasteful and that's part of how we came up with lambda and that you know when we were thinking about lambda people understandably said well if we build lambda and we build the serverless event-driven computing a lot of people who are keeping clusters of instances aren't going to use them anymore it's going to lead to less absolute revenue for us but we we have learned this lesson over the last 20 years at Amazon which is if it's something it's good for customers you're much better off cannibalizing yourself and doing the right thing for customers and being part of shaping something and I think if you look at the history of Technology you always build things and people say well that's gonna cannibalize this and people are gonna spend less money what really ends up happening is they spend spend less money per unit of compute but it allows them to do so much more that the ultimately long-term end up being you know more significant customers I mean you are like beating the drum all the time customers what they say we implement the roadmap I got that you guys have that playbook down that's been really successful for you yeah two years ago you told me machine learning was really important to you because your customers told what's the next tranche of importance for customers what's on top of mine now as you look at this reinvent kind of coming to a close replays tonight you had conversations your your tech a fleet you're running around doing speeches talking to customers what's that next hill from from my fist machine learning today there's so much I mean that's not it's not a soup question you know I think we're still in this in the very early days of machine learning it's not like most companies have mastered yet even though they're using it much more than they did in the past but you know I think machine learning for sure I think the edge for sure I think that we're optimistic about quantum computing even though I think it'll be a few years before it's really broadly useful we're very enthusiastic about robotics I think the amount of functions are going to be done by these robotic applications are much more expansive than people realize it doesn't mean humans won't have jobs they're just going to work on things that are more value-added I thought we're believers in augmented and virtual reality we're big believers and what's going to happen with voice and I'm also I think sometimes people get bored you know I think you're even bored with machine learning maybe already but yet people get bored with the things you've heard about but I think just what we've done with the chips you know in terms of giving people 40% better price performance in the latest generation of x86 processors it's pretty unbelievable and the difference in what people are going to be able to do or just look at big data I mean big date we haven't gotten through big data where people have totally solved it the amount of data that companies want to store process and analyze is exponentially larger than it was a few years ago and it will I think exponentially increase again in the next few years you need different tools the service I think we're not we're not for with machine learning we're excited to get started because we have all this data from the video and you guys got sage maker yeah we call it a stairway to machine learning heaven we start with the data move up what now guys are very sophisticated with what you do with technology and machine learning and there's so much I mean we're just kind of again in this early innings and I think that it was soaked before sage maker was so hard for everyday developers and data scientists to build models but the combination of sage maker and what's happened with thousands of companies standardizing on it the last two years Plus now sage maker studio giant leap forward we hope to use the data to transform our experience with our audience and we're on Amazon Cloud I really appreciate that and appreciate your support if we're with Amazon and Instant get that machine learning going a little faster for us a big that'll be better if you have requests so any I'm you talked about that you've got the customers that are builders and the customers that need simplification traditionally when you get into the you know the heart of the majority of adoption of something you really need to simplify that environment but when I think about the successful enterprise of the future they need to be builders yeah so has the model flipped if you know I normally would said enterprise want to pay for solutions because they don't have the skill set but if they're gonna succeed in this new economy they need to go through that transformation that yeah so I mean are we in just a total new era when we look back will this be different than some of these previous waves it's a it's a really good question Stu and I I don't think there's a simple answer to it I think that a lot of enterprises in some ways I think wish that they could just skip the low level building blocks and and only operate at that higher level abstraction it's why people were so excited by things like sage maker or code guru or Kendra or contact lens these are all services that allow them to just send us data and then run it on our models and get back the answers but I think one of the big trends that we see with enterprises is that they are taking more and more of their development in-house and they are wanting to operate more and more like startups I think that they admire what companies like Airbnb and Pinterest and slack and and you know Robin Hood and a whole bunch of those companies stripe have done and so when you know I think you go through these phases and errors where there are waves of success at different companies and then others want to follow that success and and replicate and so we see more and more enterprises saying we need to take back a lot of that development in-house and as they do that and as they add more developers those developers in most cases like to deal with the building blocks and they have a lot of ideas on how they can create us to creatively stitch them together on that point I want to just quickly ask you on Amazon versus other clouds because you made a comment to me in our interview about how hard it is to provide a service that to other people and it's hard to have a service that you're using yourself and turn that around and the most quoted line in my story was the compression algorithm there's no compression outliving for experience which to me is the diseconomies of scale for taking shortcuts yeah and so I think this is a really interesting point just add some color comments or I think this is a fundamental difference between AWS and others because you guys have a trajectory over the years of serving at scale customers wherever they are whatever they want to do now you got micro services it's even more complex that's hard yeah how about that I think there are a few elements to that notion of there's no compression algorithm I think the first thing to know about AWS which is different is we just come from a different heritage in a different background we sweep ran a business for a long time that was our sole business that was a consumer retail business that was very low margin and so we had to operate a very large scale given how many people were using us but also we had to run infrastructure services deep in the stack compute storage and database in reliable scalable data centers at very low costs and margins and so when you look at our our business it actually today I mean it's it's a higher margin business in our retail business the lower margin business and software companies but at real scale it's a it's a high-volume relatively low margin business and the way that you have to operate to be successful with those businesses and the things you have to think about and that DNA come from the type of operators that we have to be in our consumer retail business and there's nobody else in our space that does that you know the way that we think about cost the way we think about innovation and the data center and and I also think the way that we operate services and how long we've been operating services of the company it's a very different mindset than operating package software then you look at when you think about some of the issues and very large scale cloud you can't learn some of those lessons until you get two different elbows of the curve and scale and so what I was telling you is it's really different to run your own platform for your own users where you get to tell them exactly how it's going to be done but that's nothing really the way the real world works I mean we have millions of external customers who use us from every imaginable country and location whenever they want without any warning for lots of different use cases and they have lots of design patterns and we don't get to tell them what to do and so operating a cloud like that at a scale that's several times larger the next few providers combined is a very different endeavor and a very different operating rigor well you got to keep raising the bar you guys do a great job really impress again another tsunami of announcements in fact you had to spill the beans early with quantum the day before the event tight schedule I gotta ask you about the music festival because I think there's a really cool innovation it's the inaugural intersex conference yeah it's not part of replay which is the concert tonight right it's a whole new thing big music act you're a big music buff your daughter's an artist why did you do this what's the purpose what's your goal yeah it's an experiment I think that what's happened is that reinvent has gotten so big with 65,000 people here that to do the party which we do every year it's like a thirty five forty thousand person concert now which means you have to have a location that has multiple stages and you know we thought about it last year when we were watching it and we said we're kind of throwing like a four hour music festival right now there's multiple stages and it's quite expensive to set up that set for our partying we said well maybe we don't have to spend all that money for four hours in the rip it apart because actually the rent to keep those locations for another two days is much smaller than the cost of actually building multiple stages and so we we would try it this year we're very passionate about music as a business and I think we are I think our customers feel like we throw in a pretty good music party the last few years and we thought we were trying at a larger scale as an experiment and if you look at the economics the headliners real quick the Foo Fighters are headlining on Saturday night Anderson Park and the free Nashville free Nationals Brandi Carlile Shawn Mullins Willie Porter it's a good set Friday night it's back in Kacey Musgraves so it's it's a really great set of about 30 artists and we're hopeful that if we can build a great experience that people want to attend that we can do it it's scale and it might be something that you know both pays for itself and maybe helps pay for reinvent to overtime and you know I think that we're also thinking about it as not just a music concert and festival the reason we named it intersect is that we want an intersection of music genres and people and ethnicities and age groups and art and Technology all there together and this will be the first year we try it it's an experiment and we're really excited about I'm gone congratulations all your success and I want to thank you we've been seven years here at reinvent we've been documenting the history two sets now once-dead upstairs so appreciate a cube is part of reinvent you know you guys really are a part of the event and we really appreciate your coming here and I know people appreciate the content you create as well and we just launched cube 365 on Amazon Marketplace built on AWS so thanks for letting us cool build on the platform appreciate it thanks for having me guys Jesse the CEO of AWS here inside the cube it's our seventh year covering and documenting they're just the thunderous innovation that Amazon is doing they're really doing amazing work building out the new technologies here in the cloud computing world I'm John Force too many men be right back with more after this short break [Music]

>>LA from Las Vegas. It's the cube covering AWS. Reinvent 20 nineteens brought to you by Amazon web services and they don't care along with its ecosystem partners. >>Hey, welcome back. Everyone is the cubes live covers in Las Vegas for AWS. Reinvent 2019 it's our seventh year covering Amazon reinvent. They've only had the conference for eight years. We've been documenting history. I'm John Farrow, stupid man. Dave Alante, John Walls, Jeff, Rick, they're all on the other step two sets sponsored by Intel. Want to thank their support without their generous support to our mission. We wouldn't be able to bring this great content. Our next guest to talk about the IOT edge jerk DDoSs column. Perfect. Welcome back. VP of IOT. Well the Greek names. Yeah, I'm half Greek, half German so I can expect, okay. Is smart. Good. So Derek, I gotta ask you, so IOT is hot. Explain quickly your role at AWS because you're not an I-Team specifically define your scope. So my scope is owning all or my team's sculpt is owning old software services and tools that deal with non it equipment. >>So when you go to AWS and look for IOT, all the service that you'll find, that's the scope of my teams and this it group which have all the it stuff and just feels like cars, manufacturing sensors, all of the axioms for the NFL, all that good stuff. So women, you're going to see Edelweiss so I go AWS, amazon.com and then you're fine either. means all of our compute, all of our databases, all of our storage and there's also all of our and Melanie and I and then there's an IOT section and there you find all of the goodness that we do for IOT. You know, it's exciting. Stu and I talking about all week here, the whole cloud native, you take the T out of cloud native, it's cloud naive. You've got the general commercial business and public sector barely getting their act together. They're transforming, they're doing it now. >>He's $1 trillion on a vouch. Trillions of dollars of of change coming. Good up business opportunity. But if they're having trouble transforming, you get this whole new world of industrial edge which requires computing cars manufactured. This is a hot area. So a lot of change happening. What is the most important story people should pay attention to in your area that that's notable for this collision of all this transformation? I think maybe the most notable story that we currently have is a corporation that they do with the VW, which is the largest a car manufacturer. And you were just lucky that via their CIO mountain Huffman being part of Verona for good's keynote, our CTO. So if you haven't seen that, just go and review the keynote of Verner and then as the larger part then he was talking about all of that, what he calls industrial 4.0, this digitization fourth revolution. And Martin did an awesome job explaining what are we doing together with them to build their industrial cloud. Yeah. >>Uh, well, one of the things we've been really watching is the, the extent that Amazon services are starting to push out. Uh, I've been super excited, really looking at some of the growth of there. Your team did a bunch of announcements ahead of the show including the one that caught my eye the most was the IOT green grass sport for Lambda and Docker. Maybe start there and walk us through some of the new pieces that in your org. Okay. >>Maybe for us to understand the offer three type of offerings for our customers. One is device software, which might sound strange that a cloud company actually gives you a software that it's not running on the cloud, but then you're talking about IOT. You need software running on your devices in order to be able to be controlled and communicate with the cloud and we have an offering in that area which is called IOT Greenglass, which is a software runtime that you can install on edge devices like gateways for example, and via announced junior additions to our IOT Greenglass. One is Docker supports, which was very important because up till now green were supporting machine learning at the edge and Lambda, which is our service offering, but many companies now more established enterprises said, you know what, I have legacy applications which I can package. Can I deploy them as well? >>Now you can deploy Docker containers, Lambda functions, and a melody edge all with one goal with green glass at the edge. So that was one of the announcements we did for our device >> software. They're, I want to get your thoughts on an area that we're reporting on and doing a lot of investigation, collecting a lot of data, talking to a lot of people and that's around the industrial IOT or IOT, industrial IOT. And one of our big concerns, I want to get your reaction to this and thoughts is security is of paramount importance because it's not just a DDoS attack or some malware which is causing credit card data or these kinds of theft. You could actually take over machines. People could die this and serious issues around the guarantee. This is the number one conversation. What is the state of the art security posture in your area around software and the edge? >>So at AWS, whether it's IOT or any other workloads, we always say if you have two primary zeros, one is security and one is operations. Because if any company puts their faith in us, if we are down, their business is down and if there would be any security issues, of course all the trust would be broken and we do the exact same approach. Now with IOT, so we built our services with security in mind. For example, when you connect to AWS IOT core, every single individual device needs to have certificates to be identified. If you require that you can encrypt your data, it doesn't even lo you to connect to the cloud without encryption. We have software, as I said, at the edge with Amazon free artists and Greengrass where we support all of the hardware TM modules that you have security postures there. If you have secrets managers, they even have an award winning clout. >>If you're like security tool, which is called IOT device management, but at any given point in time audits but the you configured correctly and does something like detection. If something's going wrong, like when you get your credit card and said, Hey, by the way, have you been in this country? Candy making any purchase? If you figure out if something's going wrong with your device >> and you feel good that it's built in from zero, I mean you've got DNS tax going on. What? I mean you feel comfortable that it's, I mean we believe whatever we build, you can never be 100% sure and security is always evolving. But we believe that we are at the forefront of being, you're always the latest and greatest technology at the hands of our customers. >>Jerks. That's really powerful. Cause I saw one of the other announcements was really taking the Alexa voice service integration, but if I understand it rightly, it pulls that core along. So you know part of me was like, it's like okay Alexa enabled everywhere. That's great. I don't need 700 devices in my house that all have that. But the security piece is going to be needed everywhere. So help us tease that out. >>Maybe, maybe don't understand what we did you ask about the other launches. We also launched something called AVS integration for IUT and AVS stands for Alexa voice services. So if you know Alexa, that's our digital assistant that runs for example an equity devices, but if you want to build a device as a third party, which you can directly talk to media, there's microphones and speakers that is called AVS or Alexa built in devices and if you wanted to build one today you needed to put quite some resources onto this device because it needs to understand you. It needs to have a lot of audio processing. That means there's a lot of memory involved and quite some processing. Now I'm using some technical terms. You need something like a cortex, a CPU which makes this device expensive. So the bill of material is quite elevated and we were working with our Alexa team saying is how can we make this really, really affordable? >>If you found a trick where we said let's offload all of this audio processing to the cloud that you an eSense can build very dumb devices. The only thing that these devices don't need to do is have microphones, have our speaker and what we call a week work detection. They need to wake up and you say, Alexa, echo computer, everything else gets streamed to the cloud. Ptosis sits there and comes back so that you can reduce cost for those devices by at least a factor of half. And we had a great customer on stage as well because if you can make so cheap Alexa built in devices, you can put this into a light switch and iDevices now believe it or not, non-sales light switch. Yup. Which you can now directly talk to, reach, talks back and place your music. They're talking about your role. Again, I want to understand that you are not technical side, your development teams. What are you, what do you do on a daily basis? What's your job? So officially I'm a VP of engineering, so I'm a tech guy, so I love the hoodie. By the way. This is tech. That's because I'm on video. Okay. >>It looks great. So I'm an engineer by Heights and at Amazon we don't have a separation between businesses and product management and engineering. They call it a single thread of leaders that we believe the teams have to own it all. So that means my teams on everything from the conception of their services, the development operations that what be called dev ops and also the business behind. So that means all of the services, whether it's free outro, screen grabs at the edge, but it's IOT core device management and defender or our data services like IOT analytics or your talked about industrial site wise, their health or being conceived by my teams. They have all been developed and they are all operated today so that all customers can use that as it make. What should people >>totally does. Thanks for clarifying. That's awesome. Uh, what should people pay attention to? What should we be reporting on in your area? What are some of the key things that people watching this should pay attention to in this, in your IOT area? What are the most important items and products and services that you're doing? I think >>one of the most important things to understand is be talk just before the interview about this, that a lot of the technical hurdles actually solve that because we have the software on devices, we have the connectivity controlled services, and we have all the analytic services to make sense of the data that you can take actions. You don't need to be an expert in machine learning anymore to do machine learning at AWS. You don't have to be an embedded software developer to get connected devices. You don't have to be a data scientist to understand what your data does. The most interesting part though is there is a cultural aspect of this because in the past you had to ideally most likely in your old company join said, Oh, I would like to connect something, so do I have a purchase acquisition? Can I go to my finance team? Does it install this today? You don't need that anymore. With AWS IOT, the same thing that happens with the cloud and it happens with IOT. So understanding that via very powerful tools for engineers in the company that you can build at any given point in time. I think that's maybe the most, >>and I think the it, I think that whole process of the time it takes, they go to the airport on Thanksgiving, go through TSA and knows all that pre ocracy. And then the other thing too is that the other IOT used to be kind of a closed system self, um, form dot devices. Now you've got with Clough, you've got a lot more range and compatibility. Can you talk about that address, address that issue? Because there might be still legacy out there and no problem. It's data's data, but those are the days come in the cloud. But there's now a new shift happening where it's not just, you know, fully monolithic OT devices if it, so the pasta >>monolithic what's called machine to machine, close systems, IOT is the opposite there. It's where you say now all the devices and connections can be done in between the devices and the cloud. So it's system of systems. And in order to make that happen. For example, when you call it the legacy systems, we also announced on Monday and our IOT day additional features for IOT core that you can migrate legacy systems much easier to the cloud without that you need to update your devices. >>Yeah. Dirk, one of the things I find most interesting about your space as you span between the consumer and the enterprise piece, so I remember a few years ago there was like a hackathon on building skills for Alexa and it got lots of people involved. There was a giveaway of lots of the devices there. You know, we used to talk about the consumerization of it. How is what's happening in the tumor world? You know, how is the enterprise going to take care of take that and transform business as we see IOT permeating everywhere. >>So the capabilities that you need, whether you're going in industrial or in consumer or in the medical or pick your favorite other vertical is in essence the same. You need to connect the devices. You need to ensure that they're secure. We talked about security. You need to make sense of the data, whether you do this in the home with your television or your light switch or your robot, or you do the exact same thing with the most sophisticated robot in the industry. It's the same thing. The good thing about us handling all of those sites is that the scale that we gain with literally hundreds of millions of devices now managed by our service in the backend of course means we will handle all of that scale also in the industry and the security and postures and complexity that we need to handle an industrial also benefits computer, so our consumer side, so you benefit from both sides, very cheap and scale on the one industrial benefit. Very complex. How do you solve that consumable benefit, so it's very fruitful synergies if you like, >>Oh, you guys love to solve problems at Amazon that's going to eat those. Yeah. Derek, thank you so much for coming on and sharing the insights and what you're working on and what's important. Congratulations on all your success. Thank you so much. The threaded leader here. Final question for you. Eighth year of reinvent. It gets bigger every year. Louder. Crazier for parties, more business development more. Exactly. I mean just, it's crazy. Yeah. It's just say work hard, play hard. What is your favorite thing going on here? What's the coolest thing that you've seen? >>I think the coolest thing, and it might sound a little cheeky, is, is the excitement from all of our customers and partners coming here every year. >>PR tells you to say, I'm not about fraud. I mean, you're talking about products. I love my products. I'm still so happy about that. I mean, I can talk to a light switch now. Well, you see the comma car and the other quad had the area that we have yet. It's a very different experience that you can do. Don't talk to your lights, which when you get home your wife will think you're going crazy. I love that. Thank you for coming on. Really appreciate it. Thanks for having cube coverage here. All I'm, we're going to wrap up here. Keep coverage with Derek runs all the IOT for with an AWS exciting new area. It's going to change the game on architecture and solutions are being baked out in real time. We're here breaking out the cube in real time. I'm John. Thanks for watching.

>>LA from Las Vegas. It's the cube covering AWS reinvent 2019 brought to you by Amazon web services and along with its ecosystem partners. >>Hello everyone. Welcome back to the cubes. Day three coverage of ADAS reinvent in Las Vegas. It's the cubes coverage. Want to thank Intel for being the headline sponsor for the cube two sets. Without Intel, we wouldn't make it happen. We're here extracting the signal from the noise as usual. Wall-to-wall SiliconANGLE the cube coverage. I'm John Feria with student men and men doing a keynote analysis from Verner Vogel. Stu, you know Vernor's, they always, they always got the disc, the format jazzy kicks it off. You get the partner thing on day two and then they say Verner flask could nerd out on all the good stuff. Uh, containers. Coobernetti's all under the hood stuff. So let's jump in a keynote analysis. What's your take? What's Verner's posture this year? What's the vibe? What's the overall theme of the keynote? >>Well, well, first of all, John, to answer the question that everybody asks when Werner takes the stage, this year's t-shirt was posse. So Verner usually either has a Seattle band or it's usually a Dutch DJ, something like that. So he always delivers it. The geek crowd there. And really after seeing it of sitting through Werner's keynote, I think everybody walks out with AWS certification because architecturally we dig into all these environments. So right. You mentioned they started out with the master class on how Amazon built their hypervisor. Super important. Nitro underneath is the secret sauce. When they bought Annapurna labs, we knew that those chips would be super important going forward. But this is what is going to be the driver for outposts. It is the outpost is the building block for many of the other services announced this week. And absolutely the number one thing I'm hearing in the ecosystems around outpost but far gate and firecracker micro databases and managing containers. >>Um, they had some enterprises up on stage talking about transformation, picking up on the themes that Andy started with his three hour keynote just yesterday. But um, it's a lighter on the news. One of the bigger things out there is we will poke Amazon about how open and transparent they are. About what they're doing. And one of the things they announced was the Amazon builders library. So it's not just getting up on stage and saying, Hey, we've got really smart people and we architected these things and you need to use all of our tools, but Hey, this is how we do things. Reminded me a little bit of a, you know, just echoes of what I heard from get lab, who of course is fully open source, fully transparent, but you know, Amazon making progress. It's Adrian Cockcroft and that team has moved on open source, the container group. >>I had a great interview yesterday with Deepak saying, and Abby fuller, the container group actually has a roadmap up on containers. They're so sharing a lot of deep knowledge and good customers talk about how they're taking advantage, transforming their business. In serverless, I mean, John, coming out of Andy's keynote, I was like, there wasn't a lot of security and there wasn't a lot of serverless. And while serverless has been something that we know is transforming Amazon underneath the covers, we finally got to hear a little bit more about not just Lambda but yes, Lambda, but the rest of it as to how serverless is transforming underneath. >>You know ain't Jessie's got along three hour keynote, 30 announcements, so he has to cut save some minutes there. So for Verner we were expecting to go in a little bit more deeper dive on this transformational architecture. What did you learn about what they're proposing, what they're saying or continuing to say around how enterprises should be reborn in the cloud? Because that's the conversation here and again, we are, the memes that are developing are take the T out of cloud native. It's cloud naive. If you're not doing it right, you're going to be pretty naive. And then reborn in the cloud is the theme. So cloud native, born in the cloud, that's proven. Reborn in the cloud is kind of the theme we're hearing. Did he show anything? Did he talk about what that architecture is for transformation? Right. >>Did actually, it was funny. I'm in a watching the social stream. While things are going on. There was actually a cube alumni that I follow that we've interviewed at this show and he's like, if we've heard one of these journeys to you know, transformation, haven't we heard them all and I said, you know, while the high level message may be similar is I'm going to transfer math transform, I'm going to use data. When you looked at what they were doing, and this is a significant, you know, Vanguard, you know the financial institutions, Dave Volante commenting that you know the big banks, John, we know Goldman Sachs, we know JP Morgan, these banks that they have huge it budgets and very smart staffs there. They years ago would have said, Oh we don't need to use those services. We'll do what ourselves. Well Vanguard talking about how they're transforming rearchitecting my trip services. >>I love your term being reborn cloud native because that is the architecture. Are you cloud native or I used to call it you've kind of cloud native or kinda you know a little bit fo a cloud. Naive is a great term too. So been digging in and it is resonating is to look, transformation is art. This is not trying to move the organizational faster than it will naturally happen is painful. There's skillsets, there's those organizational pieces. There are politics inside the company that can slow you down in the enterprise is not known for speed. The enterprises that will continue to exist going forward better have taken this methodology. They need to be more agile and move. >>Well the thing about the cloud net naive thing that I like and first of all I agree with reborn in the cloud. We coined the term in the queue but um, that's kinda got this born again kind of vibe to it, which I think is what they're trying to say. But the cloud naive is, is some of the conversations we're hearing in the community and the customer base of these clouds, which is there are, and Jesse said it is Kino. There are now two types of developers and customers, the ones that want the low level building blocks and ones who want a more custom or solution oriented packages. So if you look at Microsoft Azure and Oracle of the clouds, they're trying to appeal to the folks that are classic it. Some are saying that that's a naive approach because it's a false sense of cloud, false sense of security. >>They got a little cloud. Is it really true? Cloud is, it's really true. Cloud native. So it's an interesting confluence between what true cloud is from a cloud native standpoint and yet all the big success stories are transformations not transitions. And so to me, I'm watching this it market, which is going to have trillions of dollars in, are they just transitioning? I old it with a new coat of paint or is it truly a skill, a truly an architectural transformation and does it impact the business model? That to me is the question. What's your reaction to that? >>Yeah, so John, I think actually the best example of that cloud native architecture is the thing we're actually all talking about this week, but is misunderstood. AWS outpost was announced last year. It is GA with the AWS native services this year. First, the VMware version is going to come out early in 2020 but here's why I think it is super exciting but misunderstood. When Microsoft did Azure stack, they said, we're going to give you an availability zone basically in your data center. It wasn't giving you, it was trying to extend the operational model, but it was a different stack. It was different hardware. They had to put these things together and really it's been a failure. The architectural design point of outpost is different. It is the same stack. It is an extension of your availability zone, so don't think of it of I've got the cloud in my data center. >>It's no, no, no. What I need for low latency and locality, it's here, but starting off there is no S3 in it because we were like, wait, what do you mean there's no S3 in it? I want to do all these services and everything. Oh yeah. Your S three bucket is in your local AC, so why would you say it's sharing? If you are creating data and doing data, of course I want it in my S three bucket. You know that, that that makes that no, they're going to add us three next year, but they are going to be very careful about what surfaces do and don't go on. This is not, Oh Amazon announces lots of things. Of course it's on outpost. It has the security, it has the operational model. It fits into the whole framework. It can be disconnected song, but it is very different. >>I actually think it's a little bit of a disservice. You can actually go see the rack. I took a selfie with it and put it out on Twitter and it's cool gear. We all love to, you know, see the rack and see the cables and things like that. But you know, my recommendation to Amazon would be just put a black curtain around it because pay no attention to what's here. Amazon manages it for you and yes, it's Amazon gear with the nitro chip underneath there. So customers should not have to think about it. It's just when they're doing that architecture, which from an application standpoint, it's a hybrid architecture. John, some services stay more local because of latency, but others it's that transformation. And it's moving the cloud, the edge, my data center things are much more mobile. Can you to change and move over? >>Well this spring you mentioned hybrid. I think to me the outpost announcement in terms of unpacking that is all about validation of hybrid. You know, VMware's got a smile on their face. Sanjay Poonen came in because you know Gelson you're kind of was pitching hybrid, you know, we were challenging him and then, but truly this means cloud operations has come. This is now very clear. There's no debate and this is what multi-cloud ultimately will look like. But hybrid cloud and public cloud is now the architecture of the of it. There's no debate because outpost is absolute verification that the cloud operating model with the cloud as a center of gravity for all the reasons scale, lower costs management, but moving the cloud operations on premises or the edge proves hybrid is here to stay. And that's where the money is. >>So John, there's a small nuance I'll say there because hybrid, we often think of public and private as equal. The Amazon positioning is it's outpost. It's an extension of what we're doing. The public cloud is the main piece, the edge and the outposts are just extensions where we're reaching out as opposed to if I look at, you know what VMware's doing, I've got my data center footprint. You look at the HCI solution out there. Outpost is not an HCI competitor and people looking at this misunderstand the fundamental architecture in there. Absolutely. Hybrid is real. Edge is important. Amazon is extending their reach, but all I'm saying is that nuance is still, Amazon has matured their thinking on hybrid or even multi-cloud. When you talk to Andy, he actually would talk about multi-cloud, but still at the center of gravity is the public cloud and the Amazon services. It's not saying that, Oh yeah, like you know, let's wrap arounds around all of your existing, >>well, the reason why I liked the cloud naive, take the T out of cloud native and cloud naive is because there is a lot of negativity around what cloud actually is about. I forget outpost cloud itself, and if you look at like Microsoft for instance, love Microsoft, I think they do an amazing work. They're catching up as fast as they can, but, and they play the car. Well we are large scale too, but the difference between Amazon and Microsoft Azure is very clear. Microsoft's had these data centers for MSN, I. E. browsers, global infrastructure around the world for themselves and literally overnight they have to serve other people. And if you look at Gardner's results, their downtime has been pretty much at an all time high. So what you're seeing is the inefficiencies and the district is a scale for Microsoft trying to copy Amazon because they now have to serve millions of customers anywhere. This is what Jessie was telling me in my one-on-one, which is there's no compression algorithm for experience. What he's basically saying is when you try to take shortcuts, there's diseconomies of scale. Amazon's got years of economies of scale, they're launching new services. So Jesse's bet is to make the capabilities. The problem is Microsoft Salesforce do is out there and Amos can't compete with, they're not present and they're going into their customers think we got you covered. And frankly that's working like real well. >>Yeah. So, so, so John, we had the cube at Microsoft ignite. I've done that show for the last few years. And my takeaway at Microsoft this year was they build bridges. If you are, you know, mostly legacy, you know, everything in my data center versus cloud native, I'm going to build your bridge. They have five different developer groups to work with you where you are and they'll go there. Amazon is a little bit more aggressive with cloud native transformation, you know, you need to change your mindset. So Microsoft's a little bit more moderate and it is safer for companies to just say, well, I trust Microsoft and I've worked with Microsoft and I've got an enterprise license agreement, so I'll slowly make change. But here's the challenge, Don. We know if you really want to change your business, you can't get there incrementally. Transformation's important for innovation. So the battle is amazing. You can't be wrong for betting on either Microsoft or Amazon these days. Architecturally, I think Amazon has clear the broadest and deepest out there. They keep proving some of their environments and it has, >>well the economies of scale versus diseconomies scale discussion is huge because ultimately if Microsoft stays on that path of just, you know, we got a two and they continue down that path, they could be on the wrong side of the history. And I'll tell you why I see that and why I'm evaluating Microsoft one, they have the data center. So can they reach tool fast enough? Can they, can they eliminate that technical debt because ultimately they're, they're making a bet. And the true bet is if they become just an it transition, they in my opinion, will, will lose in the long run. Microsoft's going all in on, Nope, we're not the old guard. We're the new guard. So there's an interesting line being formed too. And if Microsoft doesn't get cloud native and doesn't bring true scale, true reliability at the capabilities of Amazon, then they're just going to be just another it solution. And they could, that could fall right on there, right on their face on that. >>And John, when we first came to this show in 2013 it was very developer centric and could Amazon be successful in wooing the enterprise? You look around this show, the answer was a resounding yes. Amazon is there. They have not lost the developers. They're doing the enterprise. When you talk to Andy, you talked about the bottoms up and the top down leadership and working there and across the board as opposed to Google. Google has been trying and not making great progress moving to the enterprise and that has been challenging. >>Oh, I've got to tell you this too. Last night I was out and I got some really good information on jet eye and I was networking around and kind of going in Cognito mode and doing the normal and I found someone who was sharing some really critical information around Jedi. Here's what I learned around this is around Microsoft, Microsoft, one that Jed ideal without the capabilities to deliver on the contract. This was a direct quote from someone inside the DOD and inside the intelligence community who I got some clear information and I said to him, I go, how's that possible? He says, Microsoft one on the fact that they say they could do it. They have not yet proven any capabilities for Jedi. And he even said quote, they don't even have the data centers to support the deal. So here you have the dynamic we save, we can do it. Amazon is doing it. This is ultimately the true test of cloud naive versus cloud native. Ask the clouds, show me the proof, John, you could do it and I'll go with, >>you've done great reporting on the jet. I, it has been a bit of a train wreck to watch what's going on in the industry with that because we know, uh, Microsoft needs to get a certain certification. They've got less than a year. The clock is ticking to be able to support some of those environments. Amazon could support that today. So we knew when this started, this was Amazon's business and that there was the executive office going in and basically making sure that Amazon did not win it. So we said there's a lot of business out there. We know Amazon doing well, and the government deals Gelsinger was on record from VMware talking about lots of, >>well here's, here's, here's the thing. I also talked to someone inside the CIA community who will tell me that the spending in the CIA is flat. Okay. And the, the flatness of the, of the spending is flat, but the demand for mission support is going exponential. So the cloud fits that bill. On the Jedi side, what we're hearing is the DOD folks love this architecture. It was not jury rig for Amazon's jury rig for the workload, so that they're all worried that it's going to get scuttled and they don't want that project to fail. There's huge support and I think the Jedi supports the workload transformational thinking because it's completely different. And that's why everyone was running scared because the old guard was getting, getting crushed by it. But no one wants that deal to fail. They want it to go forward. So it's gonna be very interesting dynamics do if Microsoft can't deliver the goods, Amazon's back in the driver's seat >>deal. And John, I guess you know my final takeaway, we talked a bunch about outpost but that is a building block, 80 West local zones starting first in LA for the telco media group, AWS wavelength working with the five G providers. We had Verizon on the program here. Amazon is becoming the everywhere cloud and they really, as Dave said in your opening keynote there, shock and awe, Amazon delivers mere after a year >>maybe this logo should be everything everywhere cause they've got a lot of capabilities that you said the everything cloud, they've got everything in the store do great stuff. Great on the keynote from Verner Vogel's again, more technology. I'm super excited around the momentum around Coobernetti's you know we love that they think cloud native is going to be absolutely legit and continue to be on a tear in 2020 and beyond. I think the five G wavelength is going to change the network constructs because that's going to introduce new levels of kinds of policy. Managing data and compute at the edge will create new opportunities at the networking layer, which for us, you know, we love that. So I think the IOT edge is going to be a super, super valuable. We even had Blackberry on their, their car group talking about the software inside the car. I mean that's a moving mobile device of, of of industrial strength is industrial IOT. So industrial IOT, IOT, edge outpost, hybrid dude, we called this what year? Yeah, we call that 2013. >>And John, it's great to help our audience get a little bit more cloud native on their education and uh, you know, make sure that we're not as naive anymore. >>Still you're not naive. You're certainly cloud native, born in the clouds do, it's us born here. Our seventh year here at Amazon web services. Want to thank Intel for being our headline sponsor. Without Intel support, we would not have the two stages and bringing all the wall to wall coverage. Thanks for supporting our mission. Intel. We really appreciate it. Give them a shout out. We've got Andy Jassy coming on for exclusive at three o'clock day three stay with us for more coverage. Live in Vegas for reinvent 2019 be right back.

>> live from Boston, Massachusetts. It's the Cube covering A W s reinforce 2019 brought to you by Amazon Web service is and its ecosystem partners. >> Hey, welcome back, everyone to Cubes. Live coverage here in Boston, Massachusetts for eight of us reinforced Amazon Web service is inaugural event around Cloud Security. I'm Jeffrey Day Volante. Two days of coverage. We're winding down Day two. We're excited to have a year in The Cube Special guest, part of Big and that one of the big announcements. Well, I think it's big. Nerdy Announcement is the automated reasoning. Byron Cook, director of the Automated Reasoning Group within AWS. Again, this is part of the team that's gonna help figure out security use automation to augment humans. Great to have you on big part of show here. Thanks very much to explain the automated reasoning group. Verner Vogel had a great block post on All things distributed applies formal verification techniques in an innovative way to cloud security and compliance for our customers. For our own there's developers. What does that mean? Your math? >> Yeah, let me try. I'll give you one explanation, and if I puzzle, you all try to explain a different way. 300 So do you know the Pythagorean Theorem? Yeah, sure, Yeah. So? So that the path I agree in theory is about all triangles that was proved in approximately B. C. It's the proof is a finite description in logic as to why it's true and holds for all possible triangles. So we're basically using This same approach is to prove properties of policies of networks of programs, for example, crypto virtualization, the storage, et cetera. So we write software. This finds proofs in mathematics and this the proofs are the same as what you could found for thuggery and should apply into >> solve problems that become these mundane tasks of checking config files, making sure things are that worries kind of that's I'll give you an example. So so that's two in which is the T. L s implementation used, for example, in history. But the large majority >> of AWS has approximately 12,000 state holding elements, so that with if you include the stack of the heat usage, so the number >> of possible >> states it could reach us to to the 12,000. And if you wanted to show that the T. L s handshake Implementation is correct or the H Mac implementation is correct. Deterministic random bit generator implementation is correct, which is what we do using conventional methods like trying to run tests on it. So you would need, if you have, like, 1,000,000 has, well, microprocessors and you would need many more lifetimes in the sun is gonna admit light at 3.4 $4,000,000,000 a year to test to exhaustively test the system. So what we do is we rather than just running a bunch of inputs on the code, we we represent that as the mathematical system and then we use proof techniques, auto automatically search for a proof and with our tools, we in about 10 minutes or able to prove all those properties of s two in the way of your intimidates. And then we apply that to pieces of s three pieces of easy to virtual ization infrastructure on. Then, uh, what we've done is we've realized that customers had a lot of questions about their networks and their policies. So, for example, they have a complicated network worldwide different different availability zones, different regions on. They want to ask. Hey, does there exist away for this machine to connect to this other machine. Oh, are you know, to do all this all SS H traffic coming in that eventually gets to my Web server, go through a bastion host, which is the best, best practice. And then we can answer that question again, using logic. So we take the representation that semantics of easy to networking the policy, the network from the customer, and then the question we're asking, expressing logic. And we throw a big through their call ifthere improver, get the answer back. And then same for policy. >> So you're analyzing policies, >> policies, networks, programs, >> networks, connections. Yeah, right. And it to the tooling is sell cova. Eso >> eso eso basically way come with We come with an approach and then we have many tools that implement the approach on different, different problems. That's how you apply Volkova all underneath. It's all uses of a kind of tool called SMT inside. So there's a south's over, uh, proves theorems about formula and proposition. A logic and SMT is sat modular theories. Those tools can prove properties of problems expressed in first order logic. And so what we do is we take the, for example, if you have a question about your policies answering, answering semantic level questions about policies is actually a piece space problem. So that's harder than NP complete. We express the question in logic and then call the silvery and they get their answer back on Marshall it back. And that's what Volkova does. So that's calling a tool called CVC four, which is which is an open source. Prove er and we wenzel Koval. We take the policy three question encoded to logic. Call a Silver and Marshall answer back. >> What's the What's the root of this? I mean, presumably there's some academic research that was done. You guys were applying it for your specific use case, But can you share with this kind of He's the origination of this. >> So the first Impey complete problem was discovered by a cook and not not me. Another cook the early seventies on. So he proved that the proposition a ll satisfy ability problem is impeccably and meanwhile, there's been a lot of research from the sixties. So Davis and Putnam, for example, I think a paper from the mid sixties where they were, we're trying to answer the question of can we efficiently solved this NP complete problem proposition will satisfy ability on that. Researchers continue. There have been a bunch of breakthroughs, and so now we're really starting to see very from. There's a big breakthrough in 2001 on, then some and then some further breakthroughs in the 5 4008 range. So what we're seeing is that the solvers air getting better and better. So there's an international competition of Let's Save, usually about 30 silvers. And there's a study recently where they took all of the winners from this competition each year 2001 5 4008 30 2002 to 2011 and compared them on the same bench marks and hardware, and the 2002 silver is able to solve 1/4 of the benchmarks in the 2011 solved practically all of them and then the the 2019 silvers, or even better. Nowadays they can take problems and logic that have many tens of millions of variables and solve them very efficiently. So we're really using the power of those underlying solvers and marshaling the questions to those to those overs, codifying thinking math. And that's the math. The hour is you gave a talk in one sessions around provable security. Kind of the title proves provable. >> What's what is that? What is that? Intel. Can you just explain that concept and sure, in the top surfaces. So, uh, uh, >> so mathematical logic. You know, it's 2000 years old, right? So and has refined Sobule, for example, made logic less of a philosophical thing and more of a mathematical thing. Uh, and and then automated reasoning was sort of developed in the sixties, where you take algorithms and apply algorithms to find proofs and mathematical logic. And then provable security is the application of automated reasoning to questions and security and compliance. So we you wanna prove absence of memory, corruption errors and C code You won't approve termination of of event handling routines that are supposed to handle security events. All of those questions, their properties of your program. And you can use these tools to automatically or uh oh, our find proofs and then check The proofs have been found manually. That's what that's >> where approvable security fix. What was the makeup of the attendee list where people dropping this where people excited was all bunch of math geeks. You have a cross section of great security people here, and they're deep dive conversations Not like reinvent this show. This is really deep security. What was some of the feedback and makeup of the attendees? >> Give you two answers because I actually gave to talks. And the and the answers are a little bit different because the subject of the talk So there was one unprovable security, which was a basically the foundation of logic And how we how Cheers since Volkova and our program, because we also prove correctness of crypto and so on. So those tools and so that was largely a, uh uh, folks who had heard about it. And we're wanting to know more, and we're and we're going to know how we're using it and trying to learn there was a second talk, which was about the application of it to compliance. So that was with Tomic, Andrew, who is the CEO of Coal Fire, one of the third party auditors that AWS uses in a lot of customers used and also Chad Wolf, who's vice president of security, focused on compliance. And so the three of us spoke about how we're using it internally within eight of us to automate, >> uh, >> certification compliance, sort of a commission on. So that crowd was really interesting mixture of people interested in automated reasoning and people interested in compliance, which are two communities you wouldn't think normally hang together. But that's sort of like chocolate and peanut butter. It turns out to be a really great application, >> and they need to work together to, because it is the world. The action is they don't get stuck in the compliance and auditing fools engineering teams emerging with old school compliance nerds. So there's a really interesting, uh, sort of dynamic to proof that has a like the perfect use casing compliance. So the problem of like proving termination of programs is undecided ble proving problems and proposition a logic is np complete as all that sounds very hard, difficult and you use dearest six to solve this problem. But the thing is that once you've found a proof replaying, the proof is linear and size of the proof, so actually you could do extremely efficiently, and that has application and compliance. So one could imagine that you have, for example, PC I hip fed ramp. You have certain controls that you want to prove that the property like, for example, within a W s. We have a control that all data dressed must be encrypted. So we are using program verification tools, too. Show that of the code base. But now, once we've run that tool that constructs a proof like Euclid founded the sectarian serum that you can package up in a file hand to an auditor. And then a very simple, easy to understand third party open source tool could replay that proof. And so that becomes audit evidence. It's a scale of total examples >> wth e engineering problem. You're solving a security at scale. The business problem. You're solving it. Yeah. His customers are struggling. Just implementing There just >> aren't enough security professionals to hire right? So the old day is, the talk explains. It's out there all on YouTube's. The people watching the show can go check it out. But I am by the way I should I should make a plug for if you Google a W s provable security. There's a Web page on eight of us that has papers and videos and lots of information, so you might wanna check that out. I can't remember what I was answering now, but >> it's got links to the academic as >> well. Oh, yes. Oh, yes. That was the point that Tommy Kendra is pointing out, as in the old days, you would do an audit would come in to be a couple minutes box that we win this box. You check a few things to be a little network. Great. But now you have machines across the world, extremely complex networks, interaction between policies, networks, crypto, etcetera. And so there's There's no way a human or even a team of human could come in and have any reasonable chance of actually deeply understanding the system. So they just sort of check some stuff and then they call it success. And these tools really allow you to actually understand the entire system buyer and you guys doing some cutting edge work, >> folks watching and want to know how math translates into the real world with all your high school kids out their parents. This is stuff you learn in school like you could be played great work. I think I think this is cutting edge. I think math and the confidence of math intersects with groups. The compliance example audited example shows that world's gonna come together with math. I think this is a big mega trend. It's gonna not eliminate the human element. It's going augment that so great stuff, its final question just randomly. And while you're here, since your math guru we're always interested, we always covering our favorite topic of Blockchain, huh? We believe that a security conference is gonna soon have a Blockchain component because because of the mutability of it, there's a lot of math behind it. So as that starts to mature certainly Facebook entering him at their own currency. Whole nother conversation you don't want to have here is bring a lot of attention. So we see the intersection of security being a supply chain problem in the future. Your thoughts on that just generally. So So the problem of proving programs is undecided, and that means that you can't build a general solution. What you're gonna have to do is look >> for niche areas like device drivers, networks, policies, AP, I used to dream crypto et cetera, and then make the tools work for that area, and you will have to be comfortable with the idea that occasionally the tools aren't gonna be able to find an answer. And so the Amazon culture of being customer obsessed and working as closely as possible with the customer has been really helpful to my community of of logic, uh, full methods, practitioners, because they were really forced to work with a customer, understand the problem. So what I've been doing is listening to the customer on finding out what the problems with concerns. They are focusing my attention on that. And I haven't yet heard of, uh, of customers asking for mathematical proof on crypto currency Blockchain sorts of stuff. But I'm I I await further and you're intrigued. Yeah, I'm s I always like mathematics, but where we have been hearing customers asked for help is for Temple. We're working on free Our toss s o i o T applications Understand the networks that are connecting up the coyote to the cloud, understanding the correctness of machine learning. So why, why So I reused. I've done some machine learning. I've constructed a model. How do I know what it does? And is it compliant? Does it respect hip fed ramp PC, i et cetera, and some other issues like that. >> There's a lot of talk in the industry about quantum computing and creating nightmares for guys like you. How much thought given that you have any thing that you can share with us? >> Yes. Oh, there's there's work in the AWS crypto team preparing for the post quantum world. So imagine Adversary has quantum computer. And so there are proposals on eight of us has a number of proposals, and we've and those proposals have been implemented. So their standards and we've our team has been doing proof on the correctness of those. So, actually, in the one of my talks, I think the talk not with Chad and Tom. I show a demo of our work to prove the correctness of someplace quantum code. >> So, Byron, thank you for coming on the inside. Congratulations on the automated reason. Good to see it put in the practice and appreciate the commentary. Thank you very much. Thank you. Here for the first inaugural security cloud security event reinforced AWS is putting on cube coverage. I'm John Fairy with Day Volonte. Thanks for watching

>> Announcer: Live, from the Moscone Center it's theCUBE. Covering AWS Summit San Francisco, 2018. Brought to you by, Amazon Web Services. >> Welcome back I'm Stu Miniman and this theCUBE's live coverage from AWS Summit San Francisco. Happy to have two industry analysts here. Also, they are founding partners of Kaleido Insights Jeremiah Owyang and Jessica Groopman. Join me and help me extract the signal from the noise that is our industry today. Thanks so much for joining us. >> Great to be here. >> Jessica it's actually the first time I've met you. Why don't you give our audience a little bit about your background and what led to the finding of Kaleido Insights. >> Of course, so I have been covering Internet of things, IOT for many years, and also in the last couple of years have gone very deep in both AI and blockchain. So, have this sort of umbrella category, which we call automation at Kaleido, that I cover and basically we formed the firm because what we saw was companies pursuing single technologies. What's your AI strategy, what's your IOG strategy what's your AR strategy? When in reality, all of these things are impacting each other. so we take a kaleidoscopic sort of converged lens. >> I love that, so Jeremiah, I can't believe it's your first time on our program, John Furrier's taking photos. You're one of the first people I followed on Twitter when I got on, I've known you for many years, so thanks. You've watched so many of these waves. Give us your take as to how you fit into the Kaleidoscope of what's happening. >> Yeah thanks a lot, so I've been in Silicon Valley for over 20 years, and I've seen threewaves.com, social media, collaborative, and now autonomous is the fourth wave that we're seeing right now. And, it's just amazing to see. I see the frequency of technologies is happening at a faster pace, and the impacts they're having to business models and what companies have to do to keep up, so it is a really exciting time. A few years ago, Uber and Airbnb were really hot and I was focused in on that topic. And now, it seems like that is a lifetime ago. We're focused on autonomous technologies; blockchain, IOT. And the things that Amazon announced today on stage like machine learning and drones and self-driving cars. It's a dizzying pace on what's going on it's like it explodes. >> Just in the last couple of weeks, look what happened to Facebook and Amazon with some of the internal and external pressures on those companies. I like what you say, we get excited by the new shiny. It was like, oh everything that was big data is now kind of AI well, IOT and ML. At WikiBound, on our research side, we say it's data at the center of it, data data data. And we've been talking about this for years. Jeremiah and I worked in the boring old storage industry. Which was never about storing the information, it was, how do I allow it to be shared and leverage it. So it's like it's maturation, you know, what's your take what's at the center over here, what are some of the biggest challenges, what's real what's not, and you know, doing it in under a minute. >> It continues to be the central focus, I mean it's been very interesting watching in the IOT space for the past couple of years where we've been fixated on things, right, the objects. But in reality it's about extracting data either between or about or in aggregate or about individuals sensor data, around those things. So the same is true, now we're seeing this shift into cognitive IOT, where devices themselves can analyze and process at the edge, or send learnings across a whole fleet of vehicles or a whole ray of devices about a given environment. Same story, different technologies continuing the cycle. >> Jeremiah, you know, that pace of change you talked about is so challenging, how do you go from I've got an idea to I'm going to start rolling it out by the time I use it, aren't I out of date? What do you see, how do you help customers look at this holistically and not constantly be tripping over themselves? >> And for the bigger the company the harder it is for them to keep up. The technology paces are coming faster, so one trend that we're seeing is corporations are launching innovation programs. It's an actual team, they have a dotted line to the CEO or the Chief Product Officer, and they're responsible for testing all of these new technologies. Maybe in a secluded area or tying it back to a business unit but their job is to experiment like a startup in the big company. So that's what we're seeing right now, these innovation programs that are merging. >> Why don't you tell us, we're here at the Amazon show. How are they doing, what's good? Where are some of the competitors leading them, you know? What are customers asking for? >> It's fascinating to see how Amazon is effectively taking different strategies at every single part of the stack. I believe this morning Verner said, offering egalitarian access to data storage, to data compute to machine learning algorithms. Effectively, it makes the company's only job to have a great idea and then sort of bringing in Amazon to do the rest. What I also see is that it's shifting the Venn diagrams or the complex diagrams of who's competitive and where. Competitive landscapes are shifting all the time at each of these new announcements. >> It's like the only thing you need from IT is bandwidth, the pipe. And Amazon is promising to do just about all the rest of that. >> Yeah, but the challenges. Remember when cloud computing was supposed to be simple and now it's like, oh okay. I'm going to build a database on Amazon. Well which one of the 15 do you want? All the languages, all the choices. >> 125 products, they listed on stage. >> Yeah, there are over 1,000 releases every year. They have two to three new products almost every day. When they do this Summit and they did a bunch of announcements most of those weren't planned for this it just happened to be what's coming out of the CIDC pipeline, if you will from them. >> Imagine being a salesperson for Amazon just to sell the products. >> Or imagine being a customer trying to figure out just what to use in the architecture. >> Unfortunately we don't have a lot more time to talk. Give us some of the things your firm is looking at what we look to see in this year from you. >> Yeah, so broadly speaking, we're really focused on these different technology convergences. Just published new research on where IOT and blockchain are coming together, that's a space we're following very closely. The next report working on right now is around AI readiness. There's much ado about data pipelines and data preparedness as there should be, but there's a whole realm of people process, governance, leadership preparedness. So we're really focused on how companies can prepare for this new technology. >> I'm also looking at how the new business models from automation will impact different enterprise business units. And our other partners are looking at content and automation in the marketing side, and we just had a report released from Jaime Szymanski on how virtual reality and mixed reality is going to impact enterprise. And there's six used cases for the business and Rebecca is working on the marketing report. >> Jeremiah and Jess, hope we can get back with you soon to discuss all this, you hit a whole bunch of things. You mentioned blockchain, so we'll get 10X of the views of what we would have had otherwise. We'll be back with lots more coverage. Thanks to Kaleido Insights for joining us on this segment. We'll be back with lots more. I'm Stu Miniman, you're watching theCUBE. >> Man: Thank you. (digital music)