>> Announcer: theCUBE's live coverage is made possible by funding from Dell Technologies. Creating technologies that drive human progress. (upbeat music) >> Hi everybody. Welcome back to Barcelona. We're here at the Fira Live, theCUBE's ongoing coverage of day two of MWC 23. Back in 2021 was my first Mobile World Congress. And you know what? It was actually quite an experience because there was nobody there. I talked to my friend, who's now my co-host, Chris Lewis about what to expect. He said, Dave, I don't think a lot of people are going to be there, but Danielle Royston is here and she's the CEO of Totoge. And that year when Erickson tapped out of its space she took out 60,000 square feet and built out Cloud City. If it weren't for Cloud City, there would've been no Mobile World Congress in June and July of 2021. DR is back. Great to see you. Thanks for coming on. >> It's great to see you. >> Chris. Awesome to see you. >> Yeah, Chris. Yep. >> Good to be back. Yep. >> You guys remember the narrative back then. There was this lady running around this crazy lady that I met at at Google Cloud next saying >> Yeah. Yeah. >> the cloud's going to take over Telco. And everybody's like, well, this lady's nuts. The cloud's been leaning in, you know? >> Yeah. >> So what do you think, I mean, what's changed since since you first caused all those ripples? >> I mean, I have to say that I think that I caused a lot of change in the industry. I was talking to leaders over at AWS yesterday and they were like, we've never seen someone push like you have and change so much in a short period of time. And Telco moves slow. It's known for that. And they're like, you are pushing buttons and you're getting people to change and thank you and keep going. And so it's been great. It's awesome. >> Yeah. I mean, it was interesting, Chris, we heard on the keynotes we had Microsoft, Satya came in, Thomas Curian came in. There was no AWS. And now I asked CMO of GSMA about that. She goes, hey, we got a great relationship with it, AWS. >> Danielle: Yeah. >> But why do you think they weren't here? >> Well, they, I mean, they are here. >> Mean, not here. Why do you think they weren't profiled? >> They weren't on the keynote stage. >> But, you know, at AWS, a lot of the times they want to be the main thing. They want to be the main part of the show. They don't like sharing the limelight. I think they just didn't want be on the stage with the Google CLoud guys and the these other guys, what they're doing they're building out, they're doing so much stuff. As Danielle said, with Telcos change in the ecosystem which is what's happening with cloud. Cloud's making the Telcos think about what the next move is, how they fit in with the way other people do business. Right? So Telcos never used to have to listen to anybody. They only listened to themselves and they dictated the way things were done. They're very successful and made a lot of money but they're now having to open up they're having to leverage the cloud they're having to leverage the services that (indistinct words) and people out provide and they're changing the way they work. >> So, okay in 2021, we talked a lot about the cloud as a potential disruptor, and your whole premise was, look you got to lean into the cloud, or you're screwed. >> Danielle: Yeah. >> But the flip side of that is, if they lean into the cloud too much, they might be screwed. >> Danielle: Yeah. >> So what's that equilibrium? Have they been able to find it? Are you working with just the disruptors or how's that? >> No I think they're finding it right. So my talk at MWC 21 was all about the cloud is a double-edged sword, right? There's two sides to it, and you definitely need to proceed through it with caution, but also I don't know that you have a choice, right? I mean, the multicloud, you know is there another industry that spends more on CapEx than Telco? >> No. >> Right. The hyperscalers are doing it right. They spend, you know, easily approaching over a $100 billion in CapEx that rivals this industry. And so when you have a player like that an industry driving, you know and investing so much Telco, you're always complaining how everyone's riding your coattails. This is the opportunity to write someone else's coattails. So jump on, right? I think you don't have a choice especially if other Telco competitors are using hyperscalers and you don't, they're going to be left behind. >> So you advise these companies all the time, but >> I mean, the issue is they're all they're all using all the hyperscalers, right? So they're the multi, the multiple relationships. And as Danielle said, the multi-layer of relationship they're using the hyperscalers to change their own internal operational environments to become more IT-centric to move to that software centric Telco. And they're also then with the hyperscalers going to market in different ways sometimes with them, sometimes competing with them. What what it means from an analyst point of view is you're suddenly changing the dynamic of a market where we used to have nicely well defined markets previously. Now they're, everyone's in it together, you know, it's great. And, and it's making people change the way they think about services. What I, what I really hope it changes more than anything else is the way the customers at the end of the, at the end of the supply, the value chain think this is what we can get hold of this stuff. Now we can go into the network through the cloud and we can get those APIs. We can draw on the mechanisms we need to to run our personal lives, to run our business lives. And frankly, society as a whole. It's really exciting. >> Then your premise is basically you were saying they should ride on the top over the top of the cloud vendor. >> Yeah. Right? >> No. Okay. But don't they lose the, all the data if they do that? >> I don't know. I mean, I think the hyperscalers are not going to take their data, right? I mean, that would be a really really bad business move if Google Cloud and Azure and and AWS start to take over that, that data. >> But they can't take it. >> They can't. >> From regulate, from sovereignty and regulation. >> They can't because of regulation, but also just like business, right? If they started taking their data and like no enterprises would use them. So I think, I think the data is safe. I think you, obviously every country is different. You got to understand the different rules and regulations for data privacy and, and how you keep it. But I think as we look at the long term, right and we always talk about 10 and 20 years there's going to be a hyperscaler region in every country right? And there will be a way for every Telco to use it. I think their data will be safe. And I think it just, you're going to be able to stand on on the shoulders of someone else for once and use the building blocks of software that these guys provide to make better experiences for subscribers. >> You guys got to explain this to me because when I say data I'm not talking about, you know, personal information. I'm talking about all the telemetry, you know, all the all the, you know the plumbing. >> Danielle: Yeah. >> Data, which is- >> It will increasingly be shared because you need to share it in order to deliver the services in the streamline efficient way that needs to be deliver. >> Did I hear the CEO of Ericsson Wright where basically he said, we're going to charge developers for access to that data through APIs. >> What the Ericsson have done, obviously with the Vage acquisition is they want to get into APIs. So the idea is you're exposing features, quality policy on demand type features for example, or even pulling we still use that a lot of SMS, right? So pulling those out using those APIs. So it will be charged in some way. Whether- >> Man: Like Twitter's charging me for APIs, now I API calls, you >> Know what it is? I think it's Twilio. >> Man: Oh, okay. >> Right. >> Man: No, no, that's sure. >> There's no reason why telcos couldn't provide a Twilio like service itself. >> It's a horizontal play though right? >> Danielle: Correct because developers need to be charged by the API. >> But doesn't there need to be an industry standard to do that as- >> Well. I think that's what they just announced. >> Industry standard. >> Danielle: I think they just announced that. Yeah. Right now I haven't looked at that API set, right? >> There's like eight of them. >> There's eight of them. Twilio has, it's a start you got to start somewhere Dave. (crosstalk) >> And there's all, the TM forum is all the other standard >> Right? Eight is better than zero- >> Right? >> Haven't got plenty. >> I mean for an industry that didn't really understand APIs as a feature, as a product as a service, right? For Mats Granryd, the deputy general of GSMA to stand on the keynote stage and say we partnered and we're unveiling, right. Pay by the use APIs. I was for it. I was like, that is insane. >> I liked his keynote actually, because I thought he was going to talk about how many attendees and how much economic benefiting >> Danielle: We're super diverse. >> He said, I would usually talk about that and you know greening in the network by what you did talk about a little bit. But, but that's, that surprised me. >> Yeah. >> But I've seen in the enterprise this is not my space as, you know, you guys don't live this but I've seen Oracle try to get developers. IBM had to pay $35 billion trying to get for Red Hat to get developers, right? EMC used to have a thing called EMC code, failed. >> I mean they got to do something, right? So 4G they didn't really make the business case the ROI on the investment in the network. Here we are with 5G, same discussion is having where's the use case? How are we going to monetize and make the ROI on this massive investment? And now they're starting to talk about 6G. Same fricking problem is going to happen again. And so I think they need to start experimenting with new ideas. I don't know if it's going to work. I don't know if this new a API network gateway theme that Mats talked about yesterday will work. But they need to start unbundling that unlimited plan. They need to start charging people who are using the network more, more money. Those who are using it less, less. They need to figure this out. This is a crisis for them. >> Yeah our own CEO, I mean she basically said, Hey, I'm for net neutrality, but I want to be able to charge the people that are using it more and more >> To make a return on, on a capital. >> I mean it costs billions of dollars to build these networks, right? And they're valuable. We use them and we talked about this in Cloud City 21, right? The ability to start building better metaverses. And I know that's a buzzword and everyone hates it, but it's true. Like we're working from home. We need- there's got to be a better experience in Zoom in 2D, right? And you need a great network for that metaverse to be awesome. >> You do. But Danielle, you don't need cellular for doing that, do you? So the fixed network is as important. >> Sure. >> And we're at mobile worlds. But actually what we beginning to hear and Crystal Bren did say this exactly, it's about the comp the access is sort of irrelevant. Fixed is better because it's more the cost the return on investment is better from fiber. Mobile we're going to change every so many years because we're a new generation. But we need to get the mechanism in place to deliver that. I actually don't agree that we should everyone should pay differently for what they use. It's a universal service. We need it as individuals. We need to make it sustainable for every user. Let's just not go for the biggest user. It's not, it's not the way to build it. It won't work if you do that you'll crash the system if you do that. And, and the other thing which I disagree on it's not about standing on the shoulders and benefiting from what- It's about cooperating across all levels. The hyperscalers want to work with the telcos as much as the telcos want to work with the hyperscalers. There's a lot of synergy there. There's a lot of ways they can work together. It's not one or the other. >> But I think you're saying let the cloud guys do the heavy lifting and I'm - >> Yeah. >> Not at all. >> And so you don't think so because I feel like the telcos are really good at pipes. They've always been good at pipes. They're engineers. >> Danielle: Yeah. >> Are they hanging on to the to the connectivity or should they let that go and well and go toward the developer. >> I mean AWS had two announcements on the 21st a week before MWC. And one was that telco network builder. This is literally being able to deploy a network capability at AWS with keystrokes. >> As a managed service. >> Danielle: Correct. >> Yeah. >> And so I don't know how the telco world I felt the shock waves, right? I was like, whoa, that seems really big. Because they're taking something that previously was like bread and butter. This is what differentiates each telco and now they've standardized it and made it super easy so anyone can do it. Now do I think the five nines of super crazy hardcore network criteria will be built on AWS this way? Probably not, but no >> It's not, it's not end twin. So you can't, no. >> Right. But private networks could be built with this pretty easily, right? And so telcos that don't have as much funding, right. Smaller, more experiments. I think it's going to change the way we think about building networks in telcos >> And those smaller telcos I think are going to be more developer friendly. >> Danielle: Yeah. >> They're going to have business models that invite those developers in. And that's, it's the disruption's going to come from the ISVs and the workloads that are on top of that. >> Well certainly what Dish is trying to do, right? Dish is trying to build a- they launched it reinvent a developer experience. >> Dave: Yeah. >> Right. Built around their network and you know, again I don't know, they were not part of this group that designed these eight APIs but I'm sure they're looking with great intent on what does this mean for them. They'll probably adopt them because they want people to consume the network as APIs. That's their whole thing that Mark Roanne is trying to do. >> Okay, and then they're doing open ran. But is it- they're not really cons- They're not as concerned as Rakuten with the reliability and is that the right play? >> In this discussion? Open RAN is not an issue. It really is irrelevant. It's relevant for the longer term future of the industry by dis aggregating and being able to share, especially ran sharing, for example, in the short term in rural environments. But we'll see some of that happening and it will change, but it will also influence the way the other, the existing ran providers build their services and offer their value. Look you got to remember in the relationship between the equipment providers and the telcos are very dramatically. Whether it's Ericson, NOKIA, Samsung, Huawei, whoever. So those relations really, and the managed services element to that depends on what skills people have in-house within the telco and what service they're trying to deliver. So there's never one size fits all in this industry. >> You're very balanced in your analysis and I appreciate that. >> I try to be. >> But I am not. (chuckles) >> So when Dr went off, this is my question. When Dr went off a couple years ago on the cloud's going to take over the world, you were skeptical. You gave a approach. Have you? >> I still am. >> Have you moderated your thoughts on that or- >> I believe the telecom industry is is a very strong industry. It's my industry of course I love it. But the relationship it is developing much different relationships with the ecosystem players around it. You mentioned developers, you mentioned the cloud players the equipment guys are changing there's so many moving parts to build the telco of the future that every country needs a very strong telco environment to be able to support the site as a whole. People individuals so- >> Well I think two years ago we were talking about should they or shouldn't they, and now it's an inevitability. >> I don't think we were Danielle. >> All using the hyperscalers. >> We were always going to need to transform the telcos from the conservative environments in which they developed. And they've had control of everything in order to reduce if they get no extra revenue at all, reducing the cost they've got to go on a cloud migration path to do that. >> Amenable. >> Has it been harder than you thought? >> It's been easier than I thought. >> You think it's gone faster than >> It's gone way faster than I thought. I mean pushing on this flywheel I thought for sure it would take five to 10 years it is moving. I mean the maths comp thing the AWS announcements last week they're putting in hyperscalers in Saudi Arabia which is probably one of the most sort of data private places in the world. It's happening really fast. >> What Azure's doing? >> I feel like I can't even go to sleep. Because I got to keep up with it. It's crazy. >> Guys. >> This is awesome. >> So awesome having you back on. >> Yeah. >> Chris, thanks for co-hosting. Appreciate you stay here. >> Yep. >> Danielle, amazing. We'll see you. >> See you soon. >> A lot of action here. We're going to come out >> Great. >> Check out your venue. >> Yeah the Togi buses that are outside. >> The big buses. You got a great setup there. We're going to see you on Wednesday. Thanks again. >> Awesome. Thanks. >> All right. Keep it right there. We'll be back to wrap up day two from MWC 23 on theCUBE. (upbeat music)

(gentle music) >> Okay, welcome back to Supercloud 2, live here in Palo Alto, California for our live stage performance. Supercloud 2 is our second Supercloud event. We're going to get these out as fast as we can every couple months. It's our second one, you'll see two and three this year. I'm John Furrier, my co-host, Dave Vellante. A panel here to break down the Supercloud momentum, the wave, and the developer impact that we bringing back Vittorio Viarengo, who's a VP for Cross-Cloud Services at VMware. Sarbjeet Johal, industry influencer and Analyst at StackPayne, his company, Cube alumni and Influencer. Sarbjeet, great to see you. Vittorio, thanks for coming back. >> Nice to be here. >> My pleasure. >> Vittorio, you just gave a keynote where we unpacked the cross-cloud services, what VMware is doing, how you guys see it, not just from VMware's perspective, but VMware looking out broadly at the industry and developers came up and you were like, "Developers, developer, developers", kind of a goof on the Steve Ballmer famous meme that everyone's seen. This is a huge star, sorry, I mean a big piece of it. The developers are the canary in the coal mines. They're the ones who are being asked to code the digital transformation, which is fully business transformation and with the market the way it is right now in terms of the accelerated technology, every enterprise grade business model's changing. The technology is evolving, the builders are kind of, they want go faster. I'm saying they're stuck in a way, but that's my opinion, but there's a lot of growth. >> Yeah. >> The impact, they got to get released up and let it go. Those developers need to accelerate faster. It's been a big part of productivity, and the conversations we've had. So developer impact is huge in Supercloud. What's your, what do you guys think about this? We'll start with you, Sarbjeet. >> Yeah, actually, developers are the masons of the digital empires I call 'em, right? They lay every brick and build all these big empires. On the left side of the SDLC, or the, you know, when you look at the system operations, developer is number one cost from economic side of things, and from technology side of things, they are tech hungry people. They are developers for that reason because developer nights are long, hours are long, they forget about when to eat, you know, like, I've been a developer, I still code. So you want to keep them happy, you want to hug your developers. We always say that, right? Vittorio said that right earlier. The key is to, in this context, in the Supercloud context, is that developers don't mind mucking around with platforms or APIs or new languages, but they hate the infrastructure part. That's a fact. They don't want to muck around with servers. It's friction for them, it is like they don't want to muck around even with the VMs. So they want the programmability to the nth degree. They want to automate everything, so that's how they think and cloud is the programmable infrastructure, industrialization of infrastructure in many ways. So they are happy with where we are going, and we need more abstraction layers for some developers. By the way, I have this sort of thinking frame for last year or so, not all developers are same, right? So if you are a developer at an ISV, you behave differently. If you are a developer at a typical enterprise, you behave differently or you are forced to behave differently because you're not writing software.- >> Well, developers, developers have changed, I mean, Vittorio, you and I were talking earlier on the keynote, and this is kind of the key point is what is a developer these days? If everything is software enabled, I mean, even hardware interviews we do with Nvidia, and Amazon and other people building silicon, they all say the same thing, "It's software on a chip." So you're seeing the role of software up and down the stack and the role of the stack is changing. The old days of full stack developer, what does that even mean? I mean, the cloud is a half a stack kind of right there. So, you know, developers are certainly more agile, but cloud native, I mean VMware is epitome of operations, IT operations, and the Tan Zoo initiative, you guys started, you went after the developers to look at them, and ask them questions, "What do you need?", "How do you transform the Ops from virtualization?" Again, back to your point, so this hardware abstraction, what is software, what is cloud native? It's kind of messy equation these days. How do you guys grokel with that? >> I would argue that developers don't want the Supercloud. I dropped that up there, so, >> Dave: Why not? >> Because developers, they, once they get comfortable in AWS or Google, because they're doing some AI stuff, which is, you know, very trendy right now, or they are in IBM, any of the IPA scaler, professional developers, system developers, they love that stuff, right? Yeah, they don't, the infrastructure gets in the way, but they're just, the problem is, and I think the Supercloud should be driven by the operators because as we discussed, the operators have been left behind because they're busy with day-to-day jobs, and in most cases IT is centralized, developers are in the business units. >> John: Yeah. >> Right? So they get the mandate from the top, say, "Our bank, they're competing against". They gave teenagers or like young people the ability to do all these new things online, and Venmo and all this integration, where are we? "Oh yeah, we can do it", and then build it, and then deploy it, "Okay, we caught up." but now the operators are back in the private cloud trying to keep the backend system running and so I think the Supercloud is needed for the primarily, initially, for the operators to get in front of the developers, fit in the workflow, but lay the foundation so it is secure.- >> So, so I love this thinking because I love the rift, because the rift points to what is the target audience for the value proposition and if you're a developer, Supercloud enables you so you shouldn't have to deal with Supercloud. >> Exactly. >> What you're saying is get the operating environment or operating system done properly, whether it's architecture, building the platform, this comes back to architecture platform conversations. What is the future platform? Is it a vendor supplied or is it customer created platform? >> Dave: So developers want best to breed, is what you just said. >> Vittorio: Yeah. >> Right and operators, they, 'cause developers don't want to deal with governance, they don't want to deal with security, >> No. >> They don't want to deal with spinning up infrastructure. That's the role of the operator, but that's where Supercloud enables, to John's point, the developer, so to your question, is it a platform where the platform vendor is responsible for the architecture, or there is it an architectural standard that spans multiple clouds that has to emerge? Based on what you just presented earlier, Vittorio, you are the determinant of the architecture. It's got to be open, but you guys determine that, whereas the nirvana is, "Oh no, it's all open, and it just kind of works." >> Yeah, so first of all, let's all level set on one thing. You cannot tell developers what to do. >> Dave: Right, great >> At least great developers, right? Cannot tell them what to do. >> Dave: So that's what, that's the way I want to sort of, >> You can tell 'em what's possible. >> There's a bottle on that >> If you tell 'em what's possible, they'll test it, they'll look at it, but if you try to jam it down their throat, >> Yeah. >> Dave: You can't tell 'em how to do it, just like your point >> Let me answer your answer the question. >> Yeah, yeah. >> So I think we need to build an architect, help them build an architecture, but it cannot be proprietary, has to be built on what works in the cloud and so what works in the cloud today is Kubernetes, is you know, number of different open source project that you need to enable and then provide, use this, but when I first got exposed to Kubernetes, I said, "Hallelujah!" We had a runtime that works the same everywhere only to realize there are 12 different distributions. So that's where we come in, right? And other vendors come in to say, "Hey, no, we can make them all look the same. So you still use Kubernetes, but we give you a place to build, to set those operation policy once so that you don't create friction for the developers because that's the last thing you want to do." >> Yeah, actually, coming back to the same point, not all developers are same, right? So if you're ISV developer, you want to go to the lowest sort of level of the infrastructure and you want to shave off the milliseconds from to get that performance, right? If you're working at AWS, you are doing that. If you're working at scale at Facebook, you're doing that. At Twitter, you're doing that, but when you go to DMV and Kansas City, you're not doing that, right? So your developers are different in nature. They are given certain parameters to work with, certain sort of constraints on the budget side. They are educated at a different level as well. Like they don't go to that end of the degree of sort of automation, if you will. So you cannot have the broad stroking of developers. We are talking about a citizen developer these days. That's a extreme low, >> You mean Low-Code. >> Yeah, Low-Code, No-code, yeah, on the extreme side. On one side, that's citizen developers. On the left side is the professional developers, when you say developers, your mind goes to the professional developers, like the hardcore developers, they love the flexibility, you know, >> John: Well app, developers too, I mean. >> App developers, yeah. >> You're right a lot of, >> Sarbjeet: Infrastructure platform developers, app developers, yes. >> But there are a lot of customers, its a spectrum, you're saying. >> Yes, it's a spectrum >> There's a lot of customers don't want deal with that muck. >> Yeah. >> You know, like you said, AWS, Twitter, the sophisticated developers do, but there's a whole suite of developers out there >> Yeah >> That just want tools that are abstracted. >> Within a company, within a company. Like how I see the Supercloud is there shouldn't be anything which blocks the developers, like their view of the world, of the future. Like if you're blocked as a developer, like something comes in front of you, you are not developer anymore, believe me, (John laughing) so you'll go somewhere else >> John: First of all, I'm, >> You'll leave the company by the way. >> Dave: Yeah, you got to quit >> Yeah, you will quit, you will go where the action is, where there's no sort of blockage there. So like if you put in front of them like a huge amount of a distraction, they don't like it, so they don't, >> Well, the idea of a developer, >> Coming back to that >> Let's get into 'cause you mentioned platform. Get year in the term platform engineering now. >> Yeah. >> Platform developer. You know, I remember back in, and I think there's still a term used today, but when I graduated my computer science degree, we were called "Software engineers," right? Do people use that term "Software engineering", or is it "Software development", or they the same, are they different? >> Well, >> I think there's a, >> So, who's engineering what? Are they engineering or are they developing? Or both? Well, I think it the, you made a great point. There is a factor of, I had the, I was blessed to work with Adam Bosworth, that is the guy that created some of the abstraction layer, like Visual Basic and Microsoft Access and he had so, he made his whole career thinking about this layer, and he always talk about the professional developers, the developers that, you know, give him a user manual, maybe just go at the APIs, he'll build anything, right, from system engine, go down there, and then through obstruction, you get the more the procedural logic type of engineers, the people that used to be able to write procedural logic and visual basic and so on and so forth. I think those developers right now are a little cut out of the picture. There's some No-code, Low-Code environment that are maybe gain some traction, I caught up with Adam Bosworth two weeks ago in New York and I asked him "What's happening to this higher level developers?" and you know what he is told me, and he is always a little bit out there, so I'm going to use his thought process here. He says, "ChapGPT", I mean, they will get to a point where this high level procedural logic will be written by, >> John: Computers. >> Computers, and so we may not need as many at the high level, but we still need the engineers down there. The point is the operation needs to get in front of them >> But, wait, wait, you seen the ChatGPT meme, I dunno if it's a Dilbert thing where it's like, "Time to tic" >> Yeah, yeah, yeah, I did that >> "Time to develop the code >> Five minutes, time to decode", you know, to debug the codes like five hours. So you know, the whole equation >> Well, this ChatGPT is a hot wave, everyone's been talking about it because I think it illustrates something that's NextGen, feels NextGen, and it's just getting started so it's going to get better. I mean people are throwing stones at it, but I think it's amazing. It's the equivalent of me seeing the browser for the first time, you know, like, "Wow, this is really compelling." This is game-changing, it's not just keyword chat bots. It's like this is real, this is next level, and I think the Supercloud wave that people are getting behind points to that and I think the question of Ops and Dev comes up because I think if you limit the infrastructure opportunity for a developer, I think they're going to be handicapped. I mean that's a general, my opinion, the thesis is you give more aperture to developers, more choice, more capabilities, more good things could happen, policy, and that's why you're seeing the convergence of networking people, virtualization talent, operational talent, get into the conversation because I think it's an infrastructure engineering opportunity. I think this is a seminal moment in a new stack that's emerging from an infrastructure, software virtualization, low-code, no-code layer that will be completely programmable by things like the next Chat GPT or something different, but yet still the mechanics and the plumbing will still need engineering. >> Sarbjeet: Oh yeah. >> So there's still going to be more stuff coming on. >> Yeah, we have, with the cloud, we have made the infrastructure programmable and you give the programmability to the programmer, they will be very creative with that and so we are being very creative with our infrastructure now and on top of that, we are being very creative with the silicone now, right? So we talk about that. That's part of it, by the way. So you write the code to the particle's silicone now, and on the flip side, the silicone is built for certain use cases for AI Inference and all that. >> You saw this at CES? >> Yeah, I saw at CES, the scenario is this, the Bosch, I spoke to Bosch, I spoke to John Deere, I spoke to AWS guys, >> Yeah. >> They were showcasing their technology there and I was spoke to Azure guys as well. So the Bosch is a good example. So they are building, they are right now using AWS. I have that interview on camera, I will put it some sometime later on there online. So they're using AWS on the back end now, but Bosch is the number one, number one or number two depending on what day it is of the year, supplier of the componentry to the auto industry, and they are creating a platform for our auto industry, so is Qualcomm actually by the way, with the Snapdragon. So they told me that customers, their customers, BMW, Audi, all the manufacturers, they demand the diversity of the backend. Like they don't want all, they, all of them don't want to go to AWS. So they want the choice on the backend. So whatever they cook in the middle has to work, they have to sprinkle the data for the data sovereign side because they have Chinese car makers as well, and for, you know, for other reasons, competitive reasons and like use. >> People don't go to, aw, people don't go to AWS either for political reasons or like competitive reasons or specific use cases, but for the most part, generally, I haven't met anyone who hasn't gone first choice with either, but that's me personally. >> No, but they're building. >> Point is the developer wants choice at the back end is what I'm hearing, but then finish that thought. >> Their developers want the choice, they want the choice on the back end, number one, because the customers are asking for, in this case, the customers are asking for it, right? But the customers requirements actually drive, their economics drives that decision making, right? So in the middle they have to, they're forced to cook up some solution which is vendor neutral on the backend or multicloud in nature. So >> Yeah, >> Every >> I mean I think that's nirvana. I don't think, I personally don't see that happening right now. I mean, I don't see the parody with clouds. So I think that's a challenge. I mean, >> Yeah, true. >> I mean the fact of the matter is if the development teams get fragmented, we had this chat with Kit Colbert last time, I think he's going to come on and I think he's going to talk about his keynote in a few, in an hour or so, development teams is this, the cloud is heterogenous, which is great. It's complex, which is challenging. You need skilled engineering to manage these clouds. So if you're a CIO and you go all in on AWS, it's hard. Then to then go out and say, "I want to be completely multi-vendor neutral" that's a tall order on many levels and this is the multicloud challenge, right? So, the question is, what's the strategy for me, the CIO or CISO, what do I do? I mean, to me, I would go all in on one and start getting hedges and start playing and then look at some >> Crystal clear. Crystal clear to me. >> Go ahead. >> If you're a CIO today, you have to build a platform engineering team, no question. 'Cause if we agree that we cannot tell the great developers what to do, we have to create a platform engineering team that using pieces of the Supercloud can build, and let's make this very pragmatic and give examples. First you need to be able to lay down the run time, okay? So you need a way to deploy multiple different Kubernetes environment in depending on the cloud. Okay, now we got that. The second part >> That's like table stakes. >> That are table stake, right? But now what is the advantage of having a Supercloud service to do that is that now you can put a policy in one place and it gets distributed everywhere consistently. So for example, you want to say, "If anybody in this organization across all these different buildings, all these developers don't even know, build a PCI compliant microservice, They can only talk to PCI compliant microservice." Now, I sleep tight. The developers still do that. Of course they're going to get their hands slapped if they don't encrypt some messages and say, "Oh, that should have been encrypted." So number one. The second thing I want to be able to say, "This service that this developer built over there better satisfy this SLA." So if the SLA is not satisfied, boom, I automatically spin up multiple instances to certify the SLA. Developers unencumbered, they don't even know. So this for me is like, CIO build a platform engineering team using one of the many Supercloud services that allow you to do that and lay down. >> And part of that is that the vendor behavior is such, 'cause the incentive is that they don't necessarily always work together. (John chuckling) I'll give you an example, we're going to hear today from Western Union. They're AWS shop, but they want to go to Google, they want to use some of Google's AI tools 'cause they're good and maybe they're even arguably better, but they're also a Snowflake customer and what you'll hear from them is Amazon and Snowflake are working together so that SageMaker can be integrated with Snowflake but Google said, "No, you want to use our AI tools, you got to use BigQuery." >> Yeah. >> Okay. So they say, "Ah, forget it." So if you have a platform engineering team, you can maybe solve some of that vendor friction and get competitive advantage. >> I think that the future proximity concept that I talk about is like, when you're doing one thing, you want to do another thing. Where do you go to get that thing, right? So that is very important. Like your question, John, is that your point is that AWS is ahead of the pack, which is true, right? They have the >> breadth of >> Infrastructure by a lot >> infrastructure service, right? They breadth of services, right? So, how do you, When do you bring in other cloud providers, right? So I believe that you should standardize on one cloud provider, like that's your primary, and for others, bring them in on as needed basis, in the subsection or sub portfolio of your applications or your platforms, what ever you can. >> So yeah, the Google AI example >> Yeah, I mean, >> Or the Microsoft collaboration software example. I mean there's always or the M and A. >> Yeah, but- >> You're going to get to run Windows, you can run Windows on Amazon, so. >> By the way, Supercloud doesn't mean that you cannot do that. So the perfect example is say that you're using Azure because you have a SQL server intensive workload. >> Yep >> And you're using Google for ML, great. If you are using some differentiated feature of this cloud, you'll have to go somewhere and configure this widget, but what you can abstract with the Supercloud is the lifecycle manage of the service that runs on top, right? So how does the service get deployed, right? How do you monitor performance? How do you lifecycle it? How you secure it that you can abstract and that's the value and eventually value will win. So the customers will find what is the values, obstructing in making it uniform or going deeper? >> How about identity? Like take identity for instance, you know, that's an opportunity to abstract. Whether I use Microsoft Identity or Okta, and I can abstract that. >> Yeah, and then we have APIs and standards that we can use so eventually I think where there is enough pain, the right open source will emerge to solve that problem. >> Dave: Yeah, I can use abstract things like object store, right? That's pretty simple. >> But back to the engineering question though, is that developers, developers, developers, one thing about developers psychology is if something's not right, they say, "Go get fixing. I'm not touching it until you fix it." They're very sticky about, if something's not working, they're not going to do it again, right? So you got to get it right for developers. I mean, they'll maybe tolerate something new, but is the "juice worth the squeeze" as they say, right? So you can't go to direct say, "Hey, it's, what's a work in progress? We're going to get our infrastructure together and the world's going to be great for you, but just hang tight." They're going to be like, "Get your shit together then talk to me." So I think that to me is the question. It's an Ops question, but where's that value for the developer in Supercloud where the capabilities are there, there's less friction, it's simpler, it solves the complexity problem. I don't need these high skilled labor to manage Amazon. I got services exposed. >> That's what we talked about earlier. It's like the Walmart example. They basically, they took away from the developer the need to spin up infrastructure and worry about all the governance. I mean, it's not completely there yet. So the developer could focus on what he or she wanted to do. >> But there's a big, like in our industry, there's a big sort of flaw or the contention between developers and operators. Developers want to be on the cutting edge, right? And operators want to be on the stability, you know, like we want governance. >> Yeah, totally. >> Right, so they want to control, developers are like these little bratty kids, right? And they want Legos, like they want toys, right? Some of them want toys by way. They want Legos, they want to build there and they want make a mess out of it. So you got to make sure. My number one advice in this context is that do it up your application portfolio and, or your platform portfolio if you are an ISV, right? So if you are ISV you most probably, you're building a platform these days, do it up in a way that you can say this portion of our applications and our platform will adhere to what you are saying, standardization, you know, like Kubernetes, like slam dunk, you know, it works across clouds and in your data center hybrid, you know, whole nine yards, but there is some subset on the next door systems of innovation. Everybody has, it doesn't matter if you're DMV of Kansas or you are, you know, metaverse, right? Or Meta company, right, which is Facebook, they have it, they are building something new. For that, give them some freedom to choose different things like play with non-standard things. So that is the mantra for moving forward, for any enterprise. >> Do you think developers are happy with the infrastructure now or are they wanting people to get their act together? I mean, what's your reaction, or you think. >> Developers are happy as long as they can do their stuff, which is running code. They want to write code and innovate. So to me, when Ballmer said, "Developer, develop, Developer, what he meant was, all you other people get your act together so these developers can do their thing, and to me the Supercloud is the way for IT to get there and let developer be creative and go fast. Why not, without getting in trouble. >> Okay, let's wrap up this segment with a super clip. Okay, we're going to do a sound bite that we're going to make into a short video for each of you >> All right >> On you guys summarizing why Supercloud's important, why this next wave is relevant for the practitioners, for the industry and we'll turn this into an Instagram reel, YouTube short. So we'll call it a "Super clip. >> Alright, >> Sarbjeet, you want, you want some time to think about it? You want to go first? Vittorio, you want. >> I just didn't mind. (all laughing) >> No, okay, okay. >> I'll do it again. >> Go back. No, we got a fresh one. We'll going to already got that one in the can. >> I'll go. >> Sarbjeet, you go first. >> I'll go >> What's your super clip? >> In software systems, abstraction is your friend. I always say that. Abstraction is your friend, even if you're super professional developer, abstraction is your friend. We saw from the MFC library from C++ days till today. Abstract, use abstraction. Do not try to reinvent what's already being invented. Leverage cloud, leverage the platform side of the cloud. Not just infrastructure service, but platform as a service side of the cloud as well, and Supercloud is a meta platform built on top of these infrastructure services from three or four or five cloud providers. So use that and embrace the programmability, embrace the abstraction layer. That's the key actually, and developers who are true developers or professional developers as you said, they know that. >> Awesome. Great super clip. Vittorio, another shot at the plate here for super clip. Go. >> Multicloud is awesome. There's a reason why multicloud happened, is because gave our developers the ability to innovate fast and ever before. So if you are embarking on a digital transformation journey, which I call a survival journey, if you're not innovating and transforming, you're not going to be around in business three, five years from now. You have to adopt the Supercloud so the developer can be developer and keep building great, innovating digital experiences for your customers and IT can get in front of it and not get in trouble together. >> Building those super apps with Supercloud. That was a great super clip. Vittorio, thank you for sharing. >> Thanks guys. >> Sarbjeet, thanks for coming on talking about the developer impact Supercloud 2. On our next segment, coming up right now, we're going to hear from Walmart enterprise architect, how they are building and they are continuing to innovate, to build their own Supercloud. Really informative, instructive from a practitioner doing it in real time. Be right back with Walmart here in Palo Alto. Thanks for watching. (gentle music)

