>>Hey everyone. Welcome back to the Cube's live coverage of snowflake summit 22. We are live at Caesar's forum in Vegas, Lisa Martin, with Dave ante, excited to welcome a VIP fresh from the keynote stage, the SAP, a product at snowflake Christian C Claman Christian. Thank you so much for joining us on the queue today. >>Thank you for having me very exciting. >>And thanks for bringing your energy, loved your keynote. I thought, wow. He is really excited about all of the announcements jam packed. We, and we didn't even get to see the entire keynote talk to us about, and, and for the audience, some of the things going on the product revenue in Q1 fiscal 23, 390 4 million, 85% growth, lot of momentum at snowflake. No doubt. >>So I think that the, the punch line is our innovation is if anything, gaining speed. Uh, we were over the moon excited to share many of these projects with customers and partners, cuz some of these efforts have been going on for multiple years. So, um, lots of interesting announcements across the board from making the existing workloads faster, but also we announced some new workloads getting into cyber security, getting into more transactional workloads with uni store. Um, so we're very excited. >>Well first time being back, this is the fourth summit, but the first time being back since 2019 a tremendous amount has changed for snowflake in that time, the IPO, the massive growth in customers, the massive growth in growth in customers with over 1 million in ARR, you talked about one of the things that clearly did not slow down during the last two years is innovation at snowflake. >>Yeah, that, that, that for, for sure, like, um, even though we, we had a, um, highly in the office culture, we did not miss a beat the moment that we said, Hey, let's all start doing zoom based calls. We, we did. So, uh, I dunno if you saw the, the first five minute minutes of my section in the keynote. Yeah. We, we originally talked about summarizing it and no we're gonna spend 40 minutes here. So we did a one minute clip and whatever gets flashed there. So no, the, the pace of innovation, I think it's second to none and maybe I'll highlight the something that we're very proud of. Snowflake is a single product, a single engine. So if we're making a query performance enhancement, it will help the cyber security workload and the low high concurrency, low latency workload. And eventually we're starting to see some of those enhancements all the way to uni store. So, so we get a lot of leverage out of our investments. What's >>Your favorite announcement? >>That's like picking children. Of course. Um, I think the native applications is the one that looks like, eh, I don't know about it on the surface, but it has the biggest potential to change everything like create an entire ecosystem of solutions for within a company or across companies that I don't know that we know what's possible. >>Well, I I've been saying for a while now that you have this application development stack over here, the database is kind of here and then you have the analytics and data pipeline stack. Those are those separate worlds. We, we talk about bringing data and AI and machine intelligence into applications. The only way that that is actually gonna move forward is if you bring those worlds together is a good example of that happening, um, within a proprietary framework, uh, it's probably gonna happen open source organically and you can sort of roll your own. Is that by design or is it just sort of happening? Well, >>The, the, they bring it all into a single platform obviously by design, cuz there is so much friction today on making all the pieces work together, which database do I use for transactions and how do I move data to my analytics system? And how do I keep system, uh, reference data in sync between the two? So, so it's complicated and our mission was remove all of this friction from, from, from the equation. Uh, the open source versus not the way we think about it is opensourcing open formats or even open APIs it's does it help us deliver the solution that we want for our customer? Does it help us solve their problems? In certain instances, it has done in the past and we've opened source frameworks in, in others. We mentioned at the keynote today, the, the integration of iceberg tables, that's an strong embrace of open technologies, but that does not mean that we want to continue to innovate in our formats. A lot of what you see in the open formats is because snowflake proprietary, uh, innovation. So, uh, we have a very clear philosophy around this. Well >>Like any cloud player, you have to bring open source tools in and make them available for your application developers. But take us through an example of, of uni store and specifically how you're embracing transaction data. What's a customer gonna actually do take us paint a picture >>For us. I I'm gonna give you a very simple use case, but I love it because it, it shows the power of the scenario today. When people are ingesting data into snowflake, you wanna do some book capping associating with those loads. So imagine I have, I dunno, a million files. How many of those files have I loaded? Imagine that one of those loads fail, how do you keep in sync? Whether the data made or not with your bookkeeping today, if you had to do it with a separate transactional database for the bookkeeping and the loading in, in snowflake, it is a lot of complexity for you to know what's where with uni store, you can just say, I'm gonna do the bookkeeping with these new table. It's called hybrid tables. The lows are transactional and all of this is a single transaction. So for, for anyone that has dealt with inconsistencies in database world, this is like a godsend. >>Okay. So my interpretation of that's all about what happens when something goes wrong >><laugh> which is a lot of the, everything about transactions. Yeah. It's what happens when goes wrong and goes wrong. Doesn't mean failures like goes wrong is when you're debiting money from your bank account, not having enough balance that counts as go wrong and the transactions should be aborted. So yes, transactions are all about conflict management and we're simplifying that in a broader set of use cases >>And, and in recovery. So you're, you're in fast recovery. So you're, you're the, the business impact of what you're doing is to sort of simplify that process. Is that the easy way to >>Boil down? Pretty much everything we do is about simplification. Like we, we we've seen organizations are large focusing on wrestling infrastructure as opposed to what are the business problems for a Frank who reference something that, that, that I believe very much in like, which is mission alignment. We are working on helping our customers achieve what they're set out to achieve, not giving them more technology for them to their goal to become, to wrestle the infrastructure. So it's all about ease of use all about simplification removal, friction, >>Just so if I may, so mission alignment, you know, you always hear about technology companies that, you know, provide infrastructure or a service, and then the customer takes that and, and, you know, monetizes it pretty much on their own. What the big change that I'm discerning from these announcements is you're talking about directly monetizing and participating in that monetization as a technology partner, but also the marketplace as well. >>Correct. And I would say in some ways this is not new. This has been happening for the last couple of years with data. Like if you just saw our industry data cloud launches, the financial services cloud, it comes with data providers that help you achieve specific outcomes on a specific industry. Mm-hmm <affirmative> what we're doing now is saying, it's not just data. Maybe it's some business logic, maybe it's some machine learning, maybe it's some user interface. So I think we're just turning the knob on collaboration and it's a continuation of what we've been doing. >>Talk a little bit more about mission alignment. When I heard Frank, Sweetman talk about that this morning. I always love that when I hear cultural alignment with organizations, but as you just said, it's really about enabling our customers to deliver outcomes to their customers as the SVP product. Can you, uh, talk a little bit about how the customers are influencing the product roadmap, the innovations and the speed with which things are coming out at snowflake? >>Yeah, so great question. We have several organizations at snowflake that are organized by vertical by industry. So the, the major sales organization is part of ed that the marketplace business development team is organized like that. We have a separate team that provides top leadership by industry vertical, um, globally. And then even within our solution engineering, there is verticals. So we have a longitudinal view of all the different functions and what do we need to do to achieve a set of use cases in a vertical? And all of those functions are in con constant communication with us on this is where the product is, um, seeing an opportunity or could do better for that vertical. So yeah, I can tell you, and obviously we love when, when there's alignment between those, but that's not always the case. You heard us talk about clean rooms now for some time, clean rooms are applicable to almost any industry, but it's red hot for media and advertising, third party, cookie deprecation, and all of that. So we, we get to, to see that lens, that our innovation is informed by industries. >>So we, we're seeing, obviously the evolution of snowflake we talked about in the keynotes today, you guys talked about 2019 and, you know, pre 2019, even it was to me anyway, your first phase was, Hey, we got a simpler EDW. You know, we're gonna pick that off and put it in the cloud and make it elastic and separate compute from storage, all that kind of cool stuff. And then during the pandemic, it was really IPO, but also the data cloud concept, you sort of laid that vision out. And now you're talking about application development, monetization, what I call the super cloud that layer. Right. Okay. So I, are >>You determin it best? >>Yes. You talk about this, uh, these announcements, how they fit into that larger vision where you're >>Going. Great question. The, the, the notion of the data cloud has not changed one bit. The data cloud thesis is that we want to provide amazing technology for our customers, but also facilitate collaboration and content exchange VR platform. And all that we did today is expand what that content can be. It's not just data or little helper function, it's entire applications, entire experiences. That is the, the summing up the, the, the impact of our announcements today. That, that that's the end of it. So it's still about the data cloud. >>So what is impressive to me is that you guys wouldn't couldn't have a company without the hyperscalers, right? It would be a lot different, right? So you built on top of that and, and now you have your customers building their own super clouds. I call it, I get a lot of grief for that term it's but the, the, the big area of criticism I get is, ah, that's just SAS. And I'm like, no, it's not, no, uh, I, I is everybody public who's announcing stuff. I, I better be careful, but you have customers that are actually building services, taking their data, their tooling, their proprietary information, and putting it on the snowflake data cloud and building their own clouds. Yeah. That's different. Then that's not multi-cloud, which is I can run on a different cloud and it's not, is it sass? If it feels like it's something new from a, from your perspective, is, is it different? >>I, I, I love that you called out that running on all clouds is not what we do right. This days, everyone is multi-cloud, you, you run on a VM or a container, and I multi-cloud check, no, we have a single platform that does multi-region multi-cloud but also cross region cross cloud globally, that that is the essence of what we're doing. So it, it is enabling new capabilities. >>I've I've also said, you know, in many respects, the super cloud hides, the underlying complexity, you think about things like exploiting graviton and a developer. Doesn't need to worry about that. You're gonna worry about that. Uh, but at the same time, they, the, as you get into the develop, the world of application development, some of your developers may want access to some of those cloud primitives. Are you providing both? What's the strategy there? >>Generally not in some areas, we, we, we, I would say bleed through some details that are material, but think of the reality of someone that wants to build a solution, it's really difficult to build an awesome solution in one cloud, Hey, you need to do this. What's the latest instance, and is gravity tank gonna help you or not all of that. Now do it for another one and then do it for another one. And I can tell you it's really difficult because we go through that exercise. Snowflake pouring to a new cloud is somewhere between one and two years of effort and not, not a small number of people because you're looking at security models and storage models. So that's the value that we give to anyone know, wants to build a solution and target customers in all three clouds. I >>Mean, people are still gonna do it themselves, but they're gonna spend a lot more and they're gonna lose their focus on what their real business is. And there'll still be that. I think that D DIY market is enormous for you guys, huge >>Opportunity. And there's also the question on what is the cost of that analysis and that effort. And can we amortize it on behalf of all of our customers? Like we talk about graviton, we have not talked about the many things that we evaluated that were not better price performance for our customers. That evaluation happened. That value was delivered by not moving there. >>And when you do it yourself, the curve looks like, okay, Hey, we can do it ourselves. We can make it pretty Inex. And then, and then the costs are gonna decline, but what really happens, like developing a mobile app, you gotta maintain it. And then if you don't have the scale and you don't have the engineering resources, you're just, the, the costs are gonna continue to go through the roof. I, >>I, I love that you compare it to mobile apps. Like, yeah. I still don't understand why every company that wants to build an app has to build two <laugh>. They got it. Yeah. There is no super cloud for the phone. >>Right. >>That's sort of our, our, our broad vision. Not yet. Not, not the phone, but the super cloud. Yeah, >>Yeah, absolutely. >>You >>Get it. This is, and you look out the ecosystem here. I mean, what a difference that you've been pointing this out, Lisa from, from, from 2019, a lot of buzz, it's all about innovation. You see this at, at thing at the reinvent is like the super bowl obviously. And you see that and it used to be, oh, how is, how is AWS gonna compete with snowflake and separate compute with stores? That's I, I feel like in a large way, that's all gone. It's like, okay, how do we like rise the whole, the whole industry? And that's really where the innovation is. >>We have an amazing partnership with AWS and they benefit from what we do. Yes. There's some competitive elements, but we're changing so many things creating so much opportunity that we're more aligned than not. Yeah. >>Last question for you is continuing on the part AWS partnership front, how does a partner like AWS and other partners, how do they fit into the data cloud narrative that you're talking about to customers? >>I would say that other than the one or two teams that are directly competitive, the rest of their teams are part of in data cloud. Like, uh, our relationship with SageMaker as an example is amazing. And a lot of what we wanna deliver to our customers is choice around machine learning, frameworks and tools. And they're part of the data cloud. We're working with them on how do you push down computation to avoid getting data out, to reinforce governance? So I, I would say that and, and go look at it that they have a hundred and something teams. So if two teams out of hundreds, uh, are, are the competitive element, we are largely aligned. And they're part of data cloud. >>Yeah. I mean, you, your customers consume a lot of compute and storage for, >>For a lot. Yes. >>AWS and, and also, you know, increasingly Azure and, and Google. I mean, it's, um, pretty amazing times, uh, Christian, I want to ask you about, um, couple of terms. Uh, one term that came up a couple of times today in Frank's keynote, he said, I'm not gonna call it a data mesh out kind of out of respect for the purists, which is cool, I thought, but then you had a customer stand up Geico and said, we're building a data. Mesh JPMC is, is speaking at this event, building a data mesh. And I look at things through that prism and say, okay, data mesh is about, you know, decentralization. Some, I I'd be curious as to whether or not you tick that box, but it's about building data products. It's about, uh, uh, self-service infrastructure. And it's about automated computational governance. You are actually tipping a lot of the ticking, a lot of those boxes and, and Mike, I guess the big one is, are, are you building a bigger walled garden? But I, I think you would say, no, it's a, it's a giant distributed network, but, but what, what, what do you say to that? We, >>The latter, the latter, yeah, giant distributed, open cloud and open in the sense that we want anyone to plug in and, and someone can say, well, but I cannot read your file formats. Sure. You can with what we announced today, but it's not about that. Our APIs are open. We have rest APIs. We have JDC ODC, probably most popular interfaces ever. Um, and we want everyone to be part of it. If anything, there's lots of areas that we would not want to go into ourselves cause we want partners and customers to go in there. So, no, we we're looking at a very broad ecosystem. We win based on the value created on top of the platform. Yeah. >>And I makes total sense to me. I mean, I think the imaculate conception of data mesh might be a purely open source version of snowflake. I just don't see that happening anytime soon. And so I, I think you're gonna, you are, I wrote about this creating a defacto standard and >>Exactly, and, and I don't like to get into the terminology that, oh, is the data measure? Not, no go look at the concepts like people used to say, but snowflake is not a data lake. Okay. What is the data lake? It's just a pattern. And if you follow the pattern and you can do it, that's fine. Then there's the, uh, emotional quasi-religious overlay open versus not, I think that's a choice. Not necessarily the concept, >>It's a moving target. I mean, I Unix used to be open. You know, that was the, I agree. Now, the reason why I do think the data mesh conversation is important is because Shaak Dani, when she defined data mesh, she pointed out in my view. Anyway, the problems of getting value outta data is that you go through these hyper specialized teams and they're they're blockers in the organization. And I think you in many respects are attacking that. And it's an organizational issue. >>The, the insights in the pattern are a hundred percent value and aligned with what we do, which is they, you want some amount of centralization, some amount of decentralization living in harmony. Uh, yeah. I have no problem with, with terminology. >>And the governance piece is, is, is massive. Especially it's the, the picture's becoming much more clear. Um, whatever's in the data cloud is a first class citizen, right? And you give all these wonderful benefits. I mean, the interesting thing, what you're doing with Dell and, and pure, I, I asked you that on the analyst call, it's a start. You know, I, I, I mean, >>And I said it briefly in, in, in the keynote this morning, we're publishing a set of standard conformance tests. So any storage system can plug into data cloud. >>Yeah. >>And by the way, it's based on S three APIs, another defect of standard. Like it's not a standard, but everyone is emulating that. And we're plugging >>Into that. Yeah. Nobody's complaining against, against S3 API >>About it is a, oh, it's not a Apache project. We shouldn't, who cares. Everyone has standard horizon net. That's it? >>Well, we've seen the mistakes of the past with this. I mean, look at, look at Hadoop, right? There was this huge battle between, you know, Cloudera and Horton works and map, oh, map bar is proprietary. Oh, Horton works is purely open. Cloudera is open. They're, they're all gone now. I mean, not gone, but they're just, they didn't have it. Right. You know, they, they got unfocused. I go back to Frank's book. They were trying to do too much to, to too many of those, the, the, the zoo animals and you can't fund it all >>To be effective for us. It's very important. I can give you, I don't know, 20 announcements or 50 announcements from the conference, but they're all going a singular goal. And it's, this do not trade off governance of data with the ability to get value out of data. That's everything we do. >>And that's critical for every company in every industry these days that has to be a data company to be, to survive, to be competitive, to be able to extract value from data. If data's currency, how do I leverage a tool like snowflake to be able to extract insights from it that I can act on and create value for my organization, Geico was on stage this morning. Everyone knows Geico and their beloved, um, gecko. Yeah. Is there another customer that you had that you think really articulates the value of the data cloud and to Dave's point how snowflake is becoming that defacto standard data platform? >>Well, we had Goldman Goldman Sachs on stage as well today. And he, he, he, he mentioned it that people think of Goldman as investment banking and all of that, but no, at the heart of what they do, there's a lot of data. And how do they make better decisions? So I think we could run through 20 different examples cuz your premise is the most important. Everything is a data problem. If it is not a data problem, you're not collecting the right data and getting the sense that you could be getting. >>These guys are public, right. >>Adobe. >>Yeah. Right. Adobe's doing it. Yeah. I dunno if the other one is, I don't wanna say, I'll have to ask you off camera, but the other financial firm building a super cloud, right. <laugh> yeah. I call it super cloud. So let be taking advantage of uni store. Yeah. To bring different data types in and monetize it. That's to me, that's the future of data. That's that's been the holy grail, right. >>We, we tried to emphasize that this is, is not a, Hey six, six months ago. We decided to do this. No, this is years in the making mm-hmm <affirmative>, which is why we were so excited to finally share it. Cuz you don't wanna say three years from now, we're gonna have something. No, it was the, now we have it. We have it in preview and it's working at it is as close to the holy grail as it gets. >>Yeah. I mean, look, pressure's on Kristin. Let's face it. Enterprise data warehouse failed to live up to the promises. Uh, certainly the data lakes fail to deliver master data management, all that's a Hadoop, all that stuff. There was a lot of hype around that. And a lot of us got really excited. Me included and then customers spent and they were underwhelmed. Yeah. So you know, you, you, you gotta deliver, you say it, you gotta do it. >>And correct. And then the, the other thing is I would say all of those waves of technology, there was no real better choice. >>Right. They added value. I wouldn't >>Debate that. You have to give it a shot. Like when you've bought 20 different appliances and you have all these silos and someone sells you, Hey, Hadoop will unify it. It sounds good. Just didn't do it. >>Yeah. And no debate that it brought some value for those that were agree. Sophisticated enough to deploy it. And I agree. Yeah. But, but this is a whole different ball game. >>Oh, everything we want to do is democratize and simplify mm-hmm <affirmative> yeah. We could go build something that I don't know. 10 companies in the world could use. That's not the sweet spot. Like how do we advance like the, the state of value generation in the world? That's the scale that we're talking about is go make it easy, accessible for everyone. >>Governed >>Governance and imperative this these days it's law. Yes. So >>Yeah, you have to, but it's not, it's, that's a, that's a ch really difficult challenge to create what I'll call automated or computational governance in a federated manner. That's not trivial. >>And that's our thesis. Everything we're doing is snow park, big announcement today. Python. I I've had people tell me well, but Python should be easy to host the Python run time. Like you can do it. Like I think in a week it took us years. Why? Oh, secure. Oh, details a lot. And <inaudible> mentioned it like securing. That is no easy, uh, feed >>Christian. Thank you so much for joining Dave and me bringing your energy from the keynote stage to the cube, set, breaking down some of the major announcements that have come out today. There's no doubt that the flywheel of innovation at snowflake is alive well and moving quickly, >>Innovation is, uh, at an all time hat snowflake. Thank you for having me. All >>Right. Our pleasure Christian from our guest, Dave ante, Lisa Martin here live in Las Vegas at Caesar's forum covering snowflake summit 22. We right back with our next guest.

