>> And I'm here at Dell's Presence at MWC with vice president of marketing for telecom and Edge Computing, Aaron Chaisson. Aaron, how's it going? >> Doing great. How's it going today, Dave? >> It's going pretty well. Pretty excited about what you've got going here and I'm looking forward to getting the tour. You ready to take a closer look? >> Ready to do it. Let's go take a look! For us in the telecom ecosystem, it's really all about how we bring together the different players that are innovating across the industry to drive value for our CSP customers. So, it starts really, for us, at the ecosystem layer, bringing partners, bringing telecommunication providers, bringing (stutters) a bunch of different technologies together to innovate together to drive new value. So Paul, take us a little bit through what we're doing to- to develop and bring in these partnerships and develop our ecosystem. >> Uh, sure. Thank you Aaron. Uh, you know, one of the things that we've been focusing on, you know, Dell is really working with many players in the open telecom ecosystem. Network equipment providers, independent software vendors, and the communication service providers. And, you know, through our lines of business or open telecom ecosystem labs, what we want to do is bring 'em together into a community with the goal of really being able to accelerate open innovation and, uh, open solutions into the market. And that's what this community is really about, is being able to, you know, have those communications, develop those collaborations whether it's through, you know, sharing information online, having webinars dedicated to sharing Dell information, whether it's our next generation hardware portfolio we announced here at the show, our use case directory, our- how we're dealing with new service opportunities, but as well as the community to share, too, which I think is an exciting way for us to be able to, you know- what is the knowledge thing? As well as activities at other events that we have coming up. So really the key thing I think about, the- the open telecom ecosystem community, it's collaboration and accelerating the open industry forward. >> So- So Aaron, if I'm hearing this correctly you're saying that you can't just say, "Hey, we're open", and throw a bunch of parts in a box and have it work? >> No, we've got to work together to integrate these pieces to be able to deliver value, and, you know, we opened up a- (stutters) in our open ecosystem labs, we started a- a self-certification process a couple of months back. We've already had 13 partners go through that, we've got 16 more in the pipeline. Everything you see in this entire booth has been innovated and worked with partnerships from Intel to Microsoft to, uh, to (stutters) Wind River and Red Hat and others. You go all the way around the booth, everything here has partnerships at its core. And why don't we go to the next section here where we're going to be showing how we're pulling that all together in our open ecosystems labs to drive that innovation? >> So Aaron, you talked about the kinds of validation and testing that goes on, so that you can prove out an open stack to deliver the same kinds of reliability and performance and availability that we expect from a wireless network. But in the opens- in the open world, uh, what are we looking at here? >> Yeah absolutely. So one of the- one of the challenges to a very big, broad open ecosystem is the complexity of integrating, deploying, and managing these, especially at telecom scale. You're not talking about thousands of servers in one site, you're talking about one server in thousands of sites. So how do you deploy that predictable stack and then also manage that at scale? I'm going to show you two places where we're talkin' about that. So, this is actually representing an area that we've been innovating in recently around creating an integrated infrastructure and virtualization stack for the telecom industry. We've been doing this for years in IT with VxBlocks and VxRails and others. Here what you see is we got, uh, Dell hardware infrastructure, we've got, uh, an open platform for virtualization providers, in this case we've created an infrastructure block for Red Hat to be able to supply an infrastructure for core operations and Packet Cores for telecoms. On the other side of this, you can actually see what we're doing with Wind River to drive innovation around RAN and being able to simplify RAN- vRAN and O-RAN deployments. >> What does that virtualization look like? Are we talking about, uh, traditional virtual machines with OSs, or is this containerized cloud native? What does it look like? >> Yeah, it's actually both, so it can support, uh, virtual, uh-uh, software as well as containerized software, so we leverage the (indistinct) distributions for these to be able to deploy, you know, cloud native applications, be able to modernize how they're deploying these applications across the telecom network. So in this case with Red Hat, uh, (stutters) leveraging OpenShift in order to support containerized apps in your Packet Core environments. >> So what are- what are some of the kinds of things that you can do once you have infrastructure like this deployed? >> Yeah, I mean by- by partnering broadly across the ecosystem with VMware, with Red Hat, uh, with- with Wind River and with others, it gives them the ability to be able to deploy the right virtualization software in their network for the types of applications they're deploying. They might want to use Red Hat in their core, they may want to use Wind River in their RAM, they may want to use, uh, Microsoft or VMware for their- for their Edge workloads, and we allow them to be able to deploy all those, but centrally manage those with a common user interface and a common set of APIs. >> Okay, well I'm dying to understand the link between this and the Lego city that the viewers can't see, yet, but it's behind me. Let's take a look. >> So let's take a look at the Lego city that shows how we not deploy just one of these, but dozens or hundreds of these at scale across a cityscape. >> So Aaron, I know we're not in Copenhagen. What's all the Lego about? >> Yeah, so the Lego city here is to show- and, uh, really there's multiple points of Presence across an entire Metro area that we want to be able to manage if we're a telecom provider. We just talked about one infrastructure block. What if I wanted to deploy dozens of these across the city to be able to manage my network, to be able to manage, uh, uh- to be able to deploy private mobility potentially out into a customer enterprise environment, and be able to manage all of these, uh, very simply and easily from a common interface? >> So it's interesting. Now I think I understand why you are VP of marketing for both telecom and Edge. Just heard- just heard a lot about Edge and I can imagine a lot of internet of things, things, hooked up at that Edge. >> Yeah, so why don't we actually go over to another area? We're actually going to show you how one small microbrewery (stutters) in one of our cities nearby, uh, (stutters) my hometown in Massachusetts is actually using this technology to go from more of an analyzed- analog world to digitizing their business to be able to brew better beer. >> So Aaron, you bring me to a brewery. What do we have- what do we have going on here? >> Yeah, so, actually (stutters) about- about a year ago or so, I- I was able to get my team to come together finally after COVID to be able to meet each other and have a nice team event. One of those nights, we went out to dinner at a- at a brewery called "Exhibit 'A'" in Massachusetts, and they actually gave us a tour of their facilities and showed us how they actually go through the process of brewing beer. What we saw as we were going through it, interestingly, was that everything was analog. They literally had people with pen and paper walking around checking time and temperature and the process of brewing the beer, and they weren't asking for help, but we actually saw an opportunity where what we're doing to help businesses digitize what they're doing in their manufacturing floor can actually help them optimize how they build whatever product they're building, in this case it was beer. >> Hey Warren, good to meet you! What do we have goin' on? >> Yeah, it's all right. So yeah, basically what we did is we took some of their assets in the, uh, brewery that were completely manually monitored. People were literally walking around the floor with clipboards, writing down values. And we censorized the asset, in this case fermentation tanks and we measured the, uh, pressure and the temperature, which in fermentation are very key to monitor those, because if they get out of range the entire batch of beer can go bad or you don't get the consistency from batch to batch if you don't tightly monitor those. So we censorized the fermentation tank, brought that into an industrial I/O network, and then brought that into a Dell gateway which is connected 5G up to the cloud, which then that data comes to a tablet or a phone, which they, rather than being out on the floor and monitor it, can look at this data remotely at any time. >> So I'm not sure the exact date, the first time we have evidence of beer being brewed by humanity... >> Yep. >> But I know it's thousands of years ago. So it's taken that long to get to the point where someone had to come along, namely Dell, to actually digitally transform the beer business. Is this sort of proof that if you can digitally transform this, you can digitally transform anything? >> Absolutely. You name it, anything that's being manufactured, sold, uh, uh, taken care of, (stutters) any business out there that's looking to be able to be modernize and deliver better service to their customers can benefit from technologies like this. >> So we've taken a look at the ecosystem, the way that you validate architectures, we've seen an example of that kind of open architecture. Now we've seen a real world use case. Do you want to take a look a little deeper under the covers and see what's powering all of this? >> We just this week announced a new line of servers that power Edge and RAN use cases, and I want to introduce Mike to kind of take us through what we've been working on and really what the power of what this providing. >> Hey Mike, welcome to theCube. >> Oh, glad- glad to be here. So, what I'd really like to talk about are the three new XR series servers that we just announced last week and we're showing here at Mobile World Congress. They are all short depth, ruggedized, uh, very environmentally tolerant, and able to withstand, you know, high temperatures, high humidities, and really be deployed to places where traditional data center servers just can't handle, you know, due to one fact or another, whether it's depth or the temperature. And so, the first one I'd like to show you is the XR7620. This is, uh, 450 millimeters deep, it's designed for, uh, high levels of acceleration so it can support up to 2-300 watt, uh, GPUs. But what I really want to show you over here, especially for Mobile World Congress, is our new XR8000. The XR8000 is based on Intel's latest Sapphire Rapids technology, and this is- happens to be one of the first, uh, EE boost processors that is out, and basically what it is (stutters) an embedded accelerator that makes, uh, the- the processing of vRAN loads very, uh, very efficient. And so they're actually projecting a, uh, 3x improvement, uh, of processing per watt over the previous generation of processors. This particular unit is also sledded. It's very much like, uh, today's traditional baseband unit, so it's something that is designed for low TCO and easy maintenance in the field. This is the frew. When anything fails, you'll pull one out, you pop a new one in, it comes back into service, and the- the, uh, you know, your radio is- is, uh, minimally disrupted. >> Yeah, would you describe this as quantitative and qualitative in terms of the kinds of performance gains that these underlying units are delivering to us? I mean, this really kind of changes the game, doesn't it? It's not just about more, is it about different also in terms of what we can do? >> Well we are (stutters) to his point, we are able to bring in new accelerator technologies. Not only are we doing it with the Intel, uh, uh, uh, of the vRAN boost technologies, but also (stutters) we can bring it, too, but there's another booth here where we're actually working with our own accelerator cards and other accelerator cards from our partners across the industry to be able to deliver the price and performance capabilities required by a vRAN or an O-RAN deployment in the network. So it's not- it's not just the chip technology, it's the integration and the innovation we're doing with others, as well as, of course, the unique power cooling capabilities that Dell provides in our servers that really makes these the most efficient way of being able to power a network. >> Any final thoughts recapping the whole picture here? >> Yeah, I mean I would just say if anybody's, uh, i- is still here in Mobile World Congress, wants to come and learn what we're doing, I only showed you a small section of the demos we've got here. We've got 13 demos across on 8th floor here. Uh, for those of you who want to talk to us (stutters) and have meetings with us, we've got 13 meeting rooms back there, over 500 costumer partner meetings this week, we've got some whisper suites for those of you who want to come and talk to us but we're innovating on going forward. So, you know, there's a lot that we're doing, we're really excited, there's a ton of passion at this event, and, uh, we're really excited about where the industry is going and our role in it. >> 'Preciate the tour, Aaron. Thanks Mike. >> Mike: Thank you! >> Well, for theCube... Again, Dave Nicholson here. Thanks for joining us on this tour of Dell's Presence here at MWC 2023.

>> theCUBE's live coverage is made possible by funding from Dell Technologies. Creating technologies that drive human progress. (upbeat music) >> Lisa Martin: Good afternoon everyone. theCUBE live in Barcelona, Spain at MWC23. Lisa Martin with Dave Nicholson. Day three of our wall-to-wall coverage of four days of CUBE content. I know, it's amazing. We're going to have a great conversation next with DISH and Dell, talking about the value of automation and telecom for 5G. Please welcome Song Toh, Senior Director of Product Management Infrastructure Automation at Dell. And Sidd Chenumolu, VP of Technology Development at DISH. Guys, great to have you on theCUBE. >> Thanks for having us. >> Thank you, it's a pleasure. >> So let's go ahead and start with you. We know that DISH is developing its own open cloud native 5G network from the ground up. Talk to us about before you were working with Dell, what the situation was like and why you brought Dell in to help drive the innovation. >> Ah, that's a good question. So, three years ago we started the journey, and one thing that was very clear to us is that we want to work with the partners who are going to be the leaders in this space. And it was very clear we are going to be in the cloud side- we are going to be in hybrid cloud, we are going to have our own data centers. Everything that we built is going to replicate a cloud model. 'Cause it was very, like we said, what is 5G? Fundamentally, if you think about 5G, right? Everyone says people talk about speeds. Okay, get it. But it's also about vertical industries. It's about customization of a network, application driven network. That's the way I call it, because if you walk around the floor right now, everyone's talking about monetization of 5G, everyone keeps doing enterprise. So you put two and two together, what do you get? That means you have to work with the leaders who have been serving enterprises forever, who know the enterprises' pain, they know all the problem statements. So we said, "okay, let's see who's out there and who can help us." And then obviously, Dell comes to the picture. So we had a good conversation, there was an alignment in where Dell wanted to go long-term, so we saw synergies. So we had a vision, we needed their help. They wanted to get into this space too. So there was an agreement, let's do it together. And it's been a good partnership since then. >> What were some of the challenges that you had at that time? Going, "we've got some challenges here, some risks, we want to move DISH forward and automate." Talk about some of those challenges that helped you understand, "Yeah, Dell's the right partner for this." >> Oh, first is when we started this, right? I'll be honest, I don't think we anticipated the complexity. We didn't know what we didn't know. So initially it was learning from Dell, who was more like teaching us, "this is what you're going to see, this is how it's going to look like". And then we started bringing the telco aspects on top of it. So it was not like, "I'm going to build a 5G". We said, "no, Dell, tell me what does the data center look like? Tell me the day-to-day challenges. How do you bring a server in? How the rack looks like, what are the connectivity?" So, learning, then you bring the telco as an application, it was not like a telco first. It was like a software first, infrastructure second, now you bring in the telco part of it. So, I mean, challenges I would say, right? Everything was new, pretty much across the board for us. It was not just one thing. We were doing Open RAN, which was a brand new cloud native, was completely new. 5G standalone was new. No one had done that before, and (mumbles) was hybrid cloud. So I think we were on a stool sitting on the, with the four legs, all were wobbly. (laughs) We made it. So, automation was definitely the key. We knew we had to go at a scale, because we are in FCC deployment, we are meeting like- we will be at covering 230 million pops by June of this year. So, aggressive timelines- >> Dave Nicholson: Wait, say that again. How many, so say that ag- how many? >> 230 million. >> And, pops being points of presence? >> No, sorry, population. U. S.- >> Oh, population. Okay, I'm sorry, I'm sorry. Okay, okay. >> Okay. I'm sorry, I'm- >> So, very aggressive buildout for us. >> Wow. >> And automation has to be the key for it, because we just cannot- first is, we cannot scale a company. We are a startup. This wireless is a startup. That's how we started with a handful of people. We obviously hired a lot of people since then, but we said, "we will never be at the scale of the existing CSPs today." We can't. Time is not on our side, and we don't want to be at that scale anyway, 'cause we want to be nimble, move fast. So what do you need? Automation. Automation at every layer. And it's a journey. Never stops. >> No, it doesn't stop. >> Oh yeah, I'm sorry. Yeah, she's- >> Go ahead and get a question in. I don't want to hog. >> So when most people hear DISH, they think of streaming content, they think of alternative to cable provider. >> Sidd: Yeah. >> In that space. But just clarify for us all of the things that DISH is involved with today, and what DISH aspires to be involved with as we move forward. >> Good question. We want to be in the connectivity space. We want to connect everything. That's our goal, our mission statement. We started with the satellite, since then we moved on to the IPTV Sling, which is a leader. So we are not afraid to take risks, right? So what we own- we own satellites, we know content delivery very well. I think we are done there for many years. We agreed to that. Now we said, "now we understand wireless". What we want to do is, we want to deliver the data to the customers, and whether it could be videos, it could be audio data, like voice, anything, or it could be a machine. We just want to be in the connectivity space of connecting everything, and based on- you look around, right? It's all about connectivity. Everything requires connectivity. It's all about data monetization, and we want to be there in every aspect of it. >> Connectivity is almost the lifeblood these days of everything that we do, right? >> Sidd: Yep. >> Song: Indeed. >> And of every industry. Song, talk a little bit about the DISH Wireless use case. How some of their challenges in telco really maybe helped even Dell accelerate its presence in telco. >> Absolutely, right. I think one thing that Sidd mentioned, right, 230 million populations, but what does that translate to in terms of infrastructure deployment? 'Cause he said it's a startup. They started from not a whole lot in terms of coverage. So, in terms of 5G deployment, whether it's virtualized or open RAN, there needs to be distributed infrastructure that covers the entire United States, right? A certain percentage of the population is still a huge amount of coverage. So deploy tens of thousands, hundreds of thousands of servers around the country, get them set up, get 'em configured, and maintain and monitor and meter all of that. We help DISH to essentially roll that out, get it going, and then they deploy their RAN workload on top. I mean, that's a very significant undertaking. We were very proud to be able to offer our Bare Metal Orchestrator to facilitate that, but ultimately their success is their success. We are there to help, right? We are partnered, and we- happy to definitely be able to say we got to a point that we are happy, you know, in claims of success there. >> Well, that's why we selected Dell. >> Thank you. (chuckles) >> Let's unpack a little bit of some of the successes, some of the outcomes that you've achieved so far, working with Dell. >> Let me give an example. Today we have an ability to upgrade, update, even swap a RAN vendor overnight. Entire market, unheard of overnight. Give me hours, I'll do the entire thing for you from scratch. We can instantiate entire data center racks remotely in a matter of minutes. Cannot do that without automation, and with the help- >> Lisa Martin: Couldn't do it before. >> We have curated an extraordinary, what you call orchestration mechanism of finely tuned data sets and pipelines. It's like a machine. It keeps spinning. It's very good. And again, not something that happened overnight. Took us several months to get there with a lot of our partners, and Dell was there. >> Song: Right. >> I'd be curious to get your perspectives, each of you, on some of the buzz that was going on around the show where the telecom, "plumbing providers"- >> Sidd: Yep. >> have complained about the content streaming through, and maybe they need to charge more for access, and Netflix hit back and said, "well, hold on a minute. You wouldn't have anything to deliver to your customers if it weren't for the content we are producing. Maybe we need licensing fees from you." >> Song: (chuckles) >> What is your view on that, in terms of this whole over the top conversation? DISH seems sort of, kind of in a hybrid position there. >> Well, it's a very complex question. I think everyone is struggling with it, so I'm not sure if I have the right answer for it. We are definitely unique because we own the content too. We want to offer- we probably may offer our own content over the wireless service. There is a pros and cons. I mean, purely from a, as a M&O service provider, it's a lot of effort and cost for us to deliver huge amount of bandwidth. But again, the networks are being built to handle huge capacity. So if you don't have video, what do we do? That's also a realistic question. I think there is a mechanism where the cost and the value both have to be shared. So that it's a win-win for everyone. It's not lopsided to one. And said, "you carry most of the cost", and I'm transparent, it doesn't work that way long term. And especially given the 5G side, with all the slicing capabilities and ability to offer QoS, better quality of experience, I think there's a value to be created here. >> If you look at the infrastructure necessary to drive all of these things- >> Right. >> We've seen, just go back to our own consumer experience with the internet. We've gone from text to images to video. >> Song: Right. >> To high definition video. >> Sidd: Yeah. >> To, is 8K video absurd? Do we really need to be able to handle that? What are the things that need to be supported as we move forward? Is it that we scale out into this world of billions and billions of things that are connected? Or are there these much bigger, fatter pipelines for things like 8K video or it a combination of the two? What is Dell thinking of when it thinks of the infrastructure that it builds and how you customize that- >> Song: Right. >> to address those things? What's on the horizon? >> Dave, I think that's a very good question, right? Certainly communication service providers like DISH has built out the capacity to handle the customers that they want to serve. But there's another aspect of this I think I'd like to add on top of the question you posed, it's not about say, 10, say a thousand streams of 8K. I would need to be able to handle that. I think the present challenge right now is really, say there's a sports stadium that you need to activate so that, not about everyone filming that sports game, it's about, "Hey, I got to tell my, whoever- I got a 10 seconds video clip that I got to share with my friends." It's also not about copyright. It's more about- >> Dave Nicholson: (laughs) >> can you as a provider- >> The NFL is listening. >> Exactly. Can you as a provider handle that service? Because otherwise your customers say, "oh, I got into the sports stadium, every time I could not even text my daughter." >> Dave Nicholson: Yeah. >> So, how do you then scale up the infrastructure as needed, the bandwidth as needed, and scale back down when it's not? Maybe, because the infrastructure can potentially be repurposed for a different workload too. That requires automation, right? From bottom to top, all the way, infrastructure - all the way up to the workload. And that's I think a question that people are starting to ask. I'm not sure. I mean, still you guys have thought about that too as a- >> I mean, instant gratification is the new thing, right? Everyone wants instant response, everyone feedback, everything. So connectivity is given. I do think there is a space for both billions of devices and the 8K and probably 16K in the future. It's going to happen in the technology walls. That's why I like, say, the 5G, and especially the way we architect our own network. We call it network of networks. I'm not designing a network that is only for one monolithic application or one stack only. We are actually programmable network, because I know network A is for 8K. Network B is for IOT, network C is for regular, network D is for something else. And the list can keeps on growing. I don't think we can stifle innovation at any level and said, "well you can't do this because we are not ready." World is going to move too fast. Technology is too fast for all of us. >> But do you have to prioritize? >> If there is a business for- it's all top-down driven, not much of a technology driven. If there's a business, someone said there's a value to be made, it's prioritized. >> What's your - Sidd, we'll stick with you, your observations. This is day three of MWC 23. Lot of talk here on disaggregation. A lot of talk about open RAN, a lot of talk about private 5G wireless networks, but also some controversy. You brought up the Netflix controversy. >> Dave: Yep. >> What are some of the messages that you've heard so far from this event - and then, Song, we'll ask you the same question - that excite you about the direction that the industry's going and where DISH Wireless stands within it? >> Yeah. I mean, I didn't have a chance to walk the floor, but for wherever I have been in the last two and a half days, one thing that stood out is people are no longer talking about gigabits capacity anymore. They're talking about monetization of the network. Everyone is talking APIs now. >> Lisa Martin: Yeah. >> That's the buzzword. If I said monetization, API- I got a beautiful network not tell me how to make money off it and how do I work with each other? It's no longer about "I want to own it all." What can I do to partner with A, partner with B? How can we all grow together? I think that's the theme that I see this year compared to the previous years, where it was always about like, "hey, build the best 5G network with the high speeds, big radios." I don't even see radios, by the way. >> Lisa Martin: (chuckles) >> Interesting. Yeah. So the actual, it's almost fascinating when you toil in obscurity to build these critical components and then people ignore you. So I feel for the radio people. >> Song: (laughs) Being a long-term infrastructure guy, what have you been seeing here that's interesting? >> Well, a few things that I feel quite excited about from the conversation I've had. One is, on the private mobility side, Lisa, as you said, I'm seeing certainly customers, partners, and even in the booth talking about what the use cases are, right? Rather than, "Hey, here's a cool technology." But actually, people talking about use cases now. And, with the communication service providers and the operators, I'm hearing - of course, I mean, Sidd's doesn't have that problem because it's building whole new, >> (chuckles) >> but there are other providers that are saying, "Hey, we acknowledge that we need to transform and we are on the way too", rather than saying, "can I not do it and still, you know, live with the modern world." So I feel that we always need to be ready to change, because the world, the market, and all other factors will cause us to either change or really to change. And I think we are changing. Open system is becoming more of a expected, you know, future. It's just how do we get there, right? What do we need to learn as we get there? And we're happy to provide the support as a partner, the automation technology, and even the solutions to enable that, from Dell's perspective. >> So DISH in particular? DISH Wireless. >> Yep. >> Despite the fact that everyone's heard of DISH. >> Song: Yeah. >> DISH has been around for a long time. Where you sit within DISH Wireless, you described it as a startup. You don't feel encumbered by a lot of the legacy things that maybe some other providers do. Is that a fair statement or are you having to navigate that? We call it ambidextrous management >> (laughs) >> in the CTO world, where it's like, got to keep the lights on, got to keep the existing revenue flowing, also got to innovate. How do you blend the two? Is that a challenge? >> Well, probably not a challenge for me. I'm on the wireless technology and architecture side, so I get to do the cool stuff. >> Dave Nicholson: Okay. >> Don't have to worry about day to day operations, some complexity or revenue. Someone else is managing that complex part. They let me play with my toys. >> Well played, well played. >> Guys, it's been great having you on the program talking about what DISH Wireless is doing with Dell. Thanks to Dell. We're going to be watching this space to see how you continue to innovate. Thank you so much for joining us on the program. >> Thanks for having us. >> Thank you. >> Our pleasure. >> For our guests and for Dave Nicholson. I'm Lisa Martin. You're watching theCUBE live from MWC 23. Stick around. Our next guest joins Dave and me in just a minute. (upbeat music) (upbeat music) (upbeat music)