(upbeat music) >> Welcome back to Supercloud 2, which is an open industry collaboration between technologists, consultants, analysts, and of course, practitioners, to help shape the future of cloud. And at this event, one of the key areas we're exploring is the intersection of cloud and data, and how building value on top of hyperscale clouds and across clouds is evolving, a concept we call supercloud. And we're pleased to welcome Harvir Singh, who's the chief data architect and global head of data at Western Union. Harvir, it's good to see you again. Thanks for coming on the program. >> Thanks, David, it's always a pleasure to talk to you. >> So many things stand out from when we first met, and one of the most gripping for me was when you said to me, "When data moves, money moves." And that's the world we live in today, and really have for a long time. Money has moved as bits, and when it has to move, we want it to move quickly, securely, and in a governed manner. And the pressure to do so is only growing. So tell us how that trend is evolved over the past decade in the context of your industry generally, and Western Union, specifically. Look, I always say to people that we are probably the first ones to introduce digital currency around the world because, hey, somebody around the world needs money, we move data to make that happen. That trend has actually accelerated quite a bit. If you look at the last 10 years, and you look at all these payment companies, digital companies, credit card companies that have evolved, majority of them are working on the same principle. When data moves, money moves. When data is stale, the money goes away, right? I think that trend is continuing, and it's not just the trend is in this space, it's also continuing in other spaces, specifically around, you know, acquisition of customers, communication with customers. It's all becoming digital, and it's, at the end of the day, it's all data being moved from one place or another. At the end of the day, you're not seeing the customer, but you're looking at, you know, the data that he's consuming, and you're making actionable items on it, and be able to respond to what they need. So I think 10 years, it's really, really evolved. >> Hmm, you operate, Western Union operates in more than 200 countries, and you you have what I would call a pseudo federated organization. You're trying to standardize wherever possible on the infrastructure, and you're curating the tooling and doing the heavy lifting in the data stack, which of course lessens the burden on the developers and the line of business consumers, so my question is, in operating in 200 countries, how do you deal with all the diversity of laws and regulations across those regions? I know you're heavily involved in AWS, but AWS isn't everywhere, you still have some on-prem infrastructure. Can you paint a picture of, you know, what that looks like? >> Yeah, a few years ago , we were primarily mostly on-prem, and one of the biggest pain points has been managing that infrastructure around the world in those countries. Yes, we operate in 200 countries, but we don't have infrastructure in 200 countries, but we do have agent locations in 200 countries. United Nations says we only have like 183 are countries, but there are countries which, you know, declare themselves countries, and we are there as well because somebody wants to send money there, right? Somebody has an agent location down there as well. So that infrastructure is obviously very hard to manage and maintain. We have to comply by numerous laws, you know. And the last few years, specifically with GDPR, CCPA, data localization laws in different countries, it's been a challenge, right? And one of the things that we did a few years ago, we decided that we want to be in the business of helping our customers move money faster, security, and with complete trust in us. We don't want to be able to, we don't want to be in the business of managing infrastructure. And that's one of the reasons we started to, you know, migrate and move our journey to the cloud. AWS, obviously chosen first because of its, you know, first in the game, has more locations, and more data centers around the world where we operate. But we still have, you know, existing infrastructure, which is in some countries, which is still localized because AWS hasn't reached there, or we don't have a comparable provider there. We still manage those. And we have to comply by those laws. Our data privacy and our data localization tech stack is pretty good, I would say. We manage our data very well, we manage our customer data very well, but it comes with a lot of complexity. You know, we get a lot of requests from European Union, we get a lot of requests from Asia Pacific every pretty much on a weekly basis to explain, you know, how we are taking controls and putting measures in place to make sure that the data is secured and is in the right place. So it's a complex environment. We do have exposure to other clouds as well, like Google and Azure. And as much as we would love to be completely, you know, very, very hybrid kind of an organization, it's still at a stage where we are still very heavily focused on AWS yet, but at some point, you know, we would love to see a world which is not reliant on a single provider, but it's more a little bit more democratized, you know, as and when what I want to use, I should be able to use, and pay-per-use. And the concept started like that, but it's obviously it's now, again, there are like three big players in the market, and, you know, they're doing their own thing. Would love to see them come collaborate at some point. >> Yeah, wouldn't we all. I want to double-click on the whole multi-cloud strategy, but if I understand it correctly, and in a perfect world, everything on-premises would be in the cloud is, first of all, is that a correct statement? Is that nirvana for you or not necessarily? >> I would say it is nirvana for us, but I would also put a caveat, is it's very tricky because from a regulatory perspective, we are a regulated entity in many countries. The regulators would want to see some control if something happens with a relationship with AWS in one country, or with Google in another country, and it keeps happening, right? For example, Russia was a good example where we had to switch things off. We should be able to do that. But if let's say somewhere in Asia, this country decides that they don't want to partner with AWS, and majority of our stuff is on AWS, where do I go from there? So we have to have some level of confidence in our own infrastructure, so we do maintain some to be able to fail back into and move things it needs to be. So it's a tricky question. Yes, it's nirvana state that I don't have to manage infrastructure, but I think it's far less practical than it said. We will still own something that we call it our own where we have complete control, being a financial entity. >> And so do you try to, I'm sure you do, standardize between all the different on-premise, and in this case, the AWS cloud or maybe even other clouds. How do you do that? Do you work with, you know, different vendors at the various places of the stack to try to do that? Some of the vendors, you know, like a Snowflake is only in the cloud. You know, others, you know, whether it's whatever, analytics, or storage, or database, might be hybrid. What's your strategy with regard to creating as common an experience as possible between your on-prem and your clouds? >> You asked a question which I asked when I joined as well, right? Which question, this is one of the most important questions is how soon when I fail back, if I need to fail back? And how quickly can I, because not everything that is sitting on the cloud is comparable to on-prem or is backward compatible. And the reason I say backward compatible is, you know, there are, our on-prem cloud is obviously behind. We haven't taken enough time to kind of put it to a state where, because we started to migrate and now we have access to infrastructure on the cloud, most of the new things are being built there. But for critical application, I would say we have chronology that could be used to move back if need to be. So, you know, technologies like Couchbase, technologies like PostgreSQL, technologies like Db2, et cetera. We still have and maintain a fairly large portion of it on-prem where critical applications could potentially be serviced. We'll give you one example. We use Neo4j very heavily for our AML use cases. And that's an important one because if Neo4j on the cloud goes down, and it's happened in the past, again, even with three clusters, having all three clusters going down with a DR, we still need some accessibility of that because that's one of the biggest, you know, fraud and risk application it supports. So we do still maintain some comparable technology. Snowflake is an odd one. It's obviously there is none on-prem. But then, you know, Snowflake, I also feel it's more analytical based technology, not a transactional-based technology, at least in our ecosystem. So for me to replicate that, yes, it'll probably take time, but I can live with that. But my business will not stop because our transactional applications can potentially move over if need to. >> Yeah, and of course, you know, all these big market cap companies, so the Snowflake or Databricks, which is not public yet, but they've got big aspirations. And so, you know, we've seen things like Snowflake do a deal with Dell for on-prem object store. I think they do the same thing with Pure. And so over time, you see, Mongo, you know, extending its estate. And so over time all these things are coming together. I want to step out of this conversation for a second. I just ask you, given the current macroeconomic climate, what are the priorities? You know, obviously, people are, CIOs are tapping the breaks on spending, we've reported on that, but what is it? Is it security? Is it analytics? Is it modernization of the on-prem stack, which you were saying a little bit behind. Where are the priorities today given the economic headwinds? >> So the most important priority right now is growing the business, I would say. It's a different, I know this is more, this is not a very techy or a tech answer that, you know, you would expect, but it's growing the business. We want to acquire more customers and be able to service them as best needed. So the majority of our investment is going in the space where tech can support that initiative. During our earnings call, we released the new pillars of our organization where we will focus on, you know, omnichannel digital experience, and then one experience for customer, whether it's retail, whether it's digital. We want to open up our own experience stores, et cetera. So we are investing in technology where it's going to support those pillars. But the spend is in a way that we are obviously taking away from the things that do not support those. So it's, I would say it's flat for us. We are not like in heavily investing or aggressively increasing our tech budget, but it's more like, hey, switch this off because it doesn't make us money, but now switch this on because this is going to support what we can do with money, right? So that's kind of where we are heading towards. So it's not not driven by technology, but it's driven by business and how it supports our customers and our ability to compete in the market. >> You know, I think Harvir, that's consistent with what we heard in some other work that we've done, our ETR partner who does these types of surveys. We're hearing the same thing, is that, you know, we might not be spending on modernizing our on-prem stack. Yeah, we want to get to the cloud at some point and modernize that. But if it supports revenue, you know, we'll invest in that, and get the, you know, instant ROI. I want to ask you about, you know, this concept of supercloud, this abstracted layer of value on top of hyperscale infrastructure, and maybe on-prem. But we were talking about the integration, for instance, between Snowflake and Salesforce, where you got different data sources and you were explaining that you had great interest in being able to, you know, have a kind of, I'll say seamless, sorry, I know it's an overused word, but integration between the data sources and those two different platforms. Can you explain that and why that's attractive to you? >> Yeah, I'm a big supporter of action where the data is, right? Because the minute you start to move, things are already lost in translation. The time is lost, you can't get to it fast enough. So if, for example, for us, Snowflake, Salesforce, is our actionable platform where we action, we send marketing campaigns, we send customer communication via SMS, in app, as well as via email. Now, we would like to be able to interact with our customers pretty much on a, I would say near real time, but the concept of real time doesn't work well with me because I always feel that if you're observing something, it's not real time, it's already happened. But how soon can I react? That's the question. And given that I have to move that data all the way from our, let's say, engagement platforms like Adobe, and particles of the world into Snowflake first, and then do my modeling in some way, and be able to then put it back into Salesforce, it takes time. Yes, you know, I can do it in a few hours, but that few hours makes a lot of difference. Somebody sitting on my website, you know, couldn't find something, walked away, how soon do you think he will lose interest? Three hours, four hours, he'll probably gone, he will never come back. I think if I can react to that as fast as possible without too much data movement, I think that's a lot of good benefit that this kind of integration will bring. Yes, I can potentially take data directly into Salesforce, but I then now have two copies of data, which is, again, something that I'm not a big (indistinct) of. Let's keep the source of the data simple, clean, and a single source. I think this kind of integration will help a lot if the actions can be brought very close to where the data resides. >> Thank you for that. And so, you know, it's funny, we sometimes try to define real time as before you lose the customer, so that's kind of real time. But I want to come back to this idea of governed data sharing. You mentioned some other clouds, a little bit of Azure, a little bit of Google. In a world where, let's say you go more aggressively, and we know that for instance, if you want to use Google's AI tools, you got to use BigQuery. You know, today, anyway, they're not sort of so friendly with Snowflake, maybe different for the AWS, maybe Microsoft's going to be different as well. But in an ideal world, what I'm hearing is you want to keep the data in place. You don't want to move the data. Moving data is expensive, making copies is badness. It's expensive, and it's also, you know, changes the state, right? So you got governance issues. So this idea of supercloud is that you can leave the data in place and actually have a common experience across clouds. Let's just say, let's assume for a minute Google kind of wakes up, my words, not yours, and says, "Hey, maybe, you know what, partnering with a Snowflake or a Databricks is better for our business. It's better for the customers," how would that affect your business and the value that you can bring to your customers? >> Again, I would say that would be the nirvana state that, you know, we want to get to. Because I would say not everyone's perfect. They have great engineers and great products that they're developing, but that's where they compete as well, right? I would like to use the best of breed as much as possible. And I've been a person who has done this in the past as well. I've used, you know, tools to integrate. And the reason why this integration has worked is primarily because sometimes you do pick the best thing for that job. And Google's AI products are definitely doing really well, but, you know, that accessibility, if it's a problem, then I really can't depend on them, right? I would love to move some of that down there, but they have to make it possible for us. Azure is doing really, really good at investing, so I think they're a little bit more and more closer to getting to that state, and I know seeking our attention than Google at this point of time. But I think there will be a revelation moment because more and more people that I talk to like myself, they're also talking about the same thing. I'd like to be able to use Google's AdSense, I would like to be able to use Google's advertising platform, but you know what? I already have all this data, why do I need to move it? Can't they just go and access it? That question will keep haunting them (indistinct). >> You know, I think, obviously, Microsoft has always known, you know, understood ecosystems. I mean, AWS is nailing it, when you go to re:Invent, it's all about the ecosystem. And they think they realized they can make a lot more money, you know, together, than trying to have, and Google's got to figure that out. I think Google thinks, "All right, hey, we got to have the best tech." And that tech, they do have the great tech, and that's our competitive advantage. They got to wake up to the ecosystem and what's happening in the field and the go-to-market. I want to ask you about how you see data and cloud evolving in the future. You mentioned that things that are driving revenue are the priorities, and maybe you're already doing this today, but my question is, do you see a day when companies like yours are increasingly offering data and software services? You've been around for a long time as a company, you've got, you know, first party data, you've got proprietary knowledge, and maybe tooling that you've developed, and you're becoming more, you're already a technology company. Do you see someday pointing that at customers, or again, maybe you're doing it already, or is that not practical in your view? >> So data monetization has always been on the charts. The reason why it hasn't seen the light is regulatory pressure at this point of time. We are partnering up with certain agencies, again, you know, some pilots are happening to see the value of that and be able to offer that. But I think, you know, eventually, we'll get to a state where our, because we are trying to build accessible financial services, we will be in a state that we will be offering those to partners, which could then extended to their customers as well. So we are definitely exploring that. We are definitely exploring how to enrich our data with other data, and be able to complete a super set of data that can be used. Because frankly speaking, the data that we have is very interesting. We have trends of people migrating, we have trends of people migrating within the US, right? So if a new, let's say there's a new, like, I'll give you an example. Let's say New York City, I can tell you, at any given point of time, with my data, what is, you know, a dominant population in that area from migrant perspective. And if I see a change in that data, I can tell you where that is moving towards. I think it's going to be very interesting. We're a little bit, obviously, sometimes, you know, you're scared of sharing too much detail because there's too much data. So, but at the end of the day, I think at some point, we'll get to a state where we are confident that the data can be used for good. One simple example is, you know, pharmacies. They would love to get, you know, we've been talking to CVS and we are talking to Walgreens, and trying to figure out, if they would get access to this kind of data demographic information, what could they do be better? Because, you know, from a gene pool perspective, there are diseases and stuff that are very prevalent in one community versus the other. We could probably equip them with this information to be able to better, you know, let's say, staff their pharmacies or keep better inventory of products that could be used for the population in that area. Similarly, the likes of Walmarts and Krogers, they would like to have more, let's say, ethnic products in their aisles, right? How do you enable that? That data is primarily, I think we are the biggest source of that data. So we do take pride in it, but you know, with caution, we are obviously exploring that as well. >> My last question for you, Harvir, is I'm going to ask you to do a thought exercise. So in that vein, that whole monetization piece, imagine that now, Harvir, you are running a P&L that is going to monetize that data. And my question to you is a there's a business vector and a technology vector. So from a business standpoint, the more distribution channels you have, the better. So running on AWS cloud, partnering with Microsoft, partnering with Google, going to market with them, going to give you more revenue. Okay, so there's a motivation for multi-cloud or supercloud. That's indisputable. But from a technical standpoint, is there an advantage to running on multiple clouds or is that a disadvantage for you? >> It's, I would say it's a disadvantage because if my data is distributed, I have to combine it at some place. So the very first step that we had taken was obviously we brought in Snowflake. The reason, we wanted our analytical data and we want our historical data in the same place. So we are already there and ready to share. And we are actually participating in the data share, but in a private setting at the moment. So we are technically enabled to share, unless there is a significant, I would say, upside to moving that data to another cloud. I don't see any reason because I can enable anyone to come and get it from Snowflake. It's already enabled for us. >> Yeah, or if somehow, magically, several years down the road, some standard developed so you don't have to move the data. Maybe there's a new, Mogli is talking about a new data architecture, and, you know, that's probably years away, but, Harvir, you're an awesome guest. I love having you on, and really appreciate you participating in the program. >> I appreciate it. Thank you, and good luck (indistinct) >> Ah, thank you very much. This is Dave Vellante for John Furrier and the entire Cube community. Keep it right there for more great coverage from Supercloud 2. (uplifting music)

