>> Hello and welcome to theCUBE's coverage of International Women's Day. I'm John Furrier, host of theCUBE. Got a variety of interviews across the gamut from topics, women in tech, mentoring, pipelining, developers, open source, executives. Stanford's having International Women's Day celebration with the women in data science, which we're streaming that live as well. Variety of programs. In this segment, Meagen Eisenberg, friend of theCUBE, she's the CMO of Laceworks, is an amazing executive, got a great journey story as a CMO but she's also actively advising startups, companies and really pays it forward. I want to say Meagen, thank you for coming on the program and thanks for sharing. >> Yeah, thank you for having me. I'm happy to be here. >> Well, we're going to get into some of the journey celebrations that you've gone through and best practice what you've learned is pay that forward. But I got to say, one of the things that really impresses me about you as an executive is you get stuff done. You're a great CMO but also you're advised a lot of companies, you have a lot of irons in the fires and you're advising companies and sometimes they're really small startups to bigger companies, and you're paying it forward, which I love. That's kind of the spirit of this day. >> Yeah, I mean, I agree with you. When I think about my career, a lot of it was looking to mentors women out in the field. This morning I was at a breakfast by Eileen and we had the CEO of General Motors on, and she was talking about her journey nine years as a CEO. And you know, and she's paying it forward with us. But I think about, you know, when you're advising startups, you know, I've gathered knowledge and pattern recognition and to be able to share that is, you know, I enjoy it. >> Yeah. And the startups are also fun too, but it's not always easy and it can get kind of messy as you know. Some startups don't make it some succeed and it's always like the origination story is kind of rewritten and then that's that messy middle. And then it's like that arrows that don't look like a straight line but everyone thinks it's great and you know, it's not for the faint of heart. And Teresa Carlson, who I've interviewed many times, former Amazon, now she's the president of Flexport, she always says, sometimes startups on certain industries aren't for the faint of heart so you got to have a little bit of metal, right? You got to be tough. And some cases that you don't need that, but startups, it's not always easy. What have you learned? >> Yeah, I mean, certainly in the startup world, grit, creativity. You know, when I was at TripActions travel company, pandemic hits, nobody's traveling. You cut budget, you cut heads, but you focus on the core, right? You focus on what you need to survive. And creativity, I think, wins. And, you know, as a CMO when you're marketing, how do you get through that noise? Even the security space, Lacework, it's a fragmented market. You've got to be differentiated and position yourself and you know, be talking to the right target audience and customers. >> Talk about your journey over the years. What have you learned? What's some observations? Can you share any stories and best practices that someone watching could learn from? I know there's a lot of people coming into the tech space with the generative AI things going on in Cloud computing, scaling to the edge, there's a lot more aperture for technical jobs as well as just new roles and new roles that haven't, you really don't go to college for anymore. You got cybersecurity you're in. What are some of the things that you've done over your career if you can share and some best practices? >> Yeah, I think number one, continual learning. When I look through my career, I was constantly reading, networking. Part of the journey is who you're meeting along the way. As you become more senior, your ability to hire and bring in talent matters a lot. I'm always trying to meet with new people. Yeah, if I look at my Amazon feed of books I've bought, right, it kind of chronicle of my history of things I was learning about. Right now I'm reading a lot about cybersecurity, how the, you know, how how they tell me the world ends is the one I'm reading most recently. But you've got to come up to speed and then know the product, get in there and talk to customers. Certainly on the marketing front, anytime I can talk with the customer and find out how they're using us, why they love us, that, you know, helps me better position and differentiate our company. >> By the way, that book is amazing. I saw Nicole speak on Tuesday night with John Markoff and Palo Alto here. What a great story she told there. I recommend that book to everyone. It goes in and she did eight years of research into that book around zero day marketplaces to all the actors involved in security. And it was very interesting. >> Yeah, I mean, it definitely wakes you up, makes you think about what's going on in the world. Very relevant. >> It's like, yeah, it was happening all the time, wasn't it. All the hacking. But this brings me, this brings up an interesting point though, because you're in a cybersecurity area, which by the way, it's changing very fast. It's becoming a bigger industry. It's not just male dominated, although it is now, it's still male dominated, but it's becoming much more and then just tech. >> Yeah, I mean it's a constantly evolving threat landscape and we're learning, and I think more than ever you need to be able to use the data that companies have and, you know, learn from it. That's one of the ways we position ourselves. We're not just about writing rules that won't help you with those zero day attacks. You've got to be able to understand your particular environment and at any moment if it changes. And that's how we help you detect a threat. >> How is, how are things going with you? Is there any new things you guys got going on? Initiatives or programs for women in tech and increasing the range of diversity inclusion in the industry? Because again, this industry's getting much wider too. It's not just specialized, it's also growing. >> Yes, actually I'm excited. We're launching secured by women, securedbywomen.com and it's very much focused on women in the industry, which some studies are showing it's about 25% of security professionals are women. And we're going to be taking nominations and sponsoring women to go to upcoming security events. And so excited to launch that this month and really celebrate women in security and help them, you know, part of that continual learning that I talked about, making sure they're there learning, having the conversations at the conferences, being able to network. >> I have to ask you, what inspired you to pursue the career in tech? What was the motivation? >> You know, if I think way back, originally I wanted to be on the art side and my dad said, "You can do anything as long as it's in the sciences." And so in undergrad I did computer science and MIS. Graduated with MIS and computer science minor. And when I came out I was a IT engineer at Cisco and you know, that kind of started my journey and decided to go back and get my MBA. And during that process I fell in love with marketing and I thought, okay, I understand the buyer, I can come out and market technology to the IT world and developers. And then from there went to several tech companies. >> I mean my father was an engineer. He had the same kind of thing. You got to be an engineer, it's a steady, stable job. But that time, computer science, I mean we've seen the evolution of computer science now it's the most popular degree at Berkeley we've heard and around the world and the education formats are changing. You're seeing a lot of people's self-training on YouTube. The field has really changed. What are some of the challenges you see for folks trying to get into the industry and how would you advise today if you were talking to your young self, what would you, what would be the narrative? >> Yeah, I mean my drawback then was HTML pages were coming out and I thought it would be fun to design, you know, webpages. So you find something you're passionate about in the space today, whether it's gaming or it's cybersecurity. Go and be excited about it and apply and don't give up, right? Do whatever you can to read and learn. And you're right, there are a ton of online self-help. I always try to hire women and people who are continual learners and are teaching themselves something. And I try to find that in an interview to know that they, because when you come to a business, you're there to solve problems and challenges. And the folks that can do that and be innovative and learn, those are the ones I want on my team. >> It's interesting, you know, technology is now impacting society and we need everyone involved to participate and give requirements. And that kind of leads my next question for you is, like, in your opinion, or let me just step back, let me rephrase. What are some of the things that you see technology being used for, for society right now that will impact people's lives? Because this is not a gender thing. We need everybody involved 'cause society is now digital. Technology's pervasive. The AI trends now we're seeing is clearly unmasking to the mainstream that there's some cool stuff happening. >> Yeah, I mean, I think ChatGPT, think about that. All the different ways we're using it we're writing content and marketing with it. We're, you know, I just read an article yesterday, folks are using it to write children's stories and then selling those stories on Amazon, right? And the amount that they can produce with it. But if you think about it, there's unlimited uses with that technology and you've got all the major players getting involved on it. That one major launch and piece of technology is going to transform us in the next six months to a year. And it's the ability to process so much data and then turn that into just assets that we use and the creativity that's building on top of it. Even TripActions has incorporated ChatGPT into your ability to figure out where you want when you're traveling, what's happening in that city. So it's just, you're going to see that incorporated everywhere. >> I mean we've done an interview before TripAction, your other company you were at. Interesting point you don't have to type in a box to say, I'm traveling, I want a hotel. You can just say, I'm going to Barcelona for Mobile World Congress, I want to have a good time. I want some tapas and a nice dinner out. >> Yes. Yeah. That easy. We're making it easy. >> It's efficiency. >> And actually I was going to say for women specifically, I think the reason why we can do so much today is all the technology and apps that we have. I think about DoorDash, I think about Waze you know, when I was younger you had to print out instructions. Now I get in the car real quick, I need to go to soccer practice, I enter it, I need to pick them up at someone's house. I enter it. It's everything's real time. And so it takes away all the things that I don't add value to and allows me to focus on what I want in business. And so there's a bunch of, you know, apps out there that have allowed me to be so much more efficient and productive that my mother didn't have for sure when I was growing up. >> That is an amazing, I think that actually illustrates, in my opinion, the best example of ChatGPT because the maps and GPS integration were two techs, technologies merged together that replace driving and looking at the map. You know, like how do you do that? Like now it's automatically. This is what's going to happen to creative, to writing, to ideation. I even heard Nicole from her book read said that they're using ChatGPT to write zero day exploits. So you seeing it... >> That's scary stuff. You're right. >> You're seeing it everywhere. Super exciting. Well, I got to ask you before you get into some of the Lacework things that you're involved with, cause I think you're doing great work over there is, what was the most exciting projects you've worked on in your career? You came in Cisco, very technical company, so got the technical chops, CSMIS which stands for Management of Information Science for all the young people out there, that was the state of the art back then. What are some of the exciting things you've done? >> Yeah, I mean, I think about, I think about MongoDB and learning to market to developers. Taking the company public in 2017. Launching Atlas database as a service. Now there's so much more of that, you know, the PLG motion, going to TripActions, you know, surviving a pandemic, still being able to come out of that and all the learnings that went with it. You know, they recently, I guess rebranded, so they're Navan now. And then now back in the security space, you know, 14 years ago I was at ArcSite and we were bought by HP. And so getting back into the security world is exciting and it's transformed a ton as you know, it's way more complicated than it was. And so just understanding the pain of our customers and how we protect them as is fun. And I like, you know, being there from a marketing standpoint. >> Well we really appreciate you coming on and sharing that. I got to ask you, for folks watching they might be interested in some advice that you might have for them and their career in tech. I know a lot of young people love the tech. It's becoming pervasive in our lives, as we mentioned. What advice would you give for folks watching that want to start a career in tech? >> Yeah, so work hard, right? Study, network, your first job, be the best at it because every job after that you get pulled into a network. And every time I move, I'm hiring people from the last job, two jobs before, three jobs before. And I'm looking for people that are working hard, care, you know, are continual learners and you know, add value. What can you do to solve problems at your work and add value? >> What's your secret networking hack or growth hack or tip that you can share? Because you're a great networker by the way. You're amazing and you do add a lot of value. I've seen you in action. >> Well, I try never to eat alone. I've got breakfast, I've got lunch, I've got coffee breaks and dinner. And so when I'm at work, I try and always sit and eat with a team member, new group. If I'm out on the road, I'm, you know, meeting people for lunch, going for dinner, just, you know, don't sit at your desk by yourself and don't sit in the hotel room. Get out and meet with people. >> What do you think about now that we're out of the pandemic or somewhat out of the pandemic so to speak, events are back. >> Yes. >> RSA is coming up. It's a big event. The bigger events are getting bigger and then the other events are kind of smaller being distributed. What's your vision of how events are evolving? >> Yeah, I mean, you've got to be in person. Those are the relationships. Right now more than ever people care about renewals and you are building that rapport. And if you're not meeting with your customers, your competitors are. So what I would say is get out there Lacework, we're going to be at RSA, we're going to be at re:Inforce, we're going to be at all of these events, building relationships, you know, coffee, lunch, and yeah, I think the future of events are here to stay and those that don't embrace in person are going to give up business. They're going to lose market share to us. >> And networking is obviously very key on events as well. >> Yes. >> A good opportunity as always get out to the events. What's the event networking trick or advice do you give folks that are going to get out to the networking world? >> Yeah, schedule ahead of time. Don't go to an event and expect people just to come by for great swag. You should be partnering with your sales team and scheduling ahead of time, getting on people's calendars. Don't go there without having 100 or 200 meetings already booked. >> Got it. All right. Let's talk about you, your career. You're currently at Lacework. It's a very hot company in a hot field, security, very male dominated, you're a leader there. What's it like? What's the strategies? How does a woman get in there and be successful? What are some tricks, observations, any data you can share? What's the best practice? What's the secret sauce from Meagen Eisenberg? >> Yes. Yeah, for Meagen Eisenberg. For Lacework, you know, we're focused on our customers. There's nothing better than getting, being close to them, solving their pain, showcasing them. So if you want to go into security, focus on their, the issues and their problems and make sure they're aware of what you're delivering. I mean, we're focused on cloud security and we go from build time to run time. And that's the draw for me here is we had a lot of, you know, happy, excited customers by what we were doing. And what we're doing is very different from legacy security providers. And it is tapping into the trend of really understanding how much data you have and what's happening in the data to detect the anomalies and the threats that are there. >> You know, one of the conversations that I was just having with a senior leader, she was amazing and I asked her what she thought of the current landscape, the job market, the how to get promoted through the careers, all those things. And the response was interesting. I want to get your reaction. She said interdisciplinary skills are critical. And now more than ever, the having that, having a set of skills, technical and social and emotional are super valuable. Do you agree? What's your reaction to that and what would, how would you reframe that? >> Yeah, I mean, I completely agree. You can't be a leader without balance. You've got to know your craft because you're developing and training your team, but you also need to know the, you know, how to build relationships. You're not going to be successful as a C-level exec if you're not partnering across the functions. As a CMO I need to partner with product, I need to partner with the head of sales, I need to partner with finance. So those relationships matter a ton. I also need to attract the right talent. I want to have solid people on the team. And what I will say in the security, cybersecurity space, there's a talent shortage and you cannot hire enough people to protect your company in that space. And that's kind of our part of it is we reduce the number of alerts that you're getting. So you don't need hundreds of people to detect an issue. You're using technology to show, you know, to highlight the issue and then your team can focus on those alerts that matter. >> Yeah, there's a lot of emerging markets where leveling up and you don't need pedigree. You can just level up skill-wise pretty quickly. Which brings me to the next question for you is how do you keep up with all the tech day-to-day and how should someone watching stay on top of it? Because I mean, you got to be on top of this stuff and you got to ride the wave. It's pretty turbulent, but it's still growing and changing. >> Yeah, it's true. I mean, there's a lot of reading. I'm watching the news. Anytime something comes out, you know, ChatGPT I'm playing with it. I've got a great network and sharing. I'm on, you know, LinkedIn reading articles all the time. I have a team, right? Every time I hire someone, they bring new information and knowledge in and I'm you know, Cal Poly had this learn by doing that was the philosophy at San Luis Obispo. So do it. Try it, don't be afraid of it. I think that's the advice. >> Well, I love some of the points you mentioned community and network. You mentioned networking. That brings up the community question, how could people get involved? What communities are out there? How should they approach communities? 'Cause communities are also networks, but also they're welcoming people in that form networks. So it's a network of networks. So what's your take on how to engage and work with communities? How do you find your tribe? If someone's getting into the business, they want support, they might want technology learnings, what's your approach? >> Yeah, so a few, a few different places. One, I'm part of the operator collective, which is a strong female investment group that's open and works a lot with operators and they're in on the newest technologies 'cause they're investing in it. Chief I think is a great organization as well. You've got a lot of, if you're in marketing, there's a ton of CMO networking events that you can go to. I would say any field, even for us at Lacework, we've got some strong CISO networks and we do dinners around you know, we have one coming up in the Bay area, in Boston, New York, and you can come and meet other CISOs and security leaders. So when I get an invite and you know we all do, I will go to it. I'll carve out the time and meet with others. So I think, you know, part of the community is get out there and, you know, join some of these different groups. >> Meagen, thank you so much for spending the time. Final question for you. How do you see the future of tech evolving and how do you see your role in it? >> Yeah, I mean, marketing's changing wildly. There's so many different channels. You think about all the social media channels that have changed over the last five years. So when I think about the future of tech, I'm looking at apps on my phone. I have three daughters, 13, 11, and 8. I'm telling you, they come to me with new apps and new technology all the time, and I'm paying attention what they're, you know, what they're participating in and what they want to be a part of. And certainly it's going to be a lot more around the data and AI. I think we're only at the beginning of that. So we will continue to, you know, learn from it and wield it and deal with the mass amount of data that's out there. >> Well, you saw TikTok just got banned by the European Commission today around their staff. Interesting times. >> It is. >> Meagen, thank you so much as always. You're a great tech athlete. Been following your career for a while, a long time. You're an amazing leader. Thank you for sharing your story here on theCUBE, celebration of International Women's Day. Every day is IWD and thanks for coming on. >> Thank you for having me. >> Okay. I'm John Furrier here in theCUBE Studios in Palo Alto. Thank you for watching, more to come stay with us. (bright music)