>> Announcer: TheCUBE's live coverage is made possible by funding from Dell Technologies, creating technologies that drive human progress. (pleasant music) >> We're back. This is Dave Vellante for our live coverage of MWC '23 SiliconANGLE's wall to wall, four-day coverage. We're here with Greg Manganello, who's from Fuijitsu. He's the global head of network services business unit at the company. And Ryan McMeniman is the director of product management for the open telecom ecosystem. We've been talking about that all week, how this ecosystem has opened up. Ryan's with Dell Technologies. Gents, welcome to theCUBE. >> Thank you, Dave. >> Thank you. >> Good to be here. >> Greg, thanks for coming on. Let's hear Fuijitsu's story. We haven't heard much at this event from Fuijitsu. I'm sure you got a big presence, but welcome to theCUBE. Tell us your angle. >> Thanks very much. So Fuijitsu, we're big O-RAN advocates, open radio access network advocates. We're one of the leading founders of that open standard. We're also members of the Open RAN Policy Coalition. I'm a board member there. We're kind of all in on OpenRAN. The reason is it gives operators choices and much more vendor diversity and therefore a lot of innovation when they build out their 5G networks. >> And so as an entry point for Dell as well, I mean obviously you guys make a lot of hay with servers and storage and other sort of hardware, but O-RAN is just this disruptive change to this industry, but it's also compute intensive. So from Dell's perspective, what are the challenges of getting customers to the carriers to adopt O-RAN? How do you de-risk it for them? >> Right, I mean O-RAN really needs to be seen as a choice, right? And that choice comes with building out an ecosystem of partners, right? Working with people like Fuijitsu and others helps us build systems that the carriers can rely upon. Otherwise, it looks like another science experiment, a sandbox, and it's really anything but that. >> So what specifically are you guys doing together? Are you doing integrations, reference architectures engineered systems, all of the above? >> Yeah, so I think it's a little bit of all of the above. So we've announced our cooperation, so the engineering teams are linked, and that we're combining our both sweet spots together from Fuijitsu's virtual CU/DU, and our OpenRAN radios, and Dell's platforms and integration capabilities. And together we're offering a pre-integrated bundle to operators to reduce that risk and kind of help overcome some of the startup obstacles by shrinking the integration cost. >> So you've got Greenfield customers, that's pretty straightforward, white sheet of paper, go, go disrupt. And then there's traditional carriers, got 4G and 5G networks, and sort of hybrid if you will, and this integration there. Where do you see the action now? I presume it's Greenfield today, but isn't it inevitable that the traditional carriers have to go open? >> It is, a couple of different ways that they need to go and they want to go might be power consumption, it might be the cloudification of their network. They're going to have different reasons for doing it. And I think we have to make sure that when we work on collaborations like we do with Fuijitsu, we have to look at all of those vectors. What is it that somebody maybe here in Europe is dealing with high gas prices, high energy prices, in the U.S. or wherever it's expansion. They're going to be different justifications for it. >> Yeah, so power must be an increasing component of the operating expense, with energy costs up, and it's a power hungry environment. So how does OpenRAN solve that problem? >> So that's a great question. So by working together we can really optimize the configurations. So on the Fuijitsu side, our radios are multi-band and highly compact and super energy efficient so that the TCO for the carrier is much, much lower. And then we've also announced on the rApp side power savings, energy savings applications, which are really sophisticated AI enabled apps that can switch off the radio based upon traffic prediction models and we can save the operator 30% on their energy bill. That's a big number. >> And that intelligence that lives in the, does it live in the RIC, is it in the brain? >> In the app right above the RIC, absolutely. >> Okay, so it's a purpose-built app to deal with that. >> It's multi-vendor app, it can sit on anybody's O-RAN system. And one of the beauties of O-RAN is there is that open architecture, so that even if Dell and Fuijitsu only sell part of the, or none of the system, an app can be selected from any vendor including Fuijitsu. So that's one of the benefits of whoever's got the best idea, the best cost performance, the best energy performance, customers can really be enabled to make the choice and continue to make choices, not just way back at RFP time, but throughout their life cycle they can keep making choices. And so that's really meaning that, hey, if we miss the buying cycle then we're closed out for 5 or 10 years. No, it's constantly being reevaluated, and that's really exciting, the whole ecosystem. But what we really want to do is make sure we partner together with key partners, Dell and Fuijitsu, such that the customer, when they do select us they see a bundle, not just every person for themselves. It de-risks it. And we get a lot of that integration headache out of the way before we launch it. >> I think that's what's different. We've been talking about how we've kind of seen this move before, in the nineties we saw the move from the mainframe vertical stack to the horizontal stack. We talked about that, but there are real differences because back then you had, I don't know, five components of the stack and there was no integration, and even converged infrastructure was kind of bolts that brought that together. And then over time it's become engineered systems. When you talk to customers, Ryan, is the conversation today mostly TCO? Is it how to get the reliability and quality of service of traditional stacks? Where's the conversation today? >> Yeah, it's the flip side of choice, which is how do you make sure you have that reliability and that security to ensure that the full stack isn't just integrated, but it lives through that whole life cycle management. What are, if you're bringing in another piece, an rApp or an xApp, how do you actually make sure that it works together as a group? Because if you don't have that kind of assurance how can you actually guarantee that O-RAN in and of itself is going to perform better than a traditional RAN system? So overcoming that barrier requires partnerships and integration activity. That is an investment on the parts of our companies, but also the operators need to look back at us and say, yeah, that work has been done, and I trust as trusted advisors for the operators that that's been done. And then we can go validate it. >> Help our audience understand it. At what point in time do you feel that from a TCO perspective there'll be parity, or in my opinion it doesn't even have to be equal. It has to be close enough. And I don't know what that close enough is because the other benefits of openness, the innovation, so there's that piece of it as the cost piece and then there is the reliability. And I would say the same thing. It's got to be, well, maybe good enough is not good enough in this world, but maybe it is for some use cases. So really my question is around adoption and what are those factors that are going to affect adoption and when can we expect them to be? >> It's a good question, Dave, and what I would say is that the closed RAN vendors are making incremental improvements. And if you think in a snapshot there might be one answer, but if you think in kind of a flow model, a river over time, our O-RAN like-minded people are on a monster innovation curve. I mean the slope of the curve is huge. So in the OpenRAN policy coalition, 60 like-minded companies working together going north, and we're saying that let's bring all the innovation together, so you can say TCO, reliability, but we're bringing the innovation curve of software and integration curve from silicon and integration from system vendors all together to really out-innovate everybody else by working together. So that's the-- >> I like that curve analogy, Greg 'cause okay, you got the ogive or S curve, and you're saying that O-RAN is entering or maybe even before the steep part of the S curve, so you're going to go hyperbolic, whereas the traditional vendors are maybe trying to squeeze a little bit more out of the lemon. >> 1, 2%, and we're making 30% or more quantum leaps at a time every innovation. So what we tell customers is you can measure right now, but if you just do the time-based competition model, as an organization, as a group of us, we're going to be ahead. >> Is it a Moore's law innovation curve or is it actually faster because you've got the combinatorial factors of silicon, certain telco technologies, other integration software. Is it actually steeper than maybe historical Moore's law? >> I think it's steeper. I don't know Ryan's opinion, but I think it's steeper because Moore's law, well-known in silicon, and it's reaching five nanometers and more and more innovations. But now we're talking about AI software and machine learning as well as the system and device vendors. So when all that's combined, what is that? So that's why I think we're at an O-RAN conference today. I'm not sure we're at MWC. >> Well, it's true. It's funny they changed the name from Mobile World Congress and that was never really meant to be a consumer show, but these things change that, right? And so I think it's appropriate MWC because we're seeing really deep enterprise technology now enter, so that's your sweet spot, isn't it? >> It really is. But I think in some ways it's the path to that price performance parity, which we saw in IT a long time ago, making its way into telecom is there, but it doesn't work unless everybody is on board. And that involves players like this and even smaller companies and innovative startups, which we really haven't seen in this space for some time. And we've been having them at the Dell booth all week long. And there's really interesting stuff like Greg said, AI, ML, optimization and efficiency, which is exciting. And that's where O-RAN can also benefit the Industry. >> And as I say, there are other differences to your advantage. You've got engineered systems or you've been through that in enterprise IT, kind of learned how to do that. But you've also got the cloud, public cloud for experimentation, so you can fail cheaply, and you got AI, right, which is, really didn't have AI in the nineties. You had it, but nobody used it. And now you're like, everybody's using ChatGPT. >> Right, but now what's exciting, and the other thing that Ryan and we are working on together is linking our labs together because it's not about the first time system integration and connecting the hoses together, and okay, there it worked, but it's about the ongoing life cycle management of all the updates and upgrades. And by using Dell's OTEL Lab and Fuijitsu's MITC lab and linking them together, now we really have a way of giving operators confidence that as we bring out the new innovations it's battle tested by two organizations. And so two logos coming together and saying, we've looked at it from our different angles and then this is battle tested. There's a lot of value there. >> I think the labs are key. >> But it's interesting, the point there is by tying labs together, there's an acknowledged skills gap as we move into this O-RAN world that operators are looking to us and probably Fuijitsu saying, help our team understand how to thrive in this new environment because we're going from closed systems to open systems where they actually again, have more choice and more ability to be flexible. >> Yeah, if you could take away that plumbing, even though they're good plumbers. All right guys, we got to go. Thanks so much for coming on theCUBE. >> Thank you much. >> It's great to have you. >> Appreciate it, Dave. >> Okay, keep it right there. Dave Vellante, Lisa Martin, and Dave Nicholson will be back from the Fira in Barcelona on theCUBE. Keep it right there. (pleasant music)

>> theCUBE's live coverage is made possible by funding from Dell Technologies, creating technologies that drive human progress. (upbeat music) >> Hey everyone, guys and gals, good to see you. It's theCUBE live in Barcelona at MWC23. Lisa Martin here with Dave Vellante on day one of four days of wall to wall CUBE coverage. Dave, today is ecosystem day. We've had some great conversations about why the open ecosystem is so important and some of the key players in it. >> Well and I'm in search of disruptors, so I'm looking for, okay, who are the network operators that are going to actually lean into the future and drive it and challenge the existing incumbents. We'll talk about that today. >> And we're going to be talking about that next. We've got one of our alumni back with us. Satish Iyer is here, the Vice President of Emerging Services at Dell. Great to have you back on the program. >> Thank you. >> Richard Leitao is with us as well, the Vice President of National Development at DISH Network. Welcome. >> Pleasure to be here. >> So, lots of, this is day one, the theme is velocity. I feel like the day has gone by so quickly. But Dell and DISH have partnered together on a multi-year initiative to build your nationwide cloud-native 5G network that's going to cover a lot of the US. Talk a little bit about that partnership, we'll get both of your perspectives. Richard, we'll start with you. >> Sure. So thank you again for having me. So DISH had the opportunity of, of going through this experience, of innovating once more. For the ones that know DISH, DISH is a company that was founded in 1980 by an innovator, a disruptor. Of course, in the course of the next 40 years, we had the opportunities of even disrupting ourselves. We launched our first satellite TV service. We then launched the first streaming, video streaming platform, disrupting our own satellite business. And since 2008, we have been acquiring Spectrum and, you know, Spectrum, the most valuable asset of a wireless operator. We felt that this was the right opportunity, having 5G , having O-RAN, and we decided to go full in in a greenfield project building national network, 5G O-RAN cloud-based network, one of a kind network in in the US and, and most of all, using O-RAN, it's very important to us, what, what it can bring and it can bring to DISH but to the entire ecosystem of, of this sector in the US. >> Satish, talk a little bit about the partnership from Dell's perspective and some of the unique advantages that Dell is delivering to DISH. >> Oh absolutely. Again, like Richard was saying, I mean the telecom network is being desegregated as we speak. You know, companies like DISH and everybody else is looking at what are the best-in-class technologies we can bring to the table. I would like to say that, you know, the cloud is coming to the telco world, right? A lot of us have seen the tremendous transformation in the cloud world in the last few years. Now, you know, DISH is a big enterprise company. As you know, you know, we are pretty strong within the cloud space and enterprise space. So what we try to work with DISH is Dell, is to bring to DISH is, you know, that notion of cloud scale and the cloud ecosystem into telecom, right? By means best-in-class infrastructure products, best-in-class software products, to allow somebody like DISH to innovate and incre, you know, basically expand and build their O-RAN network. So it's absolutely important for us as we build and get into the telecom space to work with somebody like DISH who's also disrupting as a carrier in that space. >> So it's early days for Open RAN but you've decided, "okay, we're all in". >> Yeah. >> Right? So (chuckling) you burn the bridge, as they say, "go for it". (Lisa chuckles) So when you talk to most people, they say, "okay, it's, it's, it's, it's immature." It's got to be able to get to the levels of, of the, the the hardened stack reliability. But of course it brings the advantage of flexibility and speed. Are you optimizing for one or the other right now? How are you dealing with that balance? >> Well, it, it's, it's not mature in the sense that most of operators that think about it, they have a legacy network. And in order to go full in on the O-RAN side, they need to scrap a lot of things that they have and honestly, they don't want, and it doesn't make sense. So being a greenfield operator, give us that advantage. Give us the advantage and, and desegregation, it's all about chip sets, boxes and software and the chip sets part and what I like the most in desegregation is the time of innovation. The time that we can use new chip sets coming into the market, the size of the boxes that we are using. Obviously our footprint onsite is much smaller than traditional carriers or proprietary systems. So all of that Dell has been critical in supporting us. Supporting us having the best chip sets, having the smallest footprint and, you know, the software, the cycle of innovation is much faster than in proprietary systems. So ma-, it's maturing. I'm glad to say that probably two years ago here O-RAN was more like a, a pilot type of technology. It is not, we are live, we are live for more than 30 million customers in the US and, you know, the performance levels are very similar to traditional networks. >> So you don't just buy a nationwide cloud-native 5G network out of the box, you got to- >> No, you don't. >> You got to build it. So I'm curious as to what Dell's role is in that, in that build out. >> Right? >> How and how, I'm really curious how to, how you would grade Dell but we'll get there. >> Yeah, I mean, look, yes, you don't. So I think the, the, the first and foremost is again, as, as we, Dell, comes into the telco space, one of the things we have to look at is to understand what makes Dell better in the enterprise space, right? It is the best-in-class infrastructure. It is the software ties together. As you talk about desegregated networks, it's important to understand lot of these piece parts have to still be touched together, right? So I think the integration and integration aspects becomes really key which is really Dell is very good at. So one of the things we are working really closely with DISH Tech, you know Richard was alluding to, is bringing all, not just bringing all the software and hardware assets together, but how do you continuously innovate and keep fixing things faster, right? So in the old days, traditional ways, you have a software stack, it takes you 18 months, 20 months to actually get an upgrade done. Here we have continuously CI/CD pipelines where if you want to a change done within, within a week's or within a few days, where we can actually go and test and make sure these things work. So I think a lot of the best enterprise software practices, cloud practices, combined with whatever needs for telco, actually is what makes it very unique. >> I, I saw that this started out as an FCC compliance initiative that turned into a partnership, obviously a very successful one. Richard, talk about what DISH saw in Dell that really made it the right choice, knowing you have choices, you have options. >> You know, we saw the capability to execute, but we also saw the capability to innovate. From an execution level, at the end of the day, like we were talking, we started the project in the middle of COVID, and we had the first mandate to cover 20% of the US population by June, 2022. And now we have a second one, 70% of US population by June 2023. At the beginning of the project, it was all about availability of materials, logistics, how to distribute, how to transport material. So Dell has a world-class supply chain, we felt that working with Dell through all these challenges made things easier. So from an execution perspective, whenever you need to build a network and you, you are building thousands of sites, you need to have materials, you need to distribute them and you need to install them. Dell helped us across the board. Our expectations obviously will change. We have a network, we want to cooperate with Dell in many other areas. We want to, you know, leverage on Dell ability to reach the enterprise market, to have private 5G offers. So hopefully this collaboration will endure in time and, and, you know, will change and evolve in time. >> And it's a big bet. I mean, it's not like a single, it's not like a little transaction that you guys are doing. I feel like, you know Michael Dell and Eric Carlson had dinner and they said, "okay, we're going to, we're going to partner up and this is going to be a multi-decade partnership. You had to be transparent, "Hey, we're new at this, even though we're really good at enterprise tech and so you're going to, obviously if you take a chance on us, here's what we promise you." >> Absolutely. >> And vice versa, you guys had to say, "all right, hey, we're willing to roll the dice because we're trying to change the world." So what was that dynamic like? I mean, how did, I'm curious as to this has to be a lot of different levels, engineering, senior management, board level discussions. >> You know, we felt a huge buy-in from Dell on the Open RAN concept. >> Right. >> Yeah, okay. >> And, you know, edge computing and, and the ability to get us the best product and evolve the best product, Intel is is critical in all these offerings. Intel has a great relationship with Dell. Dell helped us. Dell sponsored the DISH program and some of these suppliers, So it was definitely good to have their support and the buy-in on the O-RAN concept. We felt it from day one and we felt secure on that. >> Yeah, I mean, I, to add to that, I mean, you know DISH was very instrumental in driving, dictating and executing to our roadmap, right? They're one of the key, I mean, since they are out there and they're really turning in a way, it's important that a customer who's actually at the out front of innovation, helps us drive our own roadmap. So to Richard's point, a lot of our product roadmaps, in terms of what have you built and all that, was based on what DISH thinks as going to be market-based requirements. They also helped us a lot in the integration aspects. Like I said, one of the things about open desegregation of these networks is there is a lot of integration because, you know, there is, it's not a one, one monolithic pipe smokestack anymore. You are picking up best-in-class pieces, bits and pieces and tying it together. And it's important to understand when you tie it together things will go wrong, right? So there is a lot of learnings from an integration standpoint. Supportability, deployment, one of the things Richard talked about was supply chain, you know. Other Dell's ability to, lot of these deployments, a lot of these configs in the factory, right, in the second part. So especially a lot of these partnerships started during COVID time and as you all know, you know what we went through two years ago. So we had to make sure that lot of these things are done in one place and a factory, and not done in the field because we couldn't do a lot of these things. So there's a lot of, lot of experimentation, lot of, lot, lot of innovation on that. >> So it's 2030, what's this look like? What's the vision if we can work backwards from there? Well, a, a great network coverage to the entire country, bringing new services to enterprises, to verticals, bringing value add to customers and, you know, technology cycles, they are lasting much less than they were. I cannot even say what will happen in three years. 2030, I mean, I know, I know somebody has a vision for 2030. That's another thing. (everyone laughs) >> A lot of it is "build it and they will come", right? >> Yeah. >> I mean it really is right? You put that network in place and then innovation happens on top. That's the best thing. >> Yeah. And look and and I think the biggest people think about Open RAN in terms of cost, which, you know, you, you have some things in cost that you appreciate in Open RAN. The footprint, the the possibility to diversify suppliers and and have more competition. But for me, Open RAN is about innovation and cycles of innovation. I used to work for Nokia, I used to work for Alcatel. I knew from the generation of an idea to an execution and having a feature delivered to a certain customer, it, it took months. We want innovation to take weeks. We are innovating at the speed, speed of the cloud. We are cooperating with new players, players on the cloud and, and we expect things to happen much faster than they traditionally happen on the telecom sector. >> Move fast and break things. >> Well, we also expect that speed- >> Break and fix. (everyone laughs) >> Yeah, thank you for that. >> But speaking of speed, your customers expect that, right? They expect the service to be up 24/7. They expect to be able to access whatever content they want, whenever they want from wherever they are. So comment, Richard, in our last few minutes here of, of how the, the Dell partnership is helping DISH to really deliver the excellent customer experience that your customers just expect that you're going to deliver. >> Well by setting up the system, number one, we are leveraging on a number of services. And I mentioned the supply chain, but in reality Dell made much more than that for our 20% milestone and is supporting our 70% milestone by installing, testing, verifying most of our data center equipment. We found that this offering from Dell was really addressing some of our needs because, you know, we, we believe they know a lot in this area and they, they can provide the best advice and the best speed to market in, in terms of having this equipment. Because we are working on a time clock, we need to have this done as soon as possible. You know for the future, I hope that they can help us in driving more services. I hope they can bring all the infrastructure that we need to offer to our customers. And, you know, we keep committed to O-RAN. O-RAN is really important. We are not compromising that. And I think the future is bright for both of us. >> Yeah, and Dell learns from the experience. >> Exactly. >> Absolutely. >> There's got to be a catalyst for expanding your roadmap and vision in telecom. >> Yeah, I mean, like you said, I mean, you asked a 2030 question and I think that, you know, know six, seven years from now I think people should look at what DISH and Dell and say they were the trailblazers of make, bringing Open RAN to the market and making 5G a reality. I mean, you talk about 5G, but every 5G is on a different stages. I do think that this combination, this partnership has the best chance to be the first ones to actually have a truly Open RAN network to be successful in commercial. >> Awesome guys. Trailblazers, Dell and DISH. Well, we look forward to watching this story unfold. Thank you- >> Thank you. >> for joining Dave and me on the program today talking about what you're doing together. We appreciate it. >> Thanks for having us. >> Our pleasure. >> Thank you, bye. >> For our guests and for Dave Vellante, I'm Lisa Martin. You're watching theCUBE live from Barcelona at MWC23. We'll be back after a short break, so we'll see you soon.