>>From the Cube Studios in Palo Alto in Boston, bringing you data-driven insights from the cube and E T R. This is breaking analysis with Dave Valante. >>Making technology predictions in 2022 was tricky business, especially if you were projecting the performance of markets or identifying I P O prospects and making binary forecast on data AI and the macro spending climate and other related topics in enterprise tech 2022, of course was characterized by a seesaw economy where central banks were restructuring their balance sheets. The war on Ukraine fueled inflation supply chains were a mess. And the unintended consequences of of forced march to digital and the acceleration still being sorted out. Hello and welcome to this week's weekly on Cube Insights powered by E T R. In this breaking analysis, we continue our annual tradition of transparently grading last year's enterprise tech predictions. And you may or may not agree with our self grading system, but look, we're gonna give you the data and you can draw your own conclusions and tell you what, tell us what you think. >>All right, let's get right to it. So our first prediction was tech spending increases by 8% in 2022. And as we exited 2021 CIOs, they were optimistic about their digital transformation plans. You know, they rushed to make changes to their business and were eager to sharpen their focus and continue to iterate on their digital business models and plug the holes that they, the, in the learnings that they had. And so we predicted that 8% rise in enterprise tech spending, which looked pretty good until Ukraine and the Fed decided that, you know, had to rush and make up for lost time. We kind of nailed the momentum in the energy sector, but we can't give ourselves too much credit for that layup. And as of October, Gartner had it spending growing at just over 5%. I think it was 5.1%. So we're gonna take a C plus on this one and, and move on. >>Our next prediction was basically kind of a slow ground ball. The second base, if I have to be honest, but we felt it was important to highlight that security would remain front and center as the number one priority for organizations in 2022. As is our tradition, you know, we try to up the degree of difficulty by specifically identifying companies that are gonna benefit from these trends. So we highlighted some possible I P O candidates, which of course didn't pan out. S NQ was on our radar. The company had just had to do another raise and they recently took a valuation hit and it was a down round. They raised 196 million. So good chunk of cash, but, but not the i p O that we had predicted Aqua Securities focus on containers and cloud native. That was a trendy call and we thought maybe an M SS P or multiple managed security service providers like Arctic Wolf would I p o, but no way that was happening in the crummy market. >>Nonetheless, we think these types of companies, they're still faring well as the talent shortage in security remains really acute, particularly in the sort of mid-size and small businesses that often don't have a sock Lacework laid off 20% of its workforce in 2022. And CO C e o Dave Hatfield left the company. So that I p o didn't, didn't happen. It was probably too early for Lacework. Anyway, meanwhile you got Netscope, which we've cited as strong in the E T R data as particularly in the emerging technology survey. And then, you know, I lumia holding its own, you know, we never liked that 7 billion price tag that Okta paid for auth zero, but we loved the TAM expansion strategy to target developers beyond sort of Okta's enterprise strength. But we gotta take some points off of the failure thus far of, of Okta to really nail the integration and the go to market model with azero and build, you know, bring that into the, the, the core Okta. >>So the focus on endpoint security that was a winner in 2022 is CrowdStrike led that charge with others holding their own, not the least of which was Palo Alto Networks as it continued to expand beyond its core network security and firewall business, you know, through acquisition. So overall we're gonna give ourselves an A minus for this relatively easy call, but again, we had some specifics associated with it to make it a little tougher. And of course we're watching ve very closely this this coming year in 2023. The vendor consolidation trend. You know, according to a recent Palo Alto network survey with 1300 SecOps pros on average organizations have more than 30 tools to manage security tools. So this is a logical way to optimize cost consolidating vendors and consolidating redundant vendors. The E T R data shows that's clearly a trend that's on the upswing. >>Now moving on, a big theme of 2020 and 2021 of course was remote work and hybrid work and new ways to work and return to work. So we predicted in 2022 that hybrid work models would become the dominant protocol, which clearly is the case. We predicted that about 33% of the workforce would come back to the office in 2022 in September. The E T R data showed that figure was at 29%, but organizations expected that 32% would be in the office, you know, pretty much full-time by year end. That hasn't quite happened, but we were pretty close with the projection, so we're gonna take an A minus on this one. Now, supply chain disruption was another big theme that we felt would carry through 2022. And sure that sounds like another easy one, but as is our tradition, again we try to put some binary metrics around our predictions to put some meat in the bone, so to speak, and and allow us than you to say, okay, did it come true or not? >>So we had some data that we presented last year and supply chain issues impacting hardware spend. We said at the time, you can see this on the left hand side of this chart, the PC laptop demand would remain above pre covid levels, which would reverse a decade of year on year declines, which I think started in around 2011, 2012. Now, while demand is down this year pretty substantially relative to 2021, I D C has worldwide unit shipments for PCs at just over 300 million for 22. If you go back to 2019 and you're looking at around let's say 260 million units shipped globally, you know, roughly, so, you know, pretty good call there. Definitely much higher than pre covid levels. But so what you might be asking why the B, well, we projected that 30% of customers would replace security appliances with cloud-based services and that more than a third would replace their internal data center server and storage hardware with cloud services like 30 and 40% respectively. >>And we don't have explicit survey data on exactly these metrics, but anecdotally we see this happening in earnest. And we do have some data that we're showing here on cloud adoption from ET R'S October survey where the midpoint of workloads running in the cloud is around 34% and forecast, as you can see, to grow steadily over the next three years. So this, well look, this is not, we understand it's not a one-to-one correlation with our prediction, but it's a pretty good bet that we were right, but we gotta take some points off, we think for the lack of unequivocal proof. Cause again, we always strive to make our predictions in ways that can be measured as accurate or not. Is it binary? Did it happen, did it not? Kind of like an O K R and you know, we strive to provide data as proof and in this case it's a bit fuzzy. >>We have to admit that although we're pretty comfortable that the prediction was accurate. And look, when you make an hard forecast, sometimes you gotta pay the price. All right, next, we said in 2022 that the big four cloud players would generate 167 billion in IS and PaaS revenue combining for 38% market growth. And our current forecasts are shown here with a comparison to our January, 2022 figures. So coming into this year now where we are today, so currently we expect 162 billion in total revenue and a 33% growth rate. Still very healthy, but not on our mark. So we think a w s is gonna miss our predictions by about a billion dollars, not, you know, not bad for an 80 billion company. So they're not gonna hit that expectation though of getting really close to a hundred billion run rate. We thought they'd exit the year, you know, closer to, you know, 25 billion a quarter and we don't think they're gonna get there. >>Look, we pretty much nailed Azure even though our prediction W was was correct about g Google Cloud platform surpassing Alibaba, Alibaba, we way overestimated the performance of both of those companies. So we're gonna give ourselves a C plus here and we think, yeah, you might think it's a little bit harsh, we could argue for a B minus to the professor, but the misses on GCP and Alibaba we think warrant a a self penalty on this one. All right, let's move on to our prediction about Supercloud. We said it becomes a thing in 2022 and we think by many accounts it has, despite the naysayers, we're seeing clear evidence that the concept of a layer of value add that sits above and across clouds is taking shape. And on this slide we showed just some of the pickup in the industry. I mean one of the most interesting is CloudFlare, the biggest supercloud antagonist. >>Charles Fitzgerald even predicted that no vendor would ever use the term in their marketing. And that would be proof if that happened that Supercloud was a thing and he said it would never happen. Well CloudFlare has, and they launched their version of Supercloud at their developer week. Chris Miller of the register put out a Supercloud block diagram, something else that Charles Fitzgerald was, it was was pushing us for, which is rightly so, it was a good call on his part. And Chris Miller actually came up with one that's pretty good at David Linthicum also has produced a a a A block diagram, kind of similar, David uses the term metacloud and he uses the term supercloud kind of interchangeably to describe that trend. And so we we're aligned on that front. Brian Gracely has covered the concept on the popular cloud podcast. Berkeley launched the Sky computing initiative. >>You read through that white paper and many of the concepts highlighted in the Supercloud 3.0 community developed definition align with that. Walmart launched a platform with many of the supercloud salient attributes. So did Goldman Sachs, so did Capital One, so did nasdaq. So you know, sorry you can hate the term, but very clearly the evidence is gathering for the super cloud storm. We're gonna take an a plus on this one. Sorry, haters. Alright, let's talk about data mesh in our 21 predictions posts. We said that in the 2020s, 75% of large organizations are gonna re-architect their big data platforms. So kind of a decade long prediction. We don't like to do that always, but sometimes it's warranted. And because it was a longer term prediction, we, at the time in, in coming into 22 when we were evaluating our 21 predictions, we took a grade of incomplete because the sort of decade long or majority of the decade better part of the decade prediction. >>So last year, earlier this year, we said our number seven prediction was data mesh gains momentum in 22. But it's largely confined and narrow data problems with limited scope as you can see here with some of the key bullets. So there's a lot of discussion in the data community about data mesh and while there are an increasing number of examples, JP Morgan Chase, Intuit, H S P C, HelloFresh, and others that are completely rearchitecting parts of their data platform completely rearchitecting entire data platforms is non-trivial. There are organizational challenges, there're data, data ownership, debates, technical considerations, and in particular two of the four fundamental data mesh principles that the, the need for a self-service infrastructure and federated computational governance are challenging. Look, democratizing data and facilitating data sharing creates conflicts with regulatory requirements around data privacy. As such many organizations are being really selective with their data mesh implementations and hence our prediction of narrowing the scope of data mesh initiatives. >>I think that was right on J P M C is a good example of this, where you got a single group within a, within a division narrowly implementing the data mesh architecture. They're using a w s, they're using data lakes, they're using Amazon Glue, creating a catalog and a variety of other techniques to meet their objectives. They kind of automating data quality and it was pretty well thought out and interesting approach and I think it's gonna be made easier by some of the announcements that Amazon made at the recent, you know, reinvent, particularly trying to eliminate ET t l, better connections between Aurora and Redshift and, and, and better data sharing the data clean room. So a lot of that is gonna help. Of course, snowflake has been on this for a while now. Many other companies are facing, you know, limitations as we said here and this slide with their Hadoop data platforms. They need to do new, some new thinking around that to scale. HelloFresh is a really good example of this. Look, the bottom line is that organizations want to get more value from data and having a centralized, highly specialized teams that own the data problem, it's been a barrier and a blocker to success. The data mesh starts with organizational considerations as described in great detail by Ash Nair of Warner Brothers. So take a listen to this clip. >>Yeah, so when people think of Warner Brothers, you always think of like the movie studio, but we're more than that, right? I mean, you think of H B O, you think of t n t, you think of C N N. We have 30 plus brands in our portfolio and each have their own needs. So the, the idea of a data mesh really helps us because what we can do is we can federate access across the company so that, you know, CNN can work at their own pace. You know, when there's election season, they can ingest their own data and they don't have to, you know, bump up against, as an example, HBO if Game of Thrones is going on. >>So it's often the case that data mesh is in the eyes of the implementer. And while a company's implementation may not strictly adhere to Jamma Dani's vision of data mesh, and that's okay, the goal is to use data more effectively. And despite Gartner's attempts to deposition data mesh in favor of the somewhat confusing or frankly far more confusing data fabric concept that they stole from NetApp data mesh is taking hold in organizations globally today. So we're gonna take a B on this one. The prediction is shaping up the way we envision, but as we previously reported, it's gonna take some time. The better part of a decade in our view, new standards have to emerge to make this vision become reality and they'll come in the form of both open and de facto approaches. Okay, our eighth prediction last year focused on the face off between Snowflake and Databricks. >>And we realized this popular topic, and maybe one that's getting a little overplayed, but these are two companies that initially, you know, looked like they were shaping up as partners and they, by the way, they are still partnering in the field. But you go back a couple years ago, the idea of using an AW w s infrastructure, Databricks machine intelligence and applying that on top of Snowflake as a facile data warehouse, still very viable. But both of these companies, they have much larger ambitions. They got big total available markets to chase and large valuations that they have to justify. So what's happening is, as we've previously reported, each of these companies is moving toward the other firm's core domain and they're building out an ecosystem that'll be critical for their future. So as part of that effort, we said each is gonna become aggressive investors and maybe start doing some m and a and they have in various companies. >>And on this chart that we produced last year, we studied some of the companies that were targets and we've added some recent investments of both Snowflake and Databricks. As you can see, they've both, for example, invested in elation snowflake's, put money into Lacework, the Secur security firm, ThoughtSpot, which is trying to democratize data with ai. Collibra is a governance platform and you can see Databricks investments in data transformation with D B T labs, Matillion doing simplified business intelligence hunters. So that's, you know, they're security investment and so forth. So other than our thought that we'd see Databricks I p o last year, this prediction been pretty spot on. So we'll give ourselves an A on that one. Now observability has been a hot topic and we've been covering it for a while with our friends at E T R, particularly Eric Bradley. Our number nine prediction last year was basically that if you're not cloud native and observability, you are gonna be in big trouble. >>So everything guys gotta go cloud native. And that's clearly been the case. Splunk, the big player in the space has been transitioning to the cloud, hasn't always been pretty, as we reported, Datadog real momentum, the elk stack, that's open source model. You got new entrants that we've cited before, like observe, honeycomb, chaos search and others that we've, we've reported on, they're all born in the cloud. So we're gonna take another a on this one, admittedly, yeah, it's a re reasonably easy call, but you gotta have a few of those in the mix. Okay, our last prediction, our number 10 was around events. Something the cube knows a little bit about. We said that a new category of events would emerge as hybrid and that for the most part is happened. So that's gonna be the mainstay is what we said. That pure play virtual events are gonna give way to hi hybrid. >>And the narrative is that virtual only events are, you know, they're good for quick hits, but lousy replacements for in-person events. And you know that said, organizations of all shapes and sizes, they learn how to create better virtual content and support remote audiences during the pandemic. So when we set at pure play is gonna give way to hybrid, we said we, we i we implied or specific or specified that the physical event that v i p experience is going defined. That overall experience and those v i p events would create a little fomo, fear of, of missing out in a virtual component would overlay that serves an audience 10 x the size of the physical. We saw that really two really good examples. Red Hat Summit in Boston, small event, couple thousand people served tens of thousands, you know, online. Second was Google Cloud next v i p event in, in New York City. >>Everything else was, was, was, was virtual. You know, even examples of our prediction of metaverse like immersion have popped up and, and and, and you know, other companies are doing roadshow as we predicted like a lot of companies are doing it. You're seeing that as a major trend where organizations are going with their sales teams out into the regions and doing a little belly to belly action as opposed to the big giant event. That's a definitely a, a trend that we're seeing. So in reviewing this prediction, the grade we gave ourselves is, you know, maybe a bit unfair, it should be, you could argue for a higher grade, but the, but the organization still haven't figured it out. They have hybrid experiences but they generally do a really poor job of leveraging the afterglow and of event of an event. It still tends to be one and done, let's move on to the next event or the next city. >>Let the sales team pick up the pieces if they were paying attention. So because of that, we're only taking a B plus on this one. Okay, so that's the review of last year's predictions. You know, overall if you average out our grade on the 10 predictions that come out to a b plus, I dunno why we can't seem to get that elusive a, but we're gonna keep trying our friends at E T R and we are starting to look at the data for 2023 from the surveys and all the work that we've done on the cube and our, our analysis and we're gonna put together our predictions. We've had literally hundreds of inbounds from PR pros pitching us. We've got this huge thick folder that we've started to review with our yellow highlighter. And our plan is to review it this month, take a look at all the data, get some ideas from the inbounds and then the e t R of January surveys in the field. >>It's probably got a little over a thousand responses right now. You know, they'll get up to, you know, 1400 or so. And once we've digested all that, we're gonna go back and publish our predictions for 2023 sometime in January. So stay tuned for that. All right, we're gonna leave it there for today. You wanna thank Alex Myerson who's on production and he manages the podcast, Ken Schiffman as well out of our, our Boston studio. I gotta really heartfelt thank you to Kristen Martin and Cheryl Knight and their team. They helped get the word out on social and in our newsletters. Rob Ho is our editor in chief over at Silicon Angle who does some great editing for us. Thank you all. Remember all these podcasts are available or all these episodes are available is podcasts. Wherever you listen, just all you do Search Breaking analysis podcast, really getting some great traction there. Appreciate you guys subscribing. I published each week on wikibon.com, silicon angle.com or you can email me directly at david dot valante silicon angle.com or dm me Dante, or you can comment on my LinkedIn post. And please check out ETR AI for the very best survey data in the enterprise tech business. Some awesome stuff in there. This is Dante for the Cube Insights powered by etr. Thanks for watching and we'll see you next time on breaking analysis.

>> Narrator: "TheCUBE" presents Ignite 22. Brought to you by Palo Alto Networks. >> Hey everyone. Welcome back to "TheCUBE's" live coverage of Palo Alto Network's Ignite 22 from the MGM Grand in beautiful Las Vegas. I am Lisa Martin here with Dave Vellante. Dave, we just had a great conversa- First of all, we got to hear the keynote, most of it. We also just had a great conversation with the CEO and chairman of Palo Alto Networks, Nikesh Arora. You know, this is a company that was founded back in 2005, he's been there four years, a lot has happened. A lot of growth, a lot of momentum in his tenure. You were saying in your breaking analysis, that they are on track to nearly double revenues from FY 20 to 23. Lots of momentum in this cloud security company. >> Yeah, I'd never met him before. I mean, I've been following a little bit. It's interesting, he came in as, sort of, a security outsider. You know, he joked today that he, the host, I forget the guy's name on the stage, what was his name? Hassan. Hassan, he said "He's the only guy in the room that knows less about security than I do." Because, normally, this is an industry that's steeped in deep expertise. He came in and I think is given a good compliment to the hardcore techies at Palo Alto Network. The company, it's really interesting. The company started out building their own data centers, they called it. Now they look back and call it cloud, but it was their own data centers, kind of like Salesforce did, it's kind of like ServiceNow. Because at the time, you really couldn't do it in the public cloud. The public cloud was a little too unknown. And so they needed that type of control. But Palo Alto's been amazing story since 2020, we wrote about this during the pandemic. So what they did, is they began to pivot to the the true cloud native public cloud, which is kind of immature still. They don't tell you that, but it's kind of still a little bit immature, but it's working. And when they were pivoting, it was around the same time, at Fortinet, who's a competitor there's like, I call 'em a poor man's Palo Alto, and Fortinet probably hates that, but it's kind of true. It's like a value play on a comprehensive platform, and you know Fortinet a little bit. And so, but what was happening is Fortinet was executing on its cloud strategy better than Palo Alto. And there was a real divergence in the valuations of these stocks. And we said at the time, we felt like Palo Alto, being the gold standard, would get through it. And they did. And what's happened is interesting, I wrote about this two weeks ago. If you go back to the pandemic, peak of the pandemic, or just before the peak, kind of in that tech bubble, if you will. Splunk's down 44% from that peak, Okta's down, sorry, not down 44%. 44% of the peak. Okta's 22% of their peak. CrowdStrike, 41%, Zscaler, 36%, Fortinet, 71%. Not so bad. Palo Altos maintained 93% of its peak value, right? So it's a combination of two things. One is, they didn't run up as much during the pandemic, and they're executing through their cloud strategy. And that's provided a sort of softer landing. And I think it's going to be interesting to see where they go from here. And you heard Nikesh, we're going to double, and then double again. So that's 7 billion, 14 billion, heading to 30 billion. >> Lisa: Yeah, yeah. He also talked about one of the things that he's done in his tenure here, as really a workforce transformation. And we talk all the time, it's not just technology and processes, it's people. They've also seemed to have done a pretty good job from a cultural transformation perspective, which is benefiting their customers. And they're also growing- The ecosystem, we talked a little bit about the ecosystem with Nikesh. We've got Google Cloud on, we've got AWS on the program today alone, talking about the partnerships. The ecosystem is expanding, as well. >> Have you ever met Nir Zuk? >> I have not, not yet. >> He's the founder and CTO. I haven't, we've never been on "theCUBE." He was supposed to come on one day down in New York City. Stu and I were going to interview him, and he cut out of the conference early, so we didn't interview him. But he's a very opinionated dude. And you're going to see, he's basically going to come on, and I mean, I hope he is as opinionated on "TheCUBE," but he'll talk about how the industry has screwed it up. And Nikesh sort of talked about that, it's a shiny new toy strategy. Oh, there's another one, here's another one. It's the best in that category. Okay, let's get, and that's how we've gotten to this point. I always use that Optive graphic, which shows the taxonomy, and shows hundreds and hundreds of suppliers in the industry. And again, it's true. Customers have 20, 30, sometimes 40 different tool sets. And so now it's going to be interesting to see. So I guess my point is, it starts at the top. The founder, he's an outspoken, smart, tough Israeli, who's like, "We're going to take this on." We're not afraid to be ambitious. And so, so to your point about people and the culture, it starts there. >> Absolutely. You know, one of the things that you've written about in your breaking analysis over the weekend, Nikesh talked about it, they want to be the consolidator. You see this as they're building out the security supercloud. Talk to me about that. What do you think? What is a security supercloud in your opinion? >> Yeah, so let me start with the consolidator. So Palo Alto obviously is executing on that strategy. CrowdStrike as well, wants to be a consolidator. I would say Zscaler wants to be a consolidator. I would say that Microsoft wants to be a consolidator, so does Cisco. So they're all coming at it from different angles. Cisco coming at it from network security, which is Palo Alto's wheelhouse, with their next gen firewalls, network security. What Palo Alto did was interesting, was they started out with kind of a hardware based firewall, but they didn't try to shove everything into it. They put the other function in there, their cloud. Zscaler. Zscaler is the one running around saying you don't need firewalls anymore. Just run everything through our cloud, our security cloud. I would think that as Zscaler expands its TAM, it's going to start to acquire, and do similar types of things. We'll see how that integrates. CrowdStrike is clearly executing on a similar portfolio strategy, but they're coming at it from endpoint, okay? They have to partner for network security. Cisco is this big and legacy, but they've done a really good job of acquiring and using services to hide some of that complexity. Microsoft is, you know, they probably hate me saying this, but it's the just good enough strategy. And that may have hurt CrowdStrike last quarter, because the SMB was a soft, we'll see. But to specifically answer your question, the opportunity, we think, is to build the security supercloud. What does that mean? That means to have a common security platform across all clouds. So irrespective of whether you're running an Amazon, whether you're running an on-prem, Google, or Azure, the security policies, and the edicts, and the way you secure your enterprise, look the same. There's a PaaS layer, super PaaS layer for developers, so that that the developers can secure their code in a common framework across cloud. So that essentially, Nikesh sort of balked at it, said, "No, no, no, we're not, we're not really building a super cloud." But essentially they kind of are headed in that direction, I think. Although, what I don't know, like CrowdStrike and Microsoft are big competitors. He mentioned AWS and Google. We run on AWS, Google, and in their own data centers. That sounds like they don't currently run a Microsoft. 'Cause Microsoft is much more competitive with the security ecosystem. They got Identity, so they compete with Okta. They got Endpoint, so they compete with CrowdStrike, and Palo Alto. So Microsoft's at war with everybody. So can you build a super cloud on top of the clouds, the hyperscalers, and not do Microsoft? I would say no. >> Right. >> But there's nothing stopping Palo Alto from running in the Microsoft cloud. I don't know if that's a strategy, we should ask them. >> Yeah. They've done a great job in our last few minutes, of really expanding their TAM in the last few years, particularly under Nikesh's leadership. What are some of the things that you heard this morning that you think, really they've done a great job of expanding that TAM. He talked a little bit about, I didn't write the number down, but he talked a little bit about the market opportunity there. What do you see them doing as being best of breed for organizations that have 30 to 50 tools and need to consolidate that? >> Well the market opportunity's enormous. >> Lisa: It is. >> I mean, we're talking about, well north of a hundred billion dollars, I mean 150, 180, depending on whose numerator you use. Gartner, IDC. Dave's, whatever, it's big. Okay, and they've got... Okay, they're headed towards 7 billion out of 180 billion, whatever, again, number you use. So they started with network security, they put most of the network function in the cloud. They moved to Endpoint, Sassy for the edge. They've done acquisitions, the Cortex acquisition, to really bring automated threat intelligence. They just bought Cider Security, which is sort of the shift left, code security, developer, assistance, if you will. That whole shift left, protect right. And so I think a lot of opportunities to continue to acquire best of breed. I liked what Nikesh said. Keep the founders on board, sell them on the mission. Let them help with that integration and putting forth the cultural aspects. And then, sort of, integrate in. So big opportunities, do they get into Endpoint and compete with Okta? I think Okta's probably the one sort of outlier. They want to be the consolidator of identity, right? And they'll probably partner with Okta, just like Okta partners with CrowdStrike. So I think that's part of the challenge of being the consolidator. You're probably not going to be the consolidator for everything, but maybe someday you'll see some kind of mega merger of these companies. CrowdStrike and Okta, or Palo Alto and Okta, or to take on Microsoft, which would be kind of cool to watch. >> That would be. We have a great lineup, Dave. Today and tomorrow, full days, two full days of cube coverage. You mentioned Nir Zuk, we already had the CEO on, founder and CTO. We've got the chief product officer coming on next. We've got chief transformation officer of customers, partners. We're going to have great conversations, and really understand how this organization is helping customers ultimately achieve their SecOps transformation, their digital transformation. And really moved the needle forward to becoming secure data companies. So I'm looking forward to the next two days. >> Yeah, and Wendy Whitmore is coming on. She heads Unit 42, which is, from what I could tell, it's pretty much the competitor to Mandiant, which Google just bought. We had Kevin Mandia on at September at the CrowdStrike event. So that's interesting. That's who I was poking Nikesh a little bit on industry collaboration. You're tight with Google, and then he had an interesting answer. He said "Hey, you start sharing data, you don't know where it's going to go." I think Snowflake could help with that problem, actually. >> Interesting. >> Yeah, little Snowflake and some of the announcements ar Reinvent with the data clean rooms. Data sharing, you know, trusted data. That's one of the other things we didn't talk about, is the real tension in between security and regulation. So the regulators in public policy saying you can't move the data out of the country. And you have to prove to me that you have a chain of custody. That when you say you deleted something, you have to show me that you not only deleted the file, then the data, but also the metadata. That's a really hard problem. So to my point, something that Palo Alto might be able to solve. >> It might be. It'll be an interesting conversation with Unit 42. And like we said, we have a great lineup of guests today and tomorrow with you, so stick around. Lisa Martin and Dave Vellante are covering Palo Alto Networks Ignite 22 for you. We look forward to seeing you in our next segment. Stick around. (light music)