(light music) >> Hi everybody. Welcome to this Cube Conversation. I'm really pleased to announce a collaboration with Rob Strechay. He's a guest cube analyst, and we'll be working together to extract the signal from the noise. Rob is a long-time product pro, working at a number of firms including AWS, HP, HPE, NetApp, Snowplow. I did a stint as an analyst at Enterprise Strategy Group. Rob, good to see you. Thanks for coming into our Marlboro Studios. >> Well, thank you for having me. It's always great to be here. >> I'm really excited about working with you. We've known each other for a long time. You've been in the Cube a bunch. You know, you're in between gigs, and I think we can have a lot of fun together. Covering events, covering trends. So. let's get into it. What's happening out there? We're sort of exited the isolation economy. Things were booming. Now, everybody's tapping the brakes. From your standpoint, what are you seeing out there? >> Yeah. I'm seeing that people are really looking how to get more out of their data. How they're bringing things together, how they're looking at the costs of Cloud, and understanding how are they building out their SaaS applications. And understanding that when they go in and actually start to use Cloud, it's not only just using the base services anymore. They're looking at, how do I use these platforms as a service? Some are easier than others, and they're trying to understand, how do I get more value out of that relationship with the Cloud? They're also consolidating the number of Clouds that they have, I would say to try to better optimize their spend, and getting better pricing for that matter. >> Are you seeing people unhook Clouds, or just reduce maybe certain Cloud activities and going maybe instead of 60/40 going 90/10? >> Correct. It's more like the 90/10 type of rule where they're starting to say, Hey I'm not going to get rid of Azure or AWS or Google. I'm going to move a portion of this over that I was using on this one service. Maybe I got a great two-year contract to start with on this platform as a service or a database as a service. I'm going to unhook from that and maybe go with an independent. Maybe with something like a Snowflake or a Databricks on top of another Cloud, so that I can consolidate down. But it also gives them more flexibility as well. >> In our last breaking analysis, Rob, we identified six factors that were reducing Cloud consumption. There were factors and customer tactics. And I want to get your take on this. So, some of the factors really, you got fewer mortgage originations. FinTech, obviously big Cloud user. Crypto, not as much activity there. Lower ad spending means less Cloud. And then one of 'em, which you kind of disagreed with was less, less analytics, you know, fewer... Less frequency of calculations. I'll come back to that. But then optimizing compute using Graviton or AMD instances moving to cheaper storage tiers. That of course makes sense. And then optimize pricing plans. Maybe going from On Demand, you know, to, you know, instead of pay by the drink, buy in volume. Okay. So, first of all, do those make sense to you with the exception? We'll come back and talk about the analytics piece. Is that what you're seeing from customers? >> Yeah, I think so. I think that was pretty much dead on with what I'm seeing from customers and the ones that I go out and talk to. A lot of times they're trying to really monetize their, you know, understand how their business utilizes these Clouds. And, where their spend is going in those Clouds. Can they use, you know, lower tiers of storage? Do they really need the best processors? Do they need to be using Intel or can they get away with AMD or Graviton 2 or 3? Or do they need to move in? And, I think when you look at all of these Clouds, they always have pricing curves that are arcs from the newest to the oldest stuff. And you can play games with that. And understanding how you can actually lower your costs by looking at maybe some of the older generation. Maybe your application was written 10 years ago. You don't necessarily have to be on the best, newest processor for that application per se. >> So last, I want to come back to this whole analytics piece. Last June, I think it was June, Dev Ittycheria, who's the-- I call him Dev. Spelled Dev, pronounced Dave. (chuckles softly) Same pronunciation, different spelling. Dev Ittycheria, CEO of Mongo, on the earnings call. He was getting, you know, hit. Things were starting to get a little less visible in terms of, you know, the outlook. And people were pushing him like... Because you're in the Cloud, is it easier to dial down? And he said, because we're the document database, we support transaction applications. We're less discretionary than say, analytics. Well on the Snowflake earnings call, that same month or the month after, they were all over Slootman and Scarpelli. Oh, the Mongo CEO said that they're less discretionary than analytics. And Snowflake was an interesting comment. They basically said, look, we're the Cloud. You can dial it up, you can dial it down, but the area under the curve over a period of time is going to be the same, because they get their customers to commit. What do you say? You disagreed with the notion that people are running their calculations less frequently. Is that because they're trying to do a better job of targeting customers in near real time? What are you seeing out there? >> Yeah, I think they're moving away from using people and more expensive marketing. Or, they're trying to figure out what's my Google ad spend, what's my Meta ad spend? And what they're trying to do is optimize that spend. So, what is the return on advertising, or the ROAS as they would say. And what they're looking to do is understand, okay, I have to collect these analytics that better understand where are these people coming from? How do they get to my site, to my store, to my whatever? And when they're using it, how do they they better move through that? What you're also seeing is that analytics is not only just for kind of the retail or financial services or things like that, but then they're also, you know, using that to make offers in those categories. When you move back to more, you know, take other companies that are building products and SaaS delivered products. They may actually go and use this analytics for making the product better. And one of the big reasons for that is maybe they're dialing back how many product managers they have. And they're looking to be more data driven about how they actually go and build the product out or enhance the product. So maybe they're, you know, an online video service and they want to understand why people are either using or not using the whiteboard inside the product. And they're collecting a lot of that product analytics in a big way so that they can go through that. And they're doing it in a constant manner. This first party type tracking within applications is growing rapidly by customers. >> So, let's talk about who wins in that. So, obviously the Cloud guys, AWS, Google and Azure. I want to come back and unpack that a little bit. Databricks and Snowflake, we reported on our last breaking analysis, it kind of on a collision course. You know, a couple years ago we were thinking, okay, AWS, Snowflake and Databricks, like perfect sandwich. And then of course they started to become more competitive. My sense is they still, you know, compliment each other in the field, right? But, you know, publicly, they've got bigger aspirations, they get big TAMs that they're going after. But it's interesting, the data shows that-- So, Snowflake was off the charts in terms of spending momentum and our EPR surveys. Our partner down in New York, they kind of came into line. They're both growing in terms of market presence. Databricks couldn't get to IPO. So, we don't have as much, you know, visibility on their financials. You know, Snowflake obviously highly transparent cause they're a public company. And then you got AWS, Google and Azure. And it seems like AWS appears to be more partner friendly. Microsoft, you know, depends on what market you're in. And Google wants to sell BigQuery. >> Yeah. >> So, what are you seeing in the public Cloud from a data platform perspective? >> Yeah. I think that was pretty astute in what you were talking about there, because I think of the three, Google is definitely I think a little bit behind in how they go to market with their partners. Azure's done a fantastic job of partnering with these companies to understand and even though they may have Synapse as their go-to and where they want people to go to do AI and ML. What they're looking at is, Hey, we're going to also be friendly with Snowflake. We're also going to be friendly with a Databricks. And I think that, Amazon has always been there because that's where the market has been for these developers. So, many, like Databricks' and the Snowflake's have gone there first because, you know, Databricks' case, they built out on top of S3 first. And going and using somebody's object layer other than AWS, was not as simple as you would think it would be. Moving between those. >> So, one of the financial meetups I said meetup, but the... It was either the CEO or the CFO. It was either Slootman or Scarpelli talking at, I don't know, Merrill Lynch or one of the other financial conferences said, I think it was probably their Q3 call. Snowflake said 80% of our business goes through Amazon. And he said to this audience, the next day we got a call from Microsoft. Hey, we got to do more. And, we know just from reading the financial statements that Snowflake is getting concessions from Amazon, they're buying in volume, they're renegotiating their contracts. Amazon gets it. You know, lower the price, people buy more. Long term, we're all going to make more money. Microsoft obviously wants to get into that game with Snowflake. They understand the momentum. They said Google, not so much. And I've had customers tell me that they wanted to use Google's AI with Snowflake, but they can't, they got to go to to BigQuery. So, honestly, I haven't like vetted that so. But, I think it's true. But nonetheless, it seems like Google's a little less friendly with the data platform providers. What do you think? >> Yeah, I would say so. I think this is a place that Google looks and wants to own. Is that now, are they doing the right things long term? I mean again, you know, you look at Google Analytics being you know, basically outlawed in five countries in the EU because of GDPR concerns, and compliance and governance of data. And I think people are looking at Google and BigQuery in general and saying, is it the best place for me to go? Is it going to be in the right places where I need it? Still, it's still one of the largest used databases out there just because it underpins a number of the Google services. So you almost get, like you were saying, forced into BigQuery sometimes, if you want to use the tech on top. >> You do strategy. >> Yeah. >> Right? You do strategy, you do messaging. Is it the right call by Google? I mean, it's not a-- I criticize Google sometimes. But, I'm not sure it's the wrong call to say, Hey, this is our ace in the hole. >> Yeah. >> We got to get people into BigQuery. Cause, first of all, BigQuery is a solid product. I mean it's Cloud native and it's, you know, by all, it gets high marks. So, why give the competition an advantage? Let's try to force people essentially into what is we think a great product and it is a great product. The flip side of that is, they're giving up some potential partner TAM and not treating the ecosystem as well as one of their major competitors. What do you do if you're in that position? >> Yeah, I think that that's a fantastic question. And the question I pose back to the companies I've worked with and worked for is, are you really looking to have vendor lock-in as your key differentiator to your service? And I think when you start to look at these companies that are moving away from BigQuery, moving to even, Databricks on top of GCS in Google, they're looking to say, okay, I can go there if I have to evacuate from GCP and go to another Cloud, I can stay on Databricks as a platform, for instance. So I think it's, people are looking at what platform as a service, database as a service they go and use. Because from a strategic perspective, they don't want that vendor locking. >> That's where Supercloud becomes interesting, right? Because, if I can run on Snowflake or Databricks, you know, across Clouds. Even Oracle, you know, they're getting into business with Microsoft. Let's talk about some of the Cloud players. So, the big three have reported. >> Right. >> We saw AWSs Cloud growth decelerated down to 20%, which is I think the lowest growth rate since they started to disclose public numbers. And they said they exited, sorry, they said January they grew at 15%. >> Yeah. >> Year on year. Now, they had some pretty tough compares. But nonetheless, 15%, wow. Azure, kind of mid thirties, and then Google, we had kind of low thirties. But, well behind in terms of size. And Google's losing probably almost $3 billion annually. But, that's not necessarily a bad thing by advocating and investing. What's happening with the Cloud? Is AWS just running into the law, large numbers? Do you think we can actually see a re-acceleration like we have in the past with AWS Cloud? Azure, we predicted is going to be 75% of AWS IAS revenues. You know, we try to estimate IAS. >> Yeah. >> Even though they don't share that with us. That's a huge milestone. You'd think-- There's some people who have, I think, Bob Evans predicted a while ago that Microsoft would surpass AWS in terms of size. You know, what do you think? >> Yeah, I think that Azure's going to keep to-- Keep growing at a pretty good clip. I think that for Azure, they still have really great account control, even though people like to hate Microsoft. The Microsoft sellers that are out there making those companies successful day after day have really done a good job of being in those accounts and helping people. I was recently over in the UK. And the UK market between AWS and Azure is pretty amazing, how much Azure there is. And it's growing within Europe in general. In the states, it's, you know, I think it's growing well. I think it's still growing, probably not as fast as it is outside the U.S. But, you go down to someplace like Australia, it's also Azure. You hear about Azure all the time. >> Why? Is that just because of the Microsoft's software state? It's just so convenient. >> I think it has to do with, you know, and you can go with the reasoning they don't break out, you know, Office 365 and all of that out of their numbers is because they have-- They're in all of these accounts because the office suite is so pervasive in there. So, they always have reasons to go back in and, oh by the way, you're on these old SQL licenses. Let us move you up here and we'll be able to-- We'll support you on the old version, you know, with security and all of these things. And be able to move you forward. So, they have a lot of, I guess you could say, levers to stay in those accounts and be interesting. At least as part of the Cloud estate. I think Amazon, you know, is hitting, you know, the large number. Laws of large numbers. But I think that they're also going through, and I think this was seen in the layoffs that they were making, that they're looking to understand and have profitability in more of those services that they have. You know, over 350 odd services that they have. And you know, as somebody who went there and helped to start yet a new one, while I was there. And finally, it went to beta back in September, you start to look at the fact that, that number of services, people, their own sellers don't even know all of their services. It's impossible to comprehend and sell that many things. So, I think what they're going through is really looking to rationalize a lot of what they're doing from a services perspective going forward. They're looking to focus on more profitable services and bringing those in. Because right now it's built like a layer cake where you have, you know, S3 EBS and EC2 on the bottom of the layer cake. And then maybe you have, you're using IAM, the authorization and authentication in there and you have all these different services. And then they call it EMR on top. And so, EMR has to pay for that entire layer cake just to go and compete against somebody like Mongo or something like that. So, you start to unwind the costs of that. Whereas Azure, went and they build basically ground up services for the most part. And Google kind of falls somewhere in between in how they build their-- They're a sort of layer cake type effect, but not as many layers I guess you could say. >> I feel like, you know, Amazon's trying to be a platform for the ecosystem. Yes, they have their own products and they're going to sell. And that's going to drive their profitability cause they don't have to split the pie. But, they're taking a piece of-- They're spinning the meter, as Ziyas Caravalo likes to say on every time Snowflake or Databricks or Mongo or Atlas is, you know, running on their system. They take a piece of the action. Now, Microsoft does that as well. But, you look at Microsoft and security, head-to-head competitors, for example, with a CrowdStrike or an Okta in identity. Whereas, it seems like at least for now, AWS is a more friendly place for the ecosystem. At the same time, you do a lot of business in Microsoft. >> Yeah. And I think that a lot of companies have always feared that Amazon would just throw, you know, bodies at it. And I think that people have come to the realization that a two pizza team, as Amazon would call it, is eight people. I think that's, you know, two slices per person. I'm a little bit fat, so I don't know if that's enough. But, you start to look at it and go, okay, if they're going to start out with eight engineers, if I'm a startup and they're part of my ecosystem, do I really fear them or should I really embrace them and try to partner closer with them? And I think the smart people and the smart companies are partnering with them because they're realizing, Amazon, unless they can see it to, you know, a hundred million, $500 million market, they're not going to throw eight to 16 people at a problem. I think when, you know, you could say, you could look at the elastic with OpenSearch and what they did there. And the licensing terms and the battle they went through. But they knew that Elastic had a huge market. Also, you had a number of ecosystem companies building on top of now OpenSearch, that are now domain on top of Amazon as well. So, I think Amazon's being pretty strategic in how they're doing it. I think some of the-- It'll be interesting. I think this year is a payout year for the cuts that they're making to some of the services internally to kind of, you know, how do we take the fat off some of those services that-- You know, you look at Alexa. I don't know how much revenue Alexa really generates for them. But it's a means to an end for a number of different other services and partners. >> What do you make of this ChatGPT? I mean, Microsoft obviously is playing that card. You want to, you want ChatGPT in the Cloud, come to Azure. Seems like AWS has to respond. And we know Google is, you know, sharpening its knives to come up with its response. >> Yeah, I mean Google just went and talked about Bard for the first time this week and they're in private preview or I guess they call it beta, but. Right at the moment to select, select AI users, which I have no idea what that means. But that's a very interesting way that they're marketing it out there. But, I think that Amazon will have to respond. I think they'll be more measured than say, what Google's doing with Bard and just throwing it out there to, hey, we're going into beta now. I think they'll look at it and see where do we go and how do we actually integrate this in? Because they do have a lot of components of AI and ML underneath the hood that other services use. And I think that, you know, they've learned from that. And I think that they've already done a good job. Especially for media and entertainment when you start to look at some of the ways that they use it for helping do graphics and helping to do drones. I think part of their buy of iRobot was the fact that iRobot was a big user of RoboMaker, which is using different models to train those robots to go around objects and things like that, so. >> Quick touch on Kubernetes, the whole DevOps World we just covered. The Cloud Native Foundation Security, CNCF. The security conference up in Seattle last week. First time they spun that out kind of like reinforced, you know, AWS spins out, reinforced from reinvent. Amsterdam's coming up soon, the CubeCon. What should we expect? What's hot in Cubeland? >> Yeah, I think, you know, Kubes, you're going to be looking at how OpenShift keeps growing and I think to that respect you get to see the momentum with people like Red Hat. You see others coming up and realizing how OpenShift has gone to market as being, like you were saying, partnering with those Clouds and really making it simple. I think the simplicity and the manageability of Kubernetes is going to be at the forefront. I think a lot of the investment is still going into, how do I bring observability and DevOps and AIOps and MLOps all together. And I think that's going to be a big place where people are going to be looking to see what comes out of CubeCon in Amsterdam. I think it's that manageability ease of use. >> Well Rob, I look forward to working with you on behalf of the whole Cube team. We're going to do more of these and go out to some shows extract the signal from the noise. Really appreciate you coming into our studio. >> Well, thank you for having me on. Really appreciate it. >> You're really welcome. All right, keep it right there, or thanks for watching. This is Dave Vellante for the Cube. And we'll see you next time. (light 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 unraveling of market enthusiasm continued in Q4 of 2022 with the earnings reports from the US hyperscalers, the big three now all in. As we said earlier this year, even the cloud is an immune from the macro headwinds and the cracks in the armor that we saw from the data that we shared last summer, they're playing out into 2023. For the most part actuals are disappointing beyond expectations including our own. It turns out that our estimates for the big three hyperscaler's revenue missed by 1.2 billion or 2.7% lower than we had forecast from even our most recent November estimates. And we expect continued decelerating growth rates for the hyperscalers through the summer of 2023 and we don't think that's going to abate until comparisons get easier. Hello and welcome to this week's Wikibon Cube Insights powered by ETR. In this Breaking Analysis, we share our view of what's happening in cloud markets not just for the hyperscalers but other firms that have hitched a ride on the cloud. And we'll share new ETR data that shows why these trends are playing out tactics that customers are employing to deal with their cost challenges and how long the pain is likely to last. You know, riding the cloud wave, it's a two-edged sword. Let's look at the players that have gone all in on or are exposed to both the positive and negative trends of cloud. Look the cloud has been a huge tailwind for so many companies like Snowflake and Databricks, Workday, Salesforce, Mongo's move with Atlas, Red Hats Cloud strategy with OpenShift and so forth. And you know, the flip side is because cloud is elastic what comes up can also go down very easily. Here's an XY graphic from ETR that shows spending momentum or net score on the vertical axis and market presence in the dataset on the horizontal axis provision or called overlap. This is data from the January 2023 survey and that the red dotted lines show the positions of several companies that we've highlighted going back to January 2021. So let's unpack this for a bit starting with the big three hyperscalers. The first point is AWS and Azure continue to solidify their moat relative to Google Cloud platform. And we're going to get into this in a moment, but Azure and AWS revenues are five to six times that of GCP for IaaS. And at those deltas, Google should be gaining ground much faster than the big two. The second point on Google is notice the red line on GCP relative to its starting point. While it appears to be gaining ground on the horizontal axis, its net score is now below that of AWS and Azure in the survey. So despite its significantly smaller size it's just not keeping pace with the leaders in terms of market momentum. Now looking at AWS and Microsoft, what we see is basically AWS is holding serve. As we know both Google and Microsoft benefit from including SaaS in their cloud numbers. So the fact that AWS hasn't seen a huge downward momentum relative to a January 2021 position is one positive in the data. And both companies are well above that magic 40% line on the Y-axis, anything above 40% we consider to be highly elevated. But the fact remains that they're down as are most of the names on this chart. So let's take a closer look. I want to start with Snowflake and Databricks. Snowflake, as we reported from several quarters back came down to Earth, it was up in the 80% range in the Y-axis here. And it's still highly elevated in the 60% range and it continues to move to the right, which is positive but as we'll address in a moment it's customers can dial down consumption just as in any cloud. Now, Databricks is really interesting. It's not a public company, it never made it to IPO during the sort of tech bubble. So we don't have the same level of transparency that we do with other companies that did make it through. But look at how much more prominent it is on the X-axis relative to January 2021. And it's net score is basically held up over that period of time. So that's a real positive for Databricks. Next, look at Workday and Salesforce. They've held up relatively well, both inching to the right and generally holding their net scores. Same from Mongo, which is the brown dot above its name that says Elastic, it says a little gets a little crowded which Elastic's actually the blue dot above it. But generally, SaaS is harder to dial down, Workday, Salesforce, Oracles, SaaS and others. So it's harder to dial down because commitments have been made in advance, they're kind of locked in. Now, one of the discussions from last summer was as Mongo, less discretionary than analytics i.e. Snowflake. And it's an interesting debate but maybe Snowflake customers, you know, they're also generally committed to a dollar amount. So over time the spending is going to be there. But in the short term, yeah maybe Snowflake customers can dial down. Now that highlighted dotted red line, that bolded one is Datadog and you can see it's made major strides on the X-axis but its net score has decelerated quite dramatically. Openshift's momentum in the survey has dropped although IBM just announced that OpenShift has a a billion dollar ARR and I suspect what's happening there is IBM consulting is bundling OpenShift into its modernization projects. It's got a, that sort of captive base if you will. And as such it's probably not as top of mind to the respondents but I'll bet you the developers are certainly aware of it. Now the other really notable call out here is CloudFlare, We've reported on them earlier. Cloudflare's net score has held up really well since January of 2021. It really hasn't seen the downdraft of some of these others, but it's making major major moves to the right gaining market presence. We really like how CloudFlare is performing. And the last comment is on Oracle which as you can see, despite its much, much lower net score continues to gain ground in the market and thrive from a profitability standpoint. But the data pretty clearly shows that there's a downdraft in the market. Okay, so what's happening here? Let's dig deeper into this data. Here's a graphic from the most recent ETR drill down asking customers that said they were going to cut spending what technique they're using to do so. Now, as we've previously reported, consolidating redundant vendors is by far the most cited approach but there's two key points we want to make here. One is reducing excess cloud resources. As you can see in the bars is the second most cited technique and it's up from the previous polling period. The second we're not showing, you know directly but we've got some red call outs there. Reducing cloud costs jumps to 29% and 28% respectively in financial services and tech telco. And it's much closer to second. It's basically neck and neck with consolidating redundant vendors in those two industries. So they're being really aggressive about optimizing cloud cost. Okay, so as we said, cloud is great 'cause you can dial it up but it's just as easy to dial down. We've identified six factors that customers tell us are affecting their cloud consumption and there are probably more, if you got more we'd love to hear them but these are the ones that are fairly prominent that have hit our radar. First, rising mortgage rates mean banks are processing fewer loans means less cloud. The crypto crash means less trading activity and that means less cloud resources. Third lower ad spend has led companies to reduce not only you know, their ad buying but also their frequency of running their analytics and their calculations. And they're also often using less data, maybe compressing the timeframe of the corpus down to a shorter time period. Also very prominent is down to the bottom left, using lower cost compute instances. For example, Graviton from AWS or AMD chips and tiering storage to cheaper S3 or deep archived tiers. And finally, optimizing based on better pricing plans. So customers are moving from, you know, smaller companies in particular moving maybe from on demand or other larger companies that are experimenting using on demand or they're moving to spot pricing or reserved instances or optimized savings plans. That all lowers cost and that means less cloud resource consumption and less cloud revenue. Now in the days when everything was on prem CFOs, what would they do? They would freeze CapEx and IT Pros would have to try to do more with less and often that meant a lot of manual tasks. With the cloud it's much easier to move things around. It still takes some thinking and some effort but it's dramatically simpler to do so. So you can get those savings a lot faster. Now of course the other huge factor is you can cut or you can freeze. And this graphic shows data from a recent ETR survey with 159 respondents and you can see the meaningful uptick in hiring freezes, freezing new IT deployments and layoffs. And as we've been reporting, this has been trending up since earlier last year. And note the call out, this is especially prominent in retail sectors, all three of these techniques jump up in retail and that's a bit of a concern because oftentimes consumer spending helps the economy make a softer landing out of a pullback. But this is a potential canary in the coal mine. If retail firms are pulling back it's because consumers aren't spending as much. And so we're keeping a close eye on that. So let's boil this down to the market data and what this all means. So in this graphic we show our estimates for Q4 IaaS revenues compared to the "actual" IaaS revenues. And we say quote because AWS is the only one that reports, you know clean revenue and IaaS, Azure and GCP don't report actuals. Why would they? Because it would make them look even, you know smaller relative to AWS. Rather, they bury the figures in overall cloud which includes their, you know G-Suite for Google and all the Microsoft SaaS. And then they give us little tidbits about in Microsoft's case, Azure, they give growth rates. Google gives kind of relative growth of GCP. So, and we use survey data and you know, other data to try to really pinpoint and we've been covering this for, I don't know, five or six years ever since the cloud really became a thing. But looking at the data, we had AWS growing at 25% this quarter and it came in at 20%. So a significant decline relative to our expectations. AWS announced that it exited December, actually, sorry it's January data showed about a 15% mid-teens growth rate. So that's, you know, something we're watching. Azure was two points off our forecast coming in at 38% growth. It said it exited December in the 35% growth range and it said that it's expecting five points of deceleration off of that. So think 30% for Azure. GCP came in three points off our expectation coming in 35% and Alibaba has yet to report but we've shaved a bid off that forecast based on some survey data and you know what maybe 9% is even still not enough. Now for the year, the big four hyperscalers generated almost 160 billion of revenue, but that was 7 billion lower than what what we expected coming into 2022. For 2023, we're expecting 21% growth for a total of 193.3 billion. And while it's, you know, lower, you know, significantly lower than historical expectations it's still four to five times the overall spending forecast that we just shared with you in our predictions post of between 4 and 5% for the overall market. We think AWS is going to come in in around 93 billion this year with Azure closing in at over 71 billion. This is, again, we're talking IaaS here. Now, despite Amazon focusing investors on the fact that AWS's absolute dollar growth is still larger than its competitors. By our estimates Azure will come in at more than 75% of AWS's forecasted revenue. That's a significant milestone. AWS is operating margins by the way declined significantly this past quarter, dropping from 30% of revenue to 24%, 30% the year earlier to 24%. Now that's still extremely healthy and we've seen wild fluctuations like this before so I don't get too freaked out about that. But I'll say this, Microsoft has a marginal cost advantage relative to AWS because one, it has a captive cloud on which to run its massive software estate. So it can just throw software at its own cloud and two software marginal costs. Marginal economics despite AWS's awesomeness in high degrees of automation, software is just a better business. Now the upshot for AWS is the ecosystem. AWS is essentially in our view positioning very smartly as a platform for data partners like Snowflake and Databricks, security partners like CrowdStrike and Okta and Palo Alto and many others and SaaS companies. You know, Microsoft is more competitive even though AWS does have competitive products. Now of course Amazon's competitive to retail companies so that's another factor but generally speaking for tech players, Amazon is a really thriving ecosystem that is a secret weapon in our view. AWS happy to spin the meter with its partners even though it sells competitive products, you know, more so in our view than other cloud players. Microsoft, of course is, don't forget is hyping now, we're hearing a lot OpenAI and ChatGPT we reported last week in our predictions post. How OpenAI is shot up in terms of market sentiment in ETR's emerging technology company surveys and people are moving to Azure to get OpenAI and get ChatGPT that is a an interesting lever. Amazon in our view has to have a response. They have lots of AI and they're going to have to make some moves there. Meanwhile, Google is emphasizing itself as an AI first company. In fact, Google spent at least five minutes of continuous dialogue, nonstop on its AI chops during its latest earnings call. So that's an area that we're watching very closely as the buzz around large language models continues. All right, let's wrap up with some assumptions for 2023. We think SaaS players are going to continue to be sticky. They're going to be somewhat insulated from all these downdrafts because they're so tied in and customers, you know they make the commitment up front, you've got the lock in. Now having said that, we do expect some backlash over time on the onerous and generally customer unfriendly pricing models of most large SaaS companies. But that's going to play out over a longer period of time. Now for cloud generally and the hyperscalers specifically we do expect accelerating growth rates into Q3 but the amplitude of the demand swings from this rubber band economy, we expect to continue to compress and become more predictable throughout the year. Estimates are coming down, CEOs we think are going to be more cautious when the market snaps back more cautious about hiring and spending and as such a perhaps we expect a more orderly return to growth which we think will slightly accelerate in Q4 as comps get easier. Now of course the big risk to these scenarios is of course the economy, the FED, consumer spending, inflation, supply chain, energy prices, wars, geopolitics, China relations, you know, all the usual stuff. But as always with our partners at ETR and the Cube community, we're here for you. We have the data and we'll be the first to report when we see a change at the margin. Okay, that's a wrap for today. I want to thank Alex Morrison who's on production and manages the podcast, Ken Schiffman as well out of our Boston studio getting this up on LinkedIn Live. Thank you for that. Kristen Martin also 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 siliconangle.com. He does some great editing for us. Thank you all. Remember all these episodes are available as podcast. Wherever you listen, just search Breaking Analysis podcast. I publish each week on wikibon.com, at siliconangle.com where you can see all the data and you want to get in touch. Just all you can do is email me david.vellante@siliconangle.com or DM me @dvellante if you if you got something interesting, I'll respond. If you don't, it's either 'cause I'm swamped or it's just not tickling me. You can comment on our LinkedIn post as well. And please 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 next time on Breaking Analysis. (gentle upbeat music)

(upbeat music) >> Welcome back to Supercloud 2 this is Dave Vellante. We're here exploring the intersection of data and analytics and the future of cloud. And in this segment, we're going to look at the evolution of cloud, and try to test some of the Supercloud concepts and assumptions with Brian Gracely, is the founder and co-host along with Aaron Delp of the popular Cloudcast program. Amazing series, if you're not already familiar with it. The Cloudcast is one of the best ways to keep up with so many things going on in our industry. Enterprise tech, platform engineering, business models, obviously, cloud developer trends, crypto, Web 3.0. Sorry Brian, I know that's a sore spot, but Brian, thanks for coming >> That's okay. >> on the program, really appreciate it. >> Yeah, great to be with you, Dave. Happy New Year, and great to be back with everybody with SiliconANGLE again this year. >> Yeah, we love having you on. We miss working with you day-to-day, but I want to start with Gracely's theorem, which basically says, I'm going to paraphrase. For the most part, nothing new gets introduced in the enterprise tech business, patterns repeat themselves, maybe get applied in new ways. And you know this industry well, when something comes out that's new, if you take virtualization, for example, been around forever with mainframes, but then VMware applied it, solve a real problem in the client service system. And then it's like, "Okay, this is awesome." We get really excited and then after a while we pushed the architecture, we break things, introduce new things to fix the things that are broken and start adding new features. And oftentimes you do that through acquisitions. So, you know, has the cloud become that sort of thing? And is Supercloud sort of same wine, new bottle, following Gracely's theorem? >> Yeah, I think there's some of both of it. I hate to be the sort of, it depends sort of answer but, I think to a certain extent, you know, obviously Cloud in and of itself was, kind of revolutionary in that, you know, it wasn't that you couldn't rent things in the past, it was just being able to do it at scale, being able to do it with such amazing self-service. And then, you know, kind of proliferation of like, look at how many services I can get from, from one cloud, whether it was Amazon or Azure or Google. And then, you know, we, we slip back into the things that we know, we go, "Oh, well, okay, now I can get computing on demand, but, now it's just computing." Or I can get database on demand and it's, you know, it's got some of the same limitations of, of say, of database, right? It's still, you know, I have to think about IOPS and I have to think about caching, and other stuff. So, I think we do go through that and then we, you know, we have these sort of next paradigms that come along. So, you know, serverless was another one of those where it was like, okay, it seems sort of new. I don't have to, again, it was another level of like, I don't have to think about anything. And I was able to do that because, you know, there was either greater bandwidth available to me, or compute got cheaper. And what's been interesting is not the sort of, that specific thing, serverless in and of itself is just another way of doing compute, but the fact that it now gets applied as, sort of a no-ops model to, you know, again, like how do I provision a database? How do I think about, you know, do I have to think about the location of a service? Does that just get taken care of for me? So I think the Supercloud concept, and I did a thing and, and you and I have talked about it, you know, behind the scenes that maybe the, maybe a better name is Super app for something like Snowflake or other, but I think we're, seeing these these sort of evolutions over and over again of what were the big bottlenecks? How do we, how do we solve those bottlenecks? And I think the big thing here is, it's never, it's very rarely that you can take the old paradigm of what the thing was, the concept was, and apply it to the new model. So, I'll just give you an example. So, you know, something like VMware, which we all know, wildly popular, wildly used, but when we apply like a Supercloud concept of VMware, the concept of VMware has always been around a cluster, right? It's some finite number of servers, you sort of manage it as a cluster. And when you apply that to the cloud and you say, okay, there's, you know, for example, VMware in the cloud, it's still the same concept of a cluster of VMware. But yet when you look at some of these other services that would fit more into the, you know, Supercloud kind of paradigm, whether it's a Snowflake or a MongoDB Atlas or maybe what CloudFlare is doing at the edge, those things get rid of some of those old paradigms. And I think that's where stuff, you start to go, "Oh, okay, this is very different than before." Yes, it's still computing or storage, or data access, but there's a whole nother level of something that we didn't carry forward from the previous days. And that really kind of breaks the paradigm. And so that's the way I think I've started to think about, are these things really brand new? Yes and no, but I think it's when you can see that big, that thing that you didn't leave behind isn't there anymore, you start to get some really interesting new innovation come out of it. >> Yeah. And that's why, you know, lift and shift is okay, when you talk to practitioners, they'll say, "You know, I really didn't change my operating model. And so I just kind of moved it into the cloud. there were some benefits, but it was maybe one zero not three zeros that I was looking for." >> Right. >> You know, we always talk about what's great about cloud, the agility, and all the other wonderful stuff that we know, what's not working in cloud, you know, tie it into multi-cloud, you know, in terms of, you hear people talk about multi-cloud by accident, okay, that's true. >> Yep. >> What's not great about cloud. And then I want to get into, you know, is multi-cloud really a problem or is it just sort of vendor hype? But, but what's not working in cloud? I mean, you mentioned serverless and serverless is kind of narrow, right, for a lot of stateless apps, right? But, what's not great about cloud? >> Well, I think there's a few things that if you ask most people they don't love about cloud. I think, we can argue whether or not sort of this consolidation around a few cloud providers has been a good thing or a bad thing. I think, regardless of that, you know, we are seeing, we are hearing more and more people that say, look, you know, the experience I used to have with cloud when I went to, for example, an Amazon and there was, you know, a dozen services, it was easy to figure out what was going on. It was easy to figure out what my billing looked like. You know, now they've become so widespread, the number of services they have, you know, the number of stories you just hear of people who went, "Oh, I started a service over in US West and I can't find it anymore 'cause it's on a different screen. And I, you know, I just got billed for it." Like, so I think the sprawl of some of the clouds has gotten, has created a user experience that a lot of people are frustrated with. I think that's one thing. And we, you know, we see people like Digital Ocean and we see others who are saying, "Hey, we're going to be that simplified version." So, there's always that yin and yang. I think people are super frustrated at network costs, right? So, you know, and that's kind of at a lot of, at the center of maybe why we do or don't see more of these Supercloud services is just, you know, in the data center as an application owner, I didn't have to think about, well where, where does this go to? Where are my users? Yes, somebody took care of it, but when those things become front and center, that's super frustrating. That's the one area that we've seen absolutely no cost savings, cost reduction. So I think that frustrates people a lot. And then I think the third piece is just, you know, we're, we went from super centralized IT organizations, which, you know, for decades was how it worked. It was part of the reason why the cloud expanded and became a thing, right? Sort of shadow IT and I can't get things done. And then, now what we've seen is sort of this proliferation of little pockets of groups that are your IT, for lack of a better thing, whether they're called platform engineering or SRE or DevOps. But we have this, expansion, explosion if you will, of groups that, if I'm an app dev team, I go, "Hey, you helped me make this stuff run, but then the team next to you has another group and they have another group." And so you see this explosion of, you know, we don't have any standards in the company anymore. And, so sort of self-service has created its own nightmare to a certain extent for a lot of larger companies. >> Yeah. Thank you for that. So, you know, I want, I want to explore this multi-cloud, you know, by accident thing and is a real problem. You hear that a lot from vendors and we've been talking about Supercloud as this unifying layer across cloud. You know, but when you talk to customers, a lot of them are saying, "Yes, we have multiple clouds in our organization, but my group, we have mono cloud, we know the security, edicts, we know how to, you know, deal with the primitives, whether it's, you know, S3 or Azure Blob or whatever it is. And we're very comfortable with this." It's, that's how we're simplifying. So, do you think this is really a problem? Does it have merit that we need that unifying layer across clouds, or is it just too early for that? >> I think, yeah, I think what you, what you've laid out is basically how the world has played out. People have picked a cloud for a specific application or a series of applications. Yeah, and I think if you talk to most companies, they would tell you, you know, holistically, yes, we're multi-cloud, not, maybe not necessarily on, I don't necessarily love the phrase where people say like, well it happened by accident. I think it happened on purpose, but we got to multi-cloud, not in the way that maybe that vendors, you know, perceived, you know, kind of laid out a map for. So it was, it was, well you will lay out this sort of Supercloud framework. We didn't call it that back then, we just called it sort of multi-cloud. Maybe it was Kubernetes or maybe it was whatever. And different groups, because central IT kind of got disbanded or got fragmented. It turned into, go pick the best cloud for your application, for what you need to do for the business. And then, you know, multiple years later it was like, "Oh, hold on, I've got 20% in Google and 50% in AWS and I've got 30% in Azure. And, you know, it's, yeah, it's been evolution. I don't know that it's, I don't know if it's a mistake. I think it's now groups trying to figure out like, should I make sense of it? You know, should I try and standardize and I backwards standardize some stuff? I think that's going to be a hard thing for, for companies to do. 'cause I think they feel okay with where the applications are. They just happen to be in multiple clouds. >> I want to run something by you, and you guys, you and Aaron have talked about this. You know, still depending on who, which keynote you listen to, small percentage of the workloads are actually in cloud. And when you were with us at Wikibon, I think we called it true private cloud, and we looked at things like Nutanix and there were a lot of other examples of companies that were trying to replicate the hyperscale experience on Prem. >> Yeah. >> And, we would evaluate that, you know, beyond virtualization, and so we sort of defined that and, but I think what's, maybe what's more interesting than Supercloud across clouds is if you include that, that on Prem estate, because that's where most of the work is being done, that's where a lot of the proprietary tools have been built, a lot of data, a lot of software. So maybe there's this concept of sending that true private cloud to true hybrid cloud. So I actually think hybrid cloud in some cases is the more interesting use case for so-called Supercloud. What are your thoughts on that? >> Yeah, I think there's a couple aspects too. I think, you know, if we were to go back five or six years even, maybe even a little further and look at like what a data center looked like, even if it was just, "Hey we're a data center that runs primarily on VMware. We use some of their automation". Versus what you can, even what you can do in your data center today. The, you know, the games that people have seen through new types of automation through Kubernetes, through get ops, and a number of these things, like they've gotten significantly further along in terms of I can provision stuff really well, I can do multi-tenancy, I can do self-service. Is it, you know, is it still hard? Yeah. Because those things are hard to do, but there's been significant progress there. I don't, you know, I still look for kind of that, that killer application, that sort of, you know, lighthouse use case of, hybrid applications, you know, between data center and between cloud. I think, you know, we see some stuff where, you know, backup is a part of it. So you use the cloud for storage, maybe you use the cloud for certain kinds of resiliency, especially on maybe front end load balancing and stuff. But I think, you know, I think what we get into is, this being hung up on hybrid cloud or multi-cloud as a term and go like, "Look, what are you trying to measure? Are you trying to measure, you know, efficiency of of of IT usage? Are you trying to measure how quickly can I give these business, you know, these application teams that are part of a line of business resources that they need?" I think if we start measuring that way, we would look at, you know, you'd go, "Wow, it used to be weeks and months. Now we got rid of these boards that have to review everything every time I want to do a change management type of thing." We've seen a lot more self-service. I think those are the things we want to measure on. And then to your point of, you know, where does, where do these Supercloud applications fit in? I think there are a bunch of instances where you go, "Look, I have a, you know, global application, I have a thing that has to span multiple regions." That's where the Supercloud concept really comes into play. We used to do it in the data center, right? We'd had all sorts of technologies to help with that, I think you can now start to do it in the cloud. >> You know, one of the other things, trying to understand, your thoughts on this, do you think that you, you again have talked about this, like I'm with you. It's like, how is it that Google's losing, you know, 3 billion dollars a year, whatever. I mean, because when you go back and look at Amazon, when they were at that level of revenue where Google is today, they were making money, you know, and they were actually growing faster, by the way. So it's kind of interesting what's happened with Google. But, the reason I bring that up is, trying to understand if you think the hyperscalers will ever be motivated to create standards across clouds, and that may be a play for Google. I mean, obviously with Kubernetes it was like a Hail Mary and kind of made them relevant. Where would Google be without Kubernetes? But then did it achieve the objectives? We could have that conversation some other time, but do you think the hyperscalers will actually say, "Okay, we're going to lean in and create these standards across clouds." Because customers would love that, I would think, but it would sub-optimize their competitive advantage. What are your thoughts? >> I think, you know, on the surface, I would say they, they probably aren't. I think if you asked 'em the question, they would say, "Well, you know, first and foremost, you know, we do deliver standards, so we deliver a, you know, standard SQL interface or a SQL you know, or a standard Kubernetes API or whatever. So, in that, from that perspective, you know, we're not locking you into, you know, an Amazon specific database, or a Google specific database." You, you can argue about that, but I think to a certain extent, like they've been very good about, "Hey, we're going to adopt the standards that people want." A lot of times the open source standards. I think the problem is, let's say they did come up with a standard for it. I think you still have the problem of the costs of migration and you know, the longer you've, I think their bet is basically the longer you've been in some cloud. And again, the more data you sort of compile there, the data gravity concept, there's just going to be a natural thing that says, okay, the hurdle to get over to say, "Look, we want to move this to another cloud", becomes so cost prohibitive that they don't really have to worry about, you know, oh, I'm going to get into a war of standards. And so far I think they sort of realize like that's the flywheel that the cloud creates. And you know, unless they want to get into a world where they just cut bandwidth costs, like it just kind of won't happen. You know, I think we've even seen, and you know, the one example I'll use, and I forget the name of it off the top of my head, but there's a, there's a Google service. I think it's like BigQuery external or something along those lines, that allows you to say, "Look, you can use BigQuery against like S3 buckets and against other stuff." And so I think the cloud providers have kind of figured out, I'm never going to get the application out of that other guy's cloud or you know, the other cloud. But maybe I'm going to have to figure out some interesting ways to sort of work with it. And, you know, it's a little bit, it's a little janky, but that might be, you know, a moderate step that sort of gets customers where they want to be. >> Yeah. Or you know, it'd be interesting if you ever see AWS for example, running its database in other clouds, you started, even Oracle is doing that with, with with Azure, which is a form of Supercloud. My last question for you is, I want to get you thinking about sort of how the future plays out. You know, think about some of the companies that we've put forth this Supercloud, and by the way, this has been a criticism of the concept. Charles Fitzer, "Everything is Supercloud!" Which if true would defeat the purpose of course. >> Right. >> And so right with the community effort, we really tried to put some guardrails down on the essential characteristics, the deployment models, you know, so for example, running across multiple clouds with a purpose build pass, creating a common experience, metadata intelligence that solves a specific problem. I mean, the example I often use is Snowflake's governed data sharing. But yeah, Snowflake, Databricks, CloudFlare, Cohesity, you know, I just mentioned Oracle and Azure, these and others, they certainly claim to have that common experience across clouds. But my question is, again, I come back to, do customers need this capability? You know, is Mono Cloud the way to solve that problem? What's your, what are your thoughts on how this plays out in the future of, I guess, PAs, apps and cloud? >> Yeah, I think a couple of things. So, from a technology perspective, I think, you know, the companies you name, the services you've named, have sort of proven that the concept is viable and it's viable at a reasonable size, right? These aren't completely niche businesses, right? They're multi-billion dollar businesses. So, I think there's a subset of applications that, you know, maybe a a bigger than a niche set of applications that are going to use these types of things. A lot of what you talked about is very data centric, and that's, that's fine. That's that layer is, figuring that out. I think we'll see messaging types of services, so like Derek Hallison's, Caya Company runs a, sort of a Supercloud for messaging applications. So I think there'll be places where it makes a ton of sense. I think, the thing that I'm not sure about, and because again, we've been now 10 plus years of sort of super low, you know, interest rates in terms of being able to do things, is a lot of these things come out of research that have been done previously. Then they get turned into maybe somewhat of an open source project, and then they can become something. You know, will we see as much investment into the next Snowflake if, you know, the interest rates are three or four times that they used to be, do we, do we see VCs doing it? So that's the part that worries me a little bit, is I think we've seen what's possible. I think, you know, we've seen companies like what those services are. I think I read yesterday Snowflake was saying like, their biggest customers are growing at 30, like 50 or 60%. Like the, value they get out of it is becoming exponential. And it's just a matter of like, will the economics allow the next big thing to happen? Because some of these things are pretty, pretty costly, you know, expensive to get started. So I'm bullish on the idea. I don't know that it becomes, I think it's okay that it's still sort of, you know, niche plus, plus in terms of the size of it. Because, you know, if we think about all of IT it's still, you know, even microservices is a small part of bigger things. But I'm still really bullish on the idea. I like that it's been proven. I'm a little wary, like a lot of people have the economics of, you know, what might slow things down a little bit. But yeah, I, think the future is going to involve Supercloud somewhere, whatever people end up calling it. And you and I discussed that. (laughs) But I don't, I don't think it goes away. I don't think it's, I don't think it's a fad. I think it is something that people see tremendous value and it's just, it's got to be, you know, for what you're trying to do, your application specific thing. >> You're making a great point on the funding of innovation and we're entering a new era of public policy as well. R and D tax credit is now is shifting. >> Yeah. >> You know, you're going to have to capitalize that over five years now. And that's something that goes back to the 1950s and many people would argue that's at least in part what has helped the United States be so, you know, competitive in tech. But Brian, always great to talk to you. Thanks so much for participating in the program. Great to see you. >> Thanks Dave, appreciate it. Good luck with the rest of the show. >> Thank you. All right, this is Dave Vellante for John Furrier, the entire Cube community. Stay tuned for more content from Supercloud2.