(upbeat music) >> Hello, this is Dave Valente with theCUBE, and one of the most gratifying aspects of my role as a host of "theCUBE TV" is I get to cover a wide range of topics. And quite often, we're able to bring to our program a level of expertise that allows us to more deeply explore and unpack some of the topics that we cover throughout the year. And one of our favorite topics, of course, is data. Now, in 2021, after being in isolation for the better part of two years, a group of industry analysts met up at AWS re:Invent and started a collaboration to look at the trends in data and predict what some likely outcomes will be for the coming year. And it resulted in a very popular session that we had last year focused on the future of data management. And I'm very excited and pleased to tell you that the 2023 edition of that predictions episode is back, and with me are five outstanding market analyst, Sanjeev Mohan of SanjMo, Tony Baer of dbInsight, Carl Olofson from IDC, Dave Menninger from Ventana Research, and Doug Henschen, VP and Principal Analyst at Constellation Research. Now, what is it that we're calling you, guys? A data pack like the rat pack? No, no, no, no, that's not it. It's the data crowd, the data crowd, and the crowd includes some of the best minds in the data analyst community. They'll discuss how data management is evolving and what listeners should prepare for in 2023. Guys, welcome back. Great to see you. >> Good to be here. >> Thank you. >> Thanks, Dave. (Tony and Dave faintly speaks) >> All right, before we get into 2023 predictions, we thought it'd be good to do a look back at how we did in 2022 and give a transparent assessment of those predictions. So, let's get right into it. We're going to bring these up here, the predictions from 2022, they're color-coded red, yellow, and green to signify the degree of accuracy. And I'm pleased to report there's no red. Well, maybe some of you will want to debate that grading system. But as always, we want to be open, so you can decide for yourselves. So, we're going to ask each analyst to review their 2022 prediction and explain their rating and what evidence they have that led them to their conclusion. So, Sanjeev, please kick it off. Your prediction was data governance becomes key. I know that's going to knock you guys over, but elaborate, because you had more detail when you double click on that. >> Yeah, absolutely. Thank you so much, Dave, for having us on the show today. And we self-graded ourselves. I could have very easily made my prediction from last year green, but I mentioned why I left it as yellow. I totally fully believe that data governance was in a renaissance in 2022. And why do I say that? You have to look no further than AWS launching its own data catalog called DataZone. Before that, mid-year, we saw Unity Catalog from Databricks went GA. So, overall, I saw there was tremendous movement. When you see these big players launching a new data catalog, you know that they want to be in this space. And this space is highly critical to everything that I feel we will talk about in today's call. Also, if you look at established players, I spoke at Collibra's conference, data.world, work closely with Alation, Informatica, a bunch of other companies, they all added tremendous new capabilities. So, it did become key. The reason I left it as yellow is because I had made a prediction that Collibra would go IPO, and it did not. And I don't think anyone is going IPO right now. The market is really, really down, the funding in VC IPO market. But other than that, data governance had a banner year in 2022. >> Yeah. Well, thank you for that. And of course, you saw data clean rooms being announced at AWS re:Invent, so more evidence. And I like how the fact that you included in your predictions some things that were binary, so you dinged yourself there. So, good job. Okay, Tony Baer, you're up next. Data mesh hits reality check. As you see here, you've given yourself a bright green thumbs up. (Tony laughing) Okay. Let's hear why you feel that was the case. What do you mean by reality check? >> Okay. Thanks, Dave, for having us back again. This is something I just wrote and just tried to get away from, and this just a topic just won't go away. I did speak with a number of folks, early adopters and non-adopters during the year. And I did find that basically that it pretty much validated what I was expecting, which was that there was a lot more, this has now become a front burner issue. And if I had any doubt in my mind, the evidence I would point to is what was originally intended to be a throwaway post on LinkedIn, which I just quickly scribbled down the night before leaving for re:Invent. I was packing at the time, and for some reason, I was doing Google search on data mesh. And I happened to have tripped across this ridiculous article, I will not say where, because it doesn't deserve any publicity, about the eight (Dave laughing) best data mesh software companies of 2022. (Tony laughing) One of my predictions was that you'd see data mesh washing. And I just quickly just hopped on that maybe three sentences and wrote it at about a couple minutes saying this is hogwash, essentially. (laughs) And that just reun... And then, I left for re:Invent. And the next night, when I got into my Vegas hotel room, I clicked on my computer. I saw a 15,000 hits on that post, which was the most hits of any single post I put all year. And the responses were wildly pro and con. So, it pretty much validates my expectation in that data mesh really did hit a lot more scrutiny over this past year. >> Yeah, thank you for that. I remember that article. I remember rolling my eyes when I saw it, and then I recently, (Tony laughing) I talked to Walmart and they actually invoked Martin Fowler and they said that they're working through their data mesh. So, it takes a really lot of thought, and it really, as we've talked about, is really as much an organizational construct. You're not buying data mesh >> Bingo. >> to your point. Okay. Thank you, Tony. Carl Olofson, here we go. You've graded yourself a yellow in the prediction of graph databases. Take off. Please elaborate. >> Yeah, sure. So, I realized in looking at the prediction that it seemed to imply that graph databases could be a major factor in the data world in 2022, which obviously didn't become the case. It was an error on my part in that I should have said it in the right context. It's really a three to five-year time period that graph databases will really become significant, because they still need accepted methodologies that can be applied in a business context as well as proper tools in order for people to be able to use them seriously. But I stand by the idea that it is taking off, because for one thing, Neo4j, which is the leading independent graph database provider, had a very good year. And also, we're seeing interesting developments in terms of things like AWS with Neptune and with Oracle providing graph support in Oracle database this past year. Those things are, as I said, growing gradually. There are other companies like TigerGraph and so forth, that deserve watching as well. But as far as becoming mainstream, it's going to be a few years before we get all the elements together to make that happen. Like any new technology, you have to create an environment in which ordinary people without a whole ton of technical training can actually apply the technology to solve business problems. >> Yeah, thank you for that. These specialized databases, graph databases, time series databases, you see them embedded into mainstream data platforms, but there's a place for these specialized databases, I would suspect we're going to see new types of databases emerge with all this cloud sprawl that we have and maybe to the edge. >> Well, part of it is that it's not as specialized as you might think it. You can apply graphs to great many workloads and use cases. It's just that people have yet to fully explore and discover what those are. >> Yeah. >> And so, it's going to be a process. (laughs) >> All right, Dave Menninger, streaming data permeates the landscape. You gave yourself a yellow. Why? >> Well, I couldn't think of a appropriate combination of yellow and green. Maybe I should have used chartreuse, (Dave laughing) but I was probably a little hard on myself making it yellow. This is another type of specialized data processing like Carl was talking about graph databases is a stream processing, and nearly every data platform offers streaming capabilities now. Often, it's based on Kafka. If you look at Confluent, their revenues have grown at more than 50%, continue to grow at more than 50% a year. They're expected to do more than half a billion dollars in revenue this year. But the thing that hasn't happened yet, and to be honest, they didn't necessarily expect it to happen in one year, is that streaming hasn't become the default way in which we deal with data. It's still a sidecar to data at rest. And I do expect that we'll continue to see streaming become more and more mainstream. I do expect perhaps in the five-year timeframe that we will first deal with data as streaming and then at rest, but the worlds are starting to merge. And we even see some vendors bringing products to market, such as K2View, Hazelcast, and RisingWave Labs. So, in addition to all those core data platform vendors adding these capabilities, there are new vendors approaching this market as well. >> I like the tough grading system, and it's not trivial. And when you talk to practitioners doing this stuff, there's still some complications in the data pipeline. And so, but I think, you're right, it probably was a yellow plus. Doug Henschen, data lakehouses will emerge as dominant. When you talk to people about lakehouses, practitioners, they all use that term. They certainly use the term data lake, but now, they're using lakehouse more and more. What's your thoughts on here? Why the green? What's your evidence there? >> Well, I think, I was accurate. I spoke about it specifically as something that vendors would be pursuing. And we saw yet more lakehouse advocacy in 2022. Google introduced its BigLake service alongside BigQuery. Salesforce introduced Genie, which is really a lakehouse architecture. And it was a safe prediction to say vendors are going to be pursuing this in that AWS, Cloudera, Databricks, Microsoft, Oracle, SAP, Salesforce now, IBM, all advocate this idea of a single platform for all of your data. Now, the trend was also supported in 2023, in that we saw a big embrace of Apache Iceberg in 2022. That's a structured table format. It's used with these lakehouse platforms. It's open, so it ensures portability and it also ensures performance. And that's a structured table that helps with the warehouse side performance. But among those announcements, Snowflake, Google, Cloud Era, SAP, Salesforce, IBM, all embraced Iceberg. But keep in mind, again, I'm talking about this as something that vendors are pursuing as their approach. So, they're advocating end users. It's very cutting edge. I'd say the top, leading edge, 5% of of companies have really embraced the lakehouse. I think, we're now seeing the fast followers, the next 20 to 25% of firms embracing this idea and embracing a lakehouse architecture. I recall Christian Kleinerman at the big Snowflake event last summer, making the announcement about Iceberg, and he asked for a show of hands for any of you in the audience at the keynote, have you heard of Iceberg? And just a smattering of hands went up. So, the vendors are ahead of the curve. They're pushing this trend, and we're now seeing a little bit more mainstream uptake. >> Good. Doug, I was there. It was you, me, and I think, two other hands were up. That was just humorous. (Doug laughing) All right, well, so I liked the fact that we had some yellow and some green. When you think about these things, there's the prediction itself. Did it come true or not? There are the sub predictions that you guys make, and of course, the degree of difficulty. So, thank you for that open assessment. All right, let's get into the 2023 predictions. Let's bring up the predictions. Sanjeev, you're going first. You've got a prediction around unified metadata. What's the prediction, please? >> So, my prediction is that metadata space is currently a mess. It needs to get unified. There are too many use cases of metadata, which are being addressed by disparate systems. For example, data quality has become really big in the last couple of years, data observability, the whole catalog space is actually, people don't like to use the word data catalog anymore, because data catalog sounds like it's a catalog, a museum, if you may, of metadata that you go and admire. So, what I'm saying is that in 2023, we will see that metadata will become the driving force behind things like data ops, things like orchestration of tasks using metadata, not rules. Not saying that if this fails, then do this, if this succeeds, go do that. But it's like getting to the metadata level, and then making a decision as to what to orchestrate, what to automate, how to do data quality check, data observability. So, this space is starting to gel, and I see there'll be more maturation in the metadata space. Even security privacy, some of these topics, which are handled separately. And I'm just talking about data security and data privacy. I'm not talking about infrastructure security. These also need to merge into a unified metadata management piece with some knowledge graph, semantic layer on top, so you can do analytics on it. So, it's no longer something that sits on the side, it's limited in its scope. It is actually the very engine, the very glue that is going to connect data producers and consumers. >> Great. Thank you for that. Doug. Doug Henschen, any thoughts on what Sanjeev just said? Do you agree? Do you disagree? >> Well, I agree with many aspects of what he says. I think, there's a huge opportunity for consolidation and streamlining of these as aspects of governance. Last year, Sanjeev, you said something like, we'll see more people using catalogs than BI. And I have to disagree. I don't think this is a category that's headed for mainstream adoption. It's a behind the scenes activity for the wonky few, or better yet, companies want machine learning and automation to take care of these messy details. We've seen these waves of management technologies, some of the latest data observability, customer data platform, but they failed to sweep away all the earlier investments in data quality and master data management. So, yes, I hope the latest tech offers, glimmers that there's going to be a better, cleaner way of addressing these things. But to my mind, the business leaders, including the CIO, only want to spend as much time and effort and money and resources on these sorts of things to avoid getting breached, ending up in headlines, getting fired or going to jail. So, vendors bring on the ML and AI smarts and the automation of these sorts of activities. >> So, if I may say something, the reason why we have this dichotomy between data catalog and the BI vendors is because data catalogs are very soon, not going to be standalone products, in my opinion. They're going to get embedded. So, when you use a BI tool, you'll actually use the catalog to find out what is it that you want to do, whether you are looking for data or you're looking for an existing dashboard. So, the catalog becomes embedded into the BI tool. >> Hey, Dave Menninger, sometimes you have some data in your back pocket. Do you have any stats (chuckles) on this topic? >> No, I'm glad you asked, because I'm going to... Now, data catalogs are something that's interesting. Sanjeev made a statement that data catalogs are falling out of favor. I don't care what you call them. They're valuable to organizations. Our research shows that organizations that have adequate data catalog technologies are three times more likely to express satisfaction with their analytics for just the reasons that Sanjeev was talking about. You can find what you want, you know you're getting the right information, you know whether or not it's trusted. So, those are good things. So, we expect to see the capabilities, whether it's embedded or separate. We expect to see those capabilities continue to permeate the market. >> And a lot of those catalogs are driven now by machine learning and things. So, they're learning from those patterns of usage by people when people use the data. (airy laughs) >> All right. Okay. Thank you, guys. All right. Let's move on to the next one. Tony Bear, let's bring up the predictions. You got something in here about the modern data stack. We need to rethink it. Is the modern data stack getting long at the tooth? Is it not so modern anymore? >> I think, in a way, it's got almost too modern. It's gotten too, I don't know if it's being long in the tooth, but it is getting long. The modern data stack, it's traditionally been defined as basically you have the data platform, which would be the operational database and the data warehouse. And in between, you have all the tools that are necessary to essentially get that data from the operational realm or the streaming realm for that matter into basically the data warehouse, or as we might be seeing more and more, the data lakehouse. And I think, what's important here is that, or I think, we have seen a lot of progress, and this would be in the cloud, is with the SaaS services. And especially you see that in the modern data stack, which is like all these players, not just the MongoDBs or the Oracles or the Amazons have their database platforms. You see they have the Informatica's, and all the other players there in Fivetrans have their own SaaS services. And within those SaaS services, you get a certain degree of simplicity, which is it takes all the housekeeping off the shoulders of the customers. That's a good thing. The problem is that what we're getting to unfortunately is what I would call lots of islands of simplicity, which means that it leads it (Dave laughing) to the customer to have to integrate or put all that stuff together. It's a complex tool chain. And so, what we really need to think about here, we have too many pieces. And going back to the discussion of catalogs, it's like we have so many catalogs out there, which one do we use? 'Cause chances are of most organizations do not rely on a single catalog at this point. What I'm calling on all the data providers or all the SaaS service providers, is to literally get it together and essentially make this modern data stack less of a stack, make it more of a blending of an end-to-end solution. And that can come in a number of different ways. Part of it is that we're data platform providers have been adding services that are adjacent. And there's some very good examples of this. We've seen progress over the past year or so. For instance, MongoDB integrating search. It's a very common, I guess, sort of tool that basically, that the applications that are developed on MongoDB use, so MongoDB then built it into the database rather than requiring an extra elastic search or open search stack. Amazon just... AWS just did the zero-ETL, which is a first step towards simplifying the process from going from Aurora to Redshift. You've seen same thing with Google, BigQuery integrating basically streaming pipelines. And you're seeing also a lot of movement in database machine learning. So, there's some good moves in this direction. I expect to see more than this year. Part of it's from basically the SaaS platform is adding some functionality. But I also see more importantly, because you're never going to get... This is like asking your data team and your developers, herding cats to standardizing the same tool. In most organizations, that is not going to happen. So, take a look at the most popular combinations of tools and start to come up with some pre-built integrations and pre-built orchestrations, and offer some promotional pricing, maybe not quite two for, but in other words, get two products for the price of two services or for the price of one and a half. I see a lot of potential for this. And it's to me, if the class was to simplify things, this is the next logical step and I expect to see more of this here. >> Yeah, and you see in Oracle, MySQL heat wave, yet another example of eliminating that ETL. Carl Olofson, today, if you think about the data stack and the application stack, they're largely separate. Do you have any thoughts on how that's going to play out? Does that play into this prediction? What do you think? >> Well, I think, that the... I really like Tony's phrase, islands of simplification. It really says (Tony chuckles) what's going on here, which is that all these different vendors you ask about, about how these stacks work. All these different vendors have their own stack vision. And you can... One application group is going to use one, and another application group is going to use another. And some people will say, let's go to, like you go to a Informatica conference and they say, we should be the center of your universe, but you can't connect everything in your universe to Informatica, so you need to use other things. So, the challenge is how do we make those things work together? As Tony has said, and I totally agree, we're never going to get to the point where people standardize on one organizing system. So, the alternative is to have metadata that can be shared amongst those systems and protocols that allow those systems to coordinate their operations. This is standard stuff. It's not easy. But the motive for the vendors is that they can become more active critical players in the enterprise. And of course, the motive for the customer is that things will run better and more completely. So, I've been looking at this in terms of two kinds of metadata. One is the meaning metadata, which says what data can be put together. The other is the operational metadata, which says basically where did it come from? Who created it? What's its current state? What's the security level? Et cetera, et cetera, et cetera. The good news is the operational stuff can actually be done automatically, whereas the meaning stuff requires some human intervention. And as we've already heard from, was it Doug, I think, people are disinclined to put a lot of definition into meaning metadata. So, that may be the harder one, but coordination is key. This problem has been with us forever, but with the addition of new data sources, with streaming data with data in different formats, the whole thing has, it's been like what a customer of mine used to say, "I understand your product can make my system run faster, but right now I just feel I'm putting my problems on roller skates. (chuckles) I don't need that to accelerate what's already not working." >> Excellent. Okay, Carl, let's stay with you. I remember in the early days of the big data movement, Hadoop movement, NoSQL was the big thing. And I remember Amr Awadallah said to us in theCUBE that SQL is the killer app for big data. So, your prediction here, if we bring that up is SQL is back. Please elaborate. >> Yeah. So, of course, some people would say, well, it never left. Actually, that's probably closer to true, but in the perception of the marketplace, there's been all this noise about alternative ways of storing, retrieving data, whether it's in key value stores or document databases and so forth. We're getting a lot of messaging that for a while had persuaded people that, oh, we're not going to do analytics in SQL anymore. We're going to use Spark for everything, except that only a handful of people know how to use Spark. Oh, well, that's a problem. Well, how about, and for ordinary conventional business analytics, Spark is like an over-engineered solution to the problem. SQL works just great. What's happened in the past couple years, and what's going to continue to happen is that SQL is insinuating itself into everything we're seeing. We're seeing all the major data lake providers offering SQL support, whether it's Databricks or... And of course, Snowflake is loving this, because that is what they do, and their success is certainly points to the success of SQL, even MongoDB. And we were all, I think, at the MongoDB conference where on one day, we hear SQL is dead. They're not teaching SQL in schools anymore, and this kind of thing. And then, a couple days later at the same conference, they announced we're adding a new analytic capability-based on SQL. But didn't you just say SQL is dead? So, the reality is that SQL is better understood than most other methods of certainly of retrieving and finding data in a data collection, no matter whether it happens to be relational or non-relational. And even in systems that are very non-relational, such as graph and document databases, their query languages are being built or extended to resemble SQL, because SQL is something people understand. >> Now, you remember when we were in high school and you had had to take the... Your debating in the class and you were forced to take one side and defend it. So, I was was at a Vertica conference one time up on stage with Curt Monash, and I had to take the NoSQL, the world is changing paradigm shift. And so just to be controversial, I said to him, Curt Monash, I said, who really needs acid compliance anyway? Tony Baer. And so, (chuckles) of course, his head exploded, but what are your thoughts (guests laughing) on all this? >> Well, my first thought is congratulations, Dave, for surviving being up on stage with Curt Monash. >> Amen. (group laughing) >> I definitely would concur with Carl. We actually are definitely seeing a SQL renaissance and if there's any proof of the pudding here, I see lakehouse is being icing on the cake. As Doug had predicted last year, now, (clears throat) for the record, I think, Doug was about a year ahead of time in his predictions that this year is really the year that I see (clears throat) the lakehouse ecosystems really firming up. You saw the first shots last year. But anyway, on this, data lakes will not go away. I've actually, I'm on the home stretch of doing a market, a landscape on the lakehouse. And lakehouse will not replace data lakes in terms of that. There is the need for those, data scientists who do know Python, who knows Spark, to go in there and basically do their thing without all the restrictions or the constraints of a pre-built, pre-designed table structure. I get that. Same thing for developing models. But on the other hand, there is huge need. Basically, (clears throat) maybe MongoDB was saying that we're not teaching SQL anymore. Well, maybe we have an oversupply of SQL developers. Well, I'm being facetious there, but there is a huge skills based in SQL. Analytics have been built on SQL. They came with lakehouse and why this really helps to fuel a SQL revival is that the core need in the data lake, what brought on the lakehouse was not so much SQL, it was a need for acid. And what was the best way to do it? It was through a relational table structure. So, the whole idea of acid in the lakehouse was not to turn it into a transaction database, but to make the data trusted, secure, and more granularly governed, where you could govern down to column and row level, which you really could not do in a data lake or a file system. So, while lakehouse can be queried in a manner, you can go in there with Python or whatever, it's built on a relational table structure. And so, for that end, for those types of data lakes, it becomes the end state. You cannot bypass that table structure as I learned the hard way during my research. So, the bottom line I'd say here is that lakehouse is proof that we're starting to see the revenge of the SQL nerds. (Dave chuckles) >> Excellent. Okay, let's bring up back up the predictions. Dave Menninger, this one's really thought-provoking and interesting. We're hearing things like data as code, new data applications, machines actually generating plans with no human involvement. And your prediction is the definition of data is expanding. What do you mean by that? >> So, I think, for too long, we've thought about data as the, I would say facts that we collect the readings off of devices and things like that, but data on its own is really insufficient. Organizations need to manipulate that data and examine derivatives of the data to really understand what's happening in their organization, why has it happened, and to project what might happen in the future. And my comment is that these data derivatives need to be supported and managed just like the data needs to be managed. We can't treat this as entirely separate. Think about all the governance discussions we've had. Think about the metadata discussions we've had. If you separate these things, now you've got more moving parts. We're talking about simplicity and simplifying the stack. So, if these things are treated separately, it creates much more complexity. I also think it creates a little bit of a myopic view on the part of the IT organizations that are acquiring these technologies. They need to think more broadly. So, for instance, metrics. Metric stores are becoming much more common part of the tooling that's part of a data platform. Similarly, feature stores are gaining traction. So, those are designed to promote the reuse and consistency across the AI and ML initiatives. The elements that are used in developing an AI or ML model. And let me go back to metrics and just clarify what I mean by that. So, any type of formula involving the data points. I'm distinguishing metrics from features that are used in AI and ML models. And the data platforms themselves are increasingly managing the models as an element of data. So, just like figuring out how to calculate a metric. Well, if you're going to have the features associated with an AI and ML model, you probably need to be managing the model that's associated with those features. The other element where I see expansion is around external data. Organizations for decades have been focused on the data that they generate within their own organization. We see more and more of these platforms acquiring and publishing data to external third-party sources, whether they're within some sort of a partner ecosystem or whether it's a commercial distribution of that information. And our research shows that when organizations use external data, they derive even more benefits from the various analyses that they're conducting. And the last great frontier in my opinion on this expanding world of data is the world of driver-based planning. Very few of the major data platform providers provide these capabilities today. These are the types of things you would do in a spreadsheet. And we all know the issues associated with spreadsheets. They're hard to govern, they're error-prone. And so, if we can take that type of analysis, collecting the occupancy of a rental property, the projected rise in rental rates, the fluctuations perhaps in occupancy, the interest rates associated with financing that property, we can project forward. And that's a very common thing to do. What the income might look like from that property income, the expenses, we can plan and purchase things appropriately. So, I think, we need this broader purview and I'm beginning to see some of those things happen. And the evidence today I would say, is more focused around the metric stores and the feature stores starting to see vendors offer those capabilities. And we're starting to see the ML ops elements of managing the AI and ML models find their way closer to the data platforms as well. >> Very interesting. When I hear metrics, I think of KPIs, I think of data apps, orchestrate people and places and things to optimize around a set of KPIs. It sounds like a metadata challenge more... Somebody once predicted they'll have more metadata than data. Carl, what are your thoughts on this prediction? >> Yeah, I think that what Dave is describing as data derivatives is in a way, another word for what I was calling operational metadata, which not about the data itself, but how it's used, where it came from, what the rules are governing it, and that kind of thing. If you have a rich enough set of those things, then not only can you do a model of how well your vacation property rental may do in terms of income, but also how well your application that's measuring that is doing for you. In other words, how many times have I used it, how much data have I used and what is the relationship between the data that I've used and the benefits that I've derived from using it? Well, we don't have ways of doing that. What's interesting to me is that folks in the content world are way ahead of us here, because they have always tracked their content using these kinds of attributes. Where did it come from? When was it created, when was it modified? Who modified it? And so on and so forth. We need to do more of that with the structure data that we have, so that we can track what it's used. And also, it tells us how well we're doing with it. Is it really benefiting us? Are we being efficient? Are there improvements in processes that we need to consider? Because maybe data gets created and then it isn't used or it gets used, but it gets altered in some way that actually misleads people. (laughs) So, we need the mechanisms to be able to do that. So, I would say that that's... And I'd say that it's true that we need that stuff. I think, that starting to expand is probably the right way to put it. It's going to be expanding for some time. I think, we're still a distance from having all that stuff really working together. >> Maybe we should say it's gestating. (Dave and Carl laughing) >> Sorry, if I may- >> Sanjeev, yeah, I was going to say this... Sanjeev, please comment. This sounds to me like it supports Zhamak Dehghani's principles, but please. >> Absolutely. So, whether we call it data mesh or not, I'm not getting into that conversation, (Dave chuckles) but data (audio breaking) (Tony laughing) everything that I'm hearing what Dave is saying, Carl, this is the year when data products will start to take off. I'm not saying they'll become mainstream. They may take a couple of years to become so, but this is data products, all this thing about vacation rentals and how is it doing, that data is coming from different sources. I'm packaging it into our data product. And to Carl's point, there's a whole operational metadata associated with it. The idea is for organizations to see things like developer productivity, how many releases am I doing of this? What data products are most popular? I'm actually in right now in the process of formulating this concept that just like we had data catalogs, we are very soon going to be requiring data products catalog. So, I can discover these data products. I'm not just creating data products left, right, and center. I need to know, do they already exist? What is the usage? If no one is using a data product, maybe I want to retire and save cost. But this is a data product. Now, there's a associated thing that is also getting debated quite a bit called data contracts. And a data contract to me is literally just formalization of all these aspects of a product. How do you use it? What is the SLA on it, what is the quality that I am prescribing? So, data product, in my opinion, shifts the conversation to the consumers or to the business people. Up to this point when, Dave, you're talking about data and all of data discovery curation is a very data producer-centric. So, I think, we'll see a shift more into the consumer space. >> Yeah. Dave, can I just jump in there just very quickly there, which is that what Sanjeev has been saying there, this is really central to what Zhamak has been talking about. It's basically about making, one, data products are about the lifecycle management of data. Metadata is just elemental to that. And essentially, one of the things that she calls for is making data products discoverable. That's exactly what Sanjeev was talking about. >> By the way, did everyone just no notice how Sanjeev just snuck in another prediction there? So, we've got- >> Yeah. (group laughing) >> But you- >> Can we also say that he snuck in, I think, the term that we'll remember today, which is metadata museums. >> Yeah, but- >> Yeah. >> And also comment to, Tony, to your last year's prediction, you're really talking about it's not something that you're going to buy from a vendor. >> No. >> It's very specific >> Mm-hmm. >> to an organization, their own data product. So, touche on that one. Okay, last prediction. Let's bring them up. Doug Henschen, BI analytics is headed to embedding. What does that mean? >> Well, we all know that conventional BI dashboarding reporting is really commoditized from a vendor perspective. It never enjoyed truly mainstream adoption. Always that 25% of employees are really using these things. I'm seeing rising interest in embedding concise analytics at the point of decision or better still, using analytics as triggers for automation and workflows, and not even necessitating human interaction with visualizations, for example, if we have confidence in the analytics. So, leading companies are pushing for next generation applications, part of this low-code, no-code movement we've seen. And they want to build that decision support right into the app. So, the analytic is right there. Leading enterprise apps vendors, Salesforce, SAP, Microsoft, Oracle, they're all building smart apps with the analytics predictions, even recommendations built into these applications. And I think, the progressive BI analytics vendors are supporting this idea of driving insight to action, not necessarily necessitating humans interacting with it if there's confidence. So, we want prediction, we want embedding, we want automation. This low-code, no-code development movement is very important to bringing the analytics to where people are doing their work. We got to move beyond the, what I call swivel chair integration, between where people do their work and going off to separate reports and dashboards, and having to interpret and analyze before you can go back and do take action. >> And Dave Menninger, today, if you want, analytics or you want to absorb what's happening in the business, you typically got to go ask an expert, and then wait. So, what are your thoughts on Doug's prediction? >> I'm in total agreement with Doug. I'm going to say that collectively... So, how did we get here? I'm going to say collectively as an industry, we made a mistake. We made BI and analytics separate from the operational systems. Now, okay, it wasn't really a mistake. We were limited by the technology available at the time. Decades ago, we had to separate these two systems, so that the analytics didn't impact the operations. You don't want the operations preventing you from being able to do a transaction. But we've gone beyond that now. We can bring these two systems and worlds together and organizations recognize that need to change. As Doug said, the majority of the workforce and the majority of organizations doesn't have access to analytics. That's wrong. (chuckles) We've got to change that. And one of the ways that's going to change is with embedded analytics. 2/3 of organizations recognize that embedded analytics are important and it even ranks higher in importance than AI and ML in those organizations. So, it's interesting. This is a really important topic to the organizations that are consuming these technologies. The good news is it works. Organizations that have embraced embedded analytics are more comfortable with self-service than those that have not, as opposed to turning somebody loose, in the wild with the data. They're given a guided path to the data. And the research shows that 65% of organizations that have adopted embedded analytics are comfortable with self-service compared with just 40% of organizations that are turning people loose in an ad hoc way with the data. So, totally behind Doug's predictions. >> Can I just break in with something here, a comment on what Dave said about what Doug said, which (laughs) is that I totally agree with what you said about embedded analytics. And at IDC, we made a prediction in our future intelligence, future of intelligence service three years ago that this was going to happen. And the thing that we're waiting for is for developers to build... You have to write the applications to work that way. It just doesn't happen automagically. Developers have to write applications that reference analytic data and apply it while they're running. And that could involve simple things like complex queries against the live data, which is through something that I've been calling analytic transaction processing. Or it could be through something more sophisticated that involves AI operations as Doug has been suggesting, where the result is enacted pretty much automatically unless the scores are too low and you need to have a human being look at it. So, I think that that is definitely something we've been watching for. I'm not sure how soon it will come, because it seems to take a long time for people to change their thinking. But I think, as Dave was saying, once they do and they apply these principles in their application development, the rewards are great. >> Yeah, this is very much, I would say, very consistent with what we were talking about, I was talking about before, about basically rethinking the modern data stack and going into more of an end-to-end solution solution. I think, that what we're talking about clearly here is operational analytics. There'll still be a need for your data scientists to go offline just in their data lakes to do all that very exploratory and that deep modeling. But clearly, it just makes sense to bring operational analytics into where people work into their workspace and further flatten that modern data stack. >> But with all this metadata and all this intelligence, we're talking about injecting AI into applications, it does seem like we're entering a new era of not only data, but new era of apps. Today, most applications are about filling forms out or codifying processes and require a human input. And it seems like there's enough data now and enough intelligence in the system that the system can actually pull data from, whether it's the transaction system, e-commerce, the supply chain, ERP, and actually do something with that data without human involvement, present it to humans. Do you guys see this as a new frontier? >> I think, that's certainly- >> Very much so, but it's going to take a while, as Carl said. You have to design it, you have to get the prediction into the system, you have to get the analytics at the point of decision has to be relevant to that decision point. >> And I also recall basically a lot of the ERP vendors back like 10 years ago, we're promising that. And the fact that we're still looking at the promises shows just how difficult, how much of a challenge it is to get to what Doug's saying. >> One element that could be applied in this case is (indistinct) architecture. If applications are developed that are event-driven rather than following the script or sequence that some programmer or designer had preconceived, then you'll have much more flexible applications. You can inject decisions at various points using this technology much more easily. It's a completely different way of writing applications. And it actually involves a lot more data, which is why we should all like it. (laughs) But in the end (Tony laughing) it's more stable, it's easier to manage, easier to maintain, and it's actually more efficient, which is the result of an MIT study from about 10 years ago, and still, we are not seeing this come to fruition in most business applications. >> And do you think it's going to require a new type of data platform database? Today, data's all far-flung. We see that's all over the clouds and at the edge. Today, you cache- >> We need a super cloud. >> You cache that data, you're throwing into memory. I mentioned, MySQL heat wave. There are other examples where it's a brute force approach, but maybe we need new ways of laying data out on disk and new database architectures, and just when we thought we had it all figured out. >> Well, without referring to disk, which to my mind, is almost like talking about cave painting. I think, that (Dave laughing) all the things that have been mentioned by all of us today are elements of what I'm talking about. In other words, the whole improvement of the data mesh, the improvement of metadata across the board and improvement of the ability to track data and judge its freshness the way we judge the freshness of a melon or something like that, to determine whether we can still use it. Is it still good? That kind of thing. Bringing together data from multiple sources dynamically and real-time requires all the things we've been talking about. All the predictions that we've talked about today add up to elements that can make this happen. >> Well, guys, it's always tremendous to get these wonderful minds together and get your insights, and I love how it shapes the outcome here of the predictions, and let's see how we did. We're going to leave it there. I want to thank Sanjeev, Tony, Carl, David, and Doug. Really appreciate the collaboration and thought that you guys put into these sessions. Really, thank you. >> Thank you. >> Thanks, Dave. >> Thank you for having us. >> Thanks. >> Thank you. >> All right, this is Dave Valente for theCUBE, signing off for now. Follow these guys on social media. Look for coverage on siliconangle.com, theCUBE.net. Thank you for watching. (upbeat 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. >> Snowflake Summit 2022 underscored that the ecosystem excitement which was once forming around Hadoop is being reborn, escalated and coalescing around Snowflake's data cloud. What was once seen as a simpler cloud data warehouse and good marketing with the data cloud is evolving rapidly with new workloads of vertical industry focus, data applications, monetization, and more. The question is, will the promise of data be fulfilled this time around, or is it same wine, new bottle? Hello, and welcome to this week's Wikibon CUBE Insights powered by ETR. In this "Breaking Analysis," we'll talk about the event, the announcements that Snowflake made that are of greatest interest, the major themes of the show, what was hype and what was real, the competition, and some concerns that remain in many parts of the ecosystem and pockets of customers. First let's look at the overall event. It was held at Caesars Forum. Not my favorite venue, but I'll tell you it was packed. Fire Marshall Full, as we sometimes say. Nearly 10,000 people attended the event. Here's Snowflake's CMO Denise Persson on theCUBE describing how this event has evolved. >> Yeah, two, three years ago, we were about 1800 people at a Hilton in San Francisco. We had about 40 partners attending. This week we're close to 10,000 attendees here. Almost 10,000 people online as well, and over over 200 partners here on the show floor. >> Now, those numbers from 2019 remind me of the early days of Hadoop World, which was put on by Cloudera but then Cloudera handed off the event to O'Reilly as this article that we've inserted, if you bring back that slide would say. The headline it almost got it right. Hadoop World was a failure, but it didn't have to be. Snowflake has filled the void created by O'Reilly when it first killed Hadoop World, and killed the name and then killed Strata. Now, ironically, the momentum and excitement from Hadoop's early days, it probably could have stayed with Cloudera but the beginning of the end was when they gave the conference over to O'Reilly. We can't imagine Frank Slootman handing the keys to the kingdom to a third party. Serious business was done at this event. I'm talking substantive deals. Salespeople from a host sponsor and the ecosystems that support these events, they love physical. They really don't like virtual because physical belly to belly means relationship building, pipeline, and deals. And that was blatantly obvious at this show. And in fairness, all theCUBE events that we've done year but this one was more vibrant because of its attendance and the action in the ecosystem. Ecosystem is a hallmark of a cloud company, and that's what Snowflake is. We asked Frank Slootman on theCUBE, was this ecosystem evolution by design or did Snowflake just kind of stumble into it? Here's what he said. >> Well, when you are a data clouding, you have data, people want to do things with that data. They don't want just run data operations, populate dashboards, run reports. Pretty soon they want to build applications and after they build applications, they want build businesses on it. So it goes on and on and on. So it drives your development to enable more and more functionality on that data cloud. Didn't start out that way, you know, we were very, very much focused on data operations. Then it becomes application development and then it becomes, hey, we're developing whole businesses on this platform. So similar to what happened to Facebook in many ways. >> So it sounds like it was maybe a little bit of both. The Facebook analogy is interesting because Facebook is a walled garden, as is Snowflake, but when you come into that garden, you have assurances that things are going to work in a very specific way because a set of standards and protocols is being enforced by a steward, i.e. Snowflake. This means things run better inside of Snowflake than if you try to do all the integration yourself. Now, maybe over time, an open source version of that will come out but if you wait for that, you're going to be left behind. That said, Snowflake has made moves to make its platform more accommodating to open source tooling in many of its announcements this week. Now, I'm not going to do a deep dive on the announcements. Matt Sulkins from Monte Carlo wrote a decent summary of the keynotes and a number of analysts like Sanjeev Mohan, Tony Bear and others are posting some deeper analysis on these innovations, and so we'll point to those. I'll say a few things though. Unistore extends the type of data that can live in the Snowflake data cloud. It's enabled by a new feature called hybrid tables, a new table type in Snowflake. One of the big knocks against Snowflake was it couldn't handle and transaction data. Several database companies are creating this notion of a hybrid where both analytic and transactional workloads can live in the same data store. Oracle's doing this for example, with MySQL HeatWave and there are many others. We saw Mongo earlier this month add an analytics capability to its transaction system. Mongo also added sequel, which was kind of interesting. Here's what Constellation Research analyst Doug Henschen said about Snowflake's moves into transaction data. Play the clip. >> Well with Unistore, they're reaching out and trying to bring transactional data in. Hey, don't limit this to analytical information and there's other ways to do that like CDC and streaming but they're very closely tying that again to that marketplace, with the idea of bring your data over here and you can monetize it. Don't just leave it in that transactional database. So another reach to a broader play across a big community that they're building. >> And you're also seeing Snowflake expand its workload types in its unique way and through Snowpark and its stream lit acquisition, enabling Python so that native apps can be built in the data cloud and benefit from all that structure and the features that Snowflake is built in. Hence that Facebook analogy, or maybe the App Store, the Apple App Store as I propose as well. Python support also widens the aperture for machine intelligence workloads. We asked Snowflake senior VP of product, Christian Kleinerman which announcements he thought were the most impactful. And despite the who's your favorite child nature of the question, he did answer. Here's what he said. >> I think the native applications is the one that looks like, eh, I don't know about it on the surface but he has the biggest potential to change everything. That's create an entire ecosystem of solutions for within a company or across companies that I don't know that we know what's possible. >> Snowflake also announced support for Apache Iceberg, which is a new open table format standard that's emerging. So you're seeing Snowflake respond to these concerns about its lack of openness, and they're building optionality into their cloud. They also showed some cost op optimization tools both from Snowflake itself and from the ecosystem, notably Capital One which launched a software business on top of Snowflake focused on optimizing cost and eventually the rollout data management capabilities, and all kinds of features that Snowflake announced that the show around governance, cross cloud, what we call super cloud, a new security workload, and they reemphasize their ability to read non-native on-prem data into Snowflake through partnerships with Dell and Pure and a lot more. Let's hear from some of the analysts that came on theCUBE this week at Snowflake Summit to see what they said about the announcements and their takeaways from the event. This is Dave Menninger, Sanjeev Mohan, and Tony Bear, roll the clip. >> Our research shows that the majority of organizations, the majority of people do not have access to analytics. And so a couple of the things they've announced I think address those or help to address those issues very directly. So Snowpark and support for Python and other languages is a way for organizations to embed analytics into different business processes. And so I think that'll be really beneficial to try and get analytics into more people's hands. And I also think that the native applications as part of the marketplace is another way to get applications into people's hands rather than just analytical tools. Because most people in the organization are not analysts. They're doing some line of business function. They're HR managers, they're marketing people, they're sales people, they're finance people, right? They're not sitting there mucking around in the data, they're doing a job and they need analytics in that job. >> Primarily, I think it is to contract this whole notion that once you move data into Snowflake, it's a proprietary format. So I think that's how it started but it's usually beneficial to the customers, to the users because now if you have large amount of data in paket files you can leave it on S3, but then you using the Apache Iceberg table format in Snowflake, you get all the benefits of Snowflake's optimizer. So for example, you get the micro partitioning, you get the metadata. And in a single query, you can join, you can do select from a Snowflake table union and select from an iceberg table and you can do store procedure, user defined function. So I think what they've done is extremely interesting. Iceberg by itself still does not have multi-table transactional capabilities. So if I'm running a workload, I might be touching 10 different tables. So if I use Apache Iceberg in a raw format, they don't have it, but Snowflake does. So the way I see it is Snowflake is adding more and more capabilities right into the database. So for example, they've gone ahead and added security and privacy. So you can now create policies and do even cell level masking, dynamic masking, but most organizations have more than Snowflake. So what we are starting to see all around here is that there's a whole series of data catalog companies, a bunch of companies that are doing dynamic data masking, security and governance, data observability which is not a space Snowflake has gone into. So there's a whole ecosystem of companies that is mushrooming. Although, you know, so they're using the native capabilities of Snowflake but they are at a level higher. So if you have a data lake and a cloud data warehouse and you have other like relational databases, you can run these cross platform capabilities in that layer. So that way, you know, Snowflake's done a great job of enabling that ecosystem. >> I think it's like the last mile, essentially. In other words, it's like, okay, you have folks that are basically that are very comfortable with Tableau but you do have developers who don't want to have to shell out to a separate tool. And so this is where Snowflake is essentially working to address that constituency. To Sanjeev's point, and I think part of it, this kind of plays into it is what makes this different from the Hadoop era is the fact that all these capabilities, you know, a lot of vendors are taking it very seriously to put this native. Now, obviously Snowflake acquired Streamlit. So we can expect that the Streamlit capabilities are going to be native. >> I want to share a little bit about the higher level thinking at Snowflake, here's a chart from Frank Slootman's keynote. It's his version of the modern data stack, if you will. Now, Snowflake of course, was built on the public cloud. If there were no AWS, there would be no Snowflake. Now, they're all about bringing data and live data and expanding the types of data, including structured, we just heard about that, unstructured, geospatial, and the list is going to continue on and on. Eventually I think it's going to bleed into the edge if we can figure out what to do with that edge data. Executing on new workloads is a big deal. They started with data sharing and they recently added security and they've essentially created a PaaS layer. We call it a SuperPaaS layer, if you will, to attract application developers. Snowflake has a developer-focused event coming up in November and they've extended the marketplace with 1300 native apps listings. And at the top, that's the holy grail, monetization. We always talk about building data products and we saw a lot of that at this event, very, very impressive and unique. Now here's the thing. There's a lot of talk in the press, in the Wall Street and the broader community about consumption-based pricing and concerns over Snowflake's visibility and its forecast and how analytics may be discretionary. But if you're a company building apps in Snowflake and monetizing like Capital One intends to do, and you're now selling in the marketplace, that is not discretionary, unless of course your costs are greater than your revenue for that service, in which case is going to fail anyway. But the point is we're entering a new error where data apps and data products are beginning to be built and Snowflake is attempting to make the data cloud the defacto place as to where you're going to build them. In our view they're well ahead in that journey. Okay, let's talk about some of the bigger themes that we heard at the event. Bringing apps to the data instead of moving the data to the apps, this was a constant refrain and one that certainly makes sense from a physics point of view. But having a single source of data that is discoverable, sharable and governed with increasingly robust ecosystem options, it doesn't have to be moved. Sometimes it may have to be moved if you're going across regions, but that's unique and a differentiator for Snowflake in our view. I mean, I'm yet to see a data ecosystem that is as rich and growing as fast as the Snowflake ecosystem. Monetization, we talked about that, industry clouds, financial services, healthcare, retail, and media, all front and center at the event. My understanding is that Frank Slootman was a major force behind this shift, this development and go to market focus on verticals. It's really an attempt, and he talked about this in his keynote to align with the customer mission ultimately align with their objectives which not surprisingly, are increasingly monetizing with data as a differentiating ingredient. We heard a ton about data mesh, there were numerous presentations about the topic. And I'll say this, if you map the seven pillars Snowflake talks about, Benoit Dageville talked about this in his keynote, but if you map those into Zhamak Dehghani's data mesh framework and the four principles, they align better than most of the data mesh washing that I've seen. The seven pillars, all data, all workloads, global architecture, self-managed, programmable, marketplace and governance. Those are the seven pillars that he talked about in his keynote. All data, well, maybe with hybrid tables that becomes more of a reality. Global architecture means the data is globally distributed. It's not necessarily physically in one place. Self-managed is key. Self-service infrastructure is one of Zhamak's four principles. And then inherent governance. Zhamak talks about computational, what I'll call automated governance, built in. And with all the talk about monetization, that aligns with the second principle which is data as product. So while it's not a pure hit and to its credit, by the way, Snowflake doesn't use data mesh in its messaging anymore. But by the way, its customers do, several customers talked about it. Geico, JPMC, and a number of other customers and partners are using the term and using it pretty closely to the concepts put forth by Zhamak Dehghani. But back to the point, they essentially, Snowflake that is, is building a proprietary system that substantially addresses some, if not many of the goals of data mesh. Okay, back to the list, supercloud, that's our term. We saw lots of examples of clouds on top of clouds that are architected to spin multiple clouds, not just run on individual clouds as separate services. And this includes Snowflake's data cloud itself but a number of ecosystem partners that are headed in a very similar direction. Snowflake still talks about data sharing but now it uses the term collaboration in its high level messaging, which is I think smart. Data sharing is kind of a geeky term. And also this is an attempt by Snowflake to differentiate from everyone else that's saying, hey, we do data sharing too. And finally Snowflake doesn't say data marketplace anymore. It's now marketplace, accounting for its application market. Okay, let's take a quick look at the competitive landscape via this ETR X-Y graph. Vertical access remembers net score or spending momentum and the x-axis is penetration, pervasiveness in the data center. That's what ETR calls overlap. Snowflake continues to lead on the vertical axis. They guide it conservatively last quarter, remember, so I wouldn't be surprised if that lofty height, even though it's well down from its earlier levels but I wouldn't be surprised if it ticks down again a bit in the July survey, which will be in the field shortly. Databricks is a key competitor obviously at a strong spending momentum, as you can see. We didn't draw it here but we usually draw that 40% line or red line at 40%, anything above that is considered elevated. So you can see Databricks is quite elevated. But it doesn't have the market presence of Snowflake. It didn't get to IPO during the bubble and it doesn't have nearly as deep and capable go-to market machinery. Now, they're getting better and they're getting some attention in the market, nonetheless. But as a private company, you just naturally, more people are aware of Snowflake. Some analysts, Tony Bear in particular, believe Mongo and Snowflake are on a bit of a collision course long term. I actually can see his point. You know, I mean, they're both platforms, they're both about data. It's long ways off, but you can see them sort of in a similar path. They talk about kind of similar aspirations and visions even though they're quite in different markets today but they're definitely participating in similar tam. The cloud players are probably the biggest or definitely the biggest partners and probably the biggest competitors to Snowflake. And then there's always Oracle. Doesn't have the spending velocity of the others but it's got strong market presence. It owns a cloud and it knows a thing about data and it definitely is a go-to market machine. Okay, we're going to end on some of the things that we heard in the ecosystem. 'Cause look, we've heard before how particular technology, enterprise data warehouse, data hubs, MDM, data lakes, Hadoop, et cetera. We're going to solve all of our data problems and of course they didn't. And in fact, sometimes they create more problems that allow vendors to push more incremental technology to solve the problems that they created. Like tools and platforms to clean up the no schema on right nature of data lakes or data swamps. But here are some of the things that I heard firsthand from some customers and partners. First thing is, they said to me that they're having a hard time keeping up sometimes with the pace of Snowflake. It reminds me of AWS in 2014, 2015 timeframe. You remember that fire hose of announcements which causes increased complexity for customers and partners. I talked to several customers that said, well, yeah this is all well and good but I still need skilled people to understand all these tools that I'm integrated in the ecosystem, the catalogs, the machine learning observability. A number of customers said, I just can't use one governance tool, I need multiple governance tools and a lot of other technologies as well, and they're concerned that that's going to drive up their cost and their complexity. I heard other concerns from the ecosystem that it used to be sort of clear as to where they could add value you know, when Snowflake was just a better data warehouse. But to point number one, they're either concerned that they'll be left behind or they're concerned that they'll be subsumed. Look, I mean, just like we tell AWS customers and partners, you got to move fast, you got to keep innovating. If you don't, you're going to be left. Either if your customer you're going to be left behind your competitor, or if you're a partner, somebody else is going to get there or AWS is going to solve the problem for you. Okay, and there were a number of skeptical practitioners, really thoughtful and experienced data pros that suggested that they've seen this movie before. That's hence the same wine, new bottle. Well, this time around I certainly hope not given all the energy and investment that is going into this ecosystem. And the fact is Snowflake is unquestionably making it easier to put data to work. They built on AWS so you didn't have to worry about provisioning, compute and storage and networking and scaling. Snowflake is optimizing its platform to take advantage of things like Graviton so you don't have to, and they're doing some of their own optimization tools. The ecosystem is building optimization tools so that's all good. And firm belief is the less expensive it is, the more data will get brought into the data cloud. And they're building a data platform on which their ecosystem can build and run data applications, aka data products without having to worry about all the hard work that needs to get done to make data discoverable, shareable, and governed. And unlike the last 10 years, you don't have to be a keeper and integrate all the animals in the Hadoop zoo. Okay, that's it for today, thanks for watching. Thanks to my colleague, Stephanie Chan who helps research "Breaking Analysis" topics. Sometimes Alex Myerson is on production and manages the podcasts. Kristin Martin and Cheryl Knight help get the word out on social and in our newsletters, and Rob Hof is our editor in chief over at Silicon, and Hailey does some wonderful editing, thanks to all. Remember, all these episodes are available as podcasts wherever you listen. All you got to do is search Breaking Analysis Podcasts. I publish each week on wikibon.com and siliconangle.com and you can email me at David.Vellante@siliconangle.com or DM me @DVellante. If you got something interesting, I'll respond. If you don't, I'm sorry I won't. Or comment on my LinkedIn post. Please check out etr.ai for the best survey data in the enterprise tech business. This is Dave Vellante for theCUBE Insights powered by ETR. Thanks for watching, and we'll see you next time. (upbeat music)