(upbeat music) (air whooshing) >> Good afternoon, cloud nerds, and welcome back to beautiful Las Vegas, Nevada. We are at AWS re:invent day four. Afternoon of day four here on theCUBE. I'm Savannah Peterson, joined by my fabulous cohost, Paul Gillin. Paul, you look sharp today. How you doing? >> Oh, you're just as fabulous, Savannah. You always look sharp. >> I appreciate that. They pay you enough to keep me buttered up over here at- (Paul laughing) It's wonderful. >> You're holding up well. >> Yeah, thank you. I am excited about our next conversation. Two fabulous gentlemen. Please welcome Sam and Monty, welcome to the show. >> Thank you. >> And it was great. Of the PR 2%, the most interesting man alive. (Paul and Savannah laughing) >> In person. Yeah, yeah. >> In the flesh. Our favorite guests so far. So how's the show been for you guys? >> Sam: It's been phenomenal. >> Just spending a lot of time with customers and partners and AWS. It's been great. It's been great. >> It is great. It's really about the community. It feels good to be back. >> Monty: Eating good food, getting my steps in above goals. >> I feel like the balance is good. We walk enough of these convention centers that you can enjoy the libations and the delicious food that's in Las Vegas and still not go home feeling like a cow. It is awesome. It's a win-win. >> To Sam's point though, meeting with customers, meeting with other technology providers that we may be able to partner with. And most importantly, in my role especially, meeting with all of our AWS key stakeholders in the partnership. So yeah, it's been great. >> Everyone's here. It's just different having a conversation in person. Even like us right now. So just in case folks aren't familiar, tell me about Talend. >> Yeah. Well, Talend is a data integration company. We've been around for a while. We have tons of different ways to get data from point A to point B, lots of different sources, lots of different connectors, and it's all about creating accessibility to that data. And then on top of that, we also have a number of solutions around governance, data health, data quality, data observability, which I think is really taking off. And so that's kind of how we're changing the business here. >> Casual change, data and governance. I don't know if anyone's talking about that at all on the snow floor. >> Been on big topic here. We've had a lot of conversations with the customers about that. >> So governance, what new dynamics has the cloud introduced into data governance? >> Well, I think historically, customers have been able to have their data on-prem. They put it into things like data lakes. And now having the flexibility to be able to bring that data to the clouds, it opens up a lot of doors, but it also opens up a lot of risks. So if you think about the chief data officer role, where you have, okay, I want to be able to bring my data to the users. I want to be able to do that at scale, operationally. But at the same time you have a tension then between the governance and the rules that really restrict the way that you can do that. Very strong tension between those two things. >> It really is a delicate balance. And especially as people are trying to accelerate and streamline their cloud projects, a lot to consider. How do you all help them do that? Monty, let's go to you. >> Yeah, we keep saying data, data, what is it really? It's ones and zeros. In this day and age, everything we see, we touch, we do, we either use data, or we create data, and then that... >> Savannah: We are data quite literally. >> We literally are data. And so then what you end up with is all these disparate data silos and different applications with different data, and how do you bring all that together? And that's where customers really struggle. And what we do is we bring it all together, and we make it actionable for the customer. We make it very simple for them to take the data, use it for the outcomes that they're looking for in their business initiatives. >> Expand on that. What do you mean make it actionable? Do you tag it? Do you organize it in some way? What's different about your approach? >> I mean, it's a really flexible platform. And I think we're part of a broader ecosystem. Even internally, we are a data driven company. Coming into the company in April, I was able to come in and get this realtime view of like, "Hey, here's where our teams are." And it's all in front of me in a Tableau dashboard that's populated from Talend integration, bringing data out of our different systems, different systems like Workday where we're giving offers out to people. And so everything from managing headcount to where our AWS spend is, all of that stuff. >> Now, we've heard a lot of talk about data and in fact the keynote yesterday that was focused mainly on data and getting data out of silos. How do you play with AWS in that role? Because AWS has other data integration partners. >> Sam: For sure. >> What's different about your relationship? Yeah. >> Go ahead. >> Yeah, we've had a strong relationship with AWS for many years now. We've got more than 80 connectors into the different AWS services. So we're not new to the AWS game. We align with the sales teams, we align with the partner teams, and then of course, we align with all the different business units and verticals so that we can enact that co-sell motion together with AWS. >> Sam: Yeah. And I think from our product standpoint, again, just being a hyper flexible platform, being able to put, again, any different type of source of data, to any type of different destination, so things like Redshift, being able to bring data into those cloud data warehouses is really how we do that. And then I think we have between bringing data from A to B, we're also able to do that along a number of different dimensions. Whether that's just like, "Hey, we just need to do this once a day to batch, all the way down to event driven things, streaming and the like. >> That customization must be really valuable for your customers as well. So one of the big themes of the show has been cost reduction. Obviously with the economic times as we're potentially dipping our toes into as well, is just in general, always wanting to increase margins. How do you help customers cut cost? >> Well, it's cost cutting, but it's also speed to market. The faster you can get a product to market, the faster you can help your customers. Let's say healthcare life sciences, pharmaceutical companies, patient outcomes. >> Great and timely example there. >> Patient outcomes, how do they get drugs to market quicker? Well, AstraZeneca leveraged our platform along with AWS. And they even said >> Cool. >> for every dollar that they spend on data initiatives, they get $40 back. That's a billion dollars >> Wow. >> savings by getting a drug to market one month faster. >> Everybody wins. >> How do you accelerate that process? >> Well, by giving them the right data, taking all the massive data that I mentioned, siloed in everywhere, and making it so that the data scientists can take all of this data and make use of it, makes sense of it, and move their drug production along much quicker. >> Yeah. And I think there's other things too like being very flexible in the way that it's deployed. Again, I think like you have this historical story of like, it takes forever for data to get updated, to get put together. >> Savannah: I need it now. And in context. >> And I think where we're coming from is almost more of a developer focus where your jobs are able to be deployed in any way you want. If you want to containerize those, you want to scale them, you need to schedule them that way. We plug into a lot of different ecosystems. I think that's a differentiation as well. >> I want to hang out on this one just for a second 'cause it's such a great customer success story and so powerful. I mean, in VC land, if you can take a dollar and make two, they'll give you a 10x valuation, 40. That is so compelling. I mean, do you think other customers could expect that kind of savings? A billion dollars is nothing to laugh at especially when we're talking about developing a vaccine. Yeah, go for it, Sam. >> It really depends on the use case. I think what we're trying to do is being able to say, "Hey, it's not just about cost cutting, but it's about tailoring the offerings." We have other customers like major fast food vendors. They have mobile apps and when you pull up that mobile app and you're going to do a delivery, they want to be able to have a customized offering. And it's not like mass market, 20% off. It's like, they want to have a very tailored offer to that customer or to that person that's pulling open that app. And so we're able to help them architect and bring that data together so that it's immediately available and reliable to be able to give those promotions. >> We had ARP on the show yesterday. We're talking about 50 million subscribers and how they customize each one of their experiences. We all want it to be about us. We don't want that generic at... Yeah, go for it, Paul. >> Oh, okay. >> Yeah. >> Well, I don't want to break break the rhythm here, but one area where you have differentiated, about two years ago you introduced something called the trust score. >> Sam: Yeah. >> Can you explain what that is and how that has resonated with your customers? >> Yeah, let's talk about this. >> Yeah, the thing about the trust score is, how many times have you gotten a set of data? And you look at it and you say, "Where did you get this data? Something doesn't look right here." And with the trust score, what we're able to do is quantify and value the different attributes of the data. Whether it's how much this is being used. We can profile the data, and we have a trust score that runs over time where you can actually then look at each of these data sets. You can look at aggregates of data sets to then say... If you're the data engineer, you can say, "Oh my, something has gone wrong with this particular dataset." Go in, quickly pull up the data. You can see if some third party integration has polluted your data source. I mean, this happens all the time. And I think if you sort of compare this to the engineering world, you're always looking to solve those problems sooner, earlier in the chain. You don't want your consumer calling you saying, "Hey, I've got a problem with the data, or I've got a problem- >> You don't want them to know there was ever a problem in theory. >> Yeah, the trust score helps those data engineers and those people that are taking care of the data address those problems sooner. >> How much data does somebody need to be able to get to the point where they can have a trust score? If you know what I'm trying to say. How do we train that? >> I mean, it can be all the way from just like a single data source that's getting updated, all the way to very large complex ones. That's where we've introduced this hierarchy of data sets. So it's not just like, "Hey, you've got a billion data sources here and here are the trust scores." But it's like, you can actually architect this to say like, "Okay, well, I have these data sets that belong to finance." And then finance will actually get, "Here's the trust score for these data sets that they rely on." >> What causes datasets to become untrustworthy? >> Yeah. Yeah. I mean, it happens all the time. >> A of different things, right? >> In my history, in the different companies that I've been at, on the product side, we have seen different integrations that maybe somebody changes something. In upstream, some of those integrations can actually be quite brittle. And as a consumer of that data, it's not necessarily your fault, but that data ends up getting put into your production database. All of a sudden your data engineering team is spending two days unwinding those transactions, fixing the data that's in there. And all the while, that bad data that's in your production system, is causing a problem for somebody that is ultimately relying on that. >> Is that usually a governance problem? >> I think governance is probably a separate set of constraints. This is sort of the tension between wanting to get all of the data available to your consumers versus wanting to have the quality around it as well. >> It's tough balance. And I think that it's really interesting. Everybody wants great data, and you could be making decisions that affect people's wellness, quite frankly. >> For sure. >> Very dramatically if you're ill-informed. So that's very exciting. >> To your point, we are all data. So if the data is bad, we're not going to get the outcomes that we want ultimately, >> I know. We certainly want the best outcomes for ourselves. >> We track that data health for its entire life cycle throughout the process. >> That's cool. And that probably increases your confidence in the trust score as well 'cause you're looking at so much data all the time. You got a smart thing going on over here. I like it. I like it a lot. >> We believe in it and so does AWS because they are a strong partner of ours, and so do customers. I think we mentioned we've had some phenomenal customer conversations along with- >> What a success story and case study. I want to dust your shoulders off right now if I wasn't tethered in. That's super impressive. So what's next for you all? >> Yeah, so I think we're going to continue down this path of data health and data governance. Again, I kind of talked about the... you're talking about data health being this differentiator on top of just moving the data around and being really good at that. I think you're also going to have different things around country level or state level governance, literal laws that you need to comply with. And so like- >> Savannah: CCPA- >> I mean, a long list- >> Oodles. Yeah. Yeah, yeah, yeah. >> I think we're going to be doing some interesting things there. We are continuing to proliferate the sources of data that we connect to. We're always looking for the latest and greatest things to put the data into. I think you're going to see some interesting things come out of that too. >> And we continue to grow our relationship with AWS, our already strong relationship. So you can procure Talend products to the AWS marketplace. We just announced Redshift serverless support for Talend. >> All their age. >> Which sounds amazing, but because we've been doing this for so long with AWS, dirty little secret, that was easy for us to do because we're already doing all this stuff. So we made the announcement and everyone was like, "Congratulations." Like, "Thanks." >> Look at you all. Full of the humble brags. I love it. >> Talend has gone through some twists and turns over the last couple of years. Company went private, was purchased by Thoma Bravo about a year and a half ago. At that time, your CEO said that it was a chance to really refocus the company on some core strategic initiatives and move forward. Both of you joined obviously after that happened. But what did you see about sort of the new Talend that attracted you, made you want to come over here? >> For sure. Yeah. I think, when I got a chance to talk to the board and talk to Chris, our chair, we talked about there being the growth thesis behind it. So I think Thoma been a great partner to Talend. I think we're able to do some things internally that would be I think, fairly challenging for companies that are in the public markets right now. I think especially, just a lot of pressure on different prices and the cost capital and all of that. >> Right now. >> That was a really casual way of stating that. But yeah, just a little pressure. >> Little bit of pressure. And who knows? Who knows how long that's going to last, right? But I think we've got a great board in place. They've been very strong strategic partner for us talking about all the different ways that we can grow. I think it's been a good partner for us- >> One of the strengths of Thoma's strategy is synergy between the companies they've acquired. >> Oh, for sure. >> They've acquired about 40 software companies. Are you seeing synergy? You talk to those other companies a lot? >> Yeah, so I have an operating partner. I talk with him on a weekly, sometimes daily basis. If we have questions or like, "Hey, what are you seeing in this space?" We can get plugged in to advisors very quickly. I think it's been a very helpful thing where... otherwise, you're relying on your personal network or things like that. >> This is why Monty was saying it was easy for you guys to go serverless. >> And we keep talking about trust, but in this case, Thoma Bravo really trusts our senior leadership team to make the right decisions that Sam and I are here making as we move forward. It's a great relationship. >> Sam: A good team. >> It sounds like it. All the love. I can feel the love even from you guys talking about it, it's genuine. You're not just getting paid to show this. That's fantastic. >> Are we getting paid for this or... >> Yeah. (Savannah giggling) (Paul laughing) I mean, some folks in the audience are probably going to want your autograph after this, although you get that a lot- >> Pictures are available after- >> Yeah, selfies are 10 bucks. That's how I get my boos budget. So last question for you. We have a challenge here on the theCUBE re:invent. We're looking for your 32nd hot take. Think of it as your thought leadership sizzle reel. Biggest takeaway, key themes from the show or looking forward into 2023? Sam, you're ready to rock, go. >> Yeah, totally. >> I think you're going to continue to hear the tension between being able to bring the data to the masses versus the simplicity and being able to do that in a way that is compliant with all the different laws, and then clean data. It's like a lot of different challenges that arise when you do this at scale. And so I think if you look at the things that AWS is announcing, I think you look at any sort of vendor in the data space are announcing, you see them sort of coming around to that set of ideas. Gives me a lot of confidence in the direction that we're going that we're doing the right stuff and we're meeting customers and prospects and partners, and everybody is like... We kind of get into this conversation and I'll say, "Yeah, that's it. We want to get involved in that." >> You can really feel the momentum. Yeah, it's true. It's great. What about you, Monty? >> I mean, I don't need 30 seconds. I mentioned it. >> Great. >> Between Talend and AWS, we're aligned from the sales teams to the product teams, the partner teams and the alliances. We're just moving forward and growing this relationship. >> I love it. That was perfect. And on that note, Sam, Monty, thank you so much for joining us. >> Yeah, thanks for having us. >> I'm sure your careers are going to continue to be rad at Talend and I can't wait to continue the conversation. >> Sam: Yeah, it's a great team. >> Yeah, clearly. I mean, look at you two. If you're any representation of the culture over there, they're doing something great. (Monty laughing) I thank all of you for tuning in to our nearly... Well, shoot. I think now over 100 interviews at AWS Reinvent in Sin City. We are hanging out here. Paul and I've got a couple more for you. So we hope to see you tuning in with Paul Gillin. I'm Savannah Peterson. You're watching theCUBE, the leader in high tech coverage. (upbeat music)

(upbeat music) >> Hello, brilliant cloud community, and welcome back to AWS re:Invent. We are here in Las Vegas, Nevada. I'm Savannah Peterson, joined by my co-host Dave Vellante. Dave, how you doing? >> I'm doing well, thanks, yeah. >> Yeah, I feel like... >> I'm hanging in there. >> you've got a lot of pep in your step today for the fourth day. >> I think my voice is coming back, actually. >> (laughs) Look at you, resilient. >> I was almost lost yesterday, yeah. >> Yeah. (laughs) >> So, I actually, at a Hitachi event one time almost completely lost my voice. The production guys pulled me off. They said, "You're done." (Savannah laughing) They gave me the hook. >> You got booted? >> Dave: Yeah, yeah. >> Yeah, yeah, you actually (laughs) got the hook, wow. >> So, I have good memories of Hitachi. >> I was going to say (Dave laughing) interesting that you mentioned Hitachi. Our two guests this morning are from Hitachi. Sid and KP, welcome to the show. >> Thank you. >> Savannah: How you guys doing? Looking great for day four. >> Great. Thank you. >> Great. >> Hanging in there. >> Thank you, Dave and Savannah. (Savannah laughing) >> Dave: Yeah, cool. >> Savannah: Yeah. (laughs) >> Yeah, it was actually a Pentaho thing, right? >> Oh, Pentaho? Yeah. >> Which kind of you guys into that software edge. It was right when you announced the name change to Hitachi Vantara, which is very cool. I had Brian Householder on. You remember Brian? >> Yeah, I know. >> He was explaining the vision, and yeah (indistinct). >> Yeah. Well, look at you a little Hitachi (indistinct). >> Yeah, I've been around a long time, yeah. >> Yeah, all right. (Dave laughing) >> Just a casual flex to start us off there, Dave. I love it. I love it. Sid, we've talked a lot on the show about delivering outcomes. It's a hot theme. Everyone wants to actually have tangible business outcomes from all of this. How are customers realizing value from the cloud? What does that mean? >> See, still 2007, 2008, it was either/or kind of architecture. Either I'm going to execute my use cases on cloud or I'm going to keep my use cases and outcomes through edge. But in the last four or five years and specifically we are in re:Invent, I would talk about AWS. Lot of the power of hyperscalers has been brought to edge. If you talk about the snowball family of AWS, if you talk about monitor on edge devices, if you talk about the entire server list being brought into Lambda coupled inside snowball, now the architecture premise, if I talk about logical shift is end. Now the customers are talking about executing the use cases between edge and cloud. So, there is a continuum rather than a binary bullion decision. So, if you are talking about optimizing a factory, earlier I'll do the analytics at cloud, and I'll do machine on edge. Now it is optimization of a factory outcome at scale across my entire manufacturing where edge, private cloud, AWS, hyperscalers, everything is a continuum. And the customer is not worried about where, which part of my data ops, network ops, server ops storage ops is being executed. >> Savannah: It's like (indistinct). >> The customer is enjoying the use cases. And the orchestration is abstracted through an industrial player like Hitachi working very collaboratively with AWS. So, that is how we are working on industrial use cases right now. >> You brought up manufacturing. I don't think there's been a hotter conversation around supply chain and manufacturing than there has been the last few years. I can imagine taking that guessing game out for customers is a huge deal for you guys. >> Big because if you look at the world today, right from a safety pin, to a cell phone jacket, to a cell phone, the entire supply chain is throttled. The supply chain is throttled because there are various choke points. >> Savannah: Yeah. >> And each choke points is surrounded by different kind of supply and geopolitical issues. >> Savannah: 100%. >> Now, if we talk about the wheat crisis happening because of the Ukraine-Russia war, but the wheat crisis actually creates a multiple string of impacts which impact everything. Silicon, now we talk about silicon, but we then forget about nickel. Nickel is also controlled in one part of that geopolitical conflict. So, everything is getting conflagrated into a very big supply issue. So, if your factories are not performing beyond optimum, if they are not performing at real, I'm, we are talking about factory, hyperscale of the factory. The factory needs to perform at hyperscale to provide what the world needs today. So, we are in a very different kind of a scenario. Some of the economists call it earlier the recession was because of a demand constraint. The demand used to go down. Today's recession is because the supply is going down. The demand is there, but the supply is going down. And there is a different kind of recession in the world. The supply is what is getting throttled. >> And the demand is somewhat unpredictable too. People, you know, retailers, they've... >> Especially right now. >> kind of messed up their inventory. And so, the data is still siloed. And that's where, you know, you get to, okay, can I have the same experience across clouds, on-prem, out to the edge? Kind of bust those silos. >> Yep. >> You know, I dunno if it's, it's certainly not entirely a data problem. There's (laughs), like you say, geopolitical and social issues. >> Savannah: There's so much complexity. >> But there's a data problem too. >> Yes. >> Big. >> So, I wonder if you could talk about your sort of view of, point of view on that cross-cloud, hybrid, out to the edge, what I call super cloud? >> Absolutely. So, today, if you look at how enterprises are adopting cloud or how they're leveraging cloud, it's not just a hosting platform, right? It is the platform from where they can draw business capabilities. You heard in the re:Invent that Amazon is coming up with a supply chain service out of the box in the cloud. That's the kind of capabilities that business wants to draw from cloud today. So, the kind of multicloud or like hybrid cloud, public cloud, private cloud, those are the things which are kind of going to be behind the scenes. At the end of the day, the cloud needs to be able to support businesses by providing their services closer to their consumers. So, the challenges are going to be there in terms of like reliability, resilience, cost, security. Those are the ones that, you know, many of the enterprises are grappling with in terms of the challenges. And the way to solve that, the way how we approach our customers and work with them is to be able to bring resilience into the cloud, into the services which are running in cloud, and by driving automation, making autonomous in everything that you do, how you are monitoring your services, how we are making it available, how we are securing it, how we are making it very cost-effective as well. It cannot be manually executed; it has to be automated. So, automation is the key in terms of making the services leveraged from all of this cloud. >> That's your value add. >> Absolutely. >> And how do I consume that value add? Is it sort of embedded into infrastructure? Is it a service layer on top? >> Yeah, so everything that we do today in terms of like how these services have to be provided, how the services have to be consumed, there has to be a modern operating model, right? I think this is where Hitachi has come up with what we are calling as Hitachi Application Reliability Center and Services. That is focusing on modern operating, modern ways of like, you know, how you support these cloud workloads and driving this automation. So, whether we provide a hyper-converged infrastructure that is going to be at the edge location, or we are going to be able to take a customer through the journey of modernization or migrating onto cloud, the operating model that is going to be able to establish the foundation on cloud and then to be able to operate with the right levels of reliability, security, cost is the key. And that's the value added service that we provide. And then the way we do that is essentially by looking at three principles: one, to look at the service in totality. Gone are the days you look at infrastructure separately, applications separately, data and security separately, right? >> Savannah: No more silos. >> No more silos. You look at it as a workload, and you look at it as a service. And number two is to make sure that the DevOps that you bring and what you do at the table is totally integrated and it's end to end. It's not a product team developing a feature and then ops team trying to keep the lights on. It has to be a common backlog with the error budget that looks at you know, product releases, product functionalities, and even what ops needs to do to evolve the product as well. And then the third is to make sure that reliability and resiliency is inbuilt. Cloud offers native durability, native availability. But if your service doesn't take advantage of that, it's kind of going to still be not available. So, how do you kind of ingrain and embed all of these things as a value add that we provide? >> There's a lot of noise. We've got hybrid cloud. We've got multicloud. We've got a lot going on. It adds to the complexity. How do you help customers solve that complexity as they begin their transformation journey? I mean, I'm sure you're working with the biggest companies, making really massive change. How do you guide them through that process? >> So, it is to look at the outcome working backwards, like what AWS does, right? Like, you know, how do you look at the business outcome? What is the value that you're looking to drive? Again, it's not to be pinned through one particular cloud. I know there is lot of technology choices that you can make and lot of deployment models that you can choose from. But at the end of the day, having a common operating model which is kind of like modern, agile, and it is kind of like keeping the outcomes in the mind, that is what we do with our customers to be able to create that operating model, which completes the transformation, by the way. And cloud is just one part of the LEGO blocks which provides that overall scheme and then the view for driving that overall transformation. >> So, let's paint a picture. Let's say you've got this resilient foundation; you've kind of helped the customers build that out. How do they turn that into value for their customers? Do you have any examples that you can share? That'd be great. >> Yeah, I can start with what we're doing for one of the, you know, world's largest facility, infrastructure, power, cooling, security, monitoring company that has their products deployed in 2,000 locations across the globe. For them, and always on business means you are monitoring the temperature. You are monitoring the safety of people who are within the facility, right? A temperature shift of one to two degree can affect even the sustainability goals of NARC, our customer, but also their end consumers. So, how do you monitor these kind of like critical parameters? How do you have a platform? >> Savannah: Great example, yeah. >> How you have cloud resources that are going to be always on, that are going to be reliable, that are going to be cost-effective as well is what we are doing for one of our customers. Sid can talk about another example as well. >> Great. >> Yeah, go for it, Sid. >> So, there are examples: rail. We are working with a group in England; it's called West Coast Partnership. And they had a edge device which was increasing in size. Now, this edge device was becoming big because the parameters which go into the edge device were increasing because of regulation and because the rail is part of national security infrastructure. We have worked with West Coast Partnership and Hitachi Rail, which is a group company, to create a miniaturization of this edge device, because if the size of the edge device is increasing on the train, then the weight of the train increases, and the speed profile, velocity profile, everything goes down. So, we have miniaturized the edge device. Secondly, all the data profiles, signal control, traction control, traction motors, direction control, timetable compliance, everything has been kept uniform. And we have done analytics on cloud. So, what is the behavior of the driver? What is a big breaking parameter of the driver? If the timetable has being missed, is there an erratic behavior being demonstrated by the driver to just meet the timetable? And the timetable is a pretty important criteria in rail because if you miss one, then... So, what we have done is we have created an edge-to-cloud environment where the entire rail analytics is happening. Similarly, in another group company, Hitachi Energy, they had a problem that arguably one of the largest transformer manufacturer in the world. The transformer is a pretty common name now because you're seeing what is happening in Ukraine. Russia went after the transformers and substations before the start of the winter so that their district heating can be meddled with. Now, the transformer, it had a lead time of 17 weeks before COVID. So, if you put me an order of a three-phase transformer, I can deliver it to you in 17 weeks. After and during COVID, the entire lead time increased to 57 to 58 weeks. In cases of a complex transformer, it even went up to something like two years. >> Savannah: Ooh! >> Now, they wanted to increase the productivity of their existing plant because there is only that much sheet metal, that much copper for solenoid, that much microprocessor and silicon. So, they wanted to increase the output of their factory from 95 to 105, 10 more transformers every day, which is 500 and, which is 3,650 every- >> Savannah: Year. >> Year. Now, to do that, we went to a very complex machine; it's called a guard machine. And we increased the productivity of the guard machine by just analyzing all the throttles and all the wastages which are happening there. There are multiple case studies because, see, Hitachi is an industrial giant with 105 years of body of work. KP and I just represent the tip of the digital tip of the arrow. But what we are trying to do through HARC, through industry cloud, through partnership with AWS is basically containerizing and miniaturizing our entire body of work into a democratized environment, an industrial app store, if I may say, where people can come and take their industrial outcomes at ease without worrying about their computational and network orchestration between edge and cloud. That's what we are trying to do. >> I love that analogy of an industrial app cloud. Makes it feel easier in decreasing the complexity of all the different things that everyone's factoring into making their products, whatever they're making. So, we have a new challenge here on theCUBE at AWS re:Invent, where we are looking for your 30-second hot take, your Instagram reel, sound bite. What's the most important story or theme either for you as a team or coming out of the show? You can ponder it for a second. >> It might be different. See, for me, it is industrial security. Industrial OT security should be the theme of the Western world. Western world is on the crosshairs of multiple bad actors. And the industrial security is in the chemical plants, is in the industrial plants, is in the power grids, is in our postal networks and our rail networks. They need to be secured; otherwise, we are geopolitically very weak. Gone are the days when anyone is going to pick up a battle with America or Western world on a field. The battle is going to be pretty clandestine on an cyber world. And that is why industrial security is very important. >> Critical infrastructure and protecting it. >> Absolutely. >> Well said, Sid. KP, what's your hot take? >> My take is going to be a modern operating model, which is going to complete the transformation and to be able to tap into business services from cloud. So, a modern operating model through HARC, that is going to be my take. >> Fantastic. Well, can't wait to see what comes out of Hitachi next. Sid, KP... >> KP: Thank you. >> thank you so much for being here. >> Sid: Thank you. >> Absolutely. >> Dave: Thanks, guys. >> Savannah: This is I could talk to you all about supply chain all day long. And thank all of you for tuning in to our continuous live coverage here from AWS re:Invent in fantastic Sin City. I'm Savannah. Oh, excuse me. With Dave Vellante, I'm Savannah Peterson. You're watching theCUBE, the leader in high tech coverage. (digital xylophone music)

