(calm music) >> Okay, welcome back everyone to theCUBE's live coverage here on the floor at Moscone south in San Francisco California for AWS summit, 2022. This is part of their summit conferences, not re:Invent it's kind of like becoming like regional satellite, mini re:Invents, but it's all part of education developers. Of course theCUBE's here. We're going to be at the AWS summit in New York city, only two this year. And this summer check us out. Of course, re:MARS is another event we're going to be going to so check us out there as well. And of course re:Invent at the end of the year and re:Inforce the security conference in Boston. So, Sarbjeet Johal, our next guest here. CUBE alumni, CUBE influencer, influencer in the cloud industry. Sarbjeet great to see you. Thanks for coming on. Oh, by the way, we'll be at Boston re:Inforce, re:Invent in December, re:MARS which is the robotics AI show, and of course the summit here in San Francisco and New York city, the hot areas. >> That's cool. >> Great to see you. >> Good to see you too. >> Okay. I got a lot of data to report. You've been on the floor talking to people. What are you finding out? What's the report? >> The report is actually, I spoke to three people from AWS earlier. As said one higher up guy from the doctor, Casey Tan. He works on French SaaS chips and he gave me a low down on how that thing works. And there's a systolic arrays TPUs, and like a lot of insider stuff >> Like deep Silicon chip stuff. >> Yes. And that they're doing some great stuff there. And of course that works for us at scale and for cloud guys it's all about scale. If you're saving pennies at that scale, you're saving millions and maybe hundreds of millions at some point. Right? So that was one. And I also spoke to the analytics guys and they gave me some low-down on the Glue announcements. How the big data processing is happening at AWS and how they are now giving you the ability where your infrastructure hugs your demand. So you're not wasting any sources. So that was a number one complaint with the Glue from AWS. So that was one. And then I did the DeepRacing race and my timings were like number 78. So. >> You got some work to do. You download your machine learning module. >> No, I will do that and then play with it. Yes. I will train one. >> You like a simulation too? >> Yeah. Yeah. I will do that simulation, yes. >> What else? Anything jump off the page for you. What's the highlight if you could point at something? Did anything pop up at you in this event with AWS? Was there any aha moment or something that just jumps off the page? >> I think it was mainly sort of incremental to be honest with you. And the one thing-- >> Nothing earth shattering >> Nothing earth shattering and that at the summit it's like that, you know, like it but they are doing new announcements of like almost every day with new services. So I would go home and read on that but there are some patterns that we are seeing emerging and there are some folks very active on Twitter. Mark in recent just did very controversial kind of tweet couple of days back. That was, that was hard. >> Was he shit posting again? >> Shit posting. Yeah. He was shit posting actually, according to actually I saw Corey as well on the floor, Corey and Rodrigo. And, and-- >> Did you see Corey's interview with me? We were talking about shit posting 'cause he wrote in this newsletter. Mark and recently Elon Musk, they're all kind of like they're really kind of active on Twitter with a lot of highly intelligent snarkiness. >> They're super intelligent and they know the patterns, they know the economics and technology. Super smart guys and yeah. Who is in control, there was a move from the middle seat and social media kind of side of things where people are controlling the narratives and who controls the narrative. Is it billionaires? Is it government? We see that. >> Well I mean, it's interesting seeing the power. I mean, I call it the revenge of the nerds. You got the billionaires who are looking at the political screw-ups that Facebook and others have done. And by not being clear and it's hard, it's a hard problem to solve. I don't really want to be in their seat. Even Andy Jassy is the CEO of AWS. What is he? I mean, he's dealing with problems that for some people would be their worst part of like they could ever dream of scenario. He's dealing with that at breakfast. And then throughout his day, he's got all kinds of Amazon's so big and Apple and you got Google and you got the fan companies. So, you know, at some point tech is now so part of society, it's not just the nerds from California. It's tech is in everything now. So it's a societal impact. And so there's consequences for stuff. And so you're starting to see this force for good that's come from the sustainability angle. You're going to start to see force for good with technology as it relates to people's lives. And we had Mapbox on the CUBE and they provide all this navigation and Gareth the guy who runs that division, he talks about dark kitchens, dark stores. So just they're re-engineering the supply chain of delivery. So we all been to restaurants and seen people there from picking up food delivery. Why are they going to the retail? So dark kitchens are just basically depots for supplying the 10 menus that everyone orders from. That's a change of a structural change in the industry. So that's jumped out at me, Matt Wood spoke to me about serverless impact to the analytics team. And again, structural changes, technical and culture. Right? So, so you're starting to see to me more and more of the two themes of some technology change, architectural change, system change and culture thinking. And you know, we had a 20 year old guest on here who was first worked at Amazon web services when he was 16. >> Wow. >> Graduated high school early and went into Amazon. He's like, I love tools. So people love tools. Hardware is coming back. Right? So I mean Sarbjeet this is crazy. >> It's crazy. >> What's going on. >> It's crazy actually. Remember the nine year old kid at re:Invent 2019. Karthick was the name if I remember, but I spoke to him and he was crazy. He was AWS certified and kids are playing with this technology in their high schools. >> It's awesome. >> And even in their elementary schools now. >> They can get their hands on it quicker. They don't need to go in full class for a year. They can self-teach, they can do side projects they can launch a side hustle, they can stand up a headless retail outlet, who knows what they can do if you got the Lego blocks. This is what I love about the cloud, you can really show something fast and then abandon it. >> Actually, I think it is all enabled through cloud. Like the accessibility of technology has gone like exponentially, like wildfire. Like once you have access to the cloud just all you need is connection to the internet. After that you have the VMs. and you have the serverless, there's zero cost to you. And things are thrown at you. Somebody who was saying that earlier here like we have said that many times it's like that's how the drug dealer, you know, sell the drug. Like sniff it, it's free, >> First is free. >> So they're doing it. Yes. >> We say that about theCUBE. >> And from the, I see cloud from two different angles, like we all do. And like, I try to sort of force myself to look at it from the both angles. There's the supplier side and the buyer side or the consumer side on the other side. Right? So from the supplier side, it's a race for talent to build it, number one, then number two is race for talent to train them. So we saw the numbers and millions being shown today at the keynote again. And Google is showing those numbers as well. Like how many millions they are training like 25 to 30 million people within next two, three years. It's crazy numbers. >> Sarbjeet I got to say so if I have to look at what jumped off the page for me on this event, was couple things and this is kind of weird nuanced stuff but I'll just try to explain it as best I can. Number one, we're going to see more managed services like DevOps managed services. As DevOps teams grow, talent is a problem. And Kubernetes obviously is growing and got to get that right. It's not easy to be a Kubernetes, you know slinging clusters around with Kubernetes. It's hard. I think that's got to get easier. So I think the path to easy is going to be some sort of abstraction service layer. And I think the smart people are going to have this layer will manage it and then provide that as a service, number one. Number two is this notion of a systems design thinking around elements, whether it's storage or maps for like Mapbox and around these elements they have to have a systematic effect of other things. You can't just, if it changes, it's going to have consequences that's what systems do. So, tooling being built around these elements and they have to have hardened APIs that is clear. People who are trying to be "cloud native" need to get this right. And you have to have the tooling in and around the the element and then have APIs to connect and then glue up. So it's interesting. Clearly those things are happening and multiple conversations, people were teasing that out. And then obviously the super cloud was coming in. >> Is there. >> Mapbox is basically a super cloud. They're like what snowflake is for data analytics. They are for-- >> MongoDB is another one. >> MongoDB's got Atlas. I mean, MongoDB was criticized for years. Doesn't scale. Remember the old lamp stack days, they were preferred. They're document, they nailed it with document. The document aspects of data, but they were always getting criticized. They can't scale. And they just keep scaling. But now with Atlas, they're on AWS. It's just, auto scale. So that's killer for MongoDB. So I think their stock price is undervalued my opinion but you know, I don't give legal advice. >> I think that the whole notion of-- >> Or financial advice. >> The multicloud, right? So for a multicloud to kill that complexity of multicloud, we have to go to the what Dave Vellante and you guys say super cloud, right? Another level of abstraction on top of infrastructure provider by AWS, Google cloud, Azure. So that's where we're going. >> Well, Dave and I debate this right, he bundles multi-cloud in there and most people think that's what he's saying but I'm saying multi-cloud is a reality. I mean, multi-cloud means you're going to have multiple clouds. They're just not you're not sharing workloads across those clouds. It's like not the same workload. That's not going to yet happen. I run Azure because I have 365, that's it. I run Amazon for everything else. That's kind of the use case. But to me, super cloud is building on top of AWS or Azure where you leverage their CapEx and create differentiated value. It's your own cloud without all the CapEx but it's got to be like super integrated and the benefit's got to be so good that it seems like pennies to your point earlier. >> Yeah. >> And the economics to the applications in it are just so obvious and they got to be they got to be so big for the application developer. So that's to me is super cloud. And then of course having the connected tissue to manage the transit around multiple clouds. >> Yeah. I think they have it too. I totally agree with you. But another thing is from having the developer background I think the backward compatibility is a huge issue in cloud. >> Yeah. I agree. >> It's a lot of technical debt being built and I hear that, I'm hearing that more and more. I think that we have to solve as industry as like these three main players have to solve that problem. So that's one big thing, actually. I'm very like after, you know, like to talk about it and all that stuff. So yeah. It's another thing is another pattern actually to all the cloud naysayers out there, right? Is that those are the people who come from the hardware background. So I've seen another pattern out there. So I'm trying to synthesize, who are these people who bash cloud all the time? I'm pro-cloud of course everybody knows that. >> We know you're pro, we're all pro cloud. We're totally biased. We love cloud >> Actually. No, I've seen both sides. I've seen both sides. I've worked at EMC, VMware, I worked at Oracle cloud as well. And then, and before that I have written a lot of software. A software developer is pro-cloud. A typical hardware ops guy or girl, they are pro on-prem or pro hybrid and all that. Like they try to keep it there. >> I think first of all, I have opinion on this. I think, I think you're right. But how hardware is coming back, if you look at how cloud is enabling hardware, it's retro, it's designed for the cloud. So hardware's going to offload, either accelerate stuff and offload stuff from the software guide. So look at DeepRacer it's hardware. Now it's a car. You've got the silicon and the chips. So the chips you're talking about. Those aren't chips for service and the data center. They're just chips to make the software in the cloud run better. >> Sarbjeet: Well scale. >> So scaling. And so I think we're going to see a Renaissance in hardware. It's going to look different. It's going to act different. So we're watching this. I mean, you brought up the idea of having a CUBE hardware box. >> Yeah. It's a great idea. >> It's a good idea. DM me and tell me it's a bad idea or good idea. I'll blame Sarbjeet for that. But what else have you learned? >> What else have learnt actually it's basically boils down to economics at the end of the day. It's about moving fast. It's about having developer productivity, again going back the cloud naysayers. It's like, why did you build a bike? Remember Steve Job used to say that, "computer is the bicycle for the human minds." >> Yes. >> Right. So cloud is the bicycle for the enterprises. They makes them move faster. 'So I think that's-- >> All right. We're closing down. We're going to hold on until they pull the plug on theCUBE literally. Sarbjeet great to see you on there. Check 'em out on Twitter. Great event. Good to see you, great report. Thank for sharing. Sarbjeet Johal here on theCUBE, taking over our community site I hear, right? Now you going to work-- >> I'm there. I'm always there. >> Great to have you on. I'm going to work on some new things with theCUBE. Really appreciate working with us. Thanks a lot. >> I really appreciate you guys giving me this platform. It's an amazing platform. Thank you very much. >> That's all right. We'll be back. That's it for our coverage of AWS summit 2020 here live on the floor. Events are back. Hybrid's back. We get theCUBE studios in Palo Alto in Boston. Re:invent at the end of the year but we're going to the summit in New York city. In the summer, we got re:Inforce in Boston the security conference. Re:MARS which is the robotics IML conference. And of course the big summit New York and San Francisco we're there of course. Share thecube.net for all the action. I'm John for your host with Sarbjeet here. Closing out the show. Thanks for watching. (Calm music)

(upbeat music) >> Okay, welcome back everyone to theCUBE's coverage of AWS Summit 2022, here at Moscone Center live on the floor, I'm John Furry host of theCUBE, all the action day two, remember AWS Summit in New York City is coming in the summer. We'll be there as well. Got a great guest Murli Murli who's the VP and GM of Cloud Native Business Unit Portworx, been in theCUBE multiple times. We were just talking about the customer he had on Ford from Detroit, where kubernetes will be this year. >> That's right. >> Great to see you. >> Yeah, same here, John. Great to see. >> So, what's the update? Quickly this, before we get into the country, give the update on what's going on in the company, what's happening? >> Well, you know, we've been acquired by Pure Storage it's well over a year. So we've had one full year of being inside of Pure. It's been wonderful, right? So we've had a great ride so far, The products have been renewed. We've got a bunch of integrations with Pure. We more than doubled our business and more than doubled our head count. So things are going great. >> I always had a, congratulations by the way. And I was going to ask about the integration but before I get there, yeah, we've been always like play some jokes on theCUBE and because serverless is so hot, I've been using storage lists and actually saw a startup yesterday had the word networking lists in their title. So this idea of like making things easier, but me, I mean serverless of this is basically servers that make it easier. >> Yeah, yeah >> So this is kind of where we see Cloud Native going. Can you share your thoughts on how Pure and Portworx are bringing this together? Because you can almost connect the dots in my mind. So say specifically what is the Cloud Native angle with Pure? >> Yeah. So look, I'll kind of start by being captain an obvious, I guess. Just sort of stating some obvious stuff and then get to what I hope will be a little bit more new and interesting. So the obvious stuff to start with is just the fact that Cloud Native is exploding. Containers are exploding. It's kind of a well known fact that 85% of the enterprise organizations around the world are pretty much going to be deploying containers, if not already in the next couple of years, right? So one it's really happening. The, buzz is now, it's not just in the future, the hype is now. The second part of that is it's really part of that is things are going production. 56% of these organizations are in production already. And that's the number is going to climb to 80 fairly quickly. So not only is this stuff being deployed as being deployed in sort of fairly mission critical, especially Greenfield applications. So that's kind of one, right? Now, the second thing that we're seeing is as they go in into production, John, the migraines are starting, right? Customer migraines, right? It's always happens in stuff that they have not looked around the corner and anticipated. So one of them is, again, a fairly obvious one is as they go into production, they need to be able to kind of recover from some oops that happens, right? And the kinds of think about this, right? John, this stuff is rapidly changing, right? Look at how many versions of kubernetes come out on a regular basis. On top of that, you got all these app, virgins, new database virgins, new stuff, vendors like us, ourselves have new virgins. So with all these new virgins, when you put it all together the stack, sometimes misbehave. So you got to kind of, "Hey, let me go recover." Right? You have outages. So essentially the whole area of data protection becomes a lot more critical. That's the migraine that people are beginning to get now, right? They can feel the migraine coming on. The good news is this is not new stuff. People know on- >> John: The DevOps. >> Yeah. Well, and in fact it is that transition from DevOps to ITOps, right? People know that they're going into production, that they need backup and data protection and disaster recovery. So in a way it's kind of good news, bad news, the good news is they know that they need it. The bad news is, it turns out that it's kind of interesting as they go Cloud Native, the technology stack has changed. So 82% of customers who are kind of deploying Cloud Native are worried about data protection. And in fact, I'll go one step further 67% of those people have actually kind of looked at what they can get from existing vendors and are going, "Hey, this is not it. This is not going to do my stuff for me." >> And by the way, just to throw a little bit more gas on that fire is ransomware attacks. So any kind of vulnerability opening? Maybe make people are scared. >> Murli: Absolutely. >> So with- >> Murli: Its a board level topic, right? >> Yeah, and then you bring down the DevOps, which is we all know the innovation formula launch in iterate, pivot, iterate, pivot, then innovation you get the formula, all your metrics, but it's a system. >> Correct. >> Storage is part now of a system when you bring Cloud Native into it, you have a consequence if something changes. >> Murli: Correct. >> So I see that. And the question I have for you is, where are we in the stability side of it? Are we close to getting there and what's coming out to help that, is it more tooling? Because the trend is people are building tools around their Cloud Native thing. I was just talking to MongoDB and they got a database, now that's all tooling. Vertically integrate into the asset or the product, because it integrates with APIs, right? So that makes total sense. >> So I think there's kind of again, a good news, bad news there, right? There's a lot of good news, right? In the world of containers and kubernetes what are some of the good news items, right? A lot of the APIs have settled down have been defined well, CNCF has done a great job promoting that, right? So the APIs are stable, right? Second, the product feature set, have become more stable, particularly sort of the the core kubernetes product security kind of stuff, right? Now what's the bad news. The bad news is, while these things are stable they are not ready for scale in every case yet, right? And when you integrate at scale, so and typically the tipping point is around 20 to 30 nodes, right? So typically when you go beyond 20 to 30 nodes then the stuff starts to come a apart, right? Like, the wheels come off of the train and all of that. And that's typically because there's a lot of the products that were designed for DevOps, are not well suited for ITOps. So really there is a new- >> And the talent culture. >> Exactly. >> Talent and culture sometimes aren't ready or are changing. >> So it's a whole bunch of people trying to use kind of a maturing product set with skill sets that are pretty low, right? So when we get into production, then other factors come into play, high availability, right? Security, you talk about ransomware, disaster recovery backup. So these are things that are sort of, I would say not 101 problems, but 201 problems, so right? This is natural as we go to that part of the thing. And that's the kind of stuff that, Portworx and Pure Storage have been kind of focused on solving. And that's kind of been how we've made our mark in the industry, right? We've helped people really get to production on some of these different points. >> Expectation on both companies have been strong, high quality, obviously performance on Pure side from day one, just did a great job with the products. Now, when you go into Cloud Native you have now this connection okay. To the customer, again I think huge point on the changing landscape. How do you see that IT to DevOps emerging? Because the trend that we're seeing is, abstracting way the complexities of management. So I won't say managed services are more of a trend, they've always been around but the notion of making it easier for customers. >> Yep, absolutely right. >> Super important. So can you guys share what you guys are doing to make it easier because not everyone has a DevOps team. >> Yeah, so look, the number one way things are made more easy, is to make it more consumable by making it as a service. So this is one of the things, here we are, at AWS Summit, right? And delighted to be here by the way. And we have a strategic alliance with with AWS, and specifically, what we're here to announce really is that we're announcing a backup as a SaaS product. Coming up in a few weeks we're going to be giing running on AWS as a service integrated with AWS. So essentially what happens is, if you have a containerized set of applications you're deploying it on EKS, ECS, AWS, what have you. We will automatically provide the ability for that to be backed up scaled and to be very, very container granular, very app specific, right? Yeah, so it's designed specifically for kubernetes. Now here's the kind of key thing to say, right? Backup's been around for a long time. You've interviewed, tons of backup people in the past. But traditional backup is just not going to work for kubernetes. And it's very simple if you think about it, John. >> John: And why is that? >> It's a very simple thing, right? Traditional backup focuses on apps and data, right? Those are the two kind of legs of that. And they create catalogs and then do a great job there. Well, here's, what's happened with Cloud Native. You have a thing inserted in the middle called kubernetes. So when you take a snapshot, I'm now kind of going into a specific kind of, world of storage, right? When you take a snapshot, what Portworx does is we take a 3D snapshot. What you really need to recover, from a backup situation where, you want to go back to the earlier stage to be kubernetes specific, you need a app snapshot, snapshot of the kubernetes spec, pod spec, And third of snapshot of the data. Well, traditional, backup folks are not taking that middle snapshot. So we do a 3D snapshot and we recover all three which is really what you need to be able to kind of like get backed up, get recovered in minutes. >> Okay and so the alternative to not doing that is what? What will happen? >> You To do that, to do your old machine level backup? So what happens with traditional backups are typically VM level or machine level, right? So you're taking a snapshot of the whole kind of machine and server or VM setup and then you recover all of that, and then you run kubernetes on that and then you try to recover it- >> John: To either stand everything up again. >> Yeah, yeah. >> John: Pretty much. >> Yeah. Whereas, what do most people want to do? This is a very different use case, by the way, right? How does this work? What people are doing for kubernetes is they're not doing archival kind of backup. What they're doing is real time, right? You're running an ops. Like I said, you got an oops, "Hey, a new release for one of the new databases then work right? Boom! I want to just go back to like yesterday, right? So how do I do that? Well, here you can just go back for that one database, one app, and recover back to that. So it's operational backup and recovery as opposed to archival backup and recovery. So for that, to be able to recover in seconds, right? You need to be, he kind of want integrated with AWS which is what we are. So it's integrated, it's automated, and it's very, very container granular. And so these three things are the things that make it sort of, very specific way. >> I love the integration story. 'Cause I think that's the big mega trend we're seeing now is is that integrating in. And, but again, it's a systems concept. It's not standalone storage, detached storage. >> Murli: Exactly. >> It's always, even though it might be decoupled a little bit it's glued together through say- >> John, you said it right. The easy button is for the system, right? Not for the individual component. Look, all of us vendors in this ecosystem are going around framing, having a being easy. But when we say that, what do we mean? We mean, oh, I'm easy to use. Well that doesn't help the user. Who's got to put all this stuff together. So it's really kind of making that stack work. >> This is easy to use, but it made these things more complex. This is what we do in the enterprise solve complexity with more complexity. >> Putting the problem to the other guy. Yeah. So it's that end to end ease of use is kind of what I would say, is the number one benefit, right? One it's container specific and designed for kubernetes. And second, it really, really is easy. >> Well, I really like the whole thing and I want to get your thoughts as we close out, what should people know about Pure and Portworx's relationship now and in the Amazon integration, what's the new narrative the north Star's still the same? High performance store, backup, securely recover and deliver the data in whatever mechanism we can. That north Star's clear, never changes, which is great. I feel love about Pure and Cloud Native. It's just taking the blockers away- >> I think the single biggest thing I would say, is all of these things, what we're turning into it is as a service offering. So if we're going to backup as a service our Portworx product now is going to be the Portworx enterprise Pure Storage product is going to be offered as a service. So with, as a service, it's easy to consume. It's easy to deploy. It's fully automated. That's the kind of the single biggest aha! Especially for the folks who are deploying on AWS today, AWS is well known for being easy to use. It's kind of fully automated. Well here, now you have this functionality for Cloud Native workloads. >> Final question, real quick, customer reaction so far, I'm assuming marketplace integration, buying terms, join selling, go to market? >> So yeah, it is integrated billing and all of that is part of that kind of offering, right? So when we say easy, it's not just about being easy to use it's about being easy to buy. It's being easy to expand all of that and scaling. Yeah. And being able to kind of automatically or automagically as I like to say, scale it, right? So all of that is absolutely part of it, right? So it is really kind of... It's not about having the basics anymore. We've been in the market now for six, seven years, so right? We have sort of an advanced offering that not only knows what customer want but anticipates what ones can expect and that's a key difference. >> I was talking to Dr. Matt Wood real quick. I know we got to wrap up on the schedule, but earlier today about AI and business analytics division's running and we were talking about serverless and the impact of serverless. And he really kind of came down the same lines where you are with the storage and the cloud data which is, "Hey, some people just want storage and the elastic leap analytics without all the under the cover stuff." Some people want to look under the covers, fine whatever choice. So really two things, so. >> Yeah, yeah. All the way from you can buy the individual components or you can buy the as a service offering, which just packages it all up in a on easy to consume kind of solution, right? >> Final, final question. What's it like at Pure everything going well, things good? >> We love it, man. I'll tell you these folks have welcomed us with open arms. And look, I've been acquired twice before. And I say this, that one of the key linchpins to a successful integration or acquisition is not just the strategic intent that always exists but really around a common culture. And, we've been blessed. I think the two companies have a strong common culture of being customer first, product excellence, and team wins every time. And these three things kind of have pulled us together. It's been a pleasure. >> One of the benefits of doing the queue for 13 years is that you get the seats things. Scott came on the queue to announce Pure Storage on theCUBE, cuz he was a nobody else. There was, oh, you're never going to get escape Velocity, EMC's going to kill, you never owned you. Nope. >> Well, we're talking about marketplaces and theCUBE is the marketplace of big announcements, John. So this is, delighted- >> Announcements. >> Yeah. Yeah. Well that was the AWS announcement. Yeah. So that's, that is big >> Final words, share the audience. What's what to expect in the next year for you guys? What's the big come news coming down? What's coming around the corner? >> I think you can expect from from Pure and Portworx the as a service set of offerings around, HADR backup, but also a brand new stuff, keep an eye out. We'll be back with John. I hope that talking about this is data services. So we have a Portworx data service product that is going to be announced. And it's magic. It's allowing people to deploy databases in a very, very, it's the easy button for database deployment. >> Congratulations on all your success. The VP and General Manager of the Cloud Native Business Unit. >> You make it sound bigger than it actually is, John. >> Thanks for coming on. Appreciate it. >> Thanks. >> Okay theCUBE coverage be back for more coverage. You're watching theCUBE here, live in Moscone on the ground at an event AWS Summit 2022. I'm John Furrier. Thanks for watching. (upbeat music)

