>>Mhm. Yes. Hello. Welcome back to the cubes coverage of dr khan 2021 virtual. I'm john for your host of the cube. We're messing my fair principal technologist at AWS amazon Web services messman. Thank you for coming on the cube, appreciate it. Um >>Thank you. Thank you for having me. >>Great to see you love this amazon integration with doctor want to get into that in a second. Um Been great to see the amazon cloud native integration working well. E. C. S very popular. Every interview I've done at reinvent uh every year it gets better and better more adoption every year. Um Tell us what's going on with amazon E. C. S because you have Pcs anywhere and now that's being available. >>Yeah that's fine, that's correct, join and uh yeah so customers has been appreciating the value and the simplicity of VCS for many years now. I mean we we launched GCS back in 2014 and we have seen great adoption of the product and customers has always been appreciating. Uh the fact that it was easy to operate and easy to use. Uh This is a journey with the CS anywhere that started a few years ago actually. And we started this journey uh listening to customers that had particular requirements. Um I'd like to talk about, you know, the the law of the land and the law um uh of the physic where customers wanted to go all in into uh into the cloud, but they did have this exception that they need to uh deal with with the application that could not move to the cloud. So as I said, this journey started three years ago when we launched outpost. Um and outpost is our managed infrastructure that customers can deploy in their own data centers. And we supported Pcs on day one on outpost. Um having that said, there are lots of customers that came to us and said we love outputs but there are certain applications and certain requirements, uh such as compliance or the fact simply that we have like assets that we need to reuse in our data center uh that we want to use and before we move into into the cloud. So they were asking us, we love the simplicity of Vcs but we have to use gears that we have in our data center. That is when we started thinking about Pcs anywhere. So basically the idea of VCS anywhere is that you can use e c s E C as part of that, you know, and love um uh appreciated the simplicity of using Pcs but using your customer managed infrastructure as the data plane, basically what you could do is you can define your application within the Ec. S country plane and deploy those applications on customer own um infrastructure. What that means from a very practical perspective is that you can deploy this application on your managed infrastructure ranging from uh raspberry pis this is the demo that we show the invent when we pronounce um e c s anywhere all the way up to bare metal server, we don't really care about the infrastructure underneath. As long as it supported, the OS is supported. Um we're fine with that. >>Okay, so let's take this to the next level and actually the big theme at dr Connors developer experience, you know, that's kind of want to talk about that and obviously developer productivity and innovation have to go hand in hand. You don't want to stunt the innovation equation, which is cloud, native and scale. Right. So how does the developer experience improve with amazon ECs and anywhere now that I'm on, on premises or in the cloud? Can you take me through? What's the improvements around pcs and the developer? >>Yeah I would argue that the the what you see as anywhere solved is more for operational aspect and the requirements that more that are more akin to the operation team that that they need to meet. Uh We're working very hard to um to improve the developing experience on top of the CS beyond what we're doing with the CS anywhere. So um I'd like to step back a little bit and maybe tell a little bit of a story of why we're working on those things. So um the customer as I said before, continue to appreciate the simplicity and the easier views of E. C. S. However what we learn um over the years is that as we added more features to E. C. S, we ended up uh leveraging more easy. Um AWS services um example uh would be a load balancer integration or secret manager or Fc. Or um other things like service discovery that uses underneath other AWS products like um clubman for around 53. And what happened is that the end user experience, the developer experience became a little bit more complicated because now customers opportunity easy of use of these fully managed services. However they were responsible for time and watering all uh together in the application definition. So what we're working on to simplify this experience is we're working on tools that kind of abstract these um this verbal city that you get with pcs. Um uh An example is a confirmation template that a developer we need to use uh to deploy an application leveraging all of these features. Could then could end up being uh many hundreds of transformation lines um in the in the in the definition of the service. So we're working on new tools and new capabilities to make this experience better. Uh Some of them are C d k uh the copilot cli, dws, copilot cli those are all instruments and technologies and tools that we're building to abstract that um uh verbosity that I was alluding to and this is where actually also the doctor composed integration with the CS falls in. >>Yeah, I'm just gonna ask you that the doctor piece because actually it's dr khan all the developers love containers, they love what they do. Um This is a native, you know, mindset of shifting left with security. How is the relationship with the Docker container ecosystem going with you guys? Can you take him in to explain for the folks here watching this event and participating in the community, explain the relationship with Docker container specifically. >>Yeah, absolutely. Uh so basically we started working with dR many, many years ago, um uh Pcs was based on on DR technology when we launch it. Uh and it's still using uh DR technology and last year we started to collaborate with dR more closely um when DR releases the doctor composed specification um as an open source projects. So basically doctor is trying to use the doctor composed specification to create uh infrastructure product gnostic, uh way to deploy Docker application um uh using those specification in multiple infrastructure as part of these journey, we work with dr to support pcs as a back end um for um for the specification, basically what this means from a very practical perspective, is that you can take a doctor composed an existing doctor composed file. Um and doctor says that there are 650,000 doctor composed files spread across the top and all um uh lose control uh system um over the world. And basically you can take those doctor composed file and uh composed up and deploy transparently um into E. C. S Target on AWS. So basically if we go back to what I was alluding to before, the fact that the developer would need to author many 100 line of confirmation template to be able to take their application and deploy it into the cloud. What they need to do now is um offering a new file, a um a file uh with a very clear and easy to use dr composed syntax composed up and deploy automatically on AWS. Um and using Pcs Fargate um and many other AWS services in the back end. >>And what's the expectation in your mind as you guys look at the container service to anywhere model the on premise and without post, what does he what's the vision? Because that's again, another question mark for me, it's like, okay, I get it totally makes sense. Um, but containers are showing the mainstream enterprises, not the hyper skills. You guys always been kind of the forward thinkers, but you know, main street enterprise, I call it. They're picking up adoption of containers in a massive way. They're looking at cloud native specifically as the place for modern application development period. That's happening. What's the story? Say it again? Because I want to make sure I get this right e C s anywhere if I want to get on premises hybrid, What's it mean for me? >>Uh, this goes back to what I was saying at the beginning. So there are there are there when we have been discussing here are mostly to or token of things. Right. So the fact that we enable these big enterprises to meet their requirements and meet their um their um checkboxes sometimes to be able to deploy outside of AWS when there is a need to do that. This could be for edge use cases or for um using years that exist in the data center. So this is where e c s anywhere is basically trying, this is what uh pcs anywhere is trying to address. There is another orthogonal discussion which is developer experience, uh and that development experience is being addressed by these additional tools. Um what I like to say is that uh the confirmation is becoming a little bit like assembler in a sense, right? It's becoming very low level, super powerful, but very low level and we want to abstract and bring the experience to the next level and make it simple for developers to leverage the simplicity of some of these tools including Docker compose um and and and being able to deploy into the cloud um and getting all the benefits of the cloud scalability, electricity and security. >>I love the assembler analogy because you think about it. A lot of the innovation has been kind of like low level foundational and if you start to see all the open source activity and the customers, the tooling does matter. And I think that's where the ease of use comes in. So the simplicity totally makes sense. Um can you give an example of some simplicity piece? Because I think, you know, you guys, you know, look at looking at ec. S as the cornerstone for simplicity. I get that. Can you give an example to walk us through a day in the life of of an example >>uh in an example of simplicity? Yeah, supposedly in action. Yeah. Well, one of the examples that I usually do and there is this uh, notion of being served less and I think that there is a little bit of a, of an obsession around surveillance and trying to talk about surveillance for so many things. When I talk about the C. S, I like to use another moniker that is version less. So to me, simplicity also means that I do not have to um update my service. Right? So the way E C. S works is that engineering in the service team keeps producing and keeps delivering new features for PCS overnight for customers to wake up in the morning and consuming those features without having to deal with upgrades and updates. I think that this is a very key, um, very key example of simplicity when it comes to e C s that is very hard to find um in other, um, solutions whether there are on prime or in the cloud. >>That's a great example in one of the big complaints I hear just anecdotally around the industry is, you know, the speed of the minds of business, want the apps to move faster and the iteration with some craft obviously with security and making sure things buttoned up, but things get pulled back. It's almost slowed down because the speed of the innovation is happening faster than the compliance of some sort of old governance model or code reviews. I want to approve everything. So there's a balance between making sure what's approved, whether security or some pipeline procedures and what not. >>So that I could have. I cannot agree more with you. Yeah, no, it's absolutely true because I think that we see these very interesting um, uh, economy, I would say between startups moving super fast and enterprises try to move fast but forced to move at their own speed. So when we when we deliver services based on, for example, open source software uh, that customers need to um, look after in terms of upgrade to latest release. What we usually see is start up asking us can you move faster? There is a new version of that software, can you enable us to deploy that version? And then on the other hand of the spectrum, there are these big enterprises trying to move faster but not so much that are asking us can use lower. Can you slow down a little bit? Right, because I cannot keep that pigs. So it's a very it's a very interesting um, um, a very interesting time to be alive. >>You know, one of the, one of the things that pop up into these conversations when you talk, when I talk to VP of engineering of companies and then enterprises that the operational efficiency, you got developer productivity and you've got innovation right, you've got the three kind of things going on there knobs and they all have to turn up. People want more efficiency of the operations, they want more developed productivity and more innovation. What's interesting is you start seeing, okay, it's not that easy. There's also a team formation and I know Andy Jassy kinda referred to this in his keynote at Reinvent last year around thinking differently around your organizational but you know, that could be applied to technologists too. So I'd love to get your thoughts while you're here. I know you blog about this and you tweet about this but this is kind of like okay if these things are all going to be knobs, we turned up innovation efficiency, operationally and develop productivity. What's the makeup of the team? Because some are saying, you have an SRE embedded, you've got the platform engineering, you've got version lists, you got survival is all these things are going on all goodness. But does that mean that the teams have to change? What's your thoughts on that you want to get your perspective? >>Yeah, no, absolutely. I think that there was a joke going around that um as soon as you see a job like VP of devoPS, I mean that is not going to work, right? Because these things are needs to be like embedded into each team, right? There shouldn't be a DEVOPS team or anything, it would be just a way of working. And I totally agree with you that these knobs needs to go insane, right? And you cannot just push too hard on innovation which are not having um other folks um to uh to be able to, you know, keep that pace um with you. And we're trying to health customers with multiple uh tools and services to try to um have not only developers and making developer experience uh better but also helping people that are building these underneath platforms. Like for example, prod on AWS protein is a good example of this, where we're focusing on helping these um teams that are trying to build platforms because they are not looking themselves as being a giant or very fast. But they're they're they're measured on being secure, being compliant and being, you know, within a guardrail uh that an enterprise um regulated enterprise needs to have. So we need to have all of these people um both organizationally as well as with providing tools and technologies that have them in their specific areas um to succeed. >>Yeah. And what's interesting about all this is that you know I think we're also having conversations and and again you're starting to see things more clearly here at dr khan we saw some things that coop con which the joke there was not joke but the observation was it's less about kubernetes which is now becoming boring, lee reliable to more about cloud native applications under the covers with program ability. So as all this is going on there truly is a flip of the script. You can actually re engineer and re factor everything, not just re platform your applications in I. T. At once. Right now there's a window whether it's security or whatever. Now that the containers and and the doctor ecosystem and the container ecosystem and the The kubernetes, you've got KS and you got six far gay and all the stuff of goodness. Companies can actually do this right now. They can actually change everything. This is a unique time. This window might close are certainly changed if you're not on it now, it's the same argument of the folks who got caught in the pandemic and weren't in the cloud got flat footed. So you're seeing that example of if you weren't in the cloud up during the pandemic before the pandemic, you were probably losing during the pandemic, the ones that one where the already guys are in the cloud. Now the same thing is true with cloud native. You're not getting into it now, you're probably gonna be on the wrong side of history. What's your reaction to that? >>Yeah, No, I I I agree totally. I I like to think about this. I usually uh talk about this if I can stay back step back a little bit and I think that in this industry and I have gray areas and I have seen lots of things, I think that there has been too big Democratisation event in 90 that happened and occurred in the last 30 years. So the first one was from, you know from when um the PC technology has been introduced, distributed computing from the mainframe area and that was the first Democratisation step. Right? So everyone had access to um uh computers so they could do things if you if you fast forward to these days. Um uh what happened is that on top of that computer, whatever that became a server or whatever, there is a state a very complex stack of technologies uh that allow you to deployment and develop and deploy your application. Right. But that stack of technology and the complexity of that stack of technology is daunting in some way. Right? So it is in a bit access and democratic access to technology. So to me this is what cloud enabled, Right? So the next step of democratisation was the introduction of services that allow you to bypass that stack, which we call undifferentiated heavy lifting because you know, um you don't get paid for managing, I don't know any M. R. Server or whatever, you get paid for extracting values through application logic from that big stack. So I totally agree with you that we're in a unique position to enable everyone um with what we're building uh to innovate a lot faster and in a more secure way. >>Yeah. And what comes out, I totally agree. And I think that's a great historical view and I think let's bring this down to the present today and then bring this as the as the bridge to the future. If you're a developer you could. And by the way, no matter whether you're programming infrastructure or just writing software or even just calling a PS and rolling your own, composing your services, it's programmable and it's just all accessible. So I think that that's going to change the again back to the three knobs, developer productivity or just people productivity, operational efficiency, which is scale and then innovation, which is the business logic where I think machine learning starts to come in, right? So if you can get the container thing going, you start tapping into that control plane. It's not so much just the data control plane. It's like a software control plane. >>Yeah, no, absolutely. The fact that you can, I mean as I said, I have great hair. So I've seen a lot of things and back in the days, I mean the, I mean the whole notion of being able to call an api and get 10 servers for example or today, 10 containers. It would be like, you know, almost a joke, right? So we spent a lot of time racking and um, and doing so much manual stuff that was so ever prone because we usually talk about velocity and agility, but we, we rarely talk about, you know, the difficulties and the problems that doing things manually introduced in the process, the way that you can get wrong. >>You know, you know, it reminds me of this industry and I was like finally get off my lawn in the old days. I walk to school with no shoes on in the snow. We had to build our own colonel and our own graphics libraries and then now they have all these tools. It's like, you're just an old, you know, coder, but joking aside, you know that experience, you're bringing up appointments for the younger generation who have never loaded a Linux operating system before or had done anything like that level. It's not so much old versus young, it's more of a systems thinking, he said distributed computing. If you look at all the action, it's essentially distributed computing with new software paradigm and it's a system architecture. It's not so much software engineering, software developer, you know, this that it's just basically all engineering at this point, all software. >>It is, it is very much indeed. It's uh, it's whole software, there is no other um, there is no other way to call it. It's um, I mean we go back to talk about, you know, infrastructure as code and everything is now uh corridor software in in in a way. It's, yeah. >>This is great to have you on. Congratulations. A CS anywhere being available. It's great stuff. Um, and great to see you and, and great to have this conversation. Um, amazon web services obviously, uh, the world has has gone super cloud. Uh, now you have distributed computing with edge iot exploding beautifully, which means a lot of new opportunities. So thanks for coming on. >>Thank you very much for having me. It was a pleasure. Okay, cube >>Coverage of Dr Khan 2021 virtual. This is the Cube. I'm John for your host. Thanks for watching.

>>law from Las Vegas. It's the Q covering a ws re invent 2019. Brought to you by Amazon Web service is and in along with its ecosystem partners. >>Okay, Welcome back, everyone. Cube coverage. Las Vegas live action. It was re invent 2019 3rd day of a massive show where our seventh year of the eight years of Abel documenting the history and the rise in the changing landscape of the business. I'm John for Bruce. To Minutemen, my co host. Our next guest Bill McGee, senior vice president, general manager of the Hybrid Cloud Security group within Trend Micro. So, this company, those guys now lead executive of the Cloud Hybrid. I have rid Cloud Security hybrid in there looking cute. >>And I've been to every reinvent, every single one. >>Congratulations. Thank you. >>Thank you. Nice to be >>here. So, eight years, what's changed in your mind? Real quick. >>Uh, wow. The Yeah, certainly. The amount of a dot Uh, the amount of adoption is now massive mainstream. You don't have the question. Should I go to the cloud? It's all about how and how much. Probably the biggest change we've seen is how it's really being embraced all around the world where a global company we saw initially a US on Australia type focused you K. Now it's all over the place and it's really relevant everywhere, >>you know, at least from my standpoint. And I have enough friends of mine in the security industry. When we first started coming to show, I mean security was here. Security is not only is so front and center in the discussion of cloud that they had all show for it here, so you know, it gives the 2019 view of security inside that the broader hybrid cloud discussion here, a re >>investor. Let me tell you a couple of things, kind of what we're seeing within our customer base and then what matters from a security perspective. So we see, you know, some organizations doing cloud migration moving. We're close to the cloud of various forms. Had a couple of meetings yesterday. One was college evacuating their data center. The other one was celebrating that two weeks ago they closed their data center, So that's a big step. Windows and Lennox workloads moving to the cloud and really changing existing security controls toe work better in the cloud. But certainly what a lot of these cloud builders are here for is, you know, developing cloud native applications. Originally back 78 years ago, that was on top of what's now seem like pretty simple. Service is like s three E. C two. I've got containers and server lists and other platforms that that people are using. And then the last thing. A lot of companies are establishing a cloud centre of excellence, and they're trying to optimize the use of the cloud. They still have compliance requirements that they need to achieve. So these are what we see happening and really the challenge for the customer. How do we secure all this? How do we secure the aggressive, aggressive cloud Native application development? How do we help a customer achieve compliance easily from a cloud centre of excellence? So that's where we see us fitting. And we made a big announcement a couple of weeks ago about a new platform that we've created. I would love to talk to >>love that. Let's dig into that. But first we were at reinforces Amazons First security, Carver's David Locked and I were talking about cloud security was on Prem security and then what's happening here and had a conversation with someone who was close to the C I. A. Can't say his or her name. And they said Cloud has changed the game for them because they're cost line was pretty much flat. But the demand for missions were squirrels going scaling. So we're seeing that same dynamic. You were referring to it earlier that costs and data centers is kind of flat. But the demand for application new stuff's happened, so there's a real increased her demand for APS. Sure, this is the real driver, how people are flexing and deploying technology. So the security becomes really the built in conversation, cracked comment on that dynamic. And what do you recommend? Well, so here's a couple >>of things we've seen, Really? You know, again, we've been doing private security for about a decade, and really it was primarily focused on one service of eight of us, which is easy to now that's a pretty darn big service and widely used within their customer base. There's no 170 service's, I think is the most recent number. So the developers are embracing all these new service is we acquired a new capability in October. Company called Cloud Conformity, based in Sydney, Australia, very focused on AWS, analyzes implementations against the eight of US well-architected framework. So the first step we see for customers is you gotta get visibility into use of the cloud for the security team. What service is air being used, then? Can you set up a set of security guard rails to allow those service is to be used in a secure manner. Then we help our customers turn to more detailed, specialized protection of easy to or containers or server list. So that's what we've recognized ourselves. We had to create a very modest version of what Amazon has created themselves, which is a platform that allows builders to connect to and choose what security service is they want. >>Road is your service bases and all the service's air. You guys now pick and choose the wall. Yeah, there's a main ones. What does highlight? So >>there's Yeah, I'll give you the ones where we provide a very large breath of protection. So in the what we're calling Cloud one conformity service. So that's this technology we acquired a couple months ago. It cuts across about 70 service is right now and gives you visibility of potential security configuration errors that you have in your environment now if it's in a deaf team, maybe not such a big deal. But if it's in production, that is a big deal. Even better, you can scan your cloud formacion templates on the way to being live. Then we have a set of specialized protection that you know will run on a workload and protect it protected containerized environment. A library that can sit within a server lis application. That's kind of how we look at it. All right, >>So, Bill, one of things of going to the more and more cloud for customers is that there's that shared responsibility. Modern. We know that security is everyone's responsibility. It needs to be built in from the ground up. How are your customers doing with that shift? And are they understanding what they need to do? There have been some pretty visible, like a weight. I really had to configure that. I've thought about that Amazons trying to close the gap on song. But for some of those, >>we've seen a big positive change over the years. Initially I would say that there was what I would call a naive perception that the cloud with magic and it was perfectly secure and that I don't have to worry about it, right. Amazon data did the industry a real favor by establishing the shared responsibility model and making crystal clear what they've got covered that you don't need to worry about anymore as a customer. And then what are the capabilities you still need? Toe worry about? They've delivered a set of security tools that help their customers, and then they rely on partners like us. Thio deliver a set of more in depth tools. Thio, you know, specialized market. >>You actually used a word that we've been talking about a lot this week. Naive. Yeah. So we said, there's, you know, the one letter difference between being cloud native meeting Cloud naive there. Yeah. What does it mean to be cloud native in the security world? >>Well, I would say what allows you to be so first, the most important thing in every customer's mind. I don't care how good the security capabilities you're helping with me with. If you're going to slow down the improvements that I've just made to my development lifecycle. I'm not interested. So that is the most important thing is, are you able to inject your security technology and allow the customer to deliver at the rate that they're currently or continuing to improve? That is by far the most important thing. Then it's our your controls, fitting into an environment in a way that that are as easy as possible for the customer. One part that's been very critical for us. We've been a lead adopter of the AWS marketplace, allowing customers too procure security technology easily. They don't actually have to talk to us to buy our product. That's pretty revolutionary >>about the number of breaches that I'm going on, What's changed with you guys over the year because new vectors air coming out at this more surface area. Obviously, it's been discussed. What's changed most in your I'll >>tell you what we're worried about and what we expect to see, although I would say the evidence. It's early, uh, the reality in our traditional data centers. They were so porous at runtime in terms of the infrastructure and vulnerabilities that it was relatively easy for Attackers to get in the cloud has actually improved the level of security because of automation, less configuration errors. Unfortunately, what we expect his Attackers >>to move to. >>The developers moved to the depth pipeline, injecting code not a run time, but injecting it earlier in the life cycle. We've seen evidence of container images up on Dr Hub getting infected and then developers just pulling in without thinking about it. That's where Attackers are going to move to the depth pipeline. And we need to move some of our security technology to the dead pipeline toe, help customers defend themselves. >>What about International Geo Geo issues around compliance. How is that changing the game or slowing it down? Or I'm sailing it or you talk about that dynamic with regions? Are you >>sure you know us is the most innovative market and the most risk taking market, and therefore people moved to the cloud quite bravely over this over this decade. Some of the markets So, for example, were Japanese headquarters company. In general, Japanese companies, you know, really taken to a lot of considerations before they make that type of big bet. But now we're seeing it. We're seeing auto manufacturers embrace the cloud. So I think those it was a struggle for us in the early days. How regional the adoption of Cloud was. That's not the case anymore. It's really a relevant conversation in every one of our markets. >>Bill. Thank you for coming on the Cuban Sharing your insights Hybrid Cloud Security Got to ask you to end the segment. Yeah, What is going on for you This year? I'll see hybrids in your title. Operating models. Cloud center, gravity clouds going to the edge or data center. Just operate model. What's on your mind this year? What are you trying to do? Accomplish what you excited >>about? What? We're really excited about what this product announcement we made, called Cloud One. And what Cloud one is, is a set of Security Service's, which customers can access through common common access common building infrastructure, common cloud account management and choose what to use. You know, Andy put it pretty well in his keynote where you know he talked about He doesn't think of aws, a Swiss Army knife. He thinks of it as a specialized set of tools that builders get to adopt. We want to create a set of security tools in a similar way where customers can choose which of these specialized security service is that they want to adopt >>Bill. Great pleasure to meet you and have this conversation pro and then security area entrepreneur sold his company to Trend Micro. This is the hybrid world. It's all about the cloud operating model. So about agility and getting things done with application developers. This cube bringing all the data from reinvent stables for more coverage after this short break.