(upbeat music) >> Welcome back to theCUBE's live coverage of AWS re:Invent. Friends, it's good to see you. Lisa Martin here with Dave Vellante. This is our fourth day of CUBE wall-to-wall coverage, Dave. I can't believe it. And the expo hall is still going incredibly strong. >> Yeah, it is. It feels like the biggest re:Invent ever. I'm told it's almost as big as 2019. I don't know, maybe I was half asleep at 2019. That's very possible. But I'm excited because in 2017 Andy Jassy came on theCUBE and he said if Amazon had to do it all over again, if it knew then what it had now, we would've done the whole thing in containers or using Lambda, using serverless and using containers. Didn't have that opportunity back then. And I'm excited 'cause Rafay Systems is someone we've worked with a lot as an innovator in this space. >> Yep, and we're going to be talking with Rafay again. I think it's your 10th time Haseeb on the show >> Like once or twice. >> And a great customer who's going to talk about their serverless journey. Haseeb Budhani joins us once again, the CEO of Rafay. Great to see you. Rakesh Singh is here as well, the Head of Cloud and DevOps at Regeneron. Guys, it's great to have you on the program. How you feeling on day four of re:Invent? >> Excitement is as high as ever basically. >> Isn't it amazing? >> Rakesh: That's true. >> Haseeb: I just need some sleep. >> I'm with you on that. Caffeine and sleep. >> So many parties. So many meetings, oh my God. >> But the great thing is, Haseeb, that people want to engage with you. They're loving what Rafay is doing. You guys are a great testament to that, which we're going to uncover on the show. What are some of the things that you're hearing in the booth from customers? What's been some of the feedback? >> So firstly, as I said, it feels like the biggest one ever. I've been coming to re:Invent a long time and I mean, I know the numbers say it's not, but oh my God, this is a lot of people. Every time we've spoken over the last year and the point I always make to you, and we've spoken enough time about this is that enterprises are truly adopting this idea of Kubernetes containers, serverless, et cetera. And they're all trying to figure out what is the enterprise strategy for these things? They're thinking beyond technology and thinking operationalization of these technologies. And that's not the same thing. There's a toy and then there's the real thing. And that's not the same thing. And that's the gap that every enterprise customer I talked to and the booth traffic has been just amazing. I mean, but coming here I was thinking, my God, this is really expensive. And I'm thinking, wow, this is a great investment. Because we met such amazing companies who all essentially are saying exactly the same thing, which is as we go and productize and bring our high value applications to the modern infrastructure space, like Kubernetes, Lambda, et cetera, solving for the automation governance is really, really hard because, well, at one point, I guess when the economy was doing crazy well, I could keep hiring people, but I can't do that anymore either. So they're out looking for automation strategies that allow them to do more with the teams they have. And that's exactly what Rafay is here for. >> Yeah. Lisa, Adam Selipsky in his keynote, I love the, he said, "If you want to save money, the cloud is the place to do it." >> Exactly. Yep. Let's talk about Regeneron. Everyone knows it's a household word especially over the last couple of years, but talk about, Rakesh, Regeneron as a technology company that delivers life-saving pharmaceuticals. And where does cloud and Rafay fit into your strategy? >> So cloud has been a backbone of our compute strategy within Regeneron for a very long time now. The evolution from a traditional compute structure to more serverless compute has been growing at a rapid pace. And I would say like we are seeing exponential growth within the adaption of the compute within containers and Kubernetes world. So we've been on this journey for a long time and I think it's not stopping anytime soon. So we have more and more workload, which is running on Kubernetes containers and we are looking forward to our partnership with Rafay to further enhance it, as Haseeb mentioned, the efficiency is the key. We need to do more with less. Resourcing is critical and cloud is evolved from that journey that do more things in a more efficient manner. >> That was the original catalyst as we got to help our development team, be more productive. >> That's correct. >> Eliminate the heavy lifting. And then you started presumably doing some of the less heavy, but still heavy lifting and we talked off camera and then you're increasingly moving toward serverless. >> Rakesh: That's correct. >> Can you describe that journey? What that's like? >> So I think like with the whole adoption that things are taking a much faster pace. Basically we are putting more compute onto containers and the DevOps journey is increasingly getting more, more faster. >> Go ahead. 'Cause I want to understand where Rafay sits in this whole equation. I was talking about, I'm not a developer, but I was talking to developer yesterday trying to really understand the benefits of containers and serverless and I said, take me through what you have to do when you're using containers. He said, I got to build the container image then I got to deploy an EC2 instance where I got to choose and I got to allocate memory of the fence the app in a VM then I got to run the computing instance against the app. And then, oh by the way, I got to pay 'cause all that EC2 that whole time. Depending on how you approach serverless you're going to eliminate a lot of those steps. >> That is correct. So what we do is basically like in a traditional sense, the computer is sitting idle at quite a lot basically. >> But you're paying. >> And you're still paying for that. Serverless technologies allows us to use the compute as needed basis. So whenever you need it, it is available. You run your workload on that and after that it shuts down or goes to minimal state and you don't need to pay as much as your paying. >> And then where do you guys fit in that whole equation? >> Look, serverless has a paradigm. If you step back from the idea of containers versus Lambda or whatever functions. The idea should be that the list you just read out of what developers have to do. Here's what they really should do. They should write their code, they should check it in, and they never have to think about it again. That should be the case. If they want to debug their application, there should be a nice front end where they go and they interact with their application and that's it. What is Kubernetes? I don't care. That's the right answer. And we did not start this journey as an industry there because usually the initial adopters are developers who do the heavy lifting. Developers want to learn, they want to solve these problems. But then eventually the expectation is that the platform organization and an enterprise is going to own this platform for me so I can go back to doing my job, which is writing code. And that's where Rakesh's team comes in. So Rakesh team is building the standard at Regeneron. Whether you're writing a long-lasting app, which is going to run in a container or you're going to write an event-driven application, which is going to be a function, whatever. You write your app, we will give you the necessary tooling and plumbing to take care of all these things. And this is my problem. My being Rakesh. Rakesh is my customer. He has his customers. We as Rafay, A, we have to make Rakesh's system successful because we have to give them right automation to do all these things so that he can service hundred, or in his case, thousands and thousands of different individuals. But then collectively, we have to make sure that the developer experience is optimal so that truly they just write their code and EC2, they don't want to deal with this. In fact, on Monday evening, in the Kubernetes keynote by Barry Cooks, one of the things he said was that in a CIO sort of survey they did, CIO said, 80% of the time of developers is wasted on infrastructure stuff and not on innovation. We need to bring that 80% back so that a hundred percent of the work is on innovation and today it's not. >> And that's what you do. >> That's what we do. >> In your world as a developer, I only have to worry about my writing my code and what functions I'm going to call. >> That is correct. And it is important because the efficiencies of a developer need to be focused on doing the things which business is asking for. The 80% of the work like to make sure the things are secure, they're done the right way, the standards are followed, scanning part of it, that work if we can offload to a platform, for example, Rafay, saves a lot of works, a lot of work cycles from the developers perspective. >> Thank you for that. It was nice little tutorial on the benefits. >> Absolutely. So you transform the developer experience. >> That's correct. >> How does that impact Regeneron overall business? We uplevel that. Give me that view. >> So with that, like what happens, the key thing is the developers productivity increases. We are able to do more with less. And that is the key thing to our strategy that like with the increase in business demand, with the increase in lot of compute things, which we are doing, we need to do and hiring resources is getting more difficult than ever. And we need to make sure that we are leveraging platforms and tools basically to do, enable our developers to focus on key business activity rather than doing redundant things and things which we can leverage some other tooling and platform for that business. >> Is this something in terms of improving the developer experience and their productivity faster time to market? Is this accelerating? >> That's correct. >> Is this even like accelerating drug discovery in some cases? >> So COVID is like a great example for that. Like we were able to fast track our drug discovery and like we were able to turn it into an experience where we were able to discover new drugs and get it to the market in a much faster pace. That whole process was expedited using these tools and processes basically. So we are very proud of that. >> So my understanding is you're running Rafay with EKS. A lot of choices out there. Why? Why did you choose to go in that direction? >> So Regeneron has heavily invested in cloud recently, over the years basically. And then we are focusing on hybrid cloud now that we we are like, again, these multiple cloud providers of platforms which are coming in are strategies to focus on hybrid cloud and Rafay is big leader in that particular space where we felt that we need to engage or partner with Rafay to enable those capabilities, not just on AWS, but across the board. One single tool, one single process, one single knowledge base helps us achieve more efficiencies. >> Less chaos, less complexity. >> That's correct. Let's say when you're in customer conversations, which I know you've had many this week, but you probably do that all the time. Regeneron is a great use case for Rafay. It's so tangible, life sciences. We all get that, especially coming out of the pandemic. What do you say to customers are the top three differentiators of Rafay and why they should go Rafay on top of EKS? >> What's really interesting about these conversations is that, look, we have some pretty cool features in our product. Obviously we must have something interesting otherwise nobody would buy our product. And we have access management and zero trust models and cluster provisioning, all these very nice things. But it always comes down to exactly the same thing, which is every large enterprise that started a journey, independent or Rafay because they didn't know who we were, it's fine. Last year we were a young company, now we are a larger company and they all are basically building towards a roadmap which Rafay truly understands. And in my opinion, and I'm confident when I say this, we understand their life, their journey better than any other company in the market. The reason why we have the flurry of customers we have, the reason why the product has the capacity that it does is because for whatever reason, look, it's scale lock. That's for the history books. But we have complete clarity on what a pharmaceutical company or financial customers company or a high tech company the journey they will take to the cloud and automation for modern infrastructure, we get it. And what I'm selling them is the is the why, not the what. There's a lot of great answers for the what? What do we do? Rakesh doesn't care. I mean, he's trying to solve a bigger problem. He's trying to get his researchers to go faster. So then when they want to run a model, they should be able to do it right now. That's what he cares about. Then he looks for a tool to solve the business problem. And we figured out how to have that conversation and explain why Rafay helps him, essentially multiply the bandwidth that he has in his organization. And of course to that end we have some great technology/ But that's a secondary issue, the first, to me the why is more important than the what. And then we talk about how, which he has to pay us money. That's the how. But yeah, we get there too. But look, this is the important thing. Every enterprise is on exactly the same journey, Lisa. And that if you think about it from just purely economic efficiencies perspective that is not a good investment for our industry. If everybody's solving the same problem that's a waste of resources. Let's find a way to do, what is the point of the cloud? We used to all build data centers. That was not efficient. We all went to the cloud because it's more efficient to have somebody else, AWS, solve this problem for us so we can now focus on the next level problem. And then Rafay solving that problem so that he can focus on his drug discovery, not on Kubernetes. >> That's correct. It's all about efficiencies. Like doing things, learn from each other's experience and build upon it. So the things have been solved. One way you need to leverage that, reuse it. So the principles are the same. >> So then what's next? You had done an amazing job transforming the company. You're facilitating drug discovery faster than ever before. From an infrastructure perspective, what's next on your journey? >> So right now the roadmap what we have is basically talking about making sure that the workload are running more efficient, they're more secure. As we go into these expandable serverless technology, there are more challenging opportunities for us to solve. Those challenges are coming up. We need to make sure that with the new, the world we are living in, we are more securely doing stuff what we were doing previously. More efficiencies is also the key and more distributed. Like if we can leverage the power of cloud in doing more things on demand is on our roadmap. And I think that is where we are all driving. >> And when you said hybrid, you're talking about connecting to your on-prem tools and data? How about cross cloud? >> We are invested in multiple cloud platform itself and we are looking forward to leveraging a technology, which is truly cloud native and we can leverage things together on that. >> And I presume you're helping with that, obviously. >> Last question for both of you. We're making an Instagram reel. Think of this as a sizzle reel, like a 32nd elevator pitch. Question, first one goes to you, Rakesh. If you had a bumper sticker, you put it on, I don't know, say a DeLorean, I hear those are coming back. What would it say about Regeneron as a technology company that's delivering therapeutics? >> It's a tough question, but I would try my best. The bumper sticker would say, discover drug more faster, more efficient. >> Perfect. Haseeb, question about Rafay. What's the bumper sticker? If you had a billboard in on Highway 101 in Redwood City about Rafay and what it's enabling organizations enterprises across the globe to achieve, what would it say? >> I'll tell you what our customers say. So our customers call us the vCenter for Kubernetes and we all know what a vCenter is. We all know why vCenter's so amazingly successful because it takes IT engineers and gives them superpowers. You can run a data center. What is the vCenter for this new world? It us. So vCenter is obviously a trademark with our friends at VMware, so that's why I'm, but our customers truly call us the vCenter for Kubernetes. And I think that's an incredible moniker because that truly codifies our roadmap. It codifies what we are selling today. >> There's nothing more powerful and potent in the voice of the customer. Thank you both for coming on. Thank you for sharing the Regeneron story. Great to have you back on, Haseeb. You need a pin for the number of times you've been on theCUBE. >> At least a gold star. >> We'll work on that. Guys, thank you. We appreciate your time. >> Haseeb: Thank you very much. >> For our guests and for Dave Vellante, I'm Lisa Martin. You're watching theCUBE, the leader in live enterprise and emerging tech coverage. (upbeat music)

(gentle music) >> Good morning, fellow cloud nerds, and welcome back to day four of AWS re:Invent. We are here in fabulous Las Vegas, Nevada. I'm joined by my cohost Paul Gillin. I'm Savannah Peterson. We're on theCUBE. Paul, how you doing? You doing well? >> We're staggering to the conclusion. >> (laughing) It's almost the end then. >> And I say that only talking about my feet. This event is still going strong. The great keynote this morning by Werner Vogels about system architecture and really teaching 70,000 people how to design systems. AWS really taking advantage of this event to educate its customer base and- >> So much education here. >> Yeah, and that was a fantastic sort of cap to the keynotes we've seen this week. >> Yeah, I'm impressed Paul, our first AWS re:Invent. I think we're doing pretty good all things considered. >> Well, we're still alive. >> And our next guest actually looks like he's been sleeping this week, which is remarkable. Please welcome Ayal to the show. Ayal, how you doing today? >> I'm good, I'm good. Thank you for having me. >> It's our pleasure. You're with Anjuna. >> Yes. >> Just in case the audience isn't familiar, what's Anjuna? >> Anjuna is an enterprise security company. We focus in the space of confidential computing. And essentially we enable people to run anything they want in any environment with complete security and privacy. >> Which is a top priority for pretty much every single person here. >> Ayal: That is true. >> Now, confidential computing, I keep hearing that term. >> Yeah, let's go there. >> Is it, I mean, is there a trademark associated with it? Is there a certification? Is the concept or is it actually a set of principles and frameworks? >> Savannah: Give us the scoop. >> Yeah, so confidential computing is essentially a set of technologies that were added to the hardware itself, to the CPU, and now to GPUs by the hardware vendors. So Intel, AMD, Arm, Nvidia AWS with their own hardware solution for this. And essentially what it allows you to do is to run workloads on top of the CPU and the GPU in a way that even if somebody gets full access to the infrastructure, you know, root access, physical access, they're not going to have any access to the data and the code running on top of it. And as you can imagine in cloud environments, this is extremely, extremely (indistinct). >> And this done through encryption? >> It involves encryption. If you go one step deeper, it involves protecting the data while it's running, data and memory, when the application is processing it. Which is always been the missing piece in terms of where you protect data. >> So I got excited when I looked at the show notes because you are serving some of the most notoriously security strict customers in the market. Can you tell us about the Israeli Ministry of Defense? >> Sure. So essentially what we do with the Israel Ministry of Defense and other customers, especially on the on the government side, one of the challenges government has is that they have to, if they want security and privacy in the cloud, they have to use something like a gov cloud. And sometimes that makes sense, but sometimes either the gov cloud is not ready because of legal battles or just it takes time to set it up. In some countries, it's just not going to make financial sense for the clouds to create a gov cloud. So what we do is we enable them to run in the commercial cloud with the security and privacy of a gov cloud. >> Was that, I can imagine, so you took them to the public cloud, correct? >> Ayal: Yes. >> Was that a challenging process? When I think of national security, I can imagine a business transformation like that would be a little nerve-wracking. >> Oh, definitely. It was a long process and they went like, "This is probably one of the best security experts on the planet." And they went extremely deep in making sure that this aligns with what they would be able to do to actually move sensitive data to the commercial cloud. Which, obviously, that the requirements are higher than anything I've ever seen from anybody else. And the fact that they were willing to publicly talk about this and be a public reference for us shows the level of confidence that they have in the underlying technology, in the security and privacy that this allows them to achieve. >> We still hear reservations, particularly from heavily regulated industries, about moving into the cloud. Concerns about security, data ownership, shared responsibility. >> Ayal: Yes. >> Are those real, are those valid? Or is the technology foundation now strong enough that they should not be worried about those things? >> Yeah, this is an excellent question, because the the shared responsibility model, is exactly sort of the core of what this is about. The shared responsibility model essentially means the cloud's, sort of by definition, the cloud is somebody else managing the infrastructure for you, right? And if somebody's managing the infrastructure for you they have full access to what you do on top of that infrastructure. That's almost the definition. And that's always been sort of one of the core security problems that was never solved. Confidential computing solves this. It means that you can use the cloud without the clouds having any access to what you do on top of their infrastructure. And that means that if the clouds get hacked, your data is safe. If an employee of the cloud decides to get access to your data, they can't. They just don't have any access. Or if the government comes to the cloud with a subpoena, the clouds can't give them access to your data, which is obviously very important for European customers and other customers outside of the US. So this is essentially what confidential computing does and it allows to break that shared responsibility model, where you as the customer get full control of your data back. >> Now, do you need the hardware foundation to do that? Or are you solving this problem in software? >> No. So we do need a hardware foundation for this which is now available in every cloud. And it's part of every server CPU that Intel ship, that AMD ship. This is part of almost every data center in AWS. But what we bring to the table at Anjuna, is every time there was a fundamental shift in computer architecture, you needed a software stack on top of it to essentially make it usable. And I think the best last example was VMware, right? But virtualization was extremely powerful technology that nobody was using until VMware built a software stack to make it super simple to virtualize anything. And to some extent that was the birth of the public cloud. We would never have a public cloud without virtualization. We're seeing the same level of shift now with confidential computing on the hardware side. And all the large players are behind this. They're all part of the confidential computing consortium that pushes this. But the challenge customers are running into, is for them to go use this they have to go refactor and rebuild every application. >> Why? >> And nobody's going to go do that. And that's exactly what we help them with. >> Yeah. >> In terms of why, as part of confidential computing, what it essentially means is that the operating system is outside the cross cycle. You, you don't want to cross the operating system because you don't want somebody with root access to have any access to your data. And what this means is every application obviously communicates with the operating system pretty often, right? To send something to the network or some, you know, save something to the file system, which means you have to re-architect your application and break it into two: a confidential piece and a piece that's communicating with the operating system and build some channel for the two sides to communicate. Nobody's going to go do that for every application. We allow you to essentially do something like Anjuna run application and it just runs in a confidential computing environment. No changes. >> Let's talk a little bit more about that. So when we're thinking about, I think we've talked a little bit about it, but I think there's a myth of control when we're talking about on-prem. Everybody thinks that things are more secure. >> Right. >> It's not the case. Tell us how enterprise security changes once when a customer has adopted Anjuna. >> Yeah, so I think you're absolutely right. I think the clouds can put a lot more effort and expertise into bringing security than the data center. But you definitely have this sort of more sense of security in your data center because you own the full stack, right? It's your people, it's your servers, it's your networks in the cloud >> Savannah: It's in your house, so to speak. Yeah. >> Exactly. And the cloud is the third party managing all that for you. And people get very concerned about that, and to some extent for a good reason. Because if a breach happens regardless of whose fault it is, the customer's going to be the one sort of left holding the bag and dealing with the aftermath of the breach. So they're right to be concerned. In terms of what we do, once you run things in confidential computing, you sort of solve the core problem of security. One of the core problems of security has always been when somebody gets access to the infrastructure especially root access to the infrastructure, it's game over. They have access to everything. And a lot of how security's been built is almost like these bandaid solutions to try to solve. Like perimeter security is how do I make sure nobody gets access to the infrastructure if they don't need to, right? All these detection solutions is once they're in the infrastructure, how do I detect that they've done something they shouldn't have? A lot of the vulnerability management is how do I make sure everything is patched? Because if somebody gets access how do I make sure they don't get root access? And then they really get access to everything. And conversation computing solves all of that. It solves the root cause, the root problem. So even if somebody gets root access, even if somebody has full access to the infrastructure, they don't have access to anything, which allows you to one, essentially move anything you want to the public cloud regardless, of the sensitivity of it, but also get rid of a lot of these other sort of bandaid solutions that you use today to try to stop people from getting that access because it doesn't matter anymore. >> Okay. So cyber security is a one and a half trillion dollar industry, growing at over 10% a year. Are you saying that if organizations were to adopt confidential computing universally that industry would not be necessary? >> No, I think a lot of it will have to change with confidential computing. Exactly, like the computer industry changed with virtualization. If you had asked when VMware just got started if the data centers are going to like, "Oh, this is going to happen," I don't think anybody could have foreseen this. But this is exactly what virtualization did. Confidential computing will change the the security industry in a massive way, but it doesn't solve every security problem. What it essentially does is it moves the perimeter from the machine itself, which used to be sort of the smallest atom, to be around the workload. And what happens in the machine doesn't matter anymore. You still need to make sure that your workload is protected. So companies that make sure that you write secure code are still going to be needed. Plus you're going to need security for things like denial of service. Because if somebody runs, you know, gets access to their infrastructure, they can stop you from running but your data is going to be protected. You're not going to need any of these data protection solutions around the box anymore. >> Let's hang out there for a second. Where do you see, I mean what an exciting time to be you, quite frankly, and congratulations on all of your success so far. Where are we going in the next two to five years? >> Yeah, I think with confidential computing the first thing that this is going to enable is essentially moving everything to the public cloud. I think the number one concern with the cloud kind of like you mentioned, is security and privacy. >> Savannah: Right. >> And this essentially eliminates that need. And that's why the clouds are so excited about this. That's why AWS talks about it. And I think Steve Schmidt, the of CISO of Amazon, used to be the CISO of AWS, talks about confidential computing as the future of data security and privacy. And there's a reason why he does that. We've seen other clouds talk about this and push this. That's why the clouds are so excited about this. But even more so again, I think over time this will allow you to essentially remove a lot of the security tools that exist there, kind of reimagine security in a better way. >> Savannah: Clean it up a little bit. Yeah. >> Exactly. And over time, I think it's going to change the world of compute even more because one of the things this allows you to do is the closer you get to the edge, the more security and privacy problems you have. >> Savannah: Right. And so many variables. >> Exactly. And it's basically out there in the wild, and people can get physical access. >> Quite literally a lot of the time, yeah. >> Exactly. And what confidential computing does, it provides that complete security and privacy regardless of even if somebody has physical access, which will allow you to move workloads much closer to the edge or to the edge itself instead of sending everything back to your backend to process things. >> We have interviewed a number of security companies here during this event, and I have to say, confidential computing has never come up. They don't talk about it. Why is that? Is there an awareness problem? >> Savannah: Are they threatened? >> Yeah, so I think the biggest, and to some extent, this is exactly like I kept bringing up VMware. Like VMware's, you can think of Salesforce, when they talked about SaaS, they sort of embedded the concept of SaaS. No other company on the planet was talking about SaaS. They created a new category and now almost everything is SaaS. VMware with virtualization, right? Nobody was using it, and now, almost everything is virtualized. Confidential computing is a new way of doing things. It's basically a kind have to shift the way of how you think about security and how you think about privacy. And this is exactly what we're seeing. I don't expect other security companies to talk about this. And to some extent, one of the things I've realized that we're almost more of an infrastructure company than a security company, because we bake security to be part of the infrastructure. But we're seeing more and more the clouds talk about this. The CPU vendors talk about this. We talk to customers more and more. Like almost every large bank I talk to now has a confidential computing strategy for 2023. This is now becoming part of the mainstream. And yeah, security companies will have to adopt or die if they don't fit into that new world that it is going to create >> This is the new world order, baby, get on the train or get left behind. >> Ayal: Exactly. >> I love it. This is a really fascinating conversation and honestly what you're doing makes so much sense. Yeah, you don't need me to validate your business model, but I will, just for the sake of that. >> Thank you. >> We have a new challenge here at re:Invent on theCUBE where we are looking for your 30 second Instagram reel hot take, thought leadership. What's the biggest theme, key takeaway from the show or experience this year for you? >> Yeah, so for me, obviously focusing on confidential computing. I think this is just going to be similar to how no network was encrypted 10 years ago and today every network is encrypted with TLS and HTTPS. And how five years ago no disc was encrypted, and today every disc is encrypted with disc encryption. The one missing piece is memory. Memory is where data is exposed now. I think within a few years all memory is going to be encrypted and it's just going to change two industries: the security industry as well as the computer industry. >> Paul: Does that include cache memory? >> What's that? >> Does that include cache memory? >> That is encrypting the RAM essentially. So everything, this is the one last place where data is not encrypted, and that's exactly what confidential computing brings to the table. >> Are there any performance concerns with encrypting memory? >> That's a phenomenal question. One of the really nice things about confidential computing is that the heavy lifting is done by the hardware vendors themselves as part of the hardware and not part of the critical path in the CPU. It's very similar to the TLS acceleration cards, if you remember those, which allows us to be extremely, extremely performant. And that's why I think this is going to be for everything. Because every time we had a security solution that had no performance impact and was super simple to use it just became the default, because why wouldn't you use it for everything? >> Ayal, this has been absolutely fascinating. We could talk to you all day. Unfortunately, we're out of time. But really thank you so much for coming on the show. Now, we feel more confident in terms of our confidential computing knowledge and definitely learned a lot. Thank all of you for tuning in to our fantastic four day live stream at AWS re:Invent here in Sin City with Paul Gillin. I'm Savannah Peterson. You're watching theCUBE, the leader in high tech coverage. (gentle music)