>>Okay. And welcome back to the cubes live coverage here in San Francisco, California for 80 us summit 2022 Amazon web services summit 2020 New York city is coming up in the summer will be there. Check us out the cube.net. Our next guest here is Jim long. The CEO of dig also known as local. BTV a very interesting AWS customer doing some really progressive things around video and, uh, challenging the status quo in code cutting and all kinds of broadcast models. Jim, welcome to the cube. Great to see you. >>Thank you, John. Great to be here. Okay. >>So first of all, before we get into some of the disrupt option, take a minute to explain what is dig and local BTV. >>Uh, dig is all about, uh, providing, uh, edge video networking for broadcast television, basically modernizing local television and hopefully extending it to hyper local content like high schools and community government and community channels and things like that. So essentially free bringing, using the internet as an antenna to bring broadcast television to your phone, your laptop you're connected TVs. >>So if I understand it correctly, if I UN and I look at the, the materials of your site, you basically go into each market, Metro areas like New York Philly bay area, grab the tee signal out of the air. >>Yep. >>Local TV, and then open that up to everyone. Who's got, um, an >>Correct. And, uh, what, we've, where we're essentially building a hybrid network with AWS. Uh, I like to say we got all the smart and account stuff, you know, in the cloud at AWS. And we have all the dumb, fast stuff in the actual TV market. We have servers and transcoding there we work with, uh, of course, um, uh, AWS on that centrally as well. But basically that hybrid cloud allows us to be the fastest simplest and lowest cost way to get a local video. Any type could be an antenna or an IP stream to a local house. So we're, so are the local pickup and delivery people. We're not building a brand, we're not building content. We're delivering the local content to the local views. You >>Like the pipes. >>We are, we're essentially an infrastructure company. Um, we're right at that wonderful intersection of the, uh, the infrastructure and the content where I always like to play. >>I like, I love the store. I think the cost of that nature, how you're using Amazon, it's really impressive. Um, what are some of the cool things you're doing on AWS that you think's notable? >>Well, of course the, the standard issue stuff where you want to store all your data in the cloud. Right? So we, uh, and we use a quick site to, to get to that. And obviously we're using S3 and we're using media tailor, which we really like, which is cuz we first actual company on the planet. I believe that's inserting digital ads, impression based ads into local broadcast streams. So that's, that's fun because the advertisers, they like the fact that they could still do traditional TV buys and they could spice it up with digital impressions based, but ads on us. Yeah. And, and we're adding to it a real fun thing called clip it, which is user clipping. It's an app that's been running on AWS for years. It's had over half a million plays in social media. Yeah. We're combining those together and, and AWS makes it very simple to do that. >>Well, I've been using your app on my Firestick and uh, download local BTV on the app store. Um, I gotta say the calendar's awesome. And the performance is 10 times better than, than some of the other streaming apps because the other performance they crash all the time. The calendar's weird. So congratulations. Clearly you're running the cloud technology. I gotta ask you what's going on in the market? Netflix missed their earnings. The stock was down big time. Um, obviously competition what's up going on with Netflix? >>Well, what's, it's a big shift. >>What does it mean for the streaming market? >>Well, what it means is, is, is a consumer choice. It's really the golden age of consumer choice. Uh, originally back when I was a kid, it was all antenna TV. We didn't even have DBRS right. And then, uh, the cable companies and the satellite companies, the phone companies came in and took over and all of a sudden everyone started paying for TV for just linear TV. Right? And then the next thing, you know, streaming comes around, uh, Netflix shows up for, for VOD or, or SVOD, they call it cuz it's payt TV and uh, and the whole, uh, that ecosystem starts to melt down. And now you have a consumer choice market where you can pay, pay for VAD or pay for, for linear. And everyone does linear and everyone does VAD or you can use free TV. Now we correctly guessed that free TV was gonna have a huge comeback. You know, know what is it about free even obviously gen Z smarter than us boomers. They love free too. Uh, targeted advertising makes the ads less, uh, painful or less of a distraction. Uh, so we knew that free ad supported TV was gonna happen. Lots of stuff happened. And then, then the, uh, major media companies started doing their own subscription apps. Right? They're all cool. >>We like paramount plus >>Paramount plus Disney pluses, PN peacock, uh, time Warner's doing something. I mean, it's all cool, but you know, people only have so much of a big pocketbook. So what it's doing is pay TV has now become much more complicated, but also you, you know, you gotta trade off. So you saw it with Netflix, right? Yeah. Netflix is suffering from there's too much pay TV. So where are you gonna put your money on Comcast? On YouTube TV paramount plus Netflix. >>Yeah. I mean, I love the free thing. I gotta bring up something. I wanna get your reaction to a company called low cast went under, they got sued out of their deal. They were the free TV. Are you guys have issues like them? What's the cast most people don't know got was, was >>Doing same. So we started before low cast and we're uh, what we would call a permissions based system, legal system. The broadcast Mar industry, uh, is, uh, is the wild wild west. I mean, I like to say antenna TV is a direct to consumer. The antenna is a direct to consumer device and it's controlled by the channel. People it's not controlled by a platform like Comcast, right? It's not controlled by a stick. >>When you say channel, do you mean like CBS or >>Yeah, CBS or the local Korean religious cooking channel or, uh, Spanish channels or local independent to television, which is really a national treasure for us. The United States really should be making sure that local content, local channels, uh, do well local businesses, you know, with targeted advertising, Janes nail salon can, can now advertise just in San Jose and not the entire San Francisco TV market. Um, so you ha you have, have all that going on and we recognize, you know, that, that local content, but you have to have permission from the channel stuff. It's not easy because you got channels on stations. You have syndicators, it's hard to keep track of. And sometimes you, you, uh, you, you know, you have to shift things around, but, uh, low cast, uh, like another kind before it just went hog wild, illegal, trying to use a loophole, uh, didn't quite work out for 'em and, uh, >>You see, they have put out of business by the networks, the names, the big names. Yes. Content people, >>Correct. I mean the big, the big guys, but I mean, because they weren't following the rules, um, >>The rules, meaning license, the content, right. >>Well correct. Or yes, >>Basically they, they were stealing the content in the eyes of the, >>Well, there is, there is, it is a little of, a bit of a gray area between the FCC and the copyright laws that Congress made. So, um, there are people certainly out there that think there is a path there, low cast, didn't find it. We're not trying to find it. Uh, we just want to get all the free TV, uh, the bottom line. And you've seen fast channels explode recently, Pluto, uh, Samsung TV. >>And what does that all mean? >>Well, what it means is people love free TV and the best free TV out there is your local TV. So putting that on the internet and those comp, but the media companies, they have trouble with this new stuff. What's, >>What's your >>They're overthinking it. What's >>Some of this CBS, NBC, all these big guys. >>Well, those guys have a little less trouble than the people that actually, uh, they're affiliates, right? So there's 210 TV markets and the, uh, your major networks, you know, they have their own stations. And in a bit, you know, in about 39% of the population, which is about 15 to 20, is it >>Cultural or is a system system problem? >>No, it's a, it's a problem of all the, the media companies are just having trouble moving towards the new technology and, and they're, I think they're siloing it. >>So why not? You gonna let 'em die. Are you trying to do deals with em? >>Oh no, no, absolutely. For us, if we don't make money, unless stations make money, we want local TV to, to flourish. It is local TV is Neilson, just report yesterday, you know, uh, that, uh, local TV is growing. We're taking advantage of that. And I think the station groups are having a little trouble realizing that they have the original, fast channels before Pluto, before Tubi did it in movies. And, and, and what >>Are people understanding in the, in the industry? I know NA's coming up a show. Yeah, >>That's right. >>National associated of broadcasters. What's going on in that industry right now. And you're, if you get to put it down the top three problems that are opportunities to be solved, what would they be? >>Well, I think, you know, I think the, the, the, the last, the, the best one that's left is what we're doing. I have to say it, uh, I think it's worth billions. >>You free TV over the air free and stream >>O TV. Oh yeah. Over the air TV that also works with the internet, right. Public internet connected to public television stations so that everybody, including homeless people, et cetera, that, you know, they don't have a TV, they don't have an antenna, they can't afford comp. They got an >>IPhone though. >>They an iPhone. For sure. And, and so it's, it's, uh, it's a wonderful thing. It's, you know, our national broadcasting and I don't think the station groups or the major networks are taking advantage of it they're as much as they should. Yeah. And, and I don't think, you know, obviously NBC and CBS with their new apps, they're sort of done with that. They did mergers, they got, they got the virtual pay guys. I mean, YouTube TV off the ground, the only thing left is suck another shitload of good, uh, eyeballs and, and advertising. >>Well, I mean, yeah, I think that, that, and what you said earlier around subscription fatigue, I mean, nobody wants to have 20 subscriptions. >>Well, that brings up a whole new other war. That's going on that, thank goodness. We're not part of it's the platforms versus the cable companies. Right. Versus whatever. Right. Everyone's trying to be your open garden or your closed garden. They're trying to get your subscriptions in bundle self bundling it's. But I mean, it's wonderful for consumers, if you can navigate through it. Uh, we wanna, we think we'll have one of the gems in any of that everyone's want local TV. And so we'll supply that we're already doing that. We're supplying it to a couple companies, uh, free cast as a company, uh, app, a universal streaming, you know, manager, your all, all your, uh, streaming, a streaming aggregation, put your paid stuff in, put your free stuff in. They do that. And, and as, as does Roku try trying to do that fire TV, Xfinity's trying to do it. So it's all, it's a new war for the platform and hopefully we'll be on everyone. >>Well, you've been in this industry for a long time, you know, the streaming market, you know, the TV market. Um, so it's, it's good. I think it's a new battle, the shift's happening. Um, what should people know about dig local? BTV what are some of your goals for the next year or two? What are you trying to do? >>Well, what we're really trying to do is make sure that local, uh, local television thrives so that it can support wider communities. It could support hyper local content. So if you're, if you're, and we love the old paradigm and channel change, right? Forget, you know, every other app has all these boxes going by on different rows and stuff. And, and yeah, you can search and find stuff, but there's nothing like just changing channels, whether a commercial's on or, or you, you wanna see what else is on. You know, you're gonna go from local television and maybe all of a sudden, you'll see the local high school play over on another part of the, of the spectrum. And, and what we're trying to do is get those communities together. And the local high school people come over and find the local, you know, uh, Spanish, uh, Nova channel or something like that. >>So local is the new hot. >>It is. Absolutely. And by the way, it's where this high CPMs are gonna go. And the more targeted you get >>Ad revenue, >>I mean, that's for us is, is, is our number one, re we have a number of revenue streams, but targeted ads are really great for local, right? And, and so we're, we're gonna make an announce. We've >>Lost that we've lost that local, I've seen local things that local Palo Alto paper, for instance, just shut down this local sports high school coverage, our youth sports, because they don't budget, right? There's no TV community channels, like some Comcast throwaway channel. Um, we lost, we, we lo we're losing >>Local. No, I think that's a real national shame. And so I think if we can strengthen local television, I think it'll strengthen all local media. So we expect to help local radio and local newspapers. That's a bigger part of the vision. Uh, but I it's gonna happen. There's >>An education angle here too. >>There is an education angle because the bottom line is you can use linear television as a way to augment. Uh, we have a really exciting project going on in New York, uh, uh, with, uh, some of the housing, uh, projects, uh, in Harlem and, and, and the Bronx, uh, their I idea is to have the, the homework channel and they can, and literally when you have a, and both swiping and everything you can have, I mean, literally you can have a hundred schools that, that have things well, >>We know zoom schooling sucks. I mean, that didn't work. So I think you're gonna see a lot of augmentation, right. >>Amazon. >>I was just talking to some people here, AI training, machine learning, training, all here could be online in linear format. >>Yeah. And exactly. And then I think about the linear format is it's discovery television, and you can also, um, you know, you can also record it. Yeah. Right. If you see a program and you want to record it, you sit >>Record. So final minute we have left. I want to just get your thoughts on this one thing and, and ask your question. Are you looking for content? Are you, I outreach at the content providers who, >>Well, we're, we're PRI our primary mission is to get more channel local channels on which really means station groups and independence. We have a number, I mean, basically 50% of the channels in any market. When we move into it are like, this is a no-brainer. I want more eyeballs. We're Nielsen, uh, RA, uh, rated mean we support. And so we, >>How many markets are you in right now? >>We're in 21 now. And we hope to be in, uh, over 50 by the end of the year, covering more than half the United States. >>So, all right, Jim, thanks for coming on the queue. Really appreciate it. >>My pleasure. Good luck >>Recognition. Very disruptive disrupting media, um, combination of over the air TV, local with I internet. Obviously we love that with a cube. We want a cube channel anywhere possible. I'm John furry host of the queue here at AWS summit. Highing all the big trends and technologies in cloud and media back with more coverage after this short break,

>>Okay, welcome back everyone. To the cubes coverage of AWS summit, 2022 in San Francisco, California. We're here, live on the floor at the Mosconi south events are back. I'm John fur, your host. Remember AWS summit 2022 in New York city is coming this summer. We'll be there with the live cube there as well. Look for us there, but of course, we're back in action with the cloud and AWS. Our next guest Garrett Miller is the general manager of navigation at Mapbox. I mean, it's been a Amazon customer for a long time, Garrett. Thanks for coming on the cube. >>Yeah. Thanks for having us, John. >>So you guys are in the middle of, I love the whole location base slash we developer integration. We've had many conversations on the cube around how engineers and developers are becoming embedded into the application, whether it's from a security standpoint, biometrics, all kinds of stuff, being built into the app and, and location navigation. That's right. Is huge from cars. Everyone knows their car, car map. That's right. GPS satellites, some space it's complicated. It sounds like it sounds easy, but I know it's hard. Yeah. You, you get the keynote going on today. Give us a quick update on Mapbox and we'll then we'll talk about the keynote. >>Yeah. You bet John that's right. So as you were saying, you know, it really is. It's all about location intelligence. And how does that get embedded into the applications? And to the point you made vehicles that are out there on the roads to today. So we target developers. Those are our key customers, and we've got over three and a half million registered on the platform today. They consume the modules that we build with APIs, SDKs, data sets, and more and more applications to accomplish whatever those location needs might be. >>Why we appreciate you coming on. You are featured keynote by presenter here at summit, which means Amazon thinks you're super important to share. I'll say your customer. So you, I know you've been a customer for a long time as a company, but what was your keynote about what was the main theme? The developers were all here. You got the builders. What was your content? What did you present this morning on the keynote? Yeah, >>Well, this morning we really talked a lot about logistics and the, this story that we told was know in the logistics industry, there is a massive movement to shorter and shorter delivery windows. And so the, the, the story that we told is really around a 10 minute delivery. Now, have you ever wondered how you get a 10 minute delivery? You, you place an order on your phone and all of a sudden somebody shows up at your front doorstep. You ever wonder about that? >><laugh> >>Some shows supply >>Chain. Someone's waiting in the wings from my call. >>Yeah. >>Yeah. Well, that's right. >>John's about to order sometime soon. That's right. You ready? That's right. Do all these assets. That's >>Right. They're all ready for you. But there's actually a tremendous amount that actually goes into that. And so it really starts with designing the right distribution system up front. And so we've got tools and, and applications and, and APIs that support that. And really it, every single step of the way, location is a critical aspect to making that delivery happen and getting it to a customer's doorstep in 10 minutes or less. And so how are you understanding the real time road graph that underlies a, a, a driver going from perhaps a dark store, dark kitchen to getting in, excuse me, in front of a customer in 10 minutes with hot food. >>I mean, this is a big point. I was just joking about waiting for me, you know, that, but the point is, is that it's not obvious, but it sounds really hard. I know it's hard because to have that delivery, a lot of things have to happen. It's not just knowing location. >>That's exactly >>Right. So can you just UN pull appeal back the covers on that? What's going on there? >>Yeah. So imagine this is, is, it really starts, as I was saying with designing that distribution system and it's putting in place where you might not expect it, it's actually putting in place a retail store, but these aren't any retail stores, right? These are dark stores. These are dark kitchens that are strategically placed as close as possible, the customer density, so that you can actually shorten that window as much as possible to get you whatever that order might be. But from there, it actually goes quite a bit further when an order actually comes in, you've gotta be able to understand how do I sign an, a driver to get that order to the customer in that, in that very short period of time, more often than not, it's getting it to the driver that can get there the fastest, once you've got the right driver identified, how are you actually then going to enable them to get from point a to B to get that order. >>And then perhaps from B to C to get to your front door, being able to do turn by turn navigation that reflects everything. That's how happening in the real world to be able to get there on a timely way is critical. And then wrapping around that actually the, the, the end customer's experience your experience with how are you placing that order? Yeah. How are you using Mapbox services to do that? How are you being able to track on your application and say, well, you know, great, I expect 10 minutes and they're five minutes away. Are you gonna show up our APIs and SDKs power? That experience, >>I wanna get into the product in a second, but you brought up something I think's important to highlight. One is dark kitchens, dark stores. That's right. Okay. Term people may or may not have heard of, we all have experience in COVID going to our favorite restaurant, which has been kind of downsized because of the COVID and we're waiting for our food. And someone comes in from another delivery ever standing in line next was just pick something up. I mean, they're going through the front door. That's like the, the, the branded store. So, so is it right to say that dark kitchens are essentially replicas of the store to minimize that traffic, but, but also to be efficient for something else that's right. >>It actually even goes further than that. There are many restaurant brands. Now, it only exists as a brand. They don't have a restaurant that you can go to and sit down and have that meal. They actually only operate dark kitchens to, to serve that demand of people wanting to order up, Hey, I want my food. I want it. Now, those brands exist to serve that need. >>All right. So great for the definition, we just define dark kitchens, dark stores, but also brings, I wanna get your reaction to this before we get into the product, cuz this is a trend that's right. This is not like a one off thing. That's right. It's not a pulled forward TA a market that was COVID enabled. This is actually a user experience inflection point. That's >>Right. >>Can you share your vision on what this means? Because there's mobile ordering, there's the dynamics of the kitchens as a supplier of something in stores. So that's content or a product that's being delivered to a consumer via of the web. So now there's gotta be a whole nother reef factoring of the operating environment. Now that's what's happening is that might get that >>Right? No, that's exactly right. And even if you step back, even further and you, you think about the, the journey that the logistics industry has been on, it used to be that two days was that really exciting delivery time. Right. And everybody got it super excited. Then it became next day. Then it became same day and now it's become 10 minutes. And even some companies are out there offering seven minute deliveries, right. And in order to do that, you've gotta completely retool your business. So you can think the logistics and industry really existing on two continuums, you've got pre-planned deliveries on one hand and on-demand deliveries on the other. And there are two parallel distribution systems and ecosystems and industries really springing up to serve those different types of demand. >>So you've been on Amazon web services customer for how many years, >>Since 2013 in our founding. And you know, actually we're really proud to say that we were born on Amazon and we have scaled on Amazon. >>How are they helping you scale? What are they doing to help you? >>Well, I'd say just about everything. And if you think about their, the, the services that Amazon provides for us, they power every single step of our business along the way. And so I'll give you an example. We can walk through that with some of the tech technology. I, if you think about again, how do you get 10 minutes? You gotta have a pretty precise understanding of what's going on in the real world. And so to do that, it, for us, it all starts with collecting billions and billions of data points from sensors that are out there in the world. We stream that into our technology stack, starting at the very beginning with Amazon ESIS. And so that's just the start. But then that feeds into our entire technology stack that all runs on site on top of AWS, to where we're running our own AI models that we use Amazon SageMaker to make, and then stream it back out to our AP, through our APIs, to our se Ks and applications that sit on the edge again, all leveraging Amazon technology. >>Well, I think this is a great use case and I'll get back into the, the Mapbox a second, but Amazon, you guys are executing what I call the super cloud vision, which is snowflake you guys building on their CapX leverage. You're building a super cloud on your own. It's your app, it's your cloud. >>That's right. That's right. So if you, again, if you think about it, you know, and actually just stepping back for a moment, tell about Mapbox for a second is what, what Mapbox can do is provide the most accurate digital representation of the physical world. Think about the Mapbox technology, delivering the most accurate digital twin of mother earth, right? That's what we do. And the way that we do that is to consume, as I said earlier, vast amounts of data, we've got powerful AI that structures that data, and then really robust and scalable infrastructure that underpins all of that. Now the benefit of working with a company like AWS is that they take care of that third point. Yeah. Which means we get to go focus on the first two, which is how we differentiate and build our >>Business. And that's exactly the model of how you win in the cloud. In my opinion, that's the go big piece, the go and there's tools that fit in white spaces. But that's the, I think that's the right formula. Let's get back to Mac boxer. I know you've got news. You got the, the, uh, Mapbox fleet SDK. You announced, I wanna hold on that we'll get to in a second, let's get back to what you got are providing that example as you have this new operating environment of how delivery and, and supply chain and that's example, I want to know how tech your technology is making all that work. Because I was just talking to someone last night about this web van was web 1.0 and crash never was successful. Instacart is kind of hurting. So maybe they're optimized. You could save them. I mean, cuz the economics gotta work. If you don't have the underlying system built, that might fail. So there'll be probably the third version that gets it. Right. Maybe at Mapbox again, I'm speculating, but I'll let you talk. Yeah. How does Mapbox solve the, that problem? >>You know, it's interesting if you come back to that, that, that analogy we're using with AWS and how do you use AWS to win in the cloud? It's the same story for Mapbox of how do you win in the location industry? And what we do is provide those same tool sets of APIs and SDKs, the thing go power, those logistics companies like an Instacart, who's a great customer of ours to run in their logistics business on top of it again, it's all about how do you provide technology that allows your customers yeah. To focus on what matters from a differentiation perspective as they focus on building their >>Business and you think your economics is gonna enable these people to be successful >>100%. That's >>The goal >>100%. >>All right. So another thing that I wanna bring up is the fleet SDK, what was the, that you announced they can, you just quickly share the news on what this >>Is? Yeah, yeah, absolutely. I appreciate that, John. Yeah. So today on the Eve of earth day, we're very excited to announce Mapbox fleet going into, uh, our beta launch and what Mapbox fleet is, is, uh, a set of tools and application that allows our customers to more efficiently route their vehicles, which means lowering their fuel consumption. And at the same time, more efficiently dispatching those vehicles, which means that you can get more done with fewer assets, essentially. How do you get more packages onto a single vehicle to get those to the customers? Now you may be watching the news and understanding, yeah, there's a tremendous explosion of delivery going. Yeah. And that's fantastic. Right? That's great business for our logistics customers. Good business for us too. What's happening though, is that as those volumes are ballooning, everybody's all of a sudden, really looking at their cost structures and trying to understand how do I manage this? >>Right. I have efficiency targets as a business. Maybe I've been really focused on customer acquisition. Now it's time to flip the model and really understand in the economics of profitable growth. We help with that, with that focus on efficiency, but the double edged sword with growth and, and you know, running a logistics business is that you actually have a tremendous amount of carbon emissions that are associated with that. Yeah. For a car to show up or a truck to show up, to deliver something to your house, their emissions associated with that. So what we find is that we're able to not only drive dollar savings for our customers, but also as part of that, with the efficiency angle, really help to drive down the overall carbon impact in the carbon footprint of what they do. And >>How do you do that? >>Well, it's the efficiency lens, right? So if somebody is driving 20%, fewer miles, they're going to emit 20% fewer. Okay. >>Gotcha. So it's a numbers game across the board with actual measurement. That's exactly right. Built in and say optimization paths, all kinds of navigation. >>That's exactly right. So embedded within Mapbox fleet application are those optimization algorithm. >>So you got a platform that's setting up for the next level delivery system slash new way to connect people to goods and services and other things getting from point a to point B, you got the sustainability check you're in the cloud, born in the cloud cloud scale. I gotta a, I can't go without asking if you're on Amazon, you do all this cool stuff. There's gotta be a machine learning an AI angle. So what is that? Yeah, absolutely. >>Absolutely. AB yeah. You know, <laugh> guilty as charged. >>I would say >>John. Uh, so look, I >>Think, I mean AI and, and sustainability are gonna be, I think filings in my, in the future we be talking about on the cube, if you're not an AI company or, and doing force for good stuff, I think there's gonna be mandatory requirements on those. >>I couldn't three more. I think the ESG agenda is an incredibly important one. One that's core to Mapbox has been since the founding of the company back in 2013. Uh, but if you look at how does AI and ML fit into Mapbox, it does that in a number of different ways. And really when we come back to this idea of Mapbox creating a digital twin of the earth, the way that we do that, it is through ingesting a tremendous amount of sensor data. Right? You can imagine, uh, Mapbox customers on any given week drive, billions of miles, we're capturing all of that telemetry data to understand and make sense of what does that mean for, for, for the world that allows us to push in any given day 700,000 updates to our underly, your location technology stack, and at the same time provide insights as to exactly what's happening. Are there roadside incidents? Are there, are there issues with traffic? So by collecting all of that data, we run incredibly powerful AI models on top of it that allow us to create the, the real world representation of what's happening. That's exactly how >>It works. What, what, as they say in the, um, big data AI world is you guys have a tremendous observation space. You're looking at a lot of surface area data that's exactly right. Across multiple workloads and apps. That's >>Exactly >>Right. You can connect those dots with the right AI. >>That's exactly right. That's exactly right. And I think I, you know, coming back to your point around sustainability, I do think that the AI and ML capabilities that are being delivered are going to be paramount to that. It being such a fundamental aspect to what am, to what Mapbox does as a business allows us to launch these game changing solutions like Mapbox fleet and staying on that, that kind of environmental and sustainable kick for a second. Just last week, we launched our, our EV routing API that powers the next generation of EVs. So AI ML sustainability. If it's not core business today, it's gotta very quickly become core. >>It's really interesting. I really think what we're teasing out here and it's fun to talk about it now because we'll look back at it later 10 years or more and say, wow, this is completely refactored the industry and lives and the planet ultimately. Right. So this is a, a kind of got force for good built into the system natively. That's >>Right. That's >>That's interesting, Garrett, thanks so much for sharing the story. Give you the last word, share with the audience, what you guys are up to, what you're promoting, what you're looking for. Are you hiring, uh, is there a call to action? You wanna share? Give the plug for the company? Yeah, >>Absolutely hiring like crazy come join Mapbox and BU build the future of geolocation and intelligent location services with us. Uh, the, thanks so much for the time, >>John. Thanks for coming on cube coverage here in San Francisco, California Mosconi center back at live events. I'm John for host cube stayed with us as day two wraps down. Remember New York city. This summer will be there as well. Cube coverage of more cloud coverage events are back. Thanks for watching.