>>Yeah, yeah, >>Hello. We're back with Today's the last session in the creating engaging analytics experiences for all track breaking down data silos. A conversation with Snowflake on Western Union Earlier today, we did a few deep dives into the thought spot product with sessions on thoughts about one. Thoughts were everywhere on spot. Take you to close out this track. We're joined by industry leading experts Christian Kleinerman s VP of product at Snowflake and Tom Matzzie, Pharaoh, chief data officer at Western Union, for a thought provoking conversation on data transformation on how to avoid the pitfalls of traditional analytics. They'll be discussing in key challenges faced by organizations, why user engagement matters and looking towards the future of the industry. No Joining Thomas and Christian in conversation is Angela Cooper, vice president of customer success at Thought spot. Thank you all for being here today. We're so excited for what is what this conversation has in store. Handing it over now to Christian to kick things off. >>Hi. So, a few years ago, when when someone asked about Snowflake, the most common answer, it was like, what is snowflake and what do you do? Hopefully in the last couple off months, things have changed and and here I am showing a couple of momentum data points on, uh, where we have accomplished here it Snowflake. So we we have received Ah, a lot of attention and buzz. Recently, we were listed in the New York Stock Exchange And we even though we still think of ourselves as a small start up company, we have crossed the 2000 employees mark. More important, we count with 3 3000 plus amazing customers. And something that we obsess about is the a satisfaction of our customers. We really are working hard. The laboring technology that having a platform for better decisions, better analytics and then the promoters course off 71 depicted here is a testament of that. And last, but certainly not least about snowflake. It's very important that we know that we succeed with our partners. We know that we don't go to market by ourselves. We actually have Ah, fantastic set of partners and of course, thoughts. But it is one of our most important partners. >>Good morning. Good afternoon. Eso Amman Thomas affair on the chief kid officer here at Western Union. It's gonna be a background of a Western union and what we, uh, what we do and how we service our customers. So today we are in over 200 countries and territories worldwide. We have a 550,000 retail Asian network to service all of our customers, uh, needs from what he transfer and picking up in a depositing cash. We also have our digital transformation underway, where we now have educate abilities up and running and over 35 countries with paled options to accounts in over 120 countries. We think about our overall business and how support are over our customers and our services. It really has transformed over the past 12 months with Cove it and it's part of that We have to be able to really accelerate our transformation on a digital front to help to enable in the super those customers going forward. Eso as part of that, You know, a big, big help in a big supporter of that transformation has been snowflake and has been thought spot as part of that transformation. If you go the next to the next slide are our current, uh B I in our illegal tools right to date, uh, have been very useful up until the last one or two years. As data explodes and as as our customer needs transform and as our solutions and our time to act in our time to react in the overall market becomes faster and faster, we need to be able to basically look across our entire company, our entire organization and cross functionally to visit to leverage data leverage our insights to really basically pivot our overall business and our overall model to support our customers and our and to enable those services and products going forward. So as part of that, snowflakes been a huge part of that journey, right, allowing us to consolidate over our 30 plus data stores across the company on able to really leverage that overall data and insights to drive, uh, quick reaction right with the pivot, our business offered to enable new services and improve customer experiences going forward and then being able to use a snowflake and then being put the applications on top of that like thought spot, which allows, uh, users that are both technical and nontechnical to the go in and just, um, ask the question as if the searching on Google or Yahoo or being they can just ask any question they want and then get the results back in real time, made that business call and then really go forward through these is this larger ecosystem as a whole. It's really enabled us to really transform our business and supporter customers going forward. >>Wonderful. Thank you, Tom. Thank you, Christian, for the overview of both snowflake and Western Union. Both have big presence in Denver, which is where Tom and I are tonight. Um, I'm here. I'm the vice president of customer success for Thought spot, and I wanted to ask both of you some questions about the industry and specific things that you're facing within Western Union. So first I was hoping Christian that you could talk to me a little bit about Snowflake has thousands of customers at this point, servicing essentially located data sets. But what are you seeing? Has been the top challenges that businesses air facing and how it snowflake uniquely positioned to help. Yeah, >>so certainly the think the challenges air made. I would say that the macro challenge above everything is how to turn data into a competitive differentiator, their study after study that says companies that embrace data and insights and analytics they are outperforming their competitors. So that would be my macro challenge. Once you go into the next level, maybe I can think of three elements. The first one Tom already perfectly teed up the topic of of silence and the reality For most organizations, data is fragmented across different database systems. Even filed systems in some instances transactional databases, analytical data bases and what customers expect is to have, ah, unified experience like I am dealing with company extra company. Why? And I really don't care if behind the scenes there's 10 different teams or 100 different systems. I just want a unified experience. And the Congress is true. The opportunity to deliver personalized custom experiences is reliant on a single view of the day. The other topic that comes to mind this is the one of data governance, Um, as data becomes more important than a reorganization, understanding the constraints and security and privacy also become critical to not only advanced data capability but do it doing so responsibly and within the norms off regulation and the last one which is something court to tow our vision. We are pioneering the concept of the data cloud and the challenge that that we're addressing there is the problem around access to data, right. You can no longer as an organization think of making decisions just on your own data. But there's lots of data collaboration, data enrichment. Maybe I wanna put my data in context. And that's what we're trying to simplify and democratize access and simplify connecting to the data that improves decisions on all three fronts. Obviously, we're obsessed. That's no bling on on tearing down the silos on delivering a solution that is very focused on data governance. And for sure, the data cloud simplifies access to data. >>Wonderful. Now, I know we we really focused on those data silos is a business challenge. But Tom, going through your digital transformation journey are there specific challenges that you faced with Western Union That thought spot and snowflake have helped you overcome? >>Yeah. So? So first off fully agree what Christian just said, right? Those are absolutely, you know, problems that we faced. And we've had overcome, um, service, any company right being able to the transforming to modernize the cloud. Um, for us, one of the biggest things is being able to not just access our information, but have it in a way that it can be consumed, right? Have it in a way that it could be understood, right? Have it in a way that we can then drive business business decision points and and be able to use that information to either fix a problem that we see or better service our customers or offer a product that we're seeing right now is a miss in the marketplace to service in a underserved community or underserved, um, customer base. Also, from our standpoint, being able toe look, um um, uh and predict in forecast what's going to happen and be able to use that information and use our insights to then be proactive and thio in either, You know, be thoughtful about how do we shift our focus, or how do we then change our strategy to take advantage of that for that forecast in that position that we're seeing into the future? >>Wonderful. I've heard from many customers you could not have predicted what was going to happen to our businesses in the year 2020 with the traditional models and especially with what did you say? 30 plus different data silos. Being able to do that type of prediction across those systems must have been very, very difficult. You also mentioned going through a digital transformation at Western Union. So can you talk to me, Tom? A little bit about kind of present day? And why? Why is it important to enable your frontline knowledge workers with the right data at the right time with the right technology? >>Yeah, so? So you're spot on, by the way. But, uh, no one predicted that that we would have a pandemic that would literally consume the entire globe right And change how consumers, um uh, use and buy services and products, or how economies would either shut down or at the reopening shut down again. And then how different interests to be impacted by this? Right. So, uh, what we learned and what we were able to pivot was being able to do exactly what you just said, right. Being able to understand what's happening the date of the right time, right then being able to with the right technology with the right capabilities, understand? what's happening. I understand. Then what should our pivot be? And how should we then go focus on that pivot to go into go and transform? I think it's e. It's more than just just the front lines. Also, our executives. It's also are back office operations, right, because as you think through this, right as customers were having issues right, go into retail locations that were closed. It end of Q one Earlier, Q two. We obviously had a a large surplus right of phone calls coming into our call centers, asking for help, asking for How can we transact better? Where can we go? Right? How do we handle the operationally? Right? As we had a massive surge onto our digital platform where we were, we had 100% increase year over year in Q one and Q two. How do we make sure that our platform the technology can scale right and still provide the right S L A's and and and and the right, um uh, support to our internal customers as well as our extra customers in the future? Eso so really interesting, though, you know, on on on the front line side, our sales staff, right? And even our front line associates with our agent locations A to retail side, you know, for us, is really around. How do we best support them? So how do we partner with them to understand? You know, when a certain certain governments or certain, uh, regions were going toe lock down, how do we support them to keep them open, right. How do we make them a essential service going forward? How do we enable them? Right, the Wright systems or technology to do things a bit differently than they have in the past to adopt right with the changing times. But, you know, I'll tell you the amount of transformation in the basement we've done this year, I think you know, has a massive and actually on Lee, you know, created a larger wave for us to actually ride into the future as we can, to base to innovate, you know, in partnership with both thought spot and with the snowflake into the future. >>Absolutely. I've seen many, many a industry analyst reports talking about how companies now in 2020 have accelerated that digital transformation movement because of current day. In current time, Christian What are you seeing with the rest of the industry and other global companies about enabling data across the globe at the right time? >>Yeah, so I can't agree more with with with with what? Tom said. And he gave some very, um, compelling and very riel use cases where the timeliness of data and and and and and at the right time concept make a big difference. Right? They aske part of our data marketplace with snowflake with deliver, for example, um, up to date low ladies information on, uh, covert 19 data sets where we're infection spiking. And what were the trends? And the use case was very, very riel. Every single company was trying to make sense of the numbers. Uh, all machine learning models were sort of like, out of whack, because no trends and no patterns may make sense anymore. And it was They need to be able to join my data and my activity with this health data set and make decisions at the right time. Imagine if if the cycle to makes all these decisions waas Ah, monthlong. You would never catch up, right? And he speaks to tow a concept that it that is, um, dear, it wasa snowflake and is the lifetime value data right? The notion of ableto act on a piece of data on an event at the right time and obviously with the slow laden see it's possible, makes a big difference. And and there is no end of example. Stomach gives her all again very compelling ones. Um, there's many others, but if you're running a marketing campaign and would you want to know five minutes later that it's not working out, you're burning your daughters? Or would you want to know the next day? Or if someone is going to give you you have a subscription based business and you're going toe, for example, have a model that predicts the turn of your customer? How useful is if you find out Hey, your customer is gonna turn, but you found out two months later. Once probably you are really toe action and change the outcome. Eyes different and and and this order to manage that I'm talking about days or months are not uncommon. Many organizations today, and that's where the topic of right technology matters. Um, I love asking questions about Do you know, an organization and customers. Do you run data, transformations and ingests at two and three in the morning? And the most common answer is yes. And then you start asking why. And usually the answer is some flavor off technology made me do it and a big part of what we're trying to do, like what we're pioneering is. How about ingesting data, transforming data enriching data when the business needs it at the right time with the right timeliness? Not when the technology had cycles. So they were Scipio available, so the importance can't be overstated. There is value in in in analyzing understanding data on time, and we provide technology and platform to any of this. >>That's such a good point. Christian. We ended up on Lee doing processes and loading in the middle of the night because that's what the technology at that time would allow. You couldn't have the concurrency. You couldn't have, um, data happening all at the same time. And so wonderful point that stuff like enables. I think another piece that's interesting that you guys a hit on is that it's important to have the same user experiencing user interface at the right time. And so what I found talking to customers. And Tom what? You and I have discussed this. When you have 30 different data sets and you have a interface that's different, you have a legacy reports system. Maybe you have excel on top of another. You have thought spot on one. You have your dashboard of choice on another, those different sources in different ways. To view that data, it can all be so disjointed. And the combination of thought spot with snowflake and all the data in one place with a centralized, unified user experience just helps users take advantage off the insights that they need right at that right moment. So kind of finishing up for our last question for today I'm interested to hear about Christian will go back to you quickly about what do you see from snowflakes? Perspective is ahead. Future facing for data and analytics. >>One of the topics you just alluded toe Angela, which is the fact that many data sets are gonna be part of the processes by which we make decisions and that that's where were the experience with thoughts but a single unified search experience for a single unified. Um automatic insects, which is what's para que does That is the future, right? I I don't think that x many years from now on, and I think that that X is a small number. Organizations are going to say I had some business activity. I collected some data. I did some analysis and I have conclusions because it always has to be okay, put it in context or look at industry trends and look at other activity that can help him make more sense about my data. The example of tracking they covert are breaking is ah, timely one. But you can always say go on, put it in context with, I don't know, maybe the GDP of the country or the adoption of a platform and things like that. So I think that's ah big trend on having multiple data sets. Contributing towards better decisions towards better product experience is for better services. And, of course, Snowflake is trying to do its part, is doing its part with vision and simplify answers today and the answer on hot spot simplifying blending the interface so that would be super useful. The other big piece, of course, is, um, Predictive Analytics people Talk machine Learning and AI, which is a little bit to buzz worthy. But it is true that we have the technology to drive predictions and and do a better job of understanding behaviors off what's supposed to happen based on understanding the best and the last one. If if if I'm allowed one. Exco What's ahead for data industry, which sounds obvious, but But we're not all the way. There is both cloud the adoption and moving to the cloud as well as the topic of multi Cloud. Increasingly, I think we we finally shifted conversations from Should I go to the cloud or not? Now it's How fast do I do it? And increasingly what we hear is I may want to take the best of the different clouds and how doe I go in and and and embrace a multi cloud reality without having to learn 100 plus different services and nuances of services on on every car and this work technologies like snowflake and thoughts about that can can support a different multiple deployment are being well received by different customs, nerve fault, >>Tom industry trends, or one thing I know. Western Union is really leading in the digital transformation and in your space, What's next for Western Union? >>Yeah, so just add on Requip Thio Christian before I dive into a Western Union use case just to your point. Christian, I really see a convergence happening between how people today work or or manage their personal life, where the applications, the user experiences and the responses are at your fingertips. Easy to use don't need to learn different tools. It's just all there, right, whether you're an android user or an apple user rights, although your fingertips I ask you the same innovation and transmission happening now on the work side, where I see to your point right a convergence happening where not just that the technology teams but even the business teams. They wanna have that same feature, that same functionality, where all their insights their entire way to interact with the business with the business teams with their data with their systems with their products for their services are at their fingertips right where they can go and they can make a change on an iPad or an iPhone and instant effect. They can go change a rule. They could go and modify Uh uh, an algorithm. They can go and look at expanding their product base, and it's just there. It's instant now. This would take time, right? Because this is going to be a transformational journey right across many different industries, but it's part of that. I really see that type of instant gratification, uh, satisfaction, that type of being able to instantly get those insights. Be able thio to really, you know, do what you do on your personal life in your work life every single day. That trend is absolutely it's actually happening. And it's kind of like tag team that into what we're doing at Western Union is exactly that we are actually transforming how our business teams, uh, in our technology teams are able to interact with our customers, interact with our products, interact with our services, interact with our data and our systems instantly. Right? Perfect example that it's that spot where they could go on typing any question they want. And they instigate an answer like that that that was unheard of a year ago, at least for our business. Right being able to to to go and put in in a new rule and and have it flow through the rules engine and have an instant customer impact that's coming right. Being able to instantly change or configure a new product or service with new fee structure and launch in 15 minutes. That's coming, right? All these new transformations about how do we actually better, uh, leverage our capabilities, our products and our services to meet those customer demands instantly. That's where I see the industry going the next couple of years. >>Wonderful. Um, excited to have both of you on the panel this afternoon. So thank you so much for joining us, Christian and Tom as just a quick wrap up. I, you know, learned quite a bit about industry trends and the problems facing companies today. And from the macro view with snowflake and thousands of customers and thought spots, customers and Western Union. The underlying theme is data unity, right? No more fragmented silos, no more fragmented user experiences, but truly bringing everything together in a governed safe way for users. Toe have trust in the data to have trust in what to answer and what insight is being put in front of them. And all of this pulled together so that businesses can make those better decisions more informed and more personalized. Consumer like experiences for your customers in modern technology stacks. So again, thank you both today for joining us, and we look forward to many more conversations in the future. Thank you >>for having me very happy to be here. >>Thank you so much. >>Thanks. >>Thank you, Angela. And thank you, Tom and Christian for sharing your stories. It was really interesting to hear how the events of this year have prompted Western Union to accelerate their digital transformation with snowflake and thought spot and just reflecting on alot sessions in this track, I love seeing how we're making the search experience even easier and even more consumer like in that first session and then moving on to the second session with our customer Hayes. It was really impressive to see how quickly they'd embedded thought spot into their own MD audit product. And then, of course, we heard about Spot Ike, which is making it easier for everybody to get to the Y faster with automated insights. So I'm afraid that wraps up the sessions in this track. We've come to an end, But remember to join us for the exciting product roadmap session coming right up. And then after that, put your questions to the speakers that you've heard in Track two in I'll meet the Experts Roundtable, creating engaging analytics experiences for all. Now all that remains is for me to say thank you for joining us. We really appreciate you taking the time. I hope it's been interesting and valuable. And if it has, we'd love to pick up with you for a 1 to 1 conversation Bye for now.