>>Good Morning Cloud community and welcome back to Fabulous Las Vegas, Nevada, where we are at AWS Reinvent. It is day four here on the Cube. I'm Savannah Peterson with Lisa Martin. You are looking fantastic. Day four, we've done 45 interviews. How are you feeling? Oh, >>Great. I can't believe it's day four. The cube will be producing over 100 interviews. >>Impressive. Right >>On this stage where there are two sets, and of course we have the set upstairs as well. It's amazing how much content we've created, how many great conversations we've had, right? And the excitement around AWS and the, and the community. >>Yeah. I feel like we've learned so much together. Love co-hosting with you, and so excited for our first conversation this morning with Wira. Welcome, Tim and Kashmira, welcome to the show. How you doing? You both look great for day four. Thank >>You. Yeah, we're doing good. Great. We're doing good. Ready to go. Day four, let's go. >>That's the spirit. That's exactly the energy we need here on the cube. So just in case someone in the audience is not familiar, tell us about Wipro. >>So Wipro is a global consulting company and we help transform our customers and their businesses. >>Transformation's been a super hot topic here at the show, quite frankly a big priority, especially with cost cutting and everything else that's going on. How, how do you do that? How do you help customers do that? Has >>Me run? So we, we, so we have our A strategy, which we call our full stride cloud strategy. So particularly from a cloud perspective here, obviously with aws, we have end to end client services. So from high end strategic consulting through customer journeys, technology implementation, all the way through to our managed services. So we help customers with the end to end journey, particularly as here we're talking about cloud, but also business transformation as well. And we have, you know, a whole host of technologies. So about a few years ago we made an announcement around a billion investment in cloud casual and that Yeah, absolutely. A cool billion and just a cool billion. Yeah. And that pocket >>Change. Exactly. >>Right. And that investment. Over the last few years, we've acquired a number of really exciting companies like Capco, which is a consulting company in the financial services space. We've acquired design companies, a company called Design it, looking at customer journeys and user experience, and then also technology companies called Rising, which looks after the whole SAP space. So we've kind of got the end to end solutions and technologies. And then we also invest in what we call Wipro Ventures. These are really innovative, exciting startups. We invest in those companies to really drive transformation. And the final thing that really brings the whole thing together is that we have decades of experience in engineering. That's kind of the heart of where we come from. So that experience all of that together really helps our clients to transform their business. And particularly as we're talking about cloud helps us to transform the cloud. Now what we are really hoping is that we can help our clients become what we call intelligent enterprises, and we are focusing more and more on customer outcomes and really helping them with those business outcomes. >>Yeah. It doesn't matter what we do if there isn't that business outcome. >>Yeah. That's what it's all about. I'm curious, Tim, to get your, as the America's cloud leader, one of the things that, that our boss, John Furrier, who is the co CEO of the Cube, was able to do every year, he gets to sit down with the head of AWS for a preview of reinvent, right? He's been doing this for 10 years now, and one of the things that Adam Olitsky said to him, this is something about a week or so ago, is CIOs and CEOs are not coming to me to talk about technology. They wanna talk about transformation. Sure, yeah. Business transformation, not an amorphous topic of digital transformation. Are you hearing the same? >>Absolutely. Right. So I think this is my seventh reinvent, right? And I think six, seven years ago, the majority of the conversations you would've had are about technology, right? Great technology, but kind of technology for it to solve it problems. You know, how do I, how do I migrate, how do I modernize, how do I use data? How do I make all this stuff happen? Right now it's about how do I drive new business opportunities, new revenue streams, how do I drive more efficiencies through the manufacturing 2.0 or what have you, right? Yeah. One really good example, like take, take medical devices, right? So like a connected defibrillator, right? Anytime you're building a, what they call an IOT device or a connected device, right? You have four competing an edge device in the space, an edge device, yeah. Right? You have four competing elements, right? >>You've got form factor, power, connectivity and intelligence, and all those things compete, right? I can have all the power if I want, if I can have something as biggest as a tape, right? You know, I can have satellite if I, it gets right off if I can plug it in somewhere. But when you're talking about an implanted defibrillator, right? That, that all competes. So you have an engineering problem, an engineering challenge that's based on a device, right? And then it's gotta connect to the cloud, right? So you have a lot of AWS services, I ot, core device shadowing, all sorts of things. That individual patient then, so, so there's the engineering challenge of, okay, I wanna build a device, I gotta prototype it, I gotta design it, I gotta build it at scale, I have to support it. Then you have a patient, right? Which is the end goal of the business is the patient care. >>They have a console at home that connects to that defibrillator via Bluetooth, let's say. And that's where you get your device updates, just like your laptop, right? You know, now push from where updates to your chest. Yes. Device, ot. It's like, okay, I'm just gonna do this every Thursday, right? So now you've very quickly move to a patient experience and that patient experience will very greatly, right? You know, based on age and exposure to technology and all other sorts of things, how diligent they are. Do they do the update every week Right. To their primary care provider? And then what we're, we're also hearing, okay, so like Kashmira mentioned, we, we can, we can have that design discussion, right? Yeah. We can have the engineering device discussion with our device, device lab. Then we can have our, you know, what's the, what's the patient experience, but then broader, what's the patient experience as they move, as we all do through a healthcare, that's a healthcare network, it's a provider network, it's a series of hospitals and providers. So what does that big picture and ecosystem look like? And it's, you haven't heard me mention server or data center or any of that stuff? No. Right? This is >>The most human anecdote we've had on >>Show. Fantastic. This >>Sidebar. Okay. I mean it great. Keep going. It's wonderful. And it's, and it's, it's fascinating because none of this happens or is possible without cloud and, and the type of services that AWS is, is releasing out into their, into their, into their, into the world, right? But it very quickly moves from technology to human. It very quickly moves from individual to ecosystem to to, to partner and culture and, you know, society, right? So, so these are the types of conversations we're having. I mean, this is kind of stuff that gets me outta bed in the morning. So it's great, right? It's great that, I love that. It's great that we've moved, we moved into that space. >>Well, it's, I mean the human element is so important. Every, every company has to be a data company. Hospitals, absolutely. Grocery stores, retailers, you name it. And what we're seeing is this, and we talk about data democratization all the time. Well, another thing that Adam Slosky told John Furrier is that the role of, of data analysts is gonna, is going to change, maybe go away or the, or the term because data needs to be everywhere. The doctors need the data. Absolutely. Every person in the organization needs to be able to analyze data to deliver outcomes. >>Yeah, absolutely. Yeah. And it's fundamental part of our strategies. And when we are looking at, you know, data is everywhere, you need to really think about how do you align to it. But we are looking at it from an industry perspective. So when we're looking at solutions for our clients, we're looking at how do we deliver data solutions for our bank? How do we deliver data solutions in healthcare? How do we deliver data solutions in various different industry? So >>Many different verticals that you're >>Touching. Yeah, all the different verticals. So that's, you know, we have like a four point strategy industry is the first one. So we have been really worked with a lot of clients around migrations and modernizations. What we're moving to now is really this industry play. So this week we've spent a lot of time with our energy and utilities clients and the AWS practice at banking and financial services, which is a very significant part of our business. Also cloud automotive. This is a really, really, you know, the fascinat, this is so exciting, but the fundamental part of that, it's very, is data, right? It's all hits on data. So it was really great to hear some of the announcements this week around the data piece announcements just for me, that's really exciting. Yeah. A couple of other things that when we're thinking about our overall focus and strategy is, you know, looking at business transformation is, as you mentioned, is the ecosystem. >>So how do we bring all this together? And it's really, we see ourselves as an ecosystem orchestrator, and we are really here to look at leveraging our relationship with the best partners. We've actually met 17 partners here this week and had client sessions with them. And that's, you know, working with the license of Snowflake and Data Break in the, in the data space, our long term partners like sap, ibm, VMware, and you know, and new partners like Con. And we are looking at how do we bring the best of this ecosystem orchestration so that to support those client business outcome. Sure. And then one final sort of pillar, sorry, is talent, right? So the biggest thing that everyone is thinking about and we all think about every single day is talent. So we've done two really exciting things this year. One has been around our own talent. >>So we've really looked at our own internal influences, people who are speaking to our clients every single day. Not so much the technology people, but the client people speaking to the client. And we've really raised the level of cloud fluency with these people so that they can really start to have that discussion. You know, and our clients, you know, they know this technology way better than us, you most of the time. And then secondly, we actually announced last week and, and you initiative, which we are calling skill skills, which is very well known to our AWS clients because AWS provide this skill, skill concept to their clients. But we are the first partner to do the skills. Skills Yeah. From a partnering perspective. And this is really gonna transform. So it's not just about training and enablement, it's actually about creating a journey for you to, you know, do your best work. >>Tim, what, how do you define cloud fluency? We were actually talking about it yesterday. Sure, sure. Yeah. And, and really kind of bringing that across an organization, but what, what does it take for an individual who may not be a technologist to become cloud fluent? >>Sure. Well, there's a couple, there's a couple angles to that, right? One is, one is how do you create cloud fluency for people who might already be technical, right? And that's, and that's, you know, I've spent over a decade with, you know, boutique disruptive consulting companies who live and die by whether they can attract and retain talent. And there's sort of four elements to that. It's, can you, can you show people they're gonna work on interesting stuff, right? Are they gonna be excited about what they do? Can you show that they're gonna expand their skill sets? Yep. Can you show them a career path? And you can, can you surround all of that with a supportive engineering first culture, right? That, you know, rewards for outcomes, but also creates this sort of community, right? Yeah. That's, that's one thing that sort of, you know, that that will be a natural entropy, people will be attracted to that. On the other side of it, as you create fluency, you kind of do it with the conversation that I just had, like around something like medical devices or something like the cloud car. When you just say, look, you start with something everybody already knows, right? We all know what patient care is like. We all know what autonomous vehicles is kind of like, right? And you work backwards from that and say, now here's, here's how all the pieces stitch together to create this end outcome for, for us and for our customers, for >>The, you know, I'm speaking my language, Tim. So I run a boutique consultancy, my talent go, I live and die on that. Quite frankly. It's everything, right? And, and it's so, wow, it's so important. I mean, in eliminating that churn at scale, how big is your team? Now I'm just thinking about this cause I'm sure you're, your talent retention has to be a challenge as well. Sure. >>So, so we have 25,000 woo professionals on aws trained on, you know, tech cloud technologies globally. Impressive. Yeah. And then we have, in terms of our go to market team, we've got 50 strong as well. Well, so we, these are people who are live and breathe aws, right? And speaking and working with the cloud. >>Let's hang out there a little bit. Tell us a little bit more about the partnership with aws. Cast me, >>Let's go to you. Yeah, so our partnership is, you know, it's 11 years strong. It's been an and a really, really great partnership's. >>How longs >>That's true. Yeah. >>No, is you, were, you're, you're like day ones there. That's Yeah. Real legacy it. >>Awesome. You know, this year excitingly, we actually won the APJ partner of dsi, partner of the year. Congratulations. >>Really casual. >>Yeah. Just like >>Married the lead there. Congratulations. >>Yeah. So that really is testament to how we're really knuckling down and working proactively to, to really support our clients. And, you know, the, the partnership is a really, really strong partnership. It's been there for many years with, you know, great solutions and engagement and many of the things I talked about in terms of our industry plays that we're driving. We've got a whole new set of competencies that we've launched, like a new energy competency this year. So we're focusing on industry and then also security, two new security competencies. And you know, what's really exciting on the security side, you saw the announcements around the security data lake, but we've been working over the last few months with Gary, me and his team, and actually are one of the first partners that are driving that initiative. So we're really proud to be part of that. So yeah. You know, and then there's a client engagement as well. So we have a dedicated team at AWS that works with our dedicated team. So we're supporting the client's needs day to day. >>Are you as customer obsessed as AWS is? Absolutely. I >>Figured so. Absolutely. Everything's about the customer. Nothing happens about >>That. Right? Well, you talked about outcomes, it's all about outcomes. >>Well, and I mean, quite literally going for the heart with the defibrillator analogy. No, I mean, you tell the customers at the heart of what you're doing, part of everything. Can't resist a good pun there. So as I warned you, we have a little challenge for you here on the cube. We're looking for your hot take your 32nd sound bite thought leadership. What's the biggest takeaway from the event and moving forward, looking into 2023? Tim, you're giving me that eye contact. I'm going to you first, >>Right? Okay, sure. Love to. So I don't know how hot a take it is, but I kind of see this transition as cloud, as the operating system, right? So, so let's take the, the what we call the cloud car project. We have the connected car. You know, a car is a durable good, and we all know, or there's been a lot of talk about the electric cars or the autonomous vehicles being like more of a computer than a vehicle, right? But a vehicle's supposed to last 10, 15, 20 years. Our laptops don't last 10, 15, 20 years. So there's this cell, there's this major challenge to say, how can I, how can I change the way the technology operates within the vehicle? So you see this transition to where instead of it being a car that, that has a computer, then it, the, the, the latest transition is to more of a computer that, that operates like a car. >>This new vehicle that's going to emerge is gonna be much like a cell phone, right? Where it, it traverses the world and depending on where it is, different things might be available, right? And, and how and how, how the actual technology, the software that is running will, will be, you know, sort of amorphous and move between different resources in the network on the car, everywhere else. And so that's a really different way of thinking about if, if we think about how quickly the Overton window, like what becomes normal, it changes over time. We're really getting to like a very fast movement of that into something like this vehicle's still gonna be something that we don't even maybe think of as a car anymore. Just the way that an iPhone isn't what we used to think of a phone at our >>Pocket computer. Yeah. What's in the mirror part? Great. >>That's kind my >>Take. Awesome. Right? Catch me man. >>Yeah, and I mean I, if I was to suggest that, you know, summarize it by simply, for me it's really focusing on industry solutions, delivering client outcomes, fundamentally underpinned by data security and sustainability. You know, I think Nailed it. >>Yeah. Knock it outta the park. Perfect little sound bite. That was fantastic. You both were a wonderful start to the day. Thank you so much for being here. Tim and Kashmir, absolute >>Pleasure. >>This is, this is a joy. We're gonna keep learning here on the cube. And thank all of you for tuning in to our fabulous AWS reinvent coverage here from Sin City with Lisa Martin. I'm Savannah Peterson and you are watching The Cube, the leader in high tech coverage.

(soft music) >> Welcome back to Sin City, guys and girls we're glad you're with us. You've been watching theCUBE all week, we know that. This is theCUBE's live coverage of AWS re:Invent 22, from the Venetian Expo Center where there are tens of thousands of people, and this event if you know it, covers the entire strip. There are over 55,000 people here, hundreds of thousands online. Dave, this has been a fantastic show. It is clear everyone's back. We're hearing phenomenal stories from AWS and it's ecosystem. We got a great customer story coming up next, featured on the main stage. >> Yeah, I mean, you know, post pandemic, you start to think about, okay, how are things changing? And one of the things that we heard from Adam Selipsky, was, we're going beyond digital transformation into business transformation. Okay. That can mean a lot of things to a lot of people. I have a sense of what it means. And I think this next interview really talks to business transformation beyond digital transformation, beyond the IT. >> Excellent. We've got two guests. One of them is an alumni, Scott Mullins joins us, GM, AWS Worldwide Financial Services, and Brad Peterson is here, the EVP, CIO and CTO of NASDAQ. Welcome guys. Great to have you. >> Hey guys. >> Hey guys. Thanks for having us. >> Yeah >> Brad, talk a little bit, there was an announcement with NASDAQ and AWS last year, a year ago, about how they're partnering to transform capital markets. It was a highlight of last year. Remind us what you talked about and what's gone on since then. >> Yeah, so, we are very excited. I work with Adena Friedman, she's my boss, CEO of NASDAQ, and she was on stage with Adam for his first Keynote as CEO of AWS. And we made the commitment that we were going to move our markets to the Cloud. And we've been a long time customer of AWS and everyone said, you know the last piece, the last frontier to be moved was the actual matching where all the messages, the quotes get matched together to become confirmed orders. So that was what we committed to less than a year ago. And we said we were going to move one of our options markets. In the US, we have six of them. And options markets are the most challenging, they're the most high volume and high performance. So we said, let's start with something really challenging and prove we can do it together with AWS. So we committed to that. >> And? Results so far? >> So, I can sit here and say that November 7th so we are live, we're in production and the MRX Exchange is called Mercury, so we shorten it for MRX, we like acronyms in technology. And so, we started with a phased launch of symbols, so you kind of allow yourself to make sure you have all the functionality working then you add some volume on it, and we are going to complete the conversion on Monday. So we are all good so far. And I have some results I can share, but maybe Scott, if you want to talk about why we did that together. >> Yeah. >> And what we've done together over many years. >> Right. You know, Brian, I think it's a natural extension of our relationship, right? You know, you look at the 12 year relationship that AWS and NASDAQ have had together, it's just the next step, in the way that we're going to help the industry transform itself. And so not just NASDAQ's business transformation for itself, but really a blueprint and a template for the entire capital markets industry. And so many times people will ask me, who's using Cloud well? Who's doing well in the Cloud? And NASDAQ is an easy example to point to, of somebody who's truly taking advantage of these capabilities because the Cloud isn't a place, it's a set of capabilities. And so, this is a shining example of how to use these capabilities to actually deliver real business benefit, not just to to your organization, but I think the really exciting part is the market technology piece of how you're serving other exchanges. >> So last year before re:Invent, we said, and it's obvious within the tech ecosystem, that technology companies are building on top of the Cloud. We said, the big trend that we see in the 2020s is that, you know, consumers of IT, historically, your customers are going to start taking their stacks, their software, their data, their services and sassifying, putting it on the Cloud and delivering new services to customers. So when we saw Adena on stage last year, we called it by the way, we called it Super Cloud. >> Yeah. >> Okay. Some people liked the term but I love it. And so yeah, Super Cloud. So when we saw Adena on stage, we said that's a great example. We've seen Capital One doing some similar things, we've had some conversations with US West, it's happening, right? So talk about how you actually do that. I mean, because you've got a lot, you've got a big on-premises stay, are you connecting to that? Is it all in the Cloud? Paint a picture of what the architecture looks like? >> Yeah. And there's, so you started with the business transformation, so I like that. >> Yeah. >> And the Super Cloud designation, what we are is, we own and operate exchanges in the United States and in Europe and in Canada. So we have our own markets that we're looking at modernizing. So we look at this, as a modernization of the capital market infrastructure, but we happen to be the leading technology provider for other markets around the world. So you either build your own or you source from us. And we're by far the leading provider. So a lot of our customers said, how about if you go first? It's kind of like Mikey, you know, give it to Mikey, let him try it. >> See if Mikey likes it. >> Yeah. >> Penguin off the iceberg thing. >> Yeah. And so what we did is we said, to make this easy for our customers, so you want to ask your customers, you want to figure out how you can do it so that you don't disrupt their business. So we took the Edge Compute that was announced a few years ago, Amazon Outposts, and we were one of their early customers. So we started immediately to innovate with, jointly innovate with Amazon. And we said, this looks interesting for us. So we extended the region into our Carteret data center in Northern New Jersey, which gave us all the services that we know and love from Amazon. So our technical operations team has the same tools and services but then, we're able to connect because in the markets what we're doing is we need to connect fairly. So we need to ensure that you still have that fairness element. So by bringing it into our building and extending the Edge Compute platform, the AWS Outpost into Carteret, that allowed us to also talk very succinctly with our regulators. It's a familiar territory, it's all buttoned up. And that simplified the conversion conversation with the regulators. It simplified it with our customers. And then it was up to us to then deliver time and performance >> Because you had alternatives. You could have taken a more mature kind of on-prem legacy stack, figured out how to bolt that in, you know, less cloudy. So why did you choose Outposts? I am curious. >> Well, Outposts looked like when it was announced, that it was really about extending territory, so we had our customers in mind, our global customers, and they don't always have an AWS region in country. So a lot of you think about a regulator, they're going to say, well where is this region located? So finally we saw this ability to grow the Cloud geographically. And of course we're in Sweden, so we we work with the AWS region in Stockholm, but not every country has a region yet. >> And we're working as fast as we can. - Yes, you are. >> Building in every single location around the planet. >> You're doing a good job. >> So, we saw it as an investment that Amazon had to grow the geographic footprint and we have customers in many smaller countries that don't have a region today. So maybe talk a little bit about what you guys had in mind and it's a multi-industry trend that the Edge Compute has four or five industries that you can say, this really makes a lot of sense to extend the Cloud. >> And David, you said it earlier, there's a trend of ecosystems that are coming onto the Cloud. This is our opportunity to bring the Cloud to an ecosystem, to an existing ecosystem. And if you think about NASDAQ's data center in Carteret, there's an ecosystem of NASDAQ's clients there that are there to be with NASDAQ. And so, it was actually much easier for us as we worked together over a really a four year period, thinking about this and how to make this technological transition, to actually bring the capabilities to that ecosystem, rather than trying to bring the ecosystem to AWS in one of our public regions. And so, that's been our philosophy with Outpost all along. It's actually extending our capabilities that our customers know and love into any environment that they need to be able to use that in. And so to Brad's point about servicing other markets in different countries around the world, it actually gives us that ability to do that very quickly, very nimbly and very succinctly and successfully. >> Did you guys write a working backwards document for this initiative? >> We did. >> Yeah, we actually did. So to be, this is one of the fully exercised. We have a couple of... So by the way, Scott used to work at NASDAQ and we have a number of people who have gone from NASDAQ data to AWS, and from AWS to NASDAQ. So we have adopted, that's one of the things that we think is an effective way to really clarify what you're trying to accomplish with a project. So I know you're a little bit kidding on that, but we did. >> No, I was close. Because I want to go to the like, where are we in the milestone? And take us through kind of what we can expect going forward now that we've worked backwards. >> Yep, we did. >> We did. And look, I think from a milestone perspective, as you heard Brad say, we're very excited that we've stood up MRX in production. Having worked at NASDAQ myself, when you make a change and when you stand up a market that's always a moment where you're working with your community, with your clients and you've got a market-wide call that you're working and you're wanting to make sure that everything goes smoothly. And so, when that call went smoothly and that transition went smoothly I know you were very happy, and in AWS, we were also very happy as well that we hit that milestone within the timeframe that Adena set. And that was very important I know to you. >> Yeah. >> And for us as well. >> Yeah. And our commitment, so the time base of this one was by the end of 2022. So November 7th, checked. We got that one done. >> That's awesome. >> The other one is we said, we wanted the performance to be as good or better than our current platform that we have. And we were putting a new version of our derivative or options software onto this platform. We had confidence because we already rolled it to one market in the US then we rolled it earlier this year and that was last year. And we rolled it to our nordic derivatives market. And we saw really good customer feedback. So we had confidence in our software was going to run. Now we had to marry that up with the Outpost platform and we said we really want to achieve as good or better performance and we achieved better performance, so that's noticeable by our customers. And that one was the biggest question. I think our customers understand when we set a date, we test them with them. We have our national test facility that they can test in. But really the big question was how is it going to perform? And that was, I think one of the biggest proof points that we're really proud about, jointly together. And it took both, it took both of us to really innovate and get the platform right, and we did a number of iterations. We're never done. >> Right. >> But we have a final result that says it is better. >> Well, congratulations. - Thank you. >> It sounds like you guys have done a tremendous job. What can we expect in 2023? From NASDAQ and AWS? Any little nuggets you can share? >> Well, we just came from the partner, the partner Keynote with Adam and Ruba and we had another colleague on stage, so Nick Ciubotariu, so he is actually someone who brought digital assets and cryptocurrencies onto the Venmo, PayPal platform. He joined NASDAQ about a year ago and we announced that in our marketplace, the Amazon marketplace, we are going to offer digital custody, digital assets custody solution. So that is certainly going to be something we're excited about in 2023. >> I know we got to go, but I love this story because it fits so great at the Super cloud but we've learned so much from Amazon over the years. Two pieces of teams, we talked about working backwards, customer obsession, but this is a story of NASDAQ pointing its internal capabilities externally. We're already on that journey and then, bringing that to the Cloud. Very powerful story. I wonder what's next in this, because we learn a lot and we, it's like the NFL, we copy it. I think about product market fit. You think about scientific, you know, go to market and seeing that applied to the financial services industry and obviously other industries, it's really exciting to see. So congratulations. >> No, thank you. And look, I think it's an example of Invent and Simplify, that's another Amazon principle. And this is, I think a great example of inventing on behalf of an industry and then continually working to simplify the way that the industry works with all of us. >> Last question and we've got only 30 seconds left. Brad, I'm going to direct it to you. If you had the opportunity to take over the NASDAQ sign in Times Square and say a phrase that summarizes what NASDAQ and AWS are doing together, what would it say? >> Oh, and I think I'm going to put that up on Monday. So we're going to close the market together and it's going to say, "Modernizing the capital market's infrastructure together." >> Very cool. >> Excellent. Drop the mic. Guys, this was fantastic. Thank you so much for joining us. We appreciate you joining us on the show, sharing your insights and what NASDAQ and AWS are doing. We're going to have to keep watching this. You're going to have to come back next year. >> All right. >> For our guests and for Dave Vellante, I'm Lisa Martin. You're watching theCUBE, the leader in live enterprise and emerging tech coverage. (soft music)