(upbeat music) >> Okay, welcome back everyone, Cube coverage live on the floor in the Moscone center in San Francisco, California. I'm John Furrier host of the Cube. AWS summit 2022 is here in San Francisco, we're back in live events. Of course, Amazon summit in New York city is coming, Amazon summit this summer we'll be there as well. We've got a great guest Mike Miller, GN of AI devices at AWS always one of my favorite interviews. We've got a little prop here, we got the car, DeepRacer, very popular at the events. Mike, welcome to the Cube. Good to see you. >> Hey John, thank you for having me. It's really exciting to be back and chat with you a little bit about DeepRacer. >> Well I want to get into the prop in a second, not the prop, the product. >> Yeah. >> So DeepRacer program, you got the race track here. Just explain what it is real quick, we'll get that out of the way. >> Absolutely so, well, you know that AI, AWS is passionate about making AI and ML more accessible to developers of all skill levels. So DeepRacer is one of our tools to do that. So DeepRacer is a 3D cloud-based racing simulator, a 1/18th scale autonomously driven car and a league to add a little spicy competition into it. So developers can start with the cloud-based simulator where they're introduced to reinforcement learning which basically teaches the, our car to drive around a track through trial and error and of course you're in a virtual simulator so it's easy for it to make mistakes and restart. Then once that model is trained, it's downloaded to the car which then can drive around a track autonomously, kind of making its own way and of course we track lap time and your successful lap completions and all of that data feeds into our league to try to top the leaderboard and win prizes. >> This is the ultimate gamification tool. (chuckles) >> Absolutely >> Making it fun to learn about machine learning. All right, let's get into the car, let's get into the showcase of the car. show everyone what's going on. >> Absolutely. So this is our 1/18th scale autonomously driven car. It's built off of a monster truck chassis so you can see it's got four wheel drive, it's got steering in the front, we've got a camera on the front. So the camera is the, does the sensing to the compute board that's driven by an Intel atom a processor on the, on the vehicle, that allows it to make sense of the in front of it and then decide where it wants to drive. So you take the car, you download your trained model to it and then it races around the track. >> So the front is the camera. >> The front is the camera, that's correct. >> Okay, So... >> So it's a little bit awkward but we needed to give it plenty of room here so that I can actually see the track in front of it. >> John: It needs eyes. >> Yep. That's exactly right. >> Awesome. >> Yes. >> And so I got to buy that if I'm a developer. >> So, developers can start in two ways, they can use our virtual racing experience and so there's no hardware cost for that, but once you want the experience, the hands on racing, then the car is needed but if you come to one of our AWS summits, like here in San Francisco or anywhere else around the world we have one or more tracks set up and you can get hands on, you can bring the model that you trained at home download it to a car and see it race around the track. >> So use a car here. You guys are not renting cars, but you're letting people use the cars. >> Absolutely. >> Can I build my own car or does it have to be assembled by AWS? >> Yeah, we, we sell it as a, as a kit that's already assembled because we've got the specific compute board in there, that Intel processor and all of the software that's already built on there that knows how to drive around the track. >> That's awesome, so talk about the results. What's going on? What's the feedback from developers? Obviously it's a nerd dream, people like race cars, people love formula one now, all the racing there. IOT is always an IOT opportunity as well. >> Absolutely, and as you said, gamification, right? And so what we found and what we thought we would find was that adding in those sort of ease of learning so we make it the on-ramp to machine learning very easy. So developers of all skill levels can take advantage of this, but we also make it fun by kind of gamifying it. We have different challenges every month, we have a leader board so you can see how you rank against your peers and actually we have split our league into two, there's an open division which is more designed for novices so you'll get rewarded for just participating and then we have a pro league. So if you're one of the top performers in the open league each month, you graduate and you get to race against the big boys in the pro leagues. >> What's the purse? >> Oh, the, (John laughing) we definitely have cash and prizes that happen, both every month. We have prizes cause we do races every month and those winners of those races all get qualified to race at the championship, which of course happens in Las Vegas at re:Invent. So we bring all the winners to re:Invent and they all race against each other for the grand prize the big trophy and the, and the, and the cash prize. >> Well, you know, I'm a big fan of what you guys are doing so I'm kind of obviously biased on this whole program but you got to look at trend of what's going on in eSports and the online engagement is off the charts, are there plans to kind of make this more official and bigger? Is there traction there or is this just all part of the Amazon goodness, love that you guys give back? I mean, obviously it's got traction. >> Yeah. I mean, the thing that's interesting about eSports is the number of young people who are getting into it and what we saw over the last couple years is that, there were a lot of students who were adopting DeepRacer but there were some hurdles, you know, it wasn't really designed for them. So what we did was we made some changes and at the beginning of this year we launched a student focused DeepRacer program. So they get both free training every month, they get free educational materials and their own private league so they know students can race against other students, as part of that league. >> John: Yeah. >> So that was really our first step in kind of thinking about those users and what do we need to do to cater to their kind of unique needs? >> Tell about some of the power dynamics or the, or not power dynamics, the group dynamics around teams and individuals, can I play as an individual? Do I, do I have to be on a team? Can I do teams? How does that look? How do you think about those things? >> Yeah, absolutely. Great, great question. The primary way to compete is individually. Now we do have an offering that allows companies to use DeepRacer to excite and engage their own employees and this is where operating as a team and collaborating with your coworkers comes into play so, if, if I may there's, you know, Accenture and JPMC are a couple big customers of ours, really strong partners. >> John: Yeah. >> Who've been able to take advantage of DeepRacer to educate their workforce. So Accenture ran a 24 hour round the, round the globe race a couple years ago, encouraging their employees to collaborate and form teams to race and then this past year JPMC, had over 3000 of their builders participate over a three month period where they ran a private league and they went on to win the top two spots, first place and second place. >> John: Yeah. >> At reinvent last year. >> It reminds me the NASCAR and all these like competitions, the owners have multiple cars on the race. Do you guys at re:Invent have to start cutting people like, only two submissions or is it free for all? >> Well, you have to qualify to get to the races at re:invent so it's very, it's very cutthroat leading up to that point. We've got winners of our monthly virtual contests, the winners like of the summit races will also get invited. So it's interesting, this dynamic, you'll have some people who won virtual races, some people who won physical races, all competing together. >> And do you guys have a name for the final cup or is it like what's the, what's the final, how do you guys talk about the prizes and the... >> It's, it's the DeepRacer Championship Cup of course. >> John: Of course. (laughter) >> Big silver cup, you get to hoist it and... >> Are the names inscribed in it, is it like the Stanley cup or is it just one. >> It's a unique one, so you get to hold onto it each year. The champion gets their own version of the cup. >> It's a lot of fun. I think it's really kind of cool. What's the benefits for a student? Talk about the student ones. >> Yeah. Yeah. >> So I'm a student I'm learning machine learning, what's in it for me is a career path and the fund's obvious, I see that. >> Yeah absolutely. You know, the, for students, it's a hands on way that's a very easy on-ramp to machine learning and you know, one of the things, as I mentioned we're passionate about making it accessible to all. Well, when we mean all we were really do mean all. So, we've got a couple partners who are passionate about the same thing, right? Which is how do we, if, if AI and ML is going to transform our world and solve our most challenging problems, how can we get the right minds from all walks of life and all backgrounds to learn machine learning and get engaged? So with two of our partners, so with Udacity and with Intel we launched a $10 million AWS, AI and ML scholarship program and we built it around DeepRacer. So not only can students who are college and high school students, age 16 and over can use DeepRacer, can learn about machine learning and then get qualified to win one of several thousand scholarships. >> Any other promotions going on that people should know about? >> Yeah, one, one final one is, so we talked about enterprises like JPMC and Accenture, so we've got a promotion that we just started yesterday. So if you are an enterprise and you want to host a DeepRacer event at your company to excite your employees and get 'em collaborating more, if you have over 50 employees participating, we're going to give you up to a hundred thousand dollars in AWS credits, to offset the costs of running your DeepRacer event at your, at your company so >> That's real money. >> Yeah. Real, real, real exciting I think for companies now to pick up DeepRacer. >> So, I mean, honestly, I know Andy Jassy, I have many sports car conversations with him. He's a sports guy, he's now the CEO of Amazon, gets to go all the sporting events, NFL. I wish I could bring the Cube there but, we'll stick with with cloud for now. You got to look at the purse kind of thing. I'm interested in like the whole economic point of cause I mean, forget the learning for side for a second which is by the way awesome. This is great competition. You got leader boards, you got regional activities, you got a funneling system laddering up to the final output. >> And we've really done a decent job and, and of adding capabilities into that user experience to make it more engaging. You can see the countries that the different competitors are from, you can see how the lap times change over time, you know, we give awards as I mentioned, the two divisions now. So if you're not super competitive, we'll reward you for just participating in that open league but if you want to get competitive, we'll even better rewards monthly in the Pro League. >> Do you guys have any conversations internally like, this is getting too big, we might have to outsource it or you keep it in inside the fold? (laughter) >> We, we love DeepRacer and it's so much fun running this, >> You see where I'm going with this. You see where I'm going with this right? The Cube might want to take this over. >> Hey. >> And you know >> We're always looking for partners and sponsors who can help us make it bigger so, absolutely. >> It's a good business opportunity. I just love it. Congratulations, great stuff. What's the big learning in this, you know, as a as an executive, you look back you got GM, AI super important and, and I think it is great community, communal activity as well. What's the learning, what have you learned from this over the years besides that it's working but like what's the big takeaway? >> Yeah, I mean. We've got such a wide range of developers and builders who are customers that we need to provide a variety of opportunities for people to get hands on and there's no better way to learn a complex technology like AI and ML than getting hands on and seeing, you know, physically the result of the AI and I think that's been the biggest learning, is that just having the hands on and the sort of element of watching what it does, just light bulbs go off. When, when developers look at this and they start piecing the, the puzzle pieces together, how they can benefit. >> So I have to ask the question that might be on other peoples minds, maybe it's not, maybe I'm just thinking really dark here but gamers love to hack and they love cheat codes, they love to get, you know, get into the system, any attempts to do a little hacking to win the, the the game, have you guys, is there, you know? >> Well, well, you know, last year we, we we released an open source version of the vehicle so that people could start using it as a platform to explore and do that kind of hacking and give them an opportunity build on top of it. >> So using mods, mods modules, we can mod out on this thing. >> Yeah, absolutely. If you go to deepracer.com, we have sort of extensions page there, and you can see, somebody mounted a Nerf cannon onto the top of this, somebody built a computer vision model that could recognize you know, rodents and this thing would kind of drive to scare 'em, all kinds of fun topics. >> So it's a feature, not a bug. >> Absolutely. >> Open it up. >> Yeah. >> And also on transparency, if you have the source code out there you guys can have some review. >> Yeah. The whole idea is like, let's see what developers, >> It's really not hackable. It's not hackable. >> Yeah, I mean, for the, if you think about it when we do the races, we bring the cars ourselves, the only way a developer interacts is by giving us their trained models so... >> And you, do you guys review the models? Nothing to review, right? >> Yeah. There's nothing really to review. It's all about, you know, there, there was a model that we saw one time where the car went backwards and then went forwards across the finish line but we, we, we gently told them, well that's really not a valid way to race. >> That was kind of a hack, not really a hack. That was a hack hack. (laughter) That was just a growth hack. >> Exactly, but everybody just has a lot of fun with it across the board. >> Mike, great, thanks for coming on. Love the prop. Thanks for bringing the car on, looks great. Success every year. I want to see the purse, you know, big up to $1,000,000 you know, the masters, you know, tournament. >> Someday. (John chuckles) >> You guys.. >> Thank you for having me John. >> DeepRacer again, Fun Start has a great way to train people on machine learning, IOT device, turns into a league of its own. Great stuff for people to learn, especially students and people in companies, but the competitive juices flowing. That's what it's all about, having fun, learning. It's the Cube here in San Francisco. Stay with us for more coverage after this short break. (gentle music)

>>Okay, welcome back everyone. Cube's coverage here. Live on the floor at AWS summit, 2022, an in person event in San Francisco. Of course, AWS summit, 2022 in New York city is coming up this summer. The cube will be there as well. Make sure you check us out then too, but we day two of coverage had a great guest here. I Han VP of developer relations, Mongo DB, formally of AWS. We've been known each other for a long time doing, uh, developer relations at Mongo DB. Welcome to the queue. Good to see >>You. Thank to be here. Thanks for inviting me, John. It's great >>To, so Mongo DB is, um, first of all, stocks' doing really well right now. Businesswise is good, but I still think it's undervalue. A lot of people think is, is a lot more going huge success with Atlas. So congratulations to the team over there. Um, what's the update? What's the relationship withs, you know, guys have been great partners for years. What's the new thing. Yeah. >>So MongoDB Atlas obviously runs on several different major cloud providers, but AWS is the largest partner that we work with in the public cloud. So the majority of our Atlas workloads for our customers are running on the AWS platform. And just earlier this year, we announced a new strategic collaboration agreement with AWS. That's gonna further strengthen and deepen that partnership that we have with them. >>What's the main product value right now on the scale on, on Atlas, what's the drive in the revenue momentum. >>So, I mean, you know, there's a huge trend in the industry towards cloud managed databases, right? You look back 10, 15 years ago when we first met, most customers were only and operating their own data infrastructure, either running it in their own data centers, or maybe if they were really early using the primitives that cloud providers like AWS offered to run their databases in the cloud when Amazon launched RDS back in 2009, I think it was, we started to see this trend towards cloud managed databases. We followed that with our own Atlas offering back in 2016. And as Andy jazzy from AWS would say very often it's offloading that UND differentiated, heavy lifting, allowing developers to focus on building applications. They don't have to win and operate the data infrastructure. We do it for them, and that has proven incredibly popular amongst our customers. You know, Atlas route right now is growing at 50, sorry, 85% car year on year growth. >>You know, um, I've been following MongoDB for a long, long time. I mean, going back to the lamp stack days, you know, and you think about what Mongo has done as a product because of the developer traction, you know, Mongo can't do this, just keeps getting better every year. And, and the, I think the stickiness with developers is a real big part of that. Can you your view there cuz you're in VE relations. I mean, developers all love Mongo. They're teaching in school. People are picking up a side hustles, they're coding on it, using it all everywhere. I mean it's well known. >>There's a few different reasons for that. I think the main one is the, the document orientated model that we use, the document data models that are used by Mongo DB, just a net way for developers to work with data. And then, uh, we've invested in creating 16 first party drivers that allow developers using various different programming languages, whether that's JavaScript or Python or rust to integrate MongoDB, natively and idiomatic with their software. So it's very, very easy for a developer to pick up MongoDB, grab one of these drivers from their package manager of their choice and then build applications that natively manipulate data inside MongoDB, whether that's MongoDB Atlas or our enterprise edition on their own premises. They get a very consistent and very easy to, I easy to use developer experience with our, with our platform. >>Talk about the go to market with AWS. You guys also have a tightly coupled relationships. There's been announcements there recently. Uh, what's changing most right now that people should pay attention to. Well, >>The first thing is there's a huge amount of technical integration between MongoDB and AWS services. And that's the basis for many of our customers choosing to run Mon Mongo DB on AWS. We're active in 23 AWS regions around the world. And there's many other integration points as well, like cryptographic protection of Mongo MongoDB, stored data using Amazon cryptographic services, for example, or building serverless applications with AWS Lambda and MongoDB servers. So there's a ton of technical integration. Yeah, but what we started to work on now is go to market integration with AWS as well. So you can buy Mongo DB Atlas through AWS's marketplace. You can use the payer, you go offering to pay for it with your AWS bill. And then we're collaborating with AWS on migrations and other joint go to market activities as well. That >>Means get incentives, the sales people at AWS. >>Of course our moreover I mean, it's just really easy for customers, really easy for developers to consume. Yeah, they don't need to contract with MongoDB. They can use their existing AWS contracting, their existing discounting relationships and pre purchasing arrangements with AWS to consume Atlas. >>It's the classic meet the customers where they >>Are exactly right. Meet the developer where they are and meet the customers where they are now with this new model as well. >>Yeah. I love marketplace. I think it's been great. You know, even with its kind of catalog and vibe, I think it's gonna get better and better, uh, over there teams doing good work. Um, and it's easy to consume. That's key. >>Yeah. Super easy. Reduce that friction and make it real easy for developers to adopt this. Right. >>Talk about some of the top customers that you guys share with AWS. What are some of the customers you guys have together and what the benefits of the >>Relationship joint references that we talk about? A lot, one of them is Shutterfly. So in the photographic products area, they built a eCommerce offering with MongoDB and AWS. The second is seven 11 with seven 11. We're doing a lot in the mobile space. So edge applications, we've got a feature in MongoDB Atlas that allows you to synchronize data with databases on mobile devices. Those can be phones point of sale devices or handheld devices that might be used in the parcel industry, for example. So seven 11 using us in that way. And then lastly with Pitney Bowes, we've got a big digital transformation project with Pitney Bowes where they've reimagined their, uh, postage and packaging services, delivering those to their customers, using MongoDB as a data store as well. >>I wanna get in some of the trends, you've got a great per you know, you know, Mongo from Amazon side and now you're there. Um, Mongo's, as you pointed out has, has been around for a long time. What are some of the stats? I mean, how many customers, how many countries? Well, it's pretty massive >>Mind. We've got almost quarter of a billion downloads today, 240 million MongoDB downloads since we launched the first product <laugh>, we've got 33,000 active customers that are using MongoDB Atlas today and we're running well over a million free tier clusters on MongoDB Atlas across all of the different providers where we operate the service as well. So these numbers are, you know, mind blowing in terms of scale. Uh, but of course at the core of that is operational excellence. Customers love Mongo DBS because they don't have to operate it themselves. They don't have to deal with fairly conditions. They don't have to deal with scaling. They don't have to deal with deployment. We all, we do all of those things as part of the service offering and customers get an endpoint that they can use with their applications to store and retrieve data reliably. And with consistently high perform, >>You know, it's, you know, in the media, something has to be dead. Someone's the death of the iPhone, the death of this, nothing that really dies. Mongo DB has always been kind of like talked about, well, it doesn't scale on the high end. Of course, Oracle was saying that, I mean, all the, all the big database vendors were kind of throwing darts at, at Mongo, uh, DB, uh, but it kept scaling. Atlas is a whole nother. Could you just unpack that a little bit more? Why is it so important? Because scale is just, I mean, it's, it's horizontal, but it's also performant. >>Exactly. Right. So with, uh, Mongo DB's document access model that I've described already, you break some of the limitations that exist inside traditional relational databases. So, you know, they don't scale well, if you've got high concurrent and see of data access, and they're typically difficult and expensive to scale because you need to share data. Once you grow beyond individual cluster nodes, and you'll know that all relational databases suffer from these same kinds of issues with non relational systems, no SQL systems like MongoDB, you have to think a little bit more about design at the beginning. So designing database to cater for the different access patterns that you have, but in return for that upfront preparation, that design work, you get near limitless, scalability and performance will scale nearly linearly with that scalability as well. So very much more high performance, very much more simplicity for the developer as their database gets larger and their cluster gets larger to support it. >>Yeah. You know, Amazon web service has always had an a and D jazz. We talk to us all the time, every interview I've done with Swami and Matt wood or whoever on the team and executive levels always said the same thing. There's not one database to rule the world, right? Obvious you're talking about Oracle, but even within AWS customers, they're mixing and matching databases based on use cases. So in distributed environment, they're all working together. So, um, you guys fit nicely into that. So how does that, >>I think strategy slightly counterbalances that so, you know, they would say use the specific tool for the specific task that you have in hand. Yeah. What we try to focus on is creating the simple and most effective developer experience that we can, and then supporting different facets to the product in order to allow developers to different use cases. A really good example with something like MongoDB Atlas search. So we integrated Apache Luine into MongoDB Atlas. Customers can very simply apply Apache Luine search indexes to the data that they've got in MongoDB. And then they can interact with that search data using the same drivers as an API. Yeah, yeah. That they use for regular queries. So if you want to run search on your application data, you don't need a separate open search or elastic search cluster, just turn on MongoDB Atlas search and use that, that search facet. So it's interest and we have other capabilities that it's >>Vertically integrating inside within Mongo, >>Correct? Yes. That's better. Yeah. With the guy, all of creating a really simple and effective developer experience, boosting developer productivity and helping developers get more done in less time. >>You mentioned serverless earlier, what's the serverless angle with AWS when Mongo, >>Is there one? Yeah. So we have MongoDB serverless currently in preview, uh, has the same kind of characteristics that you would, or the characteristics that you would expect from a serverless data base. So consumption based model, you provision an endpoint and that will scale elastically in accordance with your usage and you get billed by consumption units so much like the serverless paradigm that we've seen delivered by AWS, the same kind of model for Mongo, DB, Atlas serverless. >>What, what attracted you to Mongo DBS? So you knew them before, or you moved over there. Um, what's going on there? What's the culture like right now? Oh, >>The culture's great. I mean, it's a much smaller company than AWS where I was before, you know, it's a very large organization. And one of the things that I really like about MongoDB is, as I've said earlier, we can serve the different use cases that a developer might have with a single product, with different aspects, to it, different facets to it. Uh, and it's a really great conversation to have with a, with a developer, with a developer customer, to be able to offer one thing that helps them solve five or six different problems that have traditionally been quite hard for them to wrestle with quite difficult for them to, to deal with. And then we've got this focus on developer experience through these driver packages that we have as well. So it's really great to have as a developer relations pro have that kind of tooling in my kit bag that can help developers become more effective. >>Talk about tooling, cuz you know, I always have, uh, kind of moments where I waffle between more. I love platforms, tools are being over overused, too many tools tool with the tool, you know, the expressions, but we're seeing from developers, the ones that don't want to go into the hood, we serverless plays beautifully. Yep. They want tools. They do. And, and the, the new engineering developers that are coming outta college and universities, they love tools. >>Yeah. And we actually have quite a few of those built into Mongo, DB Atlas. So inside Mongo, DB Atlas, we've got things like an index optimizer, which will suggest the best way that you might index your data for better perform months inside MongoDB, running on Atlas, we've got a data Explorer, which is much like another product that we've got called MongoDB compass that allows you to see and manipulate the data that you have stored within your database natively within the Atlas interface. Uh, and then we also have, uh, whole slew of different metrics, monitoring capabilities built into the platform as well. So these are aspects of Atlas that developers can take advantage of. And then over on the client side, visual studio code plugins. Yeah. So you can manipulate and operate with data directly inside visual studio code, which is obviously the most common and popular IDE out there today, as well as integration with things like infrastructure is code tools. So we support cloud formation for provisioning. We have CDK constructs inside. Yeah. The CDK construct library. We also have a lot of customers using Terraform to provision MongoDB across both AWS and other providers. So having that developer tooling of course is super important. Yeah. Aspect of the developer experience, trying to >>Build out deploying observability is a big one. How does that fit in? Cuz you knew need to talk and not only measure everything here, but talk to other systems. >>Yeah. So we recently announced a provider for Prometheus and Grafana. So we can emit metrics into those providers. Obviously CNCF projects, very common and popular inside customers that are running on Kubernetes. We've got a Kubernetes operator for MongoDB Atlas as well. Good. So you can provision MongoDB Atlas from within Kubernetes as well as having our own native metrics directly within Atlas as well. >>Ian you're crushing it. You got all the, the data, the fingertips. Are you gonna be at Cuban this year? Uh, >>I will be, but some of our team members will definitely be there. >>Yeah, we'll be at, uh, EU. The cube will be there. Great. Thanks for coming on. Appreciate the insight final world. I'll give you the last word. Tell the audience what's going on. What's at Mongo DB. What should they pay attention to? If they've used Mongo and are aware of it? What's the update. What's >>The so you should come to MongoDB world actually in New York at the beginning of June, June 7th, the ninth in the Javit center in New York. Gonna have our own show there. And of course we'd love to see you there. >>Okay. Cube comes here day two of eight, us summit, 2020, this Cub I'm John for your host. Stay with us more. Our coverage as day two winds down. Great coverage.