>>Hello and run. Welcome back to the Cube's live coverage here. Day three of Cube's coverage, two sets, wall to wall coverage. Third set upstairs in the Executive Briefing Center. I'm John Furry, host of the Cube with Dave Alon. Two other hosts here. Lot of action. Dave. The cheer here is the CEO of MongoDB, exclusive post on Silicon Angle for your prior to the event. Thanks for doing that. Great to see >>You. Likewise. Nice to see you >>Coming on. See you David. So it's great to catch up. Prior to the event for that exclusive story on ecosystem, your perspective that resonated with a lot of the people. The traffic on that post and comments have been off the charts. I think we're seeing a ecosystem kind of surge and not change over, but like a an and ISV and new platform. So I really appreciate your perspective as a platform ISV for aws. What's it like? What's this event like? What's your learnings? What's your takeaway from your customers here this year? What's the most important story going on? >>First of all, I think being here is important for us because we have so many customers and partners here. In fact, if you look at the customers that Amazon themselves announced about two thirds of those customers or MongoDB customers. So we have a huge overlap in customers here. So just connecting with customers and partners has been important. Obviously a lot of them are thinking about their plans going to next year. So we're kind of meeting with them to think about what their priorities are and how we can help. And also we're sharing a little bit of our product roadmap in terms of where we're going and helping them think through like how they can best use Mongadi B as they think about their data strategy, you know, going to next year. So it's been a very productive end. We have a lot of people here, a lot of sales people, a lot of product people, and there's tons of customers here. So we can get a lot accomplished in a few days. >>Dave and I always talk on the cube. Well, Dave always goes to the TAM expansion question. Expanding your total stressful market, the market is changing and you guys have a great position growing positioned. How do you look at the total addressable market for Mongo changing? Where's the growth gonna come from? How do you see your role in the market and how does that impact your current business model? >>Yeah, our whole goal is to really enable developers to think about Mongo, to be first when they're building modern applications. So what we've done is first built a fir, a first class transactional platform and now we've kind expanding the platform to do things like search and analytics, right? And so we are really offering a broad set of capabilities. Now our primary focus is the developer and helping developers build these amazing applications and giving them tools to really do so in a very quick way. So if you think about customers like Intuit, customers like Canva, customers like, you know, Verizon, at and t, you know, who are just using us to really transform their business. It's either to build new applications quickly to do things at a certain level of performance of scale they've never done before. And so really enabling them to do so much more in building these next generation applications that they can build anywhere else. >>So I was listening to McDermott, bill McDermott this morning. Yeah. And you listen to Bill, you just wanna buy from the guy, right? He's amazing. But he was basically saying, look, companies like he was talking about ServiceNow that could help organizations digitally transform, et cetera, but make money or save money or in a good position. And I said, right, Mongo's definitely one of those companies. What are those conversations like here? I know you've been meeting with customers, it's a different environment right now. There's a lot of uncertainty. I, I was talking to one of your customers said, yeah, I'm up for renewal. I love Mongo. I'm gonna see if they can stage my payments a little bit. You know, things like that. Are those conversations? Yeah, you know, similar to what >>You having, we clearly customers are getting a little bit more prudent, but we haven't seen any kind of like slow down terms of deal cycles or, or elongated sales cycles. I mean, obviously different customers in different sectors are going through different issues. What we are seeing customers think about is like how can I, you know, either drive more efficiency in my business like and big part of that is modernization of my existing legacy tech stack. How can maybe consolidate to a fewer set of vendors? I think they like our broad platform story. You know, rather than using three or four different databases, they can use MongoDB to do everything. So that that resonates with customers and the fact that they can move fast, right? Developer productivity is a proxy for innovation. And so being able to move fast to either seize new opportunities or respond to new threats is really, you know, top of mind for still C level executive. >>So can your software, you're right, consolidation is the number one way in which people are save money. Can your software be deflationary? I mean, I mean that in a good way. So >>I was just meeting with a customer who was thinking about Mongo for their transactional platform, elastic for the search platform and like a graph database for a special use case. And, and we said you can do all that on MongoDB. And he is like, oh my goodness, I can consolidate everything. Have one elegant developer interface. I can keep all the data in one place. I can easily access that data. And that makes so much more sense than having to basically use a bunch of peace parts. And so that's, that's what we're seeing more and more interest from customers about. >>So one of the things I want to get your reaction to is, I was saying on the cube, now you can disagree with me if you want, but at, in the cloud native world at Cuban and Kubernetes was going through its hype cycle. The conversation went to it's getting boring. And that's good cause they want it to be boring. They don't want people to talk about the run time. They want it to be working. Working is boring. That's invisible. It's good, it's sticky, it's done. As you guys have such a great sticky business model, you got a great install base. Mongo works, people are happy, they like the product. So it's kind of working, I won't wanna say boring cuz that's, it's irrelevant. What's the exciting things that Mongo's bringing on top of the existing base of product that is gonna really get your clients and prospects enthused about the innovation from Mongo? What's what cuz it's, it's almost like electricity in a way. You guys are very utility in, in the way you do, but it's growing. But is there an exciting element coming that you see that they should pay attention to? What's, what's your >>Vision that, right, so if you look back over the last 10, 15 years, there's been big two big platform shifts, mobile and cloud. I think the next big platform shift is from what I call dumb apps to smart apps. So building more intelligence into applications. And what that means is automating human decision making and embedding that into applications. So we believe that to be a fundamentally a developer problem to solve, yes, you need data scientist to build the machine learning algorithms to train the models. Yeah. But ultimately you can't really deploy, deployed at scale unless you give developers the tools to build those smart applications that what we focused on. And a big part of that is what we call application driven analytics where people or can, can embed that intelligence into applications so that they can instead rather having humans involved, they can make decisions faster, drive to businesses more quickly, you know, shorten it's short and time to market, et cetera. >>And so your strategy to implement those smart apps is to keep targeting the developer Yes. And build on that >>Base. Correct. Exactly. So we wanna essentially democratize the ability for any customer to use our tools to build a smart applications where they don't have the resources of a Google or you know, a large tech company. And that's essentially resonating with our customer base. >>We, we were talking about this earlier after Swami's keynote, is most companies struggle to put data at the core of their business. And I don't mean centralizing it all in a single place as data's everywhere, but, but really organizing their company and democratizing data so people can make data decisions. So I think what you're saying, essentially Atlas is the platform that you're gonna inject intelligence into and allow developers to then build applications that are, you know, intelligent, smart with ai, machine intelligence, et cetera. And that's how the ones that don't have the resources of a Google or an Amazon become correct the, that kind of AI company if >>You, and that's, that's the whole purpose of a developer data platform is to enable them to have the tools, you know, to have very sophisticated analytics, to have the ability to do very sophisticated indexes, optimized for analytics, the ability to use data lakes for very efficient storage and retrieval of data to leverage, you know, edge devices to be able to capture and synchronize data. These are all critical elements to build these next generation applications. And you have to do that, but you don't want to stitch together a thousand primitives. You want to have a platform to do that. And that's where we really focus. >>You know, Dave, Dave and I, three, two days, Dave and I, Dave Ante and I have been talking a lot about developer productivity. And one observation that's now validated is that developers are setting the pace for innovation. Correct? And if you look at the how they, the language that they speak, it's not the same language as security departments, right? They speak almost like different languages, developer and security, and then you got data language. But the developers are making choices of self-service. They can accelerate, they're driving the behavior behavior into the organizations. And this is one of the things I wrote about on Friday last week was the organizational changes are changing cuz the developers set the pace. You can't force tooling down their throat. They're gonna go with what's easy, what's workable. If you believe that to be true, then all the security's gonna be in the developer pipeline. All the innovations we've driven off that high velocity developer site, we're seeing success of security being embedded there with the developers. What are you gonna bring up to that developer layer that's going to help with security, help with maybe even new things, >>Right? So, you know, it's, it's almost a cliche to say now software is in the world, right? Because every company's value props is driven by, it's either enabled to find or created through software. What that really means is that developers are eating all the work, right? And you're seeing, you saw in DevOps, right? Where developers basically enro encroach into the ops world and made infrastructure a programmable interface. You see developers, to your point, encroaching in security, embedding more and more security features into their applications. We believe the same thing's gonna happen with data scientists and business analysts where developers are gonna embed that functionality that was done by different domains in the Alex world and embed that capability into apps themselves. So these applications are just naturally smarter. So you don't need someone to look at a dashboard and say, aha, there's some insight here now I need to go make a decision. The application will do that for you and actually make that decision for you so you can move that much more quickly to run your business either more efficiently or to drive more, you know, revenue. >>Well the interesting thing about your business is cuz you know, you got a lot of transactional activity going on and the data, the way I would say what you just described is the data stack and the application stacks are coming together, right? And you're in a really good position, I think to really affect that. You think about we've, we've operationalized so many systems, we really haven't operationalized our data systems. And, and particularly as you guys get more into analytics, it becomes an interesting, you know, roadmap for Mongo and your customers. How do you see that? >>Yeah, so I wanna be clear, we're not trying to be a data warehouse, I get it. We're not trying to be like, you know, go compete. In fact, we have nice partnership with data bricks and so forth. What we are really trying to do is enable developers to instrument and build these applications that embed analytics. Like a good analogy I'd use is like Google Maps. You think about how sophisticated Google Maps has, and I use that because everyone has used Google Maps. Yeah. Like in the old, I was old enough to print out the directions, map quest exactly, put it on my lap and drive and look down. Now have this device that tells me, you know, if there's a traffic, if there's an accident, if there's something you know, going will reroute me automatically. And what that app is doing is embedding real time data into, into its decision making and making the decision for you so that you don't have to think about which road to take. Right? You, you're gonna see that happen across almost every application over the next X number of years where these applications are gonna become so much smarter and make these decisions for you. So you can just move so much more quickly. >>Yeah. Talk about the company, what status of the company, your growth plans. Obviously you're seeing a lot of news and Salesforce co CEO just resigned, layoffs at cnn, layoffs at DoorDash. You know, tech unfortunately is not impacted, thank God. I'm not that too bad. Certainly in cloud's not impacted it is impacting some of the buying behavior. We talked about that. What's going on with the company head count? What's your goals? How's the team doing? What are your priorities? >>Right? So we we're going after a big, big opportunity. You know, we recognize, obviously the market's a little choppy right now, but our long term, we're very bullish on the opportunity. We believe that we can be the modern developer data platform to build these next generation applications in terms of costs. We're obviously being a little bit more judicious about where we're investing, but we see big, big opportunities for us. And so our overall cost base will grow next year. But obviously we also recognize that there's ways to drive more efficiency. We're at a scale now. We're a 1.2 billion business. We're gonna announce our Q3 results next week. So we'll talk a little bit more about, you know, what we're seeing in the business next week. But we, we think we're a business that's growing fast. You know, we grew, you know, over 50, 50% and so, so we're pretty fast growing business. Yeah. You see? >>Yeah, Tuesday, December 6th you guys announce Exactly. Course is a big, we always watch and love it. So, so what I'm hearing is you're not, you're not stepping on the brakes, you're still accelerating growth, but not at all costs. >>Correct. The term we're using is profitable growth. We wanna, you know, you know, drive the business in a way that we think continues to seize the opportunity. But we also, we always exercise discipline. You know, I, I'm old enough where I had to deal with 2000 and 2008, so, you know, seen the movie before, I'm not 28 and have not seen these markets. And so obviously some are, you know, emerging leaders have not seen these kinds of markets before. So we're kind of helping them think about how to continue to be disciplined. And >>I like that reference to two thousand.com bubble and the financial crisis of 2008. I mentioned this to you when we chat, I'd love to get your thoughts. Now looking back for reinvent, Amazon wasn't a force in, in 2008. They weren't really that big debt yet. Know impact agility, wasn't it? They didn't hit that, they didn't hit that cruising altitude of the value pro cloud agility, time of value moving fast. Now they are. So this is the first time that they're a part of the economic equation. You're on, you're on in the middle of it with Amazon. They could be a catalyst to recover faster if plan properly. What's your CEO take on just that general and other CEOs might be watching and saying, Hey, you know, if I play this right, I could leverage the cloud. You know, Adams is leading into the cloud during a recession. Okay, I get that. But specifically there might be a tactic. What's your view on >>That? I mean, what, what we're seeing the, the hyperscalers do is really continue to kind of compete at the raw infrastructure level on storage, on compute, on network performance, on security to provide the, the kind of the building blocks for companies like Monga Beach really build on. So we're leveraging that price performance curve that they're pushing. You know, they obviously talk about Graviton three, they're talking about their training model chip sets and their inference model chip sets and their security chip sets. Which is great for us because we can leverage those capabilities to build upon that. And I think, you know, if you had asked me, you know, in 2008, would we be talking about chip sets in 2022? I'd probably say, oh, we're way beyond that. But what it really speaks to is those things are still so profoundly important. And I think that's where you can see Amazon and Google and Microsoft compete to provide the best underlying infrastructure where companies like mongadi we can build upon and we can help customers leverage that to really build the next generation. >>I'm not saying it's 2008 all over again, but we have data from 2008 that was the first major tailwind for the cloud. Yeah. When the CFO said we're going from CapEx to opex. So we saw that. Now it's a lot different now it's a lot more mature >>I think. I think there's a fine tuning trend going on where people are right sizing, fine tuning, whatever you wanna call it. But a craft is coming. A trade craft of cloud management, cloud optimization, managing the cost structures, tuning, it's a crafting, it's more of a craft. It's kind of seems like we're >>In that era, I call it cost optimization, that people are looking to say like, I know I'm gonna invest but I wanna be rational and more thoughtful about where I invest and why and with whom I invest with. Versus just like, you know, just, you know, everyone getting a 30% increase in their opex budgets every year. I don't think that's gonna happen. And so, and that's where we feel like it's gonna be an opportunity for us. We've kind of hit scap velocity. We've got the developer mind share. We have 37,000 customers of all shapes and sizes across the world. And that customer crown's only growing. So we feel like we're a place where people are gonna say, I wanna standardize among the >>Db. Yeah. And so let's get a great quote in his keynote, he said, if you wanna save money, the place to do it is in the cloud. >>You tighten the belt, which belt you tightening? The marketplace belt, the wire belt. We had a whole session on that. Tighten your belt thing. David Chair, CEO of a billion dollar company, MongoDB, continue to grow and grow and continue to innovate. Thanks for coming on the cube and thanks for participating in our stories. >>Thanks for having me. Great to >>Be here. Thank. Okay, I, Dave ante live on the show floor. We'll be right back with our final interview of the day after this short break, day three coming to close. Stay with us. We'll be right back.

>>Hi, I'm John Ferry with the Cube. We're here for a special exclusive conversation with David Geria, the CEO of Mongo MongoDB. Well established leading platform. It's been around for, I mean, decades. So continues to become the platform of choice for high performance data. This modern data stack that's emerging, a big part of the story here at a reinvent 2022 on top of an already performing a cloud with, you know, chips and silicon specialized instances, the world's gonna be getting faster, smaller, higher performance, lower cost specialized. Dave, thanks for taking the time with me today, >>John. It's great to be here. Thank you for having me. >>Do you see yourself as a ISV or you just go with that, because that's kind of a nomenclature >>When, when I think of the term isv, I think of the notion of someone building an end solution for customer to get something done. Or what we're building is essentially a developer data platform and we have thousands of ISVs who build software applications on our platform. So how could we be an isv? Because by definition I, you know, we enable people to do so many different things and you know, they can be the, you know, the largest companies of the world trying to transform their business or startups who are trying to disrupt either existing industries or create new ones. And so that's, and, and that's how our customers view MongoDB and, and the whole Atlas platform basically enables them to do some amazing things. The reason for that is, you know, you know, we believe that what we are enabling developers to do is be able to reduce the friction and the work required to build modern applications through the document model, which is really intuitive to the way developers think and code through the distributed nature of platforms. >>So, you know, things like charting no other company on the planet offers the capabilities we do to enable people to build the most highly performant and scalable applications. And also what we also do is enable people to, you know, run different types of workloads on our platform. So we have obviously transactional, we have search, we have time series, we enable people to do things like sophisticated device synchronization from Edge to the back end. We do graph, we do real time analytics. So being able to consolidate all that with developers on one elegant unified platform really makes, you know, it attractive for developers to build on long >>Db. You know, you guys are a feature partner of aws and I would speculate, I don't know if you can comment on this, but I would imagine that you probably produce a lot of revenue for Amazon because you really can't turn off EC two when you do a database work. So, you know, you kind of crank it all the time. You guys are a top partner. How long have you guys been a partner with aws? What's the relationship? >>The relationship's been strong, actually, Amazon spoke at one of our first user conferences in 2013. And since then we've been working together. We've been at reinvent since essentially 2015. And we've been a premier partner, an Emerald sponsor for the last Nu you know, I think four or five years. And so we're very committed to the relationship and I think there's some things that we have a lot, we have a lot of things in common. We care a lot about customers and for us, our customers, our developers, we care a lot about removing friction from their day to day work to move, be able to move fast and be able to, in order to seize new opportunities and respond to new threats. And so consequently, I think the partnership, obviously by nature of our, our common objectives has really come together. >>Talk about the journey of Mongo. I mean, you look back at the history, I, you go back the old lamp stack days, right? So you know, the day developer traction is just really kind of stuck at the none. I mean, it's, it's really well known. And I remember over the conversations, Dave Mongo doesn't scale. I mean, every year we heard something along those lines cuz it just kept scaling. I heard the same thing with AWS back in 2013 timeframe. You, oh, it's just, it's really not for a real prime time. It's, it's for hobbyists, not so much builders, maybe startup cloud, but that developer traction is translated. Can you take us through the journey of Mongo where it is now and, and kinda look back and, and, and take us through what's the state of the art now, >>Right? So just for those of you who, who, those, you know, those in your audience who don't know too much about Mon Be I'll just, you know, start with the background. The company was astounded by developers. It was basically the CTO and some key developers from Double Click who really saw the challenges and the limitations of the relational database architecture because they're trying to serve billions of ads per day and they constantly need to work on the constraints and relational database. And so they essentially decided, why don't we just build a database that we'd want to use? And that was a catalyst to starting MongoDB. The first thing they focused on was, rather than having a tabler data structure, they focused on a document data structure. Why documents? Because there's much more natural and intuitive to work with data and documents in terms of you can set parent child relationships and how you just think about the relationship with data is much more natural in a document than trying to connect data in a, you know, in hundreds of different tables. >>And so that enabled developers to just move so much faster. The second thing they focused on was building a truly distributed architecture, not kind of some adjunct, you know, you know, architecture that maybe made the existing architecture a little bit more scalable. They really took from the ground up a truly distributed architecture. So where you can do native replication, you can do charting and you can do it on a global basis. And so that was the, the other profound, you know, thing that they did. And then since then, what we've also done is, you know, the document model is truly a super set of other models. So we enabled other capabilities like search you can do joins, so you can do very transaction intensive use case among be where fully asset compliant. So you have the highest forms of data guarantees you can do very sophisticated things like time series, you can do device synchronization, you can do real time analytics because we can carve off read only nodes to be able to read and query data in real time rather than have to offload that data into a data warehouse. >>And so that enables developers to just build a wide variety of, of application longing to be, and they get one unified developer interface. It's highly elegant and seamless. And so essentially the cost and tax of matching multiple point tools goes away when, when I think of the term isv, I think of the notion of someone building an end solution for a customer to get something done. Or what we're building is essentially a developer data platform and we have thousands of ISVs who build software applications on our platform. So how could we be an isv? Because by definition I, you know, we enable people to do so many different things and you know, they can be the, you know, the largest companies in the world trying to transform their business or startups or trying to disrupt either existing industries or create new ones. And so that's, and and that's how our customers view MongoDB and, and the whole Atlas platform basically enables them to do some amazing things. >>Yeah, we're seeing a lot of activity on the Atlas. Do you see yourself as a ISV or you just go with that because that's kind of a nomenclature? >>No, we don't view ourselves as ISV at all. We view ourselves as a developer data platform. And the reason for that is, you know, you know, we believe that what we are enabling developers to do is be able to reduce the friction and the work required to build modern applications through the document model, which is really intuitive to the way developers think and code through the distributed nature of platforms. So, you know, things like sharding, no other company on the planet offers the capabilities we do to enable people to build the most highly performant and scalable applications. And also what we also do is enable people to, you know, run different types of workflows on our platform. So we have obviously transactional, we have search, we have time series, we enable people to do things like sophisticated device synchronization from Edge to the back end. We do graph, we do real time analytics. So being able to consolidate all that with developers on one elegant unified platform really makes, you know, it attractive for developers to build on long ndb. >>You know, the cloud adoption really is putting a lot of pressure on these systems and you're seeing companies in the ecosystem and AWS stepping up, you guys are doing great job, but we're seeing a lot more acceleration around it, on staying on premise for certain use cases. Yet you got the cloud as well growing for workloads and, and you get this hybrid steady state as an operational mode. I call that 10 of the classic cloud adoption track record. You guys are an example of multiple iterations in cloud. You're doing a lot more, we're starting to see this tipping point with others and customers coming kind of on that same pattern. Building platforms on top of aws on top of the primitives, more horsepower, higher level services, industry specific capabilities with data. I mean this is a new kind of cloud, kind of a next generation, you knows next gen you got the classic high performance infrastructure, it's getting better and better, but now you've got this new application platform, you know, reminds me of the old asp, you know, if you will. I mean, so are you seeing customers doing things differently? Can you share your, your reaction to this role of, you know, this new kind of SaaS platform that just isn't an application, it's, it's more, it's deeper than that. What's going on here? We call it super cloud, but >>Like what? Yeah, so essentially what what, you know, a lot of our customers doing, and by the way we have over 37,000 customers of all shapes and sizes from the largest companies in the world to cutting edge startups who are building applications among B, why do they choose MongoDB? Because essentially it's the, you know, the fastest way to innovate and the reason it's the fastest way to innovate is because they can work with data so much easier than working with data on other types of architecture. So the document model is profoundly a breakthrough way to work with data to make it very, very easy. So customers are essentially building these modern applications, you know, applications built on microservices, event driven architectures, you know, addressing sophisticated use cases like time series to, and then ultimately now they're getting into machine learning. We have a bunch of companies building machine learning applications on top of MongoDB. And the reason they're doing that is because one, they get the benefits of being able to, you know, build and work with, with data so much easier than any other platform. And it's highly scale and performant in a way that no other platform is. So literally they can run their, you know, workloads both locally and one, you know, autonomous zone or they can basically be or available zone or they could be basically, you know, anywhere in the world. And we also offer multicloud capabilities, which I can get into later. >>Let's talk about the performance side. I know I was speaking with some Amazon folks every year it's the same story. They're really working on the physics, they're getting the chips, they wanna squeeze as much energy out of that. I've never met a developer that said they wanna run their workload on a slower platform or slower hardware. We know said no developer, right? No one wants to do that. >>Correct. >>So you guys have a lot of experience tuning in with Graviton instances, we're seeing a lot more AWS EC two instances, we're seeing a lot more kind of integrated end to end stories. Data is now security, it's tied into data stacks or data modern kind of data hybrid stack. A lot going on around the hardware performance specialization, the role of data, kind of a modern data stack emerging. What, what's your thoughts on the that that Yeah, >>I, I think if you had asked me, you know, when the cloud started going vogue, like you know, the, you know, the, the later part of the last decade and told me, you know, sitting here 12, 15 years later, would you know, would we be talking about, you know, chip processing speeds? I'd probably thought, nah, we would've moved on by then. But what's really clear is that customers, to your point, customers care about performance, they care about price performance, right? So AWS's investments in Graviton, we have actually deployed a significant portion of our at fleet on Amazon now runs on Graviton. You know, they've built other chip sets like train and, and inferential for like, you know, training models and running inferences. They're doing things like Nitro. And so what that really speaks to is that the cloud providers are focusing on the price performance of their, as you call it, their primitives and their infrastructure and the infrastructure layer that are still very, very important. >>And, and you know, if you look at their revenue, about 60 to 70% of the revenue comes from that pure infrastructure. So to your point, they can't offer a second class solution and still win. So given that now they're seeing a lot of competition from Azure, Azure's building their own chip sets, Google's already obviously doing that and and building specialized chip sets for machine learning. You're seeing these cloud providers compete. So they have to really compete to make their platform the most performant, the most price competitive in the marketplace. Which gives us a great platform to build on to enable developers to build these incredibly highly performant applications that customers are now demand. >>I think that's a really great point. I mean, you know, it's so funny Dave, because you know, I remember those, we don't talk speeds and feeds anymore. We're not talking about boxes. I mean that's old kind of school thinking because it was a data center mentality, speeds and feeds and that was super important. But we're kind of coming back to that in the cloud now in distributed architecture, as you put your platforms out there for developers, you have to run fast. You gotta, you can't give the developer subpar or any kind of performance that's, they'll, they'll go somewhere else. I mean that's the reality of what developers, no one, again, no one says I wanna go on the slower platform unless it's some sort of policy based on price or some sort of thing. But, but for the most part it's gotta run fast. So you got the tail of two clouds going on here, you got Amazon classic ias, keep making it faster under the hood. >>And then you got the new abstraction layers of the higher level services. That's where you guys are bridging this new, new generational shift where it's like, hey, you know what? I can go, I can run a headless application, I can run a SAS app that's refactored with data. So you've seen a lot more innovation with developers, you know, running stuff in, in the C I C D pipeline that was once it, and you're seeing security and data operations kind of emerging as a structural change of how companies are, are are transforming on the business side. What's your reaction to that business transformation and the role of the developer? >>Right, so I mean I have to obviously give amazing kudos to the, you know, to AWS and the Amazon team for what they've built. Obviously they're the ones who kind of created the cloud industry and they continue to push the innovation in the space. I mean today they have over 300 services and you know, obviously, you know, no star today is building anything not on the cloud because they have so many building blocks to start with. But what we though have found from our talking to our customers is that in some ways there is still, you know, the onus is on the customer to figure out which building block to use to be able to stitch together the applications and solutions they wanna build. And what we have done is taken essentially an opinionated point of view and said we will enable you to do that. >>You know, using one data model. You know, Amazon today offers I think 17 or 18 different types of databases. We don't think like, you know, having a tool for every job makes sense because over time the tax and cost of learning, managing and supporting those different applications just don't make a lot of sense or just become cost prohibitive. And so we think offering one data model, one, you know, elegant user experience, you know, one way to address the broadest set of of use cases is that we think is a better way. But clearly customers have choice. They can use Amazon's primitives and those second layer services as you as you described, or they can use us. Unfortunately we've seen a lot of customers come to us with our approach and so does Amazon. And I have to give obviously again kudos and Amazon is very customer obsessed and so we have a great relationship with them, both technically in terms of the product integrations we do as well as working with 'em in the field, you know, on joint customer opportunities. >>Speaking of, while you mentioned that, I wanna just ask you, how is that marketplace relationship going with aws? Some of the partners are really seeing great economic and joint selling or them selling your, your stuff. So there's a real revenue pop there in that religion. Can you comment on that? >>So we had been working the partner in the marketplace for many years now, more from a field point of view where customers could leverage their existing commitments to AWS and leverage essentially, you know, using Atlas and applying in an atlas towards their commits. There was also some sales incentives for people in the field to basically work together so that, you know, everyone won should we collectively win a customer? What we recently announced is as pay as you Go initiative, where literally a customer on the Amazon marketplace can basically turn up, you know, an Alice instance with no commitment. So it's so easy. So we're just pushing the envelope to just reduce the friction for people to use Atlas on aws. And it's working really very well. The uptake has been been very strong and and we feel like we're just getting started because we're so excited about the results we're >>Seeing. You know, one of the things that's kind of not core in the keynote theme, but I think it's underlying message is clear in the industry, is the developer productivity. You said making things easy is a big deal, self-service, getting in and trying, these are what developer friendly tools are like and platform. So I have to ask you, cuz this comes up a lot in our kind of business conversation, is, is if you take digital transformation concept to its completion, assuming now you know, as a thought exercise, you completely transform a company with technology that's, that is the business transformation outcome. Take it to completion. What does that look like? I mean, if you go there you'd say, okay, the company is the app, the company is the data, it's not a department serving the business, it's the business. And so I think this is kind of what we're seeing as the next big mountain climb, which is companies that do transform there, they are technology companies, they're not a department like it. So I think a lot of companies are kind of saying, wait a minute, why would we have a department? It should be the company. What's your your your view on this because this >>Yeah, so I I've had the for good fortune of being able to talk to thousand customers all over the world. And you know, one thing John, they never tell me, they never tell me that they're innovating too quickly. In fact, they always tell me the reverse. They tell me all the obstacles and impediments they have to be able to be able to be able to move fast. So one of the reasons they gravitate to MongoDB is just the speed that they wish they can build applications to, to your point, developer productivity. And by definition, developer productivity is a proxy for innovation. The faster you can make your developers, you know, move, the faster they can push out code, the faster they can iterate and build new solutions or add more capabilities on the existing applications, the faster you can innovate either to, again, seize new opportunities or to respond to new threats in your business. >>And so that resonates with every C level executive. And to your point, the developers not some side hustle that they kind of think about once in a while. It's core to the business. So developers have amassed enormous amount of power and influence. You know, their, their, their engineering teams are front and center in terms of how they think about building capabilities and and building their business. And that's also obviously enabled, you know, to your point, every software company, every company's not becoming a software company because it all starts with softwares, software enables, defines or creates almost every company's value proposition. >>You know, it makes me smile because I love operating systems as one of my hobbies in college was, you know, systems programming and I remember those network kind of like the operating systems, the cloud. So, you know, everything's got specialized capabilities and that's a big theme here at Reinvent. If you look at the announcements Monday night with Peter DeSantis, you got, you got new instances, new chips. So this whole engine kind of specialized component is like an engine. You got a core and you got other subsystems. This is gonna be an integral part of how companies architect their platform or you know, Adam calls it the landing zone or whatever they wanna call it. But you gotta start seeing a new architectural thinking for companies. What's your, can you share your experience on how companies should look at this opportunity as a plethora of more goodness on the hardware? On hardware, but like chips and instances? Cause now you can mix and match. You've got, you've got, you got everything you need to kind of not roll your own but like really build foundational high performance capabilities. >>Yeah, so I I, so I think this is where I think Amazon is really enabling all companies, including, you know, companies like Mon db, you know, push the envelope and innovation. So for example, you know, the, the next big hurdle for us, I think we've seen two big platform shifts over the last 15 years of platform shifts, you know, to mobile and the platform shift to cloud. I believe the next big platform shift is going from dumb apps to smart apps, which you're building in, you know, machine learning and you know, AI and just very sophisticated automation. And when you start automating human decision making, rather than, you know, looking at a dashboard and saying, okay, I see the data now, now I have to do this. You can automate that into your applications and make your applications leveraging real time data become that much more smart. And that ultimately then becomes a developer challenge. And so we feel really good about our position in taking advantage of those next big trends and software leveraging the price performance curves that, you know, Amazon continues to push in terms of their hardware performance, networking performance, you know, you know, price, performance and storage to build those next generation of modern applications. >>Okay, so let me get this straight. You have next generation intelligent smart apps and you have AI generative solutions coming out around the corner. This is like pretty good position for Mongo to be in with data. I mean, this is what you do, you're in that exactly of the action. What's it like? I mean, you must be like trying to shake the world and wake up. The world's starting to wake up now through this. So what's, what's it like? >>Well, I mean we're really excited and bullish about the future. We think that we're well positioned because we know as to your point, you know, we have amassed amazing amount of developer mindshare. We are the most popular modern data platform out there in the world. There's developers in almost every corner of the planet using us to do something. And to your point, leveraging data and these advances in machine learning ai. And we think the more AI becomes democratized, not, you know, done by a bunch of data scientists sitting in some corner office, but essentially enabling developers to have the tools to build these very, very sophisticated, smart applications will, you know, will position as well. So that's, you know, obviously gonna be a focus for us over the, frankly, I think this is gonna be like a 10 year, 10 15 year run and we're just getting started in this whole >>Area. I think you guys are really well positioned. I think that's a great point. And Adam mentioned to me and, and Mike interviewed, he said on stage talk about it, the role of a data analyst kind of goes away. Everyone's a data analyst, right? You'll still see specialization on, on core data engineering, which is kind of like an SRE role for data. So data ops and data as code is a big deal making data applications. So again, exciting times and you guys are well positioned. If you had to bumper sticker the event this week here at Reinvent, what would you, how would you categorize this this point in time? I mean, Adam's great leader, he is gonna help educate customers how to use technology to, for business advantage and transformation. You know, Andy did a great job making technology great and innovative and setting the table, Adam's gotta bring it to the enterprises and businesses. So it's gonna be an interesting point in time we're in now. What, how would you categorize this year's reinvent, >>Right? I think the, the, the tech world is pivoting towards what I'd call rationalization or cost optimization. I think people obviously in, you know, the last 10 years have, you know, it's all about speed, speed, speed. And I think people still value speed, but they wanna do it at some sort of predictable cost model. And I think you're gonna see a lot more focus around cost and cost optimization. That's where we think having one platform is by definition of vendor consolidation way for people to cut costs so that they can basically, you know, still move fast but don't have to incur the tax of using a whole bunch of different point tools. And so we think we're well positioned. So the bumper sticker I think about is essentially, you know, do more for less with MongoDB. >>Yeah. And the developers on the front lines. Great stuff. You guys are great partner, a top partner at AWS and great reflection on, on where you guys been, but really where you are now and great opportunity. David Didier, thank you so much for spending the time and it's been great following Mongo and the continued rise of, of developers of the on the front lines really driving the business and that, and they are, I know, driving the business, so, and I think they're gonna continue Smart apps, intelligent apps, ai, generative apps are coming. I mean this is real. >>Thanks John. It's great speaking with >>You. Yeah, thanks. Thanks so much. Okay.