>>Hey guys and girls, welcome back to The Cube's Live coverage of AWS Reinvent 22 from Sin City. We've been here, this is our third day of coverage. We started Monday night first. Full day of the show was yesterday. Big news yesterday. Big news. Today we're hearing north of 50,000 people, and I'm hearing hundreds of thousands online. We've been having great conversations with AWS folks in the ecosystem, AWS customers, partners, ISVs, you name it. We're pleased to welcome back one of our alumni to the program, talking about partner ecosystem. Dominic Rav Vida joins us, the VP of Developer relations at single store. It's so great to have you on the program. Dominic. Thanks for coming. >>Thanks. Great. Great to see you >>Again. Great to see you too. We go way back. >>We do, yeah. >>So let's talk about reinvent 22. This is the 11th reinvent. Yeah. What are some of the things that you've heard this week that are exciting that are newsworthy from single stores perspective? >>I think in particular what we heard AWS announce on the zero ETL between Aurora and Redshift, I think it's, it's significant in that AWS has provided lots of services for building blocks for applications for a long time. And that's a great amount of flexibility for developers. But there are cases where, you know, it's a common thing to need to move data from transactional systems to analytics systems and making that easy with zero etl, I think it's a significant thing and in general we see in the market and especially in the data management market in the cloud, a unification of different types of workloads. So I think that's a step in the right direction for aws. And I think for the market as a whole, why it's significant for single store is, that's our specialty in particular, is to unify transactions and analytics for realtime applications and analytics. When you've got customer facing analytic applications and you need low latency data from realtime streaming data sources and you've gotta crunch and compute that. Those are diverse types of workloads over document transactional workloads as well as, you know, analytical workloads of various shapes and the data types could be diverse from geospatial time series. And then you've gotta serve that because we're all living in this digital service first world and you need that relevant, consistent, fresh data. And so that unification is what we think is like the big thing in data right >>Now. So validation for single store, >>It does feel like that. I mean, I'd say in the recent like six months, you've seen announcements from Google with Alloy db basically adding the complement to their workload types. You see it with Snowflake adding the complement to their traditional analytical workload site. You see it with Mongo and others. And yeah, we do feel it was validation cuz at single store we completed the functionality for what we call universal storage, which is, is the industry's first third type of storage after row store and column store, single store dbs, universal storage, unifies those. So on a single copy of data you can form these diverse workloads. And that was completed three years ago. So we sort of see like, you know, we're onto something >>Here. Welcome to the game guys. >>That's right. >>What's the value in that universal storage for customers, whether it's a healthcare organization, a financial institution, what's the value in it in those business outcomes that you guys are really helping to fuel? >>I think in short, if there were like a, a bumper sticker for that message, it's like, are you ready for the next interaction? The next interaction with your customer, the next interaction with your supply chain partner, the next interaction with your internal stakeholders, your operational managers being ready for that interaction means you've gotta have the historical data at the ready, accessible, efficiently accessible, and and, and queryable along with the most recent fresh data. And that's the context that's expected and be able to serve that instantaneously. So being ready for that next interaction is what single store helps companies do. >>Talk about single store helping customers. You know, every company these days has to be a data company. I always think, whether it's my grocery store that has all my information and helps keep me fed or a gas station or a car dealer or my bank. And we've also here, one of the things that John Furrier got to do, and he does this every year before aws, he gets to sit down with the CEO and gets really kind of a preview of what's gonna happen at at the show, right? And Adams Lisky said to him some interesting very poignant things. One is that that data, we talk about data democratization, but he says the role of the data analyst is gonna go away. Or that maybe that term in, in that every person within an organization, whether you're marketing, sales, ops, finance, is going to be analyzing data for their jobs to become data driven. Right? How does single store help customers really become data companies, especially powering data intensive apps like I know you do. >>Yeah, that's, there's a lot of talk about that and, and I think there's a lot of work that's been done with companies to make that easier to analyze data in all these different job functions. While we do that, it's not really our starting point because, and our starting point is like operationalizing that analytics as part of the business. So you can think of it in terms of database terms. Like is it batch analysis? Batch analytics after the fact, what happened last week? What happened last month? That's a lot of what those data teams are doing and those analysts are doing. What single store focuses more is in putting those insights into action for the business operations, which typically is more on the application side, it's the API side, you might call it a data product. If you're monetizing your data and you're transacting with that providing as an api, or you're delivering it as software as a service, and you're providing an end-to-end function for, you know, our marketing marketer, then we help power those kinds of real time data applications that have the interactivity and have that customer touchpoint or that partner touchpoint. So you can say we sort of, we put the data in action in that way. >>And that's the most, one of the most important things is putting data in action. If it's, it can be gold, it can be whatever you wanna call it, but if you can't actually put it into action, act on insights in real time, right? The value goes way down or there's liability, >>Right? And I think you have to do that with privacy in mind as well, right? And so you have to take control of that data and use it for your business strategy And the way that you can do that, there's technology like single store makes that possible in ways that weren't possible before. And I'll give you an example. So we have a, a customer named Fathom Analytics. They provide web analytics for marketers, right? So if you're in marketing, you understand this use case. Any demand gen marketer knows that they want to see what the traffic that hits their site is. What are the page views, what are the click streams, what are the sequences? Have these visitors to my website hit certain goals? So the big name in that for years of course has been Google Analytics and that's a free service. And you interact with that and you can see how your website's performing. >>So what Fathom does is a privacy first alternative to Google Analytics. And when you think about, well, how is that possible that they, and as a paid service, it's as software, as a service, how, first of all, how can you keep up with that real time deluge of clickstream data at the rate that Google Analytics can do it? That's the technical problem. But also at the data layer, how could you keep up with Google has, you know, in terms of databases And Fathom's answer to that is to use single store. Their, their prior architecture had four different types of database technologies under the hood. They were using Redis to have fast read time cash. They were using MySEQ database as the application database they were using. They were looking at last search to do full tech search. And they were using DynamoDB as part of a another kind of fast look up fast cash. They replaced all four of those with single store. And, and again, what they're doing is like sort of battling defacto giant in Google Analytics and having a great success at doing that for posting tens of thousands of websites. Some big names that you've heard of as well. >>I can imagine that's a big reduction from four to one, four x reduction in databases. The complexities that go away, the simplification that happens, I can imagine is quite huge for them. >>And we've done a study, an independent study with Giga Home Research. We published this back in June looking at total cost of ownership with benchmarks and the relevant benchmarks for transactions and analytics and databases are tpcc for transactions, TPC H for analytics, TPC DS for analytics. And we did a TCO study using those benchmark datas on a combination of transactional and analytical databases together and saw some pretty big improvements. 60% improvement over Myse Snowflake, for >>Instance. Awesome. Big business outcomes. We only have a few seconds left, so you've already given me a bumper sticker. Yeah. And I know I live in Silicon Valley, I've seen those billboards. I know single store has done some cheeky billboard marketing campaigns. But if you had a new billboard to create from your perspective about single store, what does it say? >>I, I think it's that, are you, are you ready for the next interaction? Because business is won and lost in every moment, in every location, in every digital moment passing by. And if you're not ready to, to interact and transact rather your systems on your behalf, then you're behind the curve. It's easy to be displaced people swipe left and pick your competitor. So I think that's the next bumper sticker. I may, I would say our, my favorite billboard so far of what we've run is cover your SaaS, which is what is how, what is the data layer to, to manage the next level of SaaS applications, the next generation. And we think single store is a big part >>Of that. Cover your SaaS. Love it. Dominic, thank you so much for joining me, giving us an update on single store from your perspective, what's going on there, kind of really where you are in the market. We appreciate that. We'll have to >>Have you back. Thank you. Glad to >>Be here. All right. For Dominic rta, I'm Lisa Martin. You're watching The Cube, the leader in live, emerging and enterprise tech coverage.

(soft electronic music) >> Good afternoon guys and gals. Welcome back to theCube's Live coverage of AWS re:Invent 2022. We've been in Sin City since Monday night, giving you a load of content. I'm sure you've been watching the whole time, so you already know. Lisa Martin here with John Furrier. John, we love having these conversations at AWS re:Invent. So many different topics of conversation. We also love talking to AWS's partner ecosystem. There's so much emphasis on it, so much growth and innovation. >> Yeah, and the thing is we got two great leaders from a very popular company that's doing very well. Security, security's a big part of the story. Data and security. Taking up all the keynote time, you're hearing a lot of it. This company's a company we've been following from the beginning. Doing really good stuff in open source, cloud native, security, shifting-left. Snyk's just a great company. With the CTO and the head of the product organization, these guys have the keys to the kingdom in security. We're going to have a great conversation. >> Yeah, we are. Both from Snyk, Manoj Nair joins us, rejoins us, for your, I believe, 11th visit. Chief Product Officer of Snyk. Adi Sharabani, Chief Technology Officer. Welcome guys. Great to have you. >> Yeah, thank you. >> Great to be back. >> So what's going on at Snyk? I know we get to talk to you often, but Manoj, give us the lowdown on what are some of the things that are new since we last connected with Snyk. >> A lot of innovation going on. We just had a major launch last month and you know when we talked to our customers three big themes are happening in parallel. One is the shift to going from traditional development to, really, DevOps, but we need to make that DevSecOps and Snyk was ahead of, that was the genesis of Snyk, but we're still, you know, maybe 15, 20% of organizations have realized that. So that one big theme. Supply chain security, top of mind for everyone. And then really, cloud and, you know, how do you really take advantage of cloud. Cloud is code. So our innovation map to those three big themes, we have done a lot in terms of that shift-left. And Adi will talk about, kind of, some of our original, like, you know, thinking behind that. But we flipped the security paradigm on its head. Was to make sure developers loved what they were, you know, experiencing with Snyk. And oh, by the way, they're fixing security issues. The second one, supply chain. So you know, SBOMs and everyone hears about this and executive orders, what do you do? Who does what with that? So we launched a few things in terms of simplifying that. You can go to our website and, you know, just upload your SBOM. It'll tell you using the best security intelligence data. In fact, the same data is used by AWS inside their products, inside Inspector. So we use that data from Snyk's intelligence to light up and tell you what vulnerabilities do your third party code have. Even things that you might not be scanning. And then the last one is really code to cloud. Cloud is code. So we have brought the ability to monitor your cloud environments all the way into your platform and the security engineering teams, rather than later on and after the fact. Those are some of the big ones that we're working on. >> Lisa: Lots going on. >> Yeah. >> Lisa: Wow. >> Lots going on there. I mean, SBOMs, Software Bill of Materials. I mean, who would've thought in the developer community, going back a decade, that we'd be talking about bill of materials, open source becomes so popular. You guys are cloud native. Developer productivity's a hot trend. Not much going on here, talking about developer productivity. Maybe Werner, keynote tomorrow will talk about it. Software supply chain, huge security risk. You guys are in the front lines. I want to understand, if you can share, why is Snyk successful? Everyone is hearing about you guys. Your business is doing great. What's the secret sauce of your success? Why are you guys so successful? >> I think that, you know, I've been doing application security for more than two decades now and in the past we always saw the potential associated with transferring, shifting-left in a sense, before the term, right? Taking those security solutions out of the hands of the security people and putting it in the hands of developers. It's speeds up the process. It's very, very clear to anyone. The problem was that we always looked at it the wrong way. We did shift-left, and shift-left is not enough because in my terminology shift-left, meaning let's take those security solution put it earlier in the cycle, but that's not enough because the developer is not speaking those terms. The developer is not a security persona. The security persona is thinking in terms of risk. What are the risks that a specific issue creates? The developer is thinking in terms of the application. What would be the impact on application of a change I would might make into it. And so the root cause of Snyk success, in my opinion, is the fact that from the get-go we scratch that, we build a solution for the developer that is based on how the workflows of the developer, whether it's the ID, whether it's the change management, the pull request. Whether it's integration with the Gits and so on. And whether it's with integration with the cloud and the interaction with the cloud providers. And doing that properly, addressing the developers how they want to context, to get, with the context they want to get as part of the issues, with the workflows they want to get. That's kind of the secret sauce, in a sense. And very easy maybe to say, but very, very hard to implement properly. >> This is huge. I want to unpack that. I want to just, great call out, great description. This is huge. This is a, we're seeing the past three years in particular, maybe three with the pandemic. Okay, maybe go a couple years earlier, then. The developers' behavior is driving the change. And you know, if you look at the past three DockerCons we've covered, we've been powering that site, been following that community very closely since the beginning, as well. It just seems in the past three to four years that the developers choices at scale, not what they're buying or who's pushing tools to them, has been one big trend. >> Yeah. >> They're setting the pace. >> Developer is the king. >> If it's self-service, we've seen self-service. Whether it's freemium to paid, that works. This is the new equation. Developer, developer choice is critical. So self-service they want. And two, the language barrier or jargon between or mindsets between security and developers. Okay, so DevOps brings IT into the workflow. Check. DevSecOps brings in there. You guys crack the code on that, is that what you're saying? >> Yes, and it's both the product, like how do you use the solution, as well as the go to market. How do you consume the solution? And you alluded to that with the PLG motion, that I think Synk has done the superb job at and that really helped our businesses. >> Okay, so Manoj, product, you got the keys to the kingdom, you got the product roadmap. I could imagine, and what I'd love to get your reaction too Adi, if you don't mind. If you do that, what you've done, the consequence of that is now security teams and the data teams can build guardrails. We're reporting a lot of that in the queue. We're hearing that we can provide guardrails. So the velocity of the developer seems to be increasing. Do you see that? Is that a consequence? >> That's something that we actually measure in the product. Right, so Snyk's focus is not finding issues, it's fixing issues. So one of the things we have been able to heuristically look at our thousands of customers and say, they're fixing issues 27 days faster than they were prior to Snyk. So, you know, I'm a Formula one fan. Guardrails, you say. I say there's a speed circuit. Developers love speed. We give them the speed. We give the security teams the ability to sit on those towers and, you know, put the right policies and guardrails in place to make sure that it's not speed without safety. >> And then I'm sure you guys are in the luxury box now, partying while the developers are (Lisa laughing) no more friction, no more fighting, right? >> The culture is changing. I had a discussion with a Fortune 50 CISO a month ago, and they told me, "Adi, it's the first time in my life where the development teams are coming to me, asking me, hey I want you to buy us this security solution." And for, that was mind blowing for him, right? Because it really changes the discussion with the security teams and the development teams >> Before Lisa jumps in, well how long, okay, let me ask you that question on that point. When did that tipping point change, culturally? Was it just the past few years? Has there, has DevOps kind of brought that in, can you? >> Yeah, I think it's a journey that happened together with Snyk's, kind of, growth. So if three years ago it was the very early adopters that were starting to consume that. So companies that are very, you know, modern in the way they developed and so on. And we saw it in our business. In the early days, most of our business came from the high tech industry. And now it's like everywhere. You have manufacturing, you have banks, you have like every segment whatsoever. >> Talk about that cultural shift. That's really challenging for organizations to achieve. Are you seeing, so that, that CISO was quite surprised that the developer came and said, this is what I want. Are you seeing more of that cultural changes? Is that becoming pervasive? >> Yeah, so I think that the root cause of that is that, you mentioned the growth, like the increased speed of velocity in applications. We have 30 million developers in the world today. 30 millions. By the end of the decade it's going to be 45 millions and all of them are using open source, third party code. Look at what's going on here in the event, right? This accelerates the speed for which they develop. So with that, what happened in the digital transformation world, the organizations are facing that huge growth, exponential growth in the amount of technology and products that are being built by their teams. But the way they manage that before, from a security perspective, just doesn't scale. And it breaks and it breaks and it breaks. This is why you need a different approach. A solution that is based on the developers, who are the ones that created the problems and the ones that will be responsible of fixing the issues. This is why we are kind of centering ourselves around them. >> And the world has changed, right? What is cloud? It's code, it's not infrastructure. Old infrastructure, hosted infrastructure. So if cloud is code and cloud native applications are all code and they're being deployed with Terraform packages and cloud formations, that's code. Why take an old school approach of scanning it outside-in. I talked to CISO today who said, I feel bad that, you know, our policy makes it such that a terraform change takes six months. What did I do? I made cloud look like infrastructure. >> Yeah, it's too slow. >> So that, you know, so both sides, you know, CISOs want something that the business, you know, accepts and adopts and it's, culture changes happen because the power is with the developers because all of this is code, and we enabled that whole seamless journey, all the way from code to cloud. So it's kind, you know, I think that this is a part of it. It's by direction, it's a bridge and both sides are meeting in the middle here. >> It's a bridge. I'm curious, how are you facilitating that bridge? You, we talk about the developers being the kings and queens and really so influential in business decisions these days. And you're talking about the developers now embracing Snyk. But you're also talking to CISOs. Is your customer conversation level changing as a result of security folks understanding why it needs to shift-left. >> We had a breakfast meeting with customers, prospects and everyone, I think this morning. It was interesting, we were remarking. There are CTOs, VPs of engineering, CISOs, VPs of AppSec. And it was such a rich conversation on both sides, right? So just the joy of facilitating that conversation and dialogue. CISOs, and so the levels are changing. It started for us in CTOs and VPs of engineering and now it's both because, you know, one of the things Adi talks about is, like, that security has to become development aware. And that's starting to be like the reality. Me getting another solution, with maybe a better acronym than the old acronym, but it's still outside-in, it's scan based. I light up up the Christmas tree, who is going to fix it? And with the speed of cloud, now I got throw in more lights. Those lights are no longer valid. >> The automation. >> The automation without prioritization and actual empowerment is useless. >> All right, I know we got a couple minutes left, but I want to get into that point about automation because inside-out, you've made me think about this. I want to get your thought Adi, if you don't mind. The integration challenges now are much more part of the ecosystem, more joint engineering. You mentioned these meetings are not just salesperson and customer buyer, it's teams are talking to each other. There's a lot of that going on. How do you guys look at that? Because now the worst things that I hear and when I talk to customers is, I hate the word PenTest and AppSec review. It slows things down. People want to go faster. So how do you guys look at that? What's Snyk doing around making the AppSec review process, integration across companies, work better? >> So I'll give you an example from the cloud and then I will relate to the AppSec. And this relates to what you mentioned before. We had a discussion yesterday with a CISO that said, we are scanning the cloud, we are opening the lights, we see this issue. Now what do I do? Who needs to fix this? So they have this long process of finding the actual team that is required to fix it. Now they get to the team and they say, why didn't you tell me about it when I developed it? The same goes for AppSec, right? The audit is a very late stage of the game. You want to make sure that the testing, that the policies, everything is under the same structure, the same policies. So when you do the same thing, it's part of the first time of code that you create, it's part of the change management, it's part of the build, it's part of the deployment and it's part of the audit. And you have everything together being done under the same platform. And this is, kind of, one of the strengths that we bring to the table. The discussion changes because now you have an aligned strategy, rather than kind of blocks that we have, kind of, mashed up together. >> So the new workflow, it's a new workflow, basically, in the mindset of the customer. They got to get their arms around that thing. If we don't design it in, the wheels could come off the bus at the 11th hour. >> Adi: Yeah. >> And everything slows down. >> I had a discussion with Amazon today, actually, that they had an internal discussion and they said, like, some of the teams were like, why have you blocked my app from being released? And they said, have you ever scanned your app? Have you ever looked at your, like, and, and they're like, if you haven't, then you're not really onboard with the platform and it just breaks. This is what happens. >> Great conversation. I know we don't, I wish we had more time. We'll do a follow up on theCube for sure. Should we get into the new twist? >> I've got one final question for you guys. We're making some Instagram reels, so think about your elevator pitch in 30 seconds. And I want to ask you about Snyk's evolution. Manoj, I want to start with you. What is that elevator pitch about Snyk's evolution to the end user customer? >> Empower developers, help them go faster, more productive and do it in a way that security is really built in, not bolted on. And that's really, you know, from a, the evolution and the power that we are giving is make the organization more productive because security is just happening as a part of making the developer more productive. >> Awesome. And Adi, question for you, how, your elevator pitch on how Snyk is really an enabler for CISOs these days? >> Yeah, so I always ask the CISO first of all, are you excited about the way your environment looks like today? Do you need to have a cultural change? Because if you need to have a cultural change, if you want to get those two teams working closely together, we are here to enable that. And it goes from the product, it goes from our education pieces that we can talk about in another section, and it works around the language that we build to allow and enable that discussion. >> Awesome. Guys, that was a double mic drop for both of you. >> Manoj: Thank you. >> Adi: Thank you, Lisa. >> Thank you so much for joining John and me, talking about what's happening with Snyk, what you're enabling customers to do and how, really, you're enabling cultural change. That's hard to do. That's awesome stuff guys. And congratulations on your 11th and your first Cube. >> Second, second, >> Second. >> Adi: I will be here more, but (laughs) >> You got it, you got it. You have to come back because we have too much to talk about. >> Adi: Exactly. (laughs) >> Thanks guys, we appreciate it. >> If we can without Manoj, so I can catch up. (Manoj laughs) >> Okay. We'll work on that. >> Bring you in the studio. (everyone laughing) >> Exactly. >> Eight straight interviews. (John and Lisa laughing) >> We hope you've enjoyed this conversation. We want to thank our guests. For John Furrier, I'm Lisa Martin. You're watching theCUBE, the leader in emerging and enterprise tech coverage. (soft electronic music)