>> Announcer: theCUBE's live coverage is made possible by funding from Dell Technologies, creating technologies that drive human progress. (upbeat music) >> Welcome to the Fira in Barcelona, everybody. This is theCUBE's coverage of MWC 23, day one of that coverage. We have four days of wall-to-wall action going on, the place is going crazy. I'm here with Dave Nicholson, Lisa Martin is also in the house. Today's ecosystem day, and we're really excited to have Manish Singh who's the CTO of the Telecom Systems Business unit at Dell Technologies. He's joined by Doug Wolf who's the head of strategy for the Telecom Systems Business unit at Dell. Gents, welcome. What a show. I mean really the first major MWC or used to be Mobile World Congress since you guys have launched your telecom business, you kind of did that sort of in the Covid transition, but really exciting, obviously a huge, huge venue to match the huge market. So Manish, how did you guys get into this? What did you see? What was the overall thinking to get Dell into this business? >> Manish: Yeah, well, I mean just to start with you know, if you look at the telecom ecosystem today, the service providers in particular, they are looking for network transformation, driving more disaggregation into their network so that they can get better utilization of the infrastructure, but then also get more agility, more cloud native characteristics onto their, for their networks in particular. And then further on, it's important for them to really start to accelerate the pace of innovation on the networks itself, to start more supply chain diversity, that's one of the challenges that they've been having. And so there've been all these market forces that have been really getting these service providers to really start to transform the way they have built the infrastructure in the past, which was legacy monolithic architectures to more cloud native disaggregated. And from a Dell perspective, you know, that really gives us the permission to play, to really, given all the expertise on the work we have done in the IT with all the IT transformations to leverage all that expertise and bring that to the service providers and really help them in accelerating their network transformation. So that's where the journey started. We've been obviously ever since then working on expanding the product portfolio on our compute platforms to bring Teleco great compute platforms with more capabilities than we can talk about that. But then working with partners and building the ecosystem to again create this disaggregated and open ecosystem that will be more cloud native and really meet the objective that the service providers are after. >> Dave Vellante: Great, thank you. So, Doug the strategy obviously is to attack this market, as Manish said, from an open standpoint, that's sort of new territory. It's like a little bit like the wild, wild west. So maybe you could double click on what Manish was saying from a, from a strategy standpoint, yes, the Telecos need to be more flexible, they need to be more open, but they also need this reliability piece. So talk about that from a strategy standpoint of what you guys saw. >> Doug: Yeah, absolutely. As Manish mentioned, you know, Dell getting into open systems isn't something new. You know, Dell has been kind of playing in that world for years and years, but the opportunity in Telecom that came was opening of the RAN, the core network, the edge, all of these with 5G really created a wide opening for us. So we started developing products and solutions, you know, built our first Telecom grade servers for open RAN over the last year, we'll talk about those at the show. But you know, as, as Manish mentioned, an open ecosystem is new to Telecom. I've been in the Telecom business along with Manish for, you know, 25 plus years and this is a new thing that they're embarking on. So started with virtualization about five, six years ago, and now moving to cloud native architectures on the core, suddenly there's this need to have multiple parties partner really well, share specifications, and put that together for an operator to consume. And I think that's just the start of really where all the challenges are and the opportunities that we see. >> Where are we in this transition cycle? When the average consumer hears 5G, feels like it's been around for a long time because it was hyped beforehand. >> Doug: Yeah. >> If you're talking about moving to an open infrastructure model from a proprietary closed model, when is the opportunity for Dell to become part of that? Is it, are there specific sites that have already transitioned to 5G, therefore they've either made the decision to be open or not? Or are there places where the 5G transition has taken place, and they might then make a transition to open brand with 5G? Where, where are we in that cycle? What does the opportunity look like? >> I'll kind of take it from the typology of the operator, and I'm sure Manish will build on this, but if I look back on the core, started to get virtualized you know, back around 2015-16 with some of the lead operators like AT&T et cetera. So Dell has been partnering with those operators for some years. So it really, it's happening on the core, but it's moving with 5G to more of a cloud-like architecture, number one. And number two, they're going beyond just virtualizing the network. You know, they previously had used OpenStack and most of them are migrating to more of a cloud native architecture that Manish mentioned. And that is a bit different in terms of there's more software vendors in that ecosystem because the software is disaggregated also. So Dell's been playing in the core for a number of years, but we brought out new solutions we've announced at the show for the core. And the parts that are really starting that transition of maybe where the core was back in 2015 is on the RAN and on the edge in particular. >> Because NFV kind of predated the ascendancy of cloud. >> Exactly, yeah. >> Right, so it really didn't have the impact that people had hoped. And there's some, when you look back, 'cause it's not same wine, new bottle as the open systems movement, there are a lot of similarities but you know, you mentioned cloud, and cloud native, you really didn't have, back in the nineties, true engineered systems. You didn't really have AI that, you know, to speak of at the sort of volume of the data that we have. So Manish, from a CTO's perspective, how are you attacking some of those differences in bringing that to market? >> Manish: Yeah, I mean, I think you touched on some very important points there. So first of all, the duck's point, a lot of this transformation started in the core, right? And as the technology evolution progress, the opportunities opened up. It has now come into the edge and the radio access network as well, in particular with open RAN. And so when we talk about the disaggregation of the infrastructure from the software itself and an open ecosystem, this now starts to create the opportunity to accelerate innovation. And I really want to pick up on the point that you'd said on AI, for example. AI and machine learning bring a whole new set of capabilities and opportunities for these service providers to drive better optimization, better performance, better sustainability and energy efficiency on their infrastructure, on and on and on. But to really tap into these technologies, they really need to open that up to third parties implementation solutions that are coming up. And again, the end objective remains to accelerate that innovation. Now that said, all these things need to be brought together, right? And delivered and deployed in the network without any degradation in the KPIs and actually improving the performance on different vectors, right? So this is what the current state of play is. And with this aggregation I'm definitely a believer that all these new technologies, including AI, machine learning, and there's a whole area, host area of problems that can be solved and attacked and are actually getting attacked by applying AI and machine learning onto these networks. >> Open obviously is good. Nobody's ever going to, you know, argue that open is a bad thing. It's like democracy is a good thing, right? At least amongst us. And so, but, the RAN, the open RAN, has to be as reliable and performant, right, as these, closed networks. Or maybe not, maybe it doesn't have to be identical. Just has to be close enough in order for that tipping point to occur. Is that a fair summarization? What are you guys hearing from carriers in terms of their willingness to sort of put their toe in the water and, and what could we expect in terms of the maturity model of, of open RAN and adoption? >> Right, so I mean I think on, on performance that, that's a tough one. I think the operators will demand performance and you've seen experiments, you've really seen more of the Greenfield operators kind of launch. >> Okay. >> Doug: Open RAN or vRAN type solutions. >> So they're going to disrupt. >> Doug: Yeah, they're going to disrupt. >> Yeah. >> Doug: And there's flexibility in an open RAN architecture also for 5G that they, that they're interested in and I think the Brownfield operators are too, but let's say maybe the Greenfield jump first in terms of doing that from a mass deployment perspective. But I still think that it's going to be critical to meet very similar SLAs and end user performance. And, you know, I think that's where, you know, maturity of that model is what's required. I think Brownfield operators are conservative in terms of, you know, going with something they know, but the opportunities and the benefits of that architecture and building new flexible, potentially cost advantaged over time solutions, that's what the, where the real interest is going forward. >> And new services that you can introduce much more quickly. You know, the interesting thing about Dell to me, you don't compete with the carriers, the public cloud vendors though, the carriers are concerned about them sort of doing an end run on them. So you provide a potential partnership for the carriers that's non-threatening, right? 'Cause you're, you're an arms dealer, you're selling hardware and software, right? But, but how do you see that? Because we heard in the keynote today, one of the Teleco, I think it was the chairman of Telefonica said, you know, cloud guys can't do this alone. You know, they need, you know, this massive, you know, build out. And so, what do you think about that in terms of your relationship with the carriers not being threatening? I mean versus say potentially the cloud guys, who are also your partners, I understand, it's a really interesting dynamic, isn't it? >> Manish: Yeah, I mean I think, you know, I mean, the way I look at it, the carriers actually need someone like Dell who really come in who can bring in the right capabilities, the right infrastructure, but also bring in the ecosystem together and deliver a performance solution that they can deploy and that they can trust, number one. Number two, to your point on cloud, I mean, from a Dell perspective, you know, we announced our Dell Telecom Multicloud Foundation and as part of that last year in September, we announced what we call is the Dell Telecom Infrastructure Blocks. The first one we announced with Wind River, and this is, think of it as the, you know, hardware and the cashier all pre-integrated with lot of automation around it, factory integrated, you know, delivered to customers in an integrated model with all the licenses, everything. And so it starts to solve the day zero, day one, day two integration deployment and then lifecycle management for them. So to broaden the discussion, our view is it's a multicloud world, the future is multicloud where you can have different clouds which can be optimized for different workloads. So for example, while our work with Wind River initially was very focused on virtualization of the radio access network, we just announced our infrastructure block with Red Hat, which is very much targeted and optimized for core network and edge, right? So, you know, there are different workflows which will require different capabilities also. And so, you know, again, we are bringing those things to these service providers to again, bring those cloud characteristics and cloud native architecture for their network. >> And It's going to be hybrid, to your point. >> David N.: And you, just hit on something, you said cloud characteristics. >> Yeah. >> If you look at this through the lens of kind of the general world of IT, sometimes when people hear the word cloud, they immediately leap to the idea that it's a hyperscale cloud provider. In this scenario we're talking about radio towers that have intelligence living on them and physically at the base. And so the cloud characteristics that you're delivering might be living physically in these remote locations all over the place, is that correct? >> Yeah, I mean that, that's true. That will definitely happen over time. But I think, I think we've seen the hyperscalers enter, you know, public cloud providers, enter at the edge and they're dabbling maybe with private, but I think the public RAN is another further challenge. I think that maybe a little bit down the road for them. So I think that is a different characteristic that you're talking about managing the macro RAN environment. >> Manish: If I may just add one more perspective of this cloud, and I mean, again, the hyperscale cloud, right? I mean that world's been great when you can centralize a lot of compute capability and you can then start to, you know, do workload aggregation and use the infrastructure more efficient. When it comes to Telecom, it is inherently it distributed architecture where you have access, you talked about radio access, your port, and it is inherently distributed because it has to provide the coverage and capacity. And so, you know, it does require different kind of capabilities when you're going out and about, and this is where I was talking about things like, you know, we just talked, we just have been working on our bare metal orchestration, right? This is what we are bringing is a capability where you can actually have distributed infrastructure, you can deploy, you can actually manage, do lifecycle management, in a distributed multicloud form. So it does require, you know, different set of capabilities that need to be enabled. >> Some, when talking about cloud, would argue that it's always been information technology, it always will be information technology, and especially as what we might refer to as public cloud or hyperscale cloud providers, are delivering things essentially on premises. It's like, well, is that cloud? Because it feels like some of those players are going to be delivering physical infrastructure outside of their own data centers in order to address this. It seems the nature, the nature of the beast is that some of these things need to be distributed. So it seems perfectly situated for Dell. That's why you guys are both at Dell now and not working for other Telecom places, right? >> Exactly. Exactly, yes. >> It's definitely an exciting space. It's transformed, the networks are under transformation and I do think that Dell's very well positioned to, to really help the customers, the service providers in accelerating their transformation journey with an open ecosystem. >> Dave V.: You've got the brand, and the breadth, and the resources to actually attract an ecosystem. But I wonder if you could sort of take us through your strategy of ecosystem, the challenges that you've seen in developing that ecosystem and what the vision is that ultimately, what's the outcome going to be of that open ecosystem? >> Yeah, I can start. So maybe just to give you the big picture, right? I mean the big picture, is disaggregation with performance, right, TCO models to the service providers, right? And it starts at the infrastructure layer, builds on bringing these cloud capabilities, the cast layer, right? Bringing the right accelerators. All of this requires to pull the ecosystem. So give you an example on the infrastructure in a Teleco grade servers like XR8000 with Sapphire, the new intel processors that we've just announced, and an extended array of servers. These are Teleco grade, short depth, et cetera. You know, the Teleco great characteristic. Working with the partners like Marvel for bringing in the accelerators in there, that's important to again, drive the performance and optimize for the TCO. Working then with partners like Wind River, Red Hat, et cetera, to bring in the cast capabilities so you can start to see how this ecosystem starts to build up. And then very recently we announced our private 5G solution with AirSpan and Expeto on the core site. So bringing those workloads together. Similarly, we have an open RAN solution we announce with Fujitsu. So it's, it's open, it's disaggregated, but bringing all these together. And one of the last things I would say is, you know, to make all this happen and make all of these, we've also been putting together our OTEL, our open Telecom ecosystem lab, which is very much geared, really gives this open ecosystem a playground where they can come in and do all that heavy lifting, which is anyways required, to do the integration, optimization, and board. So put all these capabilities in place, but the end goal, the end vision again, is that cloud native disaggregated infrastructure that starts to innovate at the speed of software and scales at the speed of cloud. >> And this is different than the nineties. You didn't have something like OTEL back then, you know, you didn't have the developer ecosystem that you have today because on top of everything that you just said, Manish, are new workloads and new applications that are going to be developed. Doug, anything you'd add to what Manish said? >> Doug: Yeah, I mean, as Manish said, I think adding to the infrastructure layers, which are, you know, critical for us to, to help integrate, right? Because we kind of took a vertical Teleco stack and we've disaggregated it, and it's gotten a little bit more complex. So our Solutions Dell Technology infrastructure block, and our lab infrastructure with OTEL, helps put those pieces together. But without the software players in this, you know, that's what we really do, I think in OTEL. And that's just starting to grow. So integrating with those software providers with that integration is something that the operators need. So we fill a gap there in terms of either providing engineered solutions so they can readily build on or actually bringing in that software provider. And I think that's what you're going to see more from us going forward is just extending that ecosystem even further. More software players effectively. >> In thinking about O-RAN, are they, is it possible to have the low latency, the high performance, the reliability capabilities that carriers are used to and the flexibility? Or can you sort of prioritize one over the other from a go to market and rollout standpoint and optimize one, maybe get a foothold in the market? How do you see that balance? >> Manish: Oh the answer is absolutely yes you can have both We are on that journey, we are on that journey. This is where all these things I was talking about in terms of the right kind of accelerators, right kind of capabilities on the infrastructure, obviously retargeting the software, there are certain changes, et cetera that need to be done on the software itself to make it more cloud native. And then building all the surrounding capabilities around the CICD pipeline and all where it's not just day zero or day one that you're doing the cloud-like lifecycle management of this infrastructure. But the answer to your point, yes, absolutely. It's possible, the technology is there, and the ecosystem is coming together, and that's the direction. Now, are there challenges? Absolutely there are challenges, but directionally that's the direction the industry is moving to. >> Dave V.: I guess my question, Manish, is do they have to go in lockstep? Because I would argue that the public cloud when it first came out wasn't nearly as functional as what I could get from my own data center in terms of recovery, you know, backup and recovery is a perfect example and it took, you know, a decade plus to get there. But it was the flexibility, and the openness, and the developer affinity, the programmability, that attracted people. Do you see O-RAN following a similar path? Or does it, my question is does it have to have that carrier class reliability today? >> David N.: Everything on day one, does it have to have everything on day one? >> Yeah, I mean, I would say, you know, like again, the Greenfield operators I think we're, we're willing do a little bit more experimentation. I think the operators, Brownfield operators that have existing, you know, deployments, they're going to want to be closer. But I think there's room for innovation here. And clearly, you know, Manish came from, from Meta and we're, we've been very involved with TIP, we're very involved with the O-RAN alliance, and as Manish mentioned, with all those accelerators that we're working with on our infrastructure, that is a space that we're trying to help move the ball forward. So I think you're seeing deployments from mainstream operators, but it's maybe not in, you know, downtown New York deployment, they're more rural deployments. I think that's getting at, you know, kind of your question is there's maybe a little bit more flexibility there, they get to experiment with the technology and the flexibility and then I think it will start to evolve >> Dave V.: And that's where the disruption's going to come from, I think. >> David N.: Well, where was the first place you could get reliable 4K streaming of video content? It wasn't ABC, CBS, NBC. It was YouTube. >> Right. >> So is it possible that when you say Greenfield, are a lot of those going to be what we refer to as private 5G networks where someone may set up a private 5G network that has more functions and capabilities than the public network? >> That's exactly where I was going is that, you know, that that's why you're seeing us getting very active in 5G solutions that Manish mentioned with, you know, Expeto and AirSpan. There's more of those that we haven't publicly announced. So I think you'll be seeing more announcements from us, but that is really, you know, a new opportunity. And there's spectrum there also, right? I mean, there's public and private spectrum. We plan to work directly with the operators and do it in their spectrum when needed. But we also have solutions that will do it, you know, on non-public spectrum. >> So let's close out, oh go ahead. You you have something to add there? >> I'm just going to add one more point to Doug's point, right? Is if you look on the private 5G and the end customer, it's the enterprise, right? And they're, they're not a service provider. They're not a carrier. They're more used to deploying, you know, enterprise infrastructure, maintaining, managing that. So, you know, private 5G, especially with this open ecosystem and with all the open run capabilities, it naturally tends to, you know, blend itself very well to meet those requirements that the enterprise would have. >> And people should not think of private 5G as a sort of a replacement for wifi, right? It's to to deal with those, you know, intense situations that can afford the additional cost, but absolutely require the reliability and the performance and, you know, never go down type of scenario. Is that right? >> Doug: And low latencies usually, the primary characteristics, you know, for things like Industry 4.0 manufacturing requirements, those are tough SLAs. They're just, they're different than the operator SLAs for coverage and, you know, cell performance. They're now, you know, Five9 type characteristics, but on a manufacturing floor. >> That's why we don't use wifi on theCUBE to broadcast, we need a hard line. >> Yeah, but why wouldn't it replace wifi over time? I mean, you know, I still have a home phone number that's hardwired to align, but it goes to a voicemail. We don't even have handset anymore for it, yeah. >> I think, well, unless the cost can come down, but I think that wifi is flexible, it's cheap. It's, it's kind of perfect for that. >> Manish: And it's good technology. >> Dave V.: And it works great. >> David N.: For now, for now. >> Dave V.: But you wouldn't want it in those situations, and you're arguing that maybe. >> I'm saying eventually, what, put a sim in a device, I don't know, you know, but why not? >> Yeah, I mean, you know, and Dell offers, you know, from our laptop, you know, our client side, we do offer wifi, we do offer 4G and 5G solutions. And I think those, you know, it's a volume and scale issue, I think for the cost structure you're talking about. >> Manish: Come to our booth and see the connected laptop. >> Dave V.: Well let's, let's close on that. Why don't you guys talk a little bit about what you're going on at the show, I did go by the booth, you got a whole big lineup of servers. You got some, you know, cool devices going on. So give us the rundown and you know, let's end with the takeaways here. >> The simple rundown, a broad range of new powered servers, broad range addressing core, edge, RAN, optimized for those with all the different kind of acceleration capabilities. You can see that, you can see infrastructure blocks. These are with Wind River, with Red Hat. You can see OTEL, the open telecom ecosystem lab where all that playground, the integration, the real work, the real sausage makings happening. And then you will see some interesting solutions in terms of co-creation that we are doing, right? So you, you will see all of that and not to forget the connected laptops. >> Dave V.: Yeah, yeah, cool. >> Doug: Yeah and, we mentioned it before, but just to add on, I think, you know, for private 5G, you know, we've announced a few offers here at the show with partners. So with Expeto and AirSpan in particular, and I think, you know, I just want to emphasize the partnerships that we're doing. You know, we're doing some, you know, fundamental integration on infrastructure, bare metal and different options for the operators to get engineered systems. But building on that ecosystem is really, the move to cloud native is where Dell is trying to get in front of. And we're offering solutions and a much larger ecosystem to go after it. >> Dave V.: Great. Manish and Doug, thanks for coming on the program. It was great to have you, awesome discussion. >> Thank you for having us. >> Thanks for having us. >> All right, Dave Vellante for Dave Nicholson and Lisa Martin. We're seeing the disaggregation of the Teleco network into open ecosystems with integration from companies like Dell and others. Keep it right there for theCUBE's coverage of MWC 23. We'll be right back. (upbeat tech music)

>> From the Cube Studios in Palo Alto in Boston, bringing you data-driven insights from The Cube and ETR. This is "Breaking Analysis" with Dave Vellante. >> The world's leading telcos are trying to shed the stigma of being monopolies lacking innovation. Telcos have been great at operational efficiency and connectivity and living off of transmission, and the costs and expenses or revenue associated with that transmission. But in a world beyond telephone poles and basic wireless and mobile services, how will telcos modernize and become more agile and monetize new opportunities brought about by 5G and private wireless and a spate of new innovations and infrastructure, cloud data and apps? Hello, and welcome to this week's Wikibon CUBE Insights powered by ETR. In this breaking analysis and ahead of Mobile World Congress or now, MWC23, we explore the evolution of the telco business and how the industry is in many ways, mimicking transformations that took place decades ago in enterprise IT. We'll model some of the traditional enterprise vendors using ETR data and investigate how they're faring in the telecommunications sector, and we'll pose some of the key issues facing the industry this decade. First, let's take a look at what the GSMA has in store for MWC23. GSMA is the host of what used to be called Mobile World Congress. They've set the theme for this year's event as "Velocity" and they've rebranded MWC to reflect the fact that mobile technology is only one part of the story. MWC has become one of the world's premier events highlighting innovations not only in Telco, mobile and 5G, but the collision between cloud, infrastructure, apps, private networks, smart industries, machine intelligence, and AI, and more. MWC comprises an enormous ecosystem of service providers, technology companies, and firms from virtually every industry including sports and entertainment. And as well, GSMA, along with its venue partner at the Fira Barcelona, have placed a major emphasis on sustainability and public and private partnerships. Virtually every industry will be represented at the event because every industry is impacted by the trends and opportunities in this space. GSMA has said it expects 80,000 attendees at MWC this year, not quite back to 2019 levels, but trending in that direction. Of course, attendance from Chinese participants has historically been very high at the show, and obviously the continued travel issues from that region are affecting the overall attendance, but still very strong. And despite these concerns, Huawei, the giant Chinese technology company. has the largest physical presence of any exhibitor at the show. And finally, GSMA estimates that more than $300 million in economic benefit will result from the event which takes place at the end of February and early March. And The Cube will be back at MWC this year with a major presence thanks to our anchor sponsor, Dell Technologies and other supporters of our content program, including Enterprise Web, ArcaOS, VMware, Snowflake, Cisco, AWS, and others. And one of the areas we're interested in exploring is the evolution of the telco stack. It's a topic that's often talked about and one that we've observed taking place in the 1990s when the vertically integrated IBM mainframe monopoly gave way to a disintegrated and horizontal industry structure. And in many ways, the same thing is happening today in telecommunications, which is shown on the left-hand side of this diagram. Historically, telcos have relied on a hardened, integrated, and incredibly reliable, and secure set of hardware and software services that have been fully vetted and tested, and certified, and relied upon for decades. And at the top of that stack on the left are the crown jewels of the telco stack, the operational support systems and the business support systems. For the OSS, we're talking about things like network management, network operations, service delivery, quality of service, fulfillment assurance, and things like that. For the BSS systems, these refer to customer-facing elements of the stack, like revenue, order management, what products they sell, billing, and customer service. And what we're seeing is telcos have been really good at operational efficiency and making money off of transport and connectivity, but they've lacked the innovation in services and applications. They own the pipes and that works well, but others, be the over-the-top content companies, or private network providers and increasingly, cloud providers have been able to bypass the telcos, reach around them, if you will, and drive innovation. And so, the right-most diagram speaks to the need to disaggregate pieces of the stack. And while the similarities to the 1990s in enterprise IT are greater than the differences, there are things that are different. For example, the granularity of hardware infrastructure will not likely be as high where competition occurred back in the 90s at every layer of the value chain with very little infrastructure integration. That of course changed in the 2010s with converged infrastructure and hyper-converged and also software defined. So, that's one difference. And the advent of cloud, containers, microservices, and AI, none of that was really a major factor in the disintegration of legacy IT. And that probably means that disruptors can move even faster than did the likes of Intel and Microsoft, Oracle, Cisco, and the Seagates of the 1990s. As well, while many of the products and services will come from traditional enterprise IT names like Dell, HPE, Cisco, Red Hat, VMware, AWS, Microsoft, Google, et cetera, many of the names are going to be different and come from traditional network equipment providers. These are names like Ericsson and Huawei, and Nokia, and other names, like Wind River, and Rakuten, and Dish Networks. And there are enormous opportunities in data to help telecom companies and their competitors go beyond telemetry data into more advanced analytics and data monetization. There's also going to be an entirely new set of apps based on the workloads and use cases ranging from hospitals, sports arenas, race tracks, shipping ports, you name it. Virtually every vertical will participate in this transformation as the industry evolves its focus toward innovation, agility, and open ecosystems. Now remember, this is not a binary state. There are going to be greenfield companies disrupting the apple cart, but the incumbent telcos are going to have to continue to ensure newer systems work with their legacy infrastructure, in their OSS and BSS existing systems. And as we know, this is not going to be an overnight task. Integration is a difficult thing, transformations, migrations. So that's what makes this all so interesting because others can come in with Greenfield and potentially disrupt. There'll be interesting partnerships and ecosystems will form and coalitions will also form. Now, we mentioned that several traditional enterprise companies are or will be playing in this space. Now, ETR doesn't have a ton of data on specific telecom equipment and software providers, but it does have some interesting data that we cut for this breaking analysis. What we're showing here in this graphic is some of the names that we've followed over the years and how they're faring. Specifically, we did the cut within the telco sector. So the Y-axis here shows net score or spending velocity. And the horizontal axis, that shows the presence or pervasiveness in the data set. And that table insert in the upper left, that informs as to how the dots are plotted. You know, the two columns there, net score and the ends. And that red-dotted line, that horizontal line at 40%, that is an indicator of a highly elevated level. Anything above that, we consider quite outstanding. And what we'll do now is we'll comment on some of the cohorts and share with you how they're doing in telecommunications, and that sector, that vertical relative to their position overall in the data set. Let's start with the public cloud players. They're prominent in every industry. Telcos, telecommunications is no exception and it's quite an interesting cohort here. On the one hand, they can help telecommunication firms modernize and become more agile by eliminating the heavy lifting and you know, all the cloud, you know, value prop, data center costs, and the cloud benefits. At the same time, public cloud players are bringing their services to the edge, building out their own global networks and are a disruptive force to traditional telcos. All right, let's talk about Azure first. Their net score is basically identical to telco relative to its overall average. AWS's net score is higher in telco by just a few percentage points. Google Cloud platform is eight percentage points higher in telco with a 53% net score. So all three hyperscalers have an equal or stronger presence in telco than their average overall. Okay, let's look at the traditional enterprise hardware and software infrastructure cohort. Dell, Cisco, HPE, Red Hat, VMware, and Oracle. We've highlighted in this chart just as sort of indicators or proxies. Dell's net score's 10 percentage points higher in telco than its overall average. Interesting. Cisco's is a bit higher. HPE's is actually lower by about nine percentage points in the ETR survey, and VMware's is lower by about four percentage points. Now, Red Hat is really interesting. OpenStack, as we've previously reported is popular with telcos who want to build out their own private cloud. And the data shows that Red Hat OpenStack's net score is 15 percentage points higher in the telco sector than its overall average. OpenShift, on the other hand, has a net score that's four percentage points lower in telco than its overall average. So this to us talks to the pace of adoption of microservices and containers. You know, it's going to happen, but it's going to happen more slowly. Finally, Oracle's spending momentum is somewhat lower in the sector than its average, despite the firm having a decent telco business. IBM and Accenture, heavy services companies are both lower in this sector than their average. And real quickly, snowflake's net score is much lower by about 12 percentage points relative to its very high average net score of 62%. But we look for them to be a player in this space as telcos need to modernize their analytics stack and share data in a governed manner. Databricks' net score is also much lower than its average by about 13 points. And same, I would expect them to be a player as open architectures and cloud gains steam in telco. All right, let's close out now on what we're going to be talking about at MWC23 and some of the key issues that we'll be unpacking. We've talked about stack disaggregation in this breaking analysis, but the key here will be the pace at which it will reach the operational efficiency and reliability of closed stacks. Telcos, you know, in a large part, they're engineering heavy firms and much of their work takes place, kind of in the basement, in the dark. It's not really a big public hype machine, and they tend to move slowly and cautiously. While they understand the importance of agility, they're going to be careful because, you know, it's in their DNA. And so at the same time, if they don't move fast enough, they're going to get hurt and disrupted by competitors. So that's going to be a topic of conversation, and we'll be looking for proof points. And the other comment I'll make is around integration. Telcos because of their conservatism will benefit from better testing and those firms that can innovate on the testing front and have labs and certifications and innovate at that level, with an ecosystem are going to be in a better position. Because open sometimes means wild west. So the more players like Dell, HPE, Cisco, Red Hat, et cetera, that do that and align with their ecosystems and provide those resources, the faster adoption is going to go. So we'll be looking for, you know, who's actually doing that, Open RAN or Radio Access Networks. That fits in this discussion because O-RAN is an emerging network architecture. It essentially enables the use of open technologies from an ecosystem and over time, look at O-RAN is going to be open, but the questions, you know, a lot of questions remain as to when it will be able to deliver the operational efficiency of traditional RAN. Got some interesting dynamics going on. Rakuten is a company that's working hard on this problem, really focusing on operational efficiency. Then you got Dish Networks. They're also embracing O-RAN. They're coming at it more from service innovation. So that's something that we'll be monitoring and unpacking. We're going to look at cloud as a disruptor. On the one hand, cloud can help drive agility, as we said earlier and optionality, and innovation for incumbent telcos. But the flip side is going to also do the same for startups trying to disrupt and cloud attracts startups. While some of the telcos are actually embracing the cloud, many are being cautious. So that's going to be an interesting topic of discussion. And there's private wireless networks and 5G, and hyperlocal private networks, they're being deployed, you know, at the edge. This idea of open edge is also a really hot topic and this trend is going to accelerate. You know, the importance here is that the use cases are going to be widely varied. The needs of a hospital are going to be different than those of a sports venue are different from a remote drilling location, and energy or a concert venue. Things like real-time AI inference and data flows are going to bring new services and monetization opportunities. And many firms are going to be bypassing traditional telecommunications networks to build these out. Satellites as well, we're going to see, you know, in this decade, you're going to have, you're going to look down at Google Earth and you're going to see real-time. You know, today you see snapshots and so, lots of innovations going in that space. So how is this going to disrupt industries and traditional industry structures? Now, as always, we'll be looking at data angles, right? 'Cause it's in The Cube's DNA to follow the data and what opportunities and risks data brings. The Cube is going to be on location at MWC23 at the end of the month. We got a great set. We're in the walkway between halls four and five, right in Congress Square, it's booths CS60. So we'll have a full, they're called Stan CS60. We have a full schedule. I'm going to be there with Lisa Martin, Dave Nicholson and the entire Cube crew, so don't forget to stop by. All right, that's a wrap. I want to thank Alex Myerson, who's on production and manages the podcast, Ken Schiffman as well. Kristin Martin and Cheryl Knight help get the word out on social media and in our newsletters. And Rob Hof is our editor-in-chief over at Silicon Angle, does some great stuff for us. Thank you all. Remember, all these episodes are available as podcasts. Wherever you listen, just search "Breaking Analysis" podcasts I publish each week on wikibon.com and silicon angle.com. And all the video content is available on demand at thecube.net. You can email me directly at david.vellante@silicon angle.com. You can DM me at dvellante or comment on my LinkedIn post. Please do check out etr.ai for the best survey data in the enterprise tech business. This is Dave Vellante for The Cube Insights powered by ETR. Thanks for watching and we'll see you at Mobile World Congress, and/or at next time on "Breaking Analysis." (bright music) (bright music fades)

>>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.