(intro music) >> Good afternoon guys and gals. Welcome back to The Strip, Las Vegas. It's "theCUBE" live day four of our coverage of "AWS re:Invent". Lisa Martin, Dave Vellante. Dave, we've had some awesome conversations the last four days. I can't believe how many people are still here. The AWS ecosystem seems stronger than ever. >> Yeah, last year we really noted the ecosystem, you know, coming out of the isolation economy 'cause everybody had this old pent up demand to get together and the ecosystem, even last year, we were like, "Wow." This year's like 10x wow. >> It really is 10x wow, it feels that way. We're going to have a 10x wow conversation next. We're bringing back DataStax to "theCUBE". Please welcome Thomas Bean, it's CMO. Thomas welcome to "theCUBE". >> Thanks, thanks a lot, thanks for having me. >> Great to have you, talk to us about what's going on at DataStax, it's been a little while since we talked to you guys. >> Indeed, so DataStax, we are the realtime data company and we've always been involved in technology such as "Apache Cassandra". We actually created to support and take this, this great technology to the market. And now we're taking it, combining it with other technologies such as "Apache Pulse" for streaming to provide a realtime data cloud. Which helps our users, our customers build applications faster and help them scale without limits. So it's all about mobilizing all of this information that is going to drive the application going to create the awesome experience, when you have a customer waiting behind their mobile phone, when you need a decision to take place immediately to, that's the kind of data that we, that we provide in the cloud on any cloud, but especially with, with AWS and providing the performance that technologies like "Apache Cassandra" are known for but also with market leading unit economics. So really empowering customers to operate at speed and scale. >> Speaking of customers, nobody wants less data slower. And one of the things I think we learned in the in the pan, during the pandemic was that access to realtime data isn't nice to have anymore for any business. It is table stakes, it's competitive advantage. There's somebody right behind in the rear view mirror ready to take over. How has the business model of DataStax maybe evolved in the last couple of years with the fact that realtime data is so critical? >> Realtime data has been around for some time but it used to be really niches. You needed a lot of, a lot of people a lot of funding actually to, to implement these, these applications. So we've adapted to really democratize it, made super easy to access. Not only to start developing but also scaling. So this is why we've taken these great technologies made them serverless cloud native on the cloud so that developers could really start easily and scale. So that be on project products could be taken to the, to the market. And in terms of customers, the patterns is we've seen enterprise customers, you were talking about the pandemic, the Home Depot as an example was able to deliver curbside pickup delivery in 30 days because they were already using DataStax and could adapt their business model with a real time application that combines you were just driving by and you would get the delivery of what exactly you ordered without having to go into the the store. So they shifted their whole business model. But we also see a real strong trend about customer experiences and increasingly a lot of tech companies coming because scale means success to them and building on, on our, on our stack to, to build our applications. >> So Lisa, it's interesting. DataStax and "theCUBE" were started the same year, 2010, and that's when it was the beginning of the ascendancy of the big data era. But of course back then there was, I mean very little cloud. I mean most of it was on-prem. And so data stacks had, you know, had obviously you mentioned a number of things that you had to do to become cloud friendly. >> Thomas: Yes. >> You know, a lot of companies didn't make it, make it through. You guys just raised a bunch of dough as well last summer. And so that's been quite a transformation both architecturally, you know, bringing the customers through. I presume part of that was because you had such a great open source community, but also you have a unique value problem. Maybe you could sort of describe that a little. >> Absolutely, so the, I'll start with the open source community where we see a lot of traction at the, at the moment. We were always very involved with, with the "Apache Cassandra". But what we're seeing right now with "Apache Cassandra" is, is a lot of traction, gaining momentum. We actually, we, the open source community just won an award, did an AMA, had a, a vote from their readers about the top open source projects and "Apache Cassandra" and "Apache Pulse" are part of the top three, which is, which is great. We also run a, in collaboration with the Apache Project, the, a series of events around the, around the globe called "Cassandra Days" where we had tremendous attendance. We, some of them, we had to change venue twice because there were more people coming. A lot of students, a lot of the big users of Cassandra like Apple, Netflix who spoke at these, at these events. So we see this momentum actually picking up and that's why we're also super excited that the Linux Foundation is running the Cassandra Summit in in March in San Jose. Super happy to bring that even back with the rest of the, of the community and we have big announcements to come. "Apache Cassandra" will, will see its next version with major advances such as the support of asset transactions, which is going to make it even more suitable to more use cases. So we're bringing that scale to more applications. So a lot of momentum in terms of, in terms of the, the open source projects. And to your point about the value proposition we take this great momentum to which we contribute a lot. It's not only about taking, it's about giving as well. >> Dave: Big committers, I mean... >> Exactly big contributors. And we also have a lot of expertise, we worked with all of the members of the community, many of them being our customers. So going to the cloud, indeed there was architectural work making Cassandra cloud native putting it on Kubernetes, having the right APIs for developers to, to easily develop on top of it. But also becoming a cloud company, building customer success, our own platform engineering. We, it's interesting because actually we became like our partners in a community. We now operate Cassandra in the cloud so that all of our customers can benefit from all the power of Cassandra but really efficiently, super rapidly, and also with a, the leading unit economies as I mentioned. >> How will the, the asset compliance affect your, you know, new markets, new use cases, you know, expand your TAM, can you explain that? >> I think it will, more applications will be able to tap into the power of, of "NoSQL". Today we see a lot on the customer experience as IOT, gaming platform, a lot of SaaS companies. But now with the ability to have transactions at the database level, we can, beyond providing information, we can go even deeper into the logic of the, of the application. So it makes Cassandra and therefore Astra which is our cloud service an even more suitable database we can address, address more even in terms of the transaction that the application itself will, will support. >> What are some of the business benefits that Cassandra delivers to customers in terms of business outcomes helping businesses really transform? >> So Cassandra brings skill when you have millions of customers, when you have million of data points to go through to serve each of the customers. One of my favorite example is Priceline, who runs entirely on our cloud service. You may see one offer, but it's actually everything they know about you and everything they have to offer matched while you are refreshing your page. This is the kind of power that Cassandra provide. But the thing to say about "Apache Cassandra", it used to be also a database that was a bit hard to manage and hard to develop with. This is why as part of the cloud, we wanted to change these aspects, provide developers the API they like and need and what the application need. Making it super simple to operate and, and, and super affordable, also cost effective to, to run. So the the value to your point, it's time to market. You go faster, you don't have to worry when you choose the right database you're not going to, going to have to change horse in the middle of the river, like sixth month down the line. And you know, you have the guarantee that you're going to get the performance and also the best, the best TCO which matters a lot. I think your previous person talking was addressing it. That's also important especially in the, in a current context. >> As a managed service, you're saying, that's the enabler there, right? >> Thomas: Exactly. >> Dave: That is the model today. I mean, you have to really provide that for customers. They don't want to mess with, you know, all the plumbing, right? I mean... >> Absolutely, I don't think people want to manage databases anymore, we do that very well. We take SLAs and such and even at the developer level what they want is an API so they get all the power. All of of this powered by Cassandra, but now they get it as a, and it's as simple as using as, as an API. >> How about the ecosystem? You mentioned the show in in San Jose in March and the Linux Foundation is, is hosting that, is that correct? >> Yes, absolutely. >> And what is it, Cassandra? >> Cassandra Summit. >> Dave: Cassandra Summit >> Yep. >> What's the ecosystem like today in Cassandra, can you just sort of describe that? >> Around Cassandra, you have actually the big hyperscalers. You have also a few other companies that are supporting Cassandra like technologies. And what's interesting, and that's been a, a something we've worked on but also the "Apache Project" has worked on. Working on a lot of the adjacent technologies, the data pipelines, all of the DevOps solutions to make sure that you can actually put Cassandra as part of your way to build these products and, and build these, these applications. So the, the ecosystem keeps on, keeps on growing and actually the, the Cassandra community keeps on opening the database so that it's, it's really easy to have it connect to the rest of the, the rest environment. And we benefit from all of this in our Astra cloud service. >> So things like machine learning, governance tools that's what you would expect in the ecosystem forming around it, right? So we'll see that in March. >> Machine learning is especially a very interesting use case. We see more and more of it. We recently did a, a nice video with one of our customers called Unifour who does exactly this using also our abstract cloud service. What they provide is they analyze videos of sales calls and they help actually the sellers telling them, "Okay here's what happened here was the customer sentiment". Because they have proof that the better the sentiment is, the shorter the sell cycle is going to be. So they teach the, the sellers on how to say the right things, how to control the thing. This is machine learning applied on video. Cassandra provides I think 200 data points per second that feeds this machine learning. And we see more and more of these use cases, realtime use cases. It happens on the fly when you are on your phone, when you have a, a fraud maybe to detect and to prevent. So it is going to be more and more and we see more and more of these integration at the open source level with technologies like even "Feast" project like "Apache Feast". But also in the, in, in the partners that we're working with integrating our Cassandra and our cloud service with. >> Where are customer conversations these days, given that every company has to be a data company. They have to be able to, to democratize data, allow access to it deep into the, into the organizations. Not just IT or the data organization anymore. But are you finding that the conversations are rising up the, up the stack? Is this, is this a a C-suite priority? Is this a board level conversation? >> So that's an excellent question. We actually ran a survey this summer called "The State of the Database" where we, we asked these tech leaders, okay what's top of mind for you? And real time actually was, was really one of the top priorities. And they explained for the one that who call themselves digital leaders that for 71% of them they could correlate directly the use of realtime data, the quality of their experience or their decision making with revenue. And that's really where the discussion is. And I think it's something we can relate to as users. We don't want the, I mean if the Starbucks apps take seconds to to respond there will be a riot over there. So that's, that's something we can feel. But it really, now it's tangible in, in business terms and now then they take a look at their data strategy, are we equipped? Very often they will see, yeah, we have pockets of realtime data, but we're not really able to leverage it. >> Lisa: Yeah. >> For ML use cases, et cetera. So that's a big trend that we're seeing on one end. On the other end, what we're seeing, and it's one of the things we discussed a lot at the event is that yeah cost is important. Growth at all, at all cost does not exist. So we see a lot of push on moving a lot of the workloads to the cloud to make them scale but at the best the best cost. And we also see some organizations where like, okay let's not let a good crisis go to waste and let's accelerate our innovation not at all costs. So that we see also a lot of new projects being being pushed but reasonable, starting small and, and growing and all of this fueled by, by realtime data, so interesting. >> The other big topic amongst the, the customer community is security. >> Yep. >> I presume it's coming up a lot. What's the conversation like with DataStax? >> That's a topic we've been working on intensely since the creation of Astra less than two years ago. And we keep on reinforcing as any, any cloud provider not only our own abilities in terms of making sure that customers can manage their own keys, et cetera. But also integrating to the rest of the, of the ecosystem when some, a lot of our customers are running on AWS, how do we integrate with PrivateLink and such? We fit exactly into their security environment on AWS and they use exactly the same management tool. Because this is also what used to cost a lot in the cloud services. How much do you have to do to wire them and, and manage. And there are indeed compliance and governance challenges. So that's why making sure that it's fully connected that they have full transparency on what's happening is, is a big part of the evolution. It's always, security is always something you're working on but it's, it's a major topic for us. >> Yep, we talk about that on pretty much every event. Security, which we could dive into, but we're out of time. Last question for you. >> Thomas: Yes. >> We're talking before we went live, we're both big Formula One fans. Say DataStax has the opportunity to sponsor a team and you get the whole side pod to, to put like a phrase about DataStax on the side pod of this F1 car. (laughter) Like a billboard, what does it say? >> Billboard, because an F1 car goes pretty fast, it will be hard to, be hard to read but, "Twice the performance at half the cost, try Astra a cloud service." >> Drop the mike. Awesome, Thomas, thanks so much for joining us. >> Thank for having me. >> Pleasure having you guys on the program. For our guest, Thomas Bean and Dave Vellante, I'm Lisa Martin and you're watching "theCUBE" live from day four of our coverage. "theCUBE", the leader in live tech coverage. (outro music)