(slow upbeat music) >> Good afternoon and welcome back to Sin City. We're here at AWS reInvent with wall-to-wall coverage on theCUBE. My name is Savannah Peterson, joined with Dave Vellante, and very excited to have two exciting guests from Qlik and AARP with us. Molly and Samir, thank you so much for being here. Welcome to the show. >> Thank you for having us. >> Thank you for having us. >> How's it been so far for you, Molly? >> It's been a great show so far. We've got a big booth presence out here. We've had a lot of people coming by, doing demo stations and just really, really coming to the voice of the customer, so we've really enjoyed the event. >> Ah, love a good VOC conversation myself. How about for you, Samir? >> Oh, it's been great meeting a lot of product folks, meeting a lot of other people, trying to do similar things that we're doing, getting confirmation we're doing the right thing, and learning new things. And obviously, you know, here with Molly, it's been a highlight of my experience. >> What's the best thing you learned from your peers, this week? >> You know, some of the things, that we're all talking about, is how do we get data in the right place at the right time? And, you know, that's something that people are now starting to think about. >> Very hot topic. >> You know, doing it, and then not only getting it to the right place, but taking insights and taking action on it as it's getting there. So those are the conversations that are getting around, in the circle I've been hanging around with. >> You hearing the same thing at the booth or? >> Yeah, absolutely. >> And how are you guys responding? >> Well, I think, as a company, and the shifts in the market, people are really trying to determine what workloads belong in which Cloud, what belongs on-prem? And so talking about those realtime transformations, the integration points, the core systems they're coming from, and really how to unlock that data, is just really powerful and meaningful. So that's been a pretty consistent theme throughout the conference, and a lot of conversations that we have on a regular basis. >> I believe that, Molly, let's stick with you for a second. Just in case the audience isn't familiar, tell us a little more about Qlik. >> Yeah, so Qlik is a robust, end-to-end data pipeline. Starting with really looking at all of your source systems whether it's mainframe, SAP, relational database, kind of name your flavor as it's related to sources. Getting those sources over into the target landing spot whether it be Amazon, or other cloud players, or even if you're, if you're managing hybrid workloads. So that's kind of one piece of the end-to-end platform. And then the second piece is really having all that data, analytics ready, coming right through that real-time data pipeline, and really being able to use the data, to monetize the data, to make sense of the data. And then Qlik really does all that data preparation work underneath the visualization layer, which is where all the work happens. And then you get to see the output of that through the visualization of Qlik, which is, you know, the dashboards, the things that our people, people are used to seeing. >> I love that! So at AARP, what are you using Qlik for? What sort of dashboards are you pulling together? >> So when we started our journey to AWS, we knew that, you know, we're going to have our applications, they're distributed in the Cloud, but again, how do we get the data there, in the right place at the right time? So, as members are, taking action, they're calling into the call center, using our website, using our mobile apps. We want to want it to be able to take that information stream it, so we use Qlik, to take those changes when they happen as they happen, be able to stream it to Kafka and then push that data out to the applications that need it in the time that they needed it. So, instead of waiting for a batch job to happen overnight, we're able to now push this data in real time. And by doing that, we're able to personalize the engagement for our members. So if you come in, we know what you're doing, we can personalize the value that we put in front of you, and just make that engagement a lot more engaging for you. >> Yeah. >> And in the channel that you choose to want to come in with, right? Rather than a channel that we are trying to push to you. >> Everyone wants that personalized experience as we discussed, I love AARP, I've done a lot of work with AARP, I look forward to being a member, but in case the audience isn't familiar, you have the largest membership database of any company on Earth that I'm aware of. How many members does AARP have? >> We have nearly 38 million members, and 66,000 volunteers, and 2300 employees across every state in the United States. >> It's a perfect use case for Qlik, right? 'Cause you've been around for a while. You've got data in the million different places. You're trying to get, you've got a mainframe, right? You know, I hear Amazon's trying to put all the mainframes in the Cloud, but I'm guessing the business case isn't there for you. But you want the data that's coming out of that mainframe to be part of that data pipeline, right? So can you paint a picture, of how, what Molly was describing about the data pipeline, how that fits with AARP? >> Yeah, it's actually, it was a perfect use case. And you know, when we engaged with Qlik, what we wanted to be able to do is take that data in the mainframe, and get it distributed into the Cloud, accurately, securely, and make sure that we can track the lineage, and be able to say, hey, application A only needs name and address, application B needs, name, address, and payment. So we were able to do all of that within a couple of weeks, right? And getting that data out there, knowing that it's going to the right place, knowing it's secure, and knowing it's accurate, regardless of the application it goes to, we don't have to worry about seeking data across different applications. Now we know that there's a source of truth, and everything is done through the pipeline, and it's controlled in a way that, we can measure everything that's going through, how it's going through, and how it's being used by the applications, that are consuming it? >> So you've got the providence and the lineage of that data and that's what Qlik ensures, is that right? Is that your role or is that a partner role, combined? >> No, yes, that's absolutely Qlik's role. So for our new offering, Qlik Cloud data integration, it's a comprehensive solution, delivered as a service, delivers real time, automates, transformations, catalog and lineage, all extremely important. And in the case of Samir and AARP, they're trying to unlock the most valuable assets of their data in SAP and mainframe. And surprisingly, sometimes most valuable data in an organization is the hardest to actually get access to. >> Sure. >> So be, you know, just statistically, 70% of Fortune 500 companies still rely on mainframe. So when you think about that, and even when Samir and I are talking about it. >> That's a lot. >> Yeah. >> And that's a lot of scale, that's a lot of data. >> It's a lot of data. >> Yeah. >> So, you know, mainframe isn't a thing of the past. Companies are still relying on it. People have been saying that for years but when we're talking about getting the complex data out of there to really make something meaningful for AARP, we're really proud of the results, and the opportunity that we've been able to provide to really improve the member experience. And how people are able to consume AARP, and all the different offerings that they have? Kind of like you mentioned Savannah, and the way that you go about it. >> Well, it's also the high risk data. High value data, high risk data. You don't want to mess with it. You want to make sure that you've got that catalog to be able to say, okay, this is what we did with that data, this is where it came from. And then you essentially publish to other tools, analytic tools in the Cloud. Can you paint a picture of how that extends to the Cloud? >> Sure, so there's a couple of different things that we do with it. So once we get the data, into our streaming apps, we can publish it over to like our website. We can publish it to the call center, to mobile apps, to our data warehouse, where we can run analytics and AI on it. And then obviously a lot of our journeys, we use a journey orchestration tool, and we've built a CDP, a customer data platform, to get those insights in there, to drive, you know, personalization and experience. >> I'm smiling as you're talking, Samir, because I'm thinking of all the personalized experiences that my mother has with AARP, and it is so fun to learn about the technology that's serving that to her. >> Exactly. >> This segment actually becoming a bit more personal for me than I expected for a couple of reasons. So this is great. Molly, Qlik has been a part of the AWS ecosystem since the get go. How have things changed over the years? >> Yeah, so Qlik still remains the enterprise integration tool of choice for AWS especially- >> Let's call that a casual and just brag. >> Yeah. >> Because that's awesome. That's great, congratulations on that. >> Thank you for SAP and mainframe. So the relationship continues to evolve but we've been part of the ecosystem from since inception. So we look at, how we continue to evolve the partnership? And honestly, a lot of our customers landing spot is AWS. So the partnership evolves really on two fronts. One with Amazon itself, in a partnership lane, and two, with our customers, and what we're doing with them, and how we're able to really optimize what that looks like? And then secondly, earlier this year we announced an offering Amazon and Qlik, called Qlik Ramp, where we can come in and do, a half day architecture deep dive, look at SAP mainframe, and how they get to the Amazon landing spots, whether it's S3, Redshift, or EMR? So we got a lot of different things kind of going on in the Amazon ecosystem, whether it's customer forward and first, and how can we maximize the relationship spend et cetera, with Amazon. And then also how can we deliver, you know, kind of a shorter time to value throughout that process with something like a Qlik ramp, because we want to qualify, and solve customers needs, as equally as we want to you know, say when we're not the right fit. >> So data is a complicated- >> Love that honesty and transparency. >> Data is a complicated situation for most companies, right? And there's a lack of resource, lack of talent. There's hyper specialization. And you were just talking about the evolution of the Cloud and the relationship. How does automation fit into the equation? Are you able to automate a lot of that data integration through the pipeline? >> Yeah. >> Is it was a, what's your journey look like there? Were you resistant to that at first? 'Cause you got to trust the data. Take us through that. >> Yeah, so the first thing, we wanted to make sure is security right? We've got a lot of data, we're going to make sure privacy- >> Very personal data too. >> Exactly. And privacy and security is number one. So we want to make sure anything that we're doing with the data is secure, and it's not given out anywhere. In terms of automation, so what we've been able to do is being able to take these changes, and you know, in technology, the one thing you can guarantee is it's going to break. Network's going to go down, or a server goes down, a database goes down, and that's the only guarantee we have. And by using the product that we have today, we're able to take those outages, and minimize them because there's retry processes, there's ways of going back and saying, hey, I've missed this much data. How do we bring it back in? You don't want data to get out of sync because that causes downstream problems. >> Yeah. >> So all of that is done through the product, right? We don't have to worry about it. You know, we get notifications, but it's not like, oh, I've got to pay someone at two o'clock in the morning because the network's gone down and how's the data sync going to come back up, when it comes back up? All of that's done for us. >> Yeah, and just to add to that, automation, is a key component. I mean, the data engineering teams definitely see the value of automation and how we're able to deliver that. So, improving the experience but also the overall landscape of the environment is critical. >> Yeah, we've seen the stats, data scientists, data pro spend, you know, 80% of their time wrangling data, 20% of their time. >> Data preparation. >> You know extracting value from it. So. >> Yeah, it's so sad. It's such a waste of human capital, and you're obviously relieving that, and letting folks do their job more efficiently. >> The thing is too, you know, as I'm somebody who's love data you dive into the data, you get really excited then after a while you're like, Ugh! >> I'm still here. >> I'm slogging through this data. Taking a bath in it. >> But I think. >> I want to get to the insights. >> I think that world's changing a little bit. >> Yes, definitely. >> So as we're starting to get data that's coming through it's got high fidelity, and richness, right? So in the old days we'd put in a database, normalize it, and then, you know we'd go and do our magic, and hopefully, you know something comes out, and the least of frustration, you just spoke about. Well now, because it's moving in real time, and we can send the data to areas in the way we want it, and add automation, and machine learning on top of that, so that, now it becomes a commodity to massage that data into the in the format that you want it. Then you can concentrate on the value work, right? Which is really where people should be spending the time, rather than, oh, I've got to manipulate the data, make sure it's done in a consistent way, and then make sure it's compliant and done, the same way every single time. >> It may be too early to, you know quantify the business impact, but have you seen, for example, you know, what I was describing creates data silos. 'Cause nobody's going to use the data if it's not trusted. So what happens is it goes to a silo, they put a brick wall around it, and then, you know, they do their thing with it. They trust it for that one use case and then they don't share it. Has that begun to change as you've seen more integration that's automated and augmented? >> Absolutely. I mean, you know, if you're bringing in data and you're showing that it's consistent, and this is where governance and compliance comes in, right? So as long as you have a data catalog, you can make sure that this data's coming through with the lineage that you said is going to, here's the source, here's the target, here's who gets what they only need rather than giving them everything. And by being able to document that, in a way, that's automated rather than somebody going in, and running a report, it's key. Because that's where the trust comes in, rather than, oh, Samir has to go in and manipulate this stream so that, you know, Molly can get the reports she wants. Instead, hey, it's all going in there, the reports are coming out, they're audited, and that's where the trust factor comes. >> And that enables scale. >> Yeah. >> Cloud confidence and scale. Big topics of the show this week. >> Yep. >> It's been the whole thing. Molly, what's next for Qlik? >> Yeah, Qliks on a big journey. So we've released a lot of things most recently, Qlik Cloud data integration as a service, but we're just continuing to grow from a customer base, from a capabilities perspective. We also recently just became HIPAA compliant and went through some other services. >> Congratulations, that is not an easy process. >> Thank you, thank you. >> Yeah. >> And so for us it's really just about expanding and having, that same level of fidelity of the data, and really just getting all of that pushed out to the market so everybody really sees the full value of Qlik, and that we can make your data Qlik. And just for a minute, back to your earlier point. >> Beautiful pun drop there, Molly. Just going to see that. >> Thank you Savannah. >> Yeah. >> But back to your earlier point, just about the time that people are spending, when you're able to automate, and you're getting data delivered in real time, and operational systems are able to see that. 'Cause you're trying to create the least amount of disruption you can, right? 'Cause that's a critical part of the business. When you start to automate and relieve that burden then people have time to spend time on the real things. >> Right. >> Future forward, prescriptive analytics, machine learning, not data preparation, solving problems, fixing soft gaps. >> Staring a spreadsheet, yeah. >> Right? It's actually the full end-to-end pipeline. And so that's really where I feel like the power is unleashed. And as more sources and targets come to light, right? They're all over the showroom floor, so we don't have to mention any of 'em by name, but it's just continuing, to move into that world to have more SaaS integrations. And to be able to serve the customer, and meet them exactly where they're at, at the place that they want to be. And for Samir, and what we did in the transformation there, unlocking that data for mainframe and SAP, getting it into Qlik Cloud, has been a huge business driver for them. And so, because of partners like AWS and Samir and AARP, we're constantly evolving. And really trying to listen to the voice of the customer, to become better for all of you. >> Excellent. >> Love that community first attitude. Very clear that you both have it, both AARP and Qlik with that attitude. We have a new challenge this year to reInvent on theCUBE, little prompt here. >> Okay. >> We're going to put 30 seconds on the clock, although I'm not super crazy about watching the clock. So, feel comfortable with whatever however much time you need. >> Whatever works. >> Yeah, yeah, yeah, yeah, whatever works. But we're looking for equivocally, your Instagram reel, your hot take, your thought leadership, sizzle, with the key theme from this year's show. Molly, your smile is platinum and perfect. So I'm going to start with you. I feel like you've got this. >> Okay, great. >> Yeah. >> Just the closing statement is what you're looking for. >> Sure, yeah, sexy little sound bite. What do you, what's going to be your big takeaway from your experience here in Vegas this week? >> Yeah, so the experience at Vegas this week has been great but I think it's more than just the experience at Vegas, it's really the experience of the year, where we're at with the technology shift. And we're continuing to see, the need for Cloud, the move to Cloud, mixed workloads, hybrid workloads, unlocking core data, making sure that we're getting insights analytics, and value out of that. And really just working through that, kind of consistent evolution, which is exactly what it is. It's never, you never get to a point where, that's it, there's a bow on it, and it's perfect. It's continuously involving, evolving. >> Yeah. >> And I think that's the most important part that you have to take away. Samir's got his environment in a great place today but in six months, there may be some new things or transformations that he wants to look at, and we want to be there at the ready to work with him, roll up our sleeves, and kind of get into that. So the shift of the Cloud is here to stay. Qlik is a hundred percent here to stay. Here ready to serve our customers in any capacity that we can. And I think that's really my big takeaway from this week. And I've loved it, like this has been a great, this has been great with both of you. You both are super high energy. >> Aw, thank you. >> And Samir and I have had a great time over the event as well. >> Well, nailed it. You absolutely nailed it. All right, Samir, shoot your shot. >> So. >> Savannah. >> What I would say, I'm pretty, so. (laughing) >> I like to keep the smiles organic on stage, my perverse sense of humor, everyone just tolerates. >> Yeah, the one thing I think, I'm hearing a lot is, we have to look at data in motion. Streaming data is the way it's going to go. Whether it's customer data, operational data, it doesn't matter, right? We can't have these silos that you spoke about. Those days are gone, right? And if we really want to make a difference, and utilize all of the technology that's being built out there, all of the new features that were, you know, just in the keynotes. We can't have these separate silos, and the data has to go across, trusted data, it has to go across. The second thing I think we're all talking about is, we have to look at things differently. Unlearning the old is harder than learning the new. So we were just talking about event driven architecture. >> Understatement of the century. Sidebar, that was, yeah. >> So, you know, a lot of us techies are used to calling APIs. Well, now we have to push the data out, instead of pulling it. That just means retraining our brains, retraining our architects, retraining our developers, to think in a different way. And then the last thing I think I've learned is, us technology folks have put the customer first right? >> Yes, absolutely. >> What does a customer want? How do they want to feel when they engage with you? Because if we don't do that, none of this technology matters. And you know, we have to get away from the day where the IT guys go in the back black room, (laughing) coat up and then, you know, push something out, and don't think about what am I doing, and how am I impacting your mother? >> Yes, the end customer. It's no longer the person at the end of a terminal. Look at the green screen. >> And just one last thing. I think also it's fit for purpose transformations. And that's how we have to start thinking about how we're doing business. 'Cause there's a paradigm shift, right? From ETL to ELT, right? Extract, Load, Transform your data. And so as we're seeing that, I think it's really just about that fit for purpose, and looking at the transformations, the right transformations. And what's going to move the needle for the business. >> What a great closing note! Molly, Samir, thank you both for being here. >> Both: Thank you! >> This was a really fantastic chat, love where we took it. And thank all of you for tuning in to our live coverage from AWS reInvent here in fabulous Las Vegas, Nevada. I just want to give my mom a quick shout out, since she got a holler throughout this segment, as well as Stacy and all of my friends at AARP, I missed you all. My name's Savannah Peterson, joined with Dave Vellante. You're watching theCUBE. We are the technology leader in coverage for events like this. (slow upbeat music)

(upbeat music) >> Good morning and welcome back to fabulous Las Vegas, Nevada. We're here at AWS re:Invent with wall-to-wall coverage all day long on theCUBE. My name is Savannah Peterson and I am joined this morning by the beautiful Lisa Martin. Lisa, good morning. >> Good morning. Good. >> How you feeling day three? >> Day three is we are going to be shot out of a cannon today. The amount of content coming at you from theCUBE today- >> Get ready, you all. >> Us two gals, is a lot. We're going to have some great conversations. >> And we're starting with a really great one with a Cube Alumni to the max. You've been on the show multiple times. >> John: Yeah. >> Very excited to welcome John, the CMO of Couchbase. Welcome. How you doing this morning? >> Thanks. I'm doing great. Great to be here with you. >> How do you feel about the show so far? What's your pulse? >> The show has been great. I say the energy is great. The traffic at our booth, the conversations that we're having, both with prospective customers and even just partners, right? They're all here. The ecosystem is here >> And everyone's finally back in person and it feels so good. >> John: It does. >> So, we're going to dig in a little bit but just in case the audience isn't familiar, tell us about Couchbase. >> Sure. Couchbase is a publicly traded database company. We have a cloud database platform called Capella which is hosted on AWS and GCP. It is used for building mission-critical applications. So, we have great customers, we're building apps that really matter and are using to drive their business. So, we're very excited about that. 30% of the Fortune 100 are Couchbase customers. >> Nice. Talk a little bit about the AWS relationship. >> Mm-hm. Yeah, so we have a great AWS relationship. In fact, yesterday we announced a deepening of that relationship, a strategic collaboration agreement. We're very excited. It's a multi-year agreement. It's focused on go-to market, from a sales and marketing standpoint. We're going to target, you know, various verticals and, you know, really generate joint business between the two of us. So, it's a deepening of a already strong relationship and we're really excited about that. >> Savannah: Yeah. Go ahead. >> What are some of the industry verticals that you're going to be tackling together? >> Well, gaming for one, right? Manufacturing, the workloads that Couchbase is good for are these mission-critical workloads are ones that are really suited for us to be used with AWS. So, we've done some work with them already in those areas and I'm sure we'll be digging in even deeper. >> That's exciting. Speaking of digging in deeper, tell us a little bit more about Capella. >> Capella. It's a cloud databases services I mentioned. We launched it last October and we are super excited by the uptake, the interest that we're seeing. We have a free 30 day trial, so, you know, people can come and try it and get their hands dirty just getting experience with the product and then, you know, become a customer after that. And we're seeing very strong interest from our existing customer base as well. So, we're really excited about how things are going. >> Talk about Capella and the latest release and how it's really enabling Couchbase to invest deeper into the developer experience. >> Yeah, so, at the end of October, we announced a revamp of our user interface, our user experience for Capella really focused on developers. And what we've done is make it so that it's familiar to developers, right? It's a GitHub-like experience. So, developer comes in, they're very familiar, of course, with GitHub, they are familiar with how the Couchbase Capella interface will work. And so that's something that, you know, we've really invested, in fact, we've invested in developers quite a bit. We announced a Couchbase community hub and a Couchbase ambassadors program, both focused on developers and getting out there and building our community. >> A community is a big topic that we've been talking about at all the conferences this year. We're all back in person, in community. How often are you communicating with your community to get feedback on what that experience should be like? >> Yeah, I mean, we actually have a Discord server, so we're in constant communication. (Savannah laughing) >> Savannah: Yes. (John laughing) 24/7. (laughing) >> Basically, you know, we have staff who's dedicated to making sure that the users on there are getting their answers and giving us feedback on the experience. The ambassadors are somebody who have a really strong relationship, who get early insight and give us feedback before we even release a product. So, it gives us a chance to really test-drive it with core developers and get the insight we need before we get it in the market. >> Yeah. It matters so much. You can build it, but they won't come if it's not fantastic. >> John: Exactly. >> Lisa: Right. >> Let's shift a little bit and talk about customers. How, and price, how do you guys compare? >> Customers and? >> And price, your price performance? >> Price, oh. So, customers, we also announced this week a joint customer Arthrex with AWS. Arthrex is a orthopedics medical devices company and they use our Edge capabilities along with running Couchbase on AWS. So, you think of the kinds of surgeries that orthopedic surgeons do, it's scopes and they are often inside. So, what it does is it collects the data, the video data and all of that on a medical devices and then brings it back to a centralized app for the doctors to use sort of in post when they're actually doing further medical recommendations. >> Savannah: It's so cool. >> So, it's cool, the thing about it is it can work whether it's online or offline, it's one of the reasons that Arthrex selected us because the fact that it can, you know, often sometimes there's not connectivity in the operating room, I'd say deep inside of a hospital. So, these devices work regardless and then when they get connectivity, it sinks back to that centralized service. So, it's one of the main reasons that they selected us. >> That's outstanding. You know, one of the things that John Furrier, you know, John, well, you guys go way back. >> John: Way back. >> He had a sit down with Adam Selensky, oh, about 10 days or so ago. He gets an exclusive with the CEO of AWS every pre re:Invent. And one of the things that Adam said is that the role or the title, data analyst, is going to go away, in that every role will have responsibilities of analyzing data. And I always think of that in terms of operations, marketing, finance, sales, but you just brought up physicians as data analysts in their jobs, right? Probably not, we're thinking about it in that way. >> Yeah. >> But it's so interesting how data is really being democratized. >> John: Yeah. >> And how Couchbase is an enabler of that in an operating room. >> John: Yeah, yeah, yeah. >> That's amazing. >> It's a great story. There's many others and I think, you know, we have embedded operational analytics in Couchbase Capella, and, you know, in our offerings in general. So, what that does is allows us to do real-time, highly personalized applications based on that analytics that are coming in real-time from the data from the applications. And so that's something that's actually driving a highly interactive user experience, one that's very personalized and customized. And that's one of the things that our customers really like about what we do. >> It's fascinating. I never thought about it from a medical device perspective. >> Lisa: No, no. >> John: No. >> My gosh is if doctors don't have enough cognitive burden load. >> John: I know. >> You know, right? Like, they don't need to be a data analyst. I would much rather they were just good at the surgery part. That's a piece of the puzzle I need them to do. Yeah, for sure. That's a fascinating customer example. Can you share any other joint AWS examples with us? >> Joint AW- I mean, there's many in the gaming area where, because Couchbase is memory-first architecture, we deliver very, very interactive user experiences and we're used a lot for session management, user ID management in the gaming space, specifically with AWS. It's an area we've done some joint work already and had a lot of success, you know, with small and large gaming companies. >> Yeah. It looks like you also, according to my notes here, we've got things in travel and hospitality as well. >> Yes. Also Carnival Cruises is a great example. We enable their on-ship, on-board experience, highly customized, everybody wears a device called a medallion, and as they move around the ship, it knows where they are and it's able to provide customized services. You walk up to a bar, you have your favorite drink, it can be hit the bar when you land there. >> I'll take that. >> How about that? (laugh) >> That's outstanding. >> Isn't that great? >> Can we carry that onto the AWS show floor? >> Exactly. >> Or Starbucks order? >> Yeah, yeah. Yes, please. Yes, please. Well, another thing that's so interesting these days, is that every company has to be a data company. Say they have to be a software company. They have to be a data company. You just gave some great examples. Hospitality, gaming, healthcare, where that data democratization has to happen. >> John: Yeah. >> Businesses has to transform. But one of the things that Adam also told John is that CIOs, CEOs are coming to him not wanting to talk about technology but about transformation. >> Yeah. >> Huge topic. >> And that's a journey where every customer is at different levels. >> Yeah. >> How is Couchbase helping businesses transform and where are your customer conversations these days? >> Yeah, yeah, yeah. So, I mean, the transformation of the business is a major topic of conversation. So, we completely agree with that. How Couchbase helps is, you know, in our database, one of the things we have is the SQL engine. And so as people are looking to move and modernize their infrastructure, if they're moving off of, or from like a technology that's principally based on SQL but doesn't give all the flexibility of a JSON database or document database like we do, we actually enable them to get more easily onto our platform so that they can start that transformation. And then it's a, you know, it's a journey of how they want to transform their business and it's really focused on how do they better serve their customers and clients, whether it's internal or external? >> It really matters. I mean, and that ease of use as well as the transformation journey. It takes a long time for people to adapt. So, every piece of that puzzle, every Lego being quicker or easier, more intuitive, like you said, with the user experience, we can tell you're very thoughtful. How does this improve the total cost of ownership for your customers? >> That's one of the things that we announced along with that developer changes, was a new storage engine underneath Couchbase Capella. And it's 10 X more dense storage. And what that means is fewer servers. So, fewer servers is a much better cost of ownership story. That plus just the performance of the platform itself, we find, you know, against competition, we can do things on say six nodes that take 18 nodes for others. >> Lisa: Oh wow. >> And we have a great consolidation story as well because we have, it's a multi-modal database, meaning that it has SQL engine, document database, full tech search, eventing and analytics, all these pieces on one common data layer. So, you can actually consolidate off of other technologies onto one, onto Couchbase, and that actually saves you money. So, that's a great story for us. >> There's got to be a sustainability element to that as well? >> Yeah, I mean it's, obviously, if you're using less, using fewer servers, there's a kind of power consumption aspect of it as well. Absolutely. >> Are you finding that a lot of customers and companies we talk to these days have in their RFPs, they must only work with vendors who have an actual ESG program? Are you finding more customers coming to you saying, how can you help us dial down our carbon emissions? >> John: Yeah. >> Savannah: Great question. >> We've got a sustainability program that we've got to meet, we've got commitments to our customers. >> John: Yeah. >> Is that something that's really now kind of a hard and fast requirement? >> We're hearing it, we're definitely hearing it. I wouldn't say it's, you know, massively pervasive but I would say it's a growing component of, as you said, RFPs. And it's something that we feel like we have a great story for. And so, you know, it's something that helps when we get into those conversations, we can clearly articulate how we can provide that value and how we meet some of those needs that they have. >> Yeah, that's awesome. So, we have a bit of a challenge, new to the show at re:Invent. >> John: Mm-hm. >> Where we are prompting you to give us your 30 second Instagram Reel sizzle highlight. Don't worry, I'm not actually timing you, but your thought leadership hot-take on the most important theme or takeaway from this year's show. >> From the conference here. I would say that, and I think this was talked about a little bit by AWS as well, but the convergence of analytics and operational data, you know, through the applications is one that we're certainly seeing as well. It's the reason we have analytics in our database. But as I walk around and look at it, I see that very much as a common theme as well, in terms of what other vendors are saying and just the conversations we're having. So for me, that's one of the things I think would be a takeaway from this show. >> Yeah. Embedded analytics, real-time, everybody wants to know what's going on, in context. >> Yeah. That's right. >> Right now, not last week, not what we're processing from last month. >> Exactly. >> I mean, right? (cross-talking) >> So, I can react and take advantage or take an action if I have to. >> Exactly. And then deliver that personalized experience that we all expect these days. >> Oh, yes. >> I'll take that medallion- >> It's about the medallion. I was like, okay. >> You up with that, John? >> We'll get right on it. >> Lisa: All right. (laughs) >> About this. So, what's next for Couchbase? >> John: Well- >> I know you got the partnership, you've got all this exciting momentum. >> So, we're excited heading into next year. We're going to continue to innovate on Capella, right? Continue to deliver more value, lean into our developer community that we have. We're investing heavily, not just from a product standpoint but from a company standpoint in terms of, you know, our community meetups and some of those things. We have a big community-focused event coming up in March called Connect, Couchbase Connect. So, that's something that we'll, you know, continue to drive. That'll be a major theme for us next year. Cloud and developers and, you know, continuing to enable that ecosystem. >> Lisa: Excellent. >> I just had a Microsoft moment where I saw you saying, "Cloud developers," on stage. (Lisa and Savannah laughing) >> I'm not going Steve Ballmer on you. (all laughing) >> Pardon. I was trying to get someone to sing yesterday. I was hoping you were my Ballmer dance. Oh, man. Well, this has been a really great way to start the day. John, thank you so much for being on the show with us, seriously. And it's great that you keep coming back. I'm glad we haven't scared you off. (John laughing) >> Never. >> Savannah: We will have you anytime. >> Thank you. >> And thank you all for tuning in for yet another fantastic day of all day live coverage here from AWS re:Invent. We are in Sin City, having a fabulous time with Lisa Martin. I'm Savannah Peterson. This is theCUBE and we are the leader in high-tech technology coverage. (upbeat music) (upbeat music fades)