>>When Oracle acquired my SQL via the Sun acquisition, nobody really thought the company would put much effort into the platform preferring to focus all the wood behind its leading Oracle database, Arrow pun intended. But two years ago, Oracle surprised many folks by announcing my SQL Heatwave a new database as a service with a massively parallel hybrid Columbia in Mary Mary architecture that brings together transactional and analytic data in a single platform. Welcome to our latest database, power panel on the cube. My name is Dave Ante, and today we're gonna discuss Oracle's MySQL Heat Wave with a who's who of cloud database industry analysts. Holgar Mueller is with Constellation Research. Mark Stammer is the Dragon Slayer and Wikibon contributor. And Ron Westfall is with Fu Chim Research. Gentlemen, welcome back to the Cube. Always a pleasure to have you on. Thanks for having us. Great to be here. >>So we've had a number of of deep dive interviews on the Cube with Nip and Aggarwal. You guys know him? He's a senior vice president of MySQL, Heatwave Development at Oracle. I think you just saw him at Oracle Cloud World and he's come on to describe this is gonna, I'll call it a shock and awe feature additions to to heatwave. You know, the company's clearly putting r and d into the platform and I think at at cloud world we saw like the fifth major release since 2020 when they first announced MySQL heat wave. So just listing a few, they, they got, they taken, brought in analytics machine learning, they got autopilot for machine learning, which is automation onto the basic o l TP functionality of the database. And it's been interesting to watch Oracle's converge database strategy. We've contrasted that amongst ourselves. Love to get your thoughts on Amazon's get the right tool for the right job approach. >>Are they gonna have to change that? You know, Amazon's got the specialized databases, it's just, you know, the both companies are doing well. It just shows there are a lot of ways to, to skin a cat cuz you see some traction in the market in, in both approaches. So today we're gonna focus on the latest heat wave announcements and we're gonna talk about multi-cloud with a native MySQL heat wave implementation, which is available on aws MySQL heat wave for Azure via the Oracle Microsoft interconnect. This kind of cool hybrid action that they got going. Sometimes we call it super cloud. And then we're gonna dive into my SQL Heatwave Lake house, which allows users to process and query data across MyQ databases as heatwave databases, as well as object stores. So, and then we've got, heatwave has been announced on AWS and, and, and Azure, they're available now and Lake House I believe is in beta and I think it's coming out the second half of next year. So again, all of our guests are fresh off of Oracle Cloud world in Las Vegas. So they got the latest scoop. Guys, I'm done talking. Let's get into it. Mark, maybe you could start us off, what's your opinion of my SQL Heatwaves competitive position? When you think about what AWS is doing, you know, Google is, you know, we heard Google Cloud next recently, we heard about all their data innovations. You got, obviously Azure's got a big portfolio, snowflakes doing well in the market. What's your take? >>Well, first let's look at it from the point of view that AWS is the market leader in cloud and cloud services. They own somewhere between 30 to 50% depending on who you read of the market. And then you have Azure as number two and after that it falls off. There's gcp, Google Cloud platform, which is further way down the list and then Oracle and IBM and Alibaba. So when you look at AWS and you and Azure saying, hey, these are the market leaders in the cloud, then you start looking at it and saying, if I am going to provide a service that competes with the service they have, if I can make it available in their cloud, it means that I can be more competitive. And if I'm compelling and compelling means at least twice the performance or functionality or both at half the price, I should be able to gain market share. >>And that's what Oracle's done. They've taken a superior product in my SQL heat wave, which is faster, lower cost does more for a lot less at the end of the day and they make it available to the users of those clouds. You avoid this little thing called egress fees, you avoid the issue of having to migrate from one cloud to another and suddenly you have a very compelling offer. So I look at what Oracle's doing with MyQ and it feels like, I'm gonna use a word term, a flanking maneuver to their competition. They're offering a better service on their platforms. >>All right, so thank you for that. Holger, we've seen this sort of cadence, I sort of referenced it up front a little bit and they sat on MySQL for a decade, then all of a sudden we see this rush of announcements. Why did it take so long? And and more importantly is Oracle, are they developing the right features that cloud database customers are looking for in your view? >>Yeah, great question, but first of all, in your interview you said it's the edit analytics, right? Analytics is kind of like a marketing buzzword. Reports can be analytics, right? The interesting thing, which they did, the first thing they, they, they crossed the chasm between OTP and all up, right? In the same database, right? So major engineering feed very much what customers want and it's all about creating Bellevue for customers, which, which I think is the part why they go into the multi-cloud and why they add these capabilities. And they certainly with the AI capabilities, it's kind of like getting it into an autonomous field, self-driving field now with the lake cost capabilities and meeting customers where they are, like Mark has talked about the e risk costs in the cloud. So that that's a significant advantage, creating value for customers and that's what at the end of the day matters. >>And I believe strongly that long term it's gonna be ones who create better value for customers who will get more of their money From that perspective, why then take them so long? I think it's a great question. I think largely he mentioned the gentleman Nial, it's largely to who leads a product. I used to build products too, so maybe I'm a little fooling myself here, but that made the difference in my view, right? So since he's been charged, he's been building things faster than the rest of the competition, than my SQL space, which in hindsight we thought was a hot and smoking innovation phase. It kind of like was a little self complacent when it comes to the traditional borders of where, where people think, where things are separated between OTP and ola or as an example of adjacent support, right? Structured documents, whereas unstructured documents or databases and all of that has been collapsed and brought together for building a more powerful database for customers. >>So I mean it's certainly, you know, when, when Oracle talks about the competitors, you know, the competitors are in the, I always say they're, if the Oracle talks about you and knows you're doing well, so they talk a lot about aws, talk a little bit about Snowflake, you know, sort of Google, they have partnerships with Azure, but, but in, so I'm presuming that the response in MySQL heatwave was really in, in response to what they were seeing from those big competitors. But then you had Maria DB coming out, you know, the day that that Oracle acquired Sun and, and launching and going after the MySQL base. So it's, I'm, I'm interested and we'll talk about this later and what you guys think AWS and Google and Azure and Snowflake and how they're gonna respond. But, but before I do that, Ron, I want to ask you, you, you, you can get, you know, pretty technical and you've probably seen the benchmarks. >>I know you have Oracle makes a big deal out of it, publishes its benchmarks, makes some transparent on on GI GitHub. Larry Ellison talked about this in his keynote at Cloud World. What are the benchmarks show in general? I mean, when you, when you're new to the market, you gotta have a story like Mark was saying, you gotta be two x you know, the performance at half the cost or you better be or you're not gonna get any market share. So, and, and you know, oftentimes companies don't publish market benchmarks when they're leading. They do it when they, they need to gain share. So what do you make of the benchmarks? Have their, any results that were surprising to you? Have, you know, they been challenged by the competitors. Is it just a bunch of kind of desperate bench marketing to make some noise in the market or you know, are they real? What's your view? >>Well, from my perspective, I think they have the validity. And to your point, I believe that when it comes to competitor responses, that has not really happened. Nobody has like pulled down the information that's on GitHub and said, Oh, here are our price performance results. And they counter oracles. In fact, I think part of the reason why that hasn't happened is that there's the risk if Oracle's coming out and saying, Hey, we can deliver 17 times better query performance using our capabilities versus say, Snowflake when it comes to, you know, the Lakehouse platform and Snowflake turns around and says it's actually only 15 times better during performance, that's not exactly an effective maneuver. And so I think this is really to oracle's credit and I think it's refreshing because these differentiators are significant. We're not talking, you know, like 1.2% differences. We're talking 17 fold differences, we're talking six fold differences depending on, you know, where the spotlight is being shined and so forth. >>And so I think this is actually something that is actually too good to believe initially at first blush. If I'm a cloud database decision maker, I really have to prioritize this. I really would know, pay a lot more attention to this. And that's why I posed the question to Oracle and others like, okay, if these differentiators are so significant, why isn't the needle moving a bit more? And it's for, you know, some of the usual reasons. One is really deep discounting coming from, you know, the other players that's really kind of, you know, marketing 1 0 1, this is something you need to do when there's a real competitive threat to keep, you know, a customer in your own customer base. Plus there is the usual fear and uncertainty about moving from one platform to another. But I think, you know, the traction, the momentum is, is shifting an Oracle's favor. I think we saw that in the Q1 efforts, for example, where Oracle cloud grew 44% and that it generated, you know, 4.8 billion and revenue if I recall correctly. And so, so all these are demonstrating that's Oracle is making, I think many of the right moves, publishing these figures for anybody to look at from their own perspective is something that is, I think, good for the market and I think it's just gonna continue to pay dividends for Oracle down the horizon as you know, competition intens plots. So if I were in, >>Dave, can I, Dave, can I interject something and, and what Ron just said there? Yeah, please go ahead. A couple things here, one discounting, which is a common practice when you have a real threat, as Ron pointed out, isn't going to help much in this situation simply because you can't discount to the point where you improve your performance and the performance is a huge differentiator. You may be able to get your price down, but the problem that most of them have is they don't have an integrated product service. They don't have an integrated O L T P O L A P M L N data lake. Even if you cut out two of them, they don't have any of them integrated. They have multiple services that are required separate integration and that can't be overcome with discounting. And the, they, you have to pay for each one of these. And oh, by the way, as you grow, the discounts go away. So that's a, it's a minor important detail. >>So, so that's a TCO question mark, right? And I know you look at this a lot, if I had that kind of price performance advantage, I would be pounding tco, especially if I need two separate databases to do the job. That one can do, that's gonna be, the TCO numbers are gonna be off the chart or maybe down the chart, which you want. Have you looked at this and how does it compare with, you know, the big cloud guys, for example, >>I've looked at it in depth, in fact, I'm working on another TCO on this arena, but you can find it on Wiki bod in which I compared TCO for MySEQ Heat wave versus Aurora plus Redshift plus ML plus Blue. I've compared it against gcps services, Azure services, Snowflake with other services. And there's just no comparison. The, the TCO differences are huge. More importantly, thefor, the, the TCO per performance is huge. We're talking in some cases multiple orders of magnitude, but at least an order of magnitude difference. So discounting isn't gonna help you much at the end of the day, it's only going to lower your cost a little, but it doesn't improve the automation, it doesn't improve the performance, it doesn't improve the time to insight, it doesn't improve all those things that you want out of a database or multiple databases because you >>Can't discount yourself to a higher value proposition. >>So what about, I wonder ho if you could chime in on the developer angle. You, you followed that, that market. How do these innovations from heatwave, I think you used the term developer velocity. I've heard you used that before. Yeah, I mean, look, Oracle owns Java, okay, so it, it's, you know, most popular, you know, programming language in the world, blah, blah blah. But it does it have the, the minds and hearts of, of developers and does, where does heatwave fit into that equation? >>I think heatwave is gaining quickly mindshare on the developer side, right? It's not the traditional no sequel database which grew up, there's a traditional mistrust of oracles to developers to what was happening to open source when gets acquired. Like in the case of Oracle versus Java and where my sql, right? And, but we know it's not a good competitive strategy to, to bank on Oracle screwing up because it hasn't worked not on Java known my sequel, right? And for developers, it's, once you get to know a technology product and you can do more, it becomes kind of like a Swiss army knife and you can build more use case, you can build more powerful applications. That's super, super important because you don't have to get certified in multiple databases. You, you are fast at getting things done, you achieve fire, develop velocity, and the managers are happy because they don't have to license more things, send you to more trainings, have more risk of something not being delivered, right? >>So it's really the, we see the suite where this best of breed play happening here, which in general was happening before already with Oracle's flagship database. Whereas those Amazon as an example, right? And now the interesting thing is every step away Oracle was always a one database company that can be only one and they're now generally talking about heat web and that two database company with different market spaces, but same value proposition of integrating more things very, very quickly to have a universal database that I call, they call the converge database for all the needs of an enterprise to run certain application use cases. And that's what's attractive to developers. >>It's, it's ironic isn't it? I mean I, you know, the rumor was the TK Thomas Curian left Oracle cuz he wanted to put Oracle database on other clouds and other places. And maybe that was the rift. Maybe there was, I'm sure there was other things, but, but Oracle clearly is now trying to expand its Tam Ron with, with heatwave into aws, into Azure. How do you think Oracle's gonna do, you were at a cloud world, what was the sentiment from customers and the independent analyst? Is this just Oracle trying to screw with the competition, create a little diversion? Or is this, you know, serious business for Oracle? What do you think? >>No, I think it has lakes. I think it's definitely, again, attriting to Oracle's overall ability to differentiate not only my SQL heat wave, but its overall portfolio. And I think the fact that they do have the alliance with the Azure in place, that this is definitely demonstrating their commitment to meeting the multi-cloud needs of its customers as well as what we pointed to in terms of the fact that they're now offering, you know, MySQL capabilities within AWS natively and that it can now perform AWS's own offering. And I think this is all demonstrating that Oracle is, you know, not letting up, they're not resting on its laurels. That's clearly we are living in a multi-cloud world, so why not just make it more easy for customers to be able to use cloud databases according to their own specific, specific needs. And I think, you know, to holder's point, I think that definitely lines with being able to bring on more application developers to leverage these capabilities. >>I think one important announcement that's related to all this was the JSON relational duality capabilities where now it's a lot easier for application developers to use a language that they're very familiar with a JS O and not have to worry about going into relational databases to store their J S O N application coding. So this is, I think an example of the innovation that's enhancing the overall Oracle portfolio and certainly all the work with machine learning is definitely paying dividends as well. And as a result, I see Oracle continue to make these inroads that we pointed to. But I agree with Mark, you know, the short term discounting is just a stall tag. This is not denying the fact that Oracle is being able to not only deliver price performance differentiators that are dramatic, but also meeting a wide range of needs for customers out there that aren't just limited device performance consideration. >>Being able to support multi-cloud according to customer needs. Being able to reach out to the application developer community and address a very specific challenge that has plagued them for many years now. So bring it all together. Yeah, I see this as just enabling Oracles who ring true with customers. That the customers that were there were basically all of them, even though not all of them are going to be saying the same things, they're all basically saying positive feedback. And likewise, I think the analyst community is seeing this. It's always refreshing to be able to talk to customers directly and at Oracle cloud there was a litany of them and so this is just a difference maker as well as being able to talk to strategic partners. The nvidia, I think partnerships also testament to Oracle's ongoing ability to, you know, make the ecosystem more user friendly for the customers out there. >>Yeah, it's interesting when you get these all in one tools, you know, the Swiss Army knife, you expect that it's not able to be best of breed. That's the kind of surprising thing that I'm hearing about, about heatwave. I want to, I want to talk about Lake House because when I think of Lake House, I think data bricks, and to my knowledge data bricks hasn't been in the sites of Oracle yet. Maybe they're next, but, but Oracle claims that MySQL, heatwave, Lakehouse is a breakthrough in terms of capacity and performance. Mark, what are your thoughts on that? Can you double click on, on Lakehouse Oracle's claims for things like query performance and data loading? What does it mean for the market? Is Oracle really leading in, in the lake house competitive landscape? What are your thoughts? >>Well, but name in the game is what are the problems you're solving for the customer? More importantly, are those problems urgent or important? If they're urgent, customers wanna solve 'em. Now if they're important, they might get around to them. So you look at what they're doing with Lake House or previous to that machine learning or previous to that automation or previous to that O L A with O ltp and they're merging all this capability together. If you look at Snowflake or data bricks, they're tacking one problem. You look at MyQ heat wave, they're tacking multiple problems. So when you say, yeah, their queries are much better against the lake house in combination with other analytics in combination with O ltp and the fact that there are no ETLs. So you're getting all this done in real time. So it's, it's doing the query cross, cross everything in real time. >>You're solving multiple user and developer problems, you're increasing their ability to get insight faster, you're having shorter response times. So yeah, they really are solving urgent problems for customers. And by putting it where the customer lives, this is the brilliance of actually being multicloud. And I know I'm backing up here a second, but by making it work in AWS and Azure where people already live, where they already have applications, what they're saying is, we're bringing it to you. You don't have to come to us to get these, these benefits, this value overall, I think it's a brilliant strategy. I give Nip and Argo wallet a huge, huge kudos for what he's doing there. So yes, what they're doing with the lake house is going to put notice on data bricks and Snowflake and everyone else for that matter. Well >>Those are guys that whole ago you, you and I have talked about this. Those are, those are the guys that are doing sort of the best of breed. You know, they're really focused and they, you know, tend to do well at least out of the gate. Now you got Oracle's converged philosophy, obviously with Oracle database. We've seen that now it's kicking in gear with, with heatwave, you know, this whole thing of sweets versus best of breed. I mean the long term, you know, customers tend to migrate towards suite, but the new shiny toy tends to get the growth. How do you think this is gonna play out in cloud database? >>Well, it's the forever never ending story, right? And in software right suite, whereas best of breed and so far in the long run suites have always won, right? So, and sometimes they struggle again because the inherent problem of sweets is you build something larger, it has more complexity and that means your cycles to get everything working together to integrate the test that roll it out, certify whatever it is, takes you longer, right? And that's not the case. It's a fascinating part of what the effort around my SQL heat wave is that the team is out executing the previous best of breed data, bringing us something together. Now if they can maintain that pace, that's something to to, to be seen. But it, the strategy, like what Mark was saying, bring the software to the data is of course interesting and unique and totally an Oracle issue in the past, right? >>Yeah. But it had to be in your database on oci. And but at, that's an interesting part. The interesting thing on the Lake health side is, right, there's three key benefits of a lakehouse. The first one is better reporting analytics, bring more rich information together, like make the, the, the case for silicon angle, right? We want to see engagements for this video, we want to know what's happening. That's a mixed transactional video media use case, right? Typical Lakehouse use case. The next one is to build more rich applications, transactional applications which have video and these elements in there, which are the engaging one. And the third one, and that's where I'm a little critical and concerned, is it's really the base platform for artificial intelligence, right? To run deep learning to run things automatically because they have all the data in one place can create in one way. >>And that's where Oracle, I know that Ron talked about Invidia for a moment, but that's where Oracle doesn't have the strongest best story. Nonetheless, the two other main use cases of the lake house are very strong, very well only concern is four 50 terabyte sounds long. It's an arbitrary limitation. Yeah, sounds as big. So for the start, and it's the first word, they can make that bigger. You don't want your lake house to be limited and the terabyte sizes or any even petabyte size because you want to have the certainty. I can put everything in there that I think it might be relevant without knowing what questions to ask and query those questions. >>Yeah. And you know, in the early days of no schema on right, it just became a mess. But now technology has evolved to allow us to actually get more value out of that data. Data lake. Data swamp is, you know, not much more, more, more, more logical. But, and I want to get in, in a moment, I want to come back to how you think the competitors are gonna respond. Are they gonna have to sort of do a more of a converged approach? AWS in particular? But before I do, Ron, I want to ask you a question about autopilot because I heard Larry Ellison's keynote and he was talking about how, you know, most security issues are human errors with autonomy and autonomous database and things like autopilot. We take care of that. It's like autonomous vehicles, they're gonna be safer. And I went, well maybe, maybe someday. So Oracle really tries to emphasize this, that every time you see an announcement from Oracle, they talk about new, you know, autonomous capabilities. It, how legit is it? Do people care? What about, you know, what's new for heatwave Lakehouse? How much of a differentiator, Ron, do you really think autopilot is in this cloud database space? >>Yeah, I think it will definitely enhance the overall proposition. I don't think people are gonna buy, you know, lake house exclusively cause of autopilot capabilities, but when they look at the overall picture, I think it will be an added capability bonus to Oracle's benefit. And yeah, I think it's kind of one of these age old questions, how much do you automate and what is the bounce to strike? And I think we all understand with the automatic car, autonomous car analogy that there are limitations to being able to use that. However, I think it's a tool that basically every organization out there needs to at least have or at least evaluate because it goes to the point of it helps with ease of use, it helps make automation more balanced in terms of, you know, being able to test, all right, let's automate this process and see if it works well, then we can go on and switch on on autopilot for other processes. >>And then, you know, that allows, for example, the specialists to spend more time on business use cases versus, you know, manual maintenance of, of the cloud database and so forth. So I think that actually is a, a legitimate value proposition. I think it's just gonna be a case by case basis. Some organizations are gonna be more aggressive with putting automation throughout their processes throughout their organization. Others are gonna be more cautious. But it's gonna be, again, something that will help the overall Oracle proposition. And something that I think will be used with caution by many organizations, but other organizations are gonna like, hey, great, this is something that is really answering a real problem. And that is just easing the use of these databases, but also being able to better handle the automation capabilities and benefits that come with it without having, you know, a major screwup happened and the process of transitioning to more automated capabilities. >>Now, I didn't attend cloud world, it's just too many red eyes, you know, recently, so I passed. But one of the things I like to do at those events is talk to customers, you know, in the spirit of the truth, you know, they, you know, you'd have the hallway, you know, track and to talk to customers and they say, Hey, you know, here's the good, the bad and the ugly. So did you guys, did you talk to any customers my SQL Heatwave customers at, at cloud world? And and what did you learn? I don't know, Mark, did you, did you have any luck and, and having some, some private conversations? >>Yeah, I had quite a few private conversations. The one thing before I get to that, I want disagree with one point Ron made, I do believe there are customers out there buying the heat wave service, the MySEQ heat wave server service because of autopilot. Because autopilot is really revolutionary in many ways in the sense for the MySEQ developer in that it, it auto provisions, it auto parallel loads, IT auto data places it auto shape predictions. It can tell you what machine learning models are going to tell you, gonna give you your best results. And, and candidly, I've yet to meet a DBA who didn't wanna give up pedantic tasks that are pain in the kahoo, which they'd rather not do and if it's long as it was done right for them. So yes, I do think people are buying it because of autopilot and that's based on some of the conversations I had with customers at Oracle Cloud World. >>In fact, it was like, yeah, that's great, yeah, we get fantastic performance, but this really makes my life easier and I've yet to meet a DBA who didn't want to make their life easier. And it does. So yeah, I've talked to a few of them. They were excited. I asked them if they ran into any bugs, were there any difficulties in moving to it? And the answer was no. In both cases, it's interesting to note, my sequel is the most popular database on the planet. Well, some will argue that it's neck and neck with SQL Server, but if you add in Mariah DB and ProCon db, which are forks of MySQL, then yeah, by far and away it's the most popular. And as a result of that, everybody for the most part has typically a my sequel database somewhere in their organization. So this is a brilliant situation for anybody going after MyQ, but especially for heat wave. And the customers I talk to love it. I didn't find anybody complaining about it. And >>What about the migration? We talked about TCO earlier. Did your t does your TCO analysis include the migration cost or do you kind of conveniently leave that out or what? >>Well, when you look at migration costs, there are different kinds of migration costs. By the way, the worst job in the data center is the data migration manager. Forget it, no other job is as bad as that one. You get no attaboys for doing it. Right? And then when you screw up, oh boy. So in real terms, anything that can limit data migration is a good thing. And when you look at Data Lake, that limits data migration. So if you're already a MySEQ user, this is a pure MySQL as far as you're concerned. It's just a, a simple transition from one to the other. You may wanna make sure nothing broke and every you, all your tables are correct and your schema's, okay, but it's all the same. So it's a simple migration. So it's pretty much a non-event, right? When you migrate data from an O LTP to an O L A P, that's an ETL and that's gonna take time. >>But you don't have to do that with my SQL heat wave. So that's gone when you start talking about machine learning, again, you may have an etl, you may not, depending on the circumstances, but again, with my SQL heat wave, you don't, and you don't have duplicate storage, you don't have to copy it from one storage container to another to be able to be used in a different database, which by the way, ultimately adds much more cost than just the other service. So yeah, I looked at the migration and again, the users I talked to said it was a non-event. It was literally moving from one physical machine to another. If they had a new version of MySEQ running on something else and just wanted to migrate it over or just hook it up or just connect it to the data, it worked just fine. >>Okay, so every day it sounds like you guys feel, and we've certainly heard this, my colleague David Foyer, the semi-retired David Foyer was always very high on heatwave. So I think you knows got some real legitimacy here coming from a standing start, but I wanna talk about the competition, how they're likely to respond. I mean, if your AWS and you got heatwave is now in your cloud, so there's some good aspects of that. The database guys might not like that, but the infrastructure guys probably love it. Hey, more ways to sell, you know, EC two and graviton, but you're gonna, the database guys in AWS are gonna respond. They're gonna say, Hey, we got Redshift, we got aqua. What's your thoughts on, on not only how that's gonna resonate with customers, but I'm interested in what you guys think will a, I never say never about aws, you know, and are they gonna try to build, in your view a converged Oola and o LTP database? You know, Snowflake is taking an ecosystem approach. They've added in transactional capabilities to the portfolio so they're not standing still. What do you guys see in the competitive landscape in that regard going forward? Maybe Holger, you could start us off and anybody else who wants to can chime in, >>Happy to, you mentioned Snowflake last, we'll start there. I think Snowflake is imitating that strategy, right? That building out original data warehouse and the clouds tasking project to really proposition to have other data available there because AI is relevant for everybody. Ultimately people keep data in the cloud for ultimately running ai. So you see the same suite kind of like level strategy, it's gonna be a little harder because of the original positioning. How much would people know that you're doing other stuff? And I just, as a former developer manager of developers, I just don't see the speed at the moment happening at Snowflake to become really competitive to Oracle. On the flip side, putting my Oracle hat on for a moment back to you, Mark and Iran, right? What could Oracle still add? Because the, the big big things, right? The traditional chasms in the database world, they have built everything, right? >>So I, I really scratched my hat and gave Nipon a hard time at Cloud world say like, what could you be building? Destiny was very conservative. Let's get the Lakehouse thing done, it's gonna spring next year, right? And the AWS is really hard because AWS value proposition is these small innovation teams, right? That they build two pizza teams, which can be fit by two pizzas, not large teams, right? And you need suites to large teams to build these suites with lots of functionalities to make sure they work together. They're consistent, they have the same UX on the administration side, they can consume the same way, they have the same API registry, can't even stop going where the synergy comes to play over suite. So, so it's gonna be really, really hard for them to change that. But AWS super pragmatic. They're always by themselves that they'll listen to customers if they learn from customers suite as a proposition. I would not be surprised if AWS trying to bring things closer together, being morely together. >>Yeah. Well how about, can we talk about multicloud if, if, again, Oracle is very on on Oracle as you said before, but let's look forward, you know, half a year or a year. What do you think about Oracle's moves in, in multicloud in terms of what kind of penetration they're gonna have in the marketplace? You saw a lot of presentations at at cloud world, you know, we've looked pretty closely at the, the Microsoft Azure deal. I think that's really interesting. I've, I've called it a little bit of early days of a super cloud. What impact do you think this is gonna have on, on the marketplace? But, but both. And think about it within Oracle's customer base, I have no doubt they'll do great there. But what about beyond its existing install base? What do you guys think? >>Ryan, do you wanna jump on that? Go ahead. Go ahead Ryan. No, no, no, >>That's an excellent point. I think it aligns with what we've been talking about in terms of Lakehouse. I think Lake House will enable Oracle to pull more customers, more bicycle customers onto the Oracle platforms. And I think we're seeing all the signs pointing toward Oracle being able to make more inroads into the overall market. And that includes garnishing customers from the leaders in, in other words, because they are, you know, coming in as a innovator, a an alternative to, you know, the AWS proposition, the Google cloud proposition that they have less to lose and there's a result they can really drive the multi-cloud messaging to resonate with not only their existing customers, but also to be able to, to that question, Dave's posing actually garnish customers onto their platform. And, and that includes naturally my sequel but also OCI and so forth. So that's how I'm seeing this playing out. I think, you know, again, Oracle's reporting is indicating that, and I think what we saw, Oracle Cloud world is definitely validating the idea that Oracle can make more waves in the overall market in this regard. >>You know, I, I've floated this idea of Super cloud, it's kind of tongue in cheek, but, but there, I think there is some merit to it in terms of building on top of hyperscale infrastructure and abstracting some of the, that complexity. And one of the things that I'm most interested in is industry clouds and an Oracle acquisition of Cerner. I was struck by Larry Ellison's keynote, it was like, I don't know, an hour and a half and an hour and 15 minutes was focused on healthcare transformation. Well, >>So vertical, >>Right? And so, yeah, so you got Oracle's, you know, got some industry chops and you, and then you think about what they're building with, with not only oci, but then you got, you know, MyQ, you can now run in dedicated regions. You got ADB on on Exadata cloud to customer, you can put that OnPrem in in your data center and you look at what the other hyperscalers are, are doing. I I say other hyperscalers, I've always said Oracle's not really a hyperscaler, but they got a cloud so they're in the game. But you can't get, you know, big query OnPrem, you look at outposts, it's very limited in terms of, you know, the database support and again, that that will will evolve. But now you got Oracle's got, they announced Alloy, we can white label their cloud. So I'm interested in what you guys think about these moves, especially the industry cloud. We see, you know, Walmart is doing sort of their own cloud. You got Goldman Sachs doing a cloud. Do you, you guys, what do you think about that and what role does Oracle play? Any thoughts? >>Yeah, let me lemme jump on that for a moment. Now, especially with the MyQ, by making that available in multiple clouds, what they're doing is this follows the philosophy they've had the past with doing cloud, a customer taking the application and the data and putting it where the customer lives. If it's on premise, it's on premise. If it's in the cloud, it's in the cloud. By making the mice equal heat wave, essentially a plug compatible with any other mice equal as far as your, your database is concern and then giving you that integration with O L A P and ML and Data Lake and everything else, then what you've got is a compelling offering. You're making it easier for the customer to use. So I look the difference between MyQ and the Oracle database, MyQ is going to capture market more market share for them. >>You're not gonna find a lot of new users for the Oracle debate database. Yeah, there are always gonna be new users, don't get me wrong, but it's not gonna be a huge growth. Whereas my SQL heatwave is probably gonna be a major growth engine for Oracle going forward. Not just in their own cloud, but in AWS and in Azure and on premise over time that eventually it'll get there. It's not there now, but it will, they're doing the right thing on that basis. They're taking the services and when you talk about multicloud and making them available where the customer wants them, not forcing them to go where you want them, if that makes sense. And as far as where they're going in the future, I think they're gonna take a page outta what they've done with the Oracle database. They'll add things like JSON and XML and time series and spatial over time they'll make it a, a complete converged database like they did with the Oracle database. The difference being Oracle database will scale bigger and will have more transactions and be somewhat faster. And my SQL will be, for anyone who's not on the Oracle database, they're, they're not stupid, that's for sure. >>They've done Jason already. Right. But I give you that they could add graph and time series, right. Since eat with, Right, Right. Yeah, that's something absolutely right. That's, that's >>A sort of a logical move, right? >>Right. But that's, that's some kid ourselves, right? I mean has worked in Oracle's favor, right? 10 x 20 x, the amount of r and d, which is in the MyQ space, has been poured at trying to snatch workloads away from Oracle by starting with IBM 30 years ago, 20 years ago, Microsoft and, and, and, and didn't work, right? Database applications are extremely sticky when they run, you don't want to touch SIM and grow them, right? So that doesn't mean that heat phase is not an attractive offering, but it will be net new things, right? And what works in my SQL heat wave heat phases favor a little bit is it's not the massive enterprise applications which have like we the nails like, like you might be only running 30% or Oracle, but the connections and the interfaces into that is, is like 70, 80% of your enterprise. >>You take it out and it's like the spaghetti ball where you say, ah, no I really don't, don't want to do all that. Right? You don't, don't have that massive part with the equals heat phase sequel kind of like database which are more smaller tactical in comparison, but still I, I don't see them taking so much share. They will be growing because of a attractive value proposition quickly on the, the multi-cloud, right? I think it's not really multi-cloud. If you give people the chance to run your offering on different clouds, right? You can run it there. The multi-cloud advantages when the Uber offering comes out, which allows you to do things across those installations, right? I can migrate data, I can create data across something like Google has done with B query Omni, I can run predictive models or even make iron models in different place and distribute them, right? And Oracle is paving the road for that, but being available on these clouds. But the multi-cloud capability of database which knows I'm running on different clouds that is still yet to be built there. >>Yeah. And >>That the problem with >>That, that's the super cloud concept that I flowed and I I've always said kinda snowflake with a single global instance is sort of, you know, headed in that direction and maybe has a league. What's the issue with that mark? >>Yeah, the problem with the, with that version, the multi-cloud is clouds to charge egress fees. As long as they charge egress fees to move data between clouds, it's gonna make it very difficult to do a real multi-cloud implementation. Even Snowflake, which runs multi-cloud, has to pass out on the egress fees of their customer when data moves between clouds. And that's really expensive. I mean there, there is one customer I talked to who is beta testing for them, the MySQL heatwave and aws. The only reason they didn't want to do that until it was running on AWS is the egress fees were so great to move it to OCI that they couldn't afford it. Yeah. Egress fees are the big issue but, >>But Mark the, the point might be you might wanna root query and only get the results set back, right was much more tinier, which been the answer before for low latency between the class A problem, which we sometimes still have but mostly don't have. Right? And I think in general this with fees coming down based on the Oracle general E with fee move and it's very hard to justify those, right? But, but it's, it's not about moving data as a multi-cloud high value use case. It's about doing intelligent things with that data, right? Putting into other places, replicating it, what I'm saying the same thing what you said before, running remote queries on that, analyzing it, running AI on it, running AI models on that. That's the interesting thing. Cross administered in the same way. Taking things out, making sure compliance happens. Making sure when Ron says I don't want to be American anymore, I want to be in the European cloud that is gets migrated, right? So tho those are the interesting value use case which are really, really hard for enterprise to program hand by hand by developers and they would love to have out of the box and that's yet the innovation to come to, we have to come to see. But the first step to get there is that your software runs in multiple clouds and that's what Oracle's doing so well with my SQL >>Guys. Amazing. >>Go ahead. Yeah. >>Yeah. >>For example, >>Amazing amount of data knowledge and, and brain power in this market. Guys, I really want to thank you for coming on to the cube. Ron Holger. Mark, always a pleasure to have you on. Really appreciate your time. >>Well all the last names we're very happy for Romanic last and moderator. Thanks Dave for moderating us. All right, >>We'll see. We'll see you guys around. Safe travels to all and thank you for watching this power panel, The Truth About My SQL Heat Wave on the cube. Your leader in enterprise and emerging tech coverage.