>>Hey, welcome back to live coverage in San Francisco, California, the cubes coverage of 80 west summit, 2022 here in SF and NYC New York city. Summit's coming up in the summer. We'll be there as well. Check it out. Okay. We've got a great guest here. C Bhan co and CEO RAI systems. Welcome to the cube, hot startup and growing company. And Kubernetes is great to see you. >>Yeah, John, thanks for having me. Appreciate it. >>Great to have you on. So Cubans coming up, you got cloud native here at AWS. You guys in the middle of it, take a minute to explain what your company does. Sure. >>So 50,000 enterprises are going to modernize in the next five to 10 years. They're all going to run into the exact same problem, which is they're gonna choose Kubernetes as the orchestra platform. And then they're gonna invest in building a platform essentially on top of Kubernetes so that their internal consumers, that developers can consume it. That requires a lot, a lot of effort. We, lot of people, a lot of time, a lot of effort, what we did was we thought about entire journey for Kubernetes operations that a team would go through and we package that as an offering. It's a SaaS product that you can consume. You can make it work with Amazon's Kubernetes, Azures Kubernetes, Googles, Kubernetes, upstream, Kubernetes, but then you can move significantly faster so that the goal of modernization can be achieved now versus two years more. >>What's the big, uh, opportunity that Kubernetes brings. And what are some of the pain points that are being removed or solved or blockers being removed and pain being reduced? Is it standing up Kubernetes? Is it running it in production? Is it the new revisions? I mean, honestly, it's huge. Yeah. What's the pain point. The customers that you guys solve. >>Yeah. Look, the, the paradox with Kubernetes is when it's working. It's awesome. It's great. And we can move it fast, but to get there, it's hard. Yeah. So simple things as a starting point, how do I provision my infrastructure repeatedly in the same way with the right blueprints? How do I make sure they all look the same? How do I make sure John can access certain things? And he cannot, how do I make sure the right policies are set up? How do I make sure consistent deployment is happening? Can I watch every we think, and I measure everything and we are not beyond basic things, right? Yeah. I need to back this up, you know, on and on. I need to do cost management. I need to network policy management. I need service management. You already built the team now. Right? Each of these is, is, is multiple people's jobs sometimes. Right? So it's really complicated. But again, everybody is investing. This is complexity. It's complexity. Yes. But people are investing in this because everybody understands now that once this is all working, the beauty, the, the P the pace at which you can run is exactly what we were promised five, six years ago when we were all told about modernization. Yeah. So the, when you get there, it's awesome. And we are helping companies get there significantly faster. Then they would've had, were they not working with a company? >>It's it really is a holy grail kind of orchestration layer if it works. And a lot of people, even myself, which a big fan of Kubernetes, caution, cautions over the oo problem, which is the clusters are up. I can't find talent to run them. They're too hard. Um, that's kind of in the back of people's minds and there's a lot of scar tissue around that. Uh, and then a little bit of open stack, you know, is it too hard, too hard? So the question is, is that what needs to happen to be successful with Kubernetes to make that go faster? So that's easy to deploy. Exactly. Yeah. And what what's your product do? Is it software open source? Yeah. What's, what's your product? >>The, the key here is repeatably usable automation. It's automation that it can use again and again, and it's flexible enough that it solves for many companies problem. You know, the funny thing is, and this is something that took me a while to figure out whether we have a financial services customer or an insurance company, or a healthcare company, or a high tech company, you know, what their problems are exactly the same. <laugh> when it comes to Kubernetes, it's all the same, right? So we figured out what it takes to build that automation in a repeatable fashion so that we could essentially sell it as a product. Our product is a SaaS product. Um, and once you have the right automation in place that you can ideally consume as a service, then now the beauty is that the people who are using it on a day to day basis, they don't need to be as expert at Kubernetes as today. Yeah. And that's the issue today? The issue is, you know, people, I've seen ads now where people say, you know, looking for Kubernetes expertise, 10 years, minimum experience, okay, that's ridiculous. Right. But you see these ads out there, right? Because people are rude about it, a tool like this makes it easy for you to take your existing skillset, existing resources and allow them to become Kubernetes. >>That's the key. I think that's the key in my mind is like hiring talent for these, I call DevOps glass eating projects, cuz it's hard. Yep. Some of this stuff's hard when you get down to the early stuff. And even in the hyperscalers, you look at the early hyperscalers, they were rolling their own and they were rock stars. And they were like the 1% of top developers. Right? Yep. And now you have general audiences who just want to code. Yep. They want abstractions. They want Kubernetes as a service. Uh, and they want all the benefits. And even if they could hire the Oddsly hiring the low level core people yeah. Is hard. Yeah. >>It takes time. Yeah. >>Absolutely. That's a core problem you guys solve. >>Absolutely. I think look, the, the one thing that every enterprise you think about is when the, the big companies, the hyperscale is that you mentioned that build this themselves when they us out 5, 6, 7, whatever years ago, when, you know, even some, some of them pre Kubernetes, it was a competitive advantage to roll this out because nobody else was doing it now as, as an enterprise who is trying to use software to move faster. Yeah. It's actually a competitive disadvantage because now you're building your own product. And now you're building this thing called Kubernetes that doesn't make any sense, focus your application, focus on your products, roll them out faster, and then essentially reuse the learnings from the market. Right. That's what we are doing. Really? What, what are we doing? We're taking the best practices of this industry and packaging that up into an easy to consume platform. That's awesome. That's it? >>Well, we'll see you in Cooper, Cuban, not Kubernetes contest in Valencia. Yep. Uh, and thanks for coming on. I know we didn't have a lot of time to drill into it, um, here, but great to meet you and the company. Final question as a co-founder what's your north star, you got, you got a company to run in. Bill got employees, you're managing and hiring inspiring. What's the north star for the company. >>So I'd say, I mean, the phrase that I, that, that I think about when, when you say north star is, is loyalty with urgency. >>So loyalty to whom? Yeah. It's to my team, right? My team comes first beyond before anything else. Right? And then my customers, right? My customers, many, many of our, our customers even now, right? We a four old company, they have my cell phone number and people call me at odd hours and I will show up. I will get people on a call. I will show up. Right. That's critical. But with urgency now my customer needs help. It needs to happen now. Not tomorrow, not next week. My team has heard me say this a thousand times, by the way, not tomorrow, not next week now. And this, if you do this in a startup, you will be successful. >>Yeah. I mean, you gotta make the market as the founder, inspiring people, product market fits huge. Yep. Getting that scale point. Yep. Where you're got the value proposition in position you're in mode to scale, you got visibility on unit economics. It's hard. Yep. It's super hard look. Good news is you get in a good area. Cloud native Kubernetes, automation, cloud, native modernization of apps. Super hot right now. Yeah. Big >>Time. Yeah. Look, I mean, you know, of course you, you want your teams to be topnotch. Right. But I gotta tell you there's a lot of luck and timing to everything. >>Exactly. >>Timing is in hindsight, nobody times anything. Right. So we have, time is perfect, but it's luck. Yeah. Right. We're very lucky. We're we have the right team. We're doing a great job. I think our customers are very happy. What we've rebuilt and uh, you know, look forward >>To Steve. You're humble. And you're a humble person. I can tell. I don't believe in luck. I think you make luck. I think luck is just part of the hustle, making those phone calls, doing those calls, doing the right things, grinding. And then when you get the shot, you're ready. Yeah. Yeah. So congratulations. Thanks for coming the queue. Appreciate it. Appreciate your time, sir. Nice to meet you coverage here in San Francisco, back with more day, two coverage. After this short break, stay with us.

>>Okay, welcome back everyone to the cubes coverage here in San Francisco, California of AWS summit, 2022. I'm John Farry host of the cube AWS summit in New York city. Coming up in the summer. We'll be there as well for live interviews there. Events are back and we're excited. I have a great guest here y'all you of CEO and co-founder and Juna security based outta Palo Alto. Great to have you coming on the queue. Appreciate it. Yeah. >>Thanks. >>Thanks for having, so tell us about what you guys are doing. You guys have a really cool cost of confidential computing. Take a minute to explain what the company does. >>Sure. So, uh, at high level confidential computing is the ability to take any workload, any piece of data, regardless of sensitive, it is and run it completely isolated, completely private, completely protected, essentially on any infrastructure, uh, and that enables organizations to take any, any workload and move it to UN you know, um, sensitive, potential sensitive locations, like the public cloud, where somebody else is managing your infrastructure. >>So basically the problem you solve is you provide security layer for workloads. >>Exactly. >>Exactly's also govern in security issues, but also just general hacking, >>Right? Oh, ex exactly. Essentially any, any organization having any type of sensitive information, think about, you know, financial services, think about healthcare, think about, you know, oil and gas that need to protect the data where they're gonna drill next. Any, any kind of organization that has sensitive information has that issue and needs to protect data in any environment they run in. >>So Amazon would be like, wait a minute. We're secure. What come on. >>Uh, actually AWS is, uh, is one of our partners and we we're actually building on top of, uh, a new technology that AWS, uh, built called, uh, nitro enclaves. And actually all the public clouds have built a technology like this. Uh, the reason why they've done this is to security and privacy are the number one. And number two reasons why people don't move more workloads to the public cloud. Mm-hmm <affirmative>. So what the public clouds have done is added this technology to be able to tell their customers one is we don't have any access to your data running on top of our infrastructure. And number two, be able to turn to the government and tell them, uh, during the case with the iPhone and, uh, the FBI or the FBI to apple asked him for data on the iPhone. Yeah. And apple said, we just can't, we don't have access to that data. This is exactly what the public clouds want to be able to do, turn to the government and tell them we just don't have access to our customer's data. >>Wow. That's gonna put a lot of pressure. So talk about the surface area of attacks. How has that changed? What do you guys, what's your role in that obviously this no perimeter anymore in the cloud, the security is dead. That's a huge issue. >>Yeah, of course. So, so I guess what we fit into this, as I mentioned, all the clouds added, uh, this technology, uh, what we fit in is very similar to what VMware did for virtualization, right? Virtualization was this extremely powerful technology that everybody knew was going to change the world. You wouldn't have the public cloud without virtualization. Uh, the problem was, it was very difficult to use very, very low level because it was a hardware technology. And then every, uh, vendor built a different technology. This is exactly the case now with confidential computing, every cloud added, uh, uh, a hardware level technology to go support this. But one it's very low level. It's very, very difficult to use. And every cloud added the different technology, which makes it even harder for organizations to go use. We added a softer stack exactly like VE VMware did for virtualization to make it super simple, to use and ubiquitous across the different clouds. >>How did you come up with the idea? What did this all come from? Were you scratching and inch and security? Did you have one of those things like, Hey, I can solve this problem. What's the origination story? Where did this all start? >>Yeah, it's actually, so I I've been in security for, you know, over 20 years now. Um, and I kept running into that same problem. Right. I, I was in the, I was actually in, um, unit 8,200, which is the really equivalent of the NSA. Uh, I was then, uh, in the private sector and I was, uh, a bunch of companies open DNS, Cisco, and, and I kept running into that same issue. And when you kind of peeled the layers of the onion of what the core security problem was, it always came back to how do you protect data while it's being used, which is essentially the core, the same sort of core problem, the confidential computing solves. Um, but there was never a solution. There was never a way to solve this. Uh, and, uh, above four years ago, my co-founder, uh, just finished his PhD at Stanford and he ran into, there's finally a way to do this. Finally, the CPU vendors have built something in, uh, the clouds are going to adopt this. This is going to allow you to one finally solve that huge problem that always existed. And, and number two, this allows you to kind of rearchitect security the right way, uh, because this has always been the core problem that people try to somehow mitigate never having a good solution. >>It's like putting a rapper around it, an envelope and saying secure. >>Exactly. So was this >>PhD working at Stanford in parallel to industry momentum at the same time Sarah Diply? Or was it kind of like, was he working with partners already in his program? >>Yeah, so he just, uh, this was something was happening and this is, uh, this has been going on for, well over a decade. It, it actually funny enough, it started with the, uh, with cell phones. I dunno if you ever thought, you know, what happens if you lose your phone, you have the biometric data, right? Your fingerprint or your face ID. Can somebody get that information out the phone if you lose it? And what the, the phone vendors have done is basically put techn, confidential computing technology to make sure that even if somebody gets physical access to your device, they're not going to be able to get access to that data. And what the, the evolution was is that the Intel AMD, the CPU vendors have realized, wait, this is a really, really great idea. Yeah, you should put it on the server side as well. >>And that started with Intel in 2015. So this has been an evolution, uh, and now essentially every, every one of the CPU vendors is now supporting this. You have Intel and R and AMD and video just announced, uh, their confidential, uh, uh, GPU solution, uh, all the clouds and I've adopted this. Uh, so my, my co-founder when he ran into this, this was as this was, uh, starting to, to happen. He got extremely excited, but he has noticed a big problem of everyone is coming up with different solutions. We're gonna need to build a layer, a software layer on top of this, uh, to, so >>You have, you have to get this to be de facto >>Exactly standard. >>Oh, how's that going? So Amazon's a partner, >>Amazon's a partner. Aw. Uh, Azure is a partner. Uh, we can run on top of essentially any, any one of the clouds out there >>They're enabling you to do that. Cuz they're they want to buy into security. >>Exactly. They want the benefit. Exactly. They want tell their customers, you can move anything to the cloud because we don't have any access to your data. This helps us, them essentially sell cloud >>A couple things around. Um, I want to ask about performance, but before I get to that, yep. It seems like this whole protective data thing has always been like a database thing. Not so much low level re resetting, if you will, it's almost a reset. It's not like just protect your data in the database. >>Oh yeah. Yes. It's different. Yes, exactly. It's funny because uh, you bring sort of the right exact right point. Really. You kind of think about where data can reside. There're essentially three locations. There's data at rest, which is essentially data in a database or file system. There's data in transit, which is data on the, you know, in the network. Yep. Uh, and then there's data use and the data and use piece is essentially when an application needs to process data, it has to decry it and load it completely in the clear, in memory in order to process it. Got it. And at that point, the data is not decade. This is why it's so hard for organizations to move data to the cloud or to run data and geographies where they're not, you know, they don't trust the government or don't trust the, the admins. >>So injecting some malware or vulnerability or attack in the workload while it's running is just another attack, vector. >>Exactly. Or just, or just stealing the data. If you, if you have access to the infrastructure, if you can run code, you can then just basically look in the memory and get all the data out of it. And, and to some extent, even the, the, the encryption keys you use for data, rest those keys, leaving the clear in memory. So even that hasn't been completely solved. Got it. Now that you have this component, you can finally solve, you know, solved our problem and protect the data regardless of where it resides. >>All right. So I gotta a performance question cause remember going, even back to the earlier encryption. Yeah. There's always overhead penalty. Yes. But cloud's a beautiful thing you can spend compute up and you're talking about now, the, the CPU vendors are kind of getting involved. >>Yes. Talk >>About the security, uh, how you mitigate that. Is it an issue? No issue. Why? Yeah, >>Actually, actually, uh, you talk about performance because I think this is a really, really great point. What's nice about this. Uh, and uh, this is why the, the, the, the sort of the benefit of the CPU vendors doing this performance has always essentially had two underlying issues. One is performance, as you mentioned. And the other one is ease of use. This is, this is sort of the, the piece we add to that. We make it super simple to use when you can take essentially any workload and run it securely on top of any, any one of these solutions and the performing thing, the, the heavy lifting is done by the hardware vendors themselves, which means there's a another, uh, chip next to the CPU that does all the heavy lifting encryption, which is very similar. I don't know if you remember the, uh, um, uh, the TLS, you know, the SL acceleration cards. Yeah. This was exactly the same thing. It was this, you know, chip outside the CPU. So it's not, uh, in the sort of the critical path that does all the heavy lifting. And this is what allowed, uh, TLS or HTB TTP HTTPS to become the default where you now protect every website. And this is sort of when security becomes transparent and there's no performance impact, like why, why would you use it for everything? >>It becomes a no brainer unless there's legacy baggage, right. >>In >>Dogma around use this approach, culture issue, or technical, right. Unwind those two, two things. So what's your a take on that? What's your react. Culture's easy. Just like, I think that's easy to fix. We want better security get on board or see you later. Exactly. Technical architecture could be an inhibitor. How do you see that is the blocker? How do you unwind that? How do you get that to >>Reset? So it's exactly the value that we bring to the table. We build a software stack to make it super simple. You don't need to, you know, you don't need to rewrite the application. You don't need to recompile, it's essentially security becoming a part of the infrastructure. You essentially have security as just a piece of the infrastructure that makes it super simple to get a no brainer. Yeah, exactly. The way, you know, TLS was it's. Yeah. We're a software vendor. >>All right. So how do I see it integrating with Amazon? It's gonna get into the chip level. They're enabling hooks for you. Exactly. That's how it works. >>So there's essentially the, uh, all the cloud vendors have enabled these technologies for Amazon it's yeah. It's essentially this hardware capability. We, we have access to it and we're a software layer on top of it to make it simple, similar to, again, what M VMware did for virtualization and what, um, some extent, this is what, uh, Microsoft has done for the CPU, what windows is right. Every time there's a new, really amazing hardware, hardware, uh, feature. You need a software sec on top of it to make it simple use. >>What's great about the cloud is, is that you kind of have that whole operating system mindset now being democratized across everything. Right. I mean, it's a systems thinking in software, right. With all the cap X of the cloud. Yes. And you're decoupled from it and you're riding on top of >>It. Exactly. >>It's an amazing opportunity as a co-founder or just if, if there was no cloud, how hard were this to be the two <laugh>, I mean, like almost impossible. Yep. So very cool. All right. Take a minute to explain what you guys are working on. How big is the company, what you guys are doing right now, you're hiring, you're looking for people funding, give a, give some, uh, give, give some, give a plug to the company. >>Sure. So, uh, we're, uh, we're a series B company, uh, lost, uh, raised 30 million from insight in the last round. Um, we're, uh, we're about 80 people right now. We're growing extremely aggressively. Um, mostly on the salsa and the cells go to market side just because of the demand that we're seeing in the market, but we're also growing on the engineering side. So again, if, uh, we're always happy to talk to >>Side about Palo Alto probably have remote teams, >>Uh, we're based in Palo Alto. So the, the, the, the sort of headquarters and most of the team is in Palo Alto, but yeah, we're very open to remote. We have now engineers in all across the us, and also outside the us as well, just because COVID made it sort of very easy to, to do >>That. Right. I mean, you got a good product, great idea, and a great opportunity. I mean, this is, you know, Dave LAN and I had at a VM world, I think it was like 2013. Now we're dating ourselves. <laugh> this is when we started covering AWS. Yep. He asked pat Gelsinger, it might have been 2015. Cause the CEO of VMware at the time. Yeah. Is security a Doover. Yep. And he's like, absolutely. And this is now happening. This is a security Mulligan, a redo over, this is what we need. Right. >>Exactly. And this is why, so, uh, we're part of a, uh, something called the confidential computing consortium, which essentially has all the large, all the, you know, the cloud vendors, the CPU vendors, VMware is a part of this as well. Basically the, this is sort of too big of a shift for these large organizations to ignore the, and uh, yeah. VMware is definitely going to have a, a part of >>This. Awesome. Well, congratulations. You guys are gonna probably be really huge or get bought out pretty quickly. <laugh> we're I think >>This, this is a huge, this is just a huge opportunity. We can become the VMware of security. So I think this is, you know, I'm hoping to stay independent. >>Yeah. Congratulations on a great venture. Love the idea. And again, every application should run this way. It's no, uh, if you can get that security built in yep. You gotta shield. Right. You wrap it up, probe it anywhere exactly made the best cloud >>Win. Exactly. Right. Exactly. >>And that's, what's gonna happen. That's >>That's >>Why I love the Silicon angle of Amazon Silicon play. Yes. As that Silicon gets better. >>Yes. >>It only helps this, these kinds of use cases. Right? >>Exactly. We, we, again, we, we leverage, we leverage these technologies and to some extent, this is, this is actually part of the, the value we talk to customers about, because this is sort of the cutting edge of technology and security. And this keeps evolving. As, as I mentioned in video, just announced their confidential GPS. We provide this layer on top of it where organizations don't have to go and kind of rebuild every application as this evolves and just use our people >>Who know me in the cube know I'm a Hawk when it comes to cybersecurity. I think the red line is people operating below the red line. And, and why should companies have to provision their own militia? Exactly. This is essentially the shield they can put up. Exactly. And not rely on the government who just know what they're doing. Exactly. >>So get exactly security should be easy. Should be, should be us everywhere. I >>Should you get a lot of banking customers, FinTech customers coming on board. Exactly. Right. Outta the gate. Yeah. Thanks for coming on the queue. Yeah. Appreciate. Thank you. Live coverage here. San Francisco, California. I'm John farrier with the cube. We'll be right back with more after this short break.