(lively music) >> Good afternoon cloud community and welcome back to beautiful Las Vegas, Nevada. We are here at AWS re:Invent, day four of our wall to wall coverage. It is day four in the afternoon and we are holding strong. I'm Savannah Peterson, joined by my fabulous co-host Paul Gillen. Paul, how you doing? >> I'm doing well, fine Savannah. You? >> You look great. >> We're in the home stretch here. >> Yeah, (laughs) we are. >> You still look fresh as a daisy. I don't know how you do it. >> (laughs) You're too kind. You're too kind, but I'm vain enough to take that compliment. I'm very excited about the conversation that we're going to have up next. We get to get a little DevRel and we got a little swagger on the stage. Welcome, Austin. How you doing? >> Hey, great to be here. Thanks for having me. >> Savannah: Yeah, it's our pleasure. How's the show been for you so far? >> Busy, exciting. Feels a lot like, you know it used to be right? >> Yeah, I know. A little reminiscent of the before times. >> Well, before times. >> Before we dig into the technical stuff, you're the most intriguingly dressed person we've had on the show this week. >> Austin: I feel extremely underdressed. >> Well, and we were talking about developer fancy. Talk to me a little bit about your approach to fashion. Wasn't expecting to lead with this, but I like this but I like this actually. >> No, it's actually good with my PR. You're going to love it. My approach, here's the thing, I give free advice all the time about developer relations, about things that work, have worked, and don't work in community and all that stuff. I love talking about that. Someone came up to me and said, "Where do you get your fashion tips from? What's the secret Discord server that I need to go on?" I'm like, "I will never tell." >> Oh, okay. >> This is an actual trait secret. >> Top secret. Wow! Talk about. >> If someone else starts wearing the hat, then everyone's going to be like, "There's so many white guys." Look, I'm a white guy with a beard that works in technology. >> Savannah: I've never met one of those. >> Exactly, there's none of them at all. So, you have to do something to kind stand out from the crowd a little bit. >> I love it, and it's a talk trigger. We're talking about it now. Production team loved it. It's fantastic. >> It's great. >> So your DevRel for Lightstep, in case the audience isn't familiar tell us about Lightstep. >> So Lightstep is a cloud native observability platform built at planet scale, and it powers observability at some places you've heard of like Spotify, GitHub, right? We're designed to really help developers that are working in the cloud with Kubernetes, with these huge distributed systems, understand application performance and being able to find problems, fix problems. We're also part of the ServiceNow family and as we all know ServiceNow is on a mission to help the world of work work better by powering digital transformation around IT and customer experiences for their many, many, many global 2000 customers. We love them very much. >> You know, it's a big love fest here. A lot of people have talked about the collaboration, so many companies working together. You mentioned unified observability. What is unified observability? >> So if you think about a tradition, or if you've heard about this traditional idea of observability where you have three pillars, right? You have metrics, and you have logs, and you have traces. All those three things are different data sources. They're picked up by different tools. They're analyzed by different people for different purposes. What we believe and what we're working to accomplish right now is to take all that and if you think those pillars, flip 'em on their side and think of them as streams of data. If we can take those streams and integrate them together and let you treat traces and metrics and logs not as these kind of inviolate experiences where you're kind of paging between things and going between tab A to tab B to tab C, and give you a standard way to query this, a standard way to display this, and letting you kind of find the most relevant data, then it really unlocks a lot of power for like developers and SREs to spend less time like managing tools. You know, figuring out where to build their query or what dashboard to check, more just being able to like kind of ask a question, get an answer. When you have an incident or an outage that's the most important thing, right? How quickly can you get those answers that you need so that you can restore system health? >> You don't want to be looking in multiple spots to figure out what's going on. >> Absolutely. I mean, some people hear unified observability and they go to like tool consolidation, right? That's something I hear from a lot of our users and a lot of people in re:Invent. I'll talk to SREs, they're like, "Yeah, we've got like six or seven different metrics products alone, just on services that they cover." It is important to kind of consolidate that but we're really taking it a step lower. We're looking at the data layer and trying to say, "Okay, if the data is all consistent and vendor neutral then that gives you flexibility not only from a tool consolidation perspective but also you know, a consistency, reliability. You could have a single way to deploy your observability out regardless of what cloud you're on, regardless if you're using Kubernetes or Fargate or whatever else. or even just Bare Metal or EC2 Bare Metal, right? There's been so much historically in this space. There's been a lot of silos and we think that unify diversability means that we kind of break down those silos, right? The way that we're doing it primarily is through a project called OpenTelemetry which you might have heard of. You want to talk about that in a minute? . >> Savannah: Yeah, let's talk about it right now. Why don't you tell us about it? Keep going, you're great. You're on a roll. >> I am. >> Savannah: We'll just hang out over here. >> It's day four. I'm going to ask the questions and answer the questions. (Savannah laughs) >> Yes, you're right. >> I do yeah. >> Open Tele- >> OpenTelemetry . >> Explain what OpenTelemetry is first. >> OpenTelemetry is a CNCF project, Cloud Native Computing Foundation. The goal is to make telemetry data, high quality telemetry data, a builtin feature of cloud native software right? So right now if you wanted to get logging data out, depending on your application stack, depending on your application run time, depending on language, depending on your deployment environment. You might have a lot... You have to make a lot of choices, right? About like, what am I going to use? >> Savannah: So many different choices, and the players are changing all the time. >> Exactly, and a lot of times what people will do is they'll go and they'll say like, "We have to use this commercial solution because they have a proprietary agent that can do a lot of this for us." You know? And if you look at all those proprietary agents, what you find very quickly is it's very commodified right? There's no real difference in what they're doing at a code level and what's stopped the industry from really adopting a standard way to create this logs and metrics and traces, is simply just the fact that there was no standard. And so, OpenTelemetry is that standard, right? We've got dozens of companies many of them like very, many of them here right? Competitors all the same, working together to build this open standard and implementation of telemetry data for cloud native software and really any software right? Like we support over 12 languages. We support Kubernetes, Amazon. AWS is a huge contributor actually and we're doing some really exciting stuff with them on their Amazon distribution of OpenTelemetry. So it's been extremely interesting to see it over the past like couple years go from like, "Hey, here's this like new thing that we're doing over here," to really it's a generalized acceptance that this is the way of the future. This is what we should have been doing all along. >> Yeah. >> My opinion is there is a perception out there that observability is kind of a commodity now that all the players have the same set of tools, same set of 15 or 17 or whatever tools, and that there's very little distinction in functionality. Would you agree with that? >> I don't know if I would characterize it that way entirely. I do think that there's a lot of duplicated effort that happens and part of the reason is because of this telemetry data problem, right? Because you have to wind up... You know, there's this idea of table stakes monitoring that we talk about right? Table stakes monitoring is the stuff that you're having to do every single day to kind of make sure your system is healthy to be able to... When there's an alert, gets triggered, to see why it got triggered and to go fix it, right? Because everyone has the kind of work on that table stake stuff and then build all these integrations, there's very little time for innovation on top of that right? Because you're spending all your time just like working on keeping up with technology. >> Savannah: Doing the boring stuff to make sure the wheels don't fall off, basically. >> Austin: Right? What I think the real advantage of OpenTelemetry is that it really, from like a vendor perspective, like it unblocks us from having to kind of do all this repetitive commodified work. It lets us help move that out to the community level so that... Instead of having to kind of build, your Kubernetes integration for example, you can just have like, "Hey, OpenTelemetry is integrated into Kubernetes and you just have this data now." If you are a commercial product, or if you're even someone that's interested in fixing a, scratching a particular itch about observability. It's like, "I have this specific way that I'm doing Kubernetes and I need something to help me really analyze that data. Well, I've got the data now I can just go create a project. I can create an analysis tool." I think that's what you'll see over time as OpenTelemetry promulgates out into the ecosystem is more people building interesting analysis features, people using things like machine learning to analyze this large amount, large and consistent amount of OpenTelemetry data. It's going to be a big shakeup I think, but it has the potential to really unlock a lot of value for our customers. >> Well, so you're, you're a developer relations guy. What are developers asking for right now out of their observability platforms? >> Austin: That's a great question. I think there's two things. The first is that they want it to just work. It's actually the biggest thing, right? There's so many kind of... This goes back to the tool proliferation, right? People have too much data in too many different places, and getting that data out can still be really challenging. And so, the biggest thing they want is just like, "I want something that I can... I want a lot of these questions I have to ask, answered already and OpenTelemetry is going towards it." Keep in mind it's the project's only three years old, so we obviously have room to grow but there are people running it in production and it works really well for them but there's more that we can do. The second thing is, and this isn't what really is interesting to me, is it's less what they're asking for and more what they're not asking for. Because a lot of the stuff that you see people, saying around, "Oh, we need this like very specific sort of lower level telemetry data, or we need this kind of universal thing." People really just want to be able to get questions or get questions answered, right? They want tools that kind of have these workflows where you don't have to be an expert because a lot of times this tooling gets locked behind sort of is gate kept almost in a organization where there are teams that's like, "We're responsible for this and we're going to set it up and manage it for you, and we won't let you do things outside of it because that would mess up- >> Savannah: Here's your sandbox and- >> Right, this is your sandbox you can play in and a lot of times that's really useful and very tuned for the problems that you saw yesterday, but people are looking at like what are the problems I'm going to get tomorrow? We're deploying more rapidly. We have more and more intentional change happening in the system. Like it's not enough to have this reactive sort of approach where our SRE teams are kind of like or this observability team is building a platform for us. Developers want to be able to get in and have these kind of guided workflows really that say like, "Hey, here's where you're starting at. Let's get you to an answer. Let's help you find the needle in the haystack as it were, without you having to become a master of six different or seven different tools." >> Savannah: Right, and it shouldn't be that complicated. >> It shouldn't be. I mean we've certainly... We've been working on this problem for many years now, starting with a lot of our team that started at Google and helped build Google's planet scale monitoring systems. So we have a lot of experience in the field. It's actually one... An interesting story that our founder or now general manager tells BHS, Ben Sigelman, and he told me this story once and it's like... He had built this really cool thing called Dapper that was a tracing system at Google, and people weren't using it. Because they were like, "This is really cool, but I don't know how to... but it's not relevant to me." And he's like, the one thing that we did to get to increase usage 20 times over was we just put a link. So we went to the place that people were already looking for that data and we added a link that says, "Hey, go over here and look at this." It's those simple connections being able to kind of draw people from like point A to point B, take them from familiar workflows into unfamiliar ones. You know, that's how we think about these problems right? How is this becoming a daily part of someone's usage? How is this helping them solve problems faster and really improve their their life? >> Savannah: Yeah, exactly. It comes down to quality of life. >> Warner made the case this morning that computer architecture should be inherently event-driven and that we are moving toward a world where the person matters less than what the software does, right? The software is triggering events. Does this complicate observability or simplify it? >> Austin: I think that at the end of the day, it's about getting the... Observability to me in a lot of ways is about modeling your system, right? It's about you as a developer being able to say this is what I expect the system to do and I don't think the actual application architecture really matters that much, right? Because it's about you. You are building a system, right? It can be event driven, can be support request response, can be whatever it is. You have to be able to say, "This is what I expect to... For these given inputs, this is the expected output." Now maybe there's a lot of stuff that happens in the middle that you don't really care about. And then, I talk to people here and everyone's talking about serverless right? Everyone... You can see there's obviously some amazing statistics about how many people are using Lambda, and it's very exciting. There's a lot of stuff that you shouldn't have to care about as a developer, but you should care about those inputs and outputs. You will need to have that kind of intermediate information and understand like, what was the exact path that I took through this invented system? What was the actual resources that were being used? Because even if you trust that all this magic behind the scenes is just going to work forever, sometimes it's still really useful to have that sort of lower level abstraction, to say like, "Well, this is what actually happened so that I can figure out when I deployed a new change, did I make performance better or worse?" Or being able to kind of segregate your data out and say like... Doing AB testing, right? Doing canary releases, doing all of these things that you hear about as best practices or well architected applications. Observability is at the core of all that. You need observability to kind of do any of, ask any of those higher level interesting questions. >> Savannah: We are here at ReInvent. Tell us a little bit more about the partnership with AWS. >> So I would have to actually probably refer you to someone at Service Now on that. I know that we are a partner. We collaborate with them on various things. But really at Lightstep, we're very focused on kind of the open source part of this. So we work with AWS through the OpenTelemetry project, on things like the AWS distribution for OpenTelemetry which is really... It's OpenTelemetry, again is really designed to be like a neutral standard but we know that there are going to be integrators and implementers that need to package up and bundle it in a certain way to make it easy for their end users to consume it. So that's what Amazon has done with ADOT which is the shortening for it. So it's available in several different ways. You can use it as like an SDK and drop it into your application. There's Lambda layers. If you want to get Lambda observability, you just add this extension in and then suddenly you're getting OpenTelemetry data on the other side. So it's really cool. It's been a really exciting to kind of work with people on the AWS side over the past several years. >> Savannah: It's exciting, >> I've personally seen just a lot of change. I was talking to a PM earlier this week... It's like, "Hey, two years ago I came and talked to you about OpenTelemetry and here we are today. You're still talking about OpenTelemetry." And they're like, "What changes?" Our customers have started coming to us asking for OpenTelemetry and we see the same thing now. >> Savannah: Timing is right. >> Timing is right, but we see the same thing... Even talking to ServiceNow customers who are... These very big enterprises, banks, finance, healthcare, whatever, telcos, it used to be... You'd have to go to them and say like, "Let me tell you about distributed tracing. Let me tell you about OpenTelemetry. Let me tell you about observability." Now they're coming in and saying, "Yeah, so we're standard." If you think about Kubernetes and how Kubernetes, a lot of enterprises have spent the past five-six years standardizing, and Kubernetes is a way to deploy applications or manage containerized applications. They're doing the same journey now with OpenTelemetry where they're saying, "This is what we're betting on and we want partners we want people to help us go along that way." >> I love it, and they work hand in hand in all CNCF projects as well that you're talking about. >> Austin: Right, so we're integrated into Kubernetes. You can find OpenTelemetry and things like kept in which is application standards. And over time, it'll just like promulgate out from there. So it's really exciting times. >> A bunch of CNCF projects in this area right? Prometheus. >> Prometheus, yeah. Yeah, so we inter-operate with Prometheus as well. So if you have Prometheus metrics, then OpenTelemetry can read those. It's a... OpenTelemetry metrics are like a super set of Prometheus. We've been working with the Prometheus community for quite a while to make sure that there's really good compatibility because so many people use Prometheus you know? >> Yeah. All right, so last question. New tradition for us here on theCUBE. We're looking for your 32nd hot take, Instagram reel, biggest theme, biggest buzz for those not here on the show floor. >> Oh gosh. >> Savannah: It could be for you too. It could be whatever for... >> I think the two things that are really striking to me is one serverless. Like I see... I thought people were talking about servers a lot and they were talking about it more than ever. Two, I really think it is observability right? Like we've gone from observability being kind of a niche. >> Savannah: Not that you're biased. >> Huh? >> Savannah: Not that you're biased. >> Not that I'm biased. It used to be a niche. I'd have to go niche thing where I would go and explain what this is to people and nowpeople are coming up. It's like, "Yeah, yeah, we're using OpenTelemetry." It's very cool. I've been involved with OpenTelemetry since the jump, since it was started really. It's been very exciting to see and gratifying to see like how much adoption we've gotten even in a short amount of time. >> Yeah, absolutely. It's a pretty... Yeah, it's been a lot. That was great. Perfect soundbite for us. >> Austin: Thanks, I love soundbites. >> Savannah: Yeah. Awesome. We love your hat and your soundbites equally. Thank you so much for being on the show with us today. >> Thank you for having me. >> Savannah: Hey, anytime, anytime. Will we see you in Amsterdam, speaking of KubeCon? Awesome, we'll be there. >> There's some real exciting OpenTelemetry stuff coming up for KubeCon. >> Well, we'll have to get you back on theCUBE. (talking simultaneously) Love that for us. Thank you all for tuning in two hour wall to wall coverage here, day four at AWS re:Invent in fabulous Las Vegas, Nevada, with Paul Gillin. I'm Savannah Peterson and you're watching theCUBE, the leader in high tech coverage. (lively music)

(upbeat music) >> Hi everybody. Welcome back to theCUBE as to continue our coverage here at AWS re:Invent '22. We're in the Venetian. Out in Las Vegas, it is Wednesday. And the PaaS is still happening. I can guarantee you that. We continue our series of discussions as part of the "AWS Startup Showcase". This is the "Global Startup Program", a part of that showcase. And I'm joined by two gentlemen today who are going to talk about what CoreStack is up to. One of them is Ez Natarajan, who is the Founder and CEO. Good to have you- (simultaneous chatter) with us today. We appreciate it. Thanks, EZ. >> Nice to meet you, John. >> And Brad Winney who is the area Sales Leader for startups at AWS. Brad, good to see you. >> Good to see you, John. >> Thanks for joining us here on The Showcase. So Ez, first off, let's just talk about CoreStack a little bit for people at home who might not be familiar with what you do. It's all about obviously data, governance, giving people peace of mind, but much deeper than that. I'll let you take it from there. >> So CoreStack is a governance platform that helps customers maximize their cloud usage and get governance at scale. When we talk about governance, we instill confidence through three layers: solving the problems of the CIO, solving the problems of the CTO, solving the problems of the CFO, together with a single pin of class,- >> John: Mm-hmm. >> which helps them achieve continuous holistic automated outcomes at any given time. >> John: Mm-hmm. So, Brad, follow up on that a little bit- >> Yeah. because Ez touched on it there that he's got a lot of stakeholders- >> Right. >> with a lot of different needs and a lot of different demands- >> Mm-hmm. >> but the same overriding emotion, right? >> Yeah. >> They all want confidence. >> They all want confidence. And one of the trickiest parts of confidence is the governance issue, which is policy. It's how do we determine who has access to what, how we do that scale. And across not only start been a process. This is a huge concern, especially as we talked a lot about cutting costs as the overriding driver for 2023. >> John: Mm-hmm. >> The economic compression being what it is, you still have to do this in a secure way and as a riskless way as possible. And so companies like CoreStack really offer core, no pun intended, (Ez laughs) function there where you abstract out a lot of the complexity of governance and you make governance a much more simple process. And that's why we're big fans of what they do. >> So we think governance from a three dimensional standpoint, right? (speaks faintly) How do we help customers be more compliant, secure, achieve the best performance and operations with increased availability? >> Jaohn: Mm-hmm. >> At the same time do the right spend from a cost standpoint. >> Interviewer: Mm-hmm. So when all three dimensions are connected, the business velocity increases and the customer's ability to cater to their customers increase. So our governance tenants come from these three pillars of finance operations, security operations and air operations at cloud operations. >> Yeah. And... Yeah. Please, go ahead. >> Can I (indistinct)? >> Oh, I'm sorry. Just- >> No, that's fine. >> So part of what's going on here, which is critical for AWS, is if you notice a lot of (indistinct) language is at the business value with key stakeholders of the CTO, the CSO and so on. And we're doing a much better job of speaking business value on top of AWS services. But the AWS partners, again, like CoreStack have such great expertise- >> John: Mm-hmm. >> in that level of dialogue. That's why it's such a key part for us, why we're really interested partnering with them. >> How do you wrestle with this, wrestle may not be the right word, but because you do have, as we just went through these litany, these business parts of your business or a business that need access- >> Ez: Mm-hmm. >> and that you need to have policies in place, but they change, right? I mean, and somebody maybe from the financial side should have a window into data and other slices of their business. There's a lot of internal auditing. >> Man: Mm-hmm. >> Obviously, it's got to be done, right? And so just talk about that process a little bit. How you identify the appropriate avenues or the appropriate gateways for people to- >> Sure. >> access data so that you can have that confidence as a CTO or CSO, that it's all right. And we're not going to let too much- >> out to the wrong people. >> Sure. >> Yeah. So there are two dimensions that drive the businesses to look for that kind of confidence building exercise, right? One, there are regulatory external requirements that say that I know if I'm in the financial industry, I maybe need to following NIST, PCI, and sort of compliances. Or if I'm in the healthcare industry, maybe HIPAA and related compliance, I need to follow. >> John: Mm-hmm. >> That's an external pressure. Internally, the organizations based on their geographical presence and the kind of partners and customers they cater to, they may have their own standards. And when they start adopting cloud; A, for each service, how do I make sure the service is secure and it operates at the best level so that we don't violate any of the internal or external requirements. At the same time, we get the outcome that is needed. And that is driven into policies, that is driven into standards which are consumable easily, like AWS offers well-architected framework that helps customers make sure that I know I'm architecting my application workloads in a way that meets the business demands. >> John: Mm-hmm. >> And what CoreStack has done is taken that and automated it in such a way it helps the customers simplify that process to get that outcome measured easily so they get that confidence to consume more of the higher order services. >> John: Okay. And I'm wondering about your relationship as far with AWS goes, because, to me, it's like going deep sea fishing and all of a sudden you get this big 4, 500 pound fish. Like, now what? >> Mm-hmm. >> Now what do we do because we got what we wanted? So, talk about the "Now what?" with AWS in terms of that relationship, what they're helping you with, and the kind of services that you're seeking from them as well. >> Oh, thanks to Brad and the entire Global Startup Ecosystem team at AWS. And we have been part of AWS Ecosystem at various levels, starting from Marketplace to ISV Accelerate to APN Partners, Cloud Management Tools Competency Partner, Co-Sell programs. The team provides different leverages to connect to the entire ecosystem of how AWS gets consumed by the customers. Customers may come through channels and partners. And these channels and partners maybe from WAs to MSPs to SIs to how they really want to use each. >> John: Mm-hmm. >> And the ecosystem that AWS provides helps us feed into all these players and provide this higher order capability which instills confidence to the customers end of the day. >> Man: Absolutely. Right. >> And this can be taken through an MSP. This can be taken through a GSI. This can be taken to the customer through a WA. And that's how our play of expansion into larger AWS customer base. >> Brad: Yeah. >> Brad, from your side of the fence. >> Brad: No, its... This is where the commons of scale come to benefit our partners. And AWS has easily the largest ecosystem. >> John: Mm-hmm. >> Whether or not it's partners, customers, and the like. And so... And then, all the respective teams and programs bring all those resources to bear for startups. Your analogy of of catching a big fish off coast, I actually have a house in Florida. I spend a lot of time there. >> Interviewer: Okay. >> I've yet to catch a big 500 pound fish. But... (interviewer laughs) >> But they're out there. >> But they're definitely out there. >> Yeah. >> And so, in addition to the formalized programs like the Global Partner Network Program, the APN and Marketplace, we really break our activities down with the CoreStacks of the world into two major kind of processes: "Sell to" and "Sell with". And when we say "Sell to", what we're really doing is helping them architect for the future. And so, that plays dividends for their customers. So what do we mean by that? We mean helping them take advantage of all the latest serverless technologies: the latest chip sets like Graviton, thing like that. So that has the added benefit of just lowering the overall cost of deployment and expend. And that's... And we focus on that really extensively. So don't ever want to lose that part of the picture of what we do. >> Mm-hmm. >> And the "Sell with" is what he just mentioned, which is, our teams out in the field compliment these programs like APN and Marketplace with person-to-person in relationship development for core key opportunities in things like FinTech and Retail and so on. >> Interviewer: Mm-hmm. >> We have significant industry groups and business units- >> Interviewer: Mm-hmm. >> in the enterprise level that our teams work with day in and day out to help foster those relationships. And to help CoreStack continue to develop and grow that business. >> Yeah. We've talked a lot about cost, right? >> Yeah. >> But there's a difference between reducing costs or optimizing your spend, right? I mean there- >> Brad: Right. >> Right. There's a... They're very different prism. So in terms of optimizing and what you're doing in the data governance world, what kind of conversations discussions are you having with your clients? And how is that relationship with AWS allowing you to go with confidence into those discussions and be able to sell optimization of how they're going to spend maybe more money than they had planned on originally? >> So today, because of the extra external micro-market conditions, every single customer that we talk to wanting to take a foster status of, "Hey, where are we today? How are we using the cloud? Are we in an optimized state?" >> Interviewer: Mm-hmm. >> And when it comes to optimization, again, the larger customers that we talk to are really bothered about the business outcome and how their services and ability to cater to their customers, right? >> Interviewer: Mm-hmm. >> They don't want to compromise on that just because they want to optimize on the spend. That conversation trickled down to taking a poster assessment first, and then are you using the right set of services within AWS? Are the right set of services being optimized for various requirements? >> Interviewer: Mm-hmm. >> And AWS help in terms of catering to the segment of customers who need that kind of a play through the patent ecosystem. >> John: Mm-hmm. Yeah. We've talked a lot about confidence too, cloud with confidence. >> Brad: Yeah. Yeah. >> What does that mean to different people, you think? I mean, (Brad laughing) because don't you have to feel them out and say "Okay. What's kind of your tolerance level for certain, not risks, but certain measures that you might need to change"? >> I actually think it's flipped the other way around now. I think the risk factor- >> Okay. >> is more on your on-prem environment. And all that goes with that. 'Cause you... Because the development of the cloud in the last 15 years has been profound. It's gone from... That's been the risky proposition now. With all of the infrastructure, all the security and compliance guardrails we have built into the cloud, it's really more about transition and risk of transition. And that's what we see a lot of. And that's why, again, where governance comes into play here, which is how do I move my business from on-prem in a fairly insecure environment relatively speaking to the secure cloud? >> Interviewer: Sure. >> How do I do that without disrupting business? How do I do that without putting my business at risk? And that's a key piece. I want to come back, if I may, something on cost-cutting. >> Interviewer: Sure. >> We were talking about this on the way up here. Cost-cutting, it's the bonfire of the vanities in that in that everybody is talking about cost-cutting. And so we're in doing that perpetuating the very problem that we kind of want to avoid, which is our big cost-cutting. (laughs) So... And I say that because in the venture capital community, what's happening is two things: One is, everybody's being asked to extend their runways as much as possible, but they are not letting them off the hook on growth. And so what we're seeing a lot of is a more nuanced conversation of where you trim your costs, it's not essential, spend, but reinvest. Especially if you've got good strong product market fit, reinvest that for growth. And so that's... So if I think about our playbook for 2023, it's to help good strong startups. Either tune their market fit or now that they good have have good market fit, really run and develop their business. So growth is not off the hook for 2023. >> And then let me just hit on something- >> Yeah. >> before we say goodbye here that you just touched on too, Brad, about. How we see startups, right? AWS, I mean, obviously there's a company focus on nurturing this environment of innovation and of growth. And for people looking at maybe through different prisms and coming. >> Brad: Yeah. >> So if you would maybe from your side of the fence, Ez from CoreStack, about working as a startup with AWS, I mean, how would you characterize that relationship about the kind of partnership that you have? And I want to hear from Brad too about how he sees AWS in general in the startup world. But go ahead. >> It's kind of a mutually enriching relationship, right? The support that comes from AWS because our combined goal is help the customers maximize the potential of cloud. >> Interviewer: Mm-hmm. >> And we talked about confidence. And we talked about all the enablement that we provide. But the partnership helps us get to the reach, right? >> Interviewer: Mm-hmm. >> Reach at scale. >> Interviewer: Mm-hmm. We are talking about customers from different industry verticals having different set of problems. And how do we solve it together so that like the reimbursement that happens, in fact healthcare customers that we repeatedly talk to, even in the current market conditions, they don't want to save. They want to optimize and re-spend their savings using more cloud. >> Interviewer: Mm-hmm. >> So that's the partnership that is mutually enriching. >> Absolutely. >> Yeah. To me, this is easy. I think the reason why a lot of us are here at AWS, especially the startup world, is that our business interests are completely aligned. So I run a pretty significant business unit in a startup neighbor. But a good part of my job and my team's job is to go help cut costs. >> Interviewer: Mm-hmm. >> So tell me... Show me a revenue responsibility position where part of your job is to go cut cost. >> Interviewer: Right. >> It's so unique and we're not a non-profit. We just have a very good long-term view, right? Which is, if we help companies reduce costs and conserve capital and really make sure that that capital is being used the right way, then their long-term viability comes into play. And that's where we have a chance to win more of that business over time. >> Interviewer: Mm-hmm. >> And so because those business interests are very congruent and we come in, we earn so much trust in the process. But I think that... That's why I think we being AWS, are uniquely successful startups. Our business interests are completely aligned and there's a lot of trust for that. >> It's a great success story. It really is. And thank you for sharing your little slice of that and growing slice of that too- >> Yeah. Absolutely. >> from all appearances. Thank you both. >> Thank you, John. >> Thank you very much, John. >> Appreciate your time. >> This is part of the AWS Startup Showcase. And I'm John Walls. You're watching theCUBE here at AWS re:Invent '22. And theCUBE, of course, the leader in high tech coverage.