>>Hey guys and girls, welcome back to Motor City, Lisa Martin here with John Furrier on the Cube's third day of coverage of Coon Cloud Native Con North America. John, we've had some great conversations over the last two and a half days. We've been talking about identity and security management as a critical need for enterprises within the cloud native space. We're gonna have another quick conversation >>On that. Yeah, we got a great segment coming up from someone who's been in the industry, a long time expert, running a great company. Now it's gonna be one of those pieces that fits into what we call super cloud. Others are calling cloud operating system. Some are calling just Cloud 2.0, 3.0. But there's definitely a major trend happening around how cloud is going Next generation. We've been covering it. So this segment should be >>Great. Let's unpack those trends. One of our alumni is back with us, O Rika Zi, co-founder and CEO of Aerio. Omri. Great to have you back on the >>Cube. Thank you. Great to be here. >>So identity move to the cloud, Access authorization did not talk to us about why you found it assertive, what you guys are doing and how you're flipping that script. >>Yeah, so back 15 years ago, I helped start Azure at Microsoft. You know, one of the first few folks that you know, really focused on enterprise services within the Azure family. And at the time I was working for the guy who ran all of Windows server and you know, active directory. He called it the linchpin workload for the Windows Server franchise, like big words. But what he meant was we had 95% market share and all of these new SAS applications like ServiceNow and you know, Workday and salesforce.com, they had to invent login and they had to invent access control. And so we were like, well, we're gonna lose it unless we figure out how to replace active directory. And that's how Azure Active Directory was born. And the first thing that we had to do as an industry was fix identity, right? Yeah. So, you know, we worked on things like oof Two and Open, Id Connect and SAML and Jot as an industry and now 15 years later, no one has to go build login if you don't want to, right? You have companies like Odd Zero and Okta and one login Ping ID that solve that problem solve single sign-on, on the web. But access Control hasn't really moved forward at all in the last 15 years. And so my co-founder and I who were both involved in the early beginnings of Azure Active directory, wanted to go back to that problem. And that problem is even bigger than identity and it's far from >>Solved. Yeah, this is huge. I think, you know, self-service has been a developer thing that's, everyone knows developer productivity, we've all experienced click sign in with your LinkedIn or Twitter or Google or Apple handle. So that's single sign on check. Now the security conversation kicks in. If you look at with this no perimeter and cloud, now you've got multi-cloud or super cloud on the horizon. You've got all kinds of opportunities to innovate on the security paradigm. I think this is kind of where I'm hearing the most conversation around access control as well as operationally eliminating a lot of potential problems. So there's one clean up the siloed or fragmented access and two streamlined for security. What's your reaction to that? Do you agree? And if not, where, where am I missing that? >>Yeah, absolutely. If you look at the life of an IT pro, you know, back in the two thousands they had, you know, l d or active directory, they add in one place to configure groups and they'd map users to groups. And groups typically corresponded to roles and business applications. And it was clunky, but life was pretty simple. And now they live in dozens or hundreds of different admin consoles. So misconfigurations are rampant and over provisioning is a real problem. If you look at zero trust and the principle of lease privilege, you know, all these applications have these course grained permissions. And so when you have a breach, and it's not a matter of if, it's a matter of when you wanna limit the blast radius of you know what happened, and you can't do that unless you have fine grained access control. So all those, you know, all those reasons together are forcing us as an industry to come to terms with the fact that we really need to revisit access control and bring it to the age of cloud. >>You guys recently, just this week I saw the blog on Topaz. Congratulations. Thank you. Talk to us about what that is and some of the gaps that's gonna help sarto to fill for what's out there in the marketplace. >>Yeah, so right now there really isn't a way to go build fine grains policy based real time access control based on open source, right? We have the open policy agent, which is a great decision engine, but really optimized for infrastructure scenarios like Kubernetes admission control. And then on the other hand, you have this new, you know, generation of access control ideas. This model called relationship based access control that was popularized by Google Zanzibar system. So Zanzibar is how they do access control for Google Docs and Google Drive. If you've ever kind of looked at a Google Doc and you know you're a viewer or an owner or a commenter, Zanzibar is the system behind it. And so what we've done is we've married these two things together. We have a policy based system, OPPA based system, and at the same time we've brought together a directory, an embedded directory in Topaz that allows you to answer questions like, does this user have this permission on this object? And bringing it all together, making it open sources a real game changer from our perspective, real >>Game changer. That's good to hear. What are some of the key use cases that it's gonna help your customers address? >>So a lot of our customers really like the idea of policy based access management, but they don't know how to bring data to that decision engine. And so we basically have a, you know, a, a very opinionated way of how to model that data. So you import data out of your identity providers. So you connect us to Okta or oze or Azure, Azure Active directory. And so now you have the user data, you can define groups and then you can define, you know, your object hierarchy, your domain model. So let's say you have an applicant tracking system, you have nouns like job, you know, know job descriptions or candidates. And so you wanna model these things and you want to be able to say who has access to, you know, the candidates for this job, for example. Those are the kinds of rules that people can express really easily in Topaz and in assertive. >>What are some of the challenges that are happening right now that dissolve? What, what are you looking at to solve? Is it complexity, sprawl, logic problems? What's the main problem set you guys >>See? Yeah, so as organizations grow and they have more and more microservices, each one of these microservices does authorization differently. And so it's impossible to reason about the full surface area of, you know, permissions in your application. And more and more of these organizations are saying, You know what, we need a standard layer for this. So it's not just Google with Zanzibar, it's Intuit with Oddy, it's Carta with their own oddy system, it's Netflix, you know, it's Airbnb with heed. All of them are now talking about how they solve access control extracted into its own service to basically manage complexity and regain agility. The other thing is all about, you know, time to market and, and tco. >>So, so how do you work with those services? Do you replace them, you unify them? What is the approach that you're taking? >>So basically these organizations are saying, you know what? We want one access control service. We want all of our microservices to call that thing instead of having to roll out our own. And so we, you know, give you the guts for that service, right? Topaz is basically the way that you're gonna go implement an access control service without having to go build it the same way that you know, large companies like Airbnb or Google or, or a car to >>Have. What's the competition look like for you guys? I'm not really seeing a lot of competition out there. Are there competitors? Are there different approaches? What makes you different? >>Yeah, so I would say that, you know, the biggest competitor is roll your own. So a lot of these companies that find us, they say, We're sick and tired of investing 2, 3, 4 engineers, five engineers on this thing. You know, it's the gift that keeps on giving. We have to maintain this thing and so we can, we can use your solution at a fraction of the cost a, a fifth, a 10th of what it would cost us to maintain it locally. There are others like Sty for example, you know, they are in the space, but more in on the infrastructure side. So they solve the problem of Kubernetes submission control or things like that. So >>Rolling your own, there's a couple problems there. One is do they get all the corner cases who built a they still, it's a company. Exactly. It's heavy lifting, it's undifferentiated, you just gotta check the box. So probably will be not optimized. >>That's right. As Bezo says, only focus on the things that make your beer taste better. And access control is one of those things. It's part of your security, you know, posture, it's a critical thing to get right, but you know, I wanna work on access control, said no developer ever, right? So it's kind of like this boring, you know, like back office thing that you need to do. And so we give you the mechanisms to be able to build it securely and robustly. >>Do you have a, a customer story example that is one of your go-tos that really highlights how you're improving developer productivity? >>Yeah, so we have a couple of them actually. So there's the largest third party B2B marketplace in the us. Free retail. Instead of building their own, they actually brought in aer. And what they wanted to do with AER was be the authorization layer for both their externally facing applications as well as their internal apps. So basically every one of their applications now hooks up to AER to do authorization. They define users and groups and roles and permissions in one place and then every application can actually plug into that instead of having to roll out their own. >>I'd like to switch gears if you don't mind. I get first of all, great update on the company and progress. I'd like to get your thoughts on the cloud computing market. Obviously you were your legendary position, Azure, I mean look at the, look at the progress over the past few years. Just been spectacular from Microsoft and you set the table there. Amazon web service is still, you know, thundering away even though earnings came out, the market's kind of soft still. You know, you see the cloud hyperscalers just continuing to differentiate from software to chips. Yep. Across the board. So the hyperscalers kicking ass taking names, doing great Microsoft right up there. What's the future? Cuz you now have the conversation where, okay, we're calling it super cloud, somebody calling multi-cloud, somebody calling it distributed computing, whatever you wanna call it. The old is now new again, it just looks different as cloud becomes now the next computer industry, >>You got an operating system, you got applications, you got hardware, I mean it's all kind of playing out just on a massive global scale, but you got regions, you got all kinds of connected systems edge. What's your vision on how this plays out? Because things are starting to fall into place. Web assembly to me just points to, you know, app servers are coming back, middleware, Kubernetes containers, VMs are gonna still be there. So you got the progression. What's your, what's your take on this? How would you share, share your thoughts to a friend or the industry, the audience? So what's going on? What's, what's happening right now? What's, what's going on? >>Yeah, it's funny because you know, I remember doing this quite a few years ago with you probably in, you know, 2015 and we were talking about, back then we called it hybrid cloud, right? And it was a vision, but it is actually what's going on. It just took longer for it to get here, right? So back then, you know, the big debate was public cloud or private cloud and you know, back when we were, you know, talking about these ideas, you know, we said, well you know, some applications will always stay on-prem and some applications will move to the cloud. I was just talking to a big bank and they basically said, look, our stated objective now is to move everything we can to the public cloud and we still have a large private cloud investment that will never go away. And so now we have essentially this big operating system that can, you know, abstract all of this stuff. So we have developer platforms that can, you know, sit on top of all these different pieces of infrastructure and you know, kind of based on policy decide where these applications are gonna be scheduled. So, you know, the >>Operating schedule shows like an operating system function. >>Exactly. I mean like we now, we used to have schedulers for one CPU or you know, one box, then we had schedulers for, you know, kind of like a whole cluster and now we have schedulers across the world. >>Yeah. My final question before we kind of get run outta time is what's your thoughts on web assembly? Cuz that's getting a lot of hype here again to kind of look at this next evolution again that's lighter weight kind of feels like an app server kind of direction. What's your, what's your, it's hyped up now, what's your take on that? >>Yeah, it's interesting. I mean back, you know, what's, what's old is new again, right? So, you know, I remember back in the late nineties we got really excited about, you know, JVMs and you know, this notion of right once run anywhere and yeah, you know, I would say that web assembly provides a pretty exciting, you know, window into that where you can take the, you know, sandboxing technology from the JavaScript world, from the browser essentially. And you can, you know, compile an application down to web assembly and have it real, really truly portable. So, you know, we see for example, policies in our world, you know, with opa, one of the hottest things is to take these policies and can compile them to web assemblies so you can actually execute them at the edge, you know, wherever it is that you have a web assembly runtime. >>And so, you know, I was just talking to Scott over at Docker and you know, they're excited about kind of bringing Docker packaging, OCI packaging to web assemblies. So we're gonna see a convergence of all these technologies right now. They're kind of each, each of our, each of them are in a silo, but you know, like we'll see a lot of the patterns, like for example, OCI is gonna become the packaging format for web assemblies as it is becoming the packaging format for policies. So we did the same thing. We basically said, you know what, we want these policies to be packaged as OCI assembly so that you can sign them with cosign and bring the entire ecosystem of tools to bear on OCI packages. So convergence is I think what >>We're, and love, I love your attitude too because it's the open source community and the developers who are actually voting on the quote defacto standard. Yes. You know, if it doesn't work, right, know people know about it. Exactly. It's actually a great new production system. >>So great momentum going on to the press released earlier this week, clearly filling the gaps there that, that you and your, your co-founder saw a long time ago. What's next for the assertive business? Are you hiring? What's going on there? >>Yeah, we are really excited about launching commercially at the end of this year. So one of the things that we were, we wanted to do that we had a promise around and we delivered on our promise was open sourcing our edge authorizer. That was a huge thing for us. And we've now completed, you know, pretty much all the big pieces for AER and now it's time to commercially launch launch. We already have customers in production, you know, design partners, and you know, next year is gonna be the year to really drive commercialization. >>All right. We will be watching this space ery. Thank you so much for joining John and me on the keep. Great to have you back on the program. >>Thank you so much. It was a pleasure. >>Our pleasure as well For our guest and John Furrier, I'm Lisa Martin, you're watching The Cube Live. Michelle floor of Con Cloud Native Con 22. This is day three of our coverage. We will be back with more coverage after a short break. See that.

>>The Cube Presents UI Path Forward five. Brought to you by UI Path, >>Everybody. We're back in Las Vegas. The cube's coverage we're day one at UI Path forward. Five. Pascal Borne is here. He's an expert and bestselling author in the topic of AI and automation and the book Intelligent Automation. Welcome to the world of Hyper Automation, the first book on the topic. And of course, Ray Wong is back on the cube. He's the founder, chairman and principal analyst, Constellation Reese, also bestselling author of Everybody Wants To Rule the World. Guys, thanks so much for coming on The Cubes. Always a pleasure. Ray Pascal, First time on the Cube, I believe. >>Yes, thank you. Thanks for the invitation. Thank you. >>So what is artificial about artificial intelligence, >>For sure, not people. >>So, okay, so you guys are both speaking at the conference, Ray today. I think you're interviewing the co CEOs. What do you make of that? What's, what are you gonna, what are you gonna probe with these guys? Like, how they're gonna divide their divide and conquer, and why do you think the, the company Danielle in particular, decided to bring in Rob Sland? >>Well, you know what I mean, Like, you know, these companies are now at a different stage of growth, right? There's that early battle between RPA vendors. Now we're actually talking something different, right? We're talking about where does automation go? How do we get the decisioning? What's the next best action? That's gonna be the next step. And to take where UI path is today to somewhere else, You really want someone with that enterprise cred and experience the sales motions, the packages, the partnership capabilities, and who else better than Roblin? He, that's, he's done, he can do that in his sleep, but now he's gotta do that in a new space, taking whole category to another level. Now, Daniel on the other hand, right, I mean, he's the visionary founder. He put this thing from nothing to where he is today, right? I mean, at that point you want your founder thinking about the next set of ideas, right? So you get this interesting dynamic that we've seen for a while with co CEOs, those that are doing the operations, getting the stuff out the door, and then letting the founders get a chance to go back and rethink, take a look at the perspective, and hopefully get a chance to build the next idea or take the next idea back into the organization. >>Right? Very well said. Pascal, why did you write your book on intelligent automation and, and hyper automation, and what's changed since you've written that book? >>So, I, I wrote this book, An Intelligent Automation, two years ago. At that time, it was really a new topic. It was really about the key, the, the key, the key content of the, of the book is really about combining different technologies to automate the most complex end to end business processes in companies. And when I say capabilities, it's, we, we hear a lot about up here, especially here, robotic process automation. But up here alone, if you just trying to transform a company with only up here, you just fall short. Okay? A lot of those processes need more than execution. They need language, they need the capacity to view, to see, they need the capacity to understand and to, and to create insights. So by combining process automation with ai, natural language processing, computer vision, you give this capability to create impact by automating end to end processes in companies. >>I, I like the test, what I hear in the keynote with independent experts like yourself. So we're hearing that that intelligent automation or automation is a fundamental component of digital transformation. Is it? Or is it more sort of a back office sort of hidden in inside plumbing Ray? What do you think? >>Well, you start by understanding what's going on in the process phase. And that's where you see discover become very important in that keynote, right? And that's where process mining's playing a role. Then you gotta automate stuff. But when you get to operations, that's really where the change is going to happen, right? We actually think that, you know, when you're doing the digital transformation pieces, right? Analytics, automation and AI are coming together to create a concept we call decision velocity. You and I make a quick decision, boom, how long does it take to get out? Management committee could free forever, right? A week, two months, never. But if you're thinking about competing with the automation, right? These decisions are actually being done a hundred times per second by machine, even a thousand times per second. That asymmetry is really what people are facing at the moment. >>And the companies that are gonna be able to do that and start automating decisions are gonna be operating at another level. Back to what Pascal's book talking about, right? And there are four questions everyone has to ask you, like, when do you fully intelligently automate? And that happens right in the background when you augment the machine with a human. So we can find why did you make an exception? Why did you break a roll? Why didn't you follow this protocol so we can get it down to a higher level confidence? When do you augment the human with the machine so we can give you the information so you can act quickly. And the last one is, when do you wanna insert a human in the process? That's gonna be the biggest question. Order to cash, incident or resolution, Hire to retire, procure to pay. It doesn't matter. When do you want to put a human in the process? When do you want a man in the middle, person in the middle? And more importantly, when do you want insert friction? >>So Pascal, you wrote your book in the middle of the, the pandemic. Yes. And, and so, you know, pre pandemic digital transformation was kind of a buzzword. A lot of people gave it lip service, eh, not on my watch, I don't have to worry about that. But then it became sort of, you're not a digital business, you're out of business. So, so what have you seen as the catalyst for adoption of automation? Was it the, the pandemic? Was it sort of good runway before that? What's changed? You know, pre isolation, post isolation economy. >>You, you make me think about a joke. Who, who did your best digital transformation over the last years? The ceo, C H R O, the Covid. >>It's a big record ball, right? Yeah. >>Right. And that's exactly true. You know, before pandemic digital transformation was a competitive advantage. >>Companies that went into it had an opportunity to get a bit better than their, their competitors during the pandemic. Things have changed completely. Companies that were not digitalized and automated could not survive. And we've seen so many companies just burning out and, and, and those companies that have been able to capitalize on intelligent automation, digital transformations during the pandemic have been able not only to survive, but to, to thrive, to really create their place on the market. So that's, that has been a catalyst, definitely a catalyst for that. That explains the success of the book, basically. Yeah. >>Okay. Okay. >>So you're familiar with the concept of Stew the food, right? So Stew by definition is something that's delicious to eat. Stew isn't simply taking one of every ingredient from the pantry and throwing it in the pot and stirring it around. When we start talking about intelligent automation, artificial intelligence, augmented intelligence, it starts getting a bit overwhelming. My spy sense goes off and I start thinking, this sounds like mush. It doesn't sound like Stew. So I wanna hear from each of you, what is the methodical process that, that people need to go through when they're going through digital trans transmission, digital transformation, so that you get delicious stew instead of a mush that's just confused everything in your business. So you, Ray, you want, you want to, you wanna answer that first? >>Yeah. You know, I mean, we've been talking about digital transformation since 2010, right? And part of it was really getting the business model, right? What are you trying to achieve? Is that a new type of offering? Are you changing the way you monetize something? Are you taking existing process and applying it to a new set of technologies? And what do you wanna accomplish, right? Once you start there, then it becomes a whole lot of operational stuff. And it's more than st right? I mean, it, it could be like, well, I can't use those words there. But the point being is it could be a complete like, operational exercise. It could be a complete revenue exercise, it could be a regulatory exercise, it could be something about where you want to take growth into the next level. And each one of those processes, some of it is automation, right? There's a big component of it today. But most of it is really rethinking about what you want things to do, right? How do you actually make things to be successful, right? Do I reorganize a process? Do I insert a place to do monetization? Where do I put engagement in place? How do I collect data along the way so I can build better feedback loop? What can I do to build the business graph so that I have that knowledge for the future so I can go forward doing that so I can be successful. >>The Pascal should, should, should the directive be first ia, then ai? Or are these, are these things going to happen in parallel naturally? What's your position on that? Is it first, >>So it, so, >>So AI is part of IA because that's, it's, it's part of the big umbrella. And very often I got the question. So how do you differentiate AI in, I a, I like to say that AI is only the brain. So think of ai cuz I'm consider, I consider AI as machine learning, Okay? Think of AI in a, like a brain near jar that only can think, create, insight, learn, but doesn't do anything, doesn't have any arms, doesn't have any eyes, doesn't not have any mouth and ears can't talk, can't understand with ia, you, you give those capabilities to ai. You, you basically, you create a cap, the capability, technological capability that is able to do more than just thinking, learning and, and create insight, but also acting, speaking, understanding the environment, viewing it, interacting with it. So basically performing these, those end to end processes that are performed currently by people in companies. >>Yeah, we're gonna get to a point where we get to what we call a dynamic scenario generation. You're talking to me, you get excited, well, I changed the story because something else shows up, or you're talking to me and you're really upset. We're gonna have to actually ch, you know, address that issue right away. Well, we want the ability to have that sense and respond capability so that the next best action is served. So your data, your process, the journey, all the analytics on the top end, that's all gonna be served up and changed along the way. As we go from 2D journeys to 3D scenarios in the metaverse, if we think about what happens from a decentralized world to decentralized, and we think about what's happening from web two to web three, we're gonna make those types of shifts so that things are moving along. Everything's a choose your end venture journey. >>So I hope I remember this correctly from your book. You talked about disruption scenarios within industries and within companies. And I go back to the early days of, of our industry and East coast Prime, Wang, dg, they're all gone. And then, but, but you look at companies like Microsoft, you know, they were, they were able to, you know, get through that novel. Yeah. Ibm, you know, I call it survived. Intel is now going through their, you know, their challenge. So, so maybe it's inevitable, but how do you see the future in terms of disruption with an industry, Forget our industry for a second, all industry across, whether it's healthcare, financial services, manufacturing, automobiles, et cetera. How do you see the disruption scenario? I'm pretty sure you talked about this in your book, it's been a while since I read it, but I wonder if you could talk about that disruption scenario and, and the role that automation is going to play, either as the disruptor or as the protector of the incumbents. >>Let's take healthcare and auto as an example. Healthcare is a great example. If we think about what's going on, not enough nurses, massive shortage, right? What are we doing at the moment? We're setting five foot nine robots to do non-patient care. We're trying to capture enough information off, you know, patient analytics like this watch is gonna capture vitals from a going forward. We're doing a lot what we can do in the ambient level so that information and data is automatically captured and decisions are being rendered against that. Maybe you're gonna change your diet along the way, maybe you're gonna walk an extra 10 minutes. All those things are gonna be provided in that level of automation. Take the car business. It's not about selling cars. Tesla's a great example. We talk about this all the time. What Tesla's doing, they're basically gonna be an insurance company with all the data they have. They have better data than the insurance companies. They can do better underwriting, they've got better mapping information and insights they can actually suggest next best action do collision avoidance, right? Those are all the things that are actually happening today. And automation plays a big role, not just in the collection of that, that information insight, but also in the ability to make recommendations, to do predictions and to help you prevent things from going wrong. >>So, you know, it's interesting. It's like you talk about Tesla as the, the disrupting the insurance companies. It's almost like the over the top vendors have all the data relative to the telcos and mopped them up for lunch. Pascal, I wanna ask you, you know, the topic of future of work kind of was a bromide before, but, but now I feel like, you know, post pandemic, it, it actually has substance. How do you see the future of work? Can you even summarize what it's gonna look like? It's, it's, Or are we here? >>It's, yeah, it's, and definitely it's, it's more and more important topic currently. And you, you all heard about the great resignation and how employee experience is more and more important for companies according to have a business review. The companies that take care of their employee experience are four times more profitable that those that don't. So it's a, it's a, it's an issue for CEOs and, and shareholders. Now, how do we get there? How, how do we, how do we improve the, the quality of the employee experience, understanding the people, getting information from them, educating them. I'm talking about educating them on those new technologies and how they can benefit from those empowering them. And, and I think we've talked a lot about this, about the democratization local type of, of technologies that democratize the access to those technologies. Everyone can be empowered today to change their work, improve their work, and finally, incentivization. I think it's a very important point where companies that, yeah, I >>Give that. What's gonna be the key message of your talk tomorrow. Give us the bumper sticker, >>If you will. Oh, I'm gonna talk, It's a little bit different. I'm gonna talk for the IT community in this, in the context of the IT summit. And I'm gonna talk about the future of intelligent automation. So basically how new technologies will impact beyond what we see today, The future of work. >>Well, I always love having you on the cube, so articulate and, and and crisp. What's, what's exciting you these days, you know, in your world, I know you're traveling around a lot, but what's, what's hot? >>Yeah, I think one of the coolest thing that's going on right now is the fact that we're trying to figure out do we go to work or do we not go to work? Back to your other point, I mean, I don't know, work, work is, I mean, for me, work has been everywhere, right? And we're starting to figure out what that means. I think the second thing though is this notion around mission and purpose. And everyone's trying to figure out what does that mean for themselves? And that's really, I don't know if it's a great, great resignation. We call it great refactoring, right? Where you work, when you work, how we work, why you work, that's changing. But more importantly, the business models are changing. The monetization models are changing macro dynamics that are happening. Us versus China, G seven versus bricks, right? War on the dollar. All these things are happening around us at this moment and, and I think it's gonna really reshape us the way that we came out of the seventies into the eighties. >>Guys, always a pleasure having folks like yourself on, Thank you, Pascal. Been great to see you again. All right, Dave Nicholson, Dave Ante, keep it right there. Forward five from Las Vegas. You're watching the cue.