(gentle melody) >> Welcome back to theCUBE's live coverage of AWS Summit in San Francisco, California. Events are back. AWS Summit in New York City this summer, theCUBE will be there as well. Check us out there. I'm glad to have events back. It's great to have of everyone here. I'm John Furrier, host of theCUBE. Dr. Matt Wood is with me, CUBE alumni, now VP of Business Analytics Division of AWS. Matt, great to see you. >> Thank you, John. It's great to be here. I appreciate it. >> I always call you Dr. Matt Wood because Andy Jackson always says, "Dr. Matt, we would introduce you on the arena." (Matt laughs) >> Matt: The one and only. >> The one and only, Dr. Matt Wood. >> In joke, I love it. (laughs) >> Andy style. (Matt laughs) I think you had walk up music too. >> Yes, we all have our own personalized walk up music. >> So talk about your new role, not a new role, but you're running the analytics business for AWS. What does that consist of right now? >> Sure. So I work. I've got what I consider to be one of the best jobs in the world. I get to work with our customers and the teams at AWS to build the analytics services that millions of our customers use to slice dice, pivot, better understand their data, look at how they can use that data for reporting, looking backwards. And also look at how they can use that data looking forward, so predictive analytics and machine learning. So whether it is slicing and dicing in the lower level of Hadoop and the big data engines, or whether you're doing ETL with Glue, or whether you're visualizing the data in QuickSight or building your models in SageMaker. I got my fingers in a lot of pies. >> One of the benefits of having CUBE coverage with AWS since 2013 is watching the progression. You were on theCUBE that first year we were at Reinvent in 2013, and look at how machine learning just exploded onto the scene. You were involved in that from day one. It's still day one, as you guys say. What's the big thing now? Look at just what happened. Machine learning comes in and then a slew of services come in. You've got SageMaker, became a hot seller right out of the gate. The database stuff was kicking butt. So all this is now booming. That was a real generational change over for database. What's the perspective? What's your perspective on that's evolved? >> I think it's a really good point. I totally agree. I think for machine learning, there's sort of a Renaissance in machine learning and the application of machine learning. Machine learning as a technology has been around for 50 years, let's say. But to do machine learning right, you need like a lot of data. The data needs to be high quality. You need a lot of compute to be able to train those models and you have to be able to evaluate what those models mean as you apply them to real world problems. And so the cloud really removed a lot of the constraints. Finally, customers had all of the data that they needed. We gave them services to be able to label that data in a high quality way. There's all the compute you need to be able to train the models. And so where you go? And so the cloud really enabled this Renaissance with machine learning. And we're seeing honestly a similar Renaissance with data and analytics. If you look back five to ten years, analytics was something you did in batch, your data warehouse ran an analysis to do reconciliation at the end of the month, and that was it. (John laughs) And so that's when you needed it. But today, if your Redshift cluster isn't available, Uber drivers don't turn up, DoorDash deliveries don't get made. Analytics is now central to virtually every business, and it is central to virtually every business's digital transformation. And being able to take that data from a variety of sources, be able to query it with high performance, to be able to actually then start to augment that data with real information, which usually comes from technical experts and domain experts to form wisdom and information from raw data. That's kind of what most organizations are trying to do when they kind of go through this analytics journey. >> It's interesting. Dave Velanta and I always talk on theCUBE about the future. And you look back, the things we're talking about six years ago are actually happening now. And it's not hyped up statement to say digital transformation is actually happening now. And there's also times when we bang our fists on the table saying, say, "I really think this is so important." And David says, "John, you're going to die on that hill." (Matt laughs) And so I'm excited that this year, for the first time, I didn't die on that hill. I've been saying- >> Do all right. >> Data as code is the next infrastructure as code. And Dave's like, "What do you mean by that?" We're talking about how data gets... And it's happening. So we just had an event on our AWS startups.com site, a showcase for startups, and the theme was data as code. And interesting new trends emerging really clearly, the role of a data engineer, right? Like an SRE, what an SRE did for cloud, you have a new data engineering role because of the developer onboarding is massively increasing, exponentially, new developers. Data science scientists are growing, but the pipelining and managing and engineering as a system, almost like an operating system. >> Kind of as a discipline. >> So what's your reaction to that about this data engineer, data as code? Because if you have horizontally scalable data, you've got to be open, that's hard (laughs), okay? And you got to silo the data that needs to be siloed for compliance and reason. So that's a big policy around that. So what's your reaction to data's code and the data engineering phenomenon? >> It's a really good point. I think with any technology project inside of an organization, success with analytics or machine learning, it's kind of 50% technology and then 50% cultural. And you have often domain experts. Those could be physicians or drug design experts, or they could be financial experts or whoever they might be, got deep domain expertise, and then you've got technical implementation teams. And there's kind of a natural, often repulsive force. I don't mean that rudely, but they just don't talk the same language. And so the more complex a domain and the more complex the technology, the stronger their repulsive force. And it can become very difficult for domain experts to work closely with the technical experts to be able to actually get business decisions made. And so what data engineering does and data engineering is, in some cases a team, or it can be a role that you play. It's really allowing those two disciplines to speak the same language. You can think of it as plumbing, but I think of it as like a bridge. It's a bridge between the technical implementation and the domain experts, and that requires a very disparate range of skills. You've got to understand about statistics, you've got to understand about the implementation, you got to understand about the data, you got to understand about the domain. And if you can put all of that together, that data engineering discipline can be incredibly transformative for an organization because it builds the bridge between those two groups. >> I was advising some young computer science students at the sophomore, junior level just a couple of weeks ago, and I told them I would ask someone at Amazon this question. So I'll ask you, >> Matt: Okay. since you've been in the middle of it for years, they were asking me, and I was trying to mentor them on how do you become a data engineer, from a practical standpoint? Courseware, projects to work on, how to think, not just coding Python, because everyone's coding in Python, but what else can they do? So I was trying to help them. I didn't really know the answer myself. I was just trying to kind of help figure it out with them. So what is the answer, in your opinion, or the thoughts around advice to young students who want to be data engineers? Because data scientists is pretty clear on what that is. You use tools, you make visualizations, you manage data, you get answers and insights and then apply that to the business. That's an application. That's not the standing up a stack or managing the infrastructure. So what does that coding look like? What would your advice be to folks getting into a data engineering role? >> Yeah, I think if you believe this, what I said earlier about 50% technology, 50 % culture, the number one technology to learn as a data engineer is the tools in the cloud which allow you to aggregate data from virtually any source into something which is incrementally more valuable for the organization. That's really what data engineering is all about. It's about taking from multiple sources. Some people call them silos, but silos indicates that the storage is kind of fungible or undifferentiated. That's really not the case. Success requires you to have really purpose built, well crafted, high performance, low cost engines for all of your data. So understanding those tools and understanding how to use them, that's probably the most important technical piece. Python and programming and statistics go along with that, I think. And then the most important cultural part, I think is... It's just curiosity. You want to be able to, as a data engineer, you want to have a natural curiosity that drives you to seek the truth inside an organization, seek the truth of a particular problem, and to be able to engage because probably you're going to some choice as you go through your career about which domain you end up in. Maybe you're really passionate about healthcare, or you're really just passionate about transportation or media, whatever it might be. And you can allow that to drive a certain amount of curiosity. But within those roles, the domains are so broad you kind of got to allow your curiosity to develop and lead you to ask the right questions and engage in the right way with your teams, because you can have all the technical skills in the world. But if you're not able to help the team's truth seek through that curiosity, you simply won't be successful. >> We just had a guest, 20 year old founder, Johnny Dallas who was 16 when he worked at Amazon. Youngest engineer- >> Johnny Dallas is a great name, by the way. (both chuckle) >> It's his real name. It sounds like a football player. >> That's awesome. >> Rock star. Johnny CUBE, it's me. But he's young and he was saying... His advice was just do projects. >> Matt: And get hands on. Yeah. >> And I was saying, hey, I came from the old days where you get to stand stuff up and you hugged on for the assets because you didn't want to kill the project because you spent all this money. And he's like, yeah, with cloud you can shut it down. If you do a project that's not working and you get bad data no one's adopting it or you don't like it anymore, you shut it down, just something else. >> Yeah, totally. >> Instantly abandon it and move on to something new. That's a progression. >> Totally! The blast radius of decisions is just way reduced. We talk a lot about in the old world, trying to find the resources and get the funding is like, all right, I want to try out this kind of random idea that could be a big deal for the organization. I need $50 million and a new data center. You're not going to get anywhere. >> And you do a proposal, working backwards, documents all kinds of stuff. >> All that sort of stuff. >> Jump your hoops. >> So all of that is gone. But we sometimes forget that a big part of that is just the prototyping and the experimentation and the limited blast radius in terms of cost, and honestly, the most important thing is time, just being able to jump in there, fingers on keyboards, just try this stuff out. And that's why at AWS, we have... Part of the reason we have so many services, because we want, when you get into AWS, we want the whole toolbox to be available to every developer. And so as your ideas develop, you may want to jump from data that you have that's already in a database to doing realtime data. And then you have the tools there. And when you want to get into real time data, you don't just have kinesis, you have real time analytics, and you can run SQL against that data. The capabilities and the breadth really matter when it comes to prototyping. >> That's the culture piece, because what was once a dysfunctional behavior. I'm going to go off the reservation and try something behind my boss' back, now is a side hustle or fun project. So for fun, you can just code something. >> Yeah, totally. I remember my first Hadoop projects. I found almost literally a decommissioned set of servers in the data center that no one was using. They were super old. They're about to be literally turned off. And I managed to convince the team to leave them on for me for another month. And I installed Hadoop on them and got them going. That just seems crazy to me now that I had to go and convince anybody not to turn these servers off. But what it was like when you- >> That's when you came up with Elastic MapReduce because you said this is too hard, we got to make it easier. >> Basically yes. (John laughs) I was installing Hadoop version Beta 9.9 or whatever. It was like, this is really hard. >> We got to make it simpler. All right, good stuff. I love the walk down memory Lane. And also your advice. Great stuff. I think culture is huge. That's why I like Adam's keynote at Reinvent, Adam Selipsky talk about Pathfinders and trailblazers, because that's a blast radius impact when you can actually have innovation organically just come from anywhere. That's totally cool. >> Matt: Totally cool. >> All right, let's get into the product. Serverless has been hot. We hear a lot of EKS is hot. Containers are booming. Kubernetes is getting adopted, still a lot of work to do there. Cloud native developers are booming. Serverless, Lambda. How does that impact the analytics piece? Can you share the hot products around how that translates? >> Absolutely, yeah. >> Aurora, SageMaker. >> Yeah, I think it's... If you look at kind of the evolution and what customers are asking for, they don't just want low cost. They don't just want this broad set of services. They don't just want those services to have deep capabilities. They want those services to have as low an operating cost over time as possible. So we kind of really got it down. We got built a lot of muscle, a lot of services about getting up and running and experimenting and prototyping and turning things off and turning them on and turning them off. And that's all great. But actually, you really only in most projects start something once and then stop something once, and maybe there's an hour in between or maybe there's a year. But the real expense in terms of time and operations and complexity is sometimes in that running cost. And so we've heard very loudly and clearly from customers that running cost is just undifferentiated to them. And they want to spend more time on their work. And in analytics, that is slicing the data, pivoting the data, combining the data, labeling the data, training their models, running inference against their models, and less time doing the operational pieces. >> Is that why the service focuses there? >> Yeah, absolutely. It dramatically reduces the skill required to run these workloads of any scale. And it dramatically reduces the undifferentiated heavy lifting because you get to focus more of the time that you would have spent on the operations on the actual work that you want to get done. And so if you look at something just like Redshift Serverless, that we launched a Reinvent, we have a lot of customers that want to run the cluster, and they want to get into the weeds where there is benefit. We have a lot of customers that say there's no benefit for me, I just want to do the analytics. So you run the operational piece, you're the experts. We run 60 million instant startups every single day. We do this a lot. >> John: Exactly. We understand the operations- >> I just want the answers. Come on. >> So just give me the answers or just give me the notebook or just give me the inference prediction. Today, for example, we announced Serverless Inference. So now once you've trained your machine learning model, just run a few lines of code or you just click a few buttons and then you got an inference endpoint that you do not have to manage. And whether you're doing one query against that end point per hour or you're doing 10 million, we'll just scale it on the back end. I know we got not a lot of time left, but I want to get your reaction on this. One of the things about the data lakes not being data swamps has been, from what I've been reporting and hearing from customers, is that they want to retrain their machine learning algorithm. They need that data, they need the real time data, and they need the time series data. Even though the time has passed, they got to store in the data lake. So now the data lake's main function is being reusing the data to actually retrain. It works properly. So a lot of post mortems turn into actually business improvements to make the machine learnings smarter, faster. Do you see that same way? Do you see it the same way? >> Yeah, I think it's really interesting >> Or is that just... >> No, I think it's totally interesting because it's convenient to kind of think of analytics as a very clear progression from point A to point B. But really, you're navigating terrain for which you do not have a map, and you need a lot of help to navigate that terrain. And so having these services in place, not having to run the operations of those services, being able to have those services be secure and well governed. And we added PII detection today. It's something you can do automatically, to be able to use any unstructured data, run queries against that unstructured data. So today we added text queries. So you can just say, well, you can scan a badge, for example, and say, well, what's the name on this badge? And you don't have to identify where it is. We'll do all of that work for you. It's more like a branch than it is just a normal A to B path, a linear path. And that includes loops backwards. And sometimes you've got to get the results and use those to make improvements further upstream. And sometimes you've got to use those... And when you're downstream, it will be like, "Ah, I remember that." And you come back and bring it all together. >> Awesome. >> So it's a wonderful world for sure. >> Dr. Matt, we're here in theCUBE. Just take the last word and give the update while you're here what's the big news happening that you're announcing here at Summit in San Francisco, California, and update on the business analytics group. >> Yeah, we did a lot of announcements in the keynote. I encourage everyone to take a look at, that this morning with Swami. One of the ones I'm most excited about is the opportunity to be able to take dashboards, visualizations. We're all used to using these things. We see them in our business intelligence tools, all over the place. However, what we've heard from customers is like, yes, I want those analytics, I want that visualization, I want it to be up to date, but I don't actually want to have to go from my tools where I'm actually doing my work to another separate tool to be able to look at that information. And so today we announced 1-click public embedding for QuickSight dashboard. So today you can literally as easily as embedding a YouTube video, you can take a dashboard that you've built inside QuickSight, cut and paste the HTML, paste it into your application and that's it. That's what you have to do. It takes seconds. >> And it gets updated in real time. >> Updated in real time. It's interactive. You can do everything that you would normally do. You can brand it, there's no power by QuickSight button or anything like that. You can change the colors, fit in perfectly with your application. So that's an incredibly powerful way of being able to take an analytics capability that today sits inside its own little fiefdom and put it just everywhere. Very transformative. >> Awesome. And the business is going well. You got the Serverless detail win for you there. Good stuff. Dr. Matt Wood, thank you for coming on theCUBE. >> Anytime. Thank you. >> Okay, this is theCUBE's coverage of AWS Summit 2022 in San Francisco, California. I'm John Furrier, host of theCUBE. Stay with us for more coverage of day two after this short break. (gentle music)

>>Hello, and welcome back to the live cube coverage here in San Francisco, California, the cube live coverage. Two days, day two of a summit 2022, a summit New York city coming up in the summer. We'll be there as well. Events are back. I'm the host, John fur, the cube got great guest here, Johnny Dallas with Ze. Um, here's on the cube. We're gonna talk about his background. Uh, little trivia here. He was the youngest engineer ever worked at Amazon at the age. 17 had to get escorted into reinvent in Vegas cause he was underage <laugh> with security, all good stories. Now the CEO of gonna called Ze know DevOps kind of focus, managed service, a lot of cool stuff, John, welcome to the cube. >>Thanks John. Great. >>So tell a story. You were the youngest engineer at AWS. >>I was, yes. So I used to work at a company called Bebo. I got started very young. I started working when I was about 14, um, kind of as a software engineer. And when I, uh, was about 16, I graduated out of high school early. Um, worked at this company, Bebo running all of the DevOps at that company. Um, I went to reinvent in about 2018 to give a talk about some of the DevOps software I wrote at that company. Um, but you know, as many of those things are probably familiar with reinvent happens in a casino and I was 16, so I was not able to actually go into the casino on my own <laugh> um, so I'd have <inaudible> security as well as C security escort me in to give my talk. >>Did Andy jazzy, was he aware of this? >>Um, you know, that's a great question. I don't know. <laugh> >>I'll ask him great story. So obviously you started a young age. I mean, it's so cool to see you jump right in. I mean, I mean, you never grew up with the old school that I used to grew up in loading package software, loading it onto the server, deploying it, plugging the cables in, I mean you just rocking and rolling with DevOps as you look back now what's the big generational shift because now you got the Z generation coming in, millennials are in the workforce. It's changing. Like no one's putting package software on servers. >>Yeah, no, I mean the tools keep getting better, right? We, we keep creating more abstractions that make it easier and easier. When I, when I started doing DevOps, I could go straight into E two APIs. I had APIs from the get go and you know, my background was, I was a software engineer. I never went through like the CIS admin stack. I, I never had to, like you said, rack servers, myself. I was immediately able to scale to I, I was managing, I think 2,500 concurrent servers across every Ables region through software. It was a fundamental shift. >>Did you know what an SRE was at that time? Uh, you were kind of an SRE on >>Yeah, I was basically our first SRE, um, familiar with the, with the phrasing, but really thought of myself as a software engineer who knows cloud APIs, not a SRE. >>All right. So let's talk about what's what's going on now, as you look at the landscape today, what's the coolest thing that's going on in your mind and cloud? >>Yeah, I think the, I think the coolest thing is, you know, we're seeing the next layer of those abstraction tools exist and that's what we're doing with Ze is we've basically gone and we've, we're building an app platform that deploys onto your cloud. So if you're familiar with something like Carku, um, where you just click a GitHub repo, uh, we actually make it that easy. You click a GI hub repo and it'll deploy on a AWS using Al AWS tools. >>So, right. So this is Z. This is the company. Yes. How old's the company >>About a year and a half old now. >>Right. So explain what it does. >>Yeah. So we make it really easy for any software engineer to deploy on a AWS. Um, that's not SREs. These are the actual application engineers doing the business logic. Mm-hmm <affirmative> they don't really want to think about Yamo. They don't really want to configure everything super deeply. Um, they want to say, run this API on a AWS in the best way possible. We've encoded all the best practices into software and we set it up for you. >>Yeah. So I think the problem you're solving is, is that there's a lot of want to be DevOps engineers. And then they realize, oh shit, I don't wanna do this. Yeah. And the people want to do it. They loved under the hood. Right. People love that infrastructure, but the average developer needs to actually be as agile on scale. So that seems to be the problem you solve. Right? Yeah. >>We, we, we give way more productivity to each individual engineer, you know? >>All right. So let me ask you a question. So let me just say, I'm a developer. Cool. I built this new app. It's a streaming app or whatever. I'm making it up cube here, but let's just say I deploy it. I need your service. But what happens about when my customers say, Hey, what's your SLA? The CDN went down from this it's flaky. Does Amazon have? So how do you handle all that SLA reporting that Amazon provides? Cause they do a good job with sock reports all through the console. But as you start getting into DevOps and sell your app, mm-hmm <affirmative> you have customer issues. You, how do you view that? Yeah, >>Well, I, I think you make a great point of AWS has all this stuff already. AWS has SLAs. AWS has contract. Aw, has a lot of the tools that are expected. Um, so we don't have to reinvent the wheel here. What we do is we help people get to those SLAs more easily. So, Hey, this is a AWS SLA as a default. Um, Hey, we'll configure your services. This is what you can expect here. Um, but we can really leverage AWS reli ability of you don't have to trust us. You have to trust S and trust that the setup is good there. >>Do you handle all the recovery or mitigation between, uh, identification say downtime for instance, oh, the servers not 99% downtime, uh, went down for an hour, say something's going on? And is there a service dashboard? How does it get what's the remedy? Do you have, how does all that work? >>Yeah, so we have some built in remediation. You know, we, we basically say we're gonna do as much as we can to keep your endpoint up 24 7 mm-hmm <affirmative>. If it's something in our control, we'll do it. If it's a disc failure, that's on us. If you push bad code, we won't put out that new version until it's working. Um, so we do a lot to make sure that your endpoint stays up, um, and then alert you if there's a problem that we can't fix. So cool. Hey, S has some downtime, this thing's going on. You need to do this action. Um, we'll let you know. >>All right. So what do you do for fun? >>Yeah, so, uh, for, for fun, um, a lot of side projects. <laugh>, uh, >>What's your side hustle right now. You got going on >>The, uh, it's a lot of schools playing >>With serverless. >>Yeah. Playing with a lot of serverless stuff. Um, I think there's a lot of really cool Lam stuff as well, going on right now. Um, I love tools is, is the truest answer is I love building something that I can give to somebody else. And they're suddenly twice as productive because of it. Um, >>That's a good feeling, isn't it? Oh >>Yeah. There's nothing >>Like that. Tools versus platforms. Mm-hmm, <affirmative>, you know, the expression, too many tools in the tool, she becomes, you know, tools for all. And then ultimately tools become platforms. What's your view on that? Because if a good tool works and starts to get traction, you need to either add more tools or start building a platform platform versus tool. What's your, what's your view on our reaction to that kind of concept debate? >>Yeah, it's a good question. Uh, we we've basically started as like a, a platform. First of we've really focused on these, uh, developers who don't wanna get deep into the DevOps. And so we've done all of the piece of the stacks. We do C I C D management. We do container orchestration, we do monitoring. Um, and now we're, spliting those up into individual tools so they can be used awesome in conjunction more. >>Right. So what are some of the use cases that you see for your service? It's DevOps basically nano service DevOps for people on a DevOps team. Do clients have a DevOps person and then one person, two people what's the requirements to run >>Z? Yeah. So we we've got teams, um, from no DevOps is kind of when they start and then we've had teams grow up to about, uh, five, 10 man DevOps teams. Mm-hmm <affirmative> um, so, you know, as more structured people come in, because we're in your cloud, you're able to go in and configure it on top you're we can't block you. Uh, you wanna use some new AOL service. You're welcome to use that alongside the stack that we deploy for >>You. How many customers do you have now? >>So we've got about 40 companies that are using us for all of their infrastructure, um, kind of across the board, um, as well as >>What's the pricing model. >>Uh, so our pricing model is we, we charge basically similar to an engineer salary. So we charge, uh, a monthly rate. We have plans at 300 bucks a month, a thousand bucks a month, and then enterprise plan for based >>On the requirement scale. Yeah. You know, so back into the people cost, you must offer her discounts, not a fully loaded thing, is it? >>Yeah. There's a discounts kind of at scale, >>Then you pass through the Amazon bill. >>Yeah. So our customers actually pay for the Amazon bill themselves. Oh. So >>They have their own >>Account. There's no margin on top. You're linking your Aless account in, um, it, which is huge because we can, we are now able to help our customers get better deals with Amazon. Um, got it. We're incentivized on their team to drive your cost down. >>And what's your unit main unit of economics software scale. >>Yeah. Um, yeah, so we, we think of things as projects. How many services do you have to deploy as that scales up? Um, awesome. >>All right. You're 20 years old now you not even can't even drink legally. <laugh> what are you gonna do when you're 30? We're gonna be there. >>Well, we're, uh, we're making it better. And >>The better, the old guy on the cube here. >><laugh> I think, uh, I think we're seeing a big shift of, um, you know, we've got these major clouds. AWS is obviously the biggest cloud. Um, and it's constantly coming out with new services. Yeah. But we're starting to see other clouds have built many of the common services. So Kubernetes is a great example. It exists across all the clouds. Um, and we're starting to see new platforms come up on top that allow you to leverage tools from multiple clouds. At the same time. Many of our customers actually have AWS as their primary cloud and they'll have secondary clouds or they'll pull features from other clouds into AWS, um, through our software. I think that I'm very excited by that. And I, uh, expect to be working on that when I'm 30. Awesome. >>Well, you gonna have a good future. I gotta ask you this question cuz uh, you know, I've always, I was a computer science undergraduate in the, in the eighties and um, computer science back then was hardcore, mostly systems OS stuff, uh, database compiler. Um, now there's so much compi, right? So mm-hmm <affirmative> how do you look at the high school college curriculum experience slash folks who are nerding out on computer science? It's not one or two things much. You've got a lot of, a lot of things. I mean, look at Python, data engineering, merging as a huge skill. What's it? What's it like for college kids now and high school kids? What, what do you think they should be doing if you had to give advice to your 16 year old self back a few years ago now in college? Um, I mean Python's not a great language, but it's super effective for coding and the data's really relevant, but it's you got other language opportunities, you got tools to build. So you got a whole culture of young builders out there. What should, what should people gravitate to in your opinion stay away from yeah. Or >>Stay away from that's a good question. I, I think that first of all, you're very right of the, the amount of developers is increasing so quickly. Um, and so we see more specialization. That's why we also see, you know, these SREs that are different than typical application engineering. You get more specialization in job roles. Um, I think if, what I'd say to my 16 year old self is do projects, um, the, I learned most of my, what I've learned just on the job or online trying things, playing with different technologies, actually getting stuff out into the world, um, way more useful than what you'll learn in kind of a college classroom. I think classrooms great to, uh, get a basis, but you need to go out and experiment actually try things. >>You know? I think that's great advice. In fact, I would just say from my experience of doing all the hard stuff and cloud is so great for just saying, okay, I'm done, I'm abandoning the project. Move on. Yeah. Because you know, it's not gonna work in the old days. You have to build this data center. I bought all this certain, you know, people hang on to the old, you know, project and try to force it out there. >>You can launch a project, >>Can see gratification, it ain't working <laugh> or this is shut it down and then move on to something new. >>Yeah, exactly. Instantly you should be able to do that much more quickly. Right. >>So you're saying get those projects and don't be afraid to shut it down. Mm-hmm <affirmative> that? Do you agree with that? >>Yeah. I think it's ex experiment. Um, you're probably not gonna hit it rich on the first one. It's probably not gonna be that idea is DJing me this idea. So don't be afraid to get rid of things and just try over and over again. It's it's number of reps that a win. >>I was commenting online. Elon Musk was gonna buy Twitter, that whole Twitter thing. And, and, and someone said, Hey, you know, what's the, I go look at the product group at Twitter's been so messed up because they actually did get it right on the first time <laugh> and, and became such a great product. They could never change it because people would freak out and the utility of Twitter. I mean, they gotta add some things, the added button and we all know what they need to add, but the product, it was just like this internal dysfunction, the product team, what are we gonna work on? Don't change the product so that you kind of have there's opportunities out there where you might get the lucky strike, right. Outta the gate. Yeah. Right. You don't know, >>It's almost a curse too. It's you're not gonna Twitter. You're not gonna hit a rich second time too. So yeah. >><laugh> Johnny Dallas. Thanks for coming on the cube. Really appreciate it. Give a plug for your company. Um, take a minute to explain what you're working on, what you're looking for. You're hiring funding. Customers. Just give a plug, uh, last minute and have the last word. >>Yeah. So, um, John Dallas from Ze, if you, uh, need any help with your DevOps, if you're a early startup, you don't have DevOps team, um, or you're trying to deploy across clouds, check us out ze.com. Um, we are actively hiring. So if you are a software engineer excited about tools and cloud, or you're interested in helping getting this message out there, hit me up. Um, find a Z. >>Yeah. LinkedIn Twitter handle GitHub handle. >>Yeah. I'm the only Johnny on a LinkedIn and GitHub and underscore Johnny Dallas underscore on Twitter. Right? Um, >>Johnny Dallas, the youngest engineer working at Amazon. Um, now 20 we're on great new project here. The cube builders are all young. They're growing in to the business. They got cloud at their, at their back it's, uh, tailwind. I wish I was 20. Again, this is a cue. I'm John for your host. Thanks for watching. >>Thanks.