foreign welcome to thecube's coverage of AWS re invent 2022. this is a part of our AWS executive Summit AT AWS re invent sponsored by Accenture I'm your host Lisa Martin I've got three guests here with me Christoph schulteis head of devops and infrastructure at Vodafone Germany joins us as well as IMAP baldasare the Accenture AWS business group Europe delivery lead attic Center and Philip schmuckel senior manager at Accenture technology we're going to be talking about what Vodafone Germany is doing in terms of its agile transformation the business and I.T gentlemen it's great to have you on thecube Welcome to the program thank you thanks for having us my pleasure Kristoff let's go ahead and start with you talk to us about what Vodafone Germany is doing in its transformation project with Accenture and with AWS certainly these are but let me first start with explaining what Vodafone does in general so Vodafone is one of the leading telephone and Technology service providers in Germany half of all German citizens are Vodafone customers using Vodafone technology to access the internet make calls and watch TV in the economic sector we provide connectivity for office farms and factories so this is vodafone's largest business and I.T transformation and we're happy to have several Partners on this journey with more than a thousand people working in scaled agile framework with eight Agile Release strings and one of the largest safe implementations in Europe why are we doing this transformation well not only since the recent uncertainties the Telco Market is highly volatile and there are a few challenges that Vodafone was facing in the last years as there are Market changes caused by disruptions from technological advances in competitors or changing customer customer expectations who for example use more of the top services like Netflix or Amazon Prime video what is coming up in the next wave is unknown so Technologies evolve continual disruption from non-tel causes to be expected and being able to innovate fast is the key Focus for everyone in order to be able to react to that we need to cope with that and do so in different aspects to become the leading digital technology company therefore Vodafone Germany is highly simplifying its products as well as processes for example introducing free product upgrades for customers we're driving the change from a business perspective and modernize the it landscape which we call the technology transformation so simply business-led but it driven for that Accenture is our integration partner and AWS provides the services for our platforms got it thank you for the background on the Vodafone the impact that it's making you mentioned the volatility in the Telecom market and also setting the context for what Vodafone Germany is doing with Accenture and AWS email I want to bring you into the conversation now talk to us about the partnership between Accenture and Vodafone in AWS and how is it set up to provide maximum value for customers yeah that's a great question actually well I mean working in Partnership allows obviously to bring in transparency and trust and these are key starting points for a program of this magnitude and a program like this comes out of strong willingness to change the game both internally and on the market so as you can imagine particular attention is required that's top level alignment in general when you implement a program like this you also need to couple the long-term vision of how you want to manage your customers what are the new products that you want to bring to the market with the long-term technology roadmap because the thing that you don't want to happen is that you invest many years and a lot of efforts and then when it comes the end of the journey you figure out that you have to restart a New Journey and then you enter in the NeverEnding Loop so obviously all these things must come together and they come together in what we call the power of three and it consists in AWS Vodafone and Accenture having a strategic Vision alignment and constant updates and most importantly the best of breed in terms of technology and also people so what we do in practice is uh we bring together Market understanding business Vision technical expertise energy collaboration and what is even more important we work as a unique team everybody succeeds here and this is a true win-win partnership more specifically Vodafone leads the Strategic Direction obviously they understand the market they are close to their customers AWS provides all the expertise around the cloud infrastructure insights on the roadmap and this is a key element elasticity both technical but also Financial and the then Accenture comes with its ability to deliver with the strong industry expertise flexibility and when you combine all these ingredients together obviously you understand it's easy to succeed together the power of three it sounds quite compelling it sounds like a very partnership that has a lot of flexibility elasticity as you mentioned and obviously the customer at the end of the day benefits tremendously from that Kristoff I'd like to bring you back into the conversation talk to us about the unified unified platform approach how is walk us through how Vodafone is implementing it with AWS and with Accenture so the applications that form the basis for the transformation program were originally pursuing all kinds of approaches for deployment and use of AWS services in order to support faster adoption and optimize the usage that I mentioned before and we have provided the Vodafone Cloud framework that has been The Trusted platform for several projects within the it in Germany as a side effect the framework facilitates the compliance with Vodafone security requirements and the unified approach also has the benefit that someone who is moving from one team to another will find a structure that looks familiar the best part of the framework though is the operative rights deployment process that helps us reducing the time from implementing for example a new stage from a few weeks to me hours and that together with improvements of the cicd pipeline greatly helped us reducing the time to speed up something and deploy the software on it in order to reach our Target kpis the unified platform provides all kinds of setups like AWS eks and the ecosystem that is commonly used with coping dentists like service mesh monitoring logging and tracing but it can also be used for non-continental erased applications that we have and provide the integration with security monitoring and other tools at the moment we are in contact with other markets of Vodafone to globally share our experience in our code which makes introducing a similar system into other markets straightforward we are also continuously improving our approach and the completely new version of the framework is currently being introduced into the program Germany is doing is really kind of setting the stage as you mentioned Christopher other parts of the business who want to learn from so that's a great thing there that that what you're building is really going to spread throughout the organization and make a positive impact Philip let's bring you into the conversation now let's talk about how you're using AWS specifically to build the new Vodafone Cloud integration platform talk to us about that as part of this overall transformation program sure and let's make it even more specific let's talk API management so looking at the program and from a technology point of view what it really is it is a bold step for Vodafone it's rebuilding huge parts of the infrastructure of their business ID infrastructure on AWS it's Greenfield it's new it's a bold step I would say and then if you put the perspective of API management or integration architecture what I call it it's a unique opportunity at the same time so what it what it gives you is the the opportunity to build the API management layer or an API platform with standardized apis right from the get-go so from the beginning you can build the API platform on top which is in contrast what we see throughout the industry where we see huge problems at our clients at other engagements that try to build these layers as well but they're building them on Legacy so that really makes it unique here for Vodafone and a unique opportunity to we have this API first platform built as part of the transformation program so what we have been built is exactly this platform and as of today there is more than 50 standardized apis throughout the application landscape already available to give you a few examples there is an API where I can change customer data for instance I can change the payment method of a customer straight from an API or I can reboot a customer equipment right from it from an API to fix a network issue other than that of course I can submit an order to order one of vodafone's gigabit internet offerings so on top of the platform there's a developer portal which gives me the option to explore all of the apis yeah in a convenient way in a portal and that's yeah that's developer experience meaning I can log into this portal look through the apis understand what I what I need and just try it out directly from the portal I see the response of an API live in the portal and this is it is really in contrast to what what we've seen before where you would have a long word document a cumbersome spreadsheet a long lasting process to get your hands on and this really gives you the opportunity to just go in try out an API and see how it works so it's really developer experience and a big step forward here then yeah how have we built this platform of course it's running on AWS it's Cloud native it's using eks but what I want to point out here is three principles that that we applied where the first one is of course the cloud native principle meaning we using AKs we are using containers we have infrastructure scales so we aim for every component being Cloud native being meant to be run in the cloud so our infrastructure will sleep at night to save Vodafone cost and it will wake up for the Christmas business where Vodafone intends to do the biggest business and scale of its platform second there is the uh the aim for open API specifications what we aim for is event non-vendor-specific apis so it should not matter whether there's an mdocs backend there's a net tracker back end or an sap Behind These apis it is really meant to decouple the different Business Systems of of a Vodafone by these apis that can be applied by a new custom front-end or by a new business to business application to integrate these apis last but not least there's the automate everything so there's infrastructure as code all around our platform where where I would say the biggest magic of cloud is if we were to lose our production environment lose all apis today it will take us just a few minutes to get everything back and whatever everything I mean redeploy the platform redeploy all apis all services do the configuration again and it will be back in a few minutes that's impressive as downtime is so costly for so many different reasons I think we're gonna know when the vision of this transformation project when it's been achieved how are you going to know that okay so it's kind of flipping the perspective a bit uh maybe uh when I joined Vodafone in in late 2019 I would say the vision for Vodafone was already set and it was really well well put out there it was lived in in the organization it was for Vodafone to become a digital company to become a digital service provider to to get the engineering culture into the company and I would say this Vision has not changed until today maybe now call it a North star and maybe pointing out two big Milestones that have been achieved with this transformation program so we've talked about the safe framework already so with this program we wrote out the one of the biggest safe implementations in the industry which is a big step for Vodafone in its agile Journey as of today there's the safe framework supporting more than 1 000 FTE or 1000 colleagues working and providing value in the transformation program second example or second big milestone was the first go-life of the program so moving stuff to production really proving it works showcasing to the business that it it is actually working there is actually a value provided or constant value provided with a platform and then of course you're asking for next steps right uh talking next steps there is a renewed focus on value and A Renewed focus on value between Accenture and Vodafone means focus on what really provides the most value to Vodafone and I would like to point out two things here the first being migrate more customers scale the platform really prove the the the the the cloud native platform by migrating more customers to it and then second it enables you to decommission the Legacy Stacks decommissioning Legacy Stacks is why we are doing it right so it's migrating to the new migrating to the new platform so last but not least maybe you can hear it we will continue this journey together with with Vodafone to become a digital company or to say that their own words from Telco to TECO I love that from Telco to technology gentlemen thank you so much for joining us on thecube today talking about the power of three Accenture AWS Vodafone how you're really enabling Vodafone to transform into that digital technology company that consumers at the end of the day that demanding consumers want we appreciate your insights and your time thank you so much thank you for having us my pleasure for my guests I'm Lisa Martin you're watching thecube's coverage of the AWS executive Summit AT AWS re invent sponsored by Accenture thanks for watching

(upbeat music) (logo shimmers) >> Good afternoon everyone, and welcome back to AWS re Invent 2022. We are live here from the show floor in Las Vegas, Nevada, we're theCUBE, my name is Savannah Peterson, joined by John Furrier, John, are you excited for the next segment? >> I love the innovation story, this next segment's going to be really interesting, an example of ecosystem innovation in action, it'll be great. >> Yeah, our next guests are actually award-winning, I am very excited about that, please welcome Alan and Becky from IBM. Thank you both so much for being here, how's the show going for ya? Becky you got a, just a platinum smile, I'm going to go to you first, how's the show so far? >> No, it's going great. There's lots of buzz, lots of excitement this year, of course, three times the number of people, but it's fantastic. >> Three times the number of people- >> (indistinct) for last year. >> That is so exciting, so what is that... Do you know what the total is then? >> I think it's over 55,000. >> Ooh, loving that. >> John: A lot. >> It's a lot, you can tell by the hallways- >> Becky: It's a lot. >> John: It's crowded, right. >> Yeah, you can tell by just the energy and the, honestly the heat in here right now is pretty good. Alan, how are you feeling on the show floor this year? >> Awesome, awesome, we're meeting a lot of partners, talking to a lot of clients. We're really kind of showing them what the new IBM, AWS relationship is all about, so, beautiful time to be here. >> Well Alan, why don't you tell us what that partnership is about, to start us off? >> Sure, sure. So the partnership started with the relationship in our consulting services, and Becky's going to talk more about that, right? And it grew, this year it grew into the IBM software realm where we signed an agreement with AWS around May timeframe this year. >> I love it, so, like you said, you're just getting started- >> Just getting started. >> This is the beginning of something magic. >> We're just scratching the surface with this right? >> Savannah: Yeah. >> But it represents a huge move for IBM to meet our clients where they are, right? Meet 'em where they are with IBM technology, enterprise technology they're used to, but with the look and feel and usage model that they're used to with AWS. >> Absolutely and so to build on that, you know, we're really excited to be an AWS Premier Consulting Partner. We've had this relationship for a little over five years with AWS, I'd say it's really gone up a notch over the last year or two as we've been working more and more closely, doubling down on our investments, doubling down on our certifications, we've got over 15,000 people certified now, almost 16,000 actually- >> Savannah: Wow. >> 14 competencies, 16 service deliveries and counting. We cover a mass of information and services from Data Analytics, IoT, AI, all the way to Modernization, SAP, Security Services, right. So it's pretty comprehensive relationship, but in addition to the fantastic clients that we both share, we're doing some really great things around joint industry solutions, which I'll talk about in a few minutes and some of those are being launched at the conference this year, so that's even better. But the most exciting thing to me right now is that we just found out that we won the Global Innovator Partner of the Year award, and a LATAM Partner of the Year award. >> Savannah: Wow. >> John: That's (indistinct) >> So, super excited for IBM Consulting to win this, we're honored and it's just a great, exciting part to the conference. >> The news coming out of this event, we know tomorrow's going to be the big keynote for the new Head of the ecosystem, Ruba. We're hearing that it's going to be all about the ecosystem, enabling value creation, enabling new kinds of solutions. We heard from the CEO of AWS, this nextGen environment's upon us, it's very solution-oriented- >> Becky: Absolutely. >> A lot of technology, it's not an either or, it's an and equation, this is a huge new shift, I won't say shift, a continuation for AWS, and you guys, we've been covering, so you got the and situation going on... Innovation solutions and innovation technology and customers can choose, build a foundation or have it out of the box. What's your reaction to that? Do you think it's going to go well for AWS and IBM? >> I think it fits well into our partnership, right? The the thing you mentioned that I gravitate to the most is the customer gets to choose and the thing that's been most amazing about the partnership, both of these companies are maniacally focused on the customer, right? And so we've seen that come about as we work on ways the customer to access our technology, consume the technology, right? We've sold software on-prem to customers before, right, now we're going to be selling SaaS on AWS because we had customers that were on AWS, we're making it so that they can more easily purchase it by being in the marketplace, making it so they can draw down their committed spin with AWS, their customers like that a lot- [John] Yeah. >> Right. We've even gone further to enable our distributor network and our resellers, 'cause a lot of our customers have those relationships, so they can buy through them. And recently we've enabled the customer to leverage their EDP, their committed spend with AWS against IBM's ELA and structure, right, so you kind of get a double commit value from a customer point of view, so the amazing part is just been all about the customers. >> Well, that's interesting, you got the technology relationship with AWS, you mentioned how they're engaging with the software consumption in marketplace, licensed deals, there's all kinds of new business model innovations on top of the consumption and building. Then you got the consulting piece, which is again, a big part of, Adam calls it "Business transformation," which is the result of digital transformation. So digital transformation is the process, the outcome is the business transformation, that's kind of where it all kind of connects. Becky, what's your thoughts on the Amazon consulting relationships? Obviously the awards are great but- >> They are, no- >> What's the next step? Where does it go from here? >> I think the best way for me to describe it is to give you some rapid flyer client examples, you know, real customer stories and I think that's where it really, rubber meets the road, right? So one of the most recent examples are IBM CEO Arvind Krishna, in his three key results actually mentioned one of our big clients with AWS which is the Department of Veterans Affairs in the US and is an AI solution that's helped automate claims processing. So the veterans are trying to get their benefits, they submit the claims, snail mail, phone calls, you know, some in person, some over email- >> Savannah: Oh, it gives me all the feels hearing you talk about this- >> It's a process that used to take 25 to 30 days depending on the complexity of the claims, we've gotten it down with AWS down to within 24 hours we can get the veterans what they need really quickly so, I mean, that's just huge. And it's an exciting story that includes data analytics, AI and automation, so that's just one example. You know, we've got examples around SAP where we've developed a next generation SAP for HANA Platform for Phillips Carbon Black hosted on AWS, right? For them, it created an integrated, scalable, digital business, that cut out a hundred percent the capital cost from on-prem solutions. We've got security solutions around architectures for telecommunications advisors and of course we have lots of examples of migration and modernization and moving workloads using Red Hat to do that. So there's a lot of great client examples, so to me, this is the heart of what we do, like you said, both companies are really focused on clients, Amazon's customer-obsessed, and doing what we can for our clients together is where we get the impact. >> Yeah, that's one of the things that, it sounds kind of cliche, "Oh we're going to work backwards from the customer," I know Amazon says that, they do, you guys are also very customer-focused but the customers are changing. So I'd love to get your reaction because we're now in that cloud 2.0, I call that 2.0 or you got the Amazon Classic, my word, and then Next Gen Cloud coming, the customers are different, they're transforming because IT's not a department anymore, it's in the DevOps pipeline. The developers are driving a lot of IT but security and on DataOps, it's the structural change happening at the customer, how do you guys see that at IBM? I know we cover a lot of Red Hat and Arvind talks to us all the time, meeting the customer where they are, where are they? Where are the customers? Can you share your perspective on where they are? >> It's an astute observation, right, the customer is changing. We have both of those sets of customers, right, we still have the traditional customer, our relationship with Central IT, right, and driving governance and all of those things. But the folks that are innovating many times they're in the line of business, they're discovering solutions, they're building new things. And so we need our offerings to be available to them. We need them to understand how to use them and be convenient for these guys and take them through that process. So that change in the customer is one that we are embracing by making our offerings easy to consume, easy to use, and easy to build into solutions and then easy to parlay into what central IT needs to do for governance, compliance, and these types of things, it's becoming our new bread and butter. >> And what's really cool is- >> Is that easy button- >> We've been talking about- >> It's the easy button. >> The easy button a lot on the show this week and if you just, you just described it it's exactly what people want, go on Becky. >> Sorry about that, I was going to say, the cool part is that we're co-creating these things with our clients. So we're using things like the Amazon Working Backward that you just mentioned.` We're using the IBM garage methodology to get innovative to do design working, design thinking workshops, and think about where is that end user?, Where is that stakeholder? Where are they, they thinking, feeling, doing, saying how do we make the easier? How do we get the easy button for them so that they can have the right solutions for their businesses. We work mostly with lines of business in my part of the organization, and they're hungry for that. >> You know, we had a quote on theCUBE yesterday, Savannah remember one of our guests said, you know, back in the, you know, 1990s or two 2000s, if you had four production apps, it was considered complex >> Savannah: Yeah. >> You know, now you got hundreds of workloads, thousands of workloads, so, you know, this end-to-end vision that we heard that's playing out is getting more complex, but the easy button is where these abstraction layers and technology could come in. So it's getting more complex because there's more stuff but it's getting easier because- >> Savannah: What is the magnitude? >> You can make it easier. This is a dynamic, share your thoughts on that. >> It's getting more complex because our clients need to move faster, right, they need to be more agile, right, so not only are there thousands of applications there are hundreds of thousands microservices that are composing those applications. So they need capabilities that help them not just build but govern that structure and put the right compliance over that structure. So this relationship- >> Savannah: Lines of governance, yeah- >> This relationship we built with AWS is in our key areas, it's a strategic move, not a small thing for us, it covers things like automation and integration where you need to build that way. It covers things like data and AI where you need to do the analytics, even things like sustainability where we're totally aligned with what AWS is talking about and trying to do, right, so it's really a good match made there. >> John: It really sounds awesome. >> Yeah, it's clear. I want to dig in a little bit, I love the term, and I saw it in my, it stuck out to me in the notes right away, getting ready for you all, "maniacal", maniacal about the customer, maniacal about the community, I think that's really clear when we're talking about 24 days to 24 hours, like the veteran example that you gave right there, which I genuinely felt in my heart. These are the types of collaborations that really impact people's lives, tell me about some of the other trends or maybe a couple other examples you might have because I think sometimes when our head's in the clouds, we talk a lot about the tech and the functionality, we forget it's touching every single person walking around us, probably in a different way right now than we may even be aware- >> I think one of the things that's been, and our clients have been asking us for, is to help coming into this new era, right, so we've come out of a pandemic where a lot of them had to do some really, really basic quick decisions. Okay, "Contact Center, everyone work from home now." Okay, how do we do that? Okay, so we cobbled something together, now we're back, so what do we do? How do we create digital transformation around that so that we are going forward in a really positive way that works for our clients or for our contact center reps who are maybe used to working from home now versus what our clients need, the response times they need, and AWS has all the technology that we're working with like Amazon Connect to be able to pull those things together with some of our software like Watson Assistant. So those types of solutions are coming together out of that need and now we're moving into the trend where economy's getting tougher, right? More cost cutting potentially is coming, right, better efficiencies, how do we leverage our solutions and help our clients and customers do that? So I think that's what the customer obsession's about, is making sure we really understand where their pain points are, and not just solve them but maybe get rid of 'em. >> John: Yeah, great one. >> Yeah. And not developing in a silo, I mean, it's a classic subway problem, you got to be communicating with your community if you want to continue to serve them. And IBM's been serving their community for a very long time, which is super impressive, do you think they're ready for the challenge? >> Let's do it. >> So we have a new thing on theCUBE. >> Becky: Oh boy. >> We didn't warn you about this, but here we go. Although you told, Alan, you've mentioned you're feeling very cool with the microphone on, so I feel like, I'm going to put you in the hot seat first on this one. Not that I don't think Becky's going to smash it, but I feel like you're channeling the power of the microphone. New challenges, treat it like a 32nd Instagram reel-style story, a hot take, your thought leadership, money clip, you know, this is your moment. What is the biggest takeaway, most important thing happening at the show this year? >> Most important thing happening at the show? Well, I'm glad you mentioned it that way, because earlier you said we may have to sing (presenters and guests all laughing) >> So this is much better than- >> That's actually part of the close. >> John: Hey, hey. >> Don't worry, don't worry, I haven't forgotten that, it's your Instagram reel, go. (Savannah laughs) >> Original audio happening here on theCUBE, courtesy of Alan and IBM, I am so here for it. >> So what my takeaway and what I would like for the audience to take away, out of this conversation especially, but even broadly, the IBM AWS relationship is really like a landmark type of relationship, right? It's one of the biggest that we've established on both sides, right- >> Savannah: It seems huge, okay you are too monolith in the world of companies, like, yeah- >> Becky: Totally. >> It's huge. And it represents a strategic change on both sides, right? With that customer- >> Savannah: Fundamentally- >> In the middle right? >> Savannah: Yeah. >> So we're seeing things like, you know, AWS is working with us to make sure we're building products the way that a AWS client likes to consume them, right, so that we have the right integration, so they get that right look and feel, but they still get the enterprise level capabilities they're used to from IBM, right? So the big takeaway I like for people to take, is this is a new IBM, it's a new AWS and IBM relationship, and so expect more of that goodness, more of those new things coming out of it. [John] Excellent, wow. >> That was great, well done, you nailed it. and you're going to finish with some acapella, right? (Alan laughs) >> You got a pitch pipe ready? (everyone laughs) >> All right Becky, what about you? Give us your hot take. >> Well, so for me, the biggest takeaway is just the way this relationship has grown so much, so, like you said, it's the new IBM it's the new AWS, we were here last year, we had some good things, this year we're back at the show with joint solutions, have been jointly funded and co-created by AWS and IBM. This is huge, this is a really big opportunity and a really big deal that these two companies have come together, identified joint customer needs and we're going after 'em together and we're putting 'em in the booth. >> Savannah: So cool. And there's things like smart edge for welding solutions that are out there. >> Savannah: Yes. >> You know, I talked about, and it's, you know you wouldn't think, "Okay, well what's that?" There's a lot to that, a lot of saving when you look at how you do welding and if you apply things like visual AI and auditory AI to make sure a weld is good. I mean, I think these are, these things are cool, I geek out on these things- >> John: Every vertical. >> I'm geeking out with you right now, just geeking- >> Yeah, yeah, yeah, so- >> Every vertical is infected. >> They are and it's so impactful to have AWS just in lockstep with us, doing these solutions, it's so different from, you know, you kind of create something that you think your customers like and then you put it out there. >> Yeah, versus this moment. >> Yeah, they're better together. >> It's strategic partnership- >> It's truly a strategic partnership. and we're really bringing that this year to reinvent and so I'm super excited about that. >> Congratulations. >> Wow, well, congratulations again on your awards, on your new partnership, I can't wait to hear, I mean, we're seven months in, eight months in to this this SaaS side of the partnership, can't wait to see what we're going to be talking about next year when we have you back on theCUBE. >> I know. >> and maybe again in between now and then. Alan, Becky, thank you both so much for being here, this was truly a joy and I'm sure you gave folks a taste of the new IBM, practicing what you preach. >> John: Great momentum. >> And I'm just, I'm so impressed with the two companies collaborating, for those of us OGs in tech, the big companies never collaborated before- >> Yeah. >> John: Yeah. Joint, co-created solutions. >> And you have friction between products and everything else. I mean's it's really, co-collaboration is, it's a big theme for us at all the shows we've been doing this year but it's just nice to see it in practice too, it's an entirely different thing, so well done. >> Well it's what gets me out of the bed in the morning. >> All right, congratulations. >> Very clearly, your energy is contagious and I love it and yeah, this has been great. Thank all of you at home or at work or on the International Space Station or wherever you might be tuning in from today for joining us, here in Las Vegas at AWS re Invent where we are live from the show floor, wall-to-wall coverage for three days with John Furrier. My name is Savannah Peterson, we're theCUBE, the source for high tech coverage. (cheerful upbeat music)