>>Welcome back everyone to the Cube and Horizon three.ai special presentation. I'm John Furrier, host of the Cube. We with Chris Hill, Sector head for strategic accounts and federal@horizonthree.ai. Great innovative company. Chris, great to see you. Thanks for coming on the Cube. >>Yeah, like I said, you know, great to meet you John. Long time listener. First time call. So excited to be here with >>You guys. Yeah, we were talking before camera. You had Splunk back in 2013 and I think 2012 was our first splunk.com. Yep. And boy man, you know, talk about being in the right place at the right time. Now we're at another inflection point and Splunk continues to be relevant and continuing to have that data driving security and that interplay. And your ceo, former CTO of Splunk as well at Horizons Neha, who's been on before. Really innovative product you guys have, but you know, Yeah, don't wait for a brief to find out if you're locking the right data. This is the topic of this thread. Splunk is very much part of this new international expansion announcement with you guys. Tell us what are some of the challenges that you see where this is relevant for the Splunk and the Horizon AI as you guys expand Node zero out internationally? >>Yeah, well so across, so you know, my role within Splunk was working with our most strategic accounts. And so I look back to 2013 and I think about the sales process like working with, with our small customers. You know, it was, it was still very siloed back then. Like I was selling to an IT team that was either using us for IT operations. We generally would always even say, yeah, although we do security, we weren't really designed for it. We're a log management tool. And you know, we, and I'm sure you remember back then John, we were like sort of stepping into the security space and in the public sector domain that I was in, you know, security was 70% of what we did. When I look back to sort of the transformation that I was, was witnessing in that digital transformation, you know when I, you look at like 2019 to today, you look at how the IT team and the security teams are, have been forced to break down those barriers that they used to sort of be silo away, would not communicate one, you know, the security guys would be like, Oh this is my BA box it, you're not allowed in today. >>You can't get away with that. And I think that the value that we bring to, you know, and of course Splunk has been a huge leader in that space and continues to do innovation across the board. But I think what we've we're seeing in the space that I was talking with Patrick Kauflin, the SVP of security markets about this, is that, you know, what we've been able to do with Splunk is build a purpose built solution that allows Splunk to eat more data. So Splunk itself, as you well know, it's an ingest engine, right? So the great reason people bought it was you could build these really fast dashboards and grab intelligence out of it, but without data it doesn't do anything, right? So how do you drive and how do you bring more data in? And most importantly from a customer perspective, how do you bring the right data in? >>And so if you think about what node zero and what we're doing in a Horizon three is that, sure we do pen testing, but because we're an autonomous pen testing tool, we do it continuously. So this whole thought of being like, Oh, crud like my customers, Oh yeah, we got a pen test coming up, it's gonna be six weeks. The wait. Oh yeah. You know, and everyone's gonna sit on their hands, Call me back in two months, Chris, we'll talk to you then. Right? Not, not a real efficient way to test your environment and shoot, we, we saw that with Uber this week. Right? You know, and that's a case where we could have helped. >>Well just real quick, explain the Uber thing cause it was a contractor. Just give a quick highlight of what happened so you can connect the >>Dots. Yeah, no problem. So there it was, I think it was one of those, you know, games where they would try and test an environment. And what the pen tester did was he kept on calling them MFA guys being like, I need to reset my password re to set my password. And eventually the customer service guy said, Okay, I'm resetting it. Once he had reset and bypassed the multifactor authentication, he then was able to get in and get access to the domain area that he was in or the, not the domain, but he was able to gain access to a partial part of the network. He then paralleled over to what would I assume is like a VA VMware or some virtual machine that had notes that had all of the credentials for logging into various domains. And so within minutes they had access. And that's the sort of stuff that we do under, you know, a lot of these tools. >>Like not, and I'm not, you know, you think about the cacophony of tools that are out there in a CTA orchestra architecture, right? I'm gonna get like a Zscaler, I'm gonna have Okta, I'm gonna have a Splunk, I'm gonna do this sore system. I mean, I don't mean to name names, we're gonna have crowd strike or, or Sentinel one in there. It's just, it's a cacophony of things that don't work together. They weren't designed work together. And so we have seen so many times in our business through our customer support and just working with customers when we do their pen test, that there will be 5,000 servers out there. Three are misconfigured. Those three misconfigurations will create the open door. Cause remember the hacker only needs to be right once, the defender needs to be right all the time. And that's the challenge. And so that's why I'm really passionate about what we're doing here at Horizon three. I see this my digital transformation, migration and security going on, which we're at the tip of the sp, it's why I joined say Hall coming on this journey and just super excited about where the path's going and super excited about the relationship with Splunk. I get into more details on some of the specifics of that. But you know, >>I mean, well you're nailing, I mean we've been doing a lot of things around super cloud and this next gen environment, we're calling it NextGen. You're really seeing DevOps, obviously Dev SecOps has, has already won the IT role has moved to the developer shift left as an indicator of that. It's one of the many examples, higher velocity code software supply chain. You hear these things. That means that it is now in the developer hands, it is replaced by the new ops, data ops teams and security where there's a lot of horizontal thinking. To your point about access, there's no more perimeter. So >>That there is no perimeter. >>Huge. A hundred percent right, is really right on. I don't think it's one time, you know, to get in there. Once you're in, then you can hang out, move around, move laterally. Big problem. Okay, so we get that. Now, the challenges for these teams as they are transitioning organizationally, how do they figure out what to do? Okay, this is the next step. They already have Splunk, so now they're kind of in transition while protecting for a hundred percent ratio of success. So how would you look at that and describe the challenges? What do they do? What is, what are the teams facing with their data and what's next? What do they, what do they, what action do they take? >>So let's do some vernacular that folks will know. So if I think about dev sec ops, right? We both know what that means, that I'm gonna build security into the app, but no one really talks about SEC DevOps, right? How am I building security around the perimeter of what's going inside my ecosystem and what are they doing? And so if you think about what we're able to do with somebody like Splunk is we could pen test the entire environment from soup to nuts, right? So I'm gonna test the end points through to it. So I'm gonna look for misconfigurations, I'm gonna, and I'm gonna look for credential exposed credentials. You know, I'm gonna look for anything I can in the environment. Again, I'm gonna do it at at light speed. And, and what we're, what we're doing for that SEC dev space is to, you know, did you detect that we were in your environment? >>So did we alert Splunk or the SIM that there's someone in the environment laterally moving around? Did they, more importantly, did they log us into their environment? And when did they detect that log to trigger that log? Did they alert on us? And then finally, most importantly, for every CSO out there is gonna be did they stop us? And so that's how we, we, we do this in, I think you, when speaking with Stay Hall, before, you know, we've come up with this boils U Loop, but we call it fine fix verify. So what we do is we go in is we act as the attacker, right? We act in a production environment. So we're not gonna be, we're a passive attacker, but we will go in un credentialed UN agents. But we have to assume, have an assumed breach model, which means we're gonna put a Docker container in your environment and then we're going to fingerprint the environment. >>So we're gonna go out and do an asset survey. Now that's something that's not something that Splunk does super well, you know, so can Splunk see all the assets, do the same assets marry up? We're gonna log all that data and think then put load that into the Splunk sim or the smoke logging tools just to have it in enterprise, right? That's an immediate future ad that they've got. And then we've got the fix. So once we've completed our pen test, we are then gonna generate a report and we could talk about about these in a little bit later. But the reports will show an executive summary the assets that we found, which would be your asset discovery aspect of that, a fixed report. And the fixed report I think is probably the most important one. It will go down and identify what we did, how we did it, and then how to fix that. >>And then from that, the pen tester or the organization should fix those. Then they go back and run another test. And then they validate through like a change detection environment to see, hey, did those fixes taste, play take place? And you know, SNA Hall, when he was the CTO of JS o, he shared with me a number of times about, he's like, Man, there would be 15 more items on next week's punch sheet that we didn't know about. And it's, and it has to do with how we, you know, how they were prioritizing the CVEs and whatnot because they would take all CVS was critical or non-critical. And it's like we are able to create context in that environment that feeds better information into Splunk and whatnot. That >>Was a lot. That brings, that brings up the, the efficiency for Splunk specifically. The teams out there. By the way, the burnout thing is real. I mean, this whole, I just finished my list and I got 15 more or whatever the list just can, keeps, keeps growing. How did Node zero specifically help Splunk teams be more efficient? Now that's the question I want to get at, because this seems like a very scalable way for Splunk customers and teams, service teams to be more efficient. So the question is, how does Node zero help make Splunk specifically their service teams be more efficient? >>So to, so today in our early interactions with building Splunk customers, what we've seen are five things, and I'll start with sort of identifying the blind spots, right? So kind of what I just talked about with you. Did we detect, did we log, did we alert? Did they stop node zero, right? And so I would, I put that at, you know, a a a more layman's third grade term. And if I was gonna beat a fifth grader at this game would be, we can be the sparring partner for a Splunk enterprise customer, a Splunk essentials customer, someone using Splunk soar, or even just an enterprise Splunk customer that may be a small shop with three people and, and just wants to know where am I exposed. So by creating and generating these reports and then having the API that actually generates the dashboard, they can take all of these events that we've logged and log them in. >>And then where that then comes in is number two is how do we prioritize those logs, right? So how do we create visibility to logs that are, have critical impacts? And again, as I mentioned earlier, not all CVEs are high impact regard and also not all are low, right? So if you daisy chain a bunch of low CVEs together, boom, I've got a mission critical AP CVE that needs to be fixed now, such as a credential moving to an NT box that's got a text file with a bunch of passwords on it, that would be very bad. And then third would be verifying that you have all of the hosts. So one of the things that Splunk's not particularly great at, and they, they themselves, they don't do asset discovery. So do what assets do we see and what are they logging from that? And then for, from, for every event that they are able to identify the, one of the cool things that we can do is actually create this low-code, no-code environment. >>So they could let, you know, float customers can use Splunk. So to actually triage events and prioritize that events or where they're being routed within it to optimize the SOX team time to market or time to triage any given event. Obviously reducing mtr. And then finally, I think one of the neatest things that we'll be seeing us develop is our ability to build glass tables. So behind me you'll see one of our triage events and how we build a lock Lockheed Martin kill chain on that with a glass table, which is very familiar to this Splunk community. We're going to have the ability, not too distant future to allow people to search, observe on those IOCs. And if people aren't familiar with an ioc, it's an incident of compromise. So that's a vector that we want to drill into. And of course who's better at drilling in into data and Splunk. >>Yeah, this is a critical, this is awesome synergy there. I mean I can see a Splunk customer going, Man, this just gives me so much more capability. Action actionability. And also real understanding, and I think this is what I wanna dig into, if you don't mind understanding that critical impact, okay. Is kind of where I see this coming. I got the data, data ingest now data's data. But the question is what not to log, You know, where are things misconfigured? These are critical questions. So can you talk about what it means to understand critical impact? >>Yeah, so I think, you know, going back to those things that I just spoke about, a lot of those CVEs where you'll see low, low, low and then you daisy chain together and you're suddenly like, oh, this is high now. But then to your other impact of like if you're a, if you're a a Splunk customer, you know, and I had, I had several of them, I had one customer that, you know, terabytes of McAfee data being brought in and it was like, all right, there's a lot of other data that you probably also wanna bring, but they could only afford, wanted to do certain data sets because that's, and they didn't know how to prioritize or filter those data sets. And so we provide that opportunity to say, Hey, these are the critical ones to bring in. But there's also the ones that you don't necessarily need to bring in because low CVE in this case really does mean low cve. >>Like an ILO server would be one that, that's the print server where the, your admin credentials are on, on like a, a printer. And so there will be credentials on that. That's something that a hacker might go in to look at. So although the CVE on it is low, if you daisy chain was something that's able to get into that, you might say, ah, that's high. And we would then potentially rank it giving our AI logic to say that's a moderate. So put it on the scale and we prioritize though, versus a, a vulner review scanner's just gonna give you a bunch of CVEs and good luck. >>And translating that if I, if I can and tell me if I'm wrong, that kind of speaks to that whole lateral movement. That's it. Challenge, right? Print server, great example, look stupid low end, who's gonna wanna deal with the print server? Oh, but it's connected into a critical system. There's a path. Is that kind of what you're getting at? >>Yeah, I used daisy chain. I think that's from the community they came from. But it's, it's just a lateral movement. It's exactly what they're doing. And those low level, low critical lateral movements is where the hackers are getting in. Right? So that's what the beauty thing about the, the Uber example is that who would've thought, you know, I've got my multifactor authentication going in a human made a mistake. We can't, we can't not expect humans to make mistakes. Were fall, were fallible, right? Yeah. The reality is is once they were in the environment, they could have protected themselves by running enough pen tests to know that they had certain exposed credentials that would've stopped the breach. Yeah. And they did not, had not done that in their environment. And I'm not poking. Yeah, >>They put it's interesting trend though. I mean it's obvious if sometimes those low end items are also not protected well. So it's easy to get at from a hacker standpoint, but also the people in charge of them can be fished easily or spear fished because they're not paying attention. Cause they don't have to. No one ever told them, Hey, be careful of what you collect. >>Yeah. For the community that I came from, John, that's exactly how they, they would meet you at a, an international event introduce themselves as a graduate student. These are national actor states. Would you mind reviewing my thesis on such and such? And I was at Adobe at the time though I was working on this and start off, you get the pdf, they opened the PDF and whoever that customer was launches, and I don't know if you remember back in like 2002, 2008 time frame, there was a lot of issues around IP being by a nation state being stolen from the United States and that's exactly how they did it. And John, that's >>Or LinkedIn. Hey I wanna get a joke, we wanna hire you double the salary. Oh I'm gonna click on that for sure. You know? Yeah, >>Right. Exactly. Yeah. The one thing I would say to you is like when we look at like sort of, you know, cuz I think we did 10,000 pen test last year is it's probably over that now, you know, we have these sort of top 10 ways that we think then fine people coming into the environment. The funniest thing is that only one of them is a, a CVE related vulnerability. Like, you know, you guys know what they are, right? So it's it, but it's, it's like 2% of the attacks are occurring through the CVEs, but yet there's all that attention spent to that. Yeah. And very little attention spent to this pen testing side. Yeah. Which is sort of this continuous threat, you know, monitoring space and, and, and this vulnerability space where I think we play such an important role and I'm so excited to be a part of the tip of the spear on this one. >>Yeah. I'm old enough to know the movie sneakers, which I love as a, you know, watching that movie, you know, professional hackers are testing, testing, always testing the environment. I love this. I gotta ask you, as we kind of wrap up here, Chris, if you don't mind the benefits to team professional services from this alliance, big news Splunk and you guys work well together. We see that clearly. What are, what other benefits do professional services teams see from the Splunk and Horizon three AI alliance? >>So if you're a, I think for, from our, our, from both of our partners as we bring these guys together and many of them already are the same partner, right? Is that first off, the licensing model is probably one of the key areas that we really excel at. So if you're an end user, you can buy for the enterprise by the enter of IP addresses you're using. But if you're a partner working with this, there's solution ways that you can go in and we'll license as to MSPs and what that business model on our MSPs looks like. But the unique thing that we do here is this c plus license. And so the Consulting Plus license allows like a, somebody a small to midsize to some very large, you know, Fortune 100, you know, consulting firms uses by buying into a license called Consulting Plus where they can have unlimited access to as many ips as they want. >>But you can only run one test at a time. And as you can imagine when we're going and hacking passwords and checking hashes and decrypting hashes, that can take a while. So, but for the right customer, it's, it's a perfect tool. And so I I'm so excited about our ability to go to market with our partners so that we underhand to sell, understand how not to just sell too or not tell just to sell through, but we know how to sell with them as a good vendor partner. I think that that's one thing that we've done a really good job building bringing into market. >>Yeah. I think also the Splunk has had great success how they've enabled partners and professional services. Absolutely. They've, you know, the services that layer on top of Splunk are multifold tons of great benefits. So you guys vector right into that ride, that wave with >>Friction. And, and the cool thing is that in, you know, in one of our reports, which could be totally customized with someone else's logo, we're going to generate, you know, so I, I used to work at another organization, it wasn't Splunk, but we, we did, you know, pen testing as a, as a for, for customers and my pen testers would come on site, they, they do the engagement and they would leave. And then another really, someone would be, oh shoot, we got another sector that was breached and they'd call you back, you know, four weeks later. And so by August our entire pen testings teams would be sold out and it would be like, wow. And in March maybe, and they'd like, No, no, no, I gotta breach now. And, and, and then when they do go in, they go through, do the pen test and they hand over a PDF and they pat you on the back and say, there's where your problems are, you need to fix it. And the reality is, is that what we're gonna generate completely autonomously with no human interaction is we're gonna go and find all the permutations that anything we found and the fix for those permutations and then once you fixed everything, you just go back and run another pen test. Yeah. It's, you know, for what people pay for one pen test, they could have a tool that does that. Every, every pat patch on Tuesday pen test on Wednesday, you know, triage throughout the week, >>Green, yellow, red. I wanted to see colors show me green, green is good, right? Not red. >>And once CIO doesn't want, who doesn't want that dashboard, right? It's, it's, it is exactly it. And we can help bring, I think that, you know, I'm really excited about helping drive this with the Splunk team cuz they get that, they understand that it's the green, yellow, red dashboard and, and how do we help them find more green so that the other guys are >>In Yeah. And get in the data and do the right thing and be efficient with how you use the data, Know what to look at. So many things to pay attention to, you know, the combination of both and then, then go to market strategy. Real brilliant. Congratulations Chris. Thanks for coming on and sharing this news with the detail around this Splunk in action around the alliance. Thanks for sharing, >>John. My pleasure. Thanks. Look forward to seeing you soon. >>All right, great. We'll follow up and do another segment on DevOps and IT and security teams as the new new ops, but, and Super cloud, a bunch of other stuff. So thanks for coming on. And our next segment, the CEO of Verizon, three AA, will break down all the new news for us here on the cube. You're watching the cube, the leader in high tech enterprise coverage.

(upbeat music) >> Hello everyone, and welcome to Fal.Con 2022, CrowdStrike's big user conference. You're watching the Cube. My name is Dave Vallante. I'm here with my co-host David Nicholson. CrowdStrike is a company that was founded over 10 years ago. This is about 11 years, almost to the day. They're 2 billion company in revenue terms. They're growing at about 60% a year. They've got a path they've committed to wall street. They've got a path to $5 billion by mid decade. They got a $40 billion market cap. They're free, free cash flow positive and trying to build essentially a generational company with a very growing Tam and a modern platform. CrowdStrike has the fundamental belief that the unstoppable breach is a myth. David Nicholson, even though CSOs don't believe that, CrowdStrike is on a mission. Right? >> I didn't hear the phrase. Zero trust mentioned in the keynote >> Right. >> What was mentioned was this idea that CrowdStrike isn't simply a tool, it's a platform. And obviously it takes a platform to get to 5 billion. >> Yeah. So let's talk about the keynote. George Kurtz, the CEO came on. I thought the keynote was, was measured, but very substantive. It was not a lot of hype in there. Most security conferences, the two exceptions are this one and Reinforce, Amazon's big security conference. Steven Schmidt. The first time I was at a Reinforce said "All this narrative about security is such a bad industry" and "We're not doing a great job." And "It's so scary." That doesn't help the industry. George Kurtz sort of took a similar message. And you know what, Dave? When I think of security outside the context of IT I think of like security guards >> Right. >> Like protecting the billionaires. Right? That's a powerful, you know, positive thing. It's not really a defensive movement even though it is defensive but so that was kind of his posture there. But he talked about essentially what I call, not his words permanent changes in the, in the in the cyber defense industry, subsequent to the pandemic. Again, he didn't specifically mention the pandemic but he alluded to, you know, this new world that we live in. Fal.Con is a hundred sessions, eight tracks. And really his contention is we're in the early innings. These guys got 20,000 customers. And I think they got the potential to have hundreds of thousands. >> Yeah. Yeah. So, if I'm working with a security company I want them to be measured. I'm not looking for hype. I don't want those. I don't want those guards to be in disco shirts. I want them in black suits. So, you know, so the, the, the point about measured is is I think a positive one. I was struck by the competence of the people who were on stage today. I have seen very very large companies become kind of bureaucratic. And sometimes you don't get the best of the best up on stage. And we saw a lot of impressive folks. >> Yeah. Michael Santonis get up, but before we get to him. So, a couple points that Kurtz made he said, "digital transformation is needed to bring modern architectures to IT. And that brings modern security." And he laid out that whole sort of old way, new way very Andy Jassy-like old guard, new guard. He didn't hit on it that hard but he basically said "security is all about mitigating risk." And he mentioned that the the CSO I say CSO, he says CSO or CSO has a seat at the board. Now, many CSOs are board level participants. And then he went into the sort of four pillars of, of workload, and the areas that they focus on. So workload to them is end point, identity, and then data. They don't touch network security. That's where they partner with the likes of Cisco, >> Right. >> And Palo Alto networks. But then they went deep into identity threat protection, data, which is their observability platform from an acquisition called Humio. And then they went big time into XDR. We're going to talk about all this stuff. He said, "data is the new digital currency." Talked a lot about how they're now renaming, Humio, Log Scale. That's their Splunk killer. We're going to talk about that all week. And he talked a little bit about the single agent architecture. That is kind of the linchpin of CrowdStrike's architecture. And then Michael Santonis, the CTO came on and did a deep dive into each of those, and really went deep into XDR extended, right? Detection and response. XDR building on EDR. >> Yeah. I think the subject of XDR is something we'll be, we'll be touching on a lot. I think in the next two days. I thought the extension into observability was very, very interesting. When you look at performance metrics, where things are gathering those things in and being able to use a single agent to do so. That speaks to this idea that they are a platform and not just a tool. It's easy to say that you aspire to be a platform. I think that's a proof point. On the subject, by the way of their fundamental architecture. Over the years, there have been times when saying that your infrastructure requires an agent that would've been a deal killer. People say "No agents!" They've stuck to their guns because they know that the best way to deliver what they deliver is to have an agent in the environment. And it has proven to be the right strategy. >> Well, this is one of the things I want to explore with the technical architects that come on here today is, how do you build a lightweight agent that can do everything that you say it's going to do? Because they started out at endpoint, and then they've extended it to all these other modules, you know, identity. They're now into observability. They've got this data platform. They just announced that acquisition of another company they bought Preempt, which is their identity. They announced Responsify, responsify? Reposify, which is sort of extends the observability and gives them visualization or visibility. And I'm like, how do you take? How do you keep an agent lightweight? That's one of the things I want to better understand. And then the other is, as you get into XDR I thought Michael Santonis was pretty interesting. He had black hat last month. He did a little video, you know. >> That was great >> Man in the street, what's XDR what's XDR what's XDR. I thought the best response was, somebody said "a holistic approach to end point security." And so it's really an evolution of, of EDR. So we're going to talk about that. But, how do you keep an agent lightweight and still support all these other capabilities? That's something I really want to dig into, you know, without getting bloated. >> Yeah, Yeah. I think it's all about the TLAs, Dave. It's about the S, it's about SDKs and APIs and having an ecosystem of partners that will look at the lightweight agent and then develop around it. Again, going back to the idea of platform, it's critical. If you're trying to do it all on your own, you get bloat. If you try to be all things to all people with your agent, if you try to reverse engineer every capability that's out there, it doesn't work. >> Well that's one of the things that, again I want to explore because CrowdStrike is trying to be a generational company. In the Breaking Analysis that we published this week. One of the things I said, "In order to be a generational company you have to have a strong ecosystem." Now the ecosystem here is respectable, you know, but it's obviously not AWS class. You know, I think Snowflake is a really good example, ServiceNow. This feels to me like ServiceNow circa 2013. >> Yeah. >> And we've seen how ServiceNow has evolved. You know, Okta, bought Off Zero to give them the developer angle. We heard a little bit about a developer platform today. I want to dig into that some more. And we heard a lot about everybody hates their DLP. I want to get rid of my DLP, data loss prevention. And so, and the same thing with the SIM. One of the ETR round table, Eric Bradley, our colleague at a round table said "If it weren't for the compliance requirements, I would replace my SIM with XDR." And so that's again, another interesting topic. CrowdStrike, cloud native, lightweight agent, you know, some really interesting tuck in acquisitions. Great go-to-market, you know, not super hype just product that works and gets stuff done, you know, seems to have a really good, bright future. >> Yeah, no, I would agree. Definitely. No hype necessary. Just constant execution moving forward. It's clearly something that will be increasingly in demand. Another subject that came up that I thought was interesting, in the keynote, was this idea of security for elections, extending into the realm of misinformation and disinformation which are both very very loaded terms. It'll be very interesting to see how security works its way into that realm in the future. >> Yeah, yeah, >> Yeah. >> Yeah, his guy, Kevin Mandia, who is the CEO of Mandiant, which just got acquired. Google just closed the deal for $5.4 billion. I thought that was kind of light, by the way, I thought Mandiant was worth more than that. Still a good number, but, and Kevin, you know was the founder and, >> Great guy. >> they were self-funded. >> Yeah, yeah impressive. >> So. But I thought he was really impressive. He talked about election security in terms of hardening you know, the election infrastructure, but then, boom he went right to what I see as the biggest issue, disinformation. And so I'm sitting there asking myself, okay how do you deal with that? And what he talked about was mapping network effects and monitoring network effects, >> Right. >> to see who's pumping the disinformation and building career streams to really monitor those network effects, positive, you know, factual or non-factual network or information. Because a lot of times, you know, networks will pump factual information to build credibility. Right? >> Right. >> And get street cred, earn that trust. You know, you talk about zero trust. And then pump disinformation into the network. So they've now got a track. We'll get, we have Kevin Mandia on later with Sean Henry who's the CSO yeah, the the CSO or C S O, chief security officer of CrowdStrike >> more TLA. Well, so, you can think of it as almost the modern equivalent of the political ad where the candidate at the end says I support this ad or I stand behind whatever's in this ad. Forget about trying to define what is dis or misinformation. What is opinion versus fact. Let's have a standard for finding, for exposing where the information is coming from. So if you could see, if you're reading something and there is something that is easily de-code able that says this information is coming from a troll farm of a thousand bots and you can sort of examine the underlying ethos behind where this information is coming from. And you can take that into consideration. Personally, I'm not a believer in trying to filter stuff out. Put the garbage out there, just make sure people know where the garbage is coming from so they can make decisions about it. >> So I got a thought on that because, Kevin Mandia touched on it. Again, I want to ask about this. He said, so this whole idea of these, you know detecting the bots and monitoring the networks. Then he said, you can I think he said something that's to the effect of. "You can go on the offensive." And I'm thinking, okay, what does that mean? So for instance, you see it all the time. Anytime I see some kind of fact put out there, I got to start reading the comments and like cause I like to see both sides, you know. I'm right down the middle. And you'll go down and like 40 comments down, you're like, oh this is, this is fake. This video was edited, >> Right. >> Da, da, da, da, and then a bunch of other people. But then the bots take over and that gets buried. So, maybe going on the offensive is to your point. Go ahead and put it out there. But then the bots, the positive bots say, okay, by the way, this is fake news. This is an edited video FYI. And this is who put it out and here's the bot graph or something like that. And then you attack the bots with more bots and then now everybody can sort of of see it, you know? And it's not like you don't have to, you know email your friend and saying, "Hey dude, this is fake news." >> Right, right. >> You know, Do some research. >> Yeah. >> Put the research out there in volume is what you're saying. >> Yeah. So, it's an, it's just I thought it was an interesting segue into another area of security under the heading of election security. That is fraught with a lot of danger if done wrong, if done incorrectly, you know, you you get into the realm of opinion making. And we should be free to see information, but we also should have access to information about where the information is coming from. >> The other narrative that you hear. So, everything's down today again and I haven't checked lately, but security generally, we wrote about this in our Breaking Analysis. Security, somewhat, has held up in the stock market better than the broad tech market. Why? And the premise is, George Kurt said this on the last conference call, earnings call, that "security is non-discretionary." At the same time he did say that sales cycles are getting a little longer, but we see this as a positive for CrowdStrike. Because CrowdStrike, their mission, or one of their missions is to consolidate all these point tools. We've talked many, many times in the Cube, and in Breaking Analysis and on Silicon Angle, and on Wikibon, how the the security business use too many point tools. You know this as a former CTO. And, now you've got all these stove pipes, the number one challenge the CSOs face is lack of talent. CrowdStrike's premise is they can consolidate that with the Fal.Con platform, and have a single point of control. "Single pane of glass" to use that bromide. So, the question is, is security really non-discretionary? My answer to that is yes and no. It is to a sense, because security is the number one priority. You can't be lax on security. But at the same time the CSO doesn't have an open checkbook, >> Right. >> He or she can't just say, okay, I need this. I need that. I need this. There's other competing initiatives that have to be taken in balance. And so, we've seen in the ETR spending data, you know. By the way, everything's up relative to where it was, pre you know, right at the pandemic, right when, pandemic year everything was flat to down. Everything's up, really up last year, I don't know 8 to 10%. It was expected to be up 8% this year, let's call it 6 to 7% in 21. We were calling for 7 to 8% this year. It's back down to like, you know, 4 or 5% now. It's still healthy, but it's softer. People are being more circumspect. People aren't sure about what the fed's going to do next. Interest rates, you know, loom large. A lot of uncertainty out here. So, in that sense, I would say security is not non-discretionary. Sorry for the double negative. What's your take? >> I think it's less discretionary. >> Okay. >> Food, water, air. Non-discretionary. (David laughing) And then you move away in sort of gradations from that point. I would say that yeah, it is, it falls into the category of less-discretionary. >> Alright. >> Which is a good place to be. >> Dave Nicholson and David Vallante here. Two days of wall to wall coverage of Fal.Con 2022, CrowdStrike's big user conference. We got some great guests. Keep it right there, we'll be right back, right after this short break. (upbeat music)