>>Okay, We're now going into the technical deep dive. We're gonna geek out here a little bit. Ben Wa Dodgeville is here. He's co founder of Snowflake and president of products. And also joining us is Christian Kleinerman. Who's the senior vice president of products. Gentlemen, welcome. Good to see you. >>Yeah, you that >>get this year, they Thanks for having us. >>Very welcome. So it been well, we've heard a lot this morning about the data cloud, and it's becoming my view anyway, the linchpin of your strategy. I'm interested in what technical decisions you made early on. That that led you to this point and even enabled the data cloud. >>Yes. So? So I would say that that a crowd was built in tow in three phases. Really? The initial phase, as you call it, was it was really about 20 minutes. One regions Teoh, Data Cloud and and that region. What was important is to make that region infinity, infinity scalable, right. And that's our architectural, which we call the beauty cross to share the architectural er so that you can plug in as many were clues in that region as a Z without any limits. The limit is really the underlying prop Provide the, you know, resource is which you know, Cal provide the region as a really no limits. So So that z you know, region architecture, I think, was really the building block of the snowflake. That a cloud. But it really didn't stop there. The second aspect Waas Well, it was really data sharing. How you know munity internets within the region, how to share data between 10 and off that region between different customers on that was also enabled by architectures Because we discover, you know, compute and storage so compute You know clusters can access any storage within the region. Eso that's based off the data cloud and then really faced three Which is critical is the expansion the global expansion how we made you know, our cloud domestic layers so that we could talk You know the snowflake vision on different clouds on DNA Now we are running in three cloud on top of three cloud providers. We started with the ws and US West. We moved to assure and then uh, Google g c p On how this this crowd region way started with one crowd region as I said in the W S U S West, and then we create we created, you know, many you know, different regions. We have 22 regions today, all over the world and all over the different in the cloud providers. And what's more important is that these regions are not isolated. You know, Snowflake is one single, you know, system for the world where we created this global data mesh which connects every region such that not only there's no flex system as a whole can can be aware of for these regions, But customers can replicate data across regions on and, you know, share. There are, you know, across the planet if need be. So So this is one single, you know, really? I call it the World Wide Web. Off data that, that's, you know, is this vision of the data cloud. And it really started with this building block, which is a cloud region. >>Thank you for that. Ben White Christian. You and I have talked about this. I mean, that notion of a stripping away the complexity and that's kind of what the data cloud does. But if you think about data architectures, historically they really had no domain knowledge. They've really been focused on the technology toe ingest and analyze and prepare And then, you know, push data out to the business and you're really flipping that model, allowing the sort of domain leaders to be first class citizens if you will, uh, because they're the ones that creating data value, and they're worrying less about infrastructure. But I wonder, do you feel like customers air ready for that change? >>I I love the observation. They've that, uh, so much energy goes in in in enterprises, in organizations today, just dealing with infrastructure and dealing with pipes and plumbing and things like that and something that was insightful from from Ben Juan and and our founders from from Day one WAAS. This is a managed service. We want our customers to focus on the data, getting the insights, getting the decisions in time, not just managing pipes and plumbing and patches and upgrades, and and the the other piece that it's it's it's an interesting reality is that there is this belief that the cloud is simplifying this, and all of a sudden there's no problem but actually understanding each of the public cloud providers is a large undertaking, right? Each of them have 100 plus services, uh, sending upgrades and updates on a constant basis. And that just distracts from the time that it takes to go and say, Here's my data. Here's my data model. Here's how it make better decisions. So at the heart of everything we do is we wanna abstract the infrastructure. We don't wanna abstract the nuance of each of the cloud providers. And as you said, have companies focus on This is the domain expertise or the knowledge for my industry. Are all companies ready for it? I think it's a It's a mixed bag. We we talk to customers on a regular basis every way, every week, every day, and some of them are full on. They've sort of burned the bridges and, like I'm going to the cloud, I'm going to embrace a new model. Some others. You can see the complete like, uh, shock and all expressions like What do you mean? I don't have all these knobs. 2 to 3 can turn. Uh, but I think the future is very clear on how do we get companies to be more competitive through data? >>Well, Ben Ben. Well, it's interesting that Christian mentioned to manage service and that used to be in a hosting. Guys run around the lab lab coats and plugging things in. And of course, you're looking at this differently. It's high degrees of automation. But, you know, one of those areas is workload management. And I wonder how you think about workload management and how that changes with the data cloud. >>Yeah, this is a great question. Actually, Workload management used to be a nightmare. You know, traditional systems on it was a nightmare for the B s and they had to spend most a lot of their time, you know, just managing workloads. And why is that is because all these workloads are running on the single, you know, system and a single cluster The compete for resources. So managing workload that always explain it as explain Tetris, right? You had the first to know when to run. This work will make sure that too big workers are not overlapping. You know, maybe it really is pushed at night, you know, And And you have this 90 window which is not, you know, efficient. Of course, for you a TL because you have delays because of that. But but you have no choice, right? You have a speaks and more for resource is and you have to get the best out of this speaks resource is. And and for sure you don't want to eat here with her to impact your dash boarding workload or your reports, you know, impact and with data science and and And this became a true nine man because because everyone wants to be that a driven meaning that all the entire company wants to run new workers on on this system. And these systems are completely overwhelmed. So so, well below management was, and I may have before Snowflake and Snowflake made it really >>easy. The >>reason is it's no flag. We leverage the crowds who dedicates, you know, compute resources to each work. It's in the snowflake terminology. It's called a warehouse virtual warehouse, and each workload can run in its own virtual warehouse, and each virtual warehouse has its own dedicated competition resources. It's on, you know, I opened with and you can really control how much resources which workload gas by sizing this warehouses. You know, I just think the compute resources that they can use When the workload, you know, starts to execute automatically. The warehouse, the compute resources are turned off, but turned on by snowflake is for resuming a warehouse and you can dynamically resized this warehouse. It can be done by the system automatically. You know if if the conference see of the workload increases or it can be done manually by the administrator or, you know, just suggesting, you know, uh, compute power. You know, for each workload and and the best off that model is not only it gives you a very fine grain. Control on resource is that this work can get Not only workloads are not competing and not impacting it in any other workload. But because of that model, you can hand as many workload as you want. And that's really critical because, as I said, you know, everyone in the organization wants to use data to make decisions, So you have more and more work roads running. And then the Patriots game, you know, would have been impossible in in a in a centralized one single computer, cross the system On the flip side. Oh, is that you have to have a zone administrator off the system. You have to to justify that. The workload is worth running for your organization, right? It's so easy in literally in seconds, you can stand up a new warehouse and and start to run your your crazy on that new compute cluster. And of course, you have to justify if the cost of that because there is a cost, right, snowflake charges by seconds off compute So that cost, you know, is it's justified and you have toe. You know, it's so easy now to hire new workflow than you do new things with snowflake that that that you have to to see, you know, and and look at the trade off the cost off course and managing costs. >>So, Christian been while I use the term nightmare, I'm thinking about previous days of workload management. I mean, I talked to a lot of customers that are trying to reduce the elapsed time of going from data insights, and their nightmare is they've got this complicated data lifecycle. Andi, I'm wondering how you guys think about that. That notion of compressing elapsed time toe data value from raw data to insights. >>Yeah, so? So we we obsess or we we think a lot about this time to insight from the moment that an event happens toe the point that it shows up in a dashboard or a report or some decision or action happens based on it. There are three parts that we think on. How do we reduce that life cycle? The first one which ties to our previous conversation is related toe. Where is their muscle memory on processes or ways of doing things that don't actually make us much sense? My favorite example is you say you ask any any organization. Do you run pipelines and ingestion and transformation at two and three in the morning? And the answer is, Oh yeah, we do that. And if you go in and say, Why do you do that? The answer is typically, well, that's when the resource is are available Back to Ben Wallace. Tetris, right? That's that's when it was possible. But then you ask, Would you really want to run it two and three in the morning? If if you could do it sooner, we could do it. Mawr in time, riel time with when the event happened. So first part of it is back to removing the constraints of the infrastructures. How about running transformations and their ingestion when the business best needs it? When it's the lowest time to inside the lowest latency, not one of technology lets you do it. So that's the the the easy one out the door. The second one is instead of just fully optimizing a process, where can you remove steps of the process? This is where all of our data sharing and the snowflake data marketplace come into place. How about if you need to go in and just data from a SAS application vendor or maybe from a commercial data provider and imagine the dream off? You wouldn't have to be running constant iterations and FTP s and cracking C S V files and things like that. What if it's always available in your environment, always up to date, And that, in our mind, is a lot more revolutionary, which is not? Let's take away a process of ingesting and copying data and optimize it. How about not copying in the first place? So that's back to number two on, then back to number three is is what we do day in and day out on making sure our platform delivers the best performance. Make it faster. The combination of those three things has led many of our customers, and and And you'll see it through many of the customer testimonials today that they get insights and decisions and actions way faster, in part by removing steps, in part by doing away with all habits and in part because we deliver exceptional performance. >>Thank you, Christian. Now, Ben Wa is you know, we're big proponents of this idea of the main driven design and data architecture. Er, you know, for example, customers building entire applications and what I like all data products or data services on their data platform. I wonder if you could talk about the types of applications and services that you're seeing >>built >>on top of snowflake. >>Yeah, and And I have to say that this is a critical aspect of snowflake is to create this platform and and really help application to be built on top of this platform. And the more application we have, the better the platform will be. It is like, you know, the the analogies with your iPhone. If your iPhone that no applications, you know it would be useless. It's it's an empty platforms. So So we are really encouraging. You know, applications to be belong to the top of snowflake and from there one actually many applications and many off our customers are building applications on snowflake. We estimated that's about 30% are running already applications on top off our platform. And the reason is is off course because it's it's so easy to get compute resources. There is no limit in scale in our viability, their ability. So all these characteristics are critical for for an application on DWI deliver that you know from day One Now we have improved, you know, our increased the scope off the platform by adding, you know, Java in competition and Snow Park, which which was announced today. That's also you know, it is an enabler. Eso in terms off type of application. It's really, you know, all over and and what I like actually needs to be surprised, right? I don't know what well being on top of snowflake and how it will be the world, but with that are sharing. Also, we are opening the door to a new type of applications which are deliver of the other marketplace. Uh, where, You know, one can get this application died inside the platform, right? The platform is distributing this application, and today there was a presentation on a Christian T notes about, >>you >>know, 20 finds, which, you know, is this machine learning, you know, which is providing toe. You know, any users off snowflake off the application and and machine learning, you know, to find, you know, and apply model on on your data and enrich your data. So data enrichment, I think, will be a huge aspect of snowflake and data enrichment with machine learning would be a big, you know, use case for these applications. Also, how to get there are, you know, inside the platform. You know, a lot of applications led him to do that. Eso machine learning. Uh, that engineering enrichments away. These are application that we run on the platform. >>Great. Hey, we just got a minute or so left in. Earlier today, we ran a video. We saw that you guys announced the startup competition, >>which >>is awesome. Ben, while you're a judge in this competition, what can you tell us about this >>Yeah, >>e you know, for me, we are still a startup. I didn't you know yet, you know, realize that we're not anymore. Startup. I really, you know, you really feel about you know, l things, you know, a new startups, you know, on that. That's very important for Snowflake. We have. We were started yesterday, and we want to have new startups. So So the ends, the idea of this program, the other aspect off that program is also toe help, you know, started to build on top of snowflake and to enrich. You know, this this pain, you know, rich ecosystem that snowflake is or the data cloud off that a cloud is And we want to, you know, add and boost. You know that that excitement for the platform, so So the ants, you know, it's a win win. It's a win, you know, for for new startups. And it's a win, ofcourse for us. Because it will make the platform even better. >>Yeah, And startups, or where innovation happens. So registrations open. I've heard, uh, several, uh, startups have have signed up. You goto snowflake dot com slash startup challenge, and you can learn mawr. That's exciting program. An initiative. So thank you for doing that on behalf of of startups out there and thanks. Ben Wa and Christian. Yeah, I really appreciate you guys coming on Great conversation. >>Thanks for David. >>You're welcome. And when we talk, Thio go to market >>pros. They >>always tell us that one of the key tenets is to stay close to the customer. Well, we want to find out how data helps us. To do that in our next segment. Brings in to chief revenue officers to give us their perspective on how data is helping their customers transform. Business is digitally. Let's watch.