(upbeat intro music) >> Good afternoon, ladies and gentlemen and welcome back to fabulous Las Vegas, Nevada where we are theCUBE covering AWS re:Invent for the 10th year in a row. John Furrier, you've been here for all 10. How does this one stack up? >> It's feeling great. It's just back into the saddle of more people. Everyone's getting bigger and growing up. The companies that were originally on are getting stronger, bigger. They're doing takeovers in restaurants and still new players are coming in. More startups are coming in and taking care of what I call the (indistinct) on classic, all the primitives. And then you starting to see a lot more ecosystem platforms building on top of AWS. I call that NextGen Cloud, NextGen AWS. It's happening. It's happening right now. >> Best thing about all of these startups is they grow up, they mature, and we stay the same age, John. (John laughing) All right. All right. All right. Very excited to introduce you our next guest, he wears a lot of hats as the CEO, founder, and chairman at Reltio, please welcome Manish. Manish, welcome to the show. How is your show going so far? >> Well, thank you so much. You know, this is amazing. Just the energy, the number of people. You know, I was here last year, just after the pandemic, and I think it's almost double, if not more the number of people this year. >> John: Pushing 50,000. The high water mark was 65,000 in 2019. >> We should be doing like a Price Is Right sort of thing here on the show and figure out. >> Yeah, $1. >> Savannah: Yeah, yeah. (laughing) One guest, 80,000 guests. How many guests are here? Just in case the audience is not familiar, we know you're fast growing, very exciting business. Tell us what Reltio does. >> So, Reltio is a SaaS platform for data unification and we started Reltio in 2011. We have been serving some of the largest customers across industries like life sciences, healthcare, financial services, insurance, high tech, and retail. Those are, you know, some of the areas that we are focused on. The product capabilities are horizontal because we see the same data problem across every industry. Highly fragmented, highly siloed data that is slowing down the business for every organization out there. And that's the problem that we are solving. We are breaking down these silos, you know, one profile or one record, or one customer product supplier information record at a time, and bringing the acceleration of this unified data to every organization. >> This is the show Steam this year, Adam Celeste is going to be on stage talking about data end to end. Okay. Integrating in all aspects of a company. The word data analyst probably goes away pretty shortly. Everyone was going to be using data. This has been, and he talks about horizontal and vertical use cases. We've been saying that in theCUBE, I think it was about seven years ago, we first said we're going to start to see horizontally scalable data not just compute and cloud. This is now primetime conversation. Making that all work with governance is a real hard problem. Understanding the data. Companies have to put this horizontal and vertical capabilities in place together. >> Absolutely. You know, the data problem may be a horizontal problem, but every industry or vertical that you go into adds its own nuance or flavor to it. And that's why, you know, this has to be a combination of the horizontal and vertical. And we at Reltio thought about this for a while, where, you know, every time we enter a conversation, we are talking about patient data or physician data or client data and financial services or policy and customer information and insurance. But every time it's the number of silos that we encounter that is just an increasing number of applications, increasing number of third party data sources, and bringing that together in a manner where you can understand the semantics of it. Because, you know, every record is not created equal. Every piece of information is not created equal. But at the same time, you have to stitch it together in order to create that holistic, you know, the so-called 360 degree view. Because without that, the types of problems that you're trying to solve are not possible. Right? It's not possible to make those breakthroughs. And that's where I think the problem may be horizontal, but the application of the capabilities has to be verticalized. >> John: I'm smiling because, you know, when you're a founder like you are, and Dave, a lot here are at theCUBE, you're often misunderstood before people figure out what you do and why you started the company. And I can imagine, and knowing you and covering your company, that this is not just yesterday you came up with this idea that now everyone's talking about. There was probably moments in your history when you started, you're scratching it, "Hey the future's going to be this horizontal and vertical, especially where machine learning needs to know the data, the linguistics, whatever the data is, it's got to be very particular for the vertical, but you need to expand it." So when did you have the moment where people finally figured out like, what you guys doing is, like, relevant? I mean, now the whole world now sees- >> Savannah: Overnight success 11 years later. >> John: This shows the first time I've heard Amazon and the industry generally agree that horizontally scalable data systems with vertical value, that it's natural. We've been saying it for seven years on theCUBE. You've been doing the startup. >> Yeah. >> As a founder, you were there early. Now people are getting it. What's it like? Tell, take us through. When did you have the moment? When did you tipping point for the world getting it? >> Yeah, and you know, the key thing to remember is that, you know, not only have I been in this space for a long time but the experiences that we have gone through starting in 2011, there was a lot of focus on, you know, even AWS was at that point in time in the infancy stages. >> Yeah. >> And we said that we are going to set up a software as a service capability that runs only on public cloud because we had seen what customers had tried to do behind their firewalls and the types of hurdles that they had run into before. And while the concept was still in its nascent stages, but the directional signals, the fact that number of applications that you see in use today across any organization, that's growing. It used to be a case when in early 2000s, you know, this is early part of my career, where having six different applications across the enterprise landscape was considered complex. But now those same organizations are talking about 400, 500, a thousand different applications that they're using to run their business end to end. So, you know, this direction was clear. The need for digital transformation was becoming clear. And the fact that, you know, cloud was the only vehicle that you could use to solve these types of ad scale problems was also becoming clear. But what wasn't yet mainstream was this notion that, you know, if you're doing digital transformation, you need access to clean, consistent, trusted information. Or if you're doing machine learning or any kind of data analytics, you need similar kinds of trusted information. It wasn't a mainstream concept, but people were struggling with it because, you know, the whole notion of garbage in garbage out was becoming clearer to them as they started running into hurdles. And it's great to see that now, you know, after having gone through the transformation of, yes, we have provided the compute and the storage, but now we really need to unlock the value out of data that goes on this compute and storage. You know, it's great to see that even Amazon or AWS is talking about it. >> Well, as a founder, it's satisfying, and congratulations, we've been covering that. I got to ask, you mention this end to end. I like the example of in the 2006 applications considered complex, now hundreds and thousands of workloads are on an enterprise. Today we're going to hear more end to end data services on AWS and off AWS, hybrid or edge or whatever, that's happens. Now cross, it sounds like it's going to get more complex still. >> I mean... >> John: Right. I mean, that's not easy. >> Savannah: The gentle understatement of the century. I love that. Yes. >> If Adam's message is end to end, it's going to be more complex. How does it get easier? Because the enterprise, you know, the enterprise vendors love solving complexity with more complexity. That's the wrong answer. >> Well, you're absolutely right that things are going to get more complex. But you know, this is where, whether it is Amazon or you know, us, Reltio as a vendor coming in, the goal should always be what are we going to simplify for the customer? Because they are going to end up with a complex landscape on their hands anyway. Right? >> Savannah: Right. >> So that is where, what can be below the surface and simplified for the customers to use versus bringing their focus to the business value that they can get out of it. Unlocking that business value has to be the key aspect that we have to bring to the front. And, you know, that is where, yes, the landscape complexity may grow, but how is the solution making it simpler, easier, faster for you to get value out of the data that you're trying to work with? >> As a mission, that seems very clear and clean cut, but I'm curious, I can imagine there's so many different things that you're prioritizing when you're thinking about how to solve those problems. What is that decision matrix like for you? >> For us, it goes back to the core focus and the core problem that we are in the business of solving which is in a siloed, fragmented landscape, how can we create a single source of truth orientation that your business can depend on? If you're looking for the unified view of the customer, the product, the supplier, the location, the asset, all these are elements that are critical or crucial for you to run your business end to end. And we are there to provide that solution as Reltio to our customers. So, you know, we always, for our decision matrix have to go back to are we simplifying that problem for our customers and how much faster, easier, nimbler can it be, you know, both as a solution and also the time to value that it brings to the equation for the customer. >> Super important, end of the equation. Clearly you are on to something. You are not only a unicorn company, unicorn company being evaluated at over $1 billion latest evaluation, correct me if I'm wrong, is $1.7 billion as of last year. But you are also a centaur, which is seven times more rare than a unicorn, which for the audience maybe not familiar with the mythical creatures that define the Silicon Valley nomenclature in Lexicon. A centaur is a company with a hundred million in annual reoccurring revenue. How does it feel to be able to say that as a CEO or to hear me say that to you? >> Well, as a CEO, it's, you know, something that we have been working towards. the goal that we can deliver value to our customers, help every industry, you know, you just think about the types of products that you touch in a day, whether it's, you know, any healthcare related products that you're looking at. We are working with customers who are solving for the patient record to be unified with our platform. We are working with financial services companies who are helping you simplify how you do banking with them. We are working with retailers who are working in the area of, you know, leisure apparel or athletic goods and they are using our capabilities to simplify how they deliver better experience to you. So as I go across these industries, being able to influence and touch and simplify things overall for the customers that these companies are serving, that's an amazing feeling. And, you know, doing this while we are also making sure that we can build a durable business that has substantial revenue behind it- >> Savannah: Substantial. >> Gives us a lot of legs to stand on and talk about how we can change how the companies should run their entire data stack. >> And you're obviously a very efficient team practicing what you teach. You told me how many employees that you have? >> We have 450 employees across the globe. >> 450 employees and a hundred million in reoccurring revenue. It's pretty strong. It's pretty strong. >> Thank you. >> That's a quarter million in rev per employee. They're doing a pretty good job. That's absolutely fantastic. >> The cloud has been very successful, partnering with the cloud, a lot of leverage for the cloud. >> And that's been a part of our thesis from the very beginning that, you know, the capabilities that we build and bring to life have to be built on public cloud infrastructure. That's something that has been core to our innovation cycle because we look at it as a layer cake of innovation that we sit on and we can continue to drive faster value for our customers. >> John: Okay, so normally we do a bumper sticker. Tell me the bumper sticker for the show. We changed it to kind of modernize it called the Insta Challenge, Instagram challenge. Instagram has reels, short videos. What's the Instagram reel from your perspective? You have to do an Instagram reel right now about why this time in history, this time in for Amazon web services, this point for Reltio. Why is this moment in time important in the computer industry? Because, you know, we've reported, I put a story out, NextGen Clouds here. People are seeing their status go from ISV to ecosystem platforms on top of AWS. Your success has continued to grow. Something's going on. What's the Instagram reel about why this year's so important in the history of the cloud? >> Well, you know, just think about the overall macroeconomic conditions. You know, everybody's trying to think about where the next, you know, the set of growth is going to come from or how we are going to tackle, you know, what we have as challenges in front of us. And at the end of the day, most of the efficiency that came from applying new applications or, you know, buying new products in the application space has delivered its value. The next unlock is going to come from data. And that is the key that we have to think about because the traditional model of going across 500 different applications to run your business is no longer going to be a scalable model to work with. If you really want to move faster with your business, you have to think about how to use data as a strategic asset and think about things differently. And we are talking about delivering experience at the edge, delivering, you know, real time type of engagement with the customers that we work with. And that is where the entire data value proposition starts to deliver a whole new set of options to the customers. And that's something that we all have to think about differently. It's going to require a fundamentally different architecture, innovation, leading with data instead of thinking about the traditional landscape that we have been running with. >> Leading with data and transforming architecture. A couple themes we've had on the show lately already. >> John: Well I think there's been a great, I mean this is a great leadership example of what's going on in the industry. As young people are looking at their careers. I've talked with a lot of folks under 30, they're trying to figure out what's a good career path and they're looking at all this change in front of them. >> That's a great point, John. >> Whether it's a computer science student or someone in healthcare, these industries are being reinvented with data. What's your advice to those young, this up and coming generation that might not take the traditional path traveled 'cause it might not be there. What's your advice for those people making these career decisions? >> I think there are two things that are relevant to every career option out there. Knowledge and awareness of data and how to apply computing techniques to the data is key and relevant. It's the language that we all have to learn and be familiar with. Without that, you know, you'll be missing a key part of your arsenal that you will be required to bring to work but won't have access to if you're not well-versed or familiar with those two areas. So this is lingua franca that we all have to get used to. >> Data and computer technology applied to business or some application or some problem. >> Manish: Applied to business. You know, figuring out how to apply it to deliver business outcomes is the key thing to keep in mind. >> Okay. >> Yeah. Last question for you to wrap us up. It's obviously an exciting, thrilling, vibrant moment here on the show floor, but I'm curious because I can imagine some of your customers, especially given the scale that they're at, I mean we're talking about some Fortune 100s here, how are you delivering value in this uncertain market? I mean, I know you solved this baseline problem but I can imagine there's a little bit of frantic energy within your customer base. >> Manish: Yeah. You know, with data this has been a traditional challenge. Everybody talks about the motherhood and apple pie. If you have better data, you can drive better outcomes. But some of the work that we have been doing is quantifying, measuring those outcomes and translating what the dollar impact of that value is for each one of the customers. And this is where the work that we have done with large, you know, let's say life sciences companies like AstraZeneca or GSK or in financial services with companies like Northwestern Mutual or Fidelity or, you know, common household names like McDonald's where they're delivering their digital transformation with the data capabilities that we are helping build with them. That's the key part that's been, you know, extremely valuable. And that is where in each one of these situations, we are helping them measure what the ROI is at every turn. So being able to go into these discussions with the hard dollar ROI that you can expect out of it is the key thing that we are focused on. >> And that's so mission critical now and at any economic juncture. Just to echo that, I noticed that Forrester did an independent study looking at customers that invested in your MDM solution. 366% ROI and a total net present value of 13 million over three years. So you clearly deliver on what you just promised there with customers and brands that we touch in all of our everyday lives. Manish, thank you so much for being on the show with us today. You and Reltio are clearly crushing it. We can't wait to have you back hopefully for some more exciting updates at next year's AWS re:Invent. John, thanks for- >> Or sooner. >> Yeah, yeah. Or sooner or maybe in the studios or who knows, at one of the other fabulous events we'll all be at. I'm sure you'll be traveling around given the success that the company is seeing. And John, thanks for bringing the young folks into the conversation, was a really nice touch. >> We got skill gaps, we might as well solve that right now. >> Yeah. And I like to think that there are young minds watching theCUBE or at least watching, maybe their parents are- >> We're streaming to Twitch. All the gamers are watching this right now. Stop playing the video games. >> We have the hottest stream on Twitch right now if you're not already ready for it. John Furrier, Manish Sood, thank you so much for being on the show with us. Thank all of you at home or at the office or in outer space or wherever you happen to be tuned in to this fabulous live stream. You are watching theCUBE, the leader in high tech coverage. My name is Savannah Peterson. We're at AWS re:Invent here in Las Vegas where we'll have our head in the clouds all week.