>>Oracle continues to enhance my sequel Heatwave at a very rapid pace. The company is now in its fourth major release since the original announcement in December 2020. 1 of the main criticisms of my sequel, Heatwave, is that it only runs on O. C I. Oracle Cloud Infrastructure and as a lock in to Oracle's Cloud. Oracle recently announced that heat wave is now going to be available in AWS Cloud and it announced its intent to bring my sequel Heatwave to Azure. So my secret heatwave on AWS is a significant TAM expansion move for Oracle because of the momentum AWS Cloud continues to show. And evidently the Heatwave Engineering team has taken the development effort from O. C I. And is bringing that to A W S with a number of enhancements that we're gonna dig into today is senior vice president. My sequel Heatwave at Oracle is back with me on a cube conversation to discuss the latest heatwave news, and we're eager to hear any benchmarks relative to a W S or any others. Nippon has been leading the Heatwave engineering team for over 10 years and there's over 100 and 85 patents and database technology. Welcome back to the show and good to see you. >>Thank you. Very happy to be back. >>Now for those who might not have kept up with the news, uh, to kick things off, give us an overview of my sequel, Heatwave and its evolution. So far, >>so my sequel, Heat Wave, is a fully managed my secret database service offering from Oracle. Traditionally, my secret has been designed and optimised for transaction processing. So customers of my sequel then they had to run analytics or when they had to run machine learning, they would extract the data out of my sequel into some other database for doing. Unlike processing or machine learning processing my sequel, Heat provides all these capabilities built in to a single database service, which is my sequel. He'd fake So customers of my sequel don't need to move the data out with the same database. They can run transaction processing and predicts mixed workloads, machine learning, all with a very, very good performance in very good price performance. Furthermore, one of the design points of heat wave is is a scale out architecture, so the system continues to scale and performed very well, even when customers have very large late assignments. >>So we've seen some interesting moves by Oracle lately. The collaboration with Azure we've we've covered that pretty extensively. What was the impetus here for bringing my sequel Heatwave onto the AWS cloud? What were the drivers that you considered? >>So one of the observations is that a very large percentage of users of my sequel Heatwave, our AWS users who are migrating of Aurora or so already we see that a good percentage of my secret history of customers are migrating from GWS. However, there are some AWS customers who are still not able to migrate the O. C. I to my secret heat wave. And the reason is because of, um, exorbitant cost, which was charges. So in order to migrate the workload from AWS to go see, I digress. Charges are very high fees which becomes prohibitive for the customer or the second example we have seen is that the latency of practising a database which is outside of AWS is very high. So there's a class of customers who would like to get the benefits of my secret heatwave but were unable to do so and with this support of my secret trip inside of AWS, these customers can now get all the grease of the benefits of my secret he trip without having to pay the high fees or without having to suffer with the poorly agency, which is because of the ws architecture. >>Okay, so you're basically meeting the customer's where they are. So was this a straightforward lifted shift from from Oracle Cloud Infrastructure to AWS? >>No, it is not because one of the design girls we have with my sequel, Heatwave is that we want to provide our customers with the best price performance regardless of the cloud. So when we decided to offer my sequel, he headed west. Um, we have optimised my sequel Heatwave on it as well. So one of the things to point out is that this is a service with the data plane control plane and the console are natively running on AWS. And the benefits of doing so is that now we can optimise my sequel Heatwave for the E. W s architecture. In addition to that, we have also announced a bunch of new capabilities as a part of the service which will also be available to the my secret history of customers and our CI, But we just announced them and we're offering them as a part of my secret history of offering on AWS. >>So I just want to make sure I understand that it's not like you just wrapped your stack in a container and stuck it into a W s to be hosted. You're saying you're actually taking advantage of the capabilities of the AWS cloud natively? And I think you've made some other enhancements as well that you're alluding to. Can you maybe, uh, elucidate on those? Sure. >>So for status, um, we have taken the mind sequel Heatwave code and we have optimised for the It was infrastructure with its computer network. And as a result, customers get very good performance and price performance. Uh, with my secret he trade in AWS. That's one performance. Second thing is, we have designed new interactive counsel for the service, which means that customers can now provision there instances with the council. But in addition, they can also manage their schemas. They can. Then court is directly from the council. Autopilot is integrated. The council we have introduced performance monitoring, so a lot of capabilities which we have introduced as a part of the new counsel. The third thing is that we have added a bunch of new security features, uh, expose some of the security features which were part of the My Secret Enterprise edition as a part of the service, which gives customers now a choice of using these features to build more secure applications. And finally, we have extended my secret autopilot for a number of old gpus cases. In the past, my secret autopilot had a lot of capabilities for Benedict, and now we have augmented my secret autopilot to offer capabilities for elderly people. Includes as well. >>But there was something in your press release called Auto thread. Pooling says it provides higher and sustained throughput. High concerns concerns concurrency by determining Apple number of transactions, which should be executed. Uh, what is that all about? The auto thread pool? It seems pretty interesting. How does it affect performance? Can you help us understand that? >>Yes, and this is one of the capabilities of alluding to which we have added in my secret autopilot for transaction processing. So here is the basic idea. If you have a system where there's a large number of old EP transactions coming into it at a high degrees of concurrency in many of the existing systems of my sequel based systems, it can lead to a state where there are few transactions executing, but a bunch of them can get blocked with or a pilot tried pulling. What we basically do is we do workload aware admission control and what this does is it figures out, what's the right scheduling or all of these algorithms, so that either the transactions are executing or as soon as something frees up, they can start executing, so there's no transaction which is blocked. The advantage to the customer of this capability is twofold. A get significantly better throughput compared to service like Aurora at high levels of concurrency. So at high concurrency, for instance, uh, my secret because of this capability Uh oh, thread pulling offers up to 10 times higher compared to Aurora, that's one first benefit better throughput. The second advantage is that the true part of the system never drops, even at high levels of concurrency, whereas in the case of Aurora, the trooper goes up, but then, at high concurrency is, let's say, starting, uh, level of 500 or something. It depends upon the underlying shit they're using the troopers just dropping where it's with my secret heatwave. The truth will never drops. Now, the ramification for the customer is that if the truth is not gonna drop, the user can start off with a small shape, get the performance and be a show that even the workload increases. They will never get a performance, which is worse than what they're getting with lower levels of concurrency. So this let's leads to customers provisioning a shape which is just right for them. And if they need, they can, uh, go with the largest shape. But they don't like, you know, over pay. So those are the two benefits. Better performance and sustain, uh, regardless of the level of concurrency. >>So how do we quantify that? I know you've got some benchmarks. How can you share comparisons with other cloud databases especially interested in in Amazon's own databases are obviously very popular, and and are you publishing those again and get hub, as you have done in the past? Take us through the benchmarks. >>Sure, So benchmarks are important because that gives customers a sense of what performance to expect and what price performance to expect. So we have run a number of benchmarks. And yes, all these benchmarks are available on guitar for customers to take a look at. So we have performance results on all the three castle workloads, ol DB Analytics and Machine Learning. So let's start with the Rdp for Rdp and primarily because of the auto thread pulling feature. We show that for the IPCC for attended dataset at high levels of concurrency, heatwave offers up to 10 times better throughput and this performance is sustained, whereas in the case of Aurora, the performance really drops. So that's the first thing that, uh, tend to alibi. Sorry, 10 gigabytes. B B C c. I can come and see the performance are the throughput is 10 times better than Aurora for analytics. We have done a comparison of my secret heatwave in AWS and compared with Red Ship Snowflake Googled inquiry, we find that the price performance of my secret heatwave compared to read ship is seven times better. So my sequel, Heat Wave in AWS, provides seven times better price performance than red ship. That's a very, uh, interesting results to us. Which means that customers of Red Shift are really going to take the service seriously because they're gonna get seven times better price performance. And this is all running in a W s so compared. >>Okay, carry on. >>And then I was gonna say, compared to like, Snowflake, uh, in AWS offers 10 times better price performance. And compared to Google, ubiquity offers 12 times better price performance. And this is based on a four terabyte p PCH workload. Results are available on guitar, and then the third category is machine learning and for machine learning, uh, for training, the performance of my secret heatwave is 25 times faster compared to that shit. So all the three workloads we have benchmark's results, and all of these scripts are available on YouTube. >>Okay, so you're comparing, uh, my sequel Heatwave on AWS to Red Shift and snowflake on AWS. And you're comparing my sequel Heatwave on a W s too big query. Obviously running on on Google. Um, you know, one of the things Oracle is done in the past when you get the price performance and I've always tried to call fouls you're, like, double your price for running the oracle database. Uh, not Heatwave, but Oracle Database on a W s. And then you'll show how it's it's so much cheaper on on Oracle will be like Okay, come on. But they're not doing that here. You're basically taking my sequel Heatwave on a W s. I presume you're using the same pricing for whatever you see to whatever else you're using. Storage, um, reserved instances. That's apples to apples on A W s. And you have to obviously do some kind of mapping for for Google, for big query. Can you just verify that for me, >>we are being more than fair on two dimensions. The first thing is, when I'm talking about the price performance for analytics, right for, uh, with my secret heat rape, the cost I'm talking about from my secret heat rape is the cost of running transaction processing, analytics and machine learning. So it's a fully loaded cost for the case of my secret heatwave. There has been I'm talking about red ship when I'm talking about Snowflake. I'm just talking about the cost of these databases for running, and it's only it's not, including the source database, which may be more or some other database, right? So that's the first aspect that far, uh, trip. It's the cost for running all three kinds of workloads, whereas for the competition, it's only for running analytics. The second thing is that for these are those services whether it's like shit or snowflakes, That's right. We're talking about one year, fully paid up front cost, right? So that's what most of the customers would pay for. Many of the customers would pay that they will sign a one year contract and pay all the costs ahead of time because they get a discount. So we're using that price and the case of Snowflake. The costs were using is their standard edition of price, not the Enterprise edition price. So yes, uh, more than in this competitive. >>Yeah, I think that's an important point. I saw an analysis by Marx Tamer on Wiki Bond, where he was doing the TCO comparisons. And I mean, if you have to use two separate databases in two separate licences and you have to do et yelling and all the labour associated with that, that that's that's a big deal and you're not even including that aspect in in your comparison. So that's pretty impressive. To what do you attribute that? You know, given that unlike, oh, ci within the AWS cloud, you don't have as much control over the underlying hardware. >>So look hard, but is one aspect. Okay, so there are three things which give us this advantage. The first thing is, uh, we have designed hateful foreign scale out architecture. So we came up with new algorithms we have come up with, like, uh, one of the design points for heat wave is a massively partitioned architecture, which leads to a very high degree of parallelism. So that's a lot of hype. Each were built, So that's the first part. The second thing is that although we don't have control over the hardware, but the second design point for heat wave is that it is optimised for commodity cloud and the commodity infrastructure so we can have another guys, what to say? The computer we get, how much network bandwidth do we get? How much of, like objects to a brand that we get in here? W s. And we have tuned heat for that. That's the second point And the third thing is my secret autopilot, which provides machine learning based automation. So what it does is that has the users workload is running. It learns from it, it improves, uh, various premieres in the system. So the system keeps getting better as you learn more and more questions. And this is the third thing, uh, as a result of which we get a significant edge over the competition. >>Interesting. I mean, look, any I SV can go on any cloud and take advantage of it. And that's, uh I love it. We live in a new world. How about machine learning workloads? What? What did you see there in terms of performance and benchmarks? >>Right. So machine learning. We offer three capabilities training, which is fully automated, running in France and explanations. So one of the things which many of our customers told us coming from the enterprise is that explanations are very important to them because, uh, customers want to know that. Why did the the system, uh, choose a certain prediction? So we offer explanations for all models which have been derailed by. That's the first thing. Now, one of the interesting things about training is that training is usually the most expensive phase of machine learning. So we have spent a lot of time improving the performance of training. So we have a bunch of techniques which we have developed inside of Oracle to improve the training process. For instance, we have, uh, metal and proxy models, which really give us an advantage. We use adaptive sampling. We have, uh, invented in techniques for paralysing the hyper parameter search. So as a result of a lot of this work, our training is about 25 times faster than that ship them health and all the data is, uh, inside the database. All this processing is being done inside the database, so it's much faster. It is inside the database. And I want to point out that there is no additional charge for the history of customers because we're using the same cluster. You're not working in your service. So all of these machine learning capabilities are being offered at no additional charge inside the database and as a performance, which is significantly faster than that, >>are you taking advantage of or is there any, uh, need not need, but any advantage that you can get if two by exploiting things like gravity. John, we've talked about that a little bit in the past. Or trainee. Um, you just mentioned training so custom silicon that AWS is doing, you're taking advantage of that. Do you need to? Can you give us some insight >>there? So there are two things, right? We're always evaluating What are the choices we have from hybrid perspective? Obviously, for us to leverage is right and like all the things you mention about like we have considered them. But there are two things to consider. One is he is a memory system. So he favours a big is the dominant cost. The processor is a person of the cost, but memory is the dominant cost. So what we have evaluated and found is that the current shape which we are using is going to provide our customers with the best price performance. That's the first thing. The second thing is that there are opportunities at times when we can use a specialised processor for vaccinating the world for a bit. But then it becomes a matter of the cost of the customer. Advantage of our current architecture is on the same hardware. Customers are getting very good performance. Very good, energetic performance in a very good machine learning performance. If you will go with the specialised processor, it may. Actually, it's a machine learning, but then it's an additional cost with the customers we need to pay. So we are very sensitive to the customer's request, which is usually to provide very good performance at a very low cost. And we feel is that the current design we have as providing customers very good performance and very good price performance. >>So part of that is architectural. The memory intensive nature of of heat wave. The other is A W s pricing. If AWS pricing were to flip, it might make more sense for you to take advantage of something like like cranium. Okay, great. Thank you. And welcome back to the benchmarks benchmarks. Sometimes they're artificial right there. A car can go from 0 to 60 in two seconds. But I might not be able to experience that level of performance. Do you? Do you have any real world numbers from customers that have used my sequel Heatwave on A W s. And how they look at performance? >>Yes, absolutely so the my Secret service on the AWS. This has been in Vera for, like, since November, right? So we have a lot of customers who have tried the service. And what actually we have found is that many of these customers, um, planning to migrate from Aurora to my secret heat rape. And what they find is that the performance difference is actually much more pronounced than what I was talking about. Because with Aurora, the performance is actually much poorer compared to uh, like what I've talked about. So in some of these cases, the customers found improvement from 60 times, 240 times, right? So he travels 100 for 240 times faster. It was much less expensive. And the third thing, which is you know, a noteworthy is that customers don't need to change their applications. So if you ask the top three reasons why customers are migrating, it's because of this. No change to the application much faster, and it is cheaper. So in some cases, like Johnny Bites, what they found is that the performance of their applications for the complex storeys was about 60 to 90 times faster. Then we had 60 technologies. What they found is that the performance of heat we have compared to Aurora was 100 and 39 times faster. So, yes, we do have many such examples from real workloads from customers who have tried it. And all across what we find is if it offers better performance, lower cost and a single database such that it is compatible with all existing by sequel based applications and workloads. >>Really impressive. The analysts I talked to, they're all gaga over heatwave, and I can see why. Okay, last question. Maybe maybe two and one. Uh, what's next? In terms of new capabilities that customers are going to be able to leverage and any other clouds that you're thinking about? We talked about that upfront, but >>so in terms of the capabilities you have seen, like they have been, you know, non stop attending to the feedback from the customers in reacting to it. And also, we have been in a wedding like organically. So that's something which is gonna continue. So, yes, you can fully expect that people not dressed and continue to in a way and with respect to the other clouds. Yes, we are planning to support my sequel. He tripped on a show, and this is something that will be announced in the near future. Great. >>All right, Thank you. Really appreciate the the overview. Congratulations on the work. Really exciting news that you're moving my sequel Heatwave into other clouds. It's something that we've been expecting for some time. So it's great to see you guys, uh, making that move, and as always, great to have you on the Cube. >>Thank you for the opportunity. >>All right. And thank you for watching this special cube conversation. I'm Dave Volonte, and we'll see you next time.