(Intro music) >> Welcome back. We're LIVE here from SuperComputing 22 in Dallas Paul Gillin, for Silicon Angle in theCUBE with my guest host Dave... excuse me. And our, our guest today, this segment is Kim Leyenaar who is a storage performance architect at Broadcom. And the topic of this conversation is, is is networking, it's connectivity. I guess, how does that relate to the work of a storage performance architect? >> Well, that's a really good question. So yeah, I have been focused on storage performance for about 22 years. But even, even if we're talking about just storage the entire, all the components have a really big impact on ultimately how quickly you can access your data. So, you know, the, the switches the memory bandwidth, the, the expanders the just the different protocols that you're using. And so, and the big part of is actually ethernet because as you know, data's not siloed anymore. You have to be able to access it from anywhere in the world. >> Dave: So wait, so you're telling me that we're just not living in a CPU centric world now? >> Ha ha ha >> Because it is it is sort of interesting. When we talk about supercomputing and high performance computing we're always talking about clustering systems. So how do you connect those systems? Isn't that, isn't that kind of your, your wheelhouse? >> Kim: It really is. >> Dave: At Broadcom. >> It's, it is, it is Broadcom's wheelhouse. We are all about interconnectivity and we own the interconnectivity. You know, you know, years ago it was, 'Hey, you know buy this new server because, you know, we we've added more cores or we've got better memory.' But now you've got all this siloed data and we've got you know, we've got this, this stuff or defined kind of environment now this composable environments where, hey if you need more networking, just plug this in or just go here and just allocate yourself more. So what we're seeing is these silos really of, 'hey here's our compute, here's your networking, here's your storage.' And so, how do you put those all together? The thing is interconnectivity. So, that's really what we specialize in. I'm really, you know, I'm really happy to be here to talk about some of the things that that we do to enable high performance computing. >> Paul: Now we're seeing, you know, new breed of AI computers being built with multiple GPUs very large amounts of data being transferred between them. And the internet really has become a, a bottleneck. The interconnect has become a bottle, a bottleneck. Is that something that Broadcom is working on alleviating? >> Kim: Absolutely. So we work with a lot of different, there's there's a lot of different standards that we work with to define so that we can make sure that we work everywhere. So even if you're just a dentist's office that's deploying one server, or we're talking about these hyperscalers that are, you know that have thousands or, you know tens of thousands of servers, you know, we're working on making sure that the next generation is able to outperform the previous generation. Not only that, but we found that, you know with these siloed things, if, if you add more storage but that means we're going to eat up six cores using that it's not really as useful. So Broadcom's really been focused on trying to offload the CPU. So we're offloading it from, you know data security, data protection, you know, we're we do packet sniffing ourselves and things like that. So no longer do we rely on the CPU to do that kind of processing for us but we become very smart devices all on our own so that they work very well in these kind of environments. >> Dave: So how about, give, give us an example. I know a lot of the discussion here has been around using ethernet as the connectivity layer. >> Yes. >> You know, in in, in the past, people would think about supercomputing as exclusively being InfiniBand based. >> Ha ha ha. >> But give, give us an idea of what Broadcom is doing in the ethernet space. What, you know, what's what are the advantages of using ethernet? >> Kim: So we've made two really big announcements. The first one is our Tomahawk five ethernet switch. So it's a 400 gigi ethernet switch. And the other thing we announced too was our Thor. So we have, these are our network controllers that also support up to 400 gigi each as well. So, those two alone, it just, it's amazing to me how much data we're able to transfer with those. But not only that, but they're super super intelligent controllers too. And then we realized, you know, hey, we're we're managing all this data, let's go ahead and offload the CPU. So we actually adopted the Rocky Standards. So that's one of the things that puts us above InfiniBand is that ethernet is ubiquitous, it's everywhere. And InfiniBand is primarily just owned by one or two companies. And, and so, and it's also a lot more expensive. So ethernet is just, it's everywhere. And now with the, with the Rocky standards, we're working along with, it's, it's, it does what you're talking about much better than, you know predecessors. >> Tell us about the Rocky Standards. I'm not familiar with it. I'm sure some of our listeners are not. What is the Rocky standard? >> Kim: Ha ha ha. So it's our DNA over converged to ethernet. I'm not a Rocky expert myself but I am an expert on how to offload the CPU. And so one of the things it does is instead of using the CPU to transfer the data from, you know the user space over to the next, you know server when you're transferring it we actually will do it ourselves. So we'll handle it ourselves. We will take it, we will move it across the wire and we will put it in that remote computer. And we don't have to ask the CPU to do anything to get involved in that. So big, you know, it's a big savings. >> Yeah, I mean in, in a nutshell, because there are parts of the InfiniBand protocol that are essentially embedded in RDMA over converged ethernet. So... >> Right. >> So if you can, if you can leverage kind of the best of both worlds, but have it in an ethernet environment which is already ubiquitous, it seems like it's, kind of democratizing supercomputing and, and HPC and I know you guys are big partners with Dell as an example, you guys work with all sorts of other people. >> Kim: Yeah. >> But let's say, let's say somebody is going to be doing ethernet for connectivity, you also offer switches? >> Kim: We do, actually. >> So is that, I mean that's another piece of the puzzle. >> That's a big piece of the puzzle. So we just released our, our Atlas 2 switch. It is a PCIE Gen Five switch. And... >> Dave: What does that mean? What does Gen five, what does that mean? >> Oh, Gen Five PCIE, it's it's a magic connectivity right now. So, you know, we talk about the Sapphire Rapids release as well as the GENUWA release. I know that those, you know those have been talked about a lot here. I've been walking around and everybody's talking about it. Well, those enable the Gen Five PCIE interfaces. So we've been able to double the bandwidth from the Gen Four up to the Gen Five. So, in order to, to support that we do now have our Atlas two PCIE Gen Five switch. And it allows you to connect especially around here we're talking about, you know artificial intelligence and machine learning. A lot of these are relying on the GPU and the DPU that you see, you know a lot of people talking about enabling. So by in, you know, putting these switches in the servers you can connect multitudes of not only NVME devices but also these GPUs and these, these CPUs. So besides that we also have the storage component of it too. So to support that, we we just recently have released our 9,500 series HBAs which support 24 gig SAS. And you know, this is kind of a, this is kind of a big deal for some of our hyperscalers that say, Hey, look our next generation, we're putting a hundred hard drives in. So we're like, you know, so a lot of it is maybe for cold storage, but by giving them that 24 gig bandwidth and by having these mass 24 gig SAS expanders that allows these hyperscalers to build up their systems. >> Paul: And how are you supporting the HPC community at large? And what are you doing that's exclusively for supercomputing? >> Kim: Exclusively for? So we're doing the interconnectivity really for them. You know, you can have as, as much compute power as you want, but these are very data hungry applications and a lot of that data is not sitting right in the box. A lot of that data is sitting in some other country or in some other city, or just the box next door. So to be able to move that data around, you know there's a new concept where they say, you know do the compute where the data is and then there's another kind of, you know the other way is move the data around which is a lot easier kind of sometimes, but so we're allowing us to move that data around. So for that, you know, we do have our our tomahawk switches, we've got our Thor NICS and of course we got, you know, the really wide pipe. So our, our new 9,500 series HBA and RAID controllers not only allow us to do, so we're doing 28 gigabytes a second that we can trans through the one controller, and that's on protected data. So we can actually have the high availability protected data of RAID 5 or RAID 6, or RAID 10 in the box giving in 27 gigabytes a second. So it's, it's unheard of the latency that we're seeing even off of this too, we have a right cash latency that is sub 8 microseconds that is lower than most of the NVME drives that you see, you know that are available today. So, so you know we're able to support these applications that require really low latency as well as data protection. >> Dave: So, so often when we talk about the underlying hardware, it's a it's a game of, you know, whack-a-mole chase the bottleneck. And so you've mentioned PCIE five, a lot of folks who will be implementing five, gen five PCIE five are coming off of three, not even four. >> Kim: I know. >> So make, so, so they're not just getting a last generation to this generation bump but they're getting a two generations, bump. >> Kim: They are. >> How does that, is it the case that it would never make sense to use a next gen or a current gen card in an older generation bus because of the mismatch and performance? Are these things all designed to work together? >> Uh... That's a really tough question. I want to say, no, it doesn't make sense. It, it really makes sense just to kind of move things forward and buy a card that's made for the bus it's in. However, that's not always the case. So for instance, our 9,500 controller is a Gen four PCIE but what we did, we doubled the PCIE so it's a by 16, even though it's a gen four, it's a by 16. So we're getting really, really good bandwidth out of it. As I said before, you know, we're getting 28, 27.8 or almost 28 gigabytes a second bandwidth out of that by doubling the PCIE bus. >> Dave: But they worked together, it all works together? >> All works together. You can put, you can put our Gen four and a Gen five all day long and they work beautifully. Yeah. We, we do work to validate that. >> We're almost out our time. But I, I want to ask you a more, nuts and bolts question, about storage. And we've heard for, you know, for years of the aerial density of hard disk has been reached and there's really no, no way to excel. There's no way to make the, the dish any denser. What is the future of the hard disk look like as a storage medium? >> Kim: Multi actuator actually, we're seeing a lot of multi-actuator. I was surprised to see it come across my desk, you know because our 9,500 actually does support multi-actuator. And, and, and so it was really neat after I've been working with hard drives for 22 years and I remember when they could do 30 megabytes a second, and that was amazing. That was like, wow, 30 megabytes a second. And then, about 15 years ago, they hit around 200 to 250 megabytes a second, and they stayed there. They haven't gone anywhere. What they have done is they've increased the density so that you can have more storage. So you can easily go out and buy 15 to 30 terabyte drive, but you're not going to get any more performance. So what they've done is they've added multiple actuators. So each one of these can do its own streaming and each one of these can actually do their own seeking. So you can get two and four. And I've even seen a talk about, you know eight actuator per disc. I, I don't think that, I think that's still theory, but but they could implement those. So that's one of the things that we're seeing. >> Paul: Old technology somehow finds a way to, to remain current. >> It does. >> Even it does even in the face of new alternatives. Kim Leyenaar, Storage Architect, Storage Performance Architect at Broadcom Thanks so much for being here with us today. Thank you so much for having me. >> This is Paul Gillin with Dave Nicholson here at SuperComputing 22. We'll be right back. (Outro music)

(bright upbeat music) >> Welcome back, everyone, to the "Supercloud 22." I'm John Furrier, host of "The Cube." This is the Cloud-erati panel, the distinguished experts who have been there from day one, watching the cloud grow, from building clouds, and all open source stuff as well. Just great stuff. Good friends of "The Cube," and great to introduce back on "The Cube," Adrian Cockcroft, formerly with Netflix, formerly AWS, retired, now commentating here in "The Cube," as well as other events. Great to see you back out there, Adrian. Lori MacVittie, Cloud Evangelist with F5, also wrote a great blog post on supercloud, as well as Dave Vellante as well, setting up the supercloud conversation, which we're going to get into, and Chris Hoff, who's the CTO and CSO of LastPass who's been building clouds, and we know him from "The Cube" before with security and cloud commentary. Welcome, all, back to "The Cube" and supercloud. >> Thanks, John. >> Hi. >> All right, Lori, we'll start with you to get things going. I want to try to sit back, as you guys are awesome experts, and involved from building, and in the trenches, on the front lines, and Adrian's coming out of retirement, but Lori, you wrote the post setting the table on supercloud. Let's start with you. What is supercloud? What is it evolving into? What is the north star, from your perspective? >> Well, I don't think there's a north star yet. I think that's one of the reasons I wrote it, because I had a clear picture of this in my mind, but over the past, I don't know, three, four years, I keep seeing, in research, my own and others', complexity, multi-cloud. "We can't manage it. They're all different. "We have trouble. What's going on? "We can't do anything right." And so digging into it, you start looking into, "Well, what do you mean by complexity?" Well, security. Migration, visibility, performance. The same old problems we've always had. And so, supercloud is a concept that is supposed to overlay all of the clouds and normalize it. That's really what we're talking about, is yet another abstraction layer that would provide some consistency that would allow you to do the same security and monitor things correctly. Cornell University actually put out a definition way back in 2016. And they said, "It's an architecture that enables migration "across different zones or providers," and I think that's important, "and provides interfaces to everything, "makes it consistent, and normalizes the network," basically brings it all together, but it also extends to private clouds. Sometimes we forget about that piece of it, and I think that's important in this, so that all your clouds look the same. So supercloud, big layer on top, makes everything wonderful. It's unicorns again. >> It's interesting. We had multiple perspectives. (mumbles) was like Snowflake, who built on top of AWS. Jerry Chan, who we heard from earlier today, Greylock Penn's "Castles in the Cloud" saying, "Hey, you can have a moat, "you can build an advantage and have differentiation," so startups are starting to build on clouds, that's the native cloud view, and then, of course, they get success and they go to all the other clouds 'cause they got customers in the ecosystem, but it seems that all the cloud players, Chris, you commented before we came on today, is that they're all fighting for the customer's workloads on their infrastructure. "Come bring your stuff over to here, "and we'll make it run better." And all your developers are going to be good. Is there a problem? I mean, or is this something else happening here? Is there a real problem? >> Well, I think the north star's over there, by the way, Lori. (laughing) >> Oh, there it is. >> Right there. The supercloud north star. So indeed I think there are opportunities. Whether you call them problems or not, John, I think is to be determined. Most companies have, especially if they're a large enterprise, whether or not they've got an investment in private cloud or not, have spent time really trying to optimize their engineering and workload placement on a single cloud. And that, regardless of your choice, as we take the big three, whether it's Amazon, Google, or Microsoft, each of them have their pros and cons for various types of workloads. And so you'll see a lot of folks optimizing for a particular cloud, and it takes a huge effort up and down the stack to just get a single cloud right. That doesn't take into consideration integrations with software as a service, instantiated, oftentimes, on top of infrastructure of the service that you need to supplement where the obstruction layer ends in infrastructure of the service. You've seen most IS players starting to now move up-chain, as we predicted years ago, to platform as a service, but platforms of various types. So I definitely see it as an opportunity. Previous employers have had multiple clouds, but they were very specifically optimized for the types of workloads, for example, in, let's say, AWS versus GCP, based on the need for different types and optimized compute platforms that each of those providers ran. We never, in that particular case, thought about necessarily running the same workloads across both clouds, because they had different pricing models, different security models, et cetera. And so the challenge is really coming down to the fact that, what is the cost benefit analysis of thinking about multi-cloud when you can potentially engineer the resiliency or redundancy, all the in-season "ilities" that you might need to factor into your deployments on a single cloud, if they are investing at the pace in which they are? So I think it's an opportunity, and it's one that continues to evolve, but this just reminds me, your comments remind me, of when we were talking about OpenStack versus AWS. "Oh, if there were only APIs that existed "that everybody could use," and you saw how that went. So I think that the challenge there is, what is the impetus for a singular cloud provider, any of the big three, deciding that they're going to abstract to a single abstraction layer and not be able to differentiate from the competitors? >> Yeah, and that differentiation's going to be big. I mean, assume that the clouds aren't going to stay still like AWS and just not stop innovating. We see the devs are doing great, Adrian, open source is bigger and better than ever, but now that's been commercialized into enterprise. It's an ops problem. So to Chris's point, the cost benefit analysis is interesting, because do companies have to spin up multiple operations teams, each with specialized training and tooling for the clouds that they're using, and does that open up a can of worms, or is that a good thing? I mean, can you design for this? I mean, is there an architecture or taxonomy that makes it work, or is it just the cart before the horse, the solution before the problem? >> Yeah, well, I think that if you look at any large vendor... Sorry, large customer, they've got a bit of everything already. If you're big enough, you've bought something from everybody at some point. So then you're trying to rationalize that, and trying to make it make sense. And I think there's two ways of looking at multi-cloud or supercloud, and one is that the... And practically, people go best of breed. They say, "Okay, I'm going to get my email "from Google or Microsoft. "I'm going to run my applications on AWS. "Maybe I'm going to do some AI machine learning on Google, "'cause those are the strengths of the platforms." So people tend to go where the strength is. So that's multi-cloud, 'cause you're using multiple clouds, and you still have to move data and make sure they're all working together. But then what Lori's talking about is trying to make them all look the same and trying to get all the security architectures to be the same and put this magical layer, this unicorn magical layer that, "Let's make them all look the same." And this is something that the CIOs have wanted for years, and they keep trying to buy it, and you can sell it, but the trouble is it's really hard to deliver. And I think, when I go back to some old friends of ours at Enstratius who had... And back in the early days of cloud, said, "Well, we'll just do an API that abstracts "all the cloud APIs into one layer." Enstratius ended up being sold to Dell a few years ago, and the problem they had was that... They didn't have any problem selling it. The problem they had was, a year later, when it came up for renewal, the developers all done end runs around it were ignoring it, and the CIOs weren't seeing usage. So you can sell it, but can you actually implement it and make it work well enough that it actually becomes part of your core architecture without, from an operations point of view, without having the developers going directly to their favorite APIs around them? And I'm not sure that you can really lock an organization down enough to get them onto a layer like that. So that's the way I see it. >> You just defined- >> You just defined shadow shadow IT. (laughing) That's pretty- (crosstalk) >> Shadow shadow IT, yeah. >> Yeah, shadow shadow it. >> Yeah. >> Yeah. >> I mean, this brings up the question, I mean, is there really a problem? I mean, I guess we'll just jump to it. What is supercloud? If you can have the magic outcome, what is it? Enstratius rendered in with automation? The security issues? Kubernetes is hot. What is the supercloud dream? I guess that's the question. >> I think it's got easier than it was five, 10 years ago. Kubernetes gives you a bunch of APIs that are common across lots of different areas, things like Snowflake or MongoDB Atlas. There are SaaS-based services, which are across multiple clouds from vendors that you've picked. So it's easier to build things which are more portable, but I still don't think it's easy to build this magic API that makes them all look the same. And I think that you're going to have leaky abstractions and security being... Getting the security right's going to be really much more complex than people think. >> What about specialty superclouds, Chris? What's your view on that? >> Yeah, I think what Adrian is alluding to, those leaky abstractions, are interesting, especially from the security perspective, 'cause I think what you see is if you were to happen to be able to thin slice across a set of specific types of workloads, there is a high probability given today that, at least on two of the three major clouds, you could get SaaS providers that sit on those same infrastructure of the service clouds for you, string them together, and have a service that technically is abstracted enough from the things you care about to work on one, two, or three, maybe not all of them, but most SaaS providers in the security space, or identity space, data space, for example, coexist on at least Microsoft and AWS, if not all three, with Google. And so you could technically abstract a service to the point that you let that level of abstract... Like Lori said, no computer science problem could not be... So, no computer science problem can't be solved with more layers of abstraction or misdirection... Or redirection. And in that particular case, if you happen to pick the right vendors that run on all three clouds, you could possibly get close. But then what that really talks about is then, if you built your seven-layer dip model, then you really have specialty superclouds spanning across infrastructure of the service clouds. One for your identity apps, one for data and data layers, to normalize that, one for security, but at what cost? Because you're going to be charged not for that service as a whole, but based on compute resources, based on how these vendors charge across each cloud. So again, that cost-benefit ratio might start being something that is rather imposing from a budgetary perspective. >> Lori, weigh in on this, because the enterprise people love to solve complexity with more complexity. Here, we need to go the other way. It's a commodity. So there has to be a better way. >> I think I'm hearing two fundamental assumptions. One, that a supercloud would force the existing big three to implement some sort of equal API. Don't agree with that. There's no business case for that. There's no reason that could compel them to do that. Otherwise, we would've convinced them to do that, what? 10, 15 years ago when we said we need to be interoperable. So it's not going to happen there. They don't have a good reason to do that. There's no business justification for that. The other presumption, I think, is that we would... That it's more about the services, the differentiated services, that are offered by all of these particular providers, as opposed to treating the core IaaS as the commodity it is. It's compute, it's some storage, it's some networking. Look at that piece. Now, pull those together by... And it's not OpenStack. That's not the answer, it wasn't the answer, it's not the answer now, but something that can actually pull those together and abstract it at a different layer. So cloud providers don't have to change, 'cause they're not going to change, but if someone else were to build that architecture to say, "all right, I'm going to treat all of this compute "so you can run your workloads," as Chris pointed out, "in the best place possible. "And we'll help you do that "by being able to provide those cost benefit analysis, "'What's the best performance, what are you doing,' "And then provide that as a layer." So I think that's really where supercloud is going, 'cause I think that's what a lot of the market actually wants in terms of where they want to run their workloads, because we're seeing that they want to run workloads at the edge, "a lot closer to me," which is yet another factor that we have to consider, and how are you going to be moving individual workloads around? That's the holy grail. Let's move individual workloads to where they're the best performance, the security, cost optimized, and then one layer up. >> Yeah, I think so- >> John Considine, who ultimately ran CloudSwitch, that sold to Verizon, as well as Tom Gillis, who built Bracket, are both rolling in their graves, 'cause what you just described was exactly that. (Lori laughing) Well, they're not even dead yet, so I can't say they're rolling in their graves. Sorry, Tom. Sorry, John. >> Well, how do hyperscalers keep their advantage with all this? I mean, to that point. >> Native services and managed services on top of it. Look how many flavors of managed Kubernetes you have. So you have a choice. Roll your own, or go with a managed service, and then differentiate based on the ability to take away and simplify some of that complexity. Doesn't mean it's more secure necessarily, but I do think we're seeing opportunities where those guys are fighting tooth and nail to keep you on a singular cloud, even though, to Lori's point, I agree, I don't think it's about standardized APIs, 'cause I think that's never going to happen. I do think, though, that SaaS-y supercloud model that we were talking about, layering SaaS that happens to span all the three infrastructure of the service are probably more in line with what Lori was talking about. But I do think that portability of workload is given to you today within lots of ways. But again, how much do you manage, and how much performance do you give up by running additional abstraction layers? And how much security do you give up by having to roll your own and manage that? Because the whole point was, in many cases... Cloud is using other people's computers, so in many cases, I want to manage as little of it as I possibly can. >> I like this whole SaaS angle, because if you had the old days, you're on Amazon Web Services, hey, if you build a SaaS application that runs on Amazon, you're all great, you're born in the cloud, just like that generations of startups. Great. Now when you have this super pass layer, as Dave Vellante was riffing on his analysis, and Lori, you were getting into this pass layer that's kind of like SaaS-y, what's the SaaS equation look like? Because that, to me, sounds like a supercloud version of saying, "I have a workload that runs on all the clouds equally." I just don't think that's ever going to happen. I agree with you, Chris, on that one. But I do see that you can have an abstraction that says, "Hey, I don't really want to get in the weeds. "I don't want to spend a lot of ops time on this. "I just want it to run effectively, and magic happens," or, as you said, some layer there. How does that work? How do you see this super pass layer, if anything, enabling a different SaaS game? >> I think you hit on it there. The last like 10 or so years, we've been all focused on developers and developer productivity, and it's all about the developer experience, and it's got to be good for them, 'cause they're the kings. And I think the next 10 years are going to be very focused on operations, because once you start scaling out, it's not about developers. They can deliver fast or slow, it doesn't matter, but if you can't scale it out, then you've got a real problem. So I think that's an important part of it, is really, what is the ops experience, and what is the best way to get those costs down? And this would serve that purpose if it was done right, which, we can argue about whether that's possible or not, but I don't have to implement it, so I can say it's possible. >> Well, are we going to be getting into infrastructure as code moves into "everything is code," security, data, (laughs) applications is code? I mean, "blank" is code, fill in the blank. (Lori laughing) >> Yeah, we're seeing more of that with things like CDK and Pulumi, where you are actually coding up using a real language rather than the death by YAML or whatever. How much YAML can you take? But actually having a real language so you're not trying to do things in parsing languages. So I think that's an interesting trend. You're getting some interesting templates, and I like what... I mean, the counterexample is that if you just go deep on one vendor, then maybe you can go faster and it is simpler. And one of my favorite vendor... Favorite customers right now that I've been talking to is Liberty Mutual. Went very deep and serverless first on AWS. They're just doing everything there, and they're using CDK Patterns to do it, and they're going extremely fast. There's a book coming out called "The Value Flywheel" by Dave Anderson, it's coming out in a few months, to just detail what they're doing, but that's the counterargument. If you could pick one vendor, you can go faster, you can get that vendor to do more for you, and maybe get a bigger discount so you're not splitting your discounts across vendors. So that's one aspect of it. But I think, fundamentally, you're going to find the CIOs and the ops people generally don't like sitting on one vendor. And if that single vendor is a horizontal platform that's trying to make all the clouds look the same, now you're locked into whatever that platform was. You've still got a platform there. There's still something. So I think that's always going to be something that the CIOs want, but the developers are always going to just pick whatever the best tool for building the thing is. And a analogy here is that the developers are dating and getting married, and then the operations people are running the family and getting divorced. And all the bad parts of that cycle are in the divorce end of it. You're trying to get out of a vendor, there's lawyers, it's just a big mess. >> Who's the lawyer in this example? (crosstalk) >> Well... (laughing) >> Great example. (crosstalk) >> That's why ops people don't like lock-in, because they're the ones trying to unlock. They aren't the ones doing the lock-in. They're the ones unlocking, when developers, if you separate the two, are the ones who are going, picking, having the fun part of it, going, trying a new thing. So they're chasing a shiny object, and then the ops people are trying to untangle themselves from the remains of that shiny object a few years later. So- >> Aren't we- >> One way of fixing that is to push it all together and make it more DevOps-y. >> Yeah, that's right. >> But that's trying to put all the responsibilities in one place, like more continuous improvement, but... >> Chris, what's your reaction to that? Because you're- >> No, that's exactly what I was going to bring up, yeah, John. And 'cause we keep saying "devs," "dev," and "ops" and I've heard somewhere you can glue those two things together. Heck, you could even include "sec" in the middle of it, and "DevSecOps." So what's interesting about what Adrian's saying though, too, is I think this has a lot to do with how you structure your engineering teams and how you think about development versus operations and security. So I'm building out a team now that very much makes use of, thanks to my brilliant VP of Engineering, a "Team Topologies" approach, which is a very streamlined and product oriented way of thinking about, for example, in engineering, if you think about team structures, you might have people that build the front end, build the middle tier, and the back end, and then you have a product that needs to make use of all three components in some form. So just from getting stuff done, their ability then has to tie to three different groups, versus building a team that's streamlined that ends up having front end, middleware, and backend folks that understand and share standards but are able to uncork the velocity that's required to do that. So if you think about that, and not just from an engineering development perspective, but then you couple in operations as a foundational layer that services them with embedded capabilities, we're putting engineers and operations teams embedded in those streamlined teams so that they can run at the velocity that they need to, they can do continuous integration, they can do continuous deployment. And then we added CS, which is continuously secure, continuous security. So instead of having giant, centralized teams, we're thinking there's a core team, for example, a foundational team, that services platform, makes sure all the trains are running on time, that we're doing what we need to do foundationally to make the environments fully dev and operator and security people functional. But then ultimately, we don't have these big, monolithic teams that get into turf wars. So, to Adrian's point about, the operators don't like to be paned in, well, they actually have a say, ultimately, in how they architect, deploy, manage, plan, build, and operate those systems. But at the same point in time, we're all looking at that problem across those teams and go... Like if one streamline team says, "I really want to go run on Azure, "because I like their services better," the reality is the foundational team has a larger vote versus opinion on whether or not, functionally, we can satisfy all of the requirements of the other team. Now, they may make a fantastic business case and we play rock, paper, scissors, and we do that. Right now, that hasn't really happened. We look at the balance of AWS, we are picking SaaS-y, supercloud vendors that will, by the way, happen to run on three platforms, if we so choose to expand there. So we have a similar interface, similar capability, similar processes, but we've made the choice at LastPass to go all in on AWS currently, with respect to how we deliver our products, for all the reasons we just talked about. But I do think that operations model and how you build your teams is extremely important. >> Yeah, and to that point- >> And has the- (crosstalk) >> The vendors themselves need optionality to the customer, what you're saying. So, "I'm going to go fast, "but I need to have that optionality." I guess the question I have for you guys is, what is today's trade-off? So if the decision point today is... First of all, I love the go-fast model on one cloud. I think that's my favorite when I look at all this, and then with the option, knowing that I'm going to have the option to go to multiple clouds. But everybody wants lock-in on the vendor side. Is that scale, is that data advantage? I mean, so the lock-in's a good question, and then also the trade-offs. What do people have to do today to go on a supercloud journey to have an ideal architecture and taxonomy, and what's the right trade-offs today? >> I think that the- Sorry, just put a comment and then let Lori get a word in, but there's a lot of... A lot of the market here is you're building a product, and that product is a SaaS product, and it needs to run somewhere. And the customers that you're going to... To get the full market, you need to go across multiple suppliers, most people doing AWS and Azure, and then with Google occasionally for some people. But that, I think, has become the pattern that most of the large SaaS platforms that you'd want to build out of, 'cause that's the fast way of getting something that's going to be stable at scale, it's got functionality, you'd have to go invest in building it and running it. Those platforms are just multi-cloud platforms, they're running across them. So Snowflake, for example, has to figure out how to make their stuff work on more than one cloud. I mean, they started on one, but they're going across clouds. And I think that that is just the way it's going to be, because you're not going to get a broad enough view into the market, because there isn't a single... AWS doesn't have 100% of the market. It's maybe a bit more than them, but Azure has got a pretty solid set of markets where it is strong, and it's market by market. So in some areas, different people in some places in the world, and different vertical markets, you'll find different preferences. And if you want to be across all of them with your data product, or whatever your SaaS product is, you're just going to have to figure this out. So in some sense, the supercloud story plays best with those SaaS providers like the Snowflakes of this world, I think. >> Lori? >> Yeah, I think the SaaS product... Identity, whatever, you're going to have specialized. SaaS, superclouds. We already see that emerging. Identity is becoming like this big SaaS play that crosses all clouds. It's not just for one. So you get an evolution going on where, yes, I mean, every vendor who provides some kind of specific functionality is going to have to build out and be multi-cloud, as it were. It's got to work equally across them. And the challenge, then, for them is to make it simple for both operators and, if required, dev. And maybe that's the other lesson moving forward. You can build something that is heaven for ops, but if the developers won't use it, well, then you're not going to get it adopted. But if you make it heaven for the developers, the ops team may not be able to keep it secure, keep everything. So maybe we have to start focusing on both, make it friendly for both, at least. Maybe it won't be the perfect experience, but gee, at least make it usable for both sides of the equation so that everyone can actually work in concert, like Chris was saying. A more comprehensive, cohesive approach to delivery and deployment. >> All right, well, wrapping up here, I want to just get one final comment from you guys, if you don't mind. What does supercloud look like in five years? What's the Nirvana, what's the steady state of supercloud in five to 10 years? Or say 10 years, make it easier. (crosstalk) Five to 10 years. Chris, we'll start with you. >> Wow. >> Supercloud, what's it look like? >> Geez. A magic pane, a single pane of glass. (laughs) >> Yeah, I think- >> Single glass of pain. >> Yeah, a single glass of pain. Thank you. You stole my line. Well, not mine, but that's the one I was going to use. Yeah, I think what is really fascinating is ultimately, to answer that question, I would reflect on market consolidation and market dynamics that happens even in the SaaS space. So we will see SaaS companies combining in focal areas to be able to leverage the positions, let's say, in the identity space that somebody has built to provide a set of compelling services that help abstract that identity problem or that security problem or that instrumentation and observability problem. So take your favorite vendors today. I think what we'll end up seeing is more consolidation in SaaS offerings that run on top of infrastructure of the service offerings to where a supercloud might look like something I described before. You have the combination of your favorite interoperable identity, observability, security, orchestration platforms run across them. They're sold as a stack, whether it be co-branded by an enterprise vendor that sells all of that and manages it for you or not. But I do think that... You talked about, I think you said, "Is this an innovator's dilemma?" No, I think it's an integrator's dilemma, as it has always ultimately been. As soon as you get from Genesis to Bespoke Build to product to then commoditization, the cycle starts anew. And I think we've gotten past commoditization, and we're looking at niche areas. So I see just the evolution, not necessarily a revolution, of what we're dealing with today as we see more consolidation in the marketplace. >> Lori, what's your take? Five years, 10 years, what does supercloud look like? >> Part of me wants to take the pie in the sky unicorn approach. "No, it will be beautiful. "One button, and things will happen," but I've seen this cycle many times before, and that's not going to happen. And I think Chris has got it pretty close to what I see already evolving. Those different kinds of super services, basically. And that's really what we're talking about. We call them SaaS, but they're... X is a service. Everything is a service, and it's really a supercloud that can run anywhere, but it presents a different interface, because, well, it's easier. And I think that's where we're going to go, and that's just going to get more refined. And yes, a lot of consolidation, especially on the observability side, but that's also starting to consume the security side, which is really interesting to watch. So that could be a little different supercloud coming on there that's really focused on specific types of security, at least, that we'll layer across, and then we'll just hook them all together. It's an API first world, and it seems like that's going to be our standard for the next while of how we integrate everything. So superclouds or APIs. >> Awesome. Adrian... Adrian, take us home. >> Yeah, sure. >> What's your- I think, and just picking up on Lori's point that these are web services, meaning that you can just call them from anywhere, they don't have to run everything in one place, they can stitch it together, and that's really meant... It's somewhat composable. So in practice, people are going to be composable. Can they compose their applications on multiple platforms? But I think the interesting thing here is what the vendors do, and what I'm seeing is vendors running software on other vendors. So you have Google building platforms that, then, they will support on AWS and Azure and vice versa. You've got AWS's distro of Kubernetes, which they now give you as a distro so you can run it on another platform. So I think that trend's going to continue, and it's going to be, possibly, you pick, say, an AWS or a Google software stack, but you don't run it all on AWS, you run it in multiple places. Yeah, and then the other thing is the third tier, second, third tier vendors, like, I mean, what's IBM doing? I think in five years time, IBM is going to be a SaaS vendor running on the other clouds. I mean, they're already halfway there. To be a bit more controversial, I guess it's always fun to... Like I don't work for a corporate entity now. No one tells me what I can say. >> Bring it on. >> How long can Google keep losing a billion dollars a quarter? They've either got to figure out how to make money out of this thing, or they'll end up basically being a software stack on another cloud platform as their, likely, actual way they can make money on it. Because you've got to... And maybe Oracle, is that a viable cloud platform that... You've got to get to some level of viability. And I think the second, third tier of vendors in five, 10 years are going to be running on the primary platform. And I think, just the other final thing that's really driving this right now. If you try and place an order right now for a piece of equipment for your data center, key pieces of equipment are a year out. It's like trying to buy a new fridge from like Sub-Zero or something like that. And it's like, it's a year. You got to wait for these things. Any high quality piece of equipment. So you go to deploy in your data center, and it's like, "I can't get stuff in my data center. "Like, the key pieces I need, I can't deploy a whole system. "We didn't get bits and pieces of it." So people are going to be cobbling together, or they're going, "No, this is going to cloud, because the cloud vendors "have a much stronger supply chain to just be able "to give you the system you need. "They've got the capacity." So I think we're going to see some pandemic and supply chain induced forced cloud migrations, just because you can't build stuff anymore outside the- >> We got to accelerate supercloud, 'cause they have the supply. They are the chain. >> That's super smart. That's the benefit of going last. So I'm going to scoop in real quick. I can't believe we can call this "Web3 Supercloud," because none of us said "Web3." Don't forget DAO. (crosstalk) (indistinct) You have blockchain, blockchain superclouds. I mean, there's some very interesting distributed computing stuff there, but we'll have to do- >> (crosstalk) We're going to call that the "Cubeverse." The "Cubeverse" is coming. >> Oh, the "Cubeverse." All right. >> We will be... >> That's very meta. >> In the metaverse, Cubeverse soon. >> "Stupor cloud," perhaps. But anyway, great points, Adrian and Lori. Loved it. >> Chris, great to see you. Adrian, Lori, thanks for coming on. We've known each other for a long time. You guys are part of the cloud-erati, the group that has been in there from day one, and watched it evolve, and you get the scar tissue to prove it, and the experience. So thank you so much for sharing your commentary. We'll roll this up and make it open to everybody as additional content. We'll call this the "outtakes," the longer version. But really appreciate your time, thank you. >> Thank you. >> Thanks so much. >> Okay, we'll be back with more "Supercloud 22" right after this. (bright upbeat music)