from the cube studios in palo alto in boston bringing you data driven insights from the cube and etr this is breaking analysis with dave vellante last week's aws re invent brought into focus the degree to which cloud computing generally and aws specifically have impacted the technology landscape from making infrastructure orders of magnitude simpler to deploy to accelerating the pace of innovation to the formation of the world's most active and vibrant infrastructure ecosystem it's clear that aws has been the number one force for change in the technology industry in the last decade now going forward we see three high-level contributors from aws that will drive the next 10 years of innovation including one the degree to which data will play a defining role in determining winners and losers two the knowledge assimilation effect of aws's cultural processes such as two pizza teams customer obsession and working backwards and three the rise of super clouds that is clouds that run on top of hyperscale infrastructure that focus not only on i.t transformation but deeper business integration and digital transformation of entire industries hello everyone and welcome to this week's wikibon cube insights powered by etr in this breaking analysis we'll review some of the takeaways from the 10th annual aws re invent conference and focus on how we see the rise of super clouds impacting the future of virtually all industries one of the most poignant moments for me was a conversation with steve mullaney at aw aws re invent he's the ceo of networking company aviatrix now just before we went on the cube nick sterile one of aviatrix's vcs looked up at steve and said it's happening now before i explain what that means this was the most important hybrid event of the year you know no one really knew what the crowd would be like but well over twenty 000 people came to reinvent and i'd say at least 25 to 26 000 people attended the expo and probably another 10 000 or more came without badges to have meetings and side meetings and do networking off the expo floor so let's call it somewhere between thirty to forty thousand people physically attended the reinvent and another two hundred thousand or more online so huge event now what nick sterile meant by its happening was the next era of cloud innovation is upon us and it's happening in earnest the cloud is expanding out to the edge aws is bringing its operating model its apis its primitives and services to more and more locations yes data and machine learning are critical we talk about that all the time but the ecosystem flywheel was so evident at this year's re invent more so than any other re invent partners were charged up you know there wasn't nearly as much chatter about aws competing with them rather there was much more excitement around the value that partners are creating on top of aws's massive platform now despite aggressive marketing from competitive hyperscalers other cloud providers and as a service or on-prem slash hybrid offerings aws lead appears to be accelerating a notable example is aws's efforts around custom silicon far more companies especially isvs are tapping into aws's silicon advancements we saw the announcement of graviton 3 and new chips for training and inference and as we've reported extensively aws is now on a curve a silicon curve that will outpace x86 vis-a-vis performance price performance cost power consumption and speed of innovation and its nitro platform is giving aws and its partners the greatest degree of optionality in the industry from cpus gpus intel amd and nvidia and very importantly arm-based custom silicon springing from aws's acquisition of annapurna aws started its custom silicon journey in 2008 and is and it has invested massive resources into this effort other hyperscalers notably microsoft google and alibaba which have the scale economics to justify such custom silicon efforts are just recently announcing initiatives in this regard others who don't have the scale will be relying on third-party silicon providers a perfectly reasonable strategy but because aws has control of the entire stack we believe it has a strategic advantage in this respect silicon especially is a domain where to quote andy jassy there is no compression algorithm for experience b on the curve matters a lot and the biggest story in my view this past week was the rise of the super clouds in his 2020 book with steve hamm frank slootman laid out the case for the rise of data cloud a title which i've conveniently stolen for this breaking analysis rise of the super cloud thank you frank in his book slootman made a case for companies to put data at the center of their organizations rather than organizing just around people for example the idea is to create data networks while people of course are critical organizing around data and enabling people to access and share data will lead to the democracy democratization of data and network effects will kick in this was essentially metcalfe's law for data bob metcalf was the inventor of ethernet ethernet he put forth that premise when we we both worked or the premise when we both worked for pat mcgovern at idg that the value of a network is proportional to the square of the number of its users or nodes on the network thought of another way the first connection isn't so valuable but the billionth connection is really valuable slootman's law if i may says the more people that have access to the data governed of course and the more data connections that can be shared or create sharing the more value will be realized from that data exponential value in fact okay but what is a super cloud super cloud is an architecture that taps the underlying services and primitives of hyperscale clouds to deliver incremental value above and beyond what's available from the public cloud provider a super cloud delivers capabilities through software consumed as services and can run on a single hyperscale cloud or span multiple clouds in fact to the degree that a super cloud can span multiple clouds and even on-premises workloads and hide the underlying complexity of the infrastructure supporting this work the more adoption and the more value will be realized now we've listed some examples of what we consider to be super clouds in the making snowflake is an example we use frequently frequently building a data cloud that spans multiple clouds and supports distributed data but governs that data centrally somewhat consistent with the data mesh approach that we've been talking about for quite some time goldman sachs announced at re invent this year a new data management cloud the goldman sachs financial cloud for data with amazon web services we're going to come back to that later nasdaq ceo adina friedman spoke at the day one keynote with adam silipsky of course the new ceo of aws and talked about the super cloud they're building they didn't use that term that's our term dish networks is building a super cloud to power 5g wireless networks united airlines is really in my view they're porting applications to aws as part of its digital transformation but eventually it will start building out a super cloud travel platform what was most significant about the united effort is the best practices they're borrowing from aws like small teams and moving fast but many others that we've listed here are on a super cloud journey just some of the folks we talked to at reinvent that are building clouds on top of clouds that are shown here cohesity building out a data management cloud focused on data protection and governance hashicorp announced its ipo at a 13 billion valuation building an it automation super cloud data bricks chaos search z-scaler z-scaler is building a security super cloud and many others that we spoke with at the event now we want to take a moment to talk about castles in the cloud it's a premise put forth by jerry chen and the team at greylock it's a really important piece of work that is building out a data set and categorizing the various cloud services to better understand where the cloud giants are investing where startups can participate and how companies can play in the castles that are being built that have been built by the hyperscalers and how they can cross the moats that have been dug and where innovation opportunities exist for other companies now frequently i'm challenged about our statements that there really are only four hyperscalers that exist in the world today aws microsoft google and alibaba while we recognize that companies like oracle have done a really excellent job of improving their clouds we don't consider companies like oracle ibm and other managed service providers as hyperscalers and one of the main data points that we use to defend our thinking is capex investment this was a point that was made in castles in the cloud there are many others that we look at elder kpi size of ecosystem partner acceleration enablement for partners feature sets etc but capex is a big one here's a chart from platform nomics a firm that is obsessed with cl with capex showing annual capex spend for five cloud companies amazon google microsoft ibm and oracle this data goes through 2019 it's annual spend and we've superimposed the direction for each of these companies amazon spent more than 40 billion dollars on capex in 2020 and will spend more than 50 billion this year sure there are some warehouses for the amazon retail business in there and there's other capital expenses in these numbers but the vast majority spent on building out its cloud infrastructure same with google and microsoft now oracle is at least increasing its cap x it's going to spend about 4 billion but it's de minimis compared to the cloud giants and ibm is headed in the other direction it's choosing to invest for instance 34 billion dollars in acquiring red hat instead of putting its capital into a cloud infrastructure look that's a very reasonable strategy but it underscores the gap okay another metric we look at is i as revenue here's an updated chart that we showed last month in our cloud update which at the time excluded alibaba's most recent quarter results so we've updated that very slight change it wasn't really material so you see the four hyperscalers and by the way they invested more than a hundred billion dollars in capex last year it's gonna be larger this year they'll collectively generate more than 120 billion dollars in revenue this year and they're growing at 41 collectively that is remarkable for such a large base of revenue and for aws the rate of revenue growth is accelerating it's the only hyperscaler that can say that that's unreal at their size i mean they're going to do more than 60 billion dollars in revenue this year okay so that's why we say there are only four hyperscalers but so what there are so many opportunities to build on top of the infrastructure that the three u.s giants especially are building as folks are really cautious about china at the moment so let's take a look at what some of the companies that we've been following are doing in the super cloud arena if you will this chart shows some etr data plotting net score or spending momentum on the vertical axis and market share or presence in the etr data set on the horizontal axis most every name on the chart is building some type of super cloud but let me start as we often do calling out aws and azure i guess they're already super clouds but they're not building necessarily on top of of of other people's clouds and there are a little bit you know microsoft does some of that certainly google's doing some of that amazon really bringing its cloud to the edge at this point it's not participating in multi-cloud actively anyway aws and azure they stand alone as the cloud leaders and you can debate what's included in azure in our previous chart on revenue attempts to strip out the microsoft sas business but this is a customer view they see microsoft as a cloud leader which it is so that's why its presence on the horizontal axis and its momentum is is you know very large and very strong stronger than even in aws in this view even though it's is revenue that we showed earlier microsoft is significantly smaller but they both have strong momentum on the vertical axis as shown by that red horizontal line anything above that remember is considered considered elevated that 40 percent or above now google cloud it's well behind these two to we kind of put a red dotted line around it but look at snowflake that blue circle i mean i realize we repeat ourselves often but snowflake continues to hold a net score in the mid to high 70s it held 80 percent for a long time it's getting much much bigger it's so hard to hold that and in 165 mentions in the survey which you can see in the inserted table it continues to expand its market's presence on the horizontal axis now all the technology companies that we track of all of them we feel snowflake's vision and execution on its data cloud and that strategy is most is the most prominent example of a super cloud truly every tech company every company should be paying attention to snowflakes moves and carving out unique value propositions for their customers by standing on the shoulders of cloud giants as ceo ed walsh likes to say now on the left hand side of the chart you can see a number of companies that we spoke with that are in various stages of building out their super clouds data bricks dot spot data robots z z scalar mentioned hashi you see elastic confluent they're all above the forty percent line and somewhat below that line but still respectable we see vmware with tanzu cohesity rubric and veeam and many others that we didn't necessarily speak with directly at reinvent and or they don't show up in the etr dataset now we've also called out cisco dell hpe and ibm we didn't plot them because there's so much other data in there that's not apples to apple but we want to call them up because they all have different points of view and are two varying degrees building super clouds but to be honest these large companies are first protecting their respective on-prem turf you can't blame them those are very large install basis now they're all adding as a service offerings which is cloud-like i mean they're behind way behind trying to figure out you know things like billing and they don't nearly have the ecosystem but they're going to fight rightly they're going to fight hard and compete with their respective portfolios with their channels and their vastly improved simplicity but when you speak to customers at re invent and these are not just startups we're talking to we're talking about customers of these enterprise tech companies these customers want to build on aws they look at aws as cloud and that is the cloud that they want to write to now they want to connect they're on-prem but they're still largely different worlds when you when you talk to these customers now they'll fully admit they can't or won't move everything out of their data centers but the vast vast majority of the customers i spoke with last week at reinvent have much more momentum around moving towards aws they're not repatriating as everybody's talking about or not everybody but many are talking about and yeah there's some recency bias because we just got back but the numbers that we shared earlier don't lie the trend is very clear now these large firms that we mentioned these incumbents in the tech industry these big enterprise tech giants they're starting to move in the super cloud direction and they will have much more credibility around multi-cloud than the hyperscalers but my honest view is that aws's lead is actually accelerating the gap in my opinion is not closing now i want to come back and dig into super cloud a little bit more around 2010 and 2011 we collaborated with two individuals who really shaped our thinking in the big data space peter goldmaker was a cell side analyst at common at the time and abi abhishek meta was with bank of america and b of a was transforming its data operations and avi was was leading that now peter was you know an analyst sharp and less at the time he said you know it's going to be the buyers of big data technology and those that apply big data to their operations who would create the most value he used an example of sap he said look you you couldn't have chosen that sap was going to lead an erp but if you could have figured out who which companies were going to apply erp to their business you would have made a lot of money investing so that was kind of one of his investment theses now he posited that the companies that would apply the big data technology the buyers if you will would create far more value than the cloud errors or the hortonworks or a collection of other number of big data players and clearly he was right in that regard now abi mehta was an example of that and he posited that ecosystems would evolve within vertical industries around data kind of going back to frank slootman's premise that in putting data at the core and that would power the next generation of value creation via data machine learning and business transformation and he was right and that's what we're seeing with the rise of super cloud now after the after the first reinvent we published a post seen on the right hand side of this chart on wikibon about the making of a new gorilla aws and we said the way to compete would be to take an industry focus or one way to compete with take an industry focus and become best to breed within that industry and we aligned really with abbey meta's point of view that industry ecosystems would evolve around data and offer opportunities for non-hyperscalers to compete now what we didn't predict at the time but are now seeing clearly emerge is that these super clouds are going to be built on top of aws and other hyperscale clouds makes sense goldman's financial cloud for data is taking a page out of aws it's pointing its proprietary data algorithms tools and processes at its clients just like amazon did with its technology and it's making these assets available as a service on top of the aws cloud a super cloud for financial services if you will they are relying on aws for infrastructure compute storage networking security and other services like sagemaker to power that super cloud but they're bringing their own ip to the table nasdaq and dish similarly bringing forth their unique value and as i said as i said earlier united airlines will in our view eventually evolve from migrating its apps portfolio to the cloud to building out a super cloud for travel what about your logo what's your super cloud strategy i'm sure you've been thinking about it or perhaps you're already well down the road i'd love to hear how you're doing it and if you see the trends the same or differently as we do okay that's it for now don't forget these episodes are all available as podcasts wherever you listen all you do is search breaking analysis podcast you definitely want to check out etr's website at etr.plus for all the survey data remember we publish a full report every week on wikibon.com and siliconangle.com you can email me if you want to get in touch with david.velante at siliconangle.com you can dm me at devolante on twitter you can comment on our linkedin posts this is dave vellante for the cube insights powered by etr have a great week stay safe be well and we'll see you next time [Music] you

(upbeat music) >> Hey everyone and welcome back to the CUBE's continuous live coverage of AWS re:Invent 2021. continuous live coverage of AWS re:Invent 2021. Lisa Martin here with David Nicholson. We have two live sets going on, we've got two remote sets, over 100 guests working with AWS and it's a massive ecosystem of partners, really digging into the next decade of cloud innovation and we're pleased to welcome back one of our CUBE alumni, Edith Harbaugh, CEO, and co-founder of LaunchDarkly. We're going to be talking about a blueprint for continuous modernization, Edith, it's great to have you, thanks for coming. >> Thanks for having me. >> So I was doing some research, you guys raised 200 million in series D in August, just a few months ago, that new funding tripled your valuation to 3 billion up more than 3x from the previous funding rounds, so rocket ship. >> Edith: Yeah. >> I also noticed you guys are on the Forbes Cloud 100 2nd year on the list, you jumped dramatically from 100 in 2020 to 47 this year, talk to us about all the innovation and acceleration that's going on at LaunchDarkly. >> Yeah, well, it's, it's great to be here, you know, I'm the CEO and co-founder and we started seven years ago in 2014 and what we were doing back then was a really new field, like I actually came up with the name feature management, just to describe what we were doing and it was this idea that you could release features to different people at different times, which sounds really simple, but it really allows you to have valves to different populations that you can then turn something on, turn something off, run a beta, do personalization and then if something's going wrong out on the field quickly and easily, turn it off. >> So as an engineer, as a long standing engineer, what were the things that really frustrated you, that you thought this, this is missing, we've got to focus on this. >> Oh my gosh, so, I was an engineering manager, I actually do a podcast too called To Be Continuous just about all the bad things I saw happen, the worst thing you could do is, is build something that nobody wants, which is really frustrating, so I think a lot of continuous delivery came out of the urge to just get stuff out quicker. The flip side of that is that if you moved too fast, a release can be catastrophic. We used to call them the push and pray release because you push stuff out and then you're just crossing your fingers that nothing breaks because if something breaks it's extremely stressful. Your mind starts flooding with endorphins and hormones, your heart rate increases and you sometimes make even worse decisions, so what LaunchDarkly and feature management allow you to do is push it out to who you want and if something is going wrong, you could turn it off without a redeploy, if things are going right, you can continue to push it out. >> And when you say feature management, you're talking about, you're talking about a level of granularity that is finer than a release version. that is finer than a release version. >> Edith: Yeah. How do you do that? >> Our customers do it, so we provide a platform where our customers and we have 2,500 worldwide, everything from IBM and Atlassian, down to like three person startups, they decide how to encapsulate a feature >> David: Okay. >> So they could push it to who they want, so, so there's a lot of really neat use cases. >> So knowing that you're providing them with the valves. >> Edith: Yes. Then they can- think differently about how they're actually developing in anticipation of delivering encapsulated features, as opposed to, here's your new release. >> Edith: Exactly. >> Okay. >> Exactly, so we have some customers who've used LaunchDarkly to actually move to the cloud. So like TrueCar was running their own data centers and they wanted a way to start moving all of that data center traffic into AWS, so they could use LaunchDarkly to manage that traffic flow and do it in a controlled way instead of just one quick switch. >> I was looking at that case study of TrueCar, they migrated 500 websites to AWS without downtime and deploying 20x per day, which is up from 1x a week, that's a massive change. >> Yeah, I think really what we give our customers is confidence that if you know that you can always have control over stuff with feature management, you actually move much quicker. You can, you can move 20 times a day if you know that if something goes wrong, you can always turn it off, you have much more confidence. >> Where are your, you having customer conversations? I know you, you coined to the term feature management, I'd love to know a bit more contextually about the evolution from feature flags to feature management and where are those customer conversations happening? are they kind of down in the technical ways? are they more higher level? given the fact that we're in such a, still a, such a state of flux with COVID? >> Yeah, so we, we didn't invent feature flagging like the smart companies like Amazon, Facebook, Netflix have been doing feature flagging for decades now, it was always a secret sauce of this is how they could manage their own functionality. What LaunchDarkly did was kind of changed it to feature management about doing it where any other customer also had the same set of tools and platforms and also on top of that things like a workflow, scheduling, integrations. So that for example, a developer could develop something and then give the keys to the product manager, say product manager, you get to, you get to run the beta now. >> So putting, putting more control back in the hands of the folks that are, that really are touching and feeling and smelling the product. >> Yeah or customer support, you know, >> Yeah or customer support, you know, if something is going wrong in the field, instead of having to wait for an engineer to fix a bug customer support could just turn it off. >> So I'm curious about, you know, when we talk about it's a, this, this sort of dovetails with something that was discussed in the keynote today, out of the gate, Adam comes out and he's talking about microprocessor technology. Now in the era of cloud, generally people would say, that stuff doesn't matter, right? It's all about the feeling of being in the cloud and the flame, you know, the, the, the field of wheat blowing in the wind and it's a feeling that you get, it's really interesting what you're doing under the covers, but who is the, who is the audience? Who, who buys this? Because I can imagine some in the engineering, on the engineering side of things, feeling like maybe they're giving up some control, but really you're giving them more tools, but is it business people who are demanding this? how, how do you go to market? >> Yeah, so it's really interesting because our core audience is developers and VP of engineering, like they love the platform. Like our Net Promoter Score is extremely high, engineers say like, this gave me my weekends back because if a bug happens I don't have to come in. >> David: Okay so they get it. >> They get it. This isn't being pushed down- from executives that don't understand the technology. >> No, I mean, a typical thing is a developer's, like, I need this to do my job and then the business people say, well, if the developers are happy, we're happy, you know, it's, it's a developers world now, you know, they're hard to hire, you have to have them and if you have anything that will make their job easier and them happier, why wouldn't you buy it? >> That's a big facilitator, so you mentioned a high, high NPS, high Net Promoter Score, we, we talk with Amazon folks about their their focus on the customer and their customer obsession if you will, that everything starts backwards, we start from the customer, 2,500 customers in such a short time period, we talked about the funding, I imagine culturally there's similarities there, if one of the things that you're able to confidently give your customers is that confidence in LaunchDarkly. >> Yeah, you know, one of the happiest parts of my job is visiting customers, you know, I, my co-founder and I personally visited, I think the first 10 or 20 customers and if they had a bug, if they wanted something, and if they had a bug, if they wanted something, we built it. And I love going on customer sites, cause it's. And I love going on customer sites, cause it's. >> When they're telling you that you gave them their weekend back. >> Edith: Yeah. >> Huge. >> That's, yeah, that.- that's not an insignificant thing when you think about what people do with their weekends, you know, so? >> Yeah, you know, it, it feels really good to have customers say, like this literally has changed the way they built software for the better. >> I can't imagine this, you know, with everything that's happened in the last 22 months with the acceleration to cloud, but all these massive pivots by businesses, in every industry just to survive in the beginning, were an advantage, something like LaunchDarkly is for those organizations, so you have to move really, really quickly and keep changing direction to kind of figure out how do we stay afloat and now how do we thrive in that, that this has probably been a real lifesaver for a lot of organizations. >> Yeah, I mean, we've seen like a ten year roadmap at our customers compressed into a month, like we had a, a retail chain in the Midwest that was thinking about doing in-store pickup and then when COVID hit, they're like, okay, this changed from a, maybe to a, we need to have this to stay afloat and now, now they can help people pick up, same with, same with restaurants having a mobile app to do delivery or pickup, it used to be when we'll get to that next year, now it's something that you have to have. >> Oh yeah. >> Because if, if you're going to go get coffee and one place has a mile long line and their place has an app, which one are you going to pick? >> So, what do people do that don't have this capability? This, I mean, this might sound like a completely naive question, I know a lot about a lot of things, so I'm okay looking dumb sometimes, it's how I learn, so I'm okay looking dumb sometimes, it's how I learn, but seriously, if you don't have these valves, then aren't you doomed then aren't you doomed to releases that are going to be panic inducing. >> It's really, it's really painful, like, I mean, that's, that's the way I used to, to release, you know, I remember it, like you're released and you would have tried to have caught all the bugs, but it would go out and if something happened, you had to fix it on the fly and even if you have a really good deployment process, that's 20 minutes, maybe two hours. >> David: Sure, and, and. >> Which, which if you're a mobile app, it could be a business killer. >> Yeah, well we're here at AWS reinvent, I mean, how does, how does this dovetail with this, the AWS mission to migrate and modernize into the cloud native world? we're talking about cloud native, you know, development and operations that you're involved with, so there's obviously a synergy there, but why specifically AWS? >> Oh, I mean, I think one of the biggest tailwinds we've had as a business is if you're releasing twice a year, we've had as a business is if you're releasing twice a year, you don't really need a tool like this, or a platform like this, your business process is completely different, but you're going to die as a company cause you can't survive on two releases a year. If you're moving to the cloud, we help you get there and once you're in the cloud, if you want to move at the speed of business, but safely, we give you that platform. Like, so, I think continuous delivery got this bad wrap because people thought that meant that you push out stuff every second and break everything. >> David: Right. >> What we do is we allow you to innovate as fast as you want, but release in a controlled way. >> I got to ask you a question, you, you talked about the customers and your love of being with customers, one of the things I can't help thinking is that what you're helping facilitate is brand reputation. If, you know, if we have an expectation and we want to go on a, on an app and order coffee, and it's down, we're going to go to the next competitor, so from a brand reputation perspective, I'm just wondering if, if any of your customer conversations kind of go in addition to the VP of engineering kind of go in addition to the VP of engineering and it focused on the folks that are leading these companies going, our reputation is on the line, people are, let's face it during COVID far less patience than we've, we've seen a lot of really impatient people, but is, is that something that you also facilitate, is the brand reputation? >> Oh, not just a brand reputation that an outage can be costly of millions of dollars, like. that an outage can be costly of millions of dollars, like. >> Lisa: $5,600 a minute, I think is what Gartner estimates. >> Yeah, but depending on what business you're in, like if you're in a bank, you absolutely need to be reliable. If you're a streaming service like streaming, one of the biggest horse races in Australia, you need to have uptime. >> Everybody needs uptime, let's, let's just be clear if I can't get door dash or whatever, it's a disaster from my perspective as a consumer and yes, we have, we have far less patience than we've ever had. >> Yeah, I mean, we have a really interesting, we have both B2C, like streaming ash, streaming apps, delivery apps, as well as B2B streaming apps, delivery apps, as well as B2B and they both have problems that we solve but honestly, the, the, the business problems with a B2B are much more challenging sometimes. >> Well Edith, thank you so much for joining David and me on the program, talking about LaunchDarkly, what you're enabling organizations to achieve in every industry, it sounds like you're riding a rocket ship. >> It's been really fun, you know, I, I love seeing a customer that's been using us for three, five years. >> David: Wow. >> And how much their life has gotten better. >> And as you said, that's, that's no small statement. Thank you so much for joining us on the program, we appreciate your insights and look forward to hearing more news from LaunchDarkly coming out. >> Thanks. >> All right, for David Nicholson, I'm Lisa Martin, you're watching theCUBE's coverage of AWS:reinvent 2021, theCUBE, the global leader in live tech coverage. (upbeat music)