(upbeat music) >> Live on the floor in San Francisco for AWS Summit. I'm John Furrier, host of theCUBE. Here for the next two days getting all the action back in person. We're at AWS re:Invent, a few months ago. Now we're back, events are coming back and we're happy to be here with theCUBE. Bring all the action, also virtual, we have a hybrid cube. Check out theCUBE.net, siliconangle.com for all the coverage. After the event we've got a great guest ticking off here. Matthew Park, Director of Solutions Architecture with Innovation Solutions, the booth is right here. Matthew, welcome to theCUBE. >> Thank you very much, I'm glad to be here. >> So we're back in person. You're from Tennessee, we were chatting before you came on camera. It's great that be back to events. >> It's amazing, this is the first summit I've been to in what two, three years. >> It's awesome, we'll be at the AWS Summit in New York as well. A lot of developers and the big story this year is as developers look at cloud going, distributed computing you got on-premises, you got public cloud, you got the edge. Essentially the cloud operations is running everything, Dev sec Ops, everyone kind of sees that, you got containers, you got Kubernetes, you got cloud native. So the game is pretty much laid out, and the edge is with the action is. You guys are number one premier partner at SMB for edge. >> That's right. >> Tell us about what you guys doing at innovative and what you do. >> That's right, so I'm the director of solutions architecture. Me and my team are responsible for building out the solutions that are around especially the edge public cloud. For us edge is anything outside of an AWS availability zone. We are deploying that in countries that don't have AWS infrastructure in region. They don't have it-- >> Give an example. >> Example would be Panama. We have a customer there that needs to deploy some financial tech, data and compute is legally required to be in Panama but they love AWS, and they want to deploy AWS services in region. So they've taken EKS anywhere. We've put storage gateway and snowball in region, inside the country and they're running their FinTech on top of AWS services inside Panama. >> You know, what's interesting, Matthew is that we've been covering AWS since 2013 with theCUBE about their events, and we watched the progression. Andy Jassy was in charge and became the CEO. Now Adam Slepsky is in charge, but the edge has always been that thing they've been trying to avoid. I don't want to say trying to avoid. Of course Amazon listens to customers, they work backwards from the customers, we all know that. But the real issue is they're bread and butters, EC2 and S3. And then now they got tons of services, and the cloud is obviously successful, and we're seeing that. But the edge brings up a whole nother level. >> It does. >> Computing. >> It does. >> That's not set centralized in the public cloud. Now they got regions, so what is the issue with the edge? What's driving the behavior? Outpost came out as a reaction to competitive threats and also customer momentum around OT, operational technologies and IT merging. We see with the data at the edge, you got 5G, so it's pretty obvious, but there was a slow transition. What was the driver for the edge? What's the driver now for edge action for AWS? >> Data is the driver for the edge. Data has gravity, right? And it's pulling compute back to where the customer's generating that data and that's happening over and over again. You said it best Outpost was a reaction to a competitive situation. Whereas today we have over 15 AWS edge services and those are all reactions to things that customers need inside their data centers, on location or in the field like with media companies. >> Outpost is interesting, we always used to rip on theCUBE 'cause it's basically Amazon in a box pushed in the data center, running native, all this stuff. But now cloud native operations are becoming the standard. You're starting to see some standard, Deepak Singh's group is doing some amazing work with opensource, Raul's team on the AI side. Obviously you got Swam who's giving the keynote tomorrow. You got the big AI machine learning big part of that edge. Now you can say, okay, Outpost, is it relevant today? In other words, did Outpost do its job? 'Cause EKS anywhere seems to be getting a lot of momentum. You see local zones, the regions are kicking ass for Amazon. This edge piece is evolving. What's your take on EKS anywhere versus say Outpost? >> Yeah, I think Outpost did its job. It made customers that were looking at Outpost really consider, do I want to invest in this hardware? Do I want to have this Outpost in my data center? Do I want to manage this over the long term? A lot of those customers just transitioned to the public cloud. They went into AWS proper. Some of those customers stayed on prem because they did have use cases that were not a good fit for Outposts, they weren't a good fit in the customer's mind for the public AWS cloud inside an availability zone. Now what's happening is as AWS is pushing these services out and saying, we're going to meet you where you are with 5G. We're going to meet you where you are with wavelength. We're going to meet you where you are with EKS anywhere. I think it has really reduced the amount of times that we have conversations about Outposts and it's really increased, we can deploy fast. We don't have to spin up Outpost hardware. We can go deploy EKS anywhere in your VMware environment and it's increasing the speed of adoption for sure. >> All right so you guys are making a lot of good business decisions around managed cloud service. Innovative as that, you have the cloud advisory, the classic professional services for the specific edge piece and doing that outside of the availability zone and regions for AWS. Customers in these new areas that you're helping out are, they want cloud, they want to have modernization, modern applications. Obviously they got data machine learning and AI all part of that. What's the main product or gap that you're filling for AWS outside of their availability zones or their regions that you guys are delivering. What's the key? Is it they don't have a footprint? Is it that it's not big enough for them? What's the real gap, why are you so successful? >> So what customers want when they look towards the cloud is they want to focus on what's making them money as a business. They want to focus on their applications. They want to focus on their customers. So they look towards AWS cloud and say, AWS you take the infrastructure you take some of the higher layers and we'll focus on our revenue generating business but there's a gap there between infrastructure and revenue generating business that innovative slides into, we help manage the AWS environment. We help build out these things in local data centers for 32 plus year old company. We have traditional on-premises people that know about deploying hardware, that know about deploying VMware to host EKS anywhere. But we also have most of our company totally focused on the AWS cloud. So we're filling that gap in helping deploy these AWS services, manage them over the long term. So our customers can go to just primarily and totally focusing on their revenue generating business. >> So basically you guys are basically building AWS edges? >> Matthew: Correct. >> For companies. >> Matthew: Correct. >> Mainly because the needs are there, you got data, you got certain products, whether it's low latency type requirements, and then they still work with the regions, it's all tied together, is that how it works? >> And our customers, even the ones in the edge they also want us to build out the AWS environment inside the availability zone because we're always going to have a failback scenario. If we're going to deploy FinTech in the Caribbean we're going to talk about hurricanes. And we're going to talk about failing back into the AWS availability zones. So innovative is filling that gap across the board whether it be inside the AWS cloud or on the AWS edge. >> All right so I got to ask you on the, since you're at the edge in these areas, now, I won't say underserved but developing areas where you now have data and you have applications that are tapping into that requirement. It makes total sense, we're seeing that across the board. So it's not like it's an outlier, it's actually growing. >> Matthew: Yeah. >> There's also the crypto angle. You got the blockchain. Are you seeing any traction at the edge with blockchain? Because a lot of people are looking at the web three in these areas like Panama. And you mentioned FinTech in the islands, there are a lot of web three happening. What's your view on the web three world right now relative? >> We have some customers actually deploying crypto especially in the Caribbean. I keep bringing the Caribbean up, but it's top of my mind right now, we have customers that are deploying crypto. A lot of countries are choosing crypto to underlie parts of their central banks. So it's up and coming. I have some personal views that crypto is still searching for a use case. And I think it's searching a lot and we're there to help customers search for that use case. But crypto as a to technology lives really well on the AWS edge. And we're having more and more people talk to us about that. And ask for assistance in the infrastructure because they're developing new cryptocurrencies every day. It's not like they're deploying Ethereum or anything specific. They're actually developing new currencies and putting them out there on-- >> It's interesting. I mean, first of all we've been doing crypto for many, many years. We have our own little projects going on. But if you go talk to all the crypto people they say, look we do a smart concept. We use the blockchain. It's a lot of overhead. It's not really very technical already but it's a cultural shift but there's underserved use cases around use of money but they're all using the blockchain just for smart contracts, for instance, or certain transactions. And they go into Amazon for the database. They all, don't tell anyone we're using a centralized service. Well, what happened if decentralized? >> Yeah, and that's a conversation. >> It's a performance issue. >> Yeah and it's a cost issue and it's a development issue. So I think more and more as some of these currencies maybe come up, some of the smart contracts get into, they find their use cases. I think we'll start talking about how does that really live on AWS and what does it look like to build decentralized applications but with AWS hardware and services. >> All right so take me through a use case of a customer, Matthew, around the edge. So I'm a customer, pretend I'm a customer. Hey, we're in an underserved area. I want to modernize my business. And I got my developers that are totally peaked up on cloud but we've identified that it's just a lot of overhead latency issues. I need to have a local edge and serve my app. And I also want all the benefits of the cloud. So I want the modernization and I want to migrate to the cloud for all those cloud benefits and the goodness of the cloud. What's the answer? >> Yeah big thing is industrial manufacturing. That's one of the best use cases. Inside industrial manufacturing we can pull in many of the AWS edge services, we can bring in private 5G so that all the equipment inside that manufacturing plant can be hooked up. They don't have to pay huge overheads to deploy 5G. It's better than wifi for the industrial space. When we take computing down to that industrial area because we want to do pre-processing on the data. We want to gather some analytics. We deploy that with regular commercially available hardware, running VMware, and we deploy EKS anywhere on that. Inside of that manufacturing plant, we can do pre-processing on things coming out of the robotics depending on what we're manufacturing, right? And then we can take those refined analytics and for very low cost with maybe a little bit longer latency transmit those back to the AWS availability zone, the standard-- >> John: For data lake, or whatever. >> To the data lake, yeah data lake house, whatever it might be. And we can do additional data science on that once it gets to the AWS cloud. But a lot of that just in time business decisions, just in time manufacturing decisions can all take place on an AWS service or services inside that manufacturing plant. And that's one of the best use cases that we're seeing. >> And I think, I mean, we've been seeing this on theCUBE for many, many years, moving data around is very expensive. But also compute, going to the data that saves that cost on the data transfer but also on the benefits of the latency. So I have to ask you, by the way, that's standard best practice now for the folks watching, don't move the data unless you have to, but there's new things are developing. So I want to ask you what new are you seeing emerging once this new architecture's in place? Love that idea, localize everything, right at the edge, manufacturing, industrial, whatever the use case, retail, whatever it is. But now what does that change in the core cloud? There's a system element here, what's the new pattern? >> There's actually an organizational element as well. Because once you have to start making the decision do I put this compute at the point of use or do I put this compute in the cloud? Now you start thinking about where business decisions should be taking place. So not only are you changing your architecture you're actually changing your organization because you're thinking about a dichotomy you didn't have before. So now you say, okay, this can take place here. And maybe this decision can wait. And then how do I visualize that? >> By the way, it could be a bot too, doing the work for management. >> Yeah, exactly. >> You got observability going right. But you got to change the database architecture in the backs. There's new things developing. You've got more benefit. >> There are, there are. And we have more and more people that want to talk less about databases and want to talk more about data lakes because of this. They want to talk more about, customers are starting to talk about throwing away data. For the past maybe decade, it's been store everything. And one day we will have a data science team that we hire in our organization to do analytics on this decade of data. >> I mean, this is a great point. We don't have time to drill into, maybe we do another session on this but the one pattern we're seeing come of the past year is that throwing away data's bad. Even data lakes that so-called turn into data swamps. Actually is not the case. You look at Databrick, Snowflake and other successes out there. And even Time Series Data which may seem irrelevant efforts over actually matters when people start retraining their machine learning algorithms. >> Matthew: Yep. >> So as data becomes code, as we call it in our last showcase, we did, a whole event on this. The data's good in real time and in the lake. Because the iteration of the data feeds the machine learning training, things are getting better with the old data. So it's not throw it away. It's not just business benefits. There's all kinds of new scale. >> There are. And we have many customers that are running petabyte level. They're essentially data factories on premises, right? They're creating so much data and they're starting to say, okay we could analyze this in the cloud. We could transition it. We could move petabytes of data to the AWS cloud or we can run computational workloads on premises. We can really do some analytics on this data, transition those high level and sort of raw analytics back to AWS, run 'em through machine learning. And we don't have to transition 10, 12 petabytes of data into AWS. >> So I got to end the segment on a kind of a fun note. I was told to ask you about your personal background on premise architect, AWS cloud, and skydiving instructor. How does that all work together? What does this mean? You jumped out a plane and got a job. You got a customer to jump out? >> Kind of, so I was-- >> You jumped out? >> I was teaching skydiving before I started in the cloud space, this was 13, 14 years ago. I was a, I still am a skydiving instructor. I was teaching skydiving. And I heard out of the corner of my ear a guy that owned an MSP that was lamenting about storing data and how his customers are working. And he can't find enough people to operate all these workloads. So I walked over and said, hey, this is what I went to school for. I'd love to, I was living in a tent in the woods, teaching skydiving. I was like, I'd love to not live in a tent in the woods. So I started and the first day there we had a discussion, EC2 had just come out and-- >> This is amazing. >> Yeah and so we had this discussion, we should start moving customers here. And that totally revolutionized that business, that led to, that guy actually still owns skydiving airport. But through all of that and through being an on premises migrated me and myself, my career into the cloud. And now it feels like almost looking back and saying, now let's take what we learned in the cloud and apply those lessons in those services to on premises. >> It's such a great story, is going to, the whole growth mindset, pack your own parachute. >> Matthew: Exactly. >> The cloud in the early days was pretty much will the chute open? >> Matthew: Yeah. >> It was pretty much you had to roll your own cloud at that time. And so, you jump out a plane you got to make sure that parachute is going to open. >> And so was Kubernetes by the way, 2015 or so when that was coming out, it was, I mean, it was still, maybe it does still feel like that to some people. But it was the same kind of feeling that we had in the early days of AWS, the same feeling we have when-- >> It's pretty much now with you guys, it's more like a tandem jump. But a lot of this cutting edge stuff is like jumping out of an airplane. You got the right equipment. You got to do the right things. >> Exactly. >> John: Matthew, thanks for coming on theCUBE. Really appreciate it. Absolutely great conversation. >> Thanks for having me, thank you. >> Okay theCUBE's here live in San Francisco for AWS Summit. I'm John Furrier, host of theCUBE. We'll be at AWS Summit in New York coming up in the summer as well. Look up for that. Look at this calendar for all theCUBE action at theCUBE.net. We'll be right back with our next segment after this break. (upbeat music)

>>Hello. Welcome back to the cubes coverage here live in San Francisco, California. I'm John furrier, host of the cubes cube coverage of AWS summit 2022 here in San Francisco, where all the developers are the bay air at Silicon valley. And of course, eights summit in New York city is coming up in this summer. We'll be there as well. SF and NYC cube coverage. Look for us, of course, reinforcing Boston and re Mars with the whole robotics AI thing, all coming together. Lots of coverage. Stay with us. Say we've got a great guest from Deibel VC. John Skoda, founding partner, entrepreneurial venture is a venture firm. Your next act, welcome to the cube. Good to see you. >>Good to see you, Matt. I feel like it's been forever since we've been able to do something in person. Well, >>I'm glad you're here because we run into each other all the time. We've known each other for over a decade. Um, >>It's been at least 10 years, at >>Least 10 years more, and we don't wanna actually go back as freeze back the old school web 1.0 days. But anyway, we're in web three now. So we'll get to that in >>It's a little bit of a throwback to the path though, in my opinion, >>It's all the same. It's all distributed computing and software. We ran each other in Cuban. You're investing in a lot of tech startup founders. Okay. This next level, next gen entrepreneurs have a new makeup and it's software. It's hardcore tech in some cases, not hardcore tech, but using software, take old something old and make it better new, faster. So tell us about decibel. What's the firm. I know you're the founder, uh, which is cool. What's going on. Explain >>What you're doing. I mean, you remember I'm a recovering entrepreneur, right? So of course I, I, >>No, you're never recovering. You're always entrepreneur >>Always, but we are also always recovering. So I, um, sort of my was company when I was 24, if you remember before there was Facebook and friends, there was instant messaging. People were using that product at work every day, they were creating a security vulnerability between their network and the outside world. So I plugged that hole and built an instant messaging firewall. It was my first company. The company was called IM logic and we were required by Symantec. Uh, then spent 12 years investing in the next generation of software companies, uh, early investor in open source companies and cloud companies and spent a really wonderful 12 years, uh, at a firm called NEA. So I, I feel like my whole life I've been either starting enterprise software companies or helping founders start enterprise software C is, and I'll tell you, there's never been a better time than right now to start an enterprise software company. >>So, uh, the passion for starting a new firm was really a recognition that founders today that are starting an enterprise software company, they, they tend to be, as you said, a more technical founder, right? Usually it's a software engineer or builder. Uh, they are building products that are serving a slightly different market than what we've traditionally seen in enterprise software. Right? I think traditionally we've seen it buyers or CIOs that have agendas and strategies, which, you know, purchase software that is traditionally bought and sold tops down. But you know, today I think the most successful enterprise software companies are the ones that are built more bottoms up and have more technical early adopters. And generally speaking, they're free to use. They're free to try. They're very commonly community. So source or open source companies where you have a large technical cook community that's supporting them. So there's a, there's kind of a new normal now I think in great enterprise software. And it starts with great technical founders with great products and great bottoms of motions. And I think there's no better place to, uh, service those people than in the cloud and uh, in, in your community. >>Well, first of all, congratulations, and by the way, you got a great pedigree and great grow, super smart admire of your work and your, and, and your founding, but let's face it. Enterprise is hot because digital transformation is all companies there's no, I mean, consumer is enterprise now everything is what was once a niche. No, I won't say niche category, but you know, not for the faint of heart, you, you know, investors, >>You know, it's so funny that you say that enterprise is hot because you, and I feel that way now. But remember, like right now, there's also a giant tech and VC conference in Miami <laugh> and it's covering cryptocurrencies and FCS and web three. So I think beauty is definitely in the eye of the beholder <laugh> but no, I, I will tell you, >>Ts is one big enterprise, cuz you gotta have imutability you got performance issues. You have, I IOPS issues. Well, >>And, and I think all of us here that are, uh, may maybe students of history and have been involved in open source in the cloud would say that we're, you know, much of what we're doing is, uh, the predecessors of the web web three movement. And many of us I think are contributors to the web three. >>The hype is definitely one, three. You >>Yeah, but, >>But you know, for >>Sure. Yeah, no, but now you're taking us further east to Miami. So, uh, you know, look, I think, I, I think, um, what is unquestioned with the case now? And maybe it's, it's more obvious the more time you spend in this world is this is the fastest growing part of enterprise software. And if you include cloud infrastructure and caught infrastructure spend, you know, it is by many measures over, uh, 500 billion in growing, you know, 20 to 30% a year. So it it's a, it's a just incredibly fast, >>Well, let's getting, let's get into some of the cultural and the, the shifts that are happening, cuz again, you, you have the luxury of being in enterprise when it was hard, it's getting easier and more cooler. I get at it and more relevant <laugh> but there's also the hype of like the web three, for instance, but you know, for, uh, um, um, the CEO snowflake, okay. Has wrote a book and Dave Valenti and I were talking about it and uh, Frank Luman has says, there's no playbooks. We always ask the CEOs, what's your playbook. And he's like, there's no playbook, situational awareness, always Trump's playbooks. So in the enterprise playbook, oh, higher, a direct sales force and SAS kind of crushed that now SAS is being redefined, right. So what is SAS? Is snowflake a SaaS or is that a platform? So again, new unit economics are emerging, whole new situation, you got web three. So to me there's a cultural shift, the young entrepreneurs, the, uh, user experience, they look at Facebook and say, ah, you know, they own all my data. And you know, we know that that cliche, um, they, you know, the product. So as this next gen, the gen Z and the millennials come in and our customers and the founders, they're looking at things a little bit differently and the Tech's better. >>Yeah. I mean, I mean, I think we can, we can see a lot of commonalities across all successful startups and the overall adoption of technology. Uh, and, and I would tell you, this is all one big, giant revolution. I call it the user driven revolution, right? It's the rise of the user. And you might say product like growth is currently the hottest trend in enterprise software. It's actually user like growth, right. They're one and the same. So sometimes people think the product, uh, is what is driving. >>You just pull the >>Product through. Exactly, exactly. And so that's that I, that I think is really this revolution that you see and it, and it does extend into things like crypto or currencies and web three and, you know, sort of like the control that is taken back by the user. Um, but you know, many would say that, that the origins of this movement maybe started with open source where users were contributors, you know, contributors were users and looking back decades and seeing how, how it fast forward to today. I think that's really the trend that we're all writing and it's enabling these end users. These end users in our world are developers, data engineers, cybersecurity practitioners, right. They're really the users. And they're really the, the beneficiaries and the most, you know, kind of valued people in this. >>I wanna come back to the data engineers in a second, but I wanna make a comment and get your reaction to, I have a, I'm a gen Xer technically. So for not a boomer, but I have some boomer friends who are a little bit older than me who have, you know, experienced the sixties. And I've been saying on the cube for probably about eight years now that we are gonna hit a digital hippie revolution, meaning a rebellion against the sixties was rebellion against the fifties and the man and, you know, summer of love. That was a cultural differentiation from the other one other group, the predecessors. So we're kind of having that digital moment now where it's like, Hey boomers, Hey people, we're not gonna do that anymore. We hate how you organize shit. >>Right. But isn't this just technology. I mean, isn't it, isn't it like there used to be the old adage, like, you know, you would never get fired for buying IBM, but now it's like, you obviously probably would get fired if you bought IBM. And I mean, it, it it's just like the, the, I think >>During the mainframe days, those renegades were breaking into Stanford, starting the home brew club. So what I'm trying to get at is that, do you see the young cultural revolution also, culturally, just, this is my identity NFTs to me speak volumes about my, I wanna associate with NFTs, not single sign. >>Absolutely. And, and I think like, I think you're hitting on something, which is like this convergence of, of, you know, societal trends with technology trends and how that manifests in our world is yes. I think like there is unquestionably almost a religion yeah. Around the way in which a product is built. Right. And we can use open source, one example of that religion. Some people will say, look, I'll just never try a product in the cloud if it's not open source. Yeah. I think cloud, native's another example of that, right? It's either, it's, you know, it either is cloud native or it's not. And I think a lot of people will look at a product and say, look, you know, you were not designed in the cloud era. Therefore I just won't try. I you, and sometimes, um, like it or not, it's a religious decision, right? Yeah. It's some, it's something that people just believe to be true almost without, uh, necessarily caring >>About I data, data drives all decision making. Let me ask you this next question. As a VC. Now you look at pitch, well, you've been a VC for many years, but you also have the founder entrepreneurial mindset, but you can empathize with the founders. You know, hustle is a big part of the, that first founder check, right? You gotta convince someone to part with their ch their money and the first money in which you do a lot of is about believing in the person. So faking it till you make it is hard. Now you, the data's there, you either have it cloud native, you either have the adaption or traction. So honesty is a big part of that pitch. You can't think, oh, >>AB absolutely. You know, there used to be this concept of like the persona of an entrepreneur, right. And the persona of the entrepreneur would be, you know, somebody who was a great salesperson or somebody who tell a great story. And I still think that that's important, right. It still is a human need for people to believe in narratives and stories. Yeah. But having said that you're right. The proof is in the pudding, right. At some point you click download and you try the product and does it, is it gonna, it's gonna do, or it doesn't, or it either stands out to the load test or it doesn't. And so I, I feel like in this new economy that we live in really, it's a shift from maybe the storytellers and the creators to, to the builders, right. The people that know how to build great product. And in some ways the people that can build great product stand out for on the crowd. And they're the ones that can build communities around their products. And, you know, in some ways can, um, you know, kind of own more of the narrative because their products exactly >>The volume back to the user led >>Growth. Exactly. And it's the religion of, I just love your product. Right. And I, I, I, um, Doug song is the founder of Joe security used to say, Hey, like, you know, the, the really like today's world of like consumption based software, like the user is only gonna give you 90 seconds to figure out whether or not you're a company that's easy to do business with. Right. And so you can say, and do all the things that you want about how easy you are to work with. But if the product isn't easy to install, if it's not easy to try, if it's, if the, you know, it's gotta speak >>To the, to the user. But let me ask you a question for the people watching, who are maybe entrepreneurial entre entrepreneurs, um, masterclass here is in session. So I have to ask you, do you prefer, um, an entrepreneur come in and say, look at John. Here's where I'm at. Okay. First of all, storytelling's fine. Whether you're an extrovert or introvert, have your style, sell the story in a way that's authentic, but do you, what do you prefer? Just say, here's where I'm at. Look, I have an idea. Here's my traction. I think here's my MVP prototype. I need help. Or do you wanna just see more stats? What's the, what's the preferred way that you like to see entrepreneurs come in and engage? >>There's tons of different styles, man. I think the single most important thing that every founder should know is that we, we don't invest in what things are today. We invest in what we think something will become. Right. And I think that's why we all get up in the morning and try to build something different, right? It's that we see the world a different way. We want it to be a different way, and we wanna work every single moment of the day to try to make bad vision of reality. So I think the more that you can show people where you want to be, the more likely somebody is gonna align with your vision and, and want to invest in you wanna be along for the ride. So I, I wholeheartedly believe in showing off what you got today, because eventually we all get down to like, where are we and what are we gonna do together? But, um, no, I, you gotta show the path. I think the single most important thing for any founder and VC relationship is that they have the same vision. Uh, if you have the same vision, you can, you can get through bumps in the road, you can get through short term spills. You can all sorts of things in the middle. The journey can happen. Yeah. But it doesn't matter as much. If you share the long term vision, >>Don't flake out and, and be fashionable with the, the latest trends. Cause it's over before you even get >>There. Exactly. I think many people that, that do what we do for a living will say, you know, ultimately the future is relatively easy to predict, but it's the timing that's impossible to predict. So you, you know, you sort of have to balance the, you know, we, we, we know that the world is going this way and therefore we're gonna invest a lot of money to try to make this a reality. Uh, but sometimes it happens in six months. Sometimes it takes six years. Sometimes it takes 16 years. Uh, >>What's the hottest thing in enterprise that you see the biggest wave that people should pay attention to that you're looking at right now with Desel partners, Tebel dot your site. What's the big wave. What's your big >>Wave. There, there's three big trends that we invest in. And they're the, they're the only things we do day in, day out. One is the explosion and open source software. So I think many people think that all software is unquestionably moving to an open source model in some form or another yeah. Tons of reasons to debate whether or not that is gonna happen on AMWA timeline >>Happening forever. >>But, uh, it is, it is accelerating faster than we've ever seen. So I, I think it's, it's one big, massive wave that we continue to ride. Um, second is the rise of data engineering. Uh, I think data engineering is in and of itself now a category of software. It's not just that we store data. It's now we move data and we develop applications. And, uh, I think data is in and of itself as big of a market as any of the other markets that we invest in. Uh, and finally, it's the gift that keeps on giving. I've spent my entire career in it. We still feel that security is a market that is underinvested. It is, it continues to be the place where people need to continue to invest and spend more, more. Yeah. Uh, and those are the three major trends that we >>Run and security, you think we all need a dessert do over, right? I mean, do we need a do over in security or is what's the core problem? I, >>I, I keep using this word underinvested because I think it's the right way to think about the problem. I think if you, I think people generally speaking, look at cybersecurity as an add-on. Yeah. But if you think about it, the whole economy is moving online. And so in, in some ways like security is core to protecting the digital economy. And so it's, it shouldn't be an afterthought, right? It should be core to what everyone is doing. And that's why I think relat to the trillions of dollars that are at stake, uh, I believe the market size for cybersecurity is around 150 billion and it still is a fraction of what >>We're, what we're national security even boom is booming now. So you get the convergence of national security, geopolitics, internet digital that's >>Right. You mean arguably, right. Arguably again, it's the area of the world that people should be spending more time and more money given what to stake. >>I love your thesis. I gotta outta say, I gotta love your firm. Love what you're doing. We're big supporters of your mission. Congratulations on your entrepreneurial venture. And, uh, we'll be, we'll be talking we'll maybe see a Coon. Uh, absolutely certainly EU maybe even north Americans in Detroit this year. >>Huge fan of what you guys are doing here. Thank you so much for helping me on the >>Show. Guess a bell V see Johnson here on the cube. Check him out. Founder for founders here on the cube, more coverage from San Francisco, California. After this short break, stay with us.