>>Hello, everyone. Welcome to the cubes coverage here. New York city for AWS Amazon web services summit 2022. I'm John furrier, host of the cube with Dave ante. My co-host. We are breaking it down, getting an update on the ecosystem. As the GDP drops, inflations up gas prices up the enterprise continues to grow. We're seeing exceptional growth. We're here on the ground floor. Live at the Summit's packed house, 10,000 people. Eric Bradley's here. Chief STR at ETR, one of the premier enterprise research firms out there, partners with the cube and powers are breaking analysis that Dave does check that out as the hottest podcast in enterprise. Eric. Great to have you on the cube. Thanks for coming on. >>Thank you so much, John. I really appreciate the collaboration always. >>Yeah. Great stuff. Your data's amazing ETR folks watching check out ETR. They have a unique formula, very accurate. We love it. It's been moving the market. Congratulations. Let's talk about the market right now. This market is booming. Enterprise is the hottest thing, consumers kind of in the toilet. Okay. I said that all right, back out devices and, and, and consumer enterprise is still growing. And by the way, this first downturn, the history of the world where hyperscalers are on full pumping on all cylinders, which means they're still powering the revolution. >>Yeah, it's true. The hyperscalers were basically at this two sun system when Microsoft and an AWS first came around and everything was orbiting around it. And we're starting to see that sun cool off a little bit, but we're talking about a gradient here, right? When we say cool off, we're not talking to shutdown, it's still burning hot. That's for sure. And I can get it to some of the macro data in a minute, if that's all right. Or do you want me to go right? No, go go. Right. Yeah. So right now we just closed our most recent survey and that's macro and vendor specific. We had 1200 people talk to us on the macro side. And what we're seeing here is a cool down in spending. We originally had about 8.5% increase in budgets. That's cool down is 6.5 now, but I'll say with the doom and gloom and the headlines that we're seeing every day, 6.5% growth coming off of what we just did the last couple of years is still pretty fantastic as a backdrop. >>Okay. So you, you started to see John mentioned consumer. We saw that in Snowflake's earnings. For example, we, we certainly saw, you know, Walmart, other retailers, the FA Facebooks of the world where consumption was being dialed down, certain snowflake customers. Not necessarily, they didn't have mentioned any customers, but they were able to say, all right, we're gonna dial down, consumption this quarter, hold on until we saw some of that in snowflake results and other results. But at the same time, the rest of the industry is booming. But your data is showing softness within the fortune 500 for AWS, >>Not only AWS, but fortune 500 across the board. Okay. So going back to that larger macro data, the biggest drop in spending that we captured is fortune 500, which is surprising. But at the same time, these companies have a better purview into the economy. In general, they tend to see things further in advance. And we often remember they spend a lot of money, so they don't need to play catch up. They'll easily more easily be able to pump the brakes a little bit in the fortune 500. But to your point, when we get into the AWS data, the fortune 500 decrease seems to be hitting them a little bit more than it is Azure and GCP. I >>Mean, we're still talking about a huge business, right? >>I mean, they're catching up. I mean, Amazon has been transforming from owning the developer cloud startup cloud decade ago to really putting a dent on the enterprise as being number one cloud. And I still contest that they're number one by a long ways, but Azure kicking ass and catching up. Okay. You seeing people move to Azure, you got Charlie bell over there, Sean, by former Amazonians, Theresa Carlson, people are going over there, there there's lift over at Azure. >>There certainly is. >>Is there kinks in the arm or for AWS? There's >>A couple of kinks, but I think your point is really good. We need to take a second there. If you're talking about true pass or infrastructure is a service true cloud compute. I think AWS still is the powerhouse. And a lot of times the, the data gets a little muddied because Azure is really a hosted platform for applications. And you're not really sure where that line is drawn. And I think that's an important caveat to make, but based on the data, yes, we are seeing some kinks in the armor for AWS. Yes. Explain. So right now, a first of all caveat, 40% net score, which is our proprietary spending metric across the board. So we're not like raising any alarms here. It's still strong that said there are declines and there are declines pretty much across the board. The only spot we're not seeing a decline at all is in container, spend everything else is coming down specifically. We're seeing it come down in data analytics, data warehousing, and M I, which is a little bit of a concern because that, that rate of decline is not the same with Azure. >>Okay. So I gotta ask macro, I see the headwinds on the macro side, you pointed that out. Is there any insight into any underlying conditions that might be there on AWS or just a chronic kind of situational thing >>Right now? It seems situational. Other than that correlation between their big fortune 500, you know, audience and that being our biggest decline. The other aspect of the macro survey is we ask people, if you are planning to decline spend, how do you plan on doing it? And the number two answer is taking a look at our cloud spend and auditing it. So they're kind say, all right, you know, for the last 10 years it's been drunken, sail or spend, I >>Was gonna use that same line, you know, >>Cloud spend, just spend and we'll figure it out later, who cares? And then right now it's time to tighten the belts a little bit, >>But this is part of the allure of cloud at some point. Yeah. You, you could say, I'm gonna, I'm gonna dial it down. I'm gonna rein it in. So that's part of the reason why people go to the cloud. I want to, I wanna focus in on the data side of things and specifically the database. Let, just to give some context if, and correct me if I'm, I'm a little off here, but snowflake, which hot company, you know, on the planet, their net score was up around 80% consistently. It it's dropped down the last, you know, quarter, last survey to 60%. Yeah. So still highly, highly elevated, but that's relative to where Amazon is much larger, but you're saying they're coming down to the 40% level. Is that right? >>Yeah, they are. And I remember, you know, when I first started doing this 10 years ago, AWS at a 70%, you know, net score as well. So what's gonna happen over time is those adoptions are gonna get less and you're gonna see more flattening of spend, which ultimately is going to lower the score because we're looking for expansion rates. We wanna see adoption and increase. And when you see flattening a spend, it starts to contract a little bit. And you're right. Snowflake also was in the stratosphere that cooled off a little bit, but still, you know, very strong and AWS is coming down. I think the reason why it's so concerning is because a it's within the fortune 500 and their rate of decline is more than Azure right >>Now. Well, and, and one of the big trends you're seeing in database is this idea of converging function. In other words, bringing transaction and analytics right together at snowflake summit, they added the capability to handle transaction data, Mongo DB, which is largely mostly transactions added the capability in June to bring in analytic data. You see data bricks going from data engineering and data science now getting into snowflake space and analytics. So you're seeing that convergence Oracle is converging with my SQL heat wave and their core databases, couch base couch base is doing the same. Maria do virtually all these database companies are, are converging their platforms with the exception of AWS. AWS is still the right tool for the right job. So they've got Aurora, they've got RDS, they've got, you know, a dynamo DV, they've got red, they've got, you know, going on and on and on. And so the question everybody's asking is will that change? Will they start to sort of cross those swim lanes? We haven't seen it thus far. How is that affecting the data >>Performance? I mean, that's fantastic analysis. I think that's why we're seeing it because you have to be in the AWS ecosystem and they're really not playing nicely with others in the sandbox right now that now I will say, oh, Amazon's not playing nicely. Well, no, no. Simply to your point though, that there, the other ones are actually bringing in others at consolidating other different vendor types. And they're really not. You know, if you're in AWS, you need to stay within AWS. Now I will say their tools are fantastic. So if you do stay within AWS, they have a tool for every job they're advanced. And they're incredible. I think sometimes the complexity of their tools hurts them a little bit. Cause to your point earlier, AWS started as a developer-centric type of cloud. They have moved on to enterprise cloud and it's a little bit more business oriented, but their still roots are still DevOps friendly. And unless you're truly trained, AWS can be a little scary. >>So a common use case is I'm gonna be using Aurora for my transaction system and then I'm gonna ETL it into Redshift. Right. And, and I, now I have two data stores and I have two different sets of APIs and primitives two different teams of skills. And so that is probably causing some friction and complexity in the customer base that again, the question is, will they begin to expand some of those platforms to minimize some of that friction? >>Well, yeah, this is the question I wanted to ask on that point. So I've heard from people inside Amazon don't count out Redshift, we're making, we're catching up. I think that's my word, but they were kind of saying that right. Cuz Redshift is good, good database, but they're adding a lot more. So you got snowflake success. I think it's a little bit of a jealousy factor going on there within Redshift team, but then you got Azure synapse with the Synap product synapse. Yep. And then you got big query from Google big >>Query. Yep. >>What's the differentiation. What are you seeing for the data for the data warehouse or the data clouds that are out there for the customers? What's the data say, say to us? >>Yeah, unfortunately the data's showing that they're dropping a little bit whose day AWS is dropping a little bit now of their data products, Redshift and RDS are still the two highest of them, but they are starting to decline. Now I think one of the great data points that we have, we just closed the survey is we took a comparison of the legacy data. Now please forgive me for the word legacy. We're gonna anger a few people, but we Gotter data Oracle on-prem, we've got IBM. Some of those more legacy data warehouse type of names. When we look at our art survey takers that have them where their spend is going, that spends going to snowflake first, and then it's going to Google and then it's going to Microsoft Azure and, and AWS is actually declining in there. So when you talk about who's taking that legacy market share, it's not AWS right now. >>So legacy goes to legacy. So Microsoft, >>So, so let's work through in a little context because Redshift really was the first to take, you know, take the database to the cloud. And they did that by doing a one time license deal with par XL, which was an on-prem database. And then they re-engineered it, they did a fantastic job, but it was still engineered for on-prem. Then you along comes snowflake a couple years later and true cloud native, same thing with big query. Yep. True cloud native architecture. So they get a lot of props. Now what, what Amazon did, they took a page outta of the snowflake, for example, separating compute from storage. Now of course what's what, what Amazon did is actually not really completely separating like snowflake did they couldn't because of the architecture, they created a tearing system that you could dial down the compute. So little nuances like that. I understand. But at the end of the day, what we're seeing from snowflake is the gathering of an ecosystem in this true data cloud, bringing in different data types, they got to the public markets, data bricks was not able to get to the public markets. Yeah. And think is, is struggling >>And a 25 billion evaluation. >>Right. And so that's, that's gonna be dialed down, struggling somewhat from a go to market standpoint where snowflake has no troubles from a go to market. They are the masters at go to market. And so now they've got momentum. We talked to Frank sluman at the snowflake. He basically said, I'm not taking the foot off the gas, no way. Yeah. We, few of our large, you know, consumer customers dialed things down, but we're going balls to the >>Wall. Well, if you look at their show before you get in the numbers, you look at the two shows. Snowflake had their summit in person in Vegas. Data bricks has had their show in San Francisco. And if you compare the two shows, it's clear, who's winning snowflake is blew away from a, from a market standpoint. And we were at snowflake, but we weren't at data bricks, but there was really nothing online. I heard from sources that it was like less than 3000 people. So >>Snowflake was 1900 people in 2019, nearly 10,000. Yeah. In 2020, >>It's gonna be fun to sort of track that as a, as an odd caveat to say, okay, let's see what that growth is. Because in fairness, data, bricks, you know, a little bit younger, Snowflake's had a couple more years. So I'd be curious to see where they are. Their, their Lakehouse paradigm is interesting. >>Yeah. And I think it's >>And their product first company, yes. Their go to market might be a little bit weak from our analysis, but that, but they'll figure it out. >>CEO's pretty smart. But I think it's worth pointing out. It's like two different philosophies, right? It is. Snowflake is come into our data cloud. That's their proprietary environment. They're the, they think of the iPhone, right? End to end. We, we guarantee it's all gonna work. And we're in control. Snowflake is like, Hey, open source, no, bring in data bricks. I mean data bricks, open source, bring in this tool that too, now you are seeing snowflake capitulate a little bit. They announce, for instance, Apache iceberg support at their, at the snowflake summit. So they're tipping their cap to open source. But at the end of the day, they're gonna market and sell the fact that it's gonna run better in native snowflake. Whereas data bricks, they're coming at it from much more of an open source, a mantra. So that's gonna, you know, we'll see who look at, you had windows and you had apple, >>You got, they both want, you got Cal and you got Stanford. >>They both >>Consider, I don't think it's actually there yet. I, I find the more interesting dynamic right now is between AWS and snowflake. It's really a fun tit for tat, right? I mean, AWS has the S three and then, you know, snowflake comes right on top of it and announces R two, we're gonna do one letter, one number better than you. They just seem to have this really interesting dynamic. And I, and it is SLT and no one's betting against him. I mean, this guy's fantastic. So, and he hasn't used his war chest yet. He's still sitting on all that money that he raised to your point, that data bricks five, their timing just was a little off >>5 billion in >>Capital when Slootman hasn't used that money yet. So what's he gonna do? What can he do when he turns that on? He finds the right. >>They're making some acquisitions. They did the stream lit acquisitions stream. >>Fantastic >>Problem. With data bricks, their valuation is underwater. Yes. So they're recruiting and their MNAs. Yes. In the toilet, they cannot make the moves because they don't have the currency until they refactor the multiple, let the, this market settle. I I'm, I'm really nervous that they have to over factor the >>Valuation. Having said that to your point, Eric, the lake house architecture is definitely gaining traction. When you talk to practitioners, they're all saying, yeah, we're building data lakes, we're building lake houses. You know, it's a much, much smaller market than the enterprise data warehouse. But nonetheless, when you talk to practitioners that are actually doing things like self serve data, they're building data lakes and you know, snow. I mean, data bricks is right there. And as a clear leader in, in ML and AI and they're ahead of snowflake, right. >>And I was gonna say, that's the thing with data bricks. You know, you're getting that analytics at M I built into it. >>You know, what's ironic is I remember talking to Matt Carroll, who's CEO of auDA like four or five years ago. He came into the office in ma bro. And we were in temporary space and we were talking about how there's this new workload emerging, which combines AWS for cloud infrastructure, snowflake for the simple data warehouse and data bricks for the ML AI, and then all now all of a sudden you see data bricks yeah. And snowflake going at it. I think, you know, to your point about the competition between AWS and snowflake, here's what I think, I think the Redshift team is, you know, doesn't like snowflake, right. But I think the EC two team loves it. Loves it. Exactly. So, so I think snowflake is driving a lot of, >>Yeah. To John's point, there is plenty to go around. And I think I saw just the other day, I saw somebody say less than 40% of true global 2000 organizations believe that they're at real time data analytics right now. They're not really there yet. Yeah. Think about how much runway is left and how many tools you need to get to real time streaming use cases. It's complex. It's not easy. >>It's gonna be a product value market to me, snowflake in data bricks. They're not going away. Right. They're winning architectures. Yeah. In the cloud, what data bricks did would spark and took over the Haddo market. Yeah. To your point. Now that big data, market's got two players, in my opinion, snow flicking data, bricks converging. Well, Redshift is sitting there behind the curtain, their wild card. Yeah. They're wild card, Dave. >>Okay. I'm gonna give one more wild card, which is the edge. Sure. Okay. And that's something that when you talk about real time analytics and AI referencing at the edge, there aren't a lot of database companies in a position to do that. You know, Amazon trying to put outposts out there. I think it runs RDS. I don't think it runs any other database. Right. Snowflake really doesn't have a strong edge strategy when I'm talking the far edge, the tiny edge. >>I think, I think that's gonna be HPE or Dell's gonna own the outpost market. >>I think you're right. I'll come back to that. Couch base is an interesting company to watch with Capella Mongo. DB really doesn't have a far edge strategy at this point, but couch base does. And that's one to watch. They're doing some really interesting things there. And I think >>That, but they have to leapfrog bongo in my >>Opinion. Yeah. But there's a new architecture emerging at the edge and it's gonna take a number of years to develop, but it could eventually from an economic standpoint, seep back into the enterprise arm base, low end, take a look at what couch base is >>Doing. They hired an Amazon guard system. They have to leapfrog though. They need to, they can't incrementally who's they who >>Couch >>Base needs to needs to make a big move in >>Leap frog. Well, think they're trying to, that's what Capella is all about was not only, you know, their version of Atlas bringing to the cloud couch base, but it's also stretching it out to the edge and bringing converged database analytics >>Real quick on the numbers. Any data on CloudFlare, >>I was, I've been sitting here trying to get the word CloudFlare out my mouth the whole time you guys were talking, >>Is this another that's innovated in the ecosystem. So >>Platform, it was really simple for them early on, right? They're gonna get that edge network out there and they're gonna steal share from Akamai. Then they started doing exactly what Akamai did. We're gonna start rolling out some security. Their security is fantastic. Maybe some practitioners are saying a little bit too much, cuz they're not focused on one thing or another, but they are doing extremely well. And now they're out there in the cloud as well. You >>Got S3 compare. They got two, they got an S3 competitor. >>Exactly. So when I'm listening to you guys talk about, you know, a, a couch base I'm like, wow, those two would just be an absolute fantastic, you know, combination between the two of them. You mean >>CloudFlare >>Couch base. Yeah. >>I mean you got S3 alternative, right? You got a Mongo alternative basically in my >>Opinion. And you're going and you got the edge and you got the edge >>Network with security security, interesting dynamic. This brings up the super cloud date. I wanna talk about Supercloud because we're seeing a trend on we're reporting this since last year that basically people don't have to spend the CapEx to be cloud scale. And you're seeing Amazon enable that, but snowflake has become a super cloud. They're on AWS. Now they're on Azure. Why not tan expansion expand the market? Why not get that? And then it'll be on Google next, all these marketplaces. So the emergence of this super cloud, and then the ability to make that across a substrate across multiple clouds is a strategy we're seeing. What do you, what do you think? >>Well, honestly, I'm gonna be really Frank here. The, everything I know about the super cloud I know from this guy. So I've been following his lead on this and I'm looking forward to you guys doing that conference and that summit coming up from a data perspective. I think what you're saying is spot on though, cuz those are the areas we're seeing expansion in without a doubt. >>I think, you know, when you talk about things like super cloud and you talk about things like metaverse, there's, there's a, there, there look every 15 or 20 years or so this industry reinvents itself and a new disruption comes out and you've got the internet, you've got the cloud, you've got an AI and VR layer. You've got, you've got machine intelligence. You've got now gaming. There's a new matrix, emerging, super cloud. Metaverse there's something happening out there here. That's not just your, your father's SAS or is or pass. Well, >>No, it's also the spend too. Right? So if I'm a company like say capital one or Goldman Sachs, my it spend has traditionally been massive every year. Yes. It's basically like tons of CapEx comes the cloud. It's an operating expense. Wait a minute, Amazon has all the CapEx. So I'm not gonna dial down my budget. I want a competitive advantage. So next thing they know they have a super cloud by default because they just pivoted their, it spend into new capabilities that they then can sell to the market in FinTech makes total sense. >>Right? They're building out a digital platform >>That would, that was not possible. Pre-cloud >>No, it wasn't cause you weren't gonna go put all that money into CapEx expenditure to build that out. Not knowing whether or not the market was there, but the scalability, the ability to spend, reduce and be flexible with it really changes that paradigm entire. >>So we're looking at this market now thinking about, okay, it might be Greenfield in every vertical. It might have a power law where you have a head of the long tail. That's a player like a capital one, an insurance. It could be Liberty mutual or mass mutual that has so much it and capital that they're now gonna scale it into a super cloud >>And they have data >>And they have the data tools >>And the tools. And they're gonna bring that to their constituents. Yes, yes. And scale it using >>Cloud. So that means they can then service the entire vertical as a service provider. >>And the industry cloud is becoming bigger and bigger and bigger. I mean, that's really a way that people are delivering to market. So >>Remember in the early days of cloud, all the banks thought they could build their own cloud. Yeah. Yep. Well actually it's come full circle. They're like, we can actually build a cloud on top of the cloud. >>Right. And by the way, they can have a private cloud in their super cloud. Exactly. >>And you know, it's interesting cause we're talking about financial services insurance, all the people we know spend money in our macro survey. Do you know the, the sector that's spending the most right now? It's gonna shock you energy utilities. Oh yeah. I was gonna, the energy utilities industry right now is the one spending the most money I saw largely cuz they're playing ketchup. But also because they don't have these type of things for their consumers, they need the consumer app. They need to be able to do that delivery. They need to be able to do metrics. And they're the they're, they're the one spending right >>Now it's an arms race, but the, the vector shifts to value creation. So >>It's it just goes back to your post when it was a 2012, the trillion dollar baby. Yeah. It's a multi-trillion dollar baby that they, >>The world was going my chassis post on Forbes, headline trillion dollar baby 2012. You know, I should add it's happening. That's >>On the end. Yeah, exactly. >>Trillions of babies, Eric. Great to have you on the key. >>Thank you so much guys. >>Great to bring the data. Thanks for sharing. Check out ETR. If you're into the enterprise, want to know what's going on. They have a unique approach, very accurate in their survey data. They got a great market basket of, of, of, of, of data questions and people and community. Check it out. Thanks for coming on and sharing with. >>Thank you guys. Always enjoy. >>We'll be back with more coverage here in the cube in New York city live at summit 22. I'm John fur with Dave ante. We'll be right back.