>>Mhm. Hey, everyone, welcome back to the cubes. Continuous coverage of AWS Re Invent 2021. Live from Las Vegas. Lisa Martin with John Ferrier We have to live sets to remote studios over 100 guests on the Cube at this year's show and we're really excited to get to the next decade in cloud innovation and welcome from the keynote stage. Mark Ruin the Chief Network Officer Andy VPs Dish Network Mark, Welcome to the Cube. >>Thank you. >>Enjoyed your keynote this morning. So big news coming from AWS and dish you guys announced in the spring telecom industry First dish in AWS have formed a strategic collaboration to reinvent, reinvent five G connectivity and innovation. Let's let's really kind of dig into the AWS dish partnership. >>Yeah, you know, we're putting our network in the cloud, which allows us to have a different speed of innovation and a much more corroborative way of bringing new technology. And then we have access to all the developer ecosystem of AWS. So that's but as you say, it's a world first to put the telco in the cloud. >>And so the first time the five g network is going to be in the cloud, and it was also announced I'm curious, uh, that Las Vegas is going to be the first city live here. We are sitting in Las Vegas. What's the any status you can give us on >>that? So we're building across the US and Las Vegas is a place that we've built and we better testing. So that's where we have all run and we're testing all sorts of traffic and capability with our people and partners live here at the same time that we have the reinvent and, uh, Bianco around. We're also starting to test new capabilities like orchestration, slicing things that we've never seen any industry. So that's pretty exciting, I >>have to ask you. In the telecom industry, there has been an inflexion point around cloud and cloud Impact Ran is opening up new opportunities. What is the telecom industry getting and missing at the same time? Because it seems to be two schools of thought cloud pro cloud ran and then hold onto the old way. >>I think everybody would like to go to Iran and the cloud, but it's not as easy if you have a big installed base. So for us. You know, we all knew it. It's easy so we can adopt the best technology and the newest. But of course, if you have a big instal base, there is going to be a transformation, if you wish. So you know, people are starting trying to set the expectation of how much time it will take. But for us, you know we are. We're moving ahead because we're building a completely new network. >>It's a lot easier than well, it's a relative term. It's >>really much more fun. And we can We don't have to make compromises, right? So but it's still a lot of work, you know, we're discovering we're learning a lot of things. We're partners. >>What if you have a clean sheet of paper or Greenfield? What's the playbook to roll this out across the campus for a large geographic area? >>Yeah, so pretty much You have the same capability in terms of coverage and capabilities than anybody else, but we can do it in an automated manner. We can do it with much thinner and efficient hardware, pretty much hardware with a few accelerators, so a bit of jargon. But, you know, we just have access to a larger ecosystem and much more silicon and all the good things that are coming with the cloud >>talk to us about some of the unique challenges of five G that make running it in the cloud so much more helpful. And then also, why did you decide to partner with AWS? Clearly you have choice, but I'd love to know the backstory on that. >>Yeah, I've been in the telco industry forever, and I've always seen that our speed of innovation was to slow. The telco is very good at reliability. You know, your phone always works. Um, it's very reliable. You can have massive traffic, but the speed of innovation is not fast enough. And the the applications that are coming on the clouds are much faster. So what we wanted to marry is the reliability of the telco and and all the knowledge that exists with the speed of the cloud. And that's what we're doing with bringing their ecosystem into our ecosystem to get the best of two worlds. >>Lots of transformation in the vertical industries. We heard from Adam today on stage vertical with ai machine learning. How does that apply in the telco world because it's an edge you got. See, sports stadiums, for instance. You're seeing all kinds of home impact. How is vertical specialisation? >>Yeah. So what is unique about the cloud is that you can observe a lot of things, you know, in the cloud you have access to data, so you see what's happening, and then you use a lot of algorithms. We call it Machine Learning Analytics to make decisions. Now, for us, it means if you're a stadium, you're going to have a much better visibility of what's happening. Where is the traffic? You know, people moving in and moving out? Are they going to buy some food awards? So you see the traffic and you can adapt the way you steal the traffic the way you distribute video, the way you distribute entertainment to how people are moving because you can observe what is happening in the network, which you can't do in a classic or legacy five g network. So once you observe, you can have plenty of ideas, right? And you can start innovation again, mix a lot of things and offer new services. >>In this last 22 months, when we saw this rapid pivot to work from home. And now it's work from anywhere, right? We talk about hybrid cloud hybrid events here, but this hybrid work environment talk to me about the impact that that decision A W s are going to have on all of those companies and people who are going to be remote and working from the edge for maybe permanently. >>Yes, you say, You know what is important is that people want to have access to the to the cloud to the services, the enterprise from wherever they are. So as a software architect, I need to make sure that we can follow them and offer that service from wherever they are in a similar manner today. If you're making a phone call, you don't have to think if you're connecting to the Web, you know, through WiFi through this and that, you have to think we want to make it as simple as making a phone call. In the past, where you always connected, you always secured. You always have access to your data. So that's really the ambition we have. And, of course, with the new remote abbots, the video conferencing that's the perfect time to come with a new offer. >>And the Strand also is moving towards policy based. You mentioned understanding video and patterns. Having that differentiated services capability in real time is a big deal. >>Yeah, that's a big deal. Actually, what enterprise want? They want to manage their policy, so they want to decide what traffic gets, a premium access and what traffic can be put in the background. You want to update your computers? Maybe that's not a premium price for that. You can do it at any time, but you want to have real time, customer service and support. You want premium? And who am I to decide for an enterprise? Enterprises want to decide. So what we offer them is the tools to create their policy, and their policy will be a competitive advantage for them when they can different change. >>And this brings up another point. I want to ask you. You brought this up earlier about this. The ideas, the creativity that enables with cloud you mentioned ideas will come out. These are this is where the developers now can really encode. This is the whole theme of this Pathfinders keynote. You were up on stage. This is a real opportunity to add value. Doing all the heavy lifting in the top of the stack and enabling new use cases, new applications, new expectations. >>You know what I tell to my engineers? My dream as an engineer is to be, uh, developer friendly. I want people to come to us because it's fun to work in our environment and try things. And a lot of the ideas that developers will have won't work. But if they can spin it off very fast, they will move to that killer application of killer service very fast. So my job is to bring that to them so that it's very easy to consume and and trying to live And, you know, just like bringing >>candy to a baby here. >>Yeah, cause right And have fun and, uh, and discover it for yourself and decide for yourself. >>I gotta ask your questions in the Telecom for a while. We've been seeing on the Cube earlier in our intro keynote analysis that we're now living in an era with SAS applications. No more shelf where now, with purpose built applications that you're seeing now and horizontally scalable, vertically integrated machine learning. You can't hide the ball anymore around what's working. You can't put a project out there and say no, you can't justify. You can't put you can put lipstick on that. You can't know you're seeing on >>that bad cake. Yeah, it's all the point of beta testing and market adoption. You try, you put it there. It works. You say the brake doesn't work. You try again, right? That's the way it works. And and in Telco, you're right. We were cooking for a year or two years, Three years and saying, Oh, you know what? That's what you need. It doesn't work like this faster now. Yeah, Yeah. And people want to be able to influence and they want to say, I like it. I don't like it. And the market is deciding. >>Speaking of influence, one of the things we know we talk a lot about with A W S and their guests is their customer. First customer obsession focused. You know, the whole reason we're here is that is to serve the customer, talk to me about how customers and joint customers are influencing some of the design choices that you guys are making as you're bringing five due to the cloud. >>So what is important for us? We have to dreams, right? The first one is for consumers. We want consumers to have access to the network so that they feel that they are VIP and often I know you and I, sometimes when we're connected to the network with tropical, we don't get the feeling where a V i p So that's something that's a journey for us to make people feel like they get the service and the network is following them and caring about them for the enterprises. You want to let them decide what they want. You were talking about policy building. They want to come with their own rating engine. They want to come with their own geographical maps. Like here. I have traffic here. I don't need coverage. So we want to open up so that the enterprise decide how they invest, how they spend the money on the network >>giving control back to the end user. Whether that's a consumer or enterprise, >>absolutely giving control to the end user and the enterprises. And we're there to support and accelerate the service for them. >>Mark, I want to ask you about leadership. You mentioned all these new things. Are there your dreams? And it's happening Giving engineers the canvas to paint their own future. It's gonna be fun is fun as you're affecting that change. What can people do as leaders to create that momentum to bring the whole organisation along is their tricks of the trade. Is their best practises >>Absolutely their best practises? Um, we were very much following develops where, you know, as a leader, you don't know, you're just learning and you're exposing and you're sharing. Uh, we're also creating an open world where we're asking all our partners to be open. Sometimes, you know, they feel like a bit challenge. Like, do I want to show what I'm doing? And I would say, Yeah, sure, because you're benefiting between each other. Um, And then you want to give tools to your engineers and your marketers to be fast speed, speed, speed, speed so that they can just play and learn. And at the end of the day, you said it. It's all about fun. You know, if it's fun, it's easy to do >>that. We're having fun here. >>That is true. We always have fun here. Last question for you is talk about some of the things that AWS announced this morning. Lots of stuff going on in Adam's keynote. What excites you about this continued partnership between AWS and Dish? >>Yeah, we were. We were surprised and so happy about AWS answer to when we came in with the first one to come big time in the telco and the Cloud was not ready. To be honest, it was Enterprise and Data Club and AWS. When is going all the way, we've asked to transform their cloud to make it a telco frantic, loud. So we have a lot of discussions about networking, routing, service level agreements and a lot of things that are very technical. And there are a true partner innovating with us. We have a road map with ideas and that's pretty unique. So, great partner, >>I was going to say it sounds like a really true >>trust and partnership. We're sharing ideas and challenging each other all the time, so that's really great. >>Awesome and users benefit consumers Benefit enterprises benefit Mark Thank you for joining Joining me on the programme today. Georgia Keynote enjoyed hearing more about dish and AWS. And what are you doing to power? The future. We appreciate your time. >>Thank you. Thank you >>for John Ferrier. I'm Lisa Martin. You're watching the Cube? The global leader in tech coverage, So mhm. Yeah.

>> Announcer: From around the globe, it's theCUBE, with digital coverage of AWS re:Invent 2020. Special coverage sponsored by AWS Worldwide Public Sector. >> Welcome to theCUBE Virtual and our coverage of AWS re:Invent 2020, the specialized programming for Worldwide Public Sector. I'm Lisa Martin. I'm joined by Nick Speece the chief federal technologist for Snowflake. Nick, welcome to theCUBE. >> Thank you, Lisa. It's great to be here. >> Likewise, chief federal technologist, that's the first time I've ever heard of that title. Tell me a little bit about that. >> It's probably the last time you'll hear it. So chief federal technologist is really somebody in the company who is focused on bringing the needs of the federal government back to our corporate headquarters, making sure that the product as it's developed and evolves has the federal requirements in mind. >> Excellent. So the last couple of months for Snowflake big, biggest software IPO and software history your market cap right now is at 66 billion 515 data workloads running on Snowflake's platform every day 250 petabytes of data under management, a lot is going on. Let's talk about Snowflake. You guys operate only in the cloud, why was that decision made and how does that impact businesses analysis of data? >> Yeah, so great question and the answer is actually in the opening that you gave for us and thank you for that reinforcement. Snowflake can't exist anywhere, but the cloud. Technology over the last five to 10 years has really seen a move from what the cloud originally was, which was I have a virtual machine in my data center, I'm going to run it on your stuff not mine, into more comprehensive service offerings like Snowflake. We can't reach the kind of scale that Snowflake operates at every day and that our customers demand without the technology of clouds like AWS. The technology has to be there, the underlying and underpinning architecture has to be there, otherwise our customers get left in the dark and we can't can't have that. >> And especially today as data volumes are massively increasing and we know that that's only going to go up. We know that IT is only going to be more complex but when we talk to businesses in any industry the value of the data is in the insights the ability to extract that data in real time glean insights from it so that businesses can make data-based decisions that pivot their business, especially critical during the year that we have now known as 2020. Talk to me a little bit about though digging into your marketing material, everyone, there's all these terms, right, that everyone uses and you guys use single source of truth. What does it actually mean for single source, for stuff like? >> Yeah, so we talk about cloud, we talk about single source of truth and when you're looking at data problems, the problem and the solution are the same thing. A massive amount of data is a raw resource, that's all it is. And trying to refine that raw resource into something that is insightful or something that is useful to a business process is a challenge that every customer in every market, in every region undergoes. And how you overcome that is critical. And one of the primary focuses of Snowflake is to evolve the data cloud. Snowflake platform is the underlying technology for the data cloud but the data cloud is where we're going. And what I mean by data cloud. If you have a data set, your internal data, that is your truth, but it might not be the truth. So in Snowflake we encourage our customers to collaborate on data sets. For example, if you want to know how many people are living in a certain borough in New York City you could go around with a clicker and count everyone, or you could just ask the Census Bureau. That's the nature of the data cloud and what we're talking about here. Going to the subject matter experts who have the data that you need, using our marketplace, using our private exchanges, using our data sharing to build your own data cloud and become part of the next gen architecture for data sharing and collaboration, to get to the source of the truth, to make better decisions, to gain better insights. It's great to combine your data with enrich data from other sources, especially when it comes to making federal decisions and governance decisions. >> Absolutely that's critical. That the biggest challenge customers have is being able to sort through all that and find. I like how you put this as their single source of truth. Can you give us some examples of some federal agencies maybe even just anonymously that are using the power of Snowflake to do just that? >> Absolutely. We've got customers in the healthcare space and in some of the law enforcement spaces and especially in public education that are trying to increase the awareness of the folks that are subscribing to their services, for example, folks that are looking for healthcare help. If you're filing claims for a certain healthcare providers or certain care facilities, we want to make sure that those claims that are forwarded to those entities are legitimate, first of all, for example, if you're filing a claim for knee surgery in Florida, you probably didn't have one in California, three hours later. So those kinds of enforcement activities, and not just trying to do audits but also to benefit everybody who's receiving care. There's a lot of push now about genetic sequencing, DNA and RNA vaccination is huge with COVID-19, getting access to massive amounts of data to do analysis against and figure out the best approach, that's critical for where we go in the next 10 to 15 years in healthcare. Snowflake is very, very honored and happy to be propelling that move in the healthcare space. >> It is that's going to be absolutely critical but we're also seeing it, you know, everywhere else, such as for universities and education, suddenly this need, the last few months for real-time learning. Talk to me about data analysis. Can Snowflake help companies, you talked about enriching data sets so not just companies sources of data but additional data sets that they can add in and evaluate and analyze to make great decisions, but from a historical real-time perspective, talk to me how Snowflake helps with that data analysis. >> Yeah, sure. Right. So Snowflake in and of itself can do some analysis work. We've got some great visualization tools in our new UI that was released recently on public preview. So there's some analysis tools built into Snowflake but really where the value comes from is in taking your tools that you already use today and connecting it to a data source or platform that can wrangle that data, that can move that data through automated pipelines to give you a model view of that data that's beneficial. For example, data scientists and data engineers spend 80% of their time, and I know a lot of statistics are made up on the spot, that was not a promise, but trying to move this data through and refine it and build features to get to the point where you can ask a question is 80% of these very valuable professionals time. Shortening those timelines is what Snowflake really aims to do in the analysis space. We're not trying to replace the analysis tools that you use today, we work fine with all of them. The big difference is presenting them with enough data volume to give you real insights and eliminate bias as much as we can in data sets. >> What are some of the things that differentiates Snowflake from data warehouses and other folks in the market? >> Yeah. Great question. The big difference is Snowflake was built natively for the cloud. We weren't adapted to the cloud, we didn't adopt the cloud at some point in the future, Snowflake was built from scratch to be in the cloud. And since this is the appropriate show to mention it the primary difference between us is we were built to use object storage foundationally underneath our technology. And I know that sounds really nerdy and it is, but it adds a tremendous amount of value. If you think about how we used to collaborate 10 years ago we'd have a spreadsheet that if I open that spreadsheet for my share drive and you tried to open it at the same time, you'd get locked out. You're told you couldn't have it. And if tradition stays true I would probably be on vacation for two weeks. Contrast that now with the massive Google Doc platform and Office 365, object storage has changed the way that we collaborate on the same kinds of documents. Multiple people interacting with one thing at one time without contention, that's the reason why Snowflake has to operate in the cloud. We bring that same paradigm, multiple actors on a single object and give you that source of truth the truth that you absolutely need to make decisions. >> And that's critical these days as we know. We're in living in uncertain times and one of the things I think we can expect is the uncertainty to continue, but also for many industries people to stay remote or some big percentage for quite a while. So the ability to have those collaboration tools and be able to collaborate in real time is table stakes for so many companies. But when we're talking about some of the things going on this year, security, we can't not talk about security. You know, all these folks from home accessing corporate networks, you know, maybe not through VPNs or behind firewalls, the cloud is paramount to that. How does Snowflake address the security issue? >> Absolutely. So I'll start by saying our security is inherited from the wonderful security platform that AWS has underneath it. So we inherit all the security around data storage the EC Compute, all of the different entities and end points that AWS already secures Snowflake takes the same precautions. More than that, we've also built and rolled this access control to ensure that people are getting access only to the data that they should be getting access to, we recently implemented data masking as well, so certain roles are not able to see unmasked data, but they can still do queries that use the underlying data to filter. So there's a lot of different capabilities built in, encryption at rest, encryption in flight, AES-256 encryption keys used in a hierarchial model. These are phenomenal security architectures that are paramount to the security of the folks that are using our platform. Because we know at the end of the day the first day we have a leak in Snowflake is probably our last day in business. We got to be good at that which is why it's our top priority. >> I didn't, to ever talk about security as an inherited, I must be a dominant trait if we're going to be talking about, you know, genetics and chromosomes and mRNA and things like that. So walk me through last question, a government organization, or say they're an AWS customer or they want to start using Snowflake, what's that process? How do they go about doing that to leverage those inherited security capabilities that you talked about? >> Well, thankfully AWS has helped us put a FedRAMP moderate certified Snowflake region together in AWS, East commercial, so we're very happy to have a FedRAMP moderate region. They can access Snowflake through the AWS Marketplace or from Snowflake.com, you can start a trial in just a couple of minutes. Our security is built into all of our regions although the FedRAMP regions are specialized in some of the encryption technology we use, but we always, always always protect our users' data, regardless of where it is. >> You make it sound easy, I got to say. (laughing) >> That's because it is. (laughing) Thank you cloud. >> That's good. And well, that's good and it should be, especially because there's so much complexity and uncertainty everywhere else in the world right now. Last question for you. As I mentioned in the beginning, the biggest IPO in software history, just a couple of months ago during probably one of the most strangest time of any of us have ever, and our relatives ever witnessed, what can we expect from Snowflake in 2021? Are you going to bring all the good vibes that we all need? (laughing) >> Well, good vibes is our business model. You know, Snowflake is a phenomenal platform. We've had a ton of success driven by the success of our cloud provider partners, driven by the success of our wonderful customers. We have over 4,000 people using Snowflake now to great effect. You can look for more features, you can look for more functions, but really the evolution of the data cloud, our big push is to help our customers get into the data cloud, get the truth out of their data and make better decisions every day. And you'll see more of that from us as time continues. >> One more question I wanted to sneak in, how did you work with those customers to evolve the data cloud? What's that feedback loop like? >> It's, a lot of it comes down to silos that the customers have built up over years and years and years of operation. That's the first step. In Snowflake there isn't such thing really as a data silo there's data put into Snowflake, everything is unified, you can do queries across databases, that's the first thing. The second thing is browsing our data marketplace. It's just like an App Store for your phone but instead it's data sets and the data sets are published by the experts who know that material better than anyone. I mentioned earlier bringing in everything from housing evaluation data to COVID-19 data from California and Boston, bringing World Health Organization data, John Hopkins University data, joining that with the data that you already use today along with weather and population counts, the main thing here, the strategy is almost endless. More and more data sets are being published over every day. We have over a hundred contributors in the marketplace now. >> That's exciting that we have the technology and the power like this to help the world re, you know, recover from such a crazy time. It's nice to know that, that there was the power of that behind that, and the smart folks like you chief federal technologists, helping to fine tune that and really ensure that organizations across the government can maximize the value of data and find their single source of truth. Nick, it's been a blast having you on theCUBE. Thank you for joining me. >> Thank you for having me. >> For next piece, I'm Lisa Martin. You're watching theCUBE Virtual. (upbeat music)