>> Hello everyone, we're here at the Snowflake Data Cloud Summit. This is the Tech Titans panel. We're going to explore some of the trends that are shaping new data capabilities and specifically how organizations are transforming their companies, with data and insights. And with me are three amazing guest panelists. Christian Kleinerman is the senior vice president of product at Snowflake. He's joined by Mark Nelson, who's the EVP of product development at Salesforce/Tableau and Mai-Lan Thompson Bukovec, who's the vice president of Block and Object Storage at Amazon web services. Folks, thanks so much for coming on the program. Great to see you all. >> Thanks for having us. >> Nice to see you. >> Glad to be here. >> Excellent, so here in this session, you know, we have the confluence of the data cloud. We have simple and cost effective storage repositories and the visualization of data. These are three ingredients that are really critical for quickly analyzing and turning data into insights and telling stories with data. So, Christian, let me start with you. Of course, this is all enabled by the Cloud and Snowflake. You're extending that to this data cloud. One of the things that we can do today with data that we say weren't able to do maybe five years ago. >> Yeah, certainly I think there is lots of things that we can integrate specific actions but if you were to zoom out and look at the big picture, our ability to reason through data to inform our choices to date with data is bigger than ever before. There are still many companies that have to decide to sample data or to throw away older data, or they don't have the right data from external companies to put their decisions and actions in context. Now we have the technology and the platforms to bring all that data together, tear down silos and look a 360 of a customer or entire action. So I think it's reasoning through data that has increased the capability of organizations dramatically in the last few years. >> So Mai-Lan, when I was a young pup, at IDC, I started the storage program there, many, many moons ago. And so I always pay attention to what's going on in storage, back of my mind. And S3 people forget, sometimes, that was actually the very first cloud product announced by AWS, which really ushered in the cloud era. And that was 2006, it fundamentally changed the way we think about storing data. I wonder if you can explain how S3 specifically in an object storage generally, you know, with get put really transformed storage from a blocker to an enabler of some of these new workloads that we're seeing. >> Absolutely, I think it has been transformational for many companies in every industry. And the reason for that is because in S3, you can consolidate all the different data sets that today are scattered around so many companies, different data centers. And so if you about it, S3 gives the ability to put unstructured data which are video recordings and images. It puts semi structured data which is the CSV file, which every company has lots of. And that has also support for structured data types like parquet files, which drive a lot of the business decisions that every company has to make today. And so if you think about S3, which launched on Pi day in March of 2006, S3 started off as an object store, but it has evolved into so much more than that, where companies all over the world, and every industry are taking those different data sets, they're putting it in S3, they're growing their data and then they're growing the value that they capture on top of that data. And that is the separation we see that snowflake talks about and many of the pioneers across different industries talk about, which is a separation of the growth of storage and the growth of your computer applications. And what's happening is that when you have a place to put your data like S3, which is secure by default and has the availability and the durability and the operational profile you know, and can trust, then the innovation of the application developers really take over, and you know, one example of that is where we have a customer in the financial sector and they started to use S3 to put their customer care recordings. And they were just using it for storage because that obviously dataset grows very quickly. And then somebody in their fraud department got the idea of doing machine learning on top of those customer care recordings. And when they did that they found really interesting data that they could then feed into their fraud detection models. And so you get this kind of alchemy of innovation that happens when you take the datasets of today and yesterday and tomorrow you put them all in one place which is the history and the innovation of your application, developers just takes over and builds, not just what you need today but what you need in the future as well. >> Thank you for that. Mark, I want to bring you into this panel. It's great to have you here. So thank you. I mean, Tableau has been a game changer for organizations. I remember my first, Tableau conference, passionate customers and really bringing cloud-like agility and simplicity to visualization just totally changed the way people thought about data and met with massive data volumes and simplified access. And now we're seeing new workloads that are developing on top of data and Snowflake data and the cloud. Can you talk about how your customers are really telling stories and bringing to life those stories with data on top of things like S3, which Mai-Lan was just talking about? >> Yeah, for sure. Building on what Christian and Mai-Lan have already said our mission at Tableau has always been help people see and understand data. And you look at the amazing advances that are happening in storage and data processing. And now, the data that you can see and play with is so amazing, right? Like at this point in time, it's really nothing short of a new microscope or a new telescope that really lets you understand patterns. They were always there in the world, but you literally couldn't see them because of the limitations of the amount of data that you could bring into the picture, because of the amount of processing power and the amount of sharing of data that you could bring into the picture. And now like you said, these three things are coming together and this amazing ability to see and tell stories with your data combined with the fact that you've got so much more data at your fingertips, the fact that you can now process that data, look at that data share that data in ways that was never possible. Again, I'll go back to that analogy. It feels like the invention of a new microscope, a new telescope a new way to look at the world and tell stories and get to insights that were just, were never possible before. >> So thank you for that, and then Christian I want to come back to this notion of the data cloud and, you know, it's a very powerful concept and of course it's good marketing, but I wonder if you could add some additional color for the audience. I mean, what more can you tell us about the data cloud, how you're seeing it evolving and maybe building on some of the things that Mark was just talking about just in terms of, you know, bringing this vision into reality? >> Certainly, yeah. Data cloud for sure, is bigger and more concrete than just the marketing value of it. The big insight behind our vision for the data cloud is that just the technology, a capability, just a cloud data platform is not what gets organizations to be able to be a data driven, to be able to make great use of data or be highly capable in terms of data ability. The other element beyond technology is the access and availability of data to put their own data in context or enrich based on the knowledge or data from other third parties. So the data cloud, the way to think about it is, is a combination of both technology, which for Snowflake is our Cloud Data platform in all the workloads, the ability to do data warehousing and queries and speeds and feeds fit in there and data engineering, et cetera. But it's also, how do we make it easier for our customers to have access to the data that they need or they could benefit to improve the decisions for their own organizations. Think of the analogy of a set top box. I can give you a great technically set top box but if there's no content on the other side, it makes it difficult for you to get value out of it. That's how we should all be thinking about it, the data cloud, it's technology, but it's also seamless access to data. >> And Mai-Lan, can you give us a sense of the scope and what kind of scale are you seeing with Snowflake on AWS? >> Well, Snowflake has always driven as Christian as a very high transaction rate to S3. And in fact, when Christian and I were talking just yesterday, we were talking about some of the things that have really been remarkable about the long partnership that we've had over the years. And so I'll give you an example of how that evolution has really worked. So as you know, S3 has, is, you know, the first AWS services that is launched and we have customers who have petabytes, hundreds of petabytes and exabytes of storage on history. And so from the ground up S3 has been built for scale. And so when we have customers, like Snowflake that have very high transaction rates for requests, for S3 storage, we put our customer hat on and we ask customers like Snowflake, how do you think about performance? Not just what performance do you need but how do you think about performance? And you know, when Christian and his team were working through the demands of making requests to their S3 data, they were talking about some pretty high spikes over time and just a lot of volume. And so when we built improvements, into our performance over time, we put that hat on for work, you know, Snowflake was telling us what they needed. And then we built our performance model not around a bucket or an account. We built it around a request rate per prefix, because that's what Snowflake and other customers told us they needed. And so when you think about how we scale our performance, we scale it based on a prefix and not a bucket in our account, which other cloud providers do. We do it in this unique way because 90% of our customer roadmap across AWS comes from customer requests. And then that's what Snowflake and other customers were saying is that, "Hey, I think about my performance based on a prefix and of an object and not some, you know, arbitrary semantic of how I happened to organize my buckets." I think the other thing I would also throw out there for skill is, as you might imagine, S3 is a very large distributed system. And again, if I go back to how we architected for our performance improvements, we architected in such a way that a customer like Snowflake, could come in and they could take advantage of horizontally scaling. They can do parallel data retrievals and puts in gets for your data. And when they do that they can get tens of thousands of requests per second because they're taking advantage of the scale of S3. And so, you know, when we think about scale it's not just scale which is the growth of your storage, which every customer needs. IDC says that digital data is growing at 40% year over year. So every customer needs a place to put all of those storage sets that are growing. But the way we also have worked together for many years is this, how can we think about how Snowflake and other customers are driving these patterns of access on top of the data, not just the last history of the storage, but the access and then how can we architect often very uniquely as I talked about with our request rate in such a way that they can achieve what they need to do not just today, but in the future. >> I don't know, three companies here that don't often take their customer hats off. Mark, I wonder if we could come to you, you know, during the Data Cloud Summit, we've been exploring this notion that innovation in technology is really evolved from point products you know, the next generation of server or software tool to platforms that made infrastructure simpler or called functions and now it's evolving into leveraging ecosystems. You know, the power of many versus the resources of one. So my question is, you know, how are you all collaborating and creating innovations that your customers can leverage? >> Yeah, for sure, so certainly, you know Tableau and Snowflake, you know, kind of where were dropped at natural partners from the beginning, right? Like putting that visualization engine on top of Snowflake to, you know, combine that processing power and data and the ability to visualize it was obvious. As you talk about the larger ecosystem now of course, Tableau is part of Salesforce. And so there's a much more interesting story now to be told across the three companies, one in two and a half maybe as we talk about Tableau and Salesforce combined together of really having this full circle of Salesforce you know, with this amazing set of business apps that so much value for customers and getting the data that comes out of their Salesforce applications, putting it into Snowflake so that you can combine that, share that, you process it combine it with data, not just for across Salesforce, but from your other apps in a way that you want. And then put Tableau on top of it. Now you're talking about this amazing platform ecosystem of data, you know, coming from your most valuable business applications in the world with the most, you know, sales opportunity objects, marketing, service, all of that information flowing into this flexible data platform and then this amazing visualization platform on top of it. And there's really no end of the things that our customers can do with that combination >> Christian we're out of time, but I wonder if you could bring us home and I want to end with, you know let's say, you know, people, some people here maybe they don't, maybe they're still struggling with the cumbersome nature of let's say their on-prem data, warehouses. You know, the kids just unplugged them because they rely on them for certain things like reporting but let's say they to raise the bar on their data and analytics, what would you advise for a next step for them? >> Yeah I think the first part or first step to take is around embrace the cloud and the promise on the abilities of cloud technology. There's many studies where relative to peers, companies that are embracing data are coming out ahead and outperforming their peers. And with traditional technology on-prem technology, you ended up with a proliferation of silos and copies of data. And a lot of energy went into managing those on-prem systems and making copies and data governance and security and cloud technology and the type of platform that the Snowflake has brought to market enables organizations to focus on the data, the data model, the data insights, and not necessarily on managing the infrastructure. So I think that will be the first recommendation from our end. Embrace cloud, get onto a modern cloud data platform, make sure that you're spending your time on data, not managing infrastructure and seeing what the infrastructure lets you do. >> It makes a lot of sense, guys. Thanks, thanks so much. We'll have to end it there and thank you everybody for watching. Keep it right there. We'll be back, with the next segment, right after this short break.