(bright music) >> Okay, welcome back everyone. It's theCUBE's coverage here in San Francisco, California. We're live on the show floor of AWS Summit 2022. I'm John Furrier, your host of theCUBE. And remember AWS Summit in New York city coming up this summer. We'll be there as well. And of course, re:Invent at the end of the year for all theCUBE coverage on cloud computing and AWS. The two great guests here from the APN, Global APN, Serge Shevchenko and Jeff Grimes Partner Leader. Jeff and Serge is doing partnerships. Global APN >> AWS Global Startup Program. >> Okay, say that again. >> AWS Global Startup Program. >> That's the official name. >> I love it >> Too long for me. Thanks for coming on. >> Yeah, of course. >> Yeah, appreciate it. >> Tell us about what's going on with you guys? How was you guys organized? You guys, we're obviously we're in San Francisco bay area, Silicon Valley, zillions of startups here. New York has got another one we're going to be at. Tons of startups, a lot of them getting funded, big growth in cloud, big growth in data, security, hot in all sectors. >> Jeff: Absolutely. >> So maybe we could just start with the global startup program. It's essentially a white glove service that we provide to startups that are built on AWS. And the intention there is to help identify use cases that are being built on top of AWS. And for these startups, we want to provide white glove support in co building products together, co-marketing and co-selling. Essentially, the use cases that our customers need solved that either they don't want to build themselves or perhaps more innovative. So the AWS Global Startup Program provides white glove support, dedicated headcount for each one of those pillars. And within our program, we've also provided incentives, programs, go to market activities like the AWS Startup Showcase that we've built for these startups. >> Yeah, by the way, awsstartups.com is the URL. Check it out. Okay, so your partnerships are key. Jeff, what's your role? >> So I'm responsible for leading the overall effort for the AWS Global Startup Program. So I've got a team of partner managers that are located throughout the US managing a few hundred startup ISVs right now. >> Yeah, you got a lot. >> We've got a lot. There's a lot. >> I got to ask a tough question. I'm a startup founder. I got a team. I just got my series A. We're grown and I'm trying to hire people. I'm super busy. What's in it for me? What do you guys bring to the table? I love the white glove service but translate that. What's in it for me? What do I get out of it? What's the story? >> That's a good question. Focus, I think. >> Jeff: Yeah. >> Because we get to see a lot of partners building their businesses on AWS. So from our perspective, helping these partners focus on what do we truly need to build by working backwards from customer feedback. How do we effectively go to market? Because we've seen startups do various things through trial and error and also just messaging. Because oftentimes partners or rather startups try to boil the ocean with many different use cases. So we really help them sort of laser focus on what are you really good at and how can we bring that to the customer as quickly as possible? >> Yeah, it's truly about helping that founder accelerate the growth of their company. And there's a lot that you can do with AWS but focus is truly the key word there because they're going to be able to find their little piece of real estate and absolutely deliver incredible outcomes for our customers and then they can start their growth curve there. >> What are some of the coolest things you've seen with the APN that you can share publicly? I know you got a lot going on there, a lot of confidentiality, but we're here, a lot of great partners on the floor here. I'm glad we're back at events, a lot of stuff going on, digitally with virtual stuff and hybrid. What are some of the cool things you guys have seen in the APN that you can point to? >> Yeah, absolutely. I can point to few, you can take them. So I think what's been fun over the years for me personally, I came from a startup, ran sales at an early stage startup and I went through the whole thing. So I have a deep appreciation for what these guys are going through. And what's been interesting to see for me is taking some of these early stage guys, watching them progress, go public, get acquired, and see that big day. And being able to point to very specific items that we help them to get to that point. And it's just a really fun journey to watch. >> Yeah, and part of the reason why I really love working at the AWS Global Startup Program is working with passionate founders. I just met with a founder today, he's going to build a very big business one day and watching them grow through these stages and supporting that growth, I like to think of our program as a catalyst for enterprise sort of scale. And through that we provide visibility, credibility and growth opportunities. >> A lot of partners too, what I found, talking to staff founders is when they have that milestone, they worked so hard for it. whether it's a B round, C round, or public or get bought. Then they take a deep breath and they look back at, wow what a journey it's been. So it's kind of emotional for sure, but still it's a grind. When you get funding, it's still day one. You don't stop. It's no celebrate, you got a big round or valuation. You still got to execute. >> And look it's hypercompetitive and it's brutally difficult. And our job is to try to make that a little less difficult and navigate those waters where everyone's going after similar things. >> Yeah, and I think as a group element too. I observe that startups that I meet through the APN has been interesting because they feel part of AWS. >> Serge: Totally. >> As a group of community, as a vibe there. I know they're hustling. They're trying to make things happen. But at the same time, Amazon throws a huge halo effect. That's a huge factor. You guys are the number one cloud in the business. The growth and every sector is booming. And if you're a startup, you don't have that luxury yet. And look at companies like Snowflake that built on top of AWS. People are winning by building on AWS. >> Our program really validates their technology first. So we have what's called a foundation's technical review that we put all of our startups through before we go to market. So that when enterprise customers are looking at startup technology, they know that it's already been vetted. And to take that a step further and help these partners differentiate, we use programs like the competency programs, the DevOps competency, the security competency which continues to help provide a platform for these startups, help them differentiate, and also there's go to market benefits that are associated with that. >> So let me ask the question that's probably on everyone's mind who's watching us. Actually, I asked this a lot. There's a lot of companies startups out there. Who makes the cut? Is there a criteria? God, that's not like it's sports team or anything. >> Sure. >> There's activate program, which is like there's hundreds of thousands of startups out there. Not everyone is at the APN. >> Serge: Correct. >> So ISVs, again, that's a whole nother. That's a more mature partner that might have huge market cap or growth. How do you guys focus? How do you guys focus? >> Serge: Good question. >> A thousand flowers blooming all the time. Is there a new way you guys are looking at it? I know there's been some talk about restructure or new focus. What's the focus? >> It's definitely not an easy task by any means but I recently took over this role and we're really trying to establish focus areas. So obviously a lot of the ISVs that we look after are infrastructure ISVs. That's what we do and so we have very specific pods that look after different type of partners. So we've got a security pod, we've got a DevOps pod, we've got core infrastructure, et cetera. And really we're trying to find these ISVs that can solve really interesting AWS customer challenges. >> Do you guys have a deliberate focus on these pillars? So one, infrastructure. >> Security, DevOps and data and analytics and then line of business. >> Line of business, like web marketing solutions. (group chattering) >> Yeah, exactly. >> So solutions there. >> Yeah. More solutions and the other ones are like hardcore. So infrastructure as well like storage, backup, ransomware, kind of stuff. >> Storage, networking. >> Okay, yeah, the classic. >> Database, et cetera. >> And so there's teams on each pillar. >> Yep. So I think what's fascinating for the startups that we cover is that they truly have support from a build market sell perspective. So you've got someone who's technical to really help them get the technology figured out, someone to help them get the marketing message dialed and spread, and then someone to actually do the co-sell day to day activities to help them get in front of customers. >> Probably the number one request that we always ask for Amazon is can we wish that SOC report, oh download it on the console, which we use all the time. >> Exactly. >> But security's a big deal. SREs are evolve in that role of DevOps is taking on DevSecOps. I could see a lot of customers having that need for a relationship to move things faster. Do you guys provide like escalation or is that a part of a service or not part of? >> So the partner development manager can be an escalation point, absolutely. Think of them as an extension of your business inside of AWS. >> Great and you guys, how is that partner managers measured? >> On those three pillars. >> Got it, okay. >> Are we building valuable use cases? So product development. Go to market, so go to market activities. Think blog posts, webinars, case studies, so on and so forth. And then co-sell. Not only are we helping these partners win their current opportunities that they are sourcing, but can we also help them source net new deals? >> Jeff: Yeah. >> That's very important. Top ask from the partners is get me in front of customers. Not an easy task, but that's a huge goal of ours to help them grow their top line. >> In fact, we have some interviews here on theCUBE earlier talking about that dynamic of how enterprise customers are buying. And it's interesting, a lot more POCs. I have one partner here that you guys work with on observability. They got a huge POC with Capital One and the enterprises are engaging the startups and bringing them in. So the combination of open source software, enterprises are leaning into that hard and bringing young growing startups in. So I could see that as a huge service that you guys can bring people in. >> Right and they're bringing massively differentiated technology to the table. The challenge is they just might not have the brand recognition that the big guys have. And so that's our job is how do you get that great tech in front of the right situations. >> So my next question is about the show here and then we'll talk globally. So here in San Francisco, Silicon Valley, bay area, San Francisco bay area, a lot of startups, a lot of VCs, a lot of action. So probably a big marker for you guys. So what's exciting here in SF? And then outside of SF, you guys have a global program. You see any trends that are geography-based or is it areas more mature? There's certain regions that are better. And I just interviewed a company here that's doing AWS Edge really well. It's interesting that the partners are filling a lot of holes and gaps in the opportunities with AWS. So what's exciting here, and then what's the global perspective? >> Yeah, totally. So obviously, a ton of partners from the bay area that we support, but we're seeing a lot of really interesting technology coming out of EMEA specifically. And making a lot of noise here in the United States, which is great. And so we definitely have that global presence and starting to see super differentiated technology come out of those regions. >> Yeah, especially Tel Aviv. >> Yeah. >> EMEA real quick before you get into surge. It's interesting. The VC market in Europe is hot. They've got a lot of unicorns coming in. We've seen a lot of companies coming in. They're kind of rattling their own cage right now. Hey, look at us. Let's see if they crash, but we don't see that happening. I mean, people have been predicting a crash now in the startup ecosystem for at least a year. It's not crashing. In fact, funding's up. >> The pandemic was hard on a lot of startups for sure. >> Jeff: Yeah. >> But what we've seen is many of these startups, as quickly as they can grow, they can also pivot as well. And so I've actually seen many of our startups grow through the pandemic because their use cases are helping customers either save money, become more operationally efficient, and provide value to leadership teams that need more visibility into their infrastructure during a pandemic. >> It's an interesting point. I talked to Andy Jassy and Adam Selipsky both say the same thing during the pandemic. Necessity is the mother of all invention. And startups can move fast. So with that, you guys are there to assist. If I'm a startup and I got to pivot, 'cause remember iterate and pivot, iterate and pivot so you get your economics. That's the playbook of the ventures and the models. >> Yeah, exactly. >> How do you guys help me do that? Give an example, walk me through. Pretend me I'm a startup. Hey, I am on the cloud. Oh my God, pandemic. They need video conferencing. Hey CUBE, what do I need? Serge, what do I do? >> That's a good question. First thing is just listen. I think what we have to do is a really good job of listening to the partner. What are their needs? What is their problem statement and where do they want to go at the end of the day? And oftentimes because we've worked with so many successful startups that have come out of our program, we of either through intuition or a playbook determine what is going to be the best path forward and how do we get these partners to stop focusing on things that will eventually just be a waste of time and or not provide or bring any fruit to the table, which essentially revenue. >> Well, we love startups here in theCUBE because one, they have good stories, they're on cutting edge, always pushing the envelope, and they're kind of disrupting someone else. And so they usually have an opinion they don't mind sharing on camera. So love talking to startups. We love working with you guys on our Startup Showcase, awsstartups.com. Check out awsstartups.com and check out the showcases. Final word, I'll give you guys the last word. What's the bottom line, bumper sticker for the global APN program? Summarize the opportunity for startups, what you guys bring to the table and we'll close it out. Jeff, we'll start with you. >> Totally, yeah. I think the AWS Global Startup Program's here to help companies truly accelerate their business, full stop. And that's what we're here for. >> I love it. It's a good way to put it. >> Ditto? >> Yeah. >> All right. Serge, Jeff, thanks for coming on. >> Thanks John. >> Great to see you. Love working with you guys. Hey, startups need help and the growing and huge market opportunities, the shift cloud scale, data engineering, security, infrastructure, all the markets are exploding in growth because of the digital transformation of realities here, open source and cloud. All making it happen here in theCUBE in San Francisco, California. I'm John Furrier your host. Thanks for watching. >> Let's go, John. (soft music)