>> From the theCUBE studios in Palo Alto in Boston, bringing you data driven insights from theCUBE and ETR. This is "Breaking Analysis" with Dave Vellante. >> Welcome to this week's Wikibon, theCUBE's insights powered by ETR. As we exited the isolation economy last year, supercloud is a term that we introduced to describe something new that was happening in the world of cloud. In this Breaking Analysis, we address the 10 most frequently asked questions we get around supercloud. Okay, let's review these frequently asked questions on supercloud that we're going to try to answer today. Look at an industry that's full of hype and buzzwords. Why the hell does anyone need a new term? Aren't hyperscalers building out superclouds? We'll try to answer why the term supercloud connotes something different from hyperscale clouds. And we'll talk about the problems that superclouds solve specifically. And we'll further define the critical aspects of a supercloud architecture. We often get asked, isn't this just multi-cloud? Well, we don't think so, and we'll explain why in this Breaking Analysis. Now in an earlier episode, we introduced the notion of super PaaS. Well, isn't a plain vanilla PaaS already a super PaaS? Again, we don't think so, and we'll explain why. Who will actually build and who are the players currently building superclouds? What workloads and services will run on superclouds? And 8-A or number nine, what are some examples that we can share of supercloud? And finally, we'll answer what you can expect next from us on supercloud? Okay, let's get started. Why do we need another buzzword? Well, late last year, ahead of re:Invent, we were inspired by a post from Jerry Chen called "Castles in the Cloud." Now in that blog post, he introduced the idea that there were sub-markets emerging in cloud that presented opportunities for investors and entrepreneurs that the cloud wasn't going to suck the hyperscalers. Weren't going to suck all the value out of the industry. And so we introduced this notion of supercloud to describe what we saw as a value layer emerging above the hyperscalers CAPEX gift, we sometimes call it. Now it turns out, that we weren't the only ones using the term as both Cornell and MIT have used the phrase in somewhat similar, but different contexts. The point is something new was happening in the AWS and other ecosystems. It was more than IaaS and PaaS, and wasn't just SaaS running in the cloud. It was a new architecture that integrates infrastructure, platform and software as services to solve new problems that the cloud vendors in our view, weren't addressing by themselves. It seemed to us that the ecosystem was pursuing opportunities across clouds that went beyond conventional implementations of multi-cloud. And we felt there was a structural change going on at the industry level, the supercloud, metaphorically was highlighting. So that's the background on why we felt a new catch phrase was warranted, love it or hate it. It's memorable and it's what we chose. Now to that last point about structural industry transformation. Andy Rappaport is sometimes and often credited with identifying the shift from the vertically integrated IBM mainframe era to the fragmented PC microprocesor-based era in his HBR article in 1991. In fact, it was David Moschella, who at the time was an IDC Analyst who first introduced the concept in 1987, four years before Rappaport's article was published. Moschella saw that it was clear that Intel, Microsoft, Seagate and others would replace the system vendors, and put that forth in a graphic that looked similar to the first two on this chart. We don't have to review the shift from IBM as the center of the industry to Wintel, that's well understood. What isn't as well known or accepted is what Moschella put out in his 2018 book called "Seeing Digital" which introduced the idea of "The Matrix" that's shown on the right hand side of this chart. Moschella posited that new services were emerging built on top of the internet and hyperscale clouds that would integrate other innovations and would define the next era of computing. He used the term Matrix because the conceptual depiction included not only horizontal technology rose like the cloud and the internet, but for the first time included connected industry verticals, the columns in this chart. Moschella pointed out that whereas historically, industry verticals had a closed value chain or stack and ecosystem of R&D, and production, and manufacturing, and distribution. And if you were in that industry, the expertise within that vertical generally stayed within that vertical and was critical to success. But because of digital and data, for the first time, companies were able to traverse industries, jump across industries and compete because data enabled them to do that. Examples, Amazon and content, payments, groceries, Apple, and payments, and content, and so forth. There are many examples. Data was now this unifying enabler and this marked a change in the structure of the technology landscape. And supercloud is meant to imply more than running in hyperscale clouds, rather it's the combination of multiple technologies enabled by CloudScale with new industry participants from those verticals, financial services and healthcare, manufacturing, energy, media, and virtually all in any industry. Kind of an extension of every company is a software company. Basically, every company now has the opportunity to build their own cloud or supercloud. And we'll come back to that. Let's first address what's different about superclouds relative to hyperscale clouds? You know, this one's pretty straightforward and obvious, I think. Hyperscale clouds, they're walled gardens where they want your data in their cloud and they want to keep you there. Sure, every cloud player realizes that not all data will go to their particular cloud so they're meeting customers where their data lives with initiatives like Amazon Outposts and Azure Arc, and Google Anthos. But at the end of the day, the more homogeneous they can make their environments, the better control, security, cost, and performance they can deliver. The more complex the environment, the more difficult it is to deliver on their brand promises. And of course, the lesser margin that's left for them to capture. Will the hyperscalers get more serious about cross-cloud services? Maybe, but they have plenty of work to do within their own clouds and within enabling their own ecosystems. They had a long way to go a lot of runway. So let's talk about specifically, what problems superclouds solve? We've all seen the stats from IDC or Gartner, or whomever the customers on average use more than one cloud. You know, two clouds, three clouds, five clouds, 20 clouds. And we know these clouds operate in disconnected silos for the most part. And that's a problem because each cloud requires different skills because the development environment is different as is the operating environment. They have different APIs, different primitives, and different management tools that are optimized for each respective hyperscale cloud. Their functions and value props don't extend to their competitors' clouds for the most part. Why would they? As a result, there's friction when moving between different clouds. It's hard to share data, it's hard to move work. It's hard to secure and govern data. It's hard to enforce organizational edicts and policies across these clouds, and on-prem. Supercloud is an architecture designed to create a single environment that enables management of workloads and data across clouds in an effort to take out complexity, accelerate application development, streamline operations and share data safely, irrespective of location. It's pretty straightforward, but non-trivial, which is why I always ask a company's CEO and executives if stock buybacks and dividends will yield as much return as building out superclouds that solve really specific and hard problems, and create differential value. Okay, let's dig a bit more into the architectural aspects of supercloud. In other words, what are the salient attributes of supercloud? So first and foremost, a supercloud runs a set of specific services designed to solve a unique problem and it can do so in more than one cloud. Superclouds leverage the underlying cloud native tooling of a hyperscale cloud, but they're optimized for a specific objective that aligns with the problem that they're trying to solve. For example, supercloud might be optimized for lowest cost or lowest latency, or sharing data, or governing, or securing that data, or higher performance for networking, for example. But the point is, the collection of services that is being delivered is focused on a unique value proposition that is not being delivered by the hyperscalers across clouds. A supercloud abstracts the underlying and siloed primitives of the native PaaS layer from the hyperscale cloud and then using its own specific platform as a service tooling, creates a common experience across clouds for developers and users. And it does so in a most efficient manner, meaning it has the metadata knowledge and management capabilities that can optimize for latency, bandwidth, or recovery, or data sovereignty, or whatever unique value that supercloud is delivering for the specific use case in their domain. And a supercloud comprises a super PaaS capability that allows ecosystem partners through APIs to add incremental value on top of the supercloud platform to fill gaps, accelerate features, and of course innovate. The services can be infrastructure-related, they could be application services, they could be data services, security services, user services, et cetera, designed and packaged to bring unique value to customers. Again, that hyperscalers are not delivering across clouds or on-premises. Okay, so another common question we get is, isn't that just multi-cloud? And what we'd say to that is yes, but no. You can call it multi-cloud 2.0, if you want, if you want to use it, it's kind of a commonly used rubric. But as Dell's Chuck Whitten proclaimed at Dell Technologies World this year, multi-cloud by design, is different than multi-cloud by default. Meaning to date, multi-cloud has largely been a symptom of what we've called multi-vendor or of M&A, you buy a company and they happen to use Google Cloud, and so you bring it in. And when you look at most so-called, multi-cloud implementations, you see things like an on-prem stack, which is wrapped in a container and hosted on a specific cloud or increasingly a technology vendor has done the work of building a cloud native version of their stack and running it on a specific cloud. But historically, it's been a unique experience within each cloud with virtually no connection between the cloud silos. Supercloud sets out to build incremental value across clouds and above hyperscale CAPEX that goes beyond cloud compatibility within each cloud. So if you want to call it multi-cloud 2.0, that's fine, but we chose to call it supercloud. Okay, so at this point you may be asking, well isn't PaaS already a version of supercloud? And again, we would say no, that supercloud and its corresponding superPaaS layer which is a prerequisite, gives the freedom to store, process and manage, and secure, and connect islands of data across a continuum with a common experience across clouds. And the services offered are specific to that supercloud and will vary by each offering. Your OpenShift, for example, can be used to construct a superPaaS, but in and of itself, isn't a superPaaS, it's generic. A superPaaS might be developed to support, for instance, ultra low latency database work. It would unlikely again, taking the OpenShift example, it's unlikely that off-the-shelf OpenShift would be used to develop such a low latency superPaaS layer for ultra low latency database work. The point is supercloud and its inherent superPaaS will be optimized to solve specific problems like that low latency example for distributed databases or fast backup and recovery for data protection, and ransomware, or data sharing, or data governance. Highly specific use cases that the supercloud is designed to solve for. Okay, another question we often get is who has a supercloud today and who's building a supercloud, and who are the contenders? Well, most companies that consider themselves cloud players will, we believe, be building or are building superclouds. Here's a common ETR graphic that we like to show with Net Score or spending momentum on the Y axis and overlap or pervasiveness in the ETR surveys on the X axis. And we've randomly chosen a number of players that we think are in the supercloud mix, and we've included the hyperscalers because they are enablers. Now remember, this is a spectrum of maturity it's a maturity model and we've added some of those industry players that we see building superclouds like CapitalOne, Goldman Sachs, Walmart. This is in deference to Moschella's observation around The Matrix and the industry structural changes that are going on. This goes back to every company, being a software company and rather than pattern match an outdated SaaS model, we see new industry structures emerging where software and data, and tools, specific to an industry will lead the next wave of innovation and bring in new value that traditional technology companies aren't going to solve, and the hyperscalers aren't going to solve. You know, we've talked a lot about Snowflake's data cloud as an example of supercloud. After being at Snowflake Summit, we're more convinced than ever that they're headed in this direction. VMware is clearly going after cross-cloud services you know, perhaps creating a new category. Basically, every large company we see either pursuing supercloud initiatives or thinking about it. Dell showed project Alpine at Dell Tech World, that's a supercloud. Snowflake introducing a new application development capability based on their superPaaS, our term of course, they don't use the phrase. Mongo, Couchbase, Nutanix, Pure Storage, Veeam, CrowdStrike, Okta, Zscaler. Yeah, all of those guys. Yes, Cisco and HPE. Even though on theCUBE at HPE Discover, Fidelma Russo said on theCUBE, she wasn't a fan of cloaking mechanisms, but then we talked to HPE's Head of Storage Services, Omer Asad is clearly headed in the direction that we would consider supercloud. Again, those cross-cloud services, of course, their emphasis is connecting as well on-prem. That single experience, which traditionally has not existed with multi-cloud or hybrid. And we're seeing the emergence of companies, smaller companies like Aviatrix and Starburst, and Clumio and others that are building versions of superclouds that solve for a specific problem for their customers. Even ISVs like Adobe, ADP, we've talked to UiPath. They seem to be looking at new ways to go beyond the SaaS model and add value within their cloud ecosystem specifically, around data as part of their and their customers digital transformations. So yeah, pretty much every tech vendor with any size or momentum and new industry players are coming out of hiding, and competing. Building superclouds that look a lot like Moschella's Matrix, with machine intelligence and blockchains, and virtual realities, and gaming, all enabled by the internet and hyperscale cloud CAPEX. So it's moving fast and it's the future in our opinion. So don't get too caught up in the past or you'll be left behind. Okay, what about examples? We've given a number in the past, but let's try to be a little bit more specific. Here are a few we've selected and we're going to answer the two questions in one section here. What workloads and services will run in superclouds and what are some examples? Let's start with analytics. Our favorite example is Snowflake, it's one of the furthest along with its data cloud, in our view. It's a supercloud optimized for data sharing and governance, query performance, and security, and ecosystem enablement. When you do things inside of that data cloud, what we call a super data cloud. Again, our term, not theirs. You can do things that you could not do in a single cloud. You can't do this with Redshift, You can't do this with SQL server and they're bringing new data types now with merging analytics or at least accommodate analytics and transaction type data, and bringing open source tooling with things like Apache Iceberg. And so it ticks the boxes we laid out earlier. I would say that a company like Databricks is also in that mix doing it, coming at it from a data science perspective, trying to create that consistent experience for data scientists and data engineering across clouds. Converge databases, running transaction and analytic workloads is another example. Take a look at what Couchbase is doing with Capella and how it's enabling stretching the cloud to the edge with ARM-based platforms and optimizing for low latency across clouds, and even out to the edge. Document database workloads, look at MongoDB, a very developer-friendly platform that with the Atlas is moving toward a supercloud model running document databases very, very efficiently. How about general purpose workloads? This is where VMware comes into to play. Very clearly, there's a need to create a common operating environment across clouds and on-prem, and out to the edge. And I say VMware is hard at work on that. Managing and moving workloads, and balancing workloads, and being able to recover very quickly across clouds for everyday applications. Network routing, take a look at what Aviatrix is doing across clouds, industry workloads. We see CapitalOne, it announced its cost optimization platform for Snowflake, piggybacking on Snowflake supercloud or super data cloud. And in our view, it's very clearly going to go after other markets is going to test it out with Snowflake, running, optimizing on AWS and it's going to expand to other clouds as Snowflake's business and those other clouds grows. Walmart working with Microsoft to create an on-premed Azure experience that's seamless. Yes, that counts, on-prem counts. If you can create that seamless and continuous experience, identical experience from on-prem to a hyperscale cloud, we would include that as a supercloud. You know, we've written about what Goldman is doing. Again, connecting its on-prem data and software tooling, and other capabilities to AWS for scale. And we can bet dollars to donuts that Oracle will be building a supercloud in healthcare with its Cerner acquisition. Supercloud is everywhere you look. So I'm sorry, naysayers it's happening all around us. So what's next? Well, with all the industry buzz and debate about the future, John Furrier and I, have decided to host an event in Palo Alto, we're motivated and inspired to further this conversation. And we welcome all points of view, positive, negative, multi-cloud, supercloud, hypercloud, all welcome. So theCUBE on Supercloud is coming on August 9th, out of our Palo Alto studios, we'll be running a live program on the topic. We've reached out to a number of industry participants, VMware, Snowflake, Confluent, Sky High Security, Gee Rittenhouse's new company, HashiCorp, CloudFlare. We've hit up Red Hat and we expect many of these folks will be in our studios on August 9th. And we've invited a number of industry participants as well that we're excited to have on. From industry, from financial services, from healthcare, from retail, we're inviting analysts, thought leaders, investors. We're going to have more detail in the coming weeks, but for now, if you're interested, please reach out to me or John with how you think you can advance the discussion and we'll see if we can fit you in. So mark your calendars, stay tuned for more information. Okay, that's it for today. Thanks to Alex Myerson who handles production and manages the podcast for Breaking Analysis. And I want to thank Kristen Martin and Cheryl Knight, they help get the word out on social and in our newsletters. And Rob Hof is our editor in chief over at SiliconANGLE, who does a lot of editing and appreciate you posting on SiliconANGLE, Rob. Thanks to all of you. Remember, all these episodes are available as podcasts wherever you listen. All you got to do is search Breaking Analysis podcast. It publish each week on wikibon.com and siliconangle.com. You can email me directly at david.vellante@siliconangle.com or DM me @DVellante, or comment on my LinkedIn post. And please do check out ETR.ai for the best survey data. And the enterprise tech business will be at AWS NYC Summit next Tuesday, July 12th. So if you're there, please do stop by and say hello to theCUBE, it's at the Javits Center. This is Dave Vellante for theCUBE insights powered by ETR. Thanks for watching. And we'll see you next time on "Breaking Analysis." (bright music)

>> From theCUBE Studios in Palo Alto and Boston, bringing you data-driven insights from theCUBE and ETR. This is "Breaking Analysis" with Dave Vallante. >> Welcome to this week's Wikibon CUBE Insights powered by ETR. As we exited the isolation economy last year, Supercloud is a term that we introduced to describe something new that was happening in the world of cloud. In this "Breaking Analysis," we address the 10 most frequently asked questions we get around Supercloud. Okay, let's review these frequently asked questions on Supercloud that we're going to try to answer today. Look at an industry that's full of hype and buzzwords. Why the hell does anyone need a new term? Aren't hyperscalers building out Superclouds? We'll try to answer why the term Supercloud connotes something different from hyperscale clouds. And we'll talk about the problems that Superclouds solve specifically, and we'll further define the critical aspects of a Supercloud architecture. We often get asked, "Isn't this just multi-cloud?" Well, we don't think so, and we'll explain why in this "Breaking Analysis." Now, in an earlier episode, we introduced the notion of super PaaS. Well, isn't a plain vanilla PaaS already a super PaaS? Again, we don't think so, and we'll explain why. Who will actually build and who are the players currently building Superclouds? What workloads and services will run on Superclouds? And eight A or number nine, what are some examples that we can share of Supercloud? And finally, we'll answer what you can expect next from us on Supercloud. Okay, let's get started. Why do we need another buzzword? Well, late last year ahead of re:Invent, we were inspired by a post from Jerry Chen called castles in the cloud. Now, in that blog post, he introduced the idea that there were submarkets emerging in cloud that presented opportunities for investors and entrepreneurs. That the cloud wasn't going to suck the hyperscalers, weren't going to suck all the value out of the industry. And so we introduced this notion of Supercloud to describe what we saw as a value layer emerging above the hyperscalers CAPEX gift, we sometimes call it. Now, it turns out that we weren't the only ones using the term, as both Cornell and MIT, have used the phrase in somewhat similar, but different contexts. The point is, something new was happening in the AWS and other ecosystems. It was more than IS and PaaS, and wasn't just SaaS running in the cloud. It was a new architecture that integrates infrastructure, platform and software as services, to solve new problems that the cloud vendors, in our view, weren't addressing by themselves. It seemed to us that the ecosystem was pursuing opportunities across clouds that went beyond conventional implementations of multi-cloud. And we felt there was a structural change going on at the industry level. The Supercloud metaphorically was highlighting. So that's the background on why we felt a new catch phrase was warranted. Love it or hate it, it's memorable and it's what we chose. Now, to that last point about structural industry transformation. Andy Rapaport is sometimes and often credited with identifying the shift from the vertically integrated IBM mainframe era to the fragmented PC microprocesor based era in his HBR article in 1991. In fact, it was David Moschella, who at the time was an IDC analyst who first introduced the concept in 1987, four years before Rapaport's article was published. Moschella saw that it was clear that Intel, Microsoft, Seagate and others would replace the system vendors and put that forth in a graphic that looked similar to the first two on this chart. We don't have to review the shift from IBM as the center of the industry to Wintel. That's well understood. What isn't as well known or accepted is what Moschella put out in his 2018 book called "Seeing Digital" which introduced the idea of the matrix that's shown on the right hand side of this chart. Moschella posited that new services were emerging, built on top of the internet and hyperscale clouds that would integrate other innovations and would define the next era of computing. He used the term matrix, because the conceptual depiction included, not only horizontal technology rows, like the cloud and the internet, but for the first time included connected industry verticals, the columns in this chart. Moschella pointed out that, whereas historically, industry verticals had a closed value chain or stack and ecosystem of R&D and production and manufacturing and distribution. And if you were in that industry, the expertise within that vertical generally stayed within that vertical and was critical to success. But because of digital and data, for the first time, companies were able to traverse industries jump across industries and compete because data enabled them to do that. Examples, Amazon and content, payments, groceries, Apple and payments, and content and so forth. There are many examples. Data was now this unifying enabler and this marked a change in the structure of the technology landscape. And Supercloud is meant to imply more than running in hyperscale clouds. Rather, it's the combination of multiple technologies, enabled by cloud scale with new industry participants from those verticals; financial services, and healthcare, and manufacturing, energy, media, and virtually all and any industry. Kind of an extension of every company is a software company. Basically, every company now has the opportunity to build their own cloud or Supercloud. And we'll come back to that. Let's first address what's different about Superclouds relative to hyperscale clouds. Now, this one's pretty straightforward and obvious, I think. Hyperscale clouds, they're walled gardens where they want your data in their cloud and they want to keep you there. Sure, every cloud player realizes that not all data will go to their particular cloud. So they're meeting customers where their data lives with initiatives like Amazon Outposts and Azure Arc and Google Antos. But at the end of the day, the more homogeneous they can make their environments, the better control, security, costs, and performance they can deliver. The more complex the environment, the more difficult it is to deliver on their brand promises. And, of course, the less margin that's left for them to capture. Will the hyperscalers get more serious about cross cloud services? Maybe, but they have plenty of work to do within their own clouds and within enabling their own ecosystems. They have a long way to go, a lot of runway. So let's talk about specifically, what problems Superclouds solve. We've all seen the stats from IDC or Gartner or whomever, that customers on average use more than one cloud, two clouds, three clouds, five clouds, 20 clouds. And we know these clouds operate in disconnected silos for the most part. And that's a problem, because each cloud requires different skills, because the development environment is different as is the operating environment. They have different APIs, different primitives, and different management tools that are optimized for each respective hyperscale cloud. Their functions and value props don't extend to their competitors' clouds for the most part. Why would they? As a result, there's friction when moving between different clouds. It's hard to share data. It's hard to move work. It's hard to secure and govern data. It's hard to enforce organizational edicts and policies across these clouds and on-prem. Supercloud is an architecture designed to create a single environment that enables management of workloads and data across clouds in an effort to take out complexity, accelerate application development, streamline operations, and share data safely, irrespective of location. It's pretty straightforward, but non-trivial, which is why I always ask a company's CEO and executives if stock buybacks and dividends will yield as much return as building out Superclouds that solve really specific and hard problems and create differential value. Okay, let's dig a bit more into the architectural aspects of Supercloud. In other words, what are the salient attributes of Supercloud? So, first and foremost, a Supercloud runs a set of specific services designed to solve a unique problem, and it can do so in more than one cloud. Superclouds leverage the underlying cloud native tooling of a hyperscale cloud, but they're optimized for a specific objective that aligns with the problem that they're trying to solve. For example, Supercloud might be optimized for lowest cost or lowest latency or sharing data or governing or securing that data or higher performance for networking, for example. But the point is, the collection of services that is being delivered is focused on a unique value proposition that is not being delivered by the hyperscalers across clouds. A Supercloud abstracts the underlying and siloed primitives of the native PaaS layer from the hyperscale cloud, and then using its own specific platform as a service tooling, creates a common experience across clouds for developers and users. And it does so in the most efficient manner, meaning it has the metadata knowledge and management capabilities that can optimize for latency, bandwidth, or recovery or data sovereignty, or whatever unique value that Supercloud is delivering for the specific use case in their domain. And a Supercloud comprises a super PaaS capability that allows ecosystem partners through APIs to add incremental value on top of the Supercloud platform to fill gaps, accelerate features, and of course, innovate. The services can be infrastructure related, they could be application services, they could be data services, security services, user services, et cetera, designed and packaged to bring unique value to customers. Again, that hyperscalers are not delivering across clouds or on premises. Okay, so another common question we get is, "Isn't that just multi-cloud?" And what we'd say to that is yeah, "Yes, but no." You can call it multi-cloud 2.0, if you want. If you want to use, it's kind of a commonly used rubric. But as Dell's Chuck Whitten proclaimed at Dell Technologies World this year, multi-cloud, by design, is different than multi-cloud by default. Meaning, to date, multi-cloud has largely been a symptom of what we've called multi-vendor or of M&A. You buy a company and they happen to use Google cloud. And so you bring it in. And when you look at most so-called multi-cloud implementations, you see things like an on-prem stack, which is wrapped in a container and hosted on a specific cloud. Or increasingly, a technology vendor has done the work of building a cloud native version of their stack and running it on a specific cloud. But historically, it's been a unique experience within each cloud, with virtually no connection between the cloud silos. Supercloud sets out to build incremental value across clouds and above hyperscale CAPEX that goes beyond cloud compatibility within each cloud. So, if you want to call it multi-cloud 2.0, that's fine, but we chose to call it Supercloud. Okay, so at this point you may be asking, "Well isn't PaaS already a version of Supercloud?" And again, we would say, "No." That Supercloud and its corresponding super PaaS layer, which is a prerequisite, gives the freedom to store, process, and manage and secure and connect islands of data across a continuum with a common experience across clouds. And the services offered are specific to that Supercloud and will vary by each offering. OpenShift, for example, can be used to construct a super PaaS, but in and of itself, isn't a super PaaS, it's generic. A super PaaS might be developed to support, for instance, ultra low latency database work. It would unlikely, again, taking the OpenShift example, it's unlikely that off the shelf OpenShift would be used to develop such a low latency, super PaaS layer for ultra low latency database work. The point is, Supercloud and its inherent super PaaS will be optimized to solve specific problems like that low latency example for distributed databases or fast backup in recovery for data protection and ransomware, or data sharing or data governance. Highly specific use cases that the Supercloud is designed to solve for. Okay, another question we often get is, "Who has a Supercloud today and who's building a Supercloud and who are the contenders?" Well, most companies that consider themselves cloud players will, we believe, be building or are building Superclouds. Here's a common ETR graphic that we like to show with net score or spending momentum on the Y axis, and overlap or pervasiveness in the ETR surveys on the X axis. And we've randomly chosen a number of players that we think are in the Supercloud mix. And we've included the hyperscalers because they are enablers. Now, remember, this is a spectrum of maturity. It's a maturity model. And we've added some of those industry players that we see building Superclouds like Capital One, Goldman Sachs, Walmart. This is in deference to Moschella's observation around the matrix and the industry structural changes that are going on. This goes back to every company being a software company. And rather than pattern match and outdated SaaS model, we see new industry structures emerging where software and data and tools specific to an industry will lead the next wave of innovation and bring in new value that traditional technology companies aren't going to solve. And the hyperscalers aren't going to solve. We've talked a lot about Snowflake's data cloud as an example of Supercloud. After being at Snowflake Summit, we're more convinced than ever that they're headed in this direction. VMware is clearly going after cross cloud services, perhaps creating a new category. Basically, every large company we see either pursuing Supercloud initiatives or thinking about it. Dell showed Project Alpine at Dell Tech World. That's a Supercloud. Snowflake introducing a new application development capability based on their super PaaS, our term, of course. They don't use the phrase. Mongo, Couchbase, Nutanix, Pure Storage, Veeam, CrowdStrike, Okta, Zscaler. Yeah, all of those guys. Yes, Cisco and HPE. Even though on theCUBE at HPE Discover, Fidelma Russo said on theCUBE, she wasn't a fan of cloaking mechanisms. (Dave laughing) But then we talked to HPE's head of storage services, Omer Asad, and he's clearly headed in the direction that we would consider Supercloud. Again, those cross cloud services, of course, their emphasis is connecting as well on-prem. That single experience, which traditionally has not existed with multi-cloud or hybrid. And we're seeing the emergence of smaller companies like Aviatrix and Starburst and Clumio and others that are building versions of Superclouds that solve for a specific problem for their customers. Even ISVs like Adobe, ADP, we've talked to UiPath. They seem to be looking at new ways to go beyond the SaaS model and add value within their cloud ecosystem, specifically around data as part of their and their customer's digital transformations. So yeah, pretty much every tech vendor with any size or momentum, and new industry players are coming out of hiding and competing, building Superclouds that look a lot like Moschella's matrix, with machine intelligence and blockchains and virtual realities and gaming, all enabled by the internet and hyperscale cloud CAPEX. So it's moving fast and it's the future in our opinion. So don't get too caught up in the past or you'll be left behind. Okay, what about examples? We've given a number in the past but let's try to be a little bit more specific. Here are a few we've selected and we're going to answer the two questions in one section here. What workloads and services will run in Superclouds and what are some examples? Let's start with analytics. Our favorite example of Snowflake. It's one of the furthest along with its data cloud, in our view. It's a Supercloud optimized for data sharing and governance, and query performance, and security, and ecosystem enablement. When you do things inside of that data cloud, what we call a super data cloud. Again, our term, not theirs. You can do things that you could not do in a single cloud. You can't do this with Redshift. You can't do this with SQL server. And they're bringing new data types now with merging analytics or at least accommodate analytics and transaction type data and bringing open source tooling with things like Apache Iceberg. And so, it ticks the boxes we laid out earlier. I would say that a company like Databricks is also in that mix, doing it, coming at it from a data science perspective trying to create that consistent experience for data scientists and data engineering across clouds. Converge databases, running transaction and analytic workloads is another example. Take a look at what Couchbase is doing with Capella and how it's enabling stretching the cloud to the edge with arm based platforms and optimizing for low latency across clouds, and even out to the edge. Document database workloads, look at Mongo DB. A very developer friendly platform that where the Atlas is moving toward a Supercloud model, running document databases very, very efficiently. How about general purpose workloads? This is where VMware comes into play. Very clearly, there's a need to create a common operating environment across clouds and on-prem and out to the edge. And I say, VMware is hard at work on that, managing and moving workloads and balancing workloads, and being able to recover very quickly across clouds for everyday applications. Network routing, take a look at what Aviatrix is doing across clouds. Industry workloads, we see Capital One. It announced its cost optimization platform for Snowflake, piggybacking on Snowflake's Supercloud or super data cloud. And in our view, it's very clearly going to go after other markets. It's going to test it out with Snowflake, optimizing on AWS, and it's going to expand to other clouds as Snowflake's business and those other clouds grows. Walmart working with Microsoft to create an on-premed Azure experience that's seamless. Yes, that counts, on-prem counts. If you can create that seamless and continuous experience, identical experience from on-prem to a hyperscale cloud, we would include that as a Supercloud. We've written about what Goldman is doing. Again, connecting its on-prem data and software tooling, and other capabilities to AWS for scale. And you can bet dollars to donuts that Oracle will be building a Supercloud in healthcare with its Cerner acquisition. Supercloud is everywhere you look. So I'm sorry, naysayers, it's happening all around us. So what's next? Well, with all the industry buzz and debate about the future, John Furrier and I have decided to host an event in Palo Alto. We're motivated and inspired to further this conversation. And we welcome all points of view, positive, negative, multi-cloud, Supercloud, HyperCloud, all welcome. So theCUBE on Supercloud is coming on August 9th out of our Palo Alto studios. We'll be running a live program on the topic. We've reached out to a number of industry participants; VMware, Snowflake, Confluent, Skyhigh Security, G. Written House's new company, HashiCorp, CloudFlare. We've hit up Red Hat and we expect many of these folks will be in our studios on August 9th. And we've invited a number of industry participants as well that we're excited to have on. From industry, from financial services, from healthcare, from retail, we're inviting analysts, thought leaders, investors. We're going to have more detail in the coming weeks, but for now, if you're interested, please reach out to me or John with how you think you can advance the discussion, and we'll see if we can fit you in. So mark your calendars, stay tuned for more information. Okay, that's it for today. Thanks to Alex Myerson who handles production and manages the podcast for "Breaking Analysis." And I want to thank Kristen Martin and Cheryl Knight. They help get the word out on social and in our newsletters. And Rob Hof is our editor in chief over at SiliconANGLE, who does a lot of editing and appreciate you posting on SiliconANGLE, Rob. Thanks to all of you. Remember, all these episodes are available as podcasts wherever you listen. All you got to do is search, breaking analysis podcast. I publish each week on wikibon.com and siliconangle.com. Or you can email me directly at david.vellante@siliconangle.com. Or DM me @DVallante, or comment on my LinkedIn post. And please, do check out etr.ai for the best survey data in the enterprise tech business. We'll be at AWS NYC summit next Tuesday, July 12th. So if you're there, please do stop by and say hello to theCUBE. It's at the Javits Center. This is Dave Vallante for theCUBE Insights, powered by ETR. Thanks for watching. And we'll see you next time on "Breaking Analysis." (slow music)