(upbeat music) >> Welcome back everyone to theCUBE's coverage of VMware Explore '22, formerly VMworld. This is our 12th year covering it. I'm John Furrier with Dave Vellente. Two sets, three days of wall-to-wall coverage. We're starting to get the execs rolling in from VMware. Sumit Dhawan, president of VMware's here. Great to see you. Great keynote, day one. >> Great to be here, John. Great to see you, Dave. Day one, super exciting. We're pumped. >> And you had no problem with the keynotes. We're back in person. Smooth as silk up there. >> We were talking about it. We had to like dust off a cobweb to make some of these inputs. >> It's not like riding a bike. >> No, it's not. We had about 40% of our agencies that we had to change out because they're no longer in business. So, I have to give kudos to the team who pulled it together. They did a fabulous job. >> You do a great check, great presentation. I know you had a lot to crack in there. Raghu set the table. I know this is for him, this was a big moment to lay out the narrative, address the Broadcom thing right out of the gate, wave from Hock Tan in the audience, and then got into the top big news. Still a lot of meat on the bone. You get up there, you got to talk about the use cases, vSphere 8, big release, a lot of stuff. Take us through the keynote. What was the important highlights for you to share, the folks watching that didn't see the keynote or wanted to get your perspective? >> Well, first of all, did any of you notice that Raghu was running on the stage? He did not do that in rehearsal. (John chuckles) I was a little bit worried, but he really did it. >> I said, I betcha that was real. (everyone chuckles) >> Anyways, the jokes aside, he did fabulous. Lays out the strategy. My thinking, as you said, was to first of all speak with their customers and explain how every enterprise is facing with this concept of cloud chaos that Raghu laid out and CVS Health story sort of exemplifies the situation that every customer is facing. They go in, they start with cloud first, which is needed, I think that's the absolutely right approach. Very quickly build out a model of getting a cloud ops team and a platform engineering team which oftentimes be a parallel work stream to a private cloud infrastructure. Great start. But as Roshan, the CIO at CVS Health laid out, there's an inflection point. And that's when you have to converge these because the use cases are where stakeholders, this is the lines of businesses, app developers, finance teams, and security teams, they don't need this stove piped information coming at 'em. And the converge model is how he opted to organize his team. So we called it a multi-cloud team, just like a workspace team. And listen, our commitment and innovations are to solve the problems of those teams so that the stakeholders get what they need. That's the rest of the keynote. >> Yeah, first of all, great point. I want to call out that inflection point comment because we've been reporting coming into VMworld with super cloud and other things across open source and down into the weeds and into the hood. The chaos is real. So, good call. I love how you guys brought that up there. But all industry inflection points, if you go back in history of the tech industry, at every single major inflection point, there was chaos, complexity, or an enemy proprietary. However you want to look at it, there was a situation where you needed to kind of reign in the chaos as Andy Grove would say. So we're at that inflection point, I think that's consistent. And also the ecosystem floor yesterday, the expo floor here in San Francisco with your partners, it was vibrant. They're all on this wave. There is a wave and an inflection point. So, okay. I buy that. So, if you buy the inflection point, what has to happen next? Because this is where we're at. People are feeling it. Some say, I don't have a problem but they're cut chaos such is the problem. So, where do you see that? How does VMware's team organizing in the industry and for customers specifically to solve the chaos, to reign it in and cross over? >> Yeah, you're a 100% right. Every inflection point is associated with some kind of a chaos that had to be reigned in. So we are focused on two major things right now which we have made progress in. And maybe third, we are still work in-progress. Number one is technology. Today's technology announcements are directly to address how that streamlining of chaos can be done through a cloud smart approach that we laid out. Our Aria, a brand new solution for management, significant enhancements to Tanzu, all of these for public cloud based workloads that also extend to private cloud. And then our cloud infrastructure with newer capabilities with AWS, Azure, as well as with new innovations on vSphere 8 and vSAN 8. And then last but not the least, our continuous automation to enable anywhere workspace. All these are simple innovation that have to address because without those innovations, the problem is that the chaos oftentimes is created because lack of technology and as a result structure has to be put in place because tooling and technology is not there. So, number one goal we see is providing that. Second is we have to be independent, provide support for every possible cloud but not without being a partner of theirs. That's not an easy thing to do but we have the DNA as a company, we have done that with data centers in the past, even though being part of Dell we did that in the data center in the past, we have done that in mobility. And so we have taken the challenge of doing that with the cloud. So we are continually building newer innovation and stronger and stronger partnerships with cloud provider which is the basis of our commercial relationships with Microsoft Azure too, where we have brought Azure VMware solution into VMware cloud universal. Again, that strengthens the value of us being neutral because it's very important to have a Switzerland party that can provide these multi-cloud solutions that doesn't have an agenda of a specific cloud, yet an ecosystem, or at least an influence with the ecosystem that can bring going forward. >> Okay, so technology, I get that. Open, not going to be too competitive, but more open. So the question I got to ask you is what is the disruptive enabler to make that happen? 'Cause you got customers, partners and team of VMware, what's the disruptive enabler that's going to get you to that level? >> Over the hump. I mean, listen, our value is this community. All this community has one of two paths to go. Either, they become stove piped into just the public-private cloud infrastructure or they step up as this convergence that's happening around them to say, "You know what? I have the solution to tame this multi-cloud complexity, to reign the chaos," as you mentioned because tooling and technologies are available. And I know they work with the ecosystem. And our objective is to bring this community to that point. And to me, that is the best path to overcome it. >> You are the connective tissue. I was able to sit into the analyst meeting today. You were sort of the proxy for CVS Health where you talked about the private that's where you started, the public cloud ops team, bringing that together. The platform is the glue. That is the connective tissue. That's where Tanzu comes in. That's where Aria comes in. And that is the disruptive technology which it's hard to build that. >> From a technology perspective, it's an enabler of something that has never been done before in that level of comprehensiveness, from a more of a infrastructure side thinking perspective. Yes, infrastructure teams have enabled self-service portals. Yes, infrastructure teams have given APIs to developers, but what we are enabling through Tanzu is completely next level where you have a lot richer experience for developers so that they never ever have to think about the infrastructure at all. Because even when you enable infrastructure as API, that's still an API of the infrastructure. We go straight to the application tier where they're just thinking about authorized set of microservices. Containers can be orchestrated and built automatically, shifting security left where we're truly checking them or enabling them to check the security vulnerabilities as they're developing the application, not going into the production when they have to touch the infrastructure. To me, that's an enabler of a special power that this new multi-cloud team can have across cloud which they haven't had in the past. >> Yeah, it's funny, John, I'd say very challenging technically. The challenge in 2010 was the software mainframe, remember the marketing people killed that term. >> Yeah, exactly. >> But you think about that. We're going to make virtualization and the overhead associated with that irrelevant. We're going to be able to run any workload and VMware achieved that. Now you're saying we run anything anywhere, any Kubernete, any container. >> That's the reality. That's the chaos. >> And the cloud and that's a new, real problem. Real challenging problem that requires serious engineering. >> Well, I mean it's aspirational, right? Let's get the reality, right? So true spanning cloud, not yet there. You guys, I think your vision is definitely right on in the sense that we'd like the chaos and multicloud's a reality. The question is AWS, Azure, Google Cloud, other clouds, they're not going to sit still. No one's going to let VMware just come up and take everything. You got to enable so the market- >> True, true. I don't think this is the case of us versus them because there is so much that they have to express in terms of the value of every cloud. And this happened in the case of, by the way, whether you go into infrastructure or even workspace solutions, as long as the richest of the experience and richest of the controls are provided, for their cloud to the developers that makes the adoption of their cloud simpler. It's a win-win for every party. >> That's the key. I think the simplest. So, I want to ask you, this comes up a lot and I love that you brought that up, simple and self-service has proven developers who are driving the change, cloud DevOps developers. They're driving the change. They're in charge more than ever. They want self-service, easier to deploy. I want a test, if I don't like it, I want to throw it away. But if I like something, I want to stick with it. So it's got to be self-service. Now that's antithetical to the old enterprise model of solve complexity with more complexity. >> Yeah, yeah. >> So the question for you is as the president of VMware, do you feel good that you guys are looking out over the landscape where you're riding into the valley of the future with the demand being automation, completely invisible, abstraction layer, new use case scenarios for IT and whatever IT becomes. Take us through your mindset there, because I think that's what I'm hearing here at this year, VMware Explorer is that you guys have recognized the shift in demographics on the developer side, but ops isn't going away either. They're connecting. >> They're connected. Yeah, so our vision is, if you think about the role of developers, they have a huge influence. And most importantly they're the ones who are driving innovation, just the amount of application development, the number of developers that have emerged, yet remains the scarcest resource for the enterprise are critical. So developers often time have taken control over decision on infrastructure and ops. Why? Because infrastructure and ops haven't shown up. Not because they like it. In fact, they hate it. (John chuckles) Developers like being developers. They like writing code. They don't really want to get into the day to day operations. In fact, here's what we see with almost all our customers. They start taking control of the ops until they go into production. And at that point in time, they start requesting one by one functions of ops, move to ops because they don't like it. So with our approach and this sort of, as we are driving into the beautiful valley of multi-cloud like you laid out, in our approach with the cross cloud services, what we are saying is that why don't we enable this new team which is a reformatted version of the traditional ops, it has the platform engineering in it, the key skill that enables the developer in it, through a platform that becomes an interface to the developers. It creates that secure workflows that developers need. So that developers think and do what they really love. And the infrastructure is seamless and invisible. It's bound to happen, John. Think about it this way. >> Infrastructure is code. >> Infrastructure has code, and even next year, it's invisible because they're just dealing with the services that they need. >> So it's self-service infrastructure. And then you've got to have that capability to simplified, I'll even say automated or computational governance and security. So Chris Wolf is coming on Thursday. >> Yeah. >> Unfortunately I won't be here. And he's going to talk about all the future projects. 'Cause you're not done yet. The project narrows, it's kind of one of these boring, but important. >> Yeah, there's a lot of stuff in the oven coming out. >> There's really critical projects coming down the pipeline that support this multi-cloud vision, is it's early days. >> Well, this is the thing that we were talking about. I want to get your thoughts on. And we were commenting on the keynote review, Hock Tan bought VMware. He's a lot more there than he thought. I mean, I got to imagine him sitting in the front row going there's some stuff coming out of the oven. I didn't even, might not have known. >> He'd be like, "Hmm, this extra value." (everyone chuckles) >> He's got to be pretty stoked, don't you think? >> He is, he is. >> There's a lot of headroom on the margin. >> I mean, independent to that, I think the strategy that he sees is something that's compelling to customers which is what, in my assessment, speaking with him, he bought VMware because it's strategic to customers and the strategic value of VMware becomes even higher as we take our multi-cloud portfolio. So it's all great. >> Well, plus the ecosystem is now re-energize. It's always been energized, but energized cuz it's sort of had to be, cuz it's such a strong- >> And there was the Dell history there too. >> But, yeah it was always EMC, and then Dell, and now it's like, wow, the ecosystem's- >> Really it's released almost. I like this new team, we've been calling this new ops kind of vibe going refactored ops, as you said, that's where the action's happening because the developers want to go faster. >> They want to go faster. >> They want to go fast cuz the velocity's paying off of them. They don't want to have to wait. They don't want security reviews. They want policy. They want some guardrails. Show me the track. >> That's it. >> And let me drive this car. >> That's it because I mean think about it, if you were a developer, listen, I've been a developer. I never really wanted to see how to operate the code in production because it took time away for developing. I like developing and I like to spend my time building the applications and that's the goal of Aria and Tanzu. >> And then I got to mention the props of seeing project Monterey actually come out to fruition is huge because that's the future of computing architecture. >> I mean at this stage, if a customer from here on is modernizing their infrastructure and they're not investing in a holistic new infrastructure from a hardware and software perspective, they're missing out an opportunity on leveraging the numbers that we were showing, 20% increase in calls. Why would you not just make that investment on both the hardware and the software layer now to get the benefits for the next five-six years. >> You would and if I don't have to make any changes and I get 20% automatically. And the other thing, I don't know if people really appreciate the new curve that the Silicon industry is on. It blows away the history of Moore's law which was whatever, 35-40% a year, we're talking about 100% a year price performance or performance improvements. >> I think when you have an inflection point as we said earlier, there's going to be some things that you know is going to happen, but I think there's going to be a lot that's going to surprise people. New brands will emerge, new startups, new talent, new functionality, new use cases. So, we're going to watch that carefully. And for the folks watching that know that theCUBE's been 12 years with covering VMware VMworld, now VMware Explore, we've kind of met everybody over the years, but I want to point out a little nuance, Raghu thing in the keynote. During the end, before the collective responsibility sustainment commitment he had, he made a comment, "As proud as we are," which is a word he used, there's a lot of pride here at VMware. Raghu kind of weaved that in there, I noticed that, I want to call that out there because Raghu's proud. He's a proud product guy. He said, "I'm a product guy." He's delivering keynote. >> Almost 20 years. >> As proud as we are, there's a lot of pride at VMware, Sumit, talk about that dynamic because you mentioned customers, your customer is not a lot of churn. They've been there for a long time. They're embedded in every single company out there, pretty much VMware is in every enterprise, if not all, I mean 99%, whatever percentage it is, it's huge penetration. >> We are proud of three things. It comes down to number one, we are proud of our innovations. You can see it, you can see the tone from Raghu or myself, or other executives changes with excitement when we're talking about our technologies, we're just proud. We're just proud of it. We are a technology and product centric company. The second thing that sort of gets us excited and be proud of is exactly what you mentioned, which is the customers. The customers like us. It's a pleasure when I bring Roshan on stage and he talks about how he's expecting certain relationship and what he's viewing VMware in this new world of multi-cloud, that makes us proud. And then third, we're proud of our talent. I mean, I was jokingly talking to just the events team alone. Of course our engineers do amazing job, our sellers do amazing job, our support teams do amazing job, but we brought this team and we said, "We are going to get you to run an event after three years from not they doing one, we're going to change the name on you, we're going to change the attendees you're going to invite, we're going to change the fact that it's going to be new speakers who have never been on the stage and done that kind of presentation. >> You're also going to serve a virtual audience. >> And we're going to have a virtual audience. And you know what? They embraced it and they surprised us and it looks beautiful. So I'm proud of the talent. >> The VMware team always steps up. You never slight it, you've got great talent over there. The big thing I want to highlight as we end this day, the segment, and I'll get your thoughts and reactions, Sumit, is again, you guys were early on hybrid. We have theCUBE tape to go back into the video data lake and find the word hybrid mentioned 2013, 2014, 2015. Even when nobody was talking about hybrid. >> Yeah, yeah. >> Multicloud, Raghu, I talked to Raghu in 2016 when he did the Pat Gelsinger, I mean Raghu, Pat and Andy Jassy. >> Yeah. >> When that cloud thing got cleared up, he cleared that up. He mentioned multicloud, even then 2016, so this is not new. >> Yeah. >> You had the vision, there's a lot of stuff in the oven. You guys make announcements directionally, and then start chipping away at it. Now you got Broadcom buys VMware, what's in the oven? How much goodness is coming out that's like just hitting the fruits are starting to bear on the tree. There's a lot of good stuff and just put that, contextualize and scale that for us. What's in the oven? >> First of all, I think the vision, you have to be early to be first and we believe in it. Okay, so that's number one. Now having said that what's in the oven, you would see us actually do more controls across cloud. We are not done on networking side. Okay, we announced something as project Northstar with networking portfolio, that's not generally available. That's in the oven. We are going to come up with more capability on supporting any Kubernetes on any cloud. We did some previews of supporting, for example, EKS. You're going to see more of those cluster controls across any Kubernetes. We have more work happening on our telco partners for enablement of O-RAN as well as our edge solutions, along with the ecosystem. So more to come on those fronts. But they're all aligned with enabling customers multi-cloud through these five cross cloud services. They're all really, some of them where we have put a big sort of a version one of solution out there such as Aria continuation, some of them where even the version one's not out and you're going to see that very soon. >> All right. Sumit, what's next for you as the president? You're proud of your team, we got that. Great oven description of what's coming out for the next meal. What's next for you guys, the team? >> I think for us, two things, first of all, this is our momentum season as we call it. So for the first time, after three years, we are now being in, I think we've expanded, explored to five cities. So getting this orchestrated properly, we are expecting nearly 50,000 customers to be engaging in person and maybe a same number virtually. So a significant touchpoint, cuz we have been missing. Our customers have departed their strategy formulation and we have departed our strategy formulation. Getting them connected together is our number one priority. And number two, we are focused on getting better and better at making customers successful. There is work needed for us. We learn, then we code it and then we repeat it. And to me, those are the two key things here in the next six months. >> Sumit, thank you for coming on theCUBE. Thanks for your valuable time, sharing what's going on. Appreciate it. >> Always great to have chatting. >> Here with the president, the CEO's coming up next in theCUBE. Of course, we're John and Dave. More coverage after the short breaks, stay with us. (upbeat music)

>>Welcome to this Q conversation. I'm Dave Nicholson. And today we are joined by Andrew ish and Chris Y Moran, both from Gentech. Andrew is the vice president of marketing. Chris John is the, uh, vice president of product engineering, gentlemen, welcome to the cube. >>Welcome David. Thanks for having us. Hey, >>David, thanks for having us on your show. >>Absolutely. Give us just, let's start out by, uh, giving us some background on, on Gentech. How would you describe to a relative coming over and asking you what you do for a living? What Genotech does? >>Well, I'll take a shot at that. I'm the marketing guy, David, but, uh, I think the best way to think of Genotech first and foremost is a software company. We, uh, we do a really good job of bringing together all of that physical security sensor network onto a platform. So people can make sense out of the data that comes from video surveillance, cameras, access control, reads, license plate recognition, cameras, and from a whole host of different sensors that can live out there in the world. Temperature, sensors, microwaves, all sorts of stuff. So we're a company that's really good at making sense of complex data from sensors. That's kind of, I think that's kind of what we >>Do and, and, and we focus specifically on like larger, complex, critical infrastructure type projects, whether they be airports, uh, large enterprise campuses and whatnot. So we're not necessarily your well known consumer type brand. >>So you mentioned physical, you mentioned physical security. Um, what about the intersection between physical security and, and cyber security who are, who are the folks that you work with directly as customers and where do they, where do they sit in that spectrum of cyber versus physical? >>So we predominantly work with physical security professionals and, uh, they typically are responsible for the security of a facility, a campus, a certain area. And we'll talk about security cameras. We'll talk about access control devices with card readers and, and, and locks, uh, intrusion detection, systems, fences, and whatnot. So anything that you would see that physically protects a facility. And, uh, what's actually quite interesting is that, you know, cybersecurity, we, we hear about cybersecurity and depressed all the time, right. And who's been hacked this week is typically like, uh, a headline that we're all like looking at, uh, we're looking for in the news. Um, so we actually do quite a lot of, I would say education work with the physical security professional as it pertains to the importance of cyber security in the physical security system, which in and of itself is an information system. Right. Um, so you don't wanna put a system in place to protect your facility that is full of cybersecurity holes because at that point, you know, your physical security systems becomes, uh, your weakest link in your security chain. Uh, the way I like to say it is, you know, there's no such thing as physical security versus cyber security, it's just security. Uh, really just the concept or a context of what threat vectors does this specific control or mechanism actually protects against >>Those seem to be words to live by, but are, are they aspirational? I mean, do you, do you see gaps today, uh, between the worlds of cyber and physical security? >>I mean, for sure, right? Like we, physical security evolved from a different part of the enterprise, uh, structure then did it or cyber security. So they, they come at things from a different angle. Um, so, you know, for a long time, the two worlds didn't really meet. Uh, but now what we're seeing, I would say in the last 10 years, Christian, about that, there's a huge convergence of cyber security with physical security. It, so information technology with operation technology really coming together quite tightly in the industry. And I think leading companies and sophisticated CISOs are really giving a big pitcher thought to what's going on across the organization, not just in cybersecurity. >>Yeah. I think we've come a long way from CCTV, which stands for closed circuit television, uh, which was typically like literally separated from the rest of the organization, often managed by the facilities, uh, part of any organization. Uh, and now we're seeing more and more organizations where this is converging together, but there's still ways to go, uh, to get this proper convergence in place. But, you know, we're getting there. >>How, how does Gentech approach its addressable market? Is this, is this a direct model? Uh, do you work with partners? What, what does that look like in your world? >>Well, we're a, we're a partner led company Gentech, you know, model on many friends is all about our partners. So we go to market through our integration channel. So we work with really great integrators all around the world. Um, and they bring together our software platform, which is usually forms the nucleus of sort of any O T security network. Uh, they bring that together with all sorts of other things, such as the sensor network, the cabling, all of that. It's a very complex multiplayer world. And also in that, you know, partnership ecosystem and Christian, this is more your world. We have to build deep integrations with all of these companies that build sensors, whether that's access, Bosch, Canon, uh, Hanoi, you know, we're, we're really working with them them. And of course with our storage and server partners >>Like Dell >>Mm-hmm <affirmative>. Yeah. So we have, we have like hundreds of, I would say ecosystem partners, right? Camera manufacturers, uh, access control reader, controller manufacturers, intrusion detection, manufacturers, late LIDAR radar, you know, the list goes on and on and on. And, and basically we bring this all together. The system integrator really is going to pick best of breed based on a specific end customer's I would say requirements and then roll out the system. According >>That's very interesting, you know, at, at Silicon angle on the cube, um, we've initiated coverage of this subject of the question, does hardware still matter? And, and you know, of course we're, we're approaching that primarily from kind of the traditional it, uh, perspective, but you said at the outset, you you're a software company mm-hmm <affirmative>, but clearly correct me if I'm wrong, your software depends upon all of these hardware components and as they improve, I imagine you can do things that maybe you couldn't do before those improvements. The first thing that comes to mind is just camera resolution. Um, you know, sort of default today is 4k, uh, go back five years, 10 years. I imagine that some of the sophisticated things that you can do today weren't possible because the hardware was lagging. Is that, is that a, is that a fair assessment? >>Oh, that's a fair assessment. Just going back 20 years ago. Uh, just VGA resolution on a security camera was like out of this world resolution, uh, even more so if it was like full motion, 30 images per second. So you typically have like, probably even like three 20 by 2 44 images per second, like really lousy resolution, just from a resolution perspective, the, the imagery sensors have, have really increased in terms of what they can provide, but even more so is the horsepower of these devices. Mm-hmm, <affirmative> now it's not uncommon to have, uh, pretty, pretty powerful Silicon in those devices now that can actually run machine learning models and you can actually do computer vision and analytics straight into the device. Uh, as you know, in some of the initial years, you would actually run this on kind of racks of servers in this data center. >>Now you can actually distribute those workloads across on the edge. And what we're seeing is, you know, the power that the edge provides is us as a software company, we have the opportunity to actually bring our workloads where it makes most sense. And in some cases we'll actually also have a ground station kind of in between the sensors and potentially the cloud, uh, because the use case just, uh, calls for it. Uh, just looking from a, from a, from a video security perspective, you know, when you have hundreds or thousands of cameras on an airport, it's just not economical or not even feasible in some cases to bring all that footage to the cloud even more so when 99% of that footage is never watched by anybody. So what's the point. Uh, so you just wanna provide the clips that, that actually do matter to the cloud and for longer term retention, you also want to be able to have sometimes more resilient systems, right? So what happens if the cloud disconnects, you can stop the operations of that airport or stop that operations of that, of that prison, right? It needs to continue to operate and therefore you need higher levels of resiliency. So you do need that hardware. So it's really a question of what it calls for and having the right size type of hardware so that you don't overly complexify the installation, uh, and, and actually get the job done. Are >>You comparing airports to prisons >>Christian? Well, nowadays they're pretty much prepared <laugh>, >>But I mean, this is exactly it, David, but I mean, this payload, especially from the video surveillance, like the, the workload that's going through to the, these ground stations really demands flexible deployment, right? So like we think about it as edge to cloud and, uh, you know, that's, what's really getting us excited because it, it gives so much more flexibility to the, you know, the C I S O and security professionals in places like prisons, airports, also large scale retail and banking, and, uh, other places, >>Universities, the list goes on and on and on, and >>On the flexibility of deployment just becomes so much easier because these are lightweight, you usually word deploying on a Linux box and it can connect seamlessly with like large scale head end storage or directly to, uh, cloud providers. It's, it's really a sophisticated new way of looking at how you architect out these networks. >>You've just given, you've just given a textbook example of why, uh, folks in the it world have been talking about hybrid cloud for, for, for such a long time, and some have scoffed at the idea, but you just, you just present a perfect use case for that combination of leveraging cloud with, uh, on-premises hardware and tracking with hardware advances, um, uh, on, on the subject of camera resolution. I don't know if you've seen this meme, but there's a great one with the, the first deep field image from the, from the, I was gonna say humble, the James web space telescope, uh, in contrast with a security camera F photo, which is really blurry of someone in your driveway <laugh>, uh, which is, which is, uh, sort of funny. The reality though, is I've seen some of these latest generation security cameras, uh, you know, beyond 4k resolution. And it's amazing just, you know, the kind of detail that you can get into, but talk about what what's, what's exciting in your world. What's, what's Gentech doing, you know, over the next, uh, several quarters that's, uh, particularly interesting what's on the leading edge of your, of your world. >>Well, I think right now what's on the leading edges is being driven by our end users. So the, so the, the companies, the governments, the organizations that are implementing our software into these complex IOT networks, they wanna do more with that data, right? It's not just about, you know, monitoring surveillance. It's not just about opening and closing doors or reading license plates, but more and more we're seeing organizations taking this bigger picture view of the data that is generated in their organizations and how they can take value out of existing investments that they've made in sensor networks, uh, and to take greater insight into operations, whether that can be asset utilization, customer service efficiency, it becomes about way more than just, you know, either physical security or cyber security. It becomes really an enterprise shaping O T network. And to us, that is like a massive, massive opportunity, uh, in the, in the industry today. >>Yeah. >>Now you're you're you're oh, go ahead. I'm sorry, Christian, go ahead. Yeah, >>No, it's, it's, it's good. But, you know, going back to a comment that I mentioned earlier about how it was initially siloed and now, you know, we're kind of discovering this diamond in the rough, in terms of all these sensors that are out there, which a lot of organizations didn't even know existed or didn't even know they had. And how can you bring that on kind of across the organizations for non-security related applications? So that's kind of one very interesting kind of, uh, direction that we're, that we've been undergoing for the last few years, and then, you know, security, uh, and physical security for that matter often is kind of the bastard step child. Doesn't get all the budget and, you know, there's lots of opportunities for, to help them increase and improve their operations, uh, as, as Andrew pointed out and really help bringing them into the 21st century. >>Yeah. >>And you're, you're headquartered in Montreal, correct? >>Yes. >>Yeah. So, so the reason, the reason why that's interesting is because, um, and, you know, correct me if I'm, if I'm off base here, but, but you're sort of the bridge between north America and Europe. Uh, and, and, uh, and so you sit at that nexus where, uh, you probably have more of an awareness of, uh, trends in security, which overlap with issues of privacy. Yeah. Where Europe has led in a lot of cases. Um, some of those European like rules are coming to north America. Um, is there anything in your world that is particularly relevant or that concerns you about north America catching up, um, or, or do those worlds of privacy and security not overlap as much as I might think they do? >>Ah, thank you. Any >>Thoughts? >>Absolutely not. No, no. <laugh> joking aside. This is, this is, this is, >>Leave me hanging >><laugh>, uh, this is actually core to our DNA. And, and, and we, we often say out loud how, like Europe has really paved the way for a different way, uh, of, of looking at privacy from a security setting, right. And they're not mutually exclusive. Right. You can have high security all while protecting people's privacy. And it's all of a question of ensuring that, you know, how you kind of, I would say, uh, ethically, uh, use said technology and we can actually put some safeguards in it. So to minimize the likelihood of there being abuse, right? There's, there's something that we do, which we call the privacy protector, which, you know, for all intents and purposes, it's not that complex of an idea. It's, it's really the concept of you have security cameras in a public space or a more sensitive location. And you have your security guards that can actually watch that footage when nothing really happens. >>You, you want to protect people's privacy in these situations. Uh, however, you still want to be able to provide a view to the security guard so they can still make out that, you know, there there's actually people walking around or there's a fight that broke out. And in the likelihood that something did happen, then you can actually view the overall footage. So, and with, with the details that the cameras that you had, you know, the super high mega pixel cameras that you have will provide. So we blur the images of the individuals. We still keep the background. And once you have the proper authorization, and this is based on the governance of the organization, so it can be a four I principle where it could be the chief security officer with the chief privacy officer need to authorize this footage to be kind of UN blurred. And at that point you can UN blur the footage and provide it to law enforcement for the investigation, for example. >>Excellent. I've got Andrew, if you wanted, then I, then I'm. Well, so I, I've a, I have a final question for you. And this comes out of a game that, uh, some friends and I, some friends of mine and I devised over the years, primarily this is played with strangers that you meet on airplanes as you're traveling. But the question you ask is in your career, what you're doing now and over the course of your careers, um, what's the most shocking thing <laugh> that people would learn from what, you know, what do you, what do you find? What's the craziest thing. When you go in to look at these environments that you see that people should maybe address, um, well, go ahead and start with you, Andrew. >>I, >>The most shocking thing you see every day in your world, >>It's very interesting. The most shocking thing I think we've seen in the industry is how willing, uh, some professionals are in our industry to install any kind of device on their networks without actually taking the time to do due diligence on what kind of security risks these devices can have on a network. Because I think a lot of people don't think about a security camera as first and foremost, a computer, and it's a computer with an IP address on a network, and it has a visual sensor, but we always get pulled in by that visual sensor. Right. And it's like, oh, it's a camera. No, it's a computer. And, you know, over the last, I would say eight years in the industry, we've spent a lot of time trying to sensitize the industry to the fact that, you know, you can't just put devices on your, your network without understanding the supply chain, without understanding the motives behind who's put these together and their track record of cybersecurity. So probably the weirdest thing that I've seen in my, um, you know, career in this industry is just the willingness of people not to take time to do due diligence before they hook something up on onto their corporate network where, you know, data can start leaking out, being exfiltrated by those devices and malevolent actors behind them. So gotta ask questions about what you put on your network. >>Christian, did he steal your, did he steal your thunder? Do you have any other, any other thoughts? >>Well, so first of all, there's things I just cannot say on TV. Okay. But you can't OK. >>You can't. Yeah, yeah, yeah. Saying that you're shocked that not everyone speaks French doesn't count. Okay. Let's just get, let's get past that, but, but go, but yeah, go ahead. Any thoughts? >>So, uh, you know, I, I would say something that I I've seen a lot and, and specifically with customers sometimes that were starting to shop for a new system is you'd be surprised by first of all, there's a camera, the likelihood of actually somebody watching it live while you're actually in the field of view of that camera is close to Neil first and foremost, second, there's also a good likelihood that that camera doesn't even record. It actually is not even functional. And, and I would say a lot of organizations often realize that, you know, that camera was not functioning when they actually knew do need to get the footage. And we've seen this with some large incidents, uh, very, uh, bad incidents that happened, uh, whether in the UK or in Boston or whatnot, uh, when they're, when law enforcement is trying to get footage and they realize that a lot of cameras actually weren't recording and, and, and goes back to Andrew's point in terms of the selection process of these devices. >>Yeah. Image resolution is important, like, because you need an, an image that it actually usable so that you can actually do something with it forensically, but you know, these cameras need to be recorded by a reliable system and, and should something happen with the device. And there's always going to be something, you know, power, uh, uh, a bird ate the lens. I don't know what it might be, or squirrel ate the wire. Um, and the camera doesn't work anymore. So you have to replace it. So having a system that provides, you know, you with like health insights in terms of, of, of if it's working or not is, is actually quite important. It needs to be managed like any it environment, right? Yeah. You have all these devices and if one of them goes down, you need to manage it. And most organizations it's fire and forget, I sign a purchase order. I bought my security system, I installed it. It's done. We move on to the next one and seven years later, something bad happens. And like, uhoh, >>It's not a CCTV system. It's a network. Yeah. Life cycle management counts. >>Well, uh, I have to say on that, uh, I'm gonna be doing some research on Canadian birds and squirrels. I, I had no idea, >>Very hungry. >>Andrew, Chris, John, thank you so much. Great conversation, uh, from all of us here at the cube. Thanks for tuning in. Stay tuned. The cube from Silicon angle media, we are your leader in tech coverage.