>>Okay, welcome back everyone. This is the cubes coverage here in San Francisco, California, a Davis summit, 2022, the beginning of the event season, as it comes back, little smaller footprint, a lot of hybrid events going on, but this is actually a physical event to his summit in new York's coming in the summer. We'll be there too with the cube on the set. We're getting back in the Groove's psych to be back. We were at reinvent, uh, as well, and we'll see more and more cube, but you're can see a lot of virtual cube outta hybrid cube. We wanna get all those conversations, try to get more interviews, more flow going. But right now I'm excited to have Corey Quinn here on the back on the cube chief cloud economists with duct bill, a group, he's the founder, uh, and chief content person always got great angles, fun comedy, authoritative Corey. Great to see you. Thank >>You. Thanks. Coming on. Sure is a lot of words to describe is shit posting, which is how I describe what I tend to do. Most days, >>Shit posting is an art form now. And if you look at mark, Andrew's been doing a lot of shit posting lately. All a billionaires are shit posting, but they don't know how to do it. Like they're not >>Doing it right. There's something opportunity there. It's like, here's how to be even more obnoxious and incisive. It's honestly the most terrifying scenario for anyone is if I have that kind of budget to throw at my endeavors, it's like, I get excited with a nonsense I can do with a $20 gift card for an AWS credit compared to, oh well, if I could buy a midsize island to in doing this from, oh, then we're having fun. >>This shit posting trend. Interesting. I was watching a thread go on about, saw someone didn't get a job because of their shit posting and the employer didn't get it. And then someone on this side, I'll hire the guy cuz I get that's highly intelligent shit posting. So for the audience that doesn't know what shit posting is, what is shit posting? >>It's more or less talking about the world of enterprise technology, which even that sentence is hard to finish without falling asleep and toppling out of my chair in front of everyone on the livestream, but it's doing it in such a way that brings it to life that says the quiet part. A lot of the audience is thinking, but generally doesn't say either because they're polite or not a jackass or more prosaically are worried about getting fired for better or worse. I don't have have that particular constraint, >>Which is why people love you. So let's talk about what you, what you think is, uh, worthy and not worthy in the industry right now, obviously, uh, coupons coming up in Spain, which they're having a physical event, you see the growth of cloud native Amazon's evolving Adams, especially new CEO. Andy's move on to be the chief of all Amazon. Just so I, the cover of was it time magazine, um, he's under a lot of stress. Amazon's changed. Invoice has changed. What's working. What's not, what's rising, what's falling. What's hot. What's not, >>It's easy to sit here and criticize almost anything. These folks do. They're they're effectively in a fishbowl, but I have trouble imagining the logistics. It takes to wind up handling the catering for a relat a downscale event like this one this year, let alone running a 1.7 million employee company having to balance all the competing challenges and pressures and the rest. I, I just can't fathom what it would be like to look at all of AWS. And it's, it's sprawling immense that dominates our entire industry and say, okay, this is a good start, but I, I wanna focus on something with a broader remit. What is that? How do you even get into that position? And you can't win once you're there. All you can do is hold onto the tiger and hope you don't get mold. Well, >>There's a lot of force for good conversations. Seeing a lot of that going on, Amazon's trying to port eight of us is trying to portray themselves as you know, the Pathfinder, you know, you're the pioneer, um, force for good. And I get that. I think that's a good angle as cloud goes mainstream. It's still the question of, we had a guy on just earlier, who was a skydiving instructor and we were joking about the early days of cloud. Like that was like skydiving, build a parachute open, you know, and now it's saying kind of thing, as you move to edge, things are like reliable in some areas, but still new, new fringe, new areas. That's crazy. Well, >>Since the last time we've spoken, uh, Steve Schmidt is now the CISO for all of Amazon and his backfill replacement. The AWS CISO is CJ. Moses who as a hobby race as a semi-pro race car driver to my understanding, which either, I don't know what direction to take that in either. This is what he does to relax or ultimately, or ultimately it's. Huh? That, that certainly says something about risk assessment. I'm not entirely sure what, but okay. Either way, sounds like more exciting, like better >>Have a replacement ready <laugh> in case something gonna was wrong on the track, >>Highly available >>CSOs. I gotta say one of the things I do like in the recent trend is that the tech companies are getting into the formula one, which I was never a fan of until I watched that Netflix series. But when you look at the formula one, it's pretty cool. Cause it's got some tech angles, I get the whole data instrumentation thing, but the most coolest thing about formula one is they have these new rigs out. Yeah. Where you can actually race in e-sports with, there are people in pure simulation of the race car. You gotta get the latest and video graphics card, but it's basically a tricked out PC with amazing monitors and you have all the equipment of F1 and you're basically simulating racing. >>Oh, it's great too. And I can see the appeal of these tech companies getting into it because these things are basically rocket chips. When those cars go like they're sitting there, we cans instrument every last part of what is going on inside that vehicle. And then AWS crops up. And we can bill on every one of those dimensions too. And it's like slow down their hasty pudding one step at a time. But I do see the appeal. >>So I gotta ask you about, uh, what's going on in your world. I know you have a lot of great success. We've been following you in the queue for many, many years. Got a great newsletter, check out Corey Quinn's newsletter, uh, screaming in the cloud program. Uh, you're on the cutting edge and you've got a great balance between really being snarky and, and, and really being delivering content. That's exciting, uh, for people, uh, with a little bit of an edge, um, how's that going? Uh, what's the blowback, any blowback lately? Has there been uptick? What was, what are some of the things you're hearing from your audience, more Corey or Corey, and then of course the, the PR team's calling you >>The weird thing about having an audience beyond a certain size is far and away as a landslide. The most common response I get is silence where it's huh? I'm emailing an awful lot of people at last week in AWS every week and okay. They must not have heard me it. That is not actually true. People just generally don't respond to email because who responds to email newsletters, that sounds like something, a lunatic might do same story with response to live streams and podcasts. It's like, I'm gonna call into that am radio show and give them a piece of my mind. People generally don't do that. >>We should do that. Actually. I think sure would call in. Oh, I, >>I think >>I guarantee we had that right now. People would call in and say, Cory, what do you think about X? >>Yeah. It not, everyone understands the full context of what I do. And in fact, increasingly few people do and that's fine. I, I keep forgetting that sometimes people do not see what I'm doing in the same light that I do. And that's fine. Blowback has been largely minimal. Honestly, I am surprised anything about how little I have gotten over the last five years of doing this, but it would be easier to dismiss me if I weren't generally. Right. When, okay, so you launch this new service and it seems pretty crappy to me cuz when I try and build something, it falls over and begs for help. And people might not like hearing that, but it's what customers are finding too. Yeah. I really am the voice of the customer. >>You know, I always joke with Dave ante about how John Fort's always at, uh, um, reinvent getting the interview with jazzy now, Andy we're there, you're there. And so we have these rituals at the events. It's all cool. Um, one of the rituals I like about your, um, your content is you like to get on the naming product names. Um, and, and, and, and, and kind of Google from that. Now why I like is because I used to work at ETT Packard where they used to name things as like engineers, HP 1 0 5, or we can't call, we >>Have a new monitor. How are we gonna name it? Throw the wireless keyboard down the stairs again. And there you go. Yeah. >>It's and the old joke at HP was if they, if they invented SU uh, sushi, they'd say, yeah, we can't call sushi. It's cold, dead fish. That's what it is. And so the joke was cold. Dead fish is a better name than sushi. So, you know, fun. So what's the, what are the, how's the Amazon doing in there? Have they changed their naming, uh, strategy, uh, on some of their, their >>Producting. So they're going in different directions. When they named Amazon Aurora, they decided to explore a new theme of Disney princesses as they go down those paths. And some things are more descriptive. Some people are clearly getting bonused on a number of words. They can shove into it. Like the better a service is the longer it's name. Like AWS systems manager, session manager is a great one. I love the service ridiculous name. They have a systems manager, parameter store, which is great. They have secrets manager, which does the same thing. It's two words less, but that one costs my in a way that systems manage through parameter store does not. It's fun. >>What's your, what's your favorite combination of acronyms >>Combination >>Of you got E Ks. You got EMR, you got EC two, you got S3 SQS. Well, RedShift's not an acronym. You >>Gots is one of my personal favorites because it's either elastic block store or elastic bean stock, depending into highly on the context of the conversation. They still >>Up Beanstalk or is that still around? >>Oh, they never turn anything off. They like the Antigo, Google turns things off while they're still building it. Whereas Amazon is like, well, we built this thing in 2005 and everyone hates it, but while we certainly can't change it, now it has three customers on it. John three <laugh>. Okay. Simple DV still haunts our dreams. >>I, I actually got an email on, I saw one of my, uh, servers, all these C twos were being deprecated and I got an email. I'm like, couldn't figure out. Why can you just like roll it over? Why, why are you telling me just like, give me something else. Right. Okay. So let me talk about, uh, the other things I want to ask you is that like, okay, so as Amazon gets better, so areas where do they need more work in your opinion? Because obviously they're all interested in new stuff and they tend to like put it out there for their end to end customers. But then they've got ecosystem partners who actually have the same product. Yes. And, and this has been well documented. So it's, it's not controversial. It's just that Amazon's got a database, Snowflake's got a database service. So, you know, Redshift, snowflake 80 is out there. So you got this co-op petition. Yes. How's that going? And what are you hearing about the reaction to any of that stuff? >>Depends on who you ask. They love to basically trot out a bunch of their partners who will say nice things about them. And it very much has heirs of, let's be honest, a hostage video, but okay. Cuz these companies do partner with Amazon and they cannot afford to rock the boat too far. I'm not partnered with anyone. I can say what I want. And they're basically restricted to taking away my birthday at worse so I can live with that. >>All right. So I gotta ask about multi-cloud cause obviously the other cloud shows are coming up. Amazon hated that word. Multi-cloud um, a lot of people are saying, you know, it's not a real good marketing word. Like multi-cloud sounds like, you know, root canal. Mm-hmm <affirmative> right. So is there a better description for multi-cloud >>Multiple single, which >>Davey loves that term. Yeah. >>You know, you're building in multiple single points of failure, do it for the right reasons or don't do it as a default. I believe not doing it is probably the right answer. However, and if I were, if I were Amazon, I wouldn't want to talk about multi-cloud either as industry leader, let's talk about other clouds, bad direction to go in from a market cap perspective. It doesn't end well for you, but regardless of what they want to talk about, or don't want to talk about what they say, what they don't say, I tune all of it out. And I look at what customers are doing and multi-cloud exists in a variety of forms. Some brilliant, some brain dead. It depends a lot on context. But my general response is when someone gets on stage from a company and tells me to do a thing that directly benefits their company. I am skeptical at best. Yeah. When customers get on stage and say, this is what we're doing because it solves problems. That's when I shut up and listen. >>Yeah. Cool. Awesome. Corey, I gotta ask you a question cause I know you we've been, you know, fellow journeymen in the, and the cloud journey, going to all the events and then the pandemic hit. Of course, we're now in the third year, who knows what it's gonna gonna end? Certainly events are gonna look different. They're gonna be either changing footprint with the virtual piece, new group formations. Community's gonna emerge. You've got a pretty big community growing and it's growing like crazy. What's the weirdest or coolest thing, or just big changes you've seen with the pandemic, uh, from your perspective. Cause you've been in the you're in the middle of the whitewater rafting. Seeing the event you circle offline, you saw the online piece, come in, you're commentating, you're calling balls and strikes in the industry. You got a great team developing over there. Duck bill group. What's the big aha moment that you saw with the pandemic. Weird, funny, serious, real in the industry and with customers what's >>Accessibility. Reinvent is a great example. When in the before times it's open to anyone who wants to attend, who can pony up two grand and a week in Las Vegas and get to Las Vegas and wherever they happen to be by moving virtually suddenly it, it embraces the reality that talent is evenly. Distributed. Opportunity is not. And that means that suddenly these things are accessible to a wide swath of audience and potential customer base and the rest that hadn't been invited to the table previously, it's imperative that we not lose that. It's nice to go out and talk to people and have people come up and try and smell my hair from time to time, I smell delightful. Let me assure you. But it was, but it's also nice to be. >>I have some product for you if you want, you know? Oh, >>Oh excellent. I look forward to it. What is it? Pudding? Why not? <laugh> >>What else have you seen? So when accessibility for talent, yes. Which by the way is totally home run. What weird things have happened that you've seen? Um, that's >>Uh, it's, it's weird, but it's good that an awful lot of people giving presentations have learned to tight their message and get to the damn point because most people are not gonna get up from a front row seat in a conference hall, midway through your Aing talk and go somewhere else. But they will change a browser tab and you won't get them back. You've gotta be on point. You've gotta be compelling if it's going to be a virtual discussion. Yeah. >>And also turn off your iMessage too. >>Oh yes. It's always fun in the, in the meetings when you're talking to someone and colleague is messaging them about, should we tell 'em about this? And I'm sitting there reading it and it's >>This guy is really weird. Like, >>Yes I am and I bring it into the conversation and then everyone's uncomfortable. It goes, wow. Why >>Not? I love when my wife yells at me over I message. When I'm on a business call, like, do you wanna take that about no, I'm good. >>No, no. It's better off. I don't the only encourager. It's fine. >>Kids texting you. That's fun. Again. That's another weird thing. And, and then group behavior is weird. Now people are looking at, um, communities differently. Yes. Very much so, because if you're fatigued on content, people are looking for the personal aspect. You're starting to see much more of like yeah. Another virtual event. They gotta get better. One and two who's there. >>Yeah. >>The person >>That's a big part of it too is the human stories are what are being more and more interesting. Don't get up here and tell me about your product and how brilliant you are and how you built it. That's great. If I'm you, or if I wanna work with you or I want to compete with you, or I wanna put on my engineering hat and build it myself. Cause why would I buy anything? That's more than $8. But instead, tell me about the problem. Tell me me about the painful spot that you specialize in. Yeah. Tell me a story there. >>I, I think >>That gets a glimpse in a hook and makes >>More, more, I think you nailed it. Scaling storytelling. Yes. And access to better people because they don't have to be there in person. I just did a thing. I never, we never would've done the queue. We did. Uh, Amazon stepped up in sponsors. Thank you, Amazon for sponsoring international women's day, we did 30 interviews, APAC. We did five regions and I interviewed this, these women in Asia, Pacific eight, PJ, they call for in this world. And they're amazing. I never would've done those interviews cuz I never, would've seen 'em at an event. I never would've been in Japan or Singapore, uh, to access them. And now they're in the index. They're in the network. They're collaborating on LinkedIn. So a threads are developing around connections that I've never seen before. Yes. Around the content. >>Absolutely >>Content value plus network >>Effecting. And that is the next big revelation of this industry is going to realize you have different companies. And in Amazon's case, different service teams, all competing with each other, but you have the container group and you have the database group and you have the message cuing group. But customers don't really want to build things from spare parts. They want a solution to a problem. I want to build an app that does Twitter for pets or whatever it is I'm trying to do. I don't wanna basically have to pick and choose and fill my shopping cart with all these different things. I want something that's gonna basically give me what I'm trying to get as close to turnkey as possible. Moving up the stack. That is the future. And just how it gets here is gonna be >>Well we're here with Corey Quinn, the master of the master of content here in the a ecosystem. Of course we we've been following up from the beginning. It's great guy. Check out his blog, his site, his newsletter screaming podcast. Corey, final question for you. Uh, what do you hear doing what's on your agenda this week in San Francisco and give a plug for the duck build group. What are you guys doing? I know you're hiring some people what's on the table for the company. What's your focus this week and put a plug in for the group. >>I'm here as a customer and basically getting outta my cage cuz I do live here. It's nice to actually get out and talk to folks who are doing interesting things at the duck build group. We solve one problem. We fixed the horrifying AWS bill, both from engineering and architecture, advising as well as negotiating AWS contracts because it turns out those things are big and complicated. And of course my side media projects last week in aws.com, we are it's more or less a content operation where I indulge my continual and love affair with the sound of my own voice. >><laugh> and you're good. It's good content it's on, on point fun, Starky and relevant. So thanks for coming on the cube and sharing with us. Appreciate it. No, >>Thank you. Fun. >>Okay. This cube covers here in San Francisco, California, the cube is back going to events. These are the summits, Amazon web services summits that happen all over the world. We'll be in New York and obviously we're here in San Francisco this week. I'm John fur. Keep, keep it right here. We'll be back with more coverage after this short break.

>>Okay, welcome back everyone to San Francisco, live coverage here with the cube 80, be summit 2022. We're back in person. I'm John furry host of the cube. We'll be at the 80 us summit in New York city. This summer, check us out then. But right now, two days in San Francisco, getting all the coverage what's going on in the cloud, we got a cube, alumni and friend of the cube. I dos car CEO, investor, a Sierra, and also an investor and a bunch of startups, angel investor. I'm gonna do great to see you. Thanks for coming on the cube. Good to see you. Good to see. See you, sir. Chris pump. Cool. How are you? >>Good. How are you? >>So congratulations on all your investments. Uh, you've made a lot of great successes over the past couple years and your company raising some good cash as Sarah. So give us the update. How much cash have you guys raised? What's the status of the company product what's going on? >>First of all, thank you for having me. We're back to be business with you never while after. Great to see you. Um, so I, as the company started around four years back, I invested with a few of the investors and now I'm the CEO. Um, we have raised close to a hundred million there. The investors are people like nor west Menlo, true ventures, coast, lo ventures, Ram Shera, and all those people all well known guys, Andy Beel chime Paul Mo Mayard web. So a whole bunch of operating people and, uh, Silicon valley vs are involved >>And has it gone? >>It's going well. We are doing really well. We are going almost 300% year over year. Uh, for last three years, the space ISRA is going after is what I call the applying AI for customer service. It operations, it help desk, uh, the same place I used to work at ServiceNow. We are partners with ServiceNow to take, how can we argument for employees and customers, Salesforce, and service now to take it the next stage? Well >>Of having you on the cube, Dave and I, David ante as well loves having you on too, because you not only bring the entrepreneurial CEO experience, you're an investor. You're like a, you're like a guest analyst. <laugh> >>You know who done? You >>Get the comment, this fun to talk to you though, you >>Get the commentary, you you're your finger on the pulse. Um, so I gotta ask you obviously, AI and machine learning, machine learning AI, or you want to phrase isn't every application. Now, AI first, uh, you're seeing a lot of that going on. You're starting to see companies build the modern applications at the top of the stack. So the cloud scale has hit. We're seeing cloud scale. You predicted that we talked about in the cube many times. Now you have that past layer with a lot more services and cloud native becoming a standard layer. Containerizations growing Docker just raised a hundred million on a 2 billion valuation back from the debt after they pivoted from an enterprise services. So open source developers are booming. Um, where's the action. I mean, is there data control, plane emerging, AI needs data. There's a lot of challenges around this. There's a lot of discussions and a lot of companies being funded, observability there's 10 million observability companies. Data is the key. What's your angle on this? What's your take? Yeah, >>No, look, I think I'll give you the view that I see right from my side. Obviously data is very clear. So the things that system of recorded you and me talked about the next layer is called system of intelligence. That's where the AI will play. Like we talk cloud native, it'll be called AI. Native NATO is a new buzzword and using the AI for customer service it operations. We talk about observability. I call it AI ops, applying ops for good old it operations management, cloud management. So you'll see the AOPs applied for whole list of, uh, application from observability doing the CMDB, predicting the events incidents. So I see a lot of work clicking for AIOps and AI service desk. What used to be help desk with ServiceNow BMC <inaudible> you see a new, a layer emerging as a system of intelligence. Uh, the next would be is applying AI with workflow automation. So that's where you'll see a lot of things called customer workflows, employee workflows. So think of what UI path automation, anywhere ServiceNow are doing, that area will be driven with AI workflows. So you'll see AI going off >>Is RPA a company is AI, is RPA a feed of something bigger? Or can someone have a company on RPA UI pass? One will be at their event this summer? Um, is it a product company? I mean, I mean, RPA is almost, should be embedded in everything. It's a feature. >>It is very good point. Very, very good thing. So one is, it's the category for sure. Like it's a category, it's an area where RPA maybe change the name. I call it much more about automation, workflow automation, but RPA and automation is a category. Um, it's a company also, but that automation should be ed in every area. Yeah. Like we call cloud NATO and AI NATO. It'll become automation. NATO. Yeah. And that's your thinking? So >>It's most interesting me. I think about the, what you're talking about. What's coming to my is I'm kinda having flashbacks to the old software model of middleware. Remember at middleware, it was very easy to understand it was middleware. It sat between two things and then the middle and it was software abstraction. Now you have all kinds of workflows abstractions everywhere. So multiple databases, it's not a monolithic thing. Right? Right. So as you break that down, is this the new modern middleware? Because what you're talking about is data workflows, but they might be siloed. Are they integrated? I mean, these are the challenges. This is crazy. What's the, >>So don't put the database became called polyglot databases. Yeah. I call this one polyglot automation. So you need automation as a layer, as a category, but you also need to put automation in every area like you you're talking about. It should be part of service. Now it should be part of ISRA, like every company, every Salesforce. So that's why you see it. MuleSoft and Salesforce buying RPA companies. So you'll see all the SaaS companies, cloud companies having an automation as a core. So it's like how you have a database and compute and sales and networking. You'll also have an automation as a layer <inaudible> inside every stack. >>All right. So I wanna shift gears a little bit and get your perspective on what's going on behind us. You can see, uh, behind us, you got the expo hall, got, um, we're back to vents, but you got, you know, AMD, Clum, Ove, uh, Dynatrace data, dog, innovative all the companies out here that we know. And we interview them all. They're trying to be suppliers to this growing enterprise market. Right. Okay. But now you also got the entrepreneurial equation. Okay. We're gonna have John Sado on from Deibel later today. He's a former NEA guy and we always talk to Jerry, Jen. We know all the, the VCs. What does the startups look like? What does the, to of the, in your mind, cuz you, I know you invest the entrepreneurial founder situation. Cloud's bigger. Mm-hmm <affirmative> global, right? Data's part of it. You mentioned data's code. Yes. Basically. Data's everything. What's it like for a first an entrepreneur right now who's starting a company. What's the white space. What's the attack plan. How do they get in the market? How do they engineer everything? >>Very good. So I'll give it to two things that I'm seeing out there. Remember days of Amazon created the startups 15 years back, everybody built on Amazon now Azure and GCP. The next layer would be is people don't just build on Amazon. They're going build it on top of snowflake. Companies are snowflake becomes the data platform, right? People will build on snowflake. Right? So I, my old boss Blankman trying to build companies on snowflake. So you don't build it just on Amazon. You build it on Amazon and snowflake. Snowflake will become your data store. Snowflake will become your data layer. Right? So I think that's the next level of <inaudible> trying to do that. So if I'm doing observability AI ops, if I'm doing next level of Splunk SIM, I'm gonna build it on snowflake, on Salesforce, on Amazon, on Azure, et cetera. >>It's interesting. You know, Jerry Chan has it put out a thesis a couple months ago called castles in the cloud where your moat is, what you do in the cloud. Not necessarily in the, in the IP. Um, Dave LAN and I had last reinvent, coined the term super cloud. Right's got a lot of traction and a lot of people throwing, throwing mud at us, but we were, our thesis was, is that what Snowflake's doing? What Goldmans Sachs is doing. You're starting to see these clouds on top of clouds. So Amazon's got this huge CapEx advantage. And guys like Charles Fitzgerald out there who we like was kind of shitting on us saying, Hey, you guys terrible, they didn't get him. Like, yeah, I don't think he gets it, but that's a whole, can't wait to debate him publicly on this. He's cool. Um, but snowflake is on Amazon. Yes. Now they say they're on Azure now. Cause they've got a bigger market and they're public, but ultimately without a AWS snowflake doesn't exist and, and they're reimagining the data warehouse with the cloud, right? That's the billion dollar opportunity. >>It is. It is. They both are very tight. So imagine what Frank has done at snowflake and Amazon. So if I'm a startup today, I want to everything on Amazon where possible whatever is, I cannot build, I'll make the pass layer. Remember the middle layer pass will be snowflake so I can build it on snowflake. I can use them for data layer. If I really need do size, I'll build it on force.com Salesforce. Yeah. Right. So I think that's where you'll. >>So basically the, the, if you're an entrepreneur, the, the north star in terms of the, the outcome is be a super cloud. It is, That's the application on another big CapEx ride, the CapEx of AWS or >>Cloud, and that reduce your product development, your go to market and you get use the snowflake marketplace to drive your engagement. >>Yeah. Yeah. How are, how is Amazon and the clouds dealing with these big whales, the snowflakes of the world? I mean, I know they got a great relationship, uh, but snowflake now has to run a company they're public. Yeah. So, I mean, I'll say, I think they had Redshift. Amazon has got Redshift, um, but snowflakes, a big customer and the they're probably paying AWS, I think bills too. So >>John video it's like whole Netflix is, and Amazon prime Netflix runs on Amazon, but Amazon has Amazon prime that co-optation will be there. So Amazon will have Redshift, but Amazon is also partnering with, uh, snowflake to have native snowflake data warehouses, a data layer. So I think depending on the applic use case, you have to use each of the above. I think snowflake is here for a long term. So if I'm building an application, I want to use snowflake then, right. Think from stats. >>Well, I think that it comes back down to entrepreneurial hustle. Do you have a better product? Right. Product value will ultimately determine it as long as the cloud doesn't, You know, foreclose your value. That's right. With some sort of internal hack. But I think, I think the general question that I have is that I, I think it's okay to have a super cloud like that because the rising tide is still happening. Some point, when does the rising tide stop >>And >>The people shopping up their knives, it gets more competitive or is it just an infinite growth cycle? >>I think it's growth. You call it cloud scale. You invented the word cloud scale. So I think, look, cloud will continually agree, increase. I think there's, as long as there are more movement from on, uh, on-prem to the classical data center, I think there's no reason at this point, the rumor, the old lift and shift that's happening in like my business. I see people lift and shifting from the it operations, it helpless, even the customer service service now and, uh, ticket data from BMCs CAS like Microfocus, all those workloads are shifted to the cloud, right? So ticketing system is happening. Cloud system of record is happening. So I think this train has still a long way to go >>Made. I wanna get your thoughts for the folks watching that are, uh, enterprise buyers or practitioners, not suppliers to the market, feel free to text me or DMing next. Question's really about the buying side, which is if I'm a customer, what's the current, um, appetite for startup products, cuz you know, the big enterprises now and you know, small, medium, large, and large enterprise, they're all buying new companies cuz a startup can go from zero to relevant very quickly. So that means now enterprises are engaging heavily with startups. What's it like what's is there a change in order of magnitude of the relationship between startup selling to, or growing startup selling to an enterprise? Um, have you seen changes there? I mean I'm seeing some stuff, but why don't we get your thoughts on that? What, no, it >>Is. If I remember going back to our 2007 or eight, when I used to talk to you back then and Amazon started very small, right? We an Amazon summit here. So I think enterprises on the average used to spend nothing with startups. It's almost like 0% or one person today. Most companies are already spending 20, 30% with startups. Like if I look at a CIO, a line of business it's gone. Yeah. Can it go more? I think it can double in the next four, five years. Yeah. Spending on the startups. >>Yeah. And check our, uh, AWS startups.com. That's a site that we built for the startup community for buyers and startups. And I want get your reaction because I, I reference the URL cause it's like, there's like a bunch of companies we've been promoting because the solutions that startups have actually are new stuff. Yes. It's bending, it's shifting left for security or using data differently or are um, building tools and platforms for data engineering. Right. Which is a new persona that's emerging. So you know, a lot of good resources there. Um, and goes back now to the data question. Now, getting back to your, what you're working on now is what's your thoughts around this new, um, data engineering persona. You mentioned a AIOps we've been seeing AOPs IOPS blue booming and that's creating a new developer paradigm that's right. Which we call and coin data as code data as code is like infrastructure as code, but it's for data, right? It's developing with data, right? Retraining machine learnings, going back to the data lake, getting data to make, to do analysis, to make the machine learning better post event or post action. So this, this to engineers like an SRE for data, it's a new, scalable role we're seeing. Do you see the same things? Do you agree? Um, do you disagree or can you share >>Yourself? I, no, I have a lot of thoughts that first is I see the AOP solutions in the future should be not looking back. I need to be like we are in San Francisco bay. That means earthquake prediction. Right? I want AOPs to predict when the outages are gonna happen. When there's a performance issue. I don't think most AOPs vendors have not gone through it. Like I spend a lot of time with data dog, Cisco app dynamic, right? Dynatrace, all this solution will go future towards predict to proactive solution with AOPs. But what you bring of a very good point on the data side, I think like we have a Amazon marketplace and for startup, there should be data exchange where you want to create for AOPs and AI service desk customers that give the data, share the data because we thought the data algorithms are useless. I can come the best algorithm, but I gotta train them, modify them, tweak them, make >>Them >>Better, make them better. Yeah. And I think there are a whole data exchange is the industry has not thought through something you and me talk many times. Yeah. Yeah. I think the whole, that data is very important. >>You've always been on, on the Vanguard of data because, uh, it's been really fun. Yeah. >>Going back to big data days back in 2009, you know, >>Look at, look how much data bricks has grown. >>It is double, the >>Key cloud air kinda went private, so good stuff. But what are you working on right now? Give a, give a, um, plug for what you're working on. You'll still invest strength. >>I do still invest, but look, I'm a hundred percent on ISRA right now. I'm the CEO there. Yeah. Okay. >>So >>Right. ISRA is my number one baby right now. So I'm looking at that growing customers and my customers. Some of them you like it's zoom auto desk, MacAfee, uh, grantor. So all the top customers, um, mainly for it help desk customer service ops. Those are three product lines and going after enterprise and commercial deals. >>And when should someone buy your product? What what's their need? What category is it? >>I think the look whenever somebody needs to buy the product is if you need AOP solution to predict, keep your lights on, predict ours one area. If you want to improve employee experience, you are using a slack teams and you want to automate all your workflows. That's another value. Prop. Third is customer service. You don't want to hire more people to do it. Some of the areas where you want to scale your company, grow your company, eliminate the cost customer service. >>Great stuff, man. Great to see you. Thanks for coming on. Congratulations on the success of your company and your investments. Thanks for coming on the key. Okay. I'm John fur here at the cube live in San Francisco for day one of two days of coverage of Aish summit 2022. And we're gonna be at a summit in San, uh, in New York in the summer. So look for that on this calendar, of course, go to Aish startups.com and mention that it's ay for all the hot startups and of course the cube.net and Silicon angle.com. Thanks for watching. We'll be back more coverage after this short break.