>> From theCUBE Studios in Palo Alto in Boston, bringing you data driven insights from theCUBE and ETR. This is Breaking Analysis with Dave Vellante. >> After a two-year epic run in tech, 2022 has been an epically bad year. Through yesterday, The NASDAQ composite is down 30%. The S$P 500 is off 21%. And the Dow Jones Industrial average 16% down. And the poor holders at Bitcoin have had to endure a nearly 60% decline year to date. But judging by the attendance and enthusiasm, in major in-person tech events this spring. You'd never know that tech was in the tank. Moreover, walking around the streets of Las Vegas, where most tech conferences are held these days. One can't help but notice that the good folks of Main Street, don't seem the least bit concerned that the economy is headed for a recession. Hello, and welcome to this weeks Wiki Bond Cube Insights powered by ETR. In this Breaking Analysis we'll share our main takeaways from the first half of 2022. And talk about the outlook for tech going forward, and why despite some pretty concerning headwinds we remain sanguine about tech generally, but especially enterprise tech. Look, here's the bumper sticker on why many folks are really bearish at the moment. Of course, inflation is high, other than last year, the previous inflation high this century was in July of 2008, it was 5.6%. Inflation has proven to be very, very hard to tame. You got gas at $7 dollars a gallon. Energy prices they're not going to suddenly drop. Interest rates are climbing, which will eventually damage housing. Going to have that ripple effect, no doubt. We're seeing layoffs at companies like Tesla and the crypto names are also trimming staff. Workers, however are still in short supply. So wages are going up. Companies in retail are really struggling with the right inventory, and they can't even accurately guide on their earnings. We've seen a version of this movie before. Now, as it pertains to tech, Crawford Del Prete, who's the CEO of IDC explained this on theCUBE this very week. And I thought he did a really good job. He said the following, >> Matt, you have a great statistic that 80% of companies used COVID as their point to pivot into digital transformation. And to invest in a different way. And so what we saw now is that tech is now where I think companies need to focus. They need to invest in tech. They need to make people more productive with tech and it played out in the numbers. Now so this year what's fascinating is we're looking at two vastly different markets. We got gasoline at $7 a gallon. We've got that affecting food prices. Interesting fun fact recently it now costs over $1,000 to fill an 18 wheeler. All right, based on, I mean, this just kind of can't continue. So you think about it. >> Don't put the boat in the water. >> Yeah, yeah, yeah. Good luck if ya, yeah exactly. So a family has kind of this bag of money, and that bag of money goes up by maybe three, 4% every year, depending upon earnings. So that is sort of sloshing around. So if food and fuel and rent is taking up more, gadgets and consumer tech are not, you're going to use that iPhone a little longer. You're going to use that Android phone a little longer. You're going to use that TV a little longer. So consumer tech is getting crushed, really it's very, very, and you saw it immediately in ad spending. You've seen it in Meta, you've seen it in Facebook. Consumer tech is doing very, very, it is tough. Enterprise tech, we haven't been in the office for two and a half years. We haven't upgraded whether that be campus wifi, whether that be servers, whether that be commercial PCs as much as we would have. So enterprise tech, we're seeing double digit order rates. We're seeing strong, strong demand. We have combined that with a component shortage, and you're seeing some enterprise companies with a quarter of backlog, I mean that's really unheard of. >> And higher prices, which also profit. >> And therefore that drives up the prices. >> And this is a theme that we've heard this year at major tech events, they've really come roaring back. Last year, theCUBE had a huge presence at AWS Reinvent. The first Reinvent since 2019, it was really well attended. Now this was before the effects of the omicron variant, before they were really well understood. And in the first quarter of 2022, things were pretty quiet as far as tech events go But theCUBE'a been really busy this spring and early into the summer. We did 12 physical events as we're showing here in the slide. Coupa, did Women in Data Science at Stanford, Coupa Inspire was in Las Vegas. Now these are both smaller events, but they were well attended and beat expectations. San Francisco Summit, the AWS San Francisco Summit was a bit off, frankly 'cause of the COVID concerns. They were on the rise, then we hit Dell Tech World which was packed, it had probably around 7,000 attendees. Now Dockercon was virtual, but we decided to include it here because it was a huge global event with watch parties and many, many tens of thousands of people attending. Now the Red Hat Summit was really interesting. The choice that Red Hat made this year. It was purposefully scaled down and turned into a smaller VIP event in Boston at the Western, a couple thousand people only. It was very intimate with a much larger virtual presence. VeeamON was very well attended, not as large as previous VeeamON events, but again beat expectations. KubeCon and Cloud Native Con was really successful in Spain, Valencia, Spain. PagerDuty Summit was again a smaller intimate event in San Francisco. And then MongoDB World was at the new Javits Center and really well attended over the three day period. There were lots of developers there, lots of business people, lots of ecosystem partners. And then the Snowflake summit in Las Vegas, it was the most vibrant from the standpoint of the ecosystem with nearly 10,000 attendees. And I'll come back to that in a moment. Amazon re:Mars is the Amazon AI robotic event, it's smaller but very, very cool, a lot of innovation. And just last week we were at HPE Discover. They had around 8,000 people attending which was really good. Now I've been to over a dozen HPE or HPE Discover events, within Europe and the United States over the past decade. And this was by far the most vibrant, lot of action. HPE had a little spring in its step because the company's much more focused now but people was really well attended and people were excited to be there, not only to be back at physical events, but also to hear about some of the new innovations that are coming and HPE has a long way to go in terms of building out that ecosystem, but it's starting to form. So we saw that last week. So tech events are back, but they are smaller. And of course now a virtual overlay, they're hybrid. And just to give you some context, theCUBE did, as I said 12 physical events in the first half of 2022. Just to compare that in 2019, through June of that year we had done 35 physical events. Yeah, 35. And what's perhaps more interesting is we had our largest first half ever in our 12 year history because we're doing so much hybrid and virtual to compliment the physical. So that's the new format is CUBE plus digital or sometimes just digital but that's really what's happening in our business. So I think it's a reflection of what's happening in the broader tech community. So everyone's still trying to figure that out but it's clear that events are back and there's no replacing face to face. Or as I like to say, belly to belly, because deals are done at physical events. All these events we've been to, the sales people are so excited. They're saying we're closing business. Pipelines coming out of these events are much stronger, than they are out of the virtual events but the post virtual event continues to deliver that long tail effect. So that's not going to go away. The bottom line is hybrid is the new model. Okay let's look at some of the big themes that we've taken away from the first half of 2022. Now of course, this is all happening under the umbrella of digital transformation. I'm not going to talk about that too much, you've had plenty of DX Kool-Aid injected into your veins over the last 27 months. But one of the first observations I'll share is that the so-called big data ecosystem that was forming during the hoop and around, the hadoop infrastructure days and years. then remember it dispersed, right when the cloud came in and kind of you know, not wiped out but definitely dampened the hadoop enthusiasm for on-prem, the ecosystem dispersed, but now it's reforming. There are large pockets that are obviously seen in the various clouds. And we definitely see a ecosystem forming around MongoDB and the open source community gathering in the data bricks ecosystem. But the most notable momentum is within the Snowflake ecosystem. Snowflake is moving fast to win the day in the data ecosystem. They're providing a single platform that's bringing different data types together. Live data from systems of record, systems of engagement together with so-called systems of insight. These are converging and while others notably, Oracle are architecting for this new reality, Snowflake is leading with the ecosystem momentum and a new stack is emerging that comprises cloud infrastructure at the bottom layer. Data PaaS layer for app dev and is enabling an ecosystem of partners to build data products and data services that can be monetized. That's the key, that's the top of the stack. So let's dig into that further in a moment but you're seeing machine intelligence and data being driven into applications and the data and application stacks they're coming together to support the acceleration of physical into digital. It's happening right before our eyes in every industry. We're also seeing the evolution of cloud. It started with the SaaS-ification of the enterprise where organizations realized that they didn't have to run their own software on-prem and it made sense to move to SaaS for CRM or HR, certainly email and collaboration and certain parts of ERP and early IS was really about getting out of the data center infrastructure management business called that cloud 1.0, and then 2.0 was really about changing the operating model. And now we're seeing that operating model spill into on-prem workloads finally. We're talking about here about initiatives like HPE's Green Lake, which we heard a lot about last week at Discover and Dell's Apex, which we heard about in May, in Las Vegas. John Furrier had a really interesting observation that basically this is HPE's and Dell's version of outposts. And I found that interesting because outpost was kind of a wake up call in 2018 and a shot across the bow at the legacy enterprise infrastructure players. And they initially responded with these flexible financial schemes, but finally we're seeing real platforms emerge. Again, we saw this at Discover and at Dell Tech World, early implementations of the cloud operating model on-prem. I mean, honestly, you're seeing things like consoles and billing, similar to AWS circa 2014, but players like Dell and HPE they have a distinct advantage with respect to their customer bases, their service organizations, their very large portfolios, especially in the case of Dell and the fact that they have more mature stacks and knowhow to run mission critical enterprise applications on-prem. So John's comment was quite interesting that these firms are basically building their own version of outposts. Outposts obviously came into their wheelhouse and now they've finally responded. And this is setting up cloud 3.0 or Supercloud, as we like to call it, an abstraction layer, that sits above the clouds that serves as a unifying experience across a continuum of on-prem across clouds, whether it's AWS, Azure, or Google. And out to both the near and far edge, near edge being a Lowes or a Home Depot, but far edge could be space. And that edge again is fragmented. You've got the examples like the retail stores at the near edge. Outer space maybe is the far edge and IOT devices is perhaps the tiny edge. No one really knows how the tiny edge is going to play out but it's pretty clear that it's not going to comprise traditional X86 systems with a cool name tossed out to the edge. Rather, it's likely going to require a new low cost, low power, high performance architecture, most likely RM based that will enable things like realtime AI inferencing at that edge. Now we've talked about this a lot on Breaking Analysis, so I'm not going to double click on it. But suffice to say that it's very possible that new innovations are going to emerge from the tiny edge that could really disrupt the enterprise in terms of price performance. Okay, two other quick observations. One is that data protection is becoming a much closer cohort to the security stack where data immutability and air gaps and fast recovery are increasingly becoming a fundamental component of the security strategy to combat ransomware and recover from other potential hacks or disasters. And I got to say from our observation, Veeam is leading the pack here. It's now claiming the number one revenue spot in a statistical dead heat with the Dell's data protection business. That's according to Veeam, according to IDC. And so that space continues to be of interest. And finally, Broadcom's acquisition of Dell. It's going to have ripple effects throughout the enterprise technology business. And there of course, there are a lot of questions that remain, but the one other thing that John Furrier and I were discussing last night John looked at me and said, "Dave imagine if VMware runs better on Broadcom components and OEMs that use Broadcom run VMware better, maybe Broadcom doesn't even have to raise prices on on VMware licenses. Maybe they'll just raise prices on the OEMs and let them raise prices to the end customer." Interesting thought, I think because Broadcom is so P&L focused that it's probably not going to be the prevailing model but we'll see what happens to some of the strategic projects rather like Monterey and Capitola and Thunder. We've talked a lot about project Monterey, the others we'll see if they can make the cut. That's one of the big concerns because it's how OEMs like the ones that are building their versions of outposts are going to compete with the cloud vendors, namely AWS in the future. I want to come back to the comment on the data stack for a moment that we were talking about earlier, we talked about how the big data ecosystem that was once coalescing around hadoop dispersed. Well, the data value chain is reforming and we think it looks something like this picture, where cloud infrastructure lives at the bottom. We've said many times the cloud is expanding and evolving. And if companies like Dell and HPE can truly build a super cloud infrastructure experience then they will be in a position to capture more of the data value. If not, then it's going to go to the cloud players. And there's a live data layer that is increasingly being converged into platforms that not only simplify the movement in ELTing of data but also allow organizations to compress the time to value. Now there's a layer above that, we sometimes call it the super PaaS layer if you will, that must comprise open source tooling, partners are going to write applications and leverage platform APIs and build data products and services that can be monetized at the top of the stack. So when you observe the battle for the data future it's unlikely that any one company is going to be able to do this all on their own, which is why I often joke that the 2020s version of a sweaty Steve Bomber running around the stage, screaming, developers, developers developers, and getting the whole audience into it is now about ecosystem ecosystem ecosystem. Because when you need to fill gaps and accelerate features and provide optionality a list of capabilities on the left hand side of this chart, that's going to come from a variety of different companies and places, we're talking about catalogs and AI tools and data science capabilities, data quality, governance tools and it should be of no surprise to followers of Breaking Analysis that on the right hand side of this chart we're including the four principles of data mesh, which of course were popularized by Zhamak Dehghani. So decentralized data ownership, data as products, self-serve platform and automated or computational governance. Now whether this vision becomes a reality via a proprietary platform like Snowflake or somehow is replicated by an open source remains to be seen but history generally shows that a defacto standard for more complex problems like this is often going to emerge prior to an open source alternative. And that would be where I would place my bets. Although even that proprietary platform has to include open source optionality. But it's not a winner take all market. It's plenty of room for multiple players and ecosystem innovators, but winner will definitely take more in my opinion. Okay, let's close with some ETR data that looks at some of those major platform plays who talk a lot about digital transformation and world changing impactful missions. And they have the resources really to compete. This is an XY graphic. It's a view that we often show, it's got net score on the vertical access. That's a measure of spending momentum, and overlap or presence in the ETR survey. That red, that's the horizontal access. The red dotted line at 40% indicates that the platform is among the highest in terms of spending velocity. Which is why I always point out how impressive that makes AWS and Azure because not only are they large on the horizontal axis, the spending momentum on those two platforms rivals even that of Snowflake which continues to lead all on the vertical access. Now, while Google has momentum, given its goals and resources, it's well behind the two leaders. We've added Service Now and Salesforce, two platform names that have become the next great software companies. Joining likes of Oracle, which we show here and SAP not shown along with IBM, you can see them on this chart. We've also plotted MongoDB, which we think has real momentum as a company generally but also with Atlas, it's managed cloud database as a service specifically and Red Hat with trying to become the standard for app dev in Kubernetes environments, which is the hottest trend right now in application development and application modernization. Everybody's doing something with Kubernetes and of course, Red Hat with OpenShift wants to make that a better experience than do it yourself. The DYI brings a lot more complexity. And finally, we've got HPE and Dell both of which we've talked about pretty extensively here and VMware and Cisco. Now Cisco is executing on its portfolio strategy. It's got a lot of diverse components to its company. And it's coming at the cloud of course from a networking and security perspective. And that's their position of strength. And VMware is a staple of the enterprise. Yes, there's some uncertainty with regards to the Broadcom acquisition, but one thing is clear vSphere isn't going anywhere. It's entrenched and will continue to run lots of IT for years to come because it's the best platform on the planet. Now, of course, these are just some of the players in the mix. We expect that numerous non-traditional technology companies this is important to emerge as new cloud players. We've put a lot of emphasis on the data ecosystem because to us that's really going to be the main spring of digital, i.e., a digital company is a data company and that means an ecosystem of data partners that can advance outcomes like better healthcare, faster drug discovery, less fraud, cleaner energy, autonomous vehicles that are safer, smarter, more efficient grids and factories, better government and virtually endless litany of societal improvements that can be addressed. And these companies will be building innovations on top of cloud platforms creating their own super clouds, if you will. And they'll come from non-traditional places, industries, finance that take their data, their software, their tooling bring them to their customers and run them on various clouds. Okay, that's it for today. Thanks to Alex Myerson, who is on production and does the podcast for Breaking Analysis, Kristin Martin and Cheryl Knight, they help get the word out. And Rob Hoofe is our editor and chief over at Silicon Angle who helps edit our posts. Remember all these episodes are available as podcasts wherever you listen. All you got to do is search Breaking Analysis podcast. I publish each week on wikibon.com and siliconangle.com. You can email me directly at david.vellante@siliconangle.com or DM me at dvellante, or comment on my LinkedIn posts. And please do check out etr.ai for the best survey data in the enterprise tech business. This is Dave Vellante for theCUBE's Insights powered by ETR. Thanks for watching be well. And we'll see you next time on Breaking Analysis. (upbeat music)