>> Narrator: From around the globe, it's theCUBE. With digital coverage of AWS Reinvent Executive Summit 2020. Sponsored by Accenture and AWS. >> Welcome everyone to theCUBE virtual coverage of the Accenture Executive Summit part of AWS Re-invent 2020. I'm your host, Rebecca Knight. We are talking today about reinventing the energy data platform. We have two guests joining us. First, we have Johan Krebbers. He is the GM Digital Emerging Technologies and VP of IT Innovation at Shell. Thank you so much for coming on the show, Johan. >> You're welcome. >> Rebecca: And next we have Liz Dennett. She is the Lead Solution Architect for OSDU on AWS. Thank you so much Liz. >> Happy to be here. >> So I want to start our conversation by talking about OSDU. Like so many great innovations, it started with a problem. Johann, what was the problem you were trying to solve at Shell? >> Yeah, let's go back a couple of the years. We started summer 2017, where we had a meeting with the guys from exploration in Shell. And the main problem they had of course they got lots and lots of data, but aren't unable to find the right data they need to work from. Well the data was scattered and is scattered, it was scattered it's all over the place. And so the real problem trying to solve is how that person working in exploration could find their proper data, not just the data also the data really needed. That's what we probably talked about in summer 2017. And we said, "Okay, the only way we see this moving forward is to start pulling that data into a single data platform." And that was at the time that we called it OSDU, the Open Subsurface Data Universe, and that was what the Shell name was. So, in January 2018, we start a project with Amazon to start creating and confronting the building that OSDU environment, that subservient the universe. So that single data platform to put all your exploration and wealth data into a single environment that was the intent. And then we said, already in March of that same year, we said, 'Well, from a Shell point of view, we would be far better off if we could make this an industry solution and not just a Shell solution." Because Shell will be, if you can make this an industry solution, but people start developing applications for it also, it's far better than for Shell to say, we have it Shell special solution. Because we don't make money out of how we store the data we can make money out of we have access to the data, we can exploit the data. So storing the data, we should do as efficiently possibly can. So in March we reached out to about eight or nine other large oil and gas operators, like the ECONOS, like the Totals, like the Chevrons of this world they said, "Hey, we in Shell are doing this, do you want to join this effort?" And to our surprise, they all said yes. And then in September 2018 we had our kick-off meeting with the open group, where we said, "Okay, if you want to work together with lots of other companies, we also need to look a bit at how we organize that." Because if you start working with lots of large companies you need to have some legal framework around it. So that's why, we went to the open group and said," Okay, let's form the OSDU forum." As we call it at the time. So in September, 2018 where I had a Galleria in Houston we had a kick off meeting for the OSDU forum with about 10 members at the time. So there's, just over two years ago, we started to exercise formally we called it OSDU, we kicked it off. And so that's really where we coming from and how we got there also. >> The origin story. >> Yes. >> What, so what, digging a little deeper there, what were some of the things you were trying to achieve with the OSDU? >> Well, a couple of things we've tried to achieve with OSDU. First is really separating data from applications. But what is the biggest problem we have in the subsurface space that the data and applications are all interlinked. They are all tied together and if you have then a new company coming along and say, "I have this new application, and needs access to the data." That is not possible because the data often interlinked with the application. The first thing we did is, really breaking the link between the application and the data. So that was the first thing we did. Secondly, put all the data to a single data platform, take the silos out because what was happening in the subsurface space I mean, they got all the data in what we call silos, in small little islands out there. So we try to do is, first, break the link. Two, create, put the data in a single data platform. And then third part, put a standard layer on top of that the same API layer on top of the created platform so we could create an ecosystem out of companies to start developing software applications on top of that data platform. Because you might have a data platform, but you aren't successful if you have a rich ecosystem of people start developing applications on top of that. And then you can exploit the data like small companies, large companies, universities, you name it. But you have to create an ecosystem out of there. So the three things was, first break the link between the application data, just break it and put data at the center. And also make sure that data, this data structure would not be managed by one company. But it would be managed the data structures, by the OSDU forum. Secondly then, put the data, single data platform. Thirdly then, have an API layer on top and then create an ecosystem, really go for people, say, "Please start developing applications." Because now you have access to the data, because the data is no longer linked to somebody's application was all freely available for an API layer. That was all September, 2018, more or less. >> Liz I want to bring you, in here a little bit. >> Yeah. >> Can you talk a little bit some of the imperatives from the AWS standpoint in terms of what you were trying to achieve with this? >> Yeah, absolutely. And this whole thing is Johan said, started with a challenge that was really brought out at Shell. The challenges that geoscientists spend up to 70% of their time looking for data. I'm a geologist I've spent more than 70% of my time trying to find data in these silos. And from there, instead of just figuring out, how we could address that one problem, we worked together to really understand the root cause of these challenges. And working backwards from that use case, OSDU and OSDU on AWS has really enabled customers to create solutions that span not just this in particular problem. But can really scale to be inclusive of the entire energy value chain and deliver value from these used cases to the energy industry and beyond. >> Thank you. Johan, so talk a little bit about Accenture's Cloud First approach and how it has helped Shell work faster and better with speed. >> Well, of course Accenture Cloud First approach, really works together with Amazon environment, AWS environment. So we really look at Accenture and Amazon together, helping Shell in this space. Now the combination of the two is what we're really looking at where access of course can bring business knowledge to that environment, operate support knowledge to an environment and of course Amazon will be bring that to this environment, that underpinning services, et cetera. So we would expect of that combination, a lot of goods when we started rolling out in production, the other two or three environment. And probably our aim is, when a release fee comes to the market, in Q1 next year of OSDU have already started going out in production inside Shell. But as the first OSDU release which is ready for prime time production across an enterprise. Well we have released our one just before Christmas, last year, released two in May of this year. But release three is the first release we want to use for full scale production and deployment inside Shell and also all the operators around the world. And there is what Amazon, sorry and there when Accenture can play a role in the ongoing, in the deployment building up, but also support environment. >> So one of the other things that we talk a lot about here on theCUBE is sustainability and this is a big imperative at so many organizations around the world in particular energy companies. How does this move to OSDU, help organizations become how is this a greener solution for companies? >> Well, first we make, it's a great solution because you start making a much more efficient use of your resources, which is a really important one. The second thing we're doing is also we started with OSDU in very much in the oil and gas space, within the export development space. We've grown OSDU but in our strategy, we've grown OSDU now also to an alternative energy source. So obviously we'll all start supporting next year things like solar farms, wind farms, the geothermal environment, hydrogen. So it becomes an open energy data platform not just for the oil and gas industry, but for any type of industry, any type of energy industry. So our focus is to create, bring the data of all those various energy data sources together into a single data platform. You're going to use AI and other technology on top of that, to exploit the data to be together into a single data platform. >> Liz, I want to ask you about security, because security is such a big concern when it comes to data. How secure is the data on OSDU? >> Actually, can I talk, can I do a follow-up on the sustainability talking? >> Absolutely by all means. >> I mean, I want to interject, though security is absolutely our top priority I don't mean to move away from that but with sustainability, in addition to the benefits of the OSDU data platform. When a company moves from on-prem to the cloud they're also able to leverage the benefits of scale. Now, AWS is committed to running our business in the most environmentally friendly way possible. And our scale allows us to achieve higher resource utilization and energy efficiency than a typical on-prem data center. Now, a recent study by 451 research found that, AWS's infrastructure, is 3.6 times more energy efficient than the median of surveyed enterprise data centers. Two thirds of that advantage is due to a higher server utilization and a more energy efficient server population. But when you factor in the carbon intensity of consumed electricity and renewable energy purchases 451 found that, AWS performs the same task with an 88% lower carbon footprint. Now that's just another way that AWS and OSDU are working to support our customers as they seek to better understand their workflows and make their legacy businesses less carbon intensive. >> That's, those statistics are incredible. Do you want to talk a little bit now about security? >> Absolutely yeah. Security will always be AWS's top priority. In fact, AWS has been architected to be the most flexible and secure cloud computing environment available today. Our core infrastructure is built to satisfy the security requirements for the military, global banks and other high sensitivity organizations. And in fact, AWS uses the same secure hardware and software to build and operate each of our regions. So that customers benefit from the only commercial cloud that's had hit service offerings and associated supply chain vetted and deemed secure enough for top secret workloads. That's backed by a deep set of cloud security tools with more than 200 security compliance and governmental service and key features. As well as an ecosystem of partners like Accenture, that can really help our customers to make sure that their environments for their data meet and or exceed their security requirements. >> Johann, I want you to talk a little bit about how OSDU you can be used today. Does it only handle subsurface data? >> Today is 100 subsets of wells data we go to add that to that production around the middle of next year. That means that the whole upstream business we got included every piece goes from exploration all the way to production, you bring it together into a single data platform. So production will be added around Q3 of next year. Then in principle, we have a typical elder data, a single environment and we're going to extend them to other data sources or energy sources like solar farms, wind farms, hydrogen, hydro, et cetera. So we're going to add a whole list of other day energy source to that and bring all the data together into a single data platform. So we move from an oil and gas data platform to an energy data platform. That's really what our objective is because the whole industry if you look at our companies all moving in that same direction of course are very strong in oil and gas but also increasingly go into other energy sources like solar, like wind, like hydrogen et cetera. So we move exactly with the same method, that the whole OSDU, can really support that whole energy spectrum of energy sources, of course. >> And Liz and Johan, I want you to close us out here by just giving us a look into your crystal balls and talking about the five and 10 year plan for OSDU. We'll start with you, Liz. What do you see as the future holding for this platform? >> Honestly, the incredibly cool thing about working at AWS is you never know where the innovation and the journey is going to take you. I personally am looking forward to work with our customers wherever their OSDU journeys, take them whether it's enabling new energy solutions or continuing to expand, to support use cases throughout the energy value chain and beyond but really looking forward to continuing to partner as we innovate to slay tomorrow's challenges. >> Johan. >> Yeah, first nobody can look that far ahead anymore nowadays, especially 10 years. I mean, who knows what happens in 10 years? But if you look what our objective is that really in the next five years, OSDU will become the key backbone for energy companies for storing your data, new artificial intelligence and optimize the whole supply, the energy supply chain in this world out here. >> Johan Krebbers, Liz Dennett thank you so much for coming on theCUBE virtual. >> Thank you. >> Thank you. >> I'm Rebecca Knight stay tuned for more of our coverage of the Accenture Executive Summit. (tranquil music).

>> Live from Las Vegas, it's theCUBE, covering AWS re:Invent 2018. Brought to you by Amazon Web Services, Intel and their ecosystem partners. >> Welcome back. Here live on theCUBE, which we continue our day one coverage of AWS re:Invent, along Lauren Cooney. I'm John Walls and 40,000 of our best friends. >> Closest friends. >> That's right. It's a great venue. The Sands is. We're joined now by Tyson Clark. He's the technical director of Air Bud Entertainment. Tyson, thanks for joining us here on theCUBE. >> Thank you for having me. >> First off, let's talk about Air Bud. I mean so, you guys made Air Bud, right? >> We did. >> And you have other projects going as well? >> Yep. Right now we're working on a TV series for Disney. It's going to be about 22 episodes teaching how puppies become puppies while their owners are at school. >> How puppies become puppies? >> How puppies become puppies! >> Coming to a theater, maybe a TV channel near you? >> Disney Streaming. >> Disney Streaming? Good enough, fair enough. >> Aw, very cool. >> Alright tell us about technical director. So, you're the IT guy. >> I am the IT guy. >> You're handling a multitude of problems from a lot of different stakeholders. Tell us about it. >> So I do everything from password reset and the easy stuff all the way up to the most complicated, setting up our whole network, rendered farms, et cetera. >> So you're doing full stack IT? >> I'm doing absolutely everything. Full stack, everything. >> That's pretty impressive. >> A rare breed. >> It is. It's definitely a hand full. >> What do you work on that I would say, we've been talking to folks, like Cohesity and things along those lines. Do you use Cohesity? What are some of the things that you do with them? >> I definitely use Cohesity for our backups. They are a lifesaver. Tape backup just wasn't cutting it for us. We were generating way too much data to be able back it up to tape. Cohesity has allowed us to backup to that and pass it off to the cloud for archival. >> Well, wow. >> Sp what, in terms of the entertainment company, you talk about the data that their generating. >> Yes. >> I mean what are they trying to keep track of? What are you trying to do for them in that respect that hasn't been done before? >> So what we're doing is when we film something, we don't want to get rid of those assets. They're pretty expensive to make. So, we got to hold on to them. We got to make sure they're all recorded. We pass it off to the cloud for archival and then, next movie, say we need a dog from that movie, or an object we built. We can always bring it back and then reuse it. >> From a security standpoint, because there have been some instances-- >> Some pretty bad ones, yep. >> Where's that fit on your pyramid of concern? >> That's extremely high. In the media entertainment business it's very strict on what security rules are. We're right up there. It's pretty much number one. >> Great, so what do you hear? What's interesting for you here at AWS re:Invent? >> Pardon me? >> What is interesting for you here at AWS re:Invent? What are the things that you see as exciting and that you really want to put your hands on? >> Well, what I'm really interested in right is being able to burst in the cloud. So I'm trying to find a solution that will let me scale out my render farm on demand, instantly, pretty much. So, going up to, who knows how many cores. Just to get that render through so we can get our shots done in time. >> Great, anyone that you're looking at here? >> Not yet. Still trying to look around and find someone. >> Very cool. >> A lot of good contenders. >> So what is it in terms of how your job has evolved? If you had to cite, these are probably two or three of maybe the larger concerns that we've had that are being addressed now and fast forward that to next step, next iteration about what kind of, if there's anything that keeps you up at night, what that is? >> Well, what keeps me up at night right now is switching to 4K. A lot of people think you just flip the switch, it's easy, but that means we have four times the amount of data. It takes twice as long to render. It takes four times longer to move things around. It just, it's insane. >> So you're really excited about 5G? >> 5G will help, but right now we're looking at quadrupling pretty much all our storage. It's going to be a very exciting time and a very scary time for us. >> Who are you stakeholders, internally, and how do you handle them? Because I assume that its a dispersate group. You've got a lot of different people with a lot of different priorities, and because you're wearing that IT hat, you're the guy. You're the department that everybody's coming to for answers. >> The biggest person I deal with, personally is the CFO. The other one is the CEO, and they're both worried because I'm telling them I need to buy $5 million worth of infrastructure. The only way I can justify that is showing them. Hey look, it's working better than it was ever before. It's a better product every day. >> Yeah and we're seeing that more and more across the board with IT really having to be the partner of the CFO to actually get the budget to do what you want to do. I think that's pretty consistent for organizations that want to move forward. >> And the budgets are just getting bigger and bigger unfortunately. >> Do you find that rationalizing becomes, is a more critical factor now? >> Absolutely. Before you could get away with a lot smaller, like 10 terabytes was great. Now we're looking at petabytes. It's definitely, rationalizing is needed a lot more now. >> Is there anybody beyond the CFO? I would assume. You're got a lot of people knocking, or CFO, a lot of people knocking on your door. Hey Tyson. I need this, I need this. >> The CFO and the CEO are two best friends, and they're both the top dogs. They're the ones kind of running the whole show there. I'm pretty lucky in that aspect. >> What are you going to do to help solve their problems? Say in the coming year, if you had to say, okay this is going to be a bottleneck. This is going to be a problem. This is how I'm going to address it. What would that be for you in 2019? >> The biggest bottleneck, like I said, is just going to be data. We've got to get four time more or our Isilon. We've got to get four time more of our Qumulo. We've also have to get four times more of our Cohesity, and that's the main part. If we don't have that cohesity, we're done. >> Well I can solve a problem for you for next year. If you're looking for another dog, Lauren's got this gorgeous mix of dane lab. About 120 pounder. >> His name is Milo. He'd be perfect for a film. >> Milo, all right. >> Perfect. >> Just let us know if you need help next year. >> Absolutely. As long as that dog loves treats. >> I'm sure that's not a problem. Tyson, thanks for being with us. >> Thank you so much. >> Thank you so much. >> We'll continue our coverage here, live on theCUBE. We're at AWS re:Invent in Las Vegas. (upbeat music)

>> Live from Las Vegas, it's theCUBE, covering AWS re:Invent 2018. Brought to you by Amazon Web Services, Intel and their ecosystem partners. >> Welcome back. Here live on theCUBE, which we continue our day one coverage of AWS re:Invent, along Lauren Cooney. I'm John Walls and 40,000 of our best friends. >> Closest friends. >> That's right. It's a great venue. The Sands is. We're joined now by Tyson Clark. He's the technical director of Air Bud Entertainment. Tyson, thanks for joining us here on theCUBE. >> Thank you for having me. >> First off, let's talk about Air Bud. I mean so, you guys made Air Bud, right? >> We did. >> And you have other projects going as well? >> Yep. Right now we're working on a TV series for Disney. It's going to be about 22 episodes teaching how puppies become puppies while their owners are at school. >> How puppies become puppies? >> How puppies become puppies! >> Coming to a theater, maybe a TV channel near you? >> Disney Streaming. >> Disney Streaming? Good enough, fair enough. >> Aw, very cool. >> Alright tell us about technical director. So, you're the IT guy. >> I am the IT guy. >> You're handling a multitude of problems from a lot of different stakeholders. Tell us about it. >> So I do everything from password reset and the easy stuff all the way up to the most complicated, setting up our whole network, rendered farms, et cetera. >> So you're doing full stack IT? >> I'm doing absolutely everything. Full stack, everything. >> That's pretty impressive. >> A rare breed. >> It is. It's definitely a hand full. >> What do you work on that I would say, we've been talking to folks, like Cohesity and things along those lines. Do you use Cohesity? What are some of the things that you do with them? >> I definitely use Cohesity for our backups. They are a lifesaver. Tape backup just wasn't cutting it for us. We were generating way too much data to be able back it up to tape. Cohesity has allowed us to backup to that and pass it off to the cloud for archival. >> Well, wow. >> Sp what, in terms of the entertainment company, you talk about the data that their generating. >> Yes. >> I mean what are they trying to keep track of? What are you trying to do for them in that respect that hasn't been done before? >> So what we're doing is when we film something, we don't want to get rid of those assets. They're pretty expensive to make. So, we got to hold on to them. We got to make sure they're all recorded. We pass it off to the cloud for archival and then, next movie, say we need a dog from that movie, or an object we built. We can always bring it back and then reuse it. >> From a security standpoint, because there have been some instances-- >> Some pretty bad ones, yep. >> Where's that fit on your pyramid of concern? >> That's extremely high. In the media entertainment business it's very strict on what security rules are. We're right up there. It's pretty much number one. >> Great, so what do you hear? What's interesting for you here at AWS re:Invent? >> Pardon me? >> What is interesting for you here at AWS re:Invent? What are the things that you see as exciting and that you really want to put your hands on? >> Well, what I'm really interested in right is being able to burst in the cloud. So I'm trying to find a solution that will let me scale out my render farm on demand, instantly, pretty much. So, going up to, who knows how many cores. Just to get that render through so we can get our shots done in time. >> Great, anyone that you're looking at here? >> Not yet. Still trying to look around and find someone. >> Very cool. >> A lot of good contenders. >> So what is it in terms of how your job has evolved? If you had to cite, these are probably two or three of maybe the larger concerns that we've had that are being addressed now and fast forward that to next step, next iteration about what kind of, if there's anything that keeps you up at night, what that is? >> Well, what keeps me up at night right now is switching to 4K. A lot of people think you just flip the switch, it's easy, but that means we have four times the amount of data. It takes twice as long to render. It takes four times longer to move things around. It just, it's insane. >> So you're really excited about 5G? >> 5G will help, but right now we're looking at quadrupling pretty much all our storage. It's going to be a very exciting time and a very scary time for us. >> Who are you stakeholders, internally, and how do you handle them? Because I assume that its a dispersate group. You've got a lot of different people with a lot of different priorities, and because you're wearing that IT hat, you're the guy. You're the department that everybody's coming to for answers. >> The biggest person I deal with, personally is the CFO. The other one is the CEO, and they're both worried because I'm telling them I need to buy $5 million worth of infrastructure. The only way I can justify that is showing them. Hey look, it's working better than it was ever before. It's a better product every day. >> Yeah and we're seeing that more and more across the board with IT really having to be the partner of the CFO to actually get the budget to do what you want to do. I think that's pretty consistent for organizations that want to move forward. >> And the budgets are just getting bigger and bigger unfortunately. >> Do you find that rationalizing becomes, is a more critical factor now? >> Absolutely. Before you could get away with a lot smaller, like 10 terabytes was great. Now we're looking at petabytes. It's definitely, rationalizing is needed a lot more now. >> Is there anybody beyond the CFO? I would assume. You're got a lot of people knocking, or CFO, a lot of people knocking on your door. Hey Tyson. I need this, I need this. >> The CFO and the CEO are two best friends, and they're both the top dogs. They're the ones kind of running the whole show there. I'm pretty lucky in that aspect. >> What are you going to do to help solve their problems? Say in the coming year, if you had to say, okay this is going to be a bottleneck. This is going to be a problem. This is how I'm going to address it. What would that be for you in 2019? >> The biggest bottleneck, like I said, is just going to be data. We've got to get four time more or our Isilon. We've got to get four time more of our Qumulo. We've also have to get four times more of our Cohesity, and that's the main part. If we don't have that cohesity, we're done. >> Well I can solve a problem for you for next year. If you're looking for another dog, Lauren's got this gorgeous mix of dane lab. About 120 pounder. >> His name is Milo. He'd be perfect for a film. >> Milo, all right. >> Perfect. >> Just let us know if you need help next year. >> Absolutely. As long as that dog loves treats. >> I'm sure that's not a problem. Tyson, thanks for being with us. >> Thank you so much. >> Thank you so much. >> We'll continue our coverage here, live on theCUBE. We're at AWS re:Invent in Las Vegas. (upbeat music)