>>The cube presents HPE discover 2022 brought to you by HPE. >>Hey everyone. Welcome back to the Cube's day one coverage of HPE discover 22 live from the Venetian in Las Vegas. I got a power panel here, Lisa Martin, with Dave Valante, John furrier, Holger Mueller also joins us. We are gonna wrap this, like you've never seen a rap before guys. Lot of momentum today, lot, lot of excitement, about 8,000 or so customers, partners, HPE leaders here. Holger. Let's go ahead and start with you. What are some of the things that you heard felt saw observed today on day one? >>Yeah, it's great to be back in person. Right? 8,000 people events are rare. Uh, I'm not sure. Have you been to more than 8,000? <laugh> yeah, yeah. Okay. This year, this year. I mean, historically, yes, but, um, >>Snowflake was 10. Yeah. >>So, oh, wow. Okay. So 8,000 was my, >>Cisco was, they said 15, >>But is my, my 8,000, my record, I let us down with 7,000 kind of like, but it's in the Florida swarm. It's not nicely. Like, and there's >>Usually what SFI, there's usually >>20, 20, 30, 40, 50. I remember 50 in the nineties. Right. That was a different time. But yeah. Interesting. Yeah. Interesting what people do and it depends how much time there is to come. Right. And know that it happens. Right. But yeah, no, I think it's interesting. We, we had a good two analyst track today. Um, interesting. Like HPE is kind of like back not being your grandfather's HPE to a certain point. One of the key stats. I know Dave always for the stats, right. Is what I found really interesting that over two third of GreenLake revenue is software and services. Now a love to know how much of that services, how much of that software. But I mean, I, I, I, provocate some, one to ones, the HP executives saying, Hey, you're a hardware company. Right. And they didn't even come back. Right. But Antonio said, no, two thirds is, uh, software and services. Right. That's interesting. They passed the one exabyte, uh, being managed, uh, as a, as a hallmark. Right. I was surprised only 120,000 users if I had to remember the number. Right, right. So that doesn't seem a terrible high amount of number of users. Right. So, but that's, that's, that's promising. >>So what software is in there, cuz it's gotta be mostly services. >>Right? Well it's the 70 plus cloud services, right. That everybody's talking about where the added eight of them shockingly back up and recovery, I thought that was done at launch. Right. >>Still who >>Keep recycling storage and you back. But now it's real. Yeah. >>But the company who knows the enterprise, right. HPE, what I've been doing before with no backup and recovery GreenLake. So that was kind of like, okay, we really want to do this now and nearly, and then say like, oh, by the way, we've been doing this all the time. Yeah. >>Oh, what's your take on the installed base of HP. We had that conversation, the, uh, kickoff or on who's their target, what's the target audience environment look like. It certainly is changing. Right? If it's software and services, GreenLake is resonating. Yeah. Um, ecosystems responding. What's their customers cuz managed services are up too Kubernetes, all the managed services what's what's it like what's their it transformation base look like >>Much of it is of course install base, right? The trusted 20, 30 plus year old HP customer. Who's keeping doing stuff of HP. Right. And call it GreenLake. They've been for so many name changes. It doesn't really matter. And it's kind of like nice that you get the consume pain only what you consume. Right. I get the cloud broad to me then the general markets, of course, people who still need to run stuff on premises. Right. And there's three reasons of doing this performance, right. Because we know the speed of light is relative. If you're in the Southern hemisphere and even your email servers in Northern hemisphere, it takes a moment for your email to arrive. It's a very different user experience. Um, local legislation for data, residency privacy. And then, I mean Charles Phillips who we all know, right. Former president of uh, info nicely always said, Hey, if the CIOs over 50, I don't have to sell qu. Right. So there is not invented. I'm not gonna do cloud here. And now I've kind of like clouded with something like HP GreenLake. That's the customers. And then of course procurement is a big friend, right? Yeah. Because when you do hardware refresh, right. You have to have two or three competitors who are the two or three competitors left. Right. There's Dell. Yeah. And then maybe Lenovo. Right? So, so like a >>Little bit channels, the strength, the procurement physicians of strength, of course install base question. Do you think they have a Microsoft opportunity where, what 365 was Microsoft had office before 365, but they brought in the cloud and then everything changed. Does HP have that same opportunity with kind of the GreenLake, you know, model with their existing stuff. >>It has a GreenLake opportunity, but there's not much software left. It's a very different situation like Microsoft. Right? So, uh, which green, which HP could bring along to say, now run it with us better in the cloud because they've been selling much of it. Most of it, of their software portfolio, which they bought as an HP in the past. Right. So I don't see that happening so much, but GreenLake as a platform itself course interesting because enterprise need a modern container based platform. >>I want, I want to double click on this a little bit because the way I see it is HP is going to its installed base. I think you guys are right on say, this is how we're doing business now. Yeah. You know, come on along. But my sense is, some customers don't want to do the consumption model. There are actually some customers that say, Hey, of course I got, I don't have a cash port problem. I wanna pay for it up front and leave me alone. >>I've been doing this since 50 years. Nice. As I changed it, now <laugh> two know >>Money's wants to do it. And I don't wanna rent because rental's more expensive and blah, blah, blah. So do you see that in the customer base that, that some are pushing back? >>Of course, look, I have a German accent, right? So I go there regularly and uh, the Germans are like worried about doing anything in the cloud. And if you go to a board in Germany and say, Hey, we can pay our usual hardware, refresh, CapEx as usual, or should we bug consumption? And they might know what we are running. <laugh> so not whole, no offense against the Germans out. The German parts are there, but many of them will say, Hey, so this is change with COVID. Right. Which is super interesting. Right? So the, the traditional boards non-technical have been hearing about this cloud variable cost OPEX to CapEx and all of a sudden there's so much CapEx, right. Office buildings, which are not being used truck fleets. So there's a whole new sensitivity by traditional non-technical boards towards CapEx, which now the light bulb went on and say, oh, that's the cloud thing about also. So we have to find a way to get our cost structure, to ramp up and ramp down as our business might be ramping up through COVID through now inflation fears, recession, fears, and so on. >>So, okay. HP's, HP's made the statement that anything you can do in the cloud you can do in GreenLake. Yes. And I've said you can't run on snowflake. You can't run Mongo Atlas, you can't run data bricks, but that's okay. That's fine. Let's be, I think they're talking about, there's >>A short list of things. I think they're talking about the, their >>Stuff, their, >>The operating experience. So we've got single sign on through a URL, right. Uh, you've got, you know, some level of consistency in terms of policy. It's unclear exactly what that is. You've got storage backup. Dr. What, some other services, seven other services. If you had to sort of take your best guess as to where HP is now and peg it toward where Amazon was in which year? >>20 14, 20 14. >>Yeah. Where they had their first conference or the second we invent here with 3000 people and they were thinking, Hey, we're big. Yeah. >>Yeah. And I think GreenLake is the building blocks. So they quite that's the >>Building. Right? I mean similar. >>Okay. Well, I mean they had E C, Q and S3 and SQS, right. That was the core. And then the rest of those services were, I mean, base stock was one of that first came in behind and >>In fairness, the industry has advanced since then, Kubernetes is further along. And so HPE can take advantage of that. But in terms of just the basic platform, I, I would agree. I think it's >>Well, I mean, I think, I mean the software, question's a big one. I wanna bring up because the question is, is that software is getting the world. Hardware is really software scales, everything, data, the edge story. I love their story. I think HP story is wonderful Aruba, you know, hybrid cloud, good story, edge edge. But if you look under the covers, it's weak, right? It's like, it's not software. They don't have enough software juice, but the ecosystem opportunity to me is where you plug and play. So HP knows that game. But if you look historically over the past 25 years, HP now HPE, they understand plug and play interoperability. So the question is, can they thread the needle >>Right. >>Between filling the gaps on the software? Yeah. With partners, >>Can they get the partners? Right. And which have been long, long time. Right. For a long time, HP has been the number one platform under ICP, right? Same thing. You get certified for running this. Right. I know from my own history, uh, I joined Oracle last century and the big thing was, let's get your eBusiness suite certified on HP. Right? Like as if somebody would buy H Oracle work for them, right. This 20 years ago, server >>The original exit data was HP. Oracle. >>Exactly. Exactly. So there's this thinking that's there. But I think the key thing is we know that all modern forget about the hardware form in the platforms, right? All modern software has to move to containers and snowflake runs in containers. You mentioned that, right? Yeah. If customers force snowflake and HPE to the table, right, there will be a way to make it work. Right. And which will help HPE to be the partner open part will bring the software. >>I, I think it's, I think that's an opportunity because that changes the game and agility and speed. If HP plays their differentiation, right. Which we asked on their opening segment, what's their differentiation. They got size scale channel, >>What to the enterprise. And then the big benefit is this workload portability thing. Right? You understand what is run in the public cloud? I need to run it local. For whatever reason, performance, local residency of data. I can move that. There that's the big benefit to the ISVs, the sales vendors as well. >>But they have to have a stronger data platform story in my that's right. Opinion. I mean, you can run Oracle and HPE, but there's no reason they shouldn't be able to do a deal with, with snowflake. I mean, we saw it with Dell. Yep. We saw it with, with, with pure and I, if our HPE I'd be saying, Hey, because the way the snowflake deal worked, you probably know this is your reading data into the cloud. The compute actually occurs in the cloud viral HB going snowflake saying we can separate compute and storage. Right. And we have GreenLake. We have on demand. Why don't we run the compute on-prem and make it a full class, first class citizen, right. For all of our customers data. And that would be really innovative. And I think Mongo would be another, they've got OnPrem. >>And the question is, how many, how many snowflake customers are telling snowflake? Can I run you on premise? And how much defo open years will they hear from that? Right? This is >>Why would they deal Dell? That >>Deal though, with that, they did a deal. >>I think they did that deal because the customer came to them and said, you don't exactly that deal. We're gonna spend the >>Snowflake >>Customers think crazy things happen, right? Even, even put an Oracle database in a Microsoft Azure data center, right. Would off who, what as >>Possible snowflake, >>Oracle. So on, Aw, the >>Snow, the snowflakes in the world have to make a decision. Dave on, is it all snowflake all the time? Because what the reality is, and I think, again, this comes back down to the, the track that HP could go up or down is gonna be about software. Open source is now the software industry. There's no such thing as proprietary software, in my opinion, relatively speaking, cloud scale and integrated, integrated integration software is proprietary. The workflows are proprietary. So if they can get that right with the partners, I would focus on that. I think they can tap open source, look at Amazon with open source. They sucked it up and they integrated it in. No, no. So integration is the deal, not >>Software first, but Snowflake's made the call. You were there, Lisa. They basically saying it's we have, you have to be in snowflake in order to get the governance and the scalability, all that other wonderful stuff. Oh, but we we'll do Apache iceberg. We'll we'll open it up. We'll do Python. Yeah. >>But you can't do it data clean room unless you are in snowflake. Exactly. Snowflake on snowflake. >>Exactly. >>But got it. Isn't that? What you heard from AWS all the time till they came out outposts, right? I mean, snowflake is a market leader for what they're doing. Right. So that they want to change their platform. I mean, kudos to them. They don't need to change the platform. They will be the last to change their platform to a ne to anything on premises. Right. But I think the trend already shows that it's going that way. >>Well, if you look at outpost is an signal, Dave, the success of outpost launched what four years ago, they announced it. >>What >>EKS is beating, what outpost is doing. Outpost is there. There's not a lot of buzz and talk to the insiders and the open source community, uh, EKS and containers. To your point mm-hmm <affirmative> is moving faster on, I won't say commodity hardware, but like could be white box or HP, Dell, whatever it's gonna be that scale differentiation and the edge story is, is a good one. And I think with what we're seeing in the market now it's the industrial edge. The back office was gen one cloud back office data center. Now it's hybrid. The focus will be industrial edge machine learning and AI, and they have it here. And there's some, some early conversations with, uh, I heard it from, uh, this morning, you guys interviewed, uh, uh, John Schultz, right? With the world economic 4k birth Butterfield. She was amazing. And then you had Justin bring up a Hoar, bring up quantum. Yes. That is a differentiator. >>HP. >>Yes. Yeah. You, they have the computing shops. They had the R and D can they bring it to the table >>As, as HPC, right. To what they Schultz for of uh, the frontier system. Right. So very impressed. >>So the ecosystem is the key for them is because that's how they're gonna fill the gaps. They can't, they can't only, >>They could, they could high HPC edge piece. I wouldn't count 'em out of that game yet. If you co-locate a box, I'll use the word box, particularly at a telco tower. That's a data center. Yep. Right. If done properly. Yep. So, you know, what outpost was supposed to do actually is a hybrid opportunity. Aruba >>Gives them a unique, >>But the key thing is right. It's a yin and yang, right? It's the ecosystem it's partners to bring those software workload. Absolutely. Right. But HPE has to keep the platform attractive enough. Right. And the key thing there is that you have this workload capability thing that you can bring things, which you've built yourself. I mean, look at the telcos right. Network function, visualization, thousands of man, years into these projects. Right. So if I can't bring it to your edge box, no, I'm not trying to get to your Xbox. Right. >>Hold I gotta ask you since in the Dave too, since you guys both here and Lisa, you know, I said on the opening, they have serious customers and those customers have serious problems, cyber security, ransomware. So yeah. I teach transformation now. Industrial transformation machine learning, check, check, check. Oh, sounds good. But at the end of the day, their customers have some serious problems. Right? Cyber, this is, this is high stakes poker. Yeah. What do you think HP's position for in the security? You mentioned containers, you got all this stuff, you got open source, supply chain, you have to left supply chain issues. What is their position with security? Cuz that's the big one. >>I, I think they have to have a mature attitude that customers expect from HPE. Right? I don't have to educate HP on security. So they have to have the partner offerings again. We're back at the ecosystem to have what probably you have. So bring your own security apart from what they have to have out of the box to do business with them. This is why the shocker this morning was back up in recovery coming. <laugh> it's kind like important for that. Right? Well >>That's, that's, that's more ransomware and the >>More skeleton skeletons in the closet there, which customers should check of course. But I think the expectations HP understands that and brings it along either from partner or natively. >>I, I think it's, I think it's services. I think point next is the point of integration for their security. That's why two thirds is software and services. A lot of that is services, right? You know, you need security, we'll help you get there. We people trust HP >>Here, but we have nothing against point next or any professional service. They're all hardworking. But if I will have to rely on humans for my cyber security strategy on a daily level, I'm getting gray hair and I little gray hair >>Red. Okay. I that's, >>But >>I think, but I do think that's the camera strategy. I mean, I'm sure there's a lot of that stuff that's beginning to be designed in, but I, my guess is a lot of it is services. >>Well, you got the Aruba. Part of the booth was packed. Aruba's there. You mentioned that earlier. Is that good enough? Because the word zero trust is kicked around a lot. On one hand, on the other hand, other conversations, it's all about trust. So supply chain and software is trusting trust, trust and verified. So you got this whole mentality of perimeter gone mentality. It's zero trust. And if you've got software trust, interesting thoughts there, how do you reconcile zero trust? And then I need trust. What's what's you? What are you seeing older on that? Because I ask people all the time, they're like, uh, I'm zero trust or is it trust? >>Yeah. The middle ground. Right? Trusted. The meantime people are man manipulating what's happening in your runtime containers. Right? So, uh, drift control is a new password there that you check what's in your runtime containers, which supposedly impenetrable, but people finding ways to hack them. So we'll see this cat and mouse game going on all the time. Yeah. Yeah. There's always gonna be the need for being in a secure, good environment from that perspective. Absolutely. But the key is edge has to be more than Aruba, right? If yeah. HV goes away and says, oh yeah, we can manage your edge with our Aruba devices. That's not enough. It's the virtual probability. And you said the important thing before it's about the data, right? Because the dirty secret of containers is yeah, I move the code, but what enterprise code works without data, right? You can't say as enterprise, okay, we're done for the day check tomorrow. We didn't persist your data, auditor customer. We don't have your data anymore. So filling a way to transport the data. And there just one last thought, right? They have a super interesting asset. They want break lands for the venerable map R right. Which wrote their own storage drivers and gives you the chance to potentially do something in that area, which I'm personally excited about. But we'll see what happens. >>I mean, I think the holy grail is can I, can I put my data into a cloud who's ever, you know, call it a super cloud and can I, is it secure? Is it governed? Can I share it and be confident that it's discoverable and that the, the person I give it to has the right to use it. Yeah. And, and it's the correct data. There's not like a zillion copies running. That's the holy grail. And I, I think the answer today is no, you can, you can do that maybe inside of AWS or maybe inside of Azure, look maybe certainly inside of snowflake, can you do that inside a GreenLake? Well, you probably can inside a GreenLake, but then when you put it into the cloud, is it cross cloud? Is it really out to the edge? And that's where it starts to break down, but that's where the work is to be done. That's >>The one Exide is in there already. Right. So men being men. Yeah. >>But okay. But it it's in there. Yeah. Okay. What do you do with it? Can you share that data? What can you actually automate governance? Right? Uh, is that data discoverable? Are there multiple copies of that data? What's the, you know, master copy. Here's >>A question. You guys, here's a question for you guys analyst, what do you think the psychology is of the CIO or CSO when HP comes into town with GreenLake, uh, and they say, what's your relationship with the hyperscalers? Cause I'm a CIO. I got my environment. I might be CapEx centric or Hey, I'm open model. Open-minded to an operating model. Every one of these enterprises has a cloud relationship. Yeah. Yeah. What's the dynamic. What do you think the psychology is of the CIO when they're rationalizing their, their trajectory, their architecture, cloud, native scale integration with HPE GreenLake or >>HP service. I think she or he hears defensiveness from HPE. I think she hears HPE or he hears HPE coming in and saying, you don't need to go to the cloud. You know, you could keep it right here. I, I don't think that's the right posture. I think it should be. We are your cloud. And we can manage whether it's OnPrem hybrid in AWS, Azure, Google, across those clouds. And we have an edge story that should be the vision that they put forth. That's the super cloud vision, but I don't hear it >>From these guys. What do you think psycho, do you agree with that? >>I'm totally to make, sorry to be boring, but I totally agree with, uh, Dave on that. Right? So the, the, the multi-cloud capability from a trusted large company has worked for anybody up and down the stack. Right? You can look historically for, uh, past layers with cloud Foundry, right? It's history vulnerable. You can look for DevOps of Hashi coop. You can look for database with MongoDB right now. So if HPE provides that data access, right, with all the problems of data gravity and egres cost and the workability, they will be doing really, really well, but we need to hear it more, right. We didn't hear much software today in the keynote. Right. >>Do they have a competitive offering vis-a-vis or Azure? >>The question is, will it be an HPE offering or will, or the software platform, one of the offerings and you as customer can plug and play, right. Will software be a differentiator for HP, right. And will be close, proprietary to the point to again, be open enough for it, or will they get that R and D format that, or will they just say, okay, ES MES here on the side, your choice, and you can use OpenShift or whatever, we don't matter. That's >>The, that's the key question. That's the key question. Is it because it is a competitive strategy? Is it highly differentiated? Oracle is a highly differentiated strategy, right? Is Dell highly differentiated? Eh, Dell differentiates based on its breadth. What? >>Right. Well, let's try for the control plane too. Dell wants to be an, >>Their, their vision is differentiated. Okay. But their execution today is not >>High. All right. Let me throw, let me throw this out at you then. I'm I'm, I'm sorry. I'm I'm HPE. I wanna be the glue layer. Is that, does that fly? >>What >>Do you mean? The group glue layer? I'll I wanna be, you can do Amazon, but I wanna be the glue layer between the clouds and our GreenLake will. >>What's the, what's the incremental value that, that glue provides, >>Provides comfort and reliability and control for the single pane of glass for AWS >>And comes back to the data. In my opinion. Yeah. >>There, there there's glue levels on the data level. Yeah. And there's glue levels on API level. Right. And there's different vendors in the different spaces. Right. Um, I think HPE will want to play on the data side. We heard lots of data stuff. We >>Hear that, >>But we have to see it. Exactly. >>Yeah. But it's, it's lacking today. And so, Hey, you know, you guys know better than I APIs can be fragile and they can be, there's a lot of diversity in terms of the quality of APIs and the documentation, how they work, how mature they are, what, how, what kind of performance they can provide and recoverability. And so just saying, oh wow. We are living the API economy. You know, the it's gonna take time to brew, chime in here. Hi. >><laugh> oh, so guys, you've all been covering HPE for a long time. You know, when Antonio stood up on stage three years ago and said by 2022, and here we are, we're gonna be delivering everything as a service. He's saying we've, we've done it, but, and we're a new company. Do you guys agree with that? >>Definitely. >>I, yes. Yes. With the caveat, I think, yes. The COVID pandemic slowed them down a lot because, um, that gave a tailwind to the hyperscalers, um, because of the, the force of massive O under forecasting working at home. I mean, everyone I talked to was like, no one forecasted a hundred percent work at home, the, um, the CapEx investments. So I think that was an opportunity that they'd be much farther along if there's no COVID people >>Thought it wasn't impossible. Yeah. But so we had the old work from home thing right. Where people trying to get people fired at IBM and Yahoo. Right. So I would've this question covering the HR side and my other hat on. Right. And I would ask CHS let's assume, because I didn't know about COVID shame on me. Right. I said, big California, earthquake breaks. Right. Nobody gets hurt, but all the buildings have to be retrofitted and checked for seism logic down. So everybody's working from home, ask CHS, what kind of productivity gap hit would you get by forcing everybody working from home with the office unsafe? So one, one gentleman, I won't know him, his name, he said 20% and the other one's going ha you're smoking. It's 40 50%. We need to be in the office. We need to meet it first night. And now we went for this exercise. Luckily not with the California. Right. Well, through the price of COVID and we've seen what it can do to, to productivity well, >>The productivity, but also the impact. So like with all the, um, stories we've done over two years, the people that want came out ahead were the ones that had good cloud action. They were already in the cloud. So I, I think they're definitely in different company in the sense of they, I give 'em a pass. I think they're definitely a new company and I'm not gonna judge 'em on. I think they're doing great. But I think pandemic definitely slowed 'em down that about >>It. So I have a different take on this. I think. So we've go back a little history. I mean, you' said this, I steal your line. Meg Whitman took one for the Silicon valley team. Right. She came in. I don't think she ever was excited that I, that you said, you said that, and I think you wrote >>Up, get tape on that one. She >>Had to figure out how do I deal with this mess? I have EDS. I got PC. >>She never should have spun off the PC, but >>Okay. But >>Me, >>Yeah, you can, you certainly could listen. Maybe, maybe Gerstner never should have gone all in on services and IBM would dominate something other than mainframes. They had think pads even for a while, but, but, but so she had that mess to deal with. She dealt with it and however, they dealt with it, Antonio came in, he, he, and he said, all right, we're gonna focus the company. And we're gonna focus the mission on not the machine. Remember those yeah. Presentations, but you just make your eyes glaze over. We're going all in on Azure service >>And edge. He was all on. >>We're gonna build our own cloud. We acquired Aruba. He made some acquisitions in HPC to help differentiate. Yep. And they are definitely a much more focused company now. And unfortunately I wish Antonio would CEO in 2015, cuz that's really when this should have started. >>Yeah. And then, and if you remember back then, Dave, we were interviewing Docker with DevOps teams. They had composability, they were on hybrid really early. I think they might have even coined the term hybrid before VMware tri-state credit for it. But they were first on hybrid. They had DevOps, they had infrastructure risk code. >>HPE had an HP had an awesome cloud team. Yeah. But, and then, and then they tried to go public cloud. Yeah. You know, and then, you know, just made them, I mean, it was just a mess. The focus >>Is there. I give them huge props. And I think, I think the GreenLake to me is exciting here because it's much better than it was two years ago. When, when we talked to, when we started, it's >>Starting to get real. >>It's, it's a real thing. And I think the, the tell will be partners. If they make that right, can pull their different >>Ecosystem, >>Their scale and their customers and fill the software gas with partners mm-hmm <affirmative> and then create that integration opportunity. It's gonna be a home run if they don't do that, they're gonna miss the operating, >>But they have to have their own to your point. They have to have their own software innovation. >>They have to good infrastructure ways to build applications. I don't wanna build with somebody else. I don't wanna take a Microsoft stack on open source stack. I'm not sure if it's gonna work with HP. So they have to have an app dev answer. I absolutely agree with that. And the, the big thing for the partners is, which is a good thing, right? Yep. HPE will not move into applications. Right? You don't have to have the fear of where Microsoft is with their vocal large. Right. If AWS kind of like comes up with APIs and manufacturing, right. Google the same thing with their vertical push. Right. So HPE will not have the CapEx, but >>Application, >>As I SV making them, the partner, the bonus of being able to on premise is an attractive >>Part. That's a great point. >>Hold. So that's an inflection point for next 12 months to watch what we see absolutely running on GreenLake. >>Yeah. And I think one of the things that came out of the, the last couple events this past year, and I'll bring this up, we'll table it and we'll watch it. And it's early in this, I think this is like even, not even the first inning, the machine learning AI impact to the industrial piece. I think we're gonna see a, a brand new era of accelerated digital transformation on the industrial physical world, back office, cloud data center, accounting, all the stuff. That's applications, the app, the real world from space to like robotics. I think that HP edge opportunity is gonna be visible and different. >>So guys, Antonio Neri is on tomorrow. This is only day one. If you can imagine this power panel on day one, can you imagine tomorrow? What is your last question for each of you? What is your, what, what question would you want to ask him tomorrow? Hold start with you. >>How is HPE winning in the long run? Because we know their on premise market will shrink, right? And they can out execute Dell. They can out execute Lenovo. They can out Cisco and get a bigger share of the shrinking market. But that's the long term strategy, right? So why should I buy HPE stock now and have a good return put in the, in the safe and forget about it and have a great return 20 years from now? What's the really long term strategy might be unfair because they, they ran in survival mode to a certain point out of the mass post equipment situation. But what is really the long term strategy? Is it more on the hardware side? Is it gonna go on the HPE, the frontier side? It's gonna be a DNA question, which I would ask Antonio. >>John, >>I would ask him what relative to the macro conditions relative to their customer base, I'd say, cuz the customers are the scoreboard. Can they create a value proposition with their, I use the Microsoft 365 example how they kind of went to the cloud. So my question would be Antonio, what is your core value proposition to CIOs out there who want to transform and take a step function, increase for value with HPE? Tell me that story. I wanna hear. And I don't want to hear, oh, we got a portfolio and no, what value are you enabling your customers to do? >>What and what should that value be? >>I think it's gonna be what we were kind of riffing on, which is you have to provide either what their product market fit needs are, which is, are you solving a problem? Is it a pain point is a growth driver. Uh, and what's the, what's that tailwind. And it's obviously we know at cloud we know edge. The story is great, but what's the value proposition. But by going with HPE, you get X, Y, and Z. If they can explain that clearly with real, so qualitative and quantitative data it's home >>Run. He had a great line of the analyst summit today where somebody asking questions, I'm just listening to the customer. So be ready for this Steve jobs photo, listening to the customer. You can't build something great listening to the customer. You'll be good for the next quarter. The next exponential >>Say, what are the customers saying? <laugh> >>So I would make an observation. And my question would, so my observation would be cloud is growing collectively at 35%. It's, you know, it's approaching 200 billion with a big, big four. If you include Alibaba, IBM has actually said, Hey, we're gonna gr they've promised 6% growth. Uh, Cisco I think is at eight or 9% growth. Dow's growing in double digits. Antonio and HPE have promised three to 4% growth. So what do you have to do to actually accelerate growth? Because three to 4%, my view, not enough to answer Holger's question is why should I buy HPE stock? Well, >>If they have product, if they have customer and there's demand and traction to me, that's going to drive the growth numbers. And I think the weak side of the forecast means that they don't have that fit yet. >>Yeah. So what has to happen for them to get above five, 6% growth? >>That's what we're gonna analyze. I mean, I, I mean, I don't have an answer for that. I wish I had a better answer. I'd tell them <laugh> but I feel, it feels, it feels like, you know, HP has an opportunity to say here's the new HPE. Yeah. Okay. And this is what we stand for. And here's the one thing that we're going to do that consistently drives value for you, the customer. And that's gonna have to come into some, either architectural cloud shift or a data thing, or we are your store for blank. >>All of the above. >>I guess the other question is, would, would you know, he won't answer a rude question, would suspending things like dividends and stock buybacks and putting it into R and D. I would definitely, if you have confidence in the market and you know what to do, why wouldn't you just accelerate R and D and put the money there? IBM, since 2007, IBM spent is the last stat. And I'm looking go in 2007, IBM way, outspent, Google, and Amazon and R and D and, and CapEx two, by the way. Yep. Subsequent to that, they've spent, I believe it's the numbers close to 200 billion on stock buyback and dividends. They could have owned cloud. And so look at this business, the technology business by and large is driven by innovation. Yeah. And so how do you innovate if >>You have I'm buying, I'm buying HP because they're reliable high quality and they have the outcomes that I want. Oh, >>Buy their products and services. I'm not sure I'd buy the stock. Yeah. >>Yeah. But she has to answer ultimately, because a public company. Right. So >>Right. It's this job. Yeah. >>Never a dull moment with the three of you around <laugh> guys. Thank you so much for sharing your insights, your, an analysis from day one. I can't imagine what day two is gonna bring tomorrow. Debut and I are gonna be anchoring here. We've got a jam packed day, lots going on, hearing from the ecosystem from leadership. As we mentioned, Antonio is gonna be Tony >>Alma Russo. I'm dying. Dr. >>EDMA as well as on the CTO gonna be another action pack day. I'm excited for it, guys. Thanks so much for sharing your insights and for letting me join this power panel. >>Great. Great to be here. >>Power panel plus me. All right. For Holger, John and Dave, I'm Lisa, you're watching the cube our day one coverage of HPE discover wraps right now. Don't go anywhere, cuz we'll see you tomorrow for day two, live from Vegas, have a good night.

>>The cube presents HPE discover 2022 brought to you by HPE. >>Hey everyone. Welcome to Las Vegas. It's the cube live on the show floor at HPE discover 2022, the first in person discover in three years, there are about 8,000 people here. The keynote was standing room only Lisa Martin here. I got a powerhouse group joining me for this keynote analysis. Dave ante joins us, Keith Townsend, John farrier, guys. Lot of news. It's all about HPE GreenLake. What were some of the things Dave, that stuck out to you? >>Well, I'll tell you right now, I gotta just quote, Antonio OIR said, Neri said four years ago, I declared that the enterprise of the future would be edge centric, cloud enabled and data driven. As a result, we launched HPE GreenLake. It kind of declared victory. Now I would say that what they're talking about and what they announced, I would consider table stakes. You know, I wish it started in 2014. I wish Antonio took over in 2015 instead of 2018, but I have to give credit, he's brought a focus and uh, and a, he think he's amped it up, John. I mean, if he's really prioritizing, uh, the, as a service they're going on in all in they're burning the boats, uh, and it's good. They got a lot of work to do. They >>Got a lot of work to do three years ago, John Antonio stood on this very stage saying we, and by 2022, we're gonna be delivering our entire portfolio as a service here we are with GreenLake. What I wanna get your thoughts on Keith's as well. >>Yeah. Well, first of all, I think that the crowded house was, uh, and a sign of people wanna come back together. So it's, to me, that was the first good news I saw, which was the HP community, their customer base. They're all here. They're glad to be back and forth. So it shows that they, their customer base it's resonating their value proposition of annual recurring revenue as a service plus the contract values with GreenLake are up. So this resonance with the customers, Dave, on the new operating model, that's a great check the box there. Um, I would say that I don't think HP's, as far along as Antonio had hopes, he'd be the pandemic was a setback. Um, but GreenLake is a real shining star. It's, uh, it's producing some green if you will money for them in terms of contracts, but they still got a lot more work to do because they're in a really interesting zone, Dave, because edge the cloud, although relevant and accurate where the, the shift is going, are they really there with, with the goods? And to me, I'm looking forward to seeing this discover if they have it or not. Certainly the messaging's good, but we're gonna UN UN unpeel that onion back and look at it. But >>Keith they're on the curve, right? At least they're on the cloud curve. >>They're absolutely on the curve. They have APIs, they have consistent developer experience. They announced the developer portal. They're developer centric. You can now consume your three par storage array services via a Terraform, uh, provider. They speak the language of cloud practitioners. You might struggle a little bit if I'm a small startup, you know, why would I look towards HPE? They kind of answered that a little bit. They had evil genius as a customer on stage, not a huge organization. A lot of the pushback they've been given is that if I may startup, I can simply go to a AWS portal, launch, a free trial service and run it. HPE kind of buried the lead. They now have, at least they announced preannounced the capability to, to trial GreenLake. So they're moving in the right direction. But you know, it's, it's it's table states. Well, >>Here's the thing. Here's the dynamic day that's going on. This is something that we've got got we're first of we've been covering HPE HP for now 11 years with the cube and look at Amazon's success and look at where Amazon's struggling. If you can say that they're having crossed overs to the enterprise, uh, cuz the enterprises are now just getting up to speed. You're seeing the rise of lack of talent. It certainly changing, uh, cyber security. You can't find talent. Kubernetes, good luck with that. Try to find someone. So you're seeing the enterprise aren't really geared up or staffed up for doing what I call, you know, high end cloud. So the rise of managed services is, is what we're seeing out there right now. You want Kubernetes clusters is a great set of managed services. You want other services? So that's the tell sign that the enterprises H HP's customers are now walking before they can run. They're crawling, they're now they're walking. So it's they have time to get in the Amazon lane in my opinion. Well, you >>Think about the hallmarks of cloud, obviously there's as a service, there's consumption based pricing. There's a developer, you know, friendliness, uh, there's ecosystem, which is really, really important. I think today, a lot of the ecosystem is partners, resellers and managed service providers. And to your point, Keith table stakes are things like single sign on being able to have, you know, a console being able to do it from a, from a URL to your point about startups is really interesting because that's one of the other hallmarks of cloud is you attract startups. And Lisa, we were at the snowflake summit and I asked the same question, can snowflake attract startups with their own super cloud. And what you saw was ecosystem partners developing in the snowflake cloud and monetizing. And that's something that we're waiting to see here. And I, I think they know >>You're suggesting way you suggesting that HP's gonna attract startups. >>Well, >>I, I think that's a sign if they can do that. That's a sign. And, and right now, I mean, you heard the example that Keith Keith gave. Uh, but, but not, not many. >>Yeah. I'm hoping that H I don't think HP is gonna ever attract startups, but I think the opportunity GreenLake affords the ecosystem is build clouds or purpose driven clouds around GreenLake. Mm-hmm <affirmative> whether it's the agreement with Equinix or all the cos and semi clouds, I think GreenLake gets most small CSPs, a leg up or 80% of the way there, where they can add that 20% of the IP and build services around GreenLake. And then that can attract the, the startup >>Or entrepreneurs. So the, the big question is, okay, where are these developers gonna come from? They could come from incumbents inside of companies. You know, the, the, the DevOps crowd from the enterprise, the really ops dev crowd. Right? I mean, yeah, don't you see that as a sort of a form of innovation startup, even though it's not a true startup. >>Yeah. Even though it's not, >>So Todd's making faces over there, we <laugh> >>Look, it, look it, they have >>Listen, if they don't, if they can't >>Do that, no, this is their focus is not startups. I agree with Keith on this one, they have to take care of business, home Depot. They have big customers and they have a lot of SMBs as well. They've got a great channel. H HP's got amazing infrastructure and, and client action going on. They gotta get the operating model, right job one as a service ARR, and then contract value and, and nail that with GreenLake. >>Who's their ideal customer profile. >>Their ideal is their install base. Look what Microsoft did with 365, they were going down. Their stock price was 26. At one point go to the, they went to the cloud 365, moved everything to the cloud and look at the success they're having. HP has the same kind of installed base. They gotta bring them along. They gotta get the operating model, right. And the developers that they're targeting are the ones inside the company and, or manage services that they're gonna go to the ecosystem for. That's where the cloud native comes in. That's where thing kind of comes together. So to me, I'm bullish on the operating model, but I'm skeptical that HP can get that cloud native developer. I haven't seen it yet. I'm looking for it. We're gonna look for it here. >>A key to that is going to be consistently. I, the, one of the things I'm looking for on the tech side, I, I hate to compare what HPE is doing to what VMware did with vCloud error years ago, but vCloud error on the outside looked >>Wonderful. Yes, >>It did. Once you tried to use it, it was just flaky underneath. And that's the part I'm looking to see customers pounding on it and saying, you know what API call after API I call, can I, uh, provision 10,000 pods a day? Does it scale down? Does it scale? And is it consistent? Is it >>Fragile Al roo she's co seasoned veteran? Uh, she was at V VMware cloud. She saw that movie. She gets a Mulligan, Dave. So I think her leadership is impressive. And I think she could bring a lot to the table to your point about don't make that same mistake and they gotta get this architecture, right. If they get the operating model right with GreenLake, they can double down on that and enable the developers that are driving the digital transformation. That to me is the, the key positions that they have to nail. And they do that. The rest is just fringe work. In my opinion, >>The reason why Alma was brought in, sorry, Lisa, it was, and then you gotta chime in here was to really build out that platform so that internal people at HPE can actually build value on top of it and the ecosystem that's her priority. >>We're gonna hear a lot from the ecosystem in the next couple of days, but I wanna get your perspective on, you've been following HPE a long time, all three of you. What are some of the things that you're hearing right now that are differentiators? We were just at Dell technologies. We talking about apex. We saw the big announcement they had with snowflake. We were at snowflake two weeks ago. I wanna get all three of your opinions on what are you seeing? Where is HP leading? >>I mean, HPE and Dell will, both with Dell, with apex are go, they're both gonna differentiate with their strengths. And, you know, for Dell, that's their breadth and their, their portfolio. And for, for HPE, that's their sort of open posture. I mean, John, you, you know this well, uh, that's their, their ecosystem, which I know has to evolve. And to me, their focus, you know, Antonio laid out some of the key differentiators. I, I, I think some of them were kind of, you know, pushing the envelope a little bit. Uh, but, but I think they're focus on as a service burning the, the, the boats telling wall street, this is our business. I think that's their differentiator. Is that they're, they're all in. >>Yeah. I, I think they, they try to highlight it by re announcing their private cloud service. I don't even know why they needed to announce that they have a private cloud. GreenLake is a cloud it's is a private cloud >>With block storage, hit disaster recovery. It's like good >>With like everything you get. But I think the, the key is, is that all of that is available today and you can get it in all kinds of frame of, of formats and, and frames specifically, if I'm a customer and I wanna get outta the data center and you, you know, Dave, we go back and forth about this all the time, and I wanna repatriate some workloads to Kubernetes on prem. I don't need to spend up another data center. I can go to Equinix, get GreenLake min IO, object storage on the back end, HPE lighthouse, all those services that I need for Kubernetes and repatriate my workloads without buying a new data center. And I get it as a service. I can get that Dave from HPE GreenLake, Dell apex is on the way. The >>Other thing they're differentiating with Aruba, that's something that Dell doesn't have. Yeah. And, and that is their edge play, I think is stronger than >>Of the others. Mean the, to me, the differentiator for HP is their, their history. Their channel's amazing. They got great Salesforce and they have serious customers and they have serious customers that have serious problems, uh, cyber security, uh, infrastructure, the security paradigm's changed. Uh, the deployment is changed how they deploy applications in their customer base. So they gotta step up to that challenge. And I think their differentiator is gonna be their size, their field and their ability to bring that operating model. And the hybrid model is a steady state. That's clear multi-cloud is just hybrids stitched together, but hybrid cloud, which is basically on premises and cloud to edge operating model is the number one thing that they need to nail. And if they nail that right, they will have a poll position that they could accelerate on. And again, I'm really gonna be watching how well they could enable cloud native developers, okay. To build modern agile applications while solving those serious problems with those serious customers. So again, I think hybrids spun in their direction. I'm not gonna say they got lucky, cuz they've always been on the hybrid bandwagon since we've been covering them. But I thought they'd be for a long day, but they're lucky to have hybrid. That's good for them. And I think do what Microsoft did convert their customers over and they do that, right? >>I think the key to that is gonna be ecosystem. Again, the developers need to see, especially the data piece, they talk about the cloud operating model. I think they're really moving that direction. The data piece to me is the weakest. Like they'll, they'll make claims that we can do anything that the cloud can do. You can't run snowflake, can't run data bricks, can't run Mongo Atlas. So they gotta figure out that data layer and that's optionality of, of data stores. And they don't have that today. >>Yeah. They, they, they have an announcement coming and I can't pre-announce it, but they're, they've, I've deemed them against it. They have the vision, Emeral data services, their data fabric multi-protocol access is a great start. They need the data network behind it. They need the ability to build a super cloud, a across multiple cloud providers, bringing some Google infos love inside of, uh, right next to your data. They have the hardware, they have the infrastructure, but they don't have the services. >>That's a key thing. I think one, you just brought up great point, Keith, and that is, is that at the end of the day, Dave, we're in a market now where agility and speed can be accomplished by startups or any company and HP's customers. Okay. Can move fast too. Okay. And so whoever can extend that value. If HPE can enable value creation for their customers, that's gonna be truly their, their task at hand, they got the channel, they got some leverage, but at the end of the day, the customers have alternatives now and they can move faster to get the value that they need to solve their serious problems. Uh, like cyber, like scalable infrastructure, like infrastructures code, like data ops, like AI ops, it's all here. And it's all coming really fast. Can GreenLake carry the day. And >>By the way, everything we just said about GreenLake in terms of table stakes and everything else, it applies for Dell. >>Yeah, absolutely. >>No question. It does guys. We have, and jam packed three days. We're gonna be talking with the ecosystem. We're gonna be talking with HPE leaders with customers. You're gonna hear all of these, uh, all this information unpacked over the next three days. We will be right back with our first guest for Dave ante, Keith Townson and John furrier. I'm Lisa Martin. Our first guest joins us momentarily.