(gentle music) >> Welcome to the new abnormal. Yes, you know, the pandemic, it did accelerate the shift to digital, but it's also created disorder in our world. I mean, every day it seems that companies are resetting their office reopening playbooks. They're rethinking policies on large gatherings and vaccination mandates. There's an acute labor shortage in many industries, and we're seeing an inventory glutton in certain goods, like bleach and hand sanitizer. Airline schedules and pricing algorithms, they're all unsettled. Is inflation transitory? Is that a real threat to the economy? GDP forecasts are seesawing. In short, the world is out of whack and the need for fast access to quality, trusted and governed data has never been greater. Can coherent data strategies help solve these problems, or will we have to wait for the world to reach some type of natural equilibrium? And how are companies, like Google, helping customers solve these problems in critical industries, like financial services, retail, manufacturing, and other sectors? And with me to share his perspectives on data is a long-time CUBE alum, Bruno Aziza. He's the head of data analytics at Google. Bruno, my friend, great to see you again, welcome. >> Great to see you, thanks for having me, Dave. >> So you heard my little narrative upfront, how do you see this crazy world of data today? >> I think you're right. I think there's a lot going on in the world of data analytics today. I mean, certainly over the last 30 years, we've all tried to just make the life of people better and give them access more readily to the information that they need. But certainly over the last year and half, two years, we've seen an amazing acceleration in digital transformation. And what I think we're seeing is that even after three decades of investment in the data analytics world, you know, the opportunity is still really out wide and is still available for organizations to get value out of their data. I was looking at some of the latest research in the market, and, you know, only 32% of companies are actually able to say that they get tangible, valuable insights out of their data. So after all these years, we still have a lot of opportunity ahead of us, of course, with the democratization of access to data, but also the advent in machine learning and AI, so that people can make better decisions faster than their competitors. >> So do you think that the pandemic has heightened that sort of awareness as they were sort of forced to pivot to digital, that they're maybe not getting enough out of their data strategies? That maybe their whatever, their organization, their technology, their way they were thinking about data was not adequate and didn't allow them to be agile enough? Why do you think that only 32% are getting that type of value? >> I think it's true. I think, one, digital transformation has been accelerated over the last two years. I think, you know, if you look at research the last two years, I've seen almost a decade of digital acceleration, you know, happening. But I also think that we're hitting a particular time where employees are expecting more from their employers in terms of the type of insights that can get. Consumers are now evolving, right? So they want more information. And I think now technology has evolved to a point where it's a lot easier to provision a data cloud environment so you can get more data out to your constituents. So I think the connection of these three things, expectation of employees, expectation of customers to better customer experiences, and, of course, the global environment, has accelerated quite a bit, you know, where the space can go. And for people like me, you know, 20 years ago, nobody really cared about databases and so forth. And now I feel like, you know, everybody's, you know, understands the value that we can get out of it. And we're kind of getting, you know, in the sexy territory, finally, data now is sexy for everyone and there's a lot of interest in the space. >> You and I met, of course, in the early days of Hadoop. And there were many things about Hadoop that were profound and, of course, many things that, you know, just were overly complex, et cetera. And one of the things we saw was this sort of decentralization. We thought that Hadoop was going to send five megabytes of code to petabytes of data. And what happened is everything, you know, came into this centralized repository and that centralized thinking, the data pipeline organization was very centralized. Are you seeing companies rethink that? I mean, has the cloud changed their thinking? You know, especially as the cloud expands to the edge, on-prem, everywhere. How are you seeing organizations rethink their regimes for data? >> Yeah, I think, you know, we've seen over the last three decades kind of the pendulum, right, from really centralizing everything and making the IT organization kind of the center of excellence for data analytics, all the way to now, you know, providing data as a self-service, you know, application for end-users. And I think what we're seeing now is there's a few forces happening. The first one is, of course, multicloud, right? So the world today is clearly multicloud and it's going to be multicloud for many, many years. So I think not only are now people considering their on-prem information, but they're also looking at data across multiple clouds. And so I think that is a huge force for chief data officers to consider is that, you know, you're not going to have data centralized in one place, nicely organized, because sometimes it's going to be a factor of where you want to be as an organization. Maybe you're going to be partnering with other organizations that have data in other clouds. And so you want to have an architecture that is modern and that accommodates this idea of an open cloud. The second problem that we see is this idea around data governance, intelligent data governance, right? So the world of managing data is becoming more complex because, of course, you're now dealing with many different speeds, you're dealing with many different types of data. And so you want to be able to empower people to get access to the information, without necessarily having to move this data, so they can make quick decisions on the data. So this idea of a data fabric is becoming really important. And then the third trend that we see, of course, is this idea around data sharing, right? People are now looking to use their own data to create a data economy around their business. And so the ability to augment their existing data with external data and create data products around it is becoming more and more important to the chief data officers. So it's really interesting we're seeing a switch from, you know, this chief data officer really only worried about governance, to this we're now worried about innovation, while making sure that security and governance is taken care of. You know, we call this freedom within the framework, which is a great challenge, but a great opportunity for many of these data leaders. >> You mentioned several things there. Self-service, multicloud, the governance key, especially if we can federate that governance in a decentralized world. Data fabric is interesting. I was talking to Zhamak Dehghani this weekend on email. She coined the term data mesh. And there seems to be some confusion, data mesh, data fabric. I think Gartner's using the term fabric. I know like NetApp, I think coined that term, which to me is like an infrastructure layer, you know. But what do you mean by data fabric? >> Well, the first thing that I would say is that it's not up to the vendors to define what it is. It really is up to the customer. The problem that we're seeing these customers trying to fix is you have a diversity of data, right? So you have data stored in the data mart, in a data lake, in a data warehouse, and they all have their specific, you know, reasons for being there. And so this idea of a data fabric is that without moving the data, can you, one, govern it intelligently? And, two, can you provide landing zones for people to actually do their work without having to go through the pain of setting up new infrastructure, or moving information left and right, and creating new applications? So it's this idea of basically taking advantage of your existing environment, but also governing it centrally, and also now providing self-service capabilities so people can do their job easily. So, you know, you might call it a data mesh, you might call it a data fabric. You know, the terminology to me, you know, doesn't seem to be the barrier. The issue today is how do we enable, you know, this freedom for customers? Because, you know, I think what we've seen with vendors out there is they're trying to just take the customer down to their paradigms. So if they believe in all the answers need to be in a data warehouse, they're going to guide the customer there. If they believe that, you know, everything needs to be in a data lake, they're going to guide the customer there. What we believe in is this idea of choice. You should be able to do every single use case. And we should be able to enable you to manage it intelligently, both from an access standpoint, as well as a governance standpoint. >> So when you think about those different, and I like that, you're making it somewhat technology agnostic, so whether it's a data warehouse, or a data lake, or a data hub, a data mart, those are nodes within the mesh or the fabric, right? That are discoverable, accessible, I guess, governed. I think that there's got to be some kind of centralized governance edict, but in a federated governance model so you don't have to move the data around. Is that how you're thinking about it? >> Absolutely, you know, in our recent event, in the Data Cloud Summit, we had Equifax. So the gentleman there was the VP of data governance and data fabric. So you can start seeing now these roles, you know, created around this problem. And really when you listen to what they're trying to do, they're trying to provide as much value as they can without changing the habits of their users. I think that's what's key here, is that the minute you start changing habits, force people into paradigms that maybe, you know, are useful for you as a vendor, but not so useful to the customer, you get into the danger zone. So the idea here is how can you provide a broad enough platform, a platform that is deep enough, so the data can be intelligently managed and also distributed and activated at the point of interaction for the end-user, so they can do their job a lot easier? And that's really what we're about, is how do you make data simpler? How do you make, you know, the process of getting to insight a lot more fluid without changing habits necessarily, both on the IT side and the business side? >> I want to get to specifics on what Google is doing, but the last sort of uber-trends I want to ask you about 'cause, again, we've known each other for a long time. We've seen this data world grow up. And you're right, 20, 30 years ago, nobody cared about database. Well, maybe 30 years ago. But 20 years ago, it was a boring market, right now it's like the hottest thing going. But we saw, you know, bromide like data is the new oil. Well, we found out, well, actually data is more valuable than oil 'cause you can use, you know, data in a lot of different places, oil you can use once. And then the term like data as an asset, and you said data sharing. And it brings up the notion that, you know, you don't want to share your assets, but you do want to share your data as long as it can be governed. So we're starting to change the language that we use to describe data and our thinking is changing. And so it says to me that the next 10 years, aren't going to be like the last 10 years. What are your thoughts on that? >> I think you're absolutely right. I think if you look at how companies are maturing their use of data, obviously the first barrier is, "How do I, as a company, make sure that I take advantage of my data as an asset? How do I turn, you know, all this information into a sustainable, competitive advantage, really top of mind for organizations?" The second piece around it is, "How do I create now this innovation flywheel so that I can create value for my customers, and my employees, and my partners?" And then, finally, "How do I use data as the center of a product that I can then further monetize and create further value into my ecosystem?" I think the piece that's been happening that people have not talked a lot about I think, with the cloud, what's come is it's given us the opportunity to think about data as an ecosystem. Now you and I are partnering on insights. You and I are creating assets that might be the combination of your data and my data. Maybe it's an intelligent application on top of that data that now has become an intelligent, rich experience, if you will, that we can either both monetize or that we can drive value from. And so I think, you know, it's just scratching the surface on that. But I think that's where the next 10 years, to your point, are going to be, is that the companies that win with data are going to create products, intelligent products, out of that data. And they're just going to take us to places that, you know, we are not even thinking about right now. >> Yeah, and I think you're right on. That is going to be one of the big differences in the coming years is data as product. And that brings up sort of the line of business, right? I mean the lines of business heads historically have been kind of removed from the data group, that's why I was asking you about the organization before. But let's get into Google. How do you describe Google's strategy, its approach, and why it's unique? >> You know, I think one of the reasons, so I just, you know, started about a year ago, and one of the reasons for why I found, you know, the Google mission interesting, is that it's really rooted at who we are and what we do. If you think about it, we make data simple. That's really what we're about. And we live that value. If you go to google.com today, what's happening? Right, as an end-user, you don't need any training. You're going to type in whatever it is that you're looking for, and then we're going to return to you highly personalized, highly actionable insights to you as a consumer of insights, if you will. And I think that's where the market is going to. Now, you know, making data simple doesn't mean that you have to have simple infrastructure. In fact, you need to be able to handle sophistication at scale. And so simply our differentiation here is how do we go from highly sophisticated world of the internet, disconnected data, changing all the time, vast volume, and a lot of different types of data, to a simple answer that's actionable to the end-user? It's intelligence. And so our differentiation is around that. Our mission is to make data simple and we use intelligence to take the sophistication and provide to you an answer that's highly actionable, highly relevant, highly personalized for you, so you can go on and do your job, 'cause ultimately the majority of people are not in the data business. And so they need to get the information just like you said, as a business user, that's relevant, actionable, timely, so they can go off and, you know, create value for their organization. >> So I don't think anybody would argue that Google, obviously, are data experts, arguably the best in the world. But it's interesting, some of the uniqueness here that I'm hearing in your language. You used the word multicloud, Amazon doesn't, you know, use that term. So that's a differentiation. And you sell a cloud, right? You sell cloud services, but you're talking about multicloud. You sell databases, but, of course, you host other databases, like Snowflake. So where do you fit in all this? Do you see your role, as the head of data analytics, is to sort of be the chef that helps combine all these different capabilities? Or are you sort of trying to help people adopt Google products and services? How should we think about that? >> Yeah, the best way to think about, you know, I spend 60 to 70% of my time with customers. And the best way I can think about our role is to be your innovation partner as an organization. And, you know, whichever is the scenario that you're going to be using, I think you talked about open cloud, I think another uniqueness of Google is that we have a very partner friendly, you know, approach to the business. Because we realized that when you walk into an enterprise or a digital native, and so forth, they already have a lot of assets that they have accumulated over the years. And it might be technology assets, but also might be knowledge, and know-how, right? So we want to be able to be the innovation vendor that enables you to take these assets, put them together, and create simplicity towards the data. You know, ultimately, you can have all types of complexity in the backend. But what we can do the best for you is make that really simple, really integrated, really unified, so you, as a business user, you don't have to worry about, "Where is my data? Do I need to think about moving data from here to there? Are there things that I can do only if the data is formatted that way and this way?" We want to remove all that complexity, just like we do it on google.com, so you can do your job. And so that's our job, and that's the reason for why people come to us, is because they see that we can be their best innovation partner, regardless where the data is and regardless, you know, what part of the stack they're using. >> Well, I want to take an example, because my example, I mean, I don't know Google's portfolio like you do, obviously, but one of the things I hear from customers is, "We're trying to inject as much machine intelligence into our data as possible. We see opportunities to automate." So I look at something like BigQuery, which has a strong affinity in embedded machine learning and machine intelligence, as an example, maybe of that simplification. But maybe you could pick up on that and give us some other concrete examples. >> Yeah, specifically on products, I mean, there are a lot products we can talk about, and certainly BigQuery has tremendous market momentum. You know, and it's really anchored on this idea that, you know, the idea behind BigQuery is that just add data and we'll do the rest, right? So that's kind of the idea where you can start small and you can scale at incredible, you know, volumes without really having to think about tuning it, about creating indexes, and so forth. Also, we think about BigQuery as the place that people start in order to build their ecosystem. That's why we've invested a lot in machine learning. Just a few years ago, we introduced this functionality called BigQuery Machine Learning, or BigQuery ML, if you're familiar with it. And you notice out of the top 100 customers we have, 80% of these customers are using machine learning right out of, you know, BigQuery. So now why is that? Why is it that it's so easy to use machine learning using BigQuery is because it's built in. It was built from the ground up. Instead of thinking about machine learning as an afterthought, or maybe something that only data scientists have access to that you're going to license just for narrow scenarios, we think about you have your data in a warehouse that can scale, that is equally awesome at small volume as very large volume, and we build on top of that. You know, similarly, we just announced our analytics exchange, which is basically the place where you can now build these data analytics assets that we discussed, so you can now build an ecosystem that creates value for end-users. And so BigQuery is really at the center of a lot of that strategy, but it's not unlike any of the other products that we have. We want to make it simple for people to onboard, simple to scale, to really accomplish, you know, whatever success is ahead of them. >> Well, I think ecosystems is another one of those big differences in the coming decade, because you're able to build ecosystems around data, especially if you can share that data, you know, and do so in a governed and secure way. But it leads to my question on industries, and I'm wondering if you see any patterns emerging in industries? And each industry seems to have its own unique disruption scenario. You know, retail obviously has been, you know, disrupted with online commerce. And healthcare with, of course, the pandemic. Financial services, you wonder, "Okay, are traditional banks going to lose control of payment systems?" Manufacturing you see our reliance on China's supply chain in, of course, North America. Are you seeing any patterns in industry as it pertains to data? And what can you share with us in terms of insights there? >> Yeah, we are. And, I mean, you know, there's obviously the industries that are, you know, very data savvy or data hungry. You think about, you know, the telecommunication industry, you think about manufacturing, you think about financial services and retail. I mean, financial services and retailers are particularly interesting, because they're kind of both in the retail business and having to deal with this level of complexity of they have physical locations and they also have a relationship with people online, so they really want to be able to bring these two worlds together. You know, I think, you know, about those scenarios of Carrefour, for instance. It's a large retailer in Europe that has been able to not only to, you know, onboard on our platform and they're using, you know, everything from BigQuery, all the way to Looker, but also now create the data assets that enable them to differentiate within their own industry. And so we see a lot of that happening across pretty much all industries. It's difficult to think about an industry that is not really taking a hard look at their data strategy recently, especially over the last two years, and really thought about how they're creating innovation. We have actually created what we call design patterns, which are basically blueprints for organization to take on. It's free, it's free guidance, it's free datasets and code that can accelerate their building of these innovative solutions. So think about the, you know, ability to determine propensity to purchase. Or build, you know, a big trend is recommendation systems. Another one is anomaly detection, and this was great because anomaly detection is a scenario that works in telco, but also in financial services. So we certainly are seeing now companies moving up in their level of maturity, because we're making it easier and simpler for them to assemble these technologies and create, you know, what we call data-rich experiences. >> The last question is how you see the emerging edge, IoT, analytics in that space? You know, a lot of the machine learning or AI today is modeling in the cloud, as you well know. But when you think about a lot of the consumer applications, whether it's voice recognition or, you know, or fingerprinting, et cetera, you're seeing some really interesting use cases that could bleed into the enterprise. And we think about AI inferencing at the edge as really driving a lot of value. How do you see that playing out and what's Google's role there? >> So there's a lot going on in that space. I'll give you just a simple example. Maybe something that's easy for the community to understand is there's still ways that we define certain metrics that are not taking into account what actually is happening in reality. I was just talking to a company whose job is to deliver meals to people. And what they have realized is that in order for them to predict exactly the time it's going to take them from the kitchen to your desk, they have to take into account the fact that distance sometimes it's not just horizontal, it's also vertical. So if you're distributing and you're delivering meals, you know, in Singapore, for instance, high density, you have to understand maybe the data coming from the elevators. So you can determine, "Oh, if you're on the 20th floor, now my distance to you, and my ability to forecast exactly when you're going to get that meal, is going to be different than if you are on the fifth floor. And, particularly, if you're ordering at 11:32, versus if you're ordering at 11:58." And so what's happening here is that as people are developing these intelligent systems, they're now starting to input a lot of information that historically we might not have thought about, but that actually is very relevant to the end-user. And so, you know, how do you do that? Again, and you have to have a platform that enables you to have a large diversity of use cases, and that thinks ahead, if you will, of the problems you might run into. Lots and lots of innovation in this space. I mean, we work with, you know, companies like Ford to, you know, reinvent the connected, you know, cars. We work with companies like Vodafone, 700 use cases, to think about how they're going to deal with what they call their data ocean. You know, I thought you would like this term, because we've gone from data lakes to data oceans. And so there is certainly a ton of innovation and certainly, you know, the chief data officers that I have the opportunity to work with are really not short of ideas. I think what's been happening up until now, they haven't had this kind of single, unified, simple experience that they can use in order to onboard quickly and then enable their people to build great, rich-data applications. >> Yeah, we certainly had fun with that over the years, data lake or data ocean. And thank you for remembering that, Bruno. Always a pleasure seeing you. Thanks so much for your time and sharing your perspectives, and informing us about what Google's up to. Can't wait to have you back. >> Thanks for having me, Dave. >> All right, and thank you for watching, everybody. This is Dave Vellante. Appreciate you watching this CUBE Conversation, and we'll see you next time. (gentle music)

>>from around the globe. It's the >>cube presenting >>active de que intelligent automation for data quality brought to you by Iota Ho >>Welcome to the sixth episode of the I. O. Tahoe data automation series. On the cube. We're gonna start off with a segment on how to accelerate the adoption of snowflake with Glenn Grossman, who is the enterprise account executive from Snowflake and yusef khan, the head of data services from Iota. Gentlemen welcome. >>Good afternoon. Good morning, Good evening. Dave. >>Good to see you. Dave. Good to see you. >>Okay glenn uh let's start with you. I mean the Cube hosted the snowflake data cloud summit in November and we heard from customers and going from love the tagline zero to snowflake, you know, 90 minutes very quickly. And of course you want to make it simple and attractive for enterprises to move data and analytics into the snowflake platform but help us understand once the data is there, how is snowflake helping to achieve savings compared to the data lake? >>Absolutely. dave. It's a great question, you know, it starts off first with the notion and uh kind of, we coined it in the industry or t shirt size pricing. You know, you don't necessarily always need the performance of a high end sports car when you're just trying to go get some groceries and drive down the street 20 mph. The t shirt pricing really aligns to, depending on what your operational workload is to support the business and the value that you need from that business? Not every day. Do you need data? Every second of the moment? Might be once a day, once a week through that t shirt size price and we can align for the performance according to the environmental needs of the business. What those drivers are the key performance indicators to drive that insight to make better decisions, It allows us to control that cost. So to my point, not always do you need the performance of a Ferrari? Maybe you need the performance and gas mileage of the Honda Civic if you would just get and deliver the value of the business but knowing that you have that entire performance landscape at a moments notice and that's really what what allows us to hold and get away from. How much is it going to cost me in a data lake type of environment? >>Got it. Thank you for that yussef. Where does Io Tahoe fit into this equation? I mean what's, what's, what's unique about the approach that you're taking towards this notion of mobilizing data on snowflake? >>Well, Dave in the first instance we profile the data itself at the data level, so not just at the level of metadata and we do that wherever that data lives. So it could be structured data could be semi structured data could be unstructured data and that data could be on premise. It could be in the cloud or it could be on some kind of SAAS platform. And so we profile this data at the source system that is feeding snowflake within snowflake itself within the end applications and the reports that the snowflake environment is serving. So what we've done here is take our machine learning discovery technology and make snowflake itself the repository for knowledge and insights on data. And this is pretty unique. Uh automation in the form of our P. A. Is being applied to the data both before after and within snowflake. And so the ultimate outcome is that business users can have a much greater degree of confidence that the data they're using can be trusted. Um The other thing we do uh which is unique is employee data R. P. A. To proactively detect and recommend fixes the data quality so that removes the manual time and effort and cost it takes to fix those data quality issues. Uh If they're left unchecked and untouched >>so that's key to things their trust, nobody's gonna use the data. It's not trusted. But also context. If you think about it, we've contextualized are operational systems but not our analytic system. So there's a big step forward glen. I wonder if you can tell us how customers are managing data quality when they migrate to snowflake because there's a lot of baggage in in traditional data warehouses and data lakes and and data hubs. Maybe you can talk about why this is a challenge for customers. And like for instance can you proactively address some of those challenges that customers face >>that we certainly can. They have. You know, data quality. Legacy data sources are always inherent with D. Q. Issues whether it's been master data management and data stewardship programs over the last really almost two decades right now, you do have systemic data issues. You have siloed data, you have information operational, data stores data marks. It became a hodgepodge when organizations are starting their journey to migrate to the cloud. One of the things that were first doing is that inspection of data um you know first and foremost even looking to retire legacy data sources that aren't even used across the enterprise but because they were part of the systemic long running operational on premise technology, it stayed there when we start to look at data pipelines as we onboard a customer. You know we want to do that era. We want to do QA and quality assurance so that we can, And our ultimate goal eliminate the garbage in garbage out scenarios that we've been plagued with really over the last 40, 50 years of just data in general. So we have to take an inspection where traditionally it was E. T. L. Now in the world of snowflake, it's really lt we're extracting were loading or inspecting them. We're transforming out to the business so that these routines could be done once and again give great business value back to making decisions around the data instead of spending all this long time. Always re architect ng the data pipeline to serve the business. >>Got it. Thank you. Glenda yourself of course. Snowflakes renowned for customers. Tell me all the time. It's so easy. It's so easy to spin up a data warehouse. It helps with my security. Again it simplifies everything but so you know, getting started is one thing but then adoption is also a key. So I'm interested in the role that that I owe. Tahoe plays in accelerating adoption for new customers. >>Absolutely. David. I mean as Ben said, you know every every migration to Snowflake is going to have a business case. Um uh and that is going to be uh partly about reducing spending legacy I. T. Servers, storage licenses, support all those good things um that see I want to be able to turn off entirely ultimately. And what Ayatollah does is help discover all the legacy undocumented silos that have been built up, as Glenn says on the data estate across a period of time, build intelligence around those silos and help reduce those legacy costs sooner by accelerating that that whole process. Because obviously the quicker that I. T. Um and Cdos can turn off legacy data sources the more funding and resources going to be available to them to manage the new uh Snowflake based data estate on the cloud. And so turning off the old building, the new go hand in hand to make sure those those numbers stack up the program is delivered uh and the benefits are delivered. And so what we're doing here with a Tahoe is improving the customers are y by accelerating their ability to adopt Snowflake. >>Great. And I mean we're talking a lot about data quality here but in a lot of ways that's table stakes like I said, if you don't trust the data, nobody's going to use it. And glenn, I mean I look at Snowflake and I see obviously the ease of use the simplicity you guys are nailing that the data sharing capabilities I think are really exciting because you know everybody talks about sharing data but then we talked about data as an asset, Everyone so high I to hold it. And so sharing is is something that I see as a paradigm shift and you guys are enabling that. So one of the things beyond data quality that are notable that customers are excited about that, maybe you're excited about >>David, I think you just cleared it out. It's it's this massive data sharing play part of the data cloud platform. Uh you know, just as of last year we had a little over about 100 people, 100 vendors in our data marketplace. That number today is well over 450 it is all about democratizing and sharing data in a world that is no longer held back by FTp s and C. S. V. S and then the organization having to take that data and ingested into their systems. You're a snowflake customer. want to subscribe to an S and P data sources an example, go subscribe it to it. It's in your account there was no data engineering, there was no physical lift of data and that becomes the most important thing when we talk about getting broader insights, data quality. Well, the data has already been inspected from your vendor is just available in your account. It's obviously a very simplistic thing to describe behind the scenes is what our founders have created to make it very, very easy for us to democratize not only internal with private sharing of data, but this notion of marketplace ensuring across your customers um marketplace is certainly on the type of all of my customers minds and probably some other areas that might have heard out of a recent cloud summit is the introduction of snow park and being able to do where all this data is going towards us. Am I in an ale, you know, along with our partners at Io Tahoe and R. P. A. Automation is what do we do with all this data? How do we put the algorithms and targets now? We'll be able to run in the future R and python scripts and java libraries directly inside Snowflake, which allows you to even accelerate even faster, Which people found traditionally when we started off eight years ago just as a data warehousing platform. >>Yeah, I think we're on the cusp of just a new way of thinking about data. I mean obviously simplicity is a starting point but but data by its very nature is decentralized. You talk about democratizing data. I like this idea of the global mesh. I mean it's very powerful concept and again it's early days but you know, keep part of this is is automation and trust, yussef you've worked with Snowflake and you're bringing active D. Q. To the market what our customers telling you so far? >>Well David the feedback so far has been great. Which is brilliant. So I mean firstly there's a point about speed and acceleration. Um So that's the speed to incite really. So where you have inherent data quality issues uh whether that's with data that was on premise and being brought into snowflake or on snowflake itself, we're able to show the customer results and help them understand their data quality better Within Day one which is which is a fantastic acceleration. I'm related to that. There's the cost and effort to get that insight is it's a massive productivity gain versus where you're seeing customers who've been struggling sometimes too remediate legacy data and legacy decisions that they've made over the past couple of decades, so that that cost and effort is much lower than it would otherwise have been. Um 3rdly, there's confidence and trust, so you can see Cdos and see IOS got demonstrable results that they've been able to improve data quality across a whole bunch of use cases for business users in marketing and customer services, for commercial teams, for financial teams. So there's that very quick kind of growth in confidence and credibility as the projects get moving. And then finally, I mean really all the use cases for the snowflake depend on data quality, really whether it's data science, uh and and the kind of snow park applications that Glenn has talked about, all those use cases work better when we're able to accelerate the ri for our joint customers by very quickly pushing out these data quality um insights. Um And I think one of the one of the things that the snowflake have recognized is that in order for C. I. O. Is to really adopt enterprise wide, um It's also as well as the great technology with Snowflake offers, it's about cleaning up that legacy data state, freeing up the budget for CIA to spend it on the new modern day to a state that lets them mobilise their data with snowflake. >>So you're seeing the Senate progression. We're simplifying the the the analytics from a tech perspective. You bring in Federated governance which which brings more trust. Then then you bring in the automation of the data quality piece which is fundamental. And now you can really start to, as you guys are saying, democratized and scale uh and share data. Very powerful guys. Thanks so much for coming on the program. Really appreciate your time. >>Thank you. I appreciate as well. Yeah.

>>with me or three amazing guest Panelists. One of the things that we can do today with data that we say weren't able to do maybe five years ago. >>Yes, certainly. Um, I think there's 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 data with data is bigger than ever before. There are still many companies have to decide to sample data or to throw away older data, or they don't have the right data from from external companies to put their decisions and actions in context. Now we have the technology and the platforms toe, bring all that data together, tear down silos and look 3 60 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, Milan, when I was a young pup at I D. C. I started the storage program there many, many moons ago, and and so I always pay attention to what's going on storage back in my mind. And as three people forget. Sometimes that was actually the very first cloud product announced by a W s, which really ushered in the cloud era. And that was 2006 and fundamentally changed the way we think about storing data. I wonder if you could explain how s three specifically and an object storage generally, you know, with get put really transform 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 s three you can consolidate all the different data sets that today are scattered around so many companies, different data centers. And so if you think about it, s three gives the ability to put on structure data, which are video recordings and images. It puts semi structured data, which is your CSP file, which every company has lots of. And it has also support for structure 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 S three, which launched on Pi Day in March of 2000 and six s three started off as an object store, but it has evolved into so much more than that where companies all over the world, in every industry are taking those different data sets. They're putting it in s three. 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 s three, which is secure by default and has the availability in the durability of 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 and the financial sector, and they started to use us three to put their customer care recordings, and they were just using it for storage because that obviously data set 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 that happens when you take the data sets of today and yesterday and tomorrow you put them all in one place, which is dust free 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 it's great to have you here, so so thank you. I mean, Tableau has been a game changer for organizations. I remember my first by tableau conference, passionate, uh, customers and and really bringing cloud like agility and simplicity. Thio visualization just totally change 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 in the cloud. Can you talk about how your customers are really telling stories and bringing toe life those stories with data on top of things like, that's three, which my mom was just talking about. >>Yeah, for sure. Building on what Christian male I have already said you are. Our mission tableau has always been to help people see and understand data. And you look at the amazing advances they're happening in storage and data processing and now you, when you that the data that you can see and play with this so amazing, right? Like at this point in time, yeah, 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 in the amount of sharing of data that you could bring into the picture. And now, like you said, these three things are coming together. 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 thio. Insights that were just were never possible before. >>So thank you for that. And 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 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, it evolving and maybe building on some of the things that Mark was just talking about just in terms of bringing this vision into reality? >>Certainly. Yeah, Data Cloud, for sure, is bigger and more concrete than than just the marketing value of it. The big insight behind our vision for the data cloud is that just a technology capability, just a cloud data platform is not what gets organizations to be able to be, uh, data driven to be ableto make great use of data or be um, highly capable in terms of data ability. Uh, the other element beyond technology is the access and availability off Data toe put their own data in context or enrich, based on the no literal 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 and all. The work loves the ability to do data warehousing, enquiries and speeds and feeds fit in there and data engineering, etcetera. But it's also how do we make it easier for our customers to have access to the data they need? Or they could benefit to improve the decisions for for their own organizations? Think of the analogy off 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 the data cloud. It's technology, but it's also seamless access to data >>in my life. Can >>you give us >>a sense of the scope And what kind of scale are you seeing with snowflake on on AWS? >>Well, Snowflake has always driven as Christian. That was a very high transaction rate, the S three. And in fact, when Chris and I were talking, uh, just yesterday we were talking about some of the things that have really been, um, been remarkable about the long partnership that we've had over the years. And so I'll give you an example of of how that evolution has really worked. So, as you know, as three has eyes, you know, the first a W s services launched, and we have customers who have petabytes hundreds of petabytes and exabytes of storage in history. And so, from the ground up, s three has been built for scale. And so when we have customers like Snowflake that have very high transaction rates for requests for ESRI storage, we put our customer hat on and we asked, we asked customers like 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 Christians team were walking through the demands of making requests? Two, there s three 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 need it. And so when you think about how we scale our performance, we Skillet based on a prefix and not a popular account, which other cloud providers dio, we do it in this unique way because 90% of our customer roadmap across AWS comes from customer request. And that's what Snowflake and other customers were saying is that Hey, I think about my performance based on a prefix 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 scale is, as you might imagine, s Tree 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 for second because they're taking advantage of the scale of s tree. And so you know when when when we think about scale, it's not just scale, which is the growth of your storage, which every customer needs. I D. C says that digital data is growing at 40% year over year, and so every customer needs a place to put all of those storage sets that are growing. But the way we also to 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 elasticity 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 you. Three companies here there don't often take their customer hats off. Mark, I wonder if you 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 toe platforms that made infrastructure simpler, uh, are called functions. And now it's evolving into leveraging ecosystems. You know, the power of many versus the resource is have one. So my question is, you know, how are you all collaborating and creating innovations that your customers could leverage? >>Yeah, for sure. So certainly, you know, tableau and snowflake, you know, kind of were dropped that natural partners from the beginning, right? Like putting that visualization engine on top of snowflake thio. You know, combine that that processing power on data and the ability to visualize it was obvious as you talk about the larger ecosystem. Now, of course, tableau is part of salesforce. Um and so there's a much more interesting story now to be told across the three companies. 1, 2.5, maybe a zoo. We talk about tableau and salesforce combined together of really having this full circle of salesforce. You know, with this amazing set of business APS that so much value for customers and getting the data that comes out of their salesforce applications, putting it into snowflakes so that you can combine that share, that you process it, combine it with data not just for across salesforce, but from your other APS in the 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 cumbersome nature of let's say they're on Prem data warehouses. You know the kids just unplug them because they rely on them for certain things, like reporting. But But let's say they want to raise the bar on their data and analytics. What would you advise for the next step? For them? >>I think the first part or first step to take is around. Embrace the cloud and they promise and the abilities of cloud technology. There's many studies where relative to peers, companies that embracing data are coming out ahead and outperforming their peers and with traditional technology on print 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 the best snowflake has brought to market enables organizations to focus on the data, the data model, data insights and not necessarily on managing the infrastructure. So I think that with the first recommended recommendation from from our end embraced cloud, get into a modern cloud data platform, make sure you're spending your time on data not managing infrastructure and seeing what the infrastructure lets you dio. >>Okay, this is Dave, Volunteer for the Cube. Thank you for watching. Keep it right there with mortgage rate content coming your way.

>>Hello, buddy. And welcome back to the cubes. Coverage of Snowflake Data Cloud Summer 2020. We're tracking the rise of the data cloud and fresh off the keynotes. Hear Frank's Luqman, the chairman and CEO of Snowflake, and Anita Lynch, the vice president of data governance at Disney Streaming Services. Folks. Welcome E Need a Disney plus. Awesome. You know, we signed up early. Watched all the Marvel movies. Hamilton, the new Pixar movie Soul. I haven't gotten to the man DeLorean yet. Your favorite, but I really appreciate you guys coming on. Let me start with Frank. I'm glad you're putting forth this vision around the data cloud because I never liked the term Enterprise Data Warehouse. What you're doing is is so different from the sort of that legacy world that I've known all these years. But start with why the data cloud? What problems are you trying to solve? And maybe some of the harder challenges you're seeing? >>Yeah, I know. You know, we have We've come a long way in terms of workload execution, right? In terms of scale and performance and, you know, concurrent execution. We really taking the lid off sort of the physical constraints that that have existed on these types of operations. But there's one problem, uh, that were not yet, uh solving. And that is the silo ing and bunkering of data. Essentially, you know, data is locked in applications. It's locked in data centers that's locked in cloud cloud regions incredibly hard for for data science teams to really, you know, unlocked the true value of data. When you when you can address patterns that that exists across data set. So we're perpetuate, Ah, status we've had for for ever since the beginning off computing. If we don't start Thio, crack that problem now we have that opportunity. But the notion of a data cloud is like basically saying, Look, folks, you know, we we have to start inside, lowing and unlocking the data on bring it into a place where we can access it. Uh, you know, across all these parameters and boundaries that have historically existed, it's It's very much a step level function. Customers have always looked at things won't workload at that time. That mentality really has to go. You really have to have a data cloud mentality as well as a workload orientation towards towards managing data. Yeah, >>Anita is great here in your role at Disney, and you're in your keynote and the work. You're doing the governance work, and you're you're serving a great number of stakeholders, enabling things like data sharing. You got really laser focused on trust, compliance, privacy. This idea of a data clean room is really interesting. You know, maybe you can expand on some of these initiatives here and share what you you're seeing as some of the biggest challenges to success. And, of course, the opportunities that you're unlocking. >>Sure. I mean, in my role leading data to governance, it's really critical to make sure that all of our stakeholders not only know what data is available and accessible to them, they can also understand really easily and quickly whether or not the data that they're using is for the appropriate use case. And so that's a big part of how we scale data governance. And a lot of the work that we would normally have to do manually is actually done for us through the data. Clean rooms. >>Thank you for that. I wonder if you could talk a little bit more about the role of data and how your data strategy has evolved and maybe discuss some of the things that Frank mentioned about data silos. And I mean, obviously you can relate to that having been in the data business for a while, but I wonder if you could elucidate on that. >>Sure, I mean data complexities air going to evolve over time in any traditional data architecture. Er, simply because you often have different teams at different periods in time trying thio, analyze and gather data across Ah, whole lot of different sources. And the complexity that just arises out of that is due to the different needs of specific stakeholders, their time constraints. And quite often, um, it's not always clear how much value they're going to be able to extract from the data at the outset. So what we've tried to do to help break down the silos is allow individuals to see up front how much value they're going to get from the data by knowing that it's trustworthy right away. By knowing that it's something that they can use in their specific use case right away, and by ensuring that essentially, as they're continuing to kind of scale the use cases that they're focused on. They're no longer required. Thio make multiple copies of the data, do multiple steps to reprocess the data. And that makes all the difference in the world, >>for sure. I mean, copy creep, because it be the silent killer. Frank, I followed you for a number of years. You know, your big thinker. You and I have had a lot of conversations about the near term midterm and long term. I wonder if you could talk about you know, when you're Kino. You talk about eliminating silos and connecting across data sources, which really powerful concept. But really only if people are willing and able to connect and collaborate. Where do you see that happening? Maybe What are some of the blockers there? >>Well, there's there's certainly, ah natural friction there. I still remember when we first started to talk to to Salesforce, you know, they had discovered that we were top three destination off sales first data, and they were wondering, you know why that was. And and the reason is, of course, that people take salesforce data, push it to snowflake because they wanna overlay it with what data outside of Salesforce. You know, whether it's adobe or any other marketing data set. And then they want to run very highly skilled processes, you know, on it. But the reflexes in the world of SAS is always like, no, we're an island were planning down to ourselves. Everybody needs to come with us as opposed to we We go, you know, to a different platform to run these type of processes. It's no different for the for the public club. Venter Day didn't mean they have, you know, massive moats around there. Uh, you know, their stories to, you know, really prevent data from from leaving their their orbit. Eso there is natural friction in in terms off for this to happen. But on the other hand, you know, there is an enormous need, you know, we can't deliver on on the power and potential of data unless we allow it to come together. Uh, snowflake is the platform that allows that to happen. You know, we were pleased with our relationship with Salesforce because they did appreciate you know why this was important and why this was necessary. And we think you know, other parts of the industry will gradually come around to it as well. So the the idea of a data cloud has really come, right? People are recognizing, you know, why does this matters now? It's not gonna happen overnight, And there's a step global function of very big change in mentality and orientation. You know, >>it's almost as though the SAS ification of our industries sort of repeated some of the application silos, and you build a hardened top around it. All the processes are hardened around it, and Okay, here we go. And you're really trying to break that, aren't you? Yeah, Exactly. Anita. Again, I wanna come back to this notion of governance. It's so it's so important. It's the first role in your title, and it really underscores the importance of this. Um, you know, Frank was just talking about some of the hurdles, and and this is this is a big one. I mean, we saw this in the early days of big data. Where governance was this after thought it was like, bolted on kind of wild, Wild West. I'm interested in your governance journey, and maybe you can share a little bit about what role Snowflake has played there in terms of supporting that agenda. Bond. Kind of What's next on that journey? >>Sure. Well, you know, I've I've led data teams in a numerous, uh, in numerous ways over my career. This is the first time that I've actually had the opportunity to focus on governance. And what it's done is allowed for my organization to scale much more rapidly. And that's so critically important for our overall strategy as a company. >>Well, I mean a big part of what you were talking about, at least my inference in your your talk was really that the business folks didn't have to care about, you know, wonder about they cared about it. But they're not the wonder about and and about the privacy, the concerns, etcetera. You've taken care of all that. It's sort of transparent to them. Is that >>yeah, right. That's right. Absolutely. So we focus on ensuring compliance across all the different regions where we operate. We also partner very heavily with our legal and information security teams. They're critical to ensuring, you know, that we're able Thio do this. We don't We don't do it alone. But governance includes not just, you know, the compliance and the privacy. It's also about data access, and it's also about ensuring data quality. And so all of that comes together under the governance umbrella. I also lead teams that focus on things like instrumentation, which is how we collect data. We focus on the infrastructure and making sure that we've architected for scale and all of these air really important components of our strategy. >>I got. So I have a question. Maybe each of you can answer. I I sort of see this our industry moving from, you know, products. So then the platforms and platforms even involving into ecosystems. And then there's this ecosystem of of data. You guys both talked a lot about data sharing. But maybe Frank, you could start in Anita. You can add on to Frank's answer. You're obviously both both passionate about the use of of data and trying to do so in a responsible way. That's critical, but it's also gonna have business impact. Frank, where's this passion come from? On your side. And how are you putting in tow action in your own organization? >>Well, you know, I'm really gonna date myself here, but, you know, many, many years ago, you know, I saw the first glimpse off, uh, multidimensional databases that were used for reporting. Really, On IBM mainframes on debt was extraordinarily difficult. We didn't even have the words back then. In terms of data, warehouses and business. All these terms didn't exist. People just knew that they wanted to have, um, or flexible way of reporting and being able Thio pivot data dimensionally and all these kinds of things. And I just whatever this predates, you know, Windows 3.1, which, really, you know, set off the whole sort of graphical in a way of dealing with systems which there's not a whole generations of people that don't know any different. Right? So I I've lived the pain off this problem on sort of been had a front row seat to watching this This transpire over a very long period of time. And that's that's one of the reasons um, you know why I'm here? Because I finally seen, you know, a glimpse off, you know, also as an industry fully fully just unleashing and unlocking the potential were not in a place where the technology is ahead of people's ability to harness it right, which we've We've never been there before, right? It was always like we wanted to do things that technology wouldn't let us. It's different now. I mean, people are just heads are spinning with what's now possible, which is why you see markets evolved very rapidly right now. Way we were talking earlier about how you can't take, you know, past definitions and concepts and apply them to what's going on the world. The world's changing right in front of your eyes right now. >>Sonita. Maybe you could add on to what Frank just said and share some of the business impacts and and outcomes that air notable since you're really applied your your love of data and maybe maybe touch on culture, your data culture. You know any words of wisdom for folks in the audience who might be thinking about embarking on a data cloud journey similar to what you've been on? >>Yeah, sure, I think for me. I fell in love with technology first, and then I fell in love with data, and I fell in love with data because of the impact the data can have on both the business and the technology strategy. And so it's sort of that nexus, you know, between all three and in terms of my career journey and and some of the impacts that I've seen I mean, I think with the advent of the cloud, you know before, Well, how do I say that before the cloud actually became, you know, so prevalent in such a common part of the strategy that's required? It was so difficult, you know, so painful. It took so many hours to actually be able to calculate, you know, the volumes of data that we had. Now we have that accessibility, and then on top of it with the snowflake data cloud, it's much more performance oriented from a cost perspective because you don't have multiple copies of the data, or at least you don't have toe have multiple copies of the data. And I think moving beyond some of the traditional mechanisms for for measuring business impact has has only been possible with the volumes of data that we have available to us today. And it's just it's phenomenal to see the speed at which we can operate and really, truly understand our customers, interests and their preferences, and then tailor the experiences that they really want and deserve for them. Um, it's It's been a great feeling. Thio, get to this point in time. >>That's fantastic. So, Frank, I gotta ask you if you're still in your spare time, you decided to write a book? I'm loving it. Um, I don't have a signed copy, so I'm gonna have to send it back and have you sign it. But you're I love the inside baseball. It's just awesome. Eso really appreciate that. So But why did you decide to write a book? >>Well, there were a couple of reasons. Obviously, we thought it was an interesting tale to tell for anybody you know who is interested in, You know what's going on. How did this come about, You know, where the characters behind the scenes and all this kind of stuff. But, you know, from a business standpoint, because this is such a step function, it's so non incremental. We felt like, you know, we really needed quite a bit of real estate to really lay out what the full narrative and context is on. Do you know we thought books titled The Rise of the Data Cloud. That's exactly what it ISS and We're trying to make the case for that mindset, that mentality, that strategy. Because all of us, you know, I think is an industry or were risk off persisting, perpetuating, You know, where we've been since the beginning off computing. So we're really trying to make a pretty forceful case for Look, you know, there is an enormous opportunity out there, The different choices you have to make along the way. >>Guys, we got to leave it there. Frank. I know you and I are gonna talk again. Anita. I hope we have a chance to meet face to face and and talking the Cube live someday. You're phenomenal, guest. And what a great story. Thank you both for coming on. And thank you for watching. Keep it right there. You're watching the Snowflake Data Cloud Summit on the Cube.

>>Hi, I'm Frank's Luqman CEO of Snowflake. And welcome to the Snowflake Data Cloud Summit. I'd like to take the next few minutes to introduce you to >>the data cloud on why it matters to the modern enterprise. As an industry, we have struggled to mobilize our data, meaning that has been hard to put data into service of our enterprises. We're not living in a data economy and for most data central how we run our lives, our businesses and our institutions, every single interaction we have now, whether it's in social media, e commerce or any other service, engagement generates critical data. You multiply this out with the number of actors and transactions. The volume is overwhelming, growing in leaps and bounds every day. There was a time when data operations focused mostly on running reports and populating dashboards to inform people in the enterprise of what had happened on what was going on. And we still do a ton of that. But the emphasis is shifting to data driving operations from just data informing people. There is such a thing as the time value off data meaning that the faster data becomes available, the more impactful and valuable it ISS. As data ages, it loses much of its actionable value. Digital transformation is an overused term in our industry, but the snowflake it means the end to end automation of business processes, from selling to transacting to supporting to servicing customers. Digital processes are entirely disinter mediated in terms of people. Involvement in are driven into end by data. Of course, many businesses have both physical and digital processes, and they are >>intertwined. Think of retail, logistics, delivery services and so on. So a data centric operating discipline is no longer optional data operations Air now the beating heart >>of the modern enterprise that requires a massively scalable data platform talented data engineering and data science teams to fully exploit the technology that now is becoming available. Enter snowflake. Chances are that, you know, snowflake as a >>world class execution platform for a diverse set of workloads. Among them data warehousing, data engineering, data, lakes, data, science, data applications and data sharing. Snowflake was architected from scratch for cloud scale computing. No legacy technology was carried forward in the process. Snowflake reimagined many aspects of data management data operations. The result was a cloud data platform with massive scale, blistering performance, superior economics and world class data governance. Snowflake innovated on a number of vectors that wants to deliver this breakthrough. First scale and performance. Snowflake is completely designed for cloud scale computing, both in terms of data volume, computational performance and concurrent workload. Execution snowflake features numerous distinct innovations in this category, but none stands up more than the multi cluster shared stories. Architectural Removing the control plane from the individual cluster led to a dramatically different approach that has yielded tremendous benefits. But our customers love about Snowflake is to spin up new workloads without limitation and provisioned these workloads with his little or as much compute as they see fit. No longer do they fear hidden capacity limits or encroaching on other workloads. Customers can have also scale storage and compute independent of each other, something that was not possible before second utility and elasticity. Not only can snowflake customer spin up much capacity for as long as they deem necessary. Three. Utility model in church, they only get charged for what they consumed by the machine. Second, highly granular measurement of utilization. Ah, lot of the economic impact of snowflake comes from the fact that customers no longer manage capacity. What they do now is focused on consumption. In snowflake is managing the capacity. Performance and economics now go hand in hand because faster is now also cheaper. Snowflake contracts with the public cloud vendors for capacity at considerable scale, which then translates to a good economic value at the retail level is, well, third ease of use and simplicity. Snowflake is a platform that scales from the smallest workloads to the largest data estates in the world. It is unusual in this offer industry to have a platform that controversy the entire spectrum of scale, a database technology snowflake is dramatically simple fire. To compare to previous generations, our founders were bent on making snowflake, a self managing platform that didn't require expert knowledge to run. The role of the Deba has evolved into snowflake world, more focused on data model insights and business value, not tuning and keeping the infrastructure up and running. This has expanded the marketplace to nearly any scale. No job too small or too large. Fourth, multi cloud and Cross Cloud or snowflake was first available on AWS. It now also runs very successfully on mark yourself. Azure and Google Cloud Snowflake is a cloud agnostic platform, meaning that it doesn't know what it's running on. Snowflake completely abstracts the underlying cloud platform. The user doesn't need to see or touch it directly and also does not receive a separate bill from the cloud vendor for capacity consumed by snowflake. Being multi cloud capable customers have a choice and also the flexibility to change over time snowflakes. Relationships with Amazon and Microsoft also allow customers to transact through their marketplaces and burned down their cloud commit with their snowflakes. Spend Snowflake is also capable of replicating across cloud regions and cloud platforms. It's not unusual to see >>the same snowflake data on more than one public cloud at the time. Also, for disaster recovery purposes, it is desirable to have access to snowflake on a completely different public cloud >>platform. Fifth, data Security and privacy, security and privacy are commonly grouped under the moniker of data governance. As a highly managed cloud data platform, snowflake designed and deploys a comprehensive and coherent security model. While privacy requirements are newer and still emerging in many areas, snowflake as a platform is evolving to help customers steer clear from costly violations. Our data sharing model has already enabled many customers to exchange data without surrendering custody of data. Key privacy concerns There's no doubt that the strong governance and compliance framework is critical to extracting you analytical value of data directly following the session. Police Stay tuned to hear from Anita Lynch at Disney Streaming services about how >>to date a cloud enables data governance at Disney. The world beat a >>path to our door snowflake unleashed to move from UN promised data centers to the public cloud platforms, notably AWS, Azure and Google Cloud. Snowflake now has thousands of enterprise customers averaging over 500 million queries >>today across all customer accounts, and it's one of the fastest growing enterprise software companies in a generation. Our recent listing on the New York Stock Exchange was built is the largest software AIPO in history. But the data cloth conversation is bigger. There is another frontier workload. Execution is a huge part of it, but it's not the entire story. There is another elephant in the room, and that is that The world's data is incredibly fragmented in siloed, across clouds of old sorts and data centers all over the place. Basically, data lives in a million places, and it's incredibly hard to analyze data across the silos. Most intelligence analytics and learning models deploy on single data sets because it has been next to impossible to analyze data across sources. Until now, Snowflake Data Cloud is a data platform shared by all snowflake users. If you are on snowflake, you are already plugged into it. It's like being part of a Global Data Federation data orbit, if you will, where all other data can now be part of your scope. Historically, technology limitations led us to build systems and services that siloed the data behind systems, software and network perimeters. To analyze data across silos, we resorted to building special purpose data warehouses force fed by multiple data sources empowered by expensive proprietary hardware. The scale limitations lead to even more silos. The onslaught of the public cloud opened the gateway to unleashing the world's data for access for sharing a monetization. But it didn't happen. Pretty soon they were new silos, different public clouds, regions within the and a huge collection of SAS applications hoarding their data all in their own formats on the East NC ations whole industries exist just to move data from A to B customer behavior precipitated the silo ing of data with what we call a war clothes at a time mentality. Customers focused on the applications in isolation of one another and then deploy data platforms for their workload characteristics and not much else, thereby throwing up new rules between data. Pretty soon, we don't just have our old Silas, but new wants to content with as well. Meanwhile, the promise of data science remains elusive. With all this silo ing and bunkering of data workload performance is necessary but not sufficient to enable the promise of data science. We must think about unfettered data access with ease, zero agency and zero friction. There's no doubt that the needs of data science and data engineering should be leading, not an afterthought. And those needs air centered on accessing and analyzing data across sources. It is now more the norm than the exception that data patterns transcend data sources. Data silos have no meaning to data science. They are just remnants of legacy computing. Architectures doesn't make sense to evaluate strictly on the basis of existing workloads. The world changes, and it changes quickly. So how does the data cloud enabled unfettered data access? It's not just a function of being in the public cloud. Public Cloud is an enabler, no doubt about it. But it introduces new silos recommendation by cloud, platform by cloud region by Data Lake and by data format, it once again triggered technical grandstands and a lot of programming to bring a single analytical perspective to a diversity of data. Data was not analytics ready, not optimized for performance or efficiency and clearly lacking on data governance. Snowflake, address these limitations, thereby combining great execution with great data >>access. But, snowflake, we can have the best of both. So how does it all work when you join Snowflake and have your snowflake account? You don't just >>avail yourself of unlimited stories. And compute resource is along with a world class execution platform. You also plug into the snowflake data cloud, meaning that old snowflake accounts across clouds, regions and geography are part of a single snowflake data universe. That is the data clouds. It is based on our global data sharing architectures. Any snowflake data can be exposed and access by any other snowflake user. It's seamless and frictionless data is generally not copied. Her moves but access in place, subject to the same snowflake governance model. Accessing the data cloth can be a tactical one on one sharing relationship. For example, imagine how retailer would share data with a consumer back. It's good company, but then it easily proliferate from 1 to 1. Too many too many. The data cloud has become a beehive of data supply and demand. It has attracted hundreds of professional data listings to the Snowflake Data Marketplace, which fuels the data cloud with a rich supply of options. For example, our partner Star Schema, listed a very detailed covert 19 incident and fatality data set on the Snowflake Data Marketplace. It became an instant hit with snowflake customers. Scar schema is not raw data. It is also platform optimize, meaning that it was analytics ready for all snowflake accounts. Snowflake users were accessing, joining and overlaying this new data within a short time of it becoming available. That is the power of platform in financial services. It's common to see snowflake users access data from snowflake marketplace listings like fax set and Standard and Poor's on, then messed it up against for example. Salesforce data There are now over 100 suppliers of data listings on the snowflake marketplace That is, in addition to thousands of enterprise and institutional snowflake users with their own data sets. Best part of the snowflake data cloud is this. You don't need to do or buy anything different. If your own snowflake you're already plugged into the data clouds. A whole world data access options awaits you on data silos. Become a thing of the past, enjoy today's presentations. By the end of it, you should have a better sense in a bigger context for your choices of data platforms. Thank you for joining us.

(upbeat music) >> Hi everyone, thank you for joining us at the Data Cloud Summit. The last couple of months have been an exciting time at Snowflake. And yet, what's even more compelling to all of us at Snowflake is what's ahead. Today I have the opportunity to share new product developments that will extend the reach and impact of our Data Cloud and improve the experience of Snowflake users. Our product strategy is focused on four major areas. First, Data Cloud content. In the Data Cloud silos are eliminated and our vision is to bring the world's data within reach of every organization. You'll hear about new data sets and data services available in our data marketplace and see how previous barriers to sourcing and unifying data are eliminated. Second, extensible data pipelines. As you gain frictionless access to a broader set of data through the Data Cloud, Snowflakes platform brings additional capabilities and extensibility to your data pipelines, simplifying data ingestion, and transformation. Third, data governance. The Data Cloud eliminates silos and breaks down barriers and in a world where data collaboration is the norm, the importance of data governance is ratified and elevated. We'll share new advancements to support how the world's most demanding organizations mobilize your data while maintaining high standards of compliance and governance. Finally, our fourth area focuses on platform performance and capabilities. We remain laser focused on continuing to lead with the most performant and capable data platform. We have some exciting news to share about the core engine of Snowflake. As always, we love showing you Snowflake in action, and we prepared some demos for you. Also, we'll keep coming back to the fact that one of the characteristics of Snowflake that we're proud as staff is that we offer a single platform from which you can operate all of your data workloads, across clouds and across regions, which workloads you may ask, specifically, data warehousing, data lake, data science, data engineering, data applications, and data sharing. Snowflake makes it possible to mobilize all your data in service of your business without the cost, complexity and overhead of managing multiple systems, tools and vendors. Let's dive in. As you heard from Frank, the Data Cloud offers a unique capability to connect organizations and create collaboration and innovation across industries fueled by data. The Snowflake data marketplace is the gateway to the Data Cloud, providing visibility for organizations to browse and discover data that can help them make better decisions. For data providers on the marketplace, there is a new opportunity to reach new customers, create new revenue streams, and radically decrease the effort and time to data delivery. Our marketplace dramatically reduces the friction of sharing and collaborating with data opening up new possibilities to all participants in the Data Cloud. We introduced the Snowflake data marketplace in 2019. And it is now home to over 100 data providers, with half of them having joined the marketplace in the last four months. Since our most recent product announcements in June, we have continued broadening the availability of the data marketplace, across regions and across clouds. Our data marketplace provides the opportunity for data providers to reach consumers across cloud and regional boundaries. A critical aspect of the Data Cloud is that we envisioned organizations collaborating not just in terms of data, but also data powered applications and services. Think of instances where a provider doesn't want to open access to the entirety of a data set, but wants to provide access to business logic that has access and leverages such data set. That is what we call data services. And we want Snowflake to be the platform of choice for developing discovering and consuming such rich building blocks. To see How the data marketplace comes to live, and in particular one of these data services, let's jump into a demo. For all of our demos today, we're going to put ourselves in the shoes of a fictional global insurance company. We've called it Insureco. Insurance is a data intensive and highly regulated industry. Having the right access control and insight from data is core to every insurance company's success. I'm going to turn it over to Prasanna to show how the Snowflake data marketplace can solve a data discoverability and access problem. >> Let's look at how Insureco can leverage data and data services from the Snowflake data marketplace and use it in conjunction with its own data in the Data Cloud to do three things, better detect fraudulent claims, arm its agents with the right information, and benchmark business health against competition. Let's start with detecting fraudulent claims. I'm an analyst in the Claims Department. I have auto claims data in my account. I can see there are 2000 auto claims, many of these submitted by auto body shops. I need to determine if they are valid and legitimate. In particular, could some of these be insurance fraud? By going to the Snowflake data marketplace where numerous data providers and data service providers can list their offerings, I find the quantifying data service. It uses a combination of external data sources and predictive risk typology models to inform the risk level of an organization. Quantifying external sources include sanctions and blacklists, negative news, social media, and real time search engine results. That's a wealth of data and models built on that data which we don't have internally. So I'd like to use Quantifind to determine a fraud risk score for each auto body shop that has submitted a claim. First, the Snowflake data marketplace made it really easy for me to discover a data service like this. Without the data marketplace, finding such a service would be a lengthy ad hoc process of doing web searches and asking around. Second, once I find Quantifind, I can use Quantifind service against my own data in three simple steps using data sharing. I create a table with the names and addresses of auto body shops that have submitted claims. I then share the table with Quantifind to start the risk assessment. Quantifind does the risk scoring and shares the data back with me. Quantifind uses external functions which we introduced in June to get results from their risk prediction models. Without Snowflake data sharing, we would have had to contact Quantifind to understand what format they wanted the data in, then extract this data into a file, FTP the file to Quantifind, wait for the results, then ingest the results back into our systems for them to be usable. Or I would have had to write code to call Quantifinds API. All of that would have taken days. In contrast, with data sharing, I can set this up in minutes. What's more, now that I have set this up, as new claims are added in the future, they will automatically leverage Quantifind's data service. I view the scores returned by Quantifind and see the two entities in my claims data have a high score for insurance fraud risk. I open up the link returned by Quantifind to read more, and find that this organization has been involved in an insurance crime ring. Looks like that is a claim that we won't be approving. Using the Quantifind data service through the Snowflake data marketplace gives me access to a risk scoring capability that we don't have in house without having to call custom APIs. For a provider like Quantifind this drives new leads and monetization opportunities. Now that I have identified potentially fraudulent claims, let's move on to the second part. I would like to share this fraud risk information with the agents who sold the corresponding policies. To do this, I need two things. First, I need to find the agents who sold these policies. Then I need to share with these agents the fraud risk information that we got from Quantifind. But I want to share it such that each agent only sees the fraud risk information corresponding to claims for policies that they wrote. To find agents who sold these policies, I need to look up our Salesforce data. I can find this easily within Insureco's internal data exchange. I see there's a listing with Salesforce data. Our sales Ops team has published this listing so I know it's our officially blessed data set, and I can immediately access it from my Snowflake account without copying any data or having to set up ETL. I can now join Salesforce data with my claims to identify the agents for the policies that were flagged to have fraudulent claims. I also have the Snowflake account information for each agent. Next, I create a secure view that joins on an entitlements table, such that each agent can only see the rows corresponding to policies that they have sold. I then share this directly with the agents. This share contains the secure view that I created with the names of the auto body shops, and the fraud risk identified by Quantifind. Finally, let's move on to the third and last part. Now that I have detected potentially fraudulent claims, I'm going to move on to building a dashboard that our executives have been asking for. They want to see how Insureco compares against other auto insurance companies on key metrics, like total claims paid out for the auto insurance line of business nationwide. I go to the Snowflake data marketplace and find SNL U.S. Insurance Statutory Data from SNP. This data is included with Insureco's existing subscription with SMP so when I request access to it, SMP can immediately share this data with me through Snowflake data sharing. I create a virtual database from the share, and I'm ready to query this data, no ETL needed. And since this is a virtual database, pointing to the original data in SNP Snowflake account, I have access to the latest data as it arrives in SNPs account. I see that the SNL U.S. Insurance Statutory Data from SNP has data on assets, premiums earned and claims paid out by each us insurance company in 2019. This data is broken up by line of business and geography and in many cases goes beyond the data that would be available from public financial filings. This is exactly the data I need. I identify a subset of comparable insurance companies whose net total assets are within 20% of Insureco's, and whose lines of business are similar to ours. I can now create a Snow site dashboard that compares Insureco against similar insurance companies on key metrics, like net earned premiums, and net claims paid out in 2019 for auto insurance. I can see that while we are below median our net earned premiums, we are doing better than our competition on total claims paid out in 2019, which could be a reflection of our improved claims handling and fraud detection. That's a good insight that I can share with our executives. In summary, the Data Cloud enabled me to do three key things. First, seamlessly fine data and data services that I need to do my job, be it an external data service like Quantifind and external data set from SNP or internal data from Insureco's data exchange. Second, get immediate live access to this data. And third, control and manage collaboration around this data. With Snowflake, I can mobilize data and data services across my business ecosystem in just minutes. >> Thank you Prasanna. Now I want to turn our focus to extensible data pipelines. We believe there are two different and important ways of making Snowflakes platform highly extensible. First, by enabling teams to leverage services or business logic that live outside of Snowflake interacting with data within Snowflake. We do this through a feature called external functions, a mechanism to conveniently bring data to where the computation is. We announced this feature for calling regional endpoints via AWS gateway in June, and it's currently available in public preview. We are also now in public preview supporting Azure API management and will soon support Google API gateway and AWS private endpoints. The second extensibility mechanism does the converse. It brings the computation to Snowflake to run closer to the data. We will do this by enabling the creation of functions and procedures in SQL, Java, Scala or Python ultimately providing choice based on the programming language preference for you or your organization. You will see Java, Scala and Python available through private and public previews in the future. The possibilities enabled by these extensibility features are broad and powerful. However, our commitment to being a great platform for data engineers, data scientists and developers goes far beyond programming language. Today, I am delighted to announce Snowpark a family of libraries that will bring a new experience to programming data in Snowflake. Snowpark enables you to write code directly against Snowflake in a way that is deeply integrated into the languages I mentioned earlier, using familiar concepts like DataFrames. But the most important aspect of Snowpark is that it has been designed and optimized to leverage the Snowflake engine with its main characteristics and benefits, performance, reliability, and scalability with near zero maintenance. Think of the power of a declarative SQL statements available through a well known API in Scala, Java or Python, all these against data governed in your core data platform. We believe Snowpark will be transformative for data programmability. I'd like to introduce Sri to showcase how our fictitious insurance company Insureco will be able to take advantage of the Snowpark API for data science workloads. >> Thanks Christian, hi, everyone? I'm Sri Chintala, a product manager at Snowflake focused on extensible data pipelines. And today, I'm very excited to show you a preview of Snowpark. In our first demo, we saw how Insureco could identify potentially fraudulent claims. Now, for all the valid claims InsureCo wants to ensure they're providing excellent customer service. To do that, they put in place a system to transcribe all of their customer calls, so they can look for patterns. A simple thing they'd like to do is detect the sentiment of each call so they can tell which calls were good and which were problematic. They can then better train their claim agents for challenging calls. Let's take a quick look at the work they've done so far. InsureCo's data science team use Snowflakes external functions to quickly and easily train a machine learning model in H2O AI. Snowflake has direct integrations with H2O and many other data science providers giving Insureco the flexibility to use a wide variety of data science libraries frameworks or tools to train their model. Now that the team has a custom trained sentiment model tailored to their specific claims data, let's see how a data engineer at Insureco can use Snowpark to build a data pipeline that scores customer call logs using the model hosted right inside of Snowflake. As you can see, we have the transcribed call logs stored in the customer call logs table inside Snowflake. Now, as a data engineer trained in Scala, and used to working with systems like Spark and Pandas, I want to use familiar programming concepts to build my pipeline. Snowpark solves for this by letting me use popular programming languages like Java or Scala. It also provides familiar concepts in APIs, such as the DataFrame abstraction, optimized to leverage and run natively on the Snowflake engine. So here I am in my ID, where I've written a simple scalar program using the Snowpark libraries. The first step in using the Snowpark API is establishing a session with Snowflake. I use the session builder object and specify the required details to connect. Now, I can create a DataFrame for the data in the transcripts column of the customer call logs table. As you can see, the Snowpark API provides native language constructs for data manipulation. Here, I use the Select method provided by the API to specify the column names to return rather than writing select transcripts as a string. By using the native language constructs provided by the API, I benefit from features like IntelliSense and type checking. Here you can see some of the other common methods that the DataFrame class offers like filters like join and others. Next, I define a get sentiment user defined function that will return a sentiment score for an input string by using our pre trained H2O model. From the UDF, we call the score method that initializes and runs the sentiment model. I've built this helper into a Java file, which along with the model object and license are added as dependencies that Snowpark will send to Snowflake for execution. As a developer, this is all programming that I'm familiar with. We can now call our get sentiment function on the transcripts column of the DataFrame and right back the results of the score transcripts to a new target table. Let's run this code and switch over to Snowflake to see the score data and also all the work that Snowpark has done for us on the back end. If I do a select star from scored logs, we can see the sentiment score of each call right alongside the transcript. With Snowpark all the logic in my program is pushed down into Snowflake. I can see in the query history that Snowpark has created a temporary Java function to host the pre trained H20 model, and that the model is running right in my Snowflake warehouse. Snowpark has allowed us to do something completely new in Snowflake. Let's recap what we saw. With Snowpark, Insureco was able to use their preferred programming language, Scala and use the familiar DataFrame constructs to score data using a machine learning model. With support for Java UDFs, they were able to run a train model natively within Snowflake. And finally, we saw how Snowpark executed computationally intensive data science workloads right within Snowflake. This simplifies Insureco's data pipeline architecture, as it reduces the number of additional systems they have to manage. We hope that extensibility with Scala, Java and Snowpark will enable our users to work with Snowflake in their preferred way while keeping the architecture simple. We are very excited to see how you use Snowpark to extend your data pipelines. Thank you for watching and with that back to you, Christian. >> Thank you Sri. You saw how Sri could utilize Snowpark to efficiently perform advanced sentiment analysis. But of course, if this use case was important to your business, you don't want to fully automate this pipeline and analysis. Imagine being able to do all of the following in Snowflake, your pipeline could start far upstream of what you saw in the demo. By storing your actual customer care call recordings in Snowflake, you may notice that this is new for Snowflake. We'll come back to the idea of storing unstructured data in Snowflake at the end of my talk today. Once you have the data in Snowflake, you can use our streams and past capabilities to call an external function to transcribe these files. To simplify this flow even further, we plan to introduce a serverless execution model for tasks where Snowflake can automatically size and manage resources for you. After this step, you can use the same serverless task to execute sentiment scoring of your transcript as shown in the demo with incremental processing as each transcript is created. Finally, you can surface the sentiment score either via snow side, or through any tool you use to share insights throughout your organization. In this example, you see data being transformed from a raw asset into a higher level of information that can drive business action, all fully automated all in Snowflake. Turning back to Insureco, you know how important data governance is for any major enterprise but particularly for one in this industry. Insurance companies manage highly sensitive data about their customers, and have some of the strictest requirements for storing and tracking such data, as well as managing and governing it. At Snowflake, we think about governance as the ability to know your data, manage your data and collaborate with confidence. As you saw in our first demo, the Data Cloud enables seamless collaboration, control and access to data via the Snowflake data marketplace. And companies may set up their own data exchanges to create similar collaboration and control across their ecosystems. In future releases, we expect to deliver enhancements that create more visibility into who has access to what data and provide usage information of that data. Today, we are announcing a new capability to help Snowflake users better know and organize your data. This is our new tagging framework. Tagging in Snowflake will allow user defined metadata to be attached to a variety of objects. We built a broad and robust framework with powerful implications. Think of the ability to annotate warehouses with cost center information for tracking or think of annotating tables and columns with sensitivity classifications. Our tagging capability will enable the creation of companies specific business annotations for objects in Snowflakes platform. Another key aspect of data governance in Snowflake is our policy based framework where you specify what you want to be true about your data, and Snowflake enforces those policies. We announced one such policy earlier this year, our dynamic data masking capability, which is now available in public preview. Today, we are announcing a great complimentary a policy to achieve row level security to see how role level security can enhance InsureCo's ability to govern and secure data. I'll hand it over to Artin for a demo. >> Hello, I'm Martin Avanes, Director of Product Management for Snowflake. As Christian has already mentioned, the rise of the Data Cloud greatly accelerates the ability to access and share diverse data leading to greater data collaboration across teams and organizations. Controlling data access with ease and ensuring compliance at the same time is top of mind for users. Today, I'm thrilled to announce our new row access policies that will allow users to define various rules for accessing data in the Data Cloud. Let's check back in with Insureco to see some of these in action and highlight how those work with other existing policies one can define in Snowflake. Because Insureco is a multinational company, it has to take extra measures to ensure data across geographic boundaries is protected to meet a wide range of compliance requirements. The Insureco team has been asked to segment what data sales team members have access to based on where they are regionally. In order to make this possible, they will use Snowflakes row access policies to implement row level security. We are going to apply policies for three Insureco's sales team members with different roles. Alice, an executive must be able to view sales data from both North America and Europe. Alex in North America sales manager will be limited to access sales data from North America only. And Jordan, a Europe sales manager will be limited to access sales data from Europe only. As a first step, the security administrator needs to create a lookup table that will be used to determine which data is accessible based on each role. As you can see, the lookup table has the row and their associated region, both of which will be used to apply policies that we will now create. Row access policies are implemented using standard SQL syntax to make it easy for administrators to create policies like the one our administrators looking to implement. And similar to masking policies, row access policies are leveraging our flexible and expressive policy language. In this demo, our admin users to create a row access policy that uses the row and region of a user to determine what row level data they have access to when queries are executed. When users queries are executed against the table protected by such a row access policy, Snowflakes query engine will dynamically generate and apply the corresponding predicate to filter out rows the user is not supposed to see. With the policy now created, let's log in as our Sales Users and see if it worked. Recall that as a sales executive, Alice should have the ability to see all rows from North America and Europe. Sure enough, when she runs her query, she can see all rows so we know the policy is working for her. You may also have noticed that some columns are showing masked data. That's because our administrator's also using our previously announced data masking capabilities to protect these data attributes for everyone in sales. When we look at our other users, we should notice that the same columns are also masked for them. As you see, you can easily combine masking and row access policies on the same data sets. Now let's look at Alex, our North American sales manager. Alex runs to st Korea's Alice, row access policies leverage the lookup table to dynamically generate the corresponding predicates for this query. The result is we see that only the data for North America is visible. Notice too that the same columns are still masked. Finally, let's try Jordan, our European sales manager. Jordan runs the query and the result is only the data for Europe with the same columns also masked. And you reintroduced masking policies, today you saw row access policies in action. And similar to our masking policies, row access policies in Snowflake will be accepted Hands of capability integrated seamlessly across all of Snowflake everywhere you expect it to work it does. If you're accessing data stored in external tables, semi structured JSON data, or building data pipelines via streams or plan to leverage Snowflakes data sharing functionality, you will be able to implement complex row access policies for all these diverse use cases and workloads within Snowflake. And with Snowflakes unique replication feature, you can instantly apply these new policies consistently to all of your Snowflake accounts, ensuring governance across regions and even across different clouds. In the future, we plan to demonstrate how to combine our new tagging capabilities with Snowflakes policies, allowing advanced audit and enforcing those policies with ease. And with that, let's pass it back over to Christian. >> Thank you Artin. We look forward to making this new tagging and row level security capabilities available in private preview in the coming months. One last note on the broad area of data governance. A big aspect of the Data Cloud is the mobilization of data to be used across organizations. At the same time, privacy is an important consideration to ensure the protection of sensitive, personal or potentially identifying information. We're working on a set of product capabilities to simplify compliance with privacy related regulatory requirements, and simplify the process of collaborating with data while preserving privacy. Earlier this year, Snowflake acquired a company called Crypto Numerix to accelerate our efforts on this front, including the identification and anonymization of sensitive data. We look forward to sharing more details in the future. We've just shown you three demos of new and exciting ways to use Snowflake. However, I want to also remind you that our commitment to the core platform has never been greater. As you move workloads on to Snowflake, we know you expect exceptional price performance and continued delivery of new capabilities that benefit every workload. On price performance, we continue to drive performance improvements throughout the platform. Let me give you an example comparing an identical set of customers submitted queries that ran both in August of 2019, and August of 2020. If I look at the set of queries that took more than one second to compile 72% of those improved by at least 50%. When we make these improvements, execution time goes down. And by implication, the required compute time is also reduced. Based on our pricing model to charge for what you use, performance improvements not only deliver faster insights, but also translate into cost savings for you. In addition, we have two new major announcements on performance to share today. First, we announced our search optimization service during our June event. This service currently in public preview can be enabled on a table by table basis, and is able to dramatically accelerate lookup queries on any column, particularly those not used as clustering columns. We initially support equality comparisons only, and today we're announcing expanded support for searches in values, such as pattern matching within strings. This will unlock a number of additional use cases such as analytics on logs data for performance or security purposes. This expanded support is currently being validated by a few customers in private preview, and will be broadly available in the future. Second, I'd like to introduce a new service that will be in private preview in a future release. The query acceleration service. This new feature will automatically identify and scale out parts of a query that could benefit from additional resources and parallelization. This means that you will be able to realize dramatic improvements in performance. This is especially impactful for data science and other scan intensive workloads. Using this feature is pretty simple. You define a maximum amount of additional resources that can be recruited by a warehouse for acceleration, and the service decides when it would be beneficial to use them. Given enough resources, a query over a massive data set can see orders of magnitude performance improvement compared to the same query without acceleration enabled. In our own usage of Snowflake, we saw a common query go 15 times faster without changing the warehouse size. All of these performance enhancements are extremely exciting, and you will see continued improvements in the future. We love to innovate and continuously raise the bar on what's possible. More important, we love seeing our customers adopt and benefit from our new capabilities. In June, we announced a number of previews, and we continue to roll those features out and see tremendous adoption, even before reaching general availability. Two have those announcements were the introduction of our geospatial support and policies for dynamic data masking. Both of these features are currently in use by hundreds of customers. The number of tables using our new geography data type recently crossed the hundred thousand mark, and the number of columns with masking policies also recently crossed the same hundred thousand mark. This momentum and level of adoption since our announcements in June is phenomenal. I have one last announcement to highlight today. In 2014, Snowflake transformed the world of data management and analytics by providing a single platform with first class support for both structured and semi structured data. Today, we are announcing that Snowflake will be adding support for unstructured data on that same platform. Think of the abilities of Snowflake used to store access and share files. As an example, would you like to leverage the power of SQL to reason through a set of image files. We have a few customers as early adopters and we'll provide additional details in the future. With this, you will be able to leverage Snowflake to mobilize all your data in the Data Cloud. Our customers rely on Snowflake as the data platform for every part of their business. However, the vision and potential of Snowflake is actually much bigger than the four walls of any organization. Snowflake has created a Data Cloud a data connected network with a vision where any Snowflake customer can leverage and mobilize the world's data. Whether it's data sets, or data services from traditional data providers for SaaS vendors, our marketplace creates opportunities for you and raises the bar in terms of what is possible. As examples, you can unify data across your supply chain to accelerate your time and quality to market. You can build entirely new revenue streams, or collaborate with a consortium on data for good. The possibilities are endless. Every company has the opportunity to gain richer insights, build greater products and deliver better services by reaching beyond the data that he owns. Our vision is to enable every company to leverage the world's data through seamless and governing access. Snowflake is your window into this data network into this broader opportunity. Welcome to the Data Cloud. (upbeat music)

>>Hey, Sue, my great to see you. Welcome to the Data Cloud Summit. Super excited to have you welcome. >>Hey, Chris. Very nice to be there. Thank you for having me >>tell us a little bit about alien spending lakhs. Tell us a little bit about yourself and your role. Italy and Benelux >>aliens, Benelux zits. Basically the aliens business in the region. Belgium, Netherlands and Luxembourg. We serve the needs of the customer here by securing the future. We actually do both PNC asses. We call it properly and casualities in life investment management and health. We do retail, uh, small and medium enterprises. I am a regional chief Data and Biggs, officer for aliens. Benelux. I report directly to the regional CEO my job here in alliance to basically drive the data and analytics agenda for aliens. Vanilla, >>cinnamon. I understand you're getting your PhD in data science. It would be great for the audience to learn a little bit more about what's driving you to do that. And kind of what? What's most interesting to you about data science? A I m l >>the reason why I started to do this because there's so much relevance. Push that which is basically driving the agenda. We need to really look at the theoretical part off it as well. To kind of concrete eyes, Andi toe bring in a certain develop dependency, consistency, timelessness, etcetera. And obviously that which we're doing is very innovative. Here, Italians, monologues driven again by relevance and which is very good for the business. But the timelessness needs to also be the sustainability the scalability needs also has to be given to this particular relevance driven topic so that we don't just create superficial impact. But we create a long lasting and everlasting impact in our competitive intelligence intelligence that building against monologues. >>That's awesome. I mean, thanks for sharing that. So So I think. Cinnamon. When when you and I met back in March 1 of the big things that you were you were considering is, you know, uh, signing up with snowflake and becoming a customer. But part of that journey was convincing Ali on spent lakhs to move to the cloud in your journey. So kind of it would be great for you to explain to the audience. You know what that journey has been like. Was it hard to convince your organization moved to the cloud, What hurdles might you have seen in your journey to the cloud? >>It was not very different to any kind of a change on the kind of effort that you need to put in a change for a normal status go set up that which exists today. So, of course, in any kind of a change, your status could change or challenge that which you bring in. There is a considerable, uh, effort that you need to put in. And it's also your responsibility to basically do that because if you don't have that energy or if you don't have that commitment and you are not able to sustain the energy of the commitment that you show in the new agenda that you bring in, then probably you're not gonna be there to see the change through. Of course, it waas difficult, obviously, because, uh, there is already existing status. Go. And there we have a lot of benefits by moving to cloud, and obviously the benefits seems very interesting. But there is skepticism, and we s alliance is from a group perspective, and Benelux perspective is full of very, very clear on a point that we cannot take advantage off the data that which we have. We want to ensure that privacy is by design. Security is by design. And we give utmost care to our customer data. Um, mhm. And all of this basically brings in tow the concept off. Okay, what is it about moving to the cloud and where are we getting exposed? Where should we basically put together? A security by design privacy with some kind of concepts before we do it and etc. Are you ready? Can be ensured that we still keep the customers data A to a place where we basically can't bust. Well, those are the things that which had to be explained. A certain level of sensitization had to be created. A certain level of awareness. Uh, then the consideration part. Yeah, all of this basically takes its own cycle. >>Awesome. Thanks for sharing that. So we're super excited to call Ali on spending lakhs of customer. Now, what are you excited about with snowflake? And I know that you're you're looking at snowflake. Is this kind of data cloud and data cloud transformation project. Tell us a little bit more about, you know, What? What excites you about Snowflake? How you think you might use stuff like, um, in this kind of transformation of Ali on spending lakhs? >>I know that snowflake is brought to us as a product by you guys, but we look at snowflake is a kind off message. We are breaking down the silos. Literally. Onda. We look at snowflake as a kind often agent to do this. Uh, this is something that which is very important to understand that whatever you do with the organizational level, you still end up with a situation where you kind of reinforce the silos. But, snowflake, we have an opportunity here to even challenge that on break the data silos. Once the data silos is broke, you basically improve the find ability of data. You basically improve the understand ability of the data accessibility of the data interpret ability on everyone sees pretty much the same truth. And that's how the silos disappear. We're very, very excited about the journey that which, which we have in front of us because we're pretty new in it. In the sense that we are going toe haven't very exciting journey as we progress, we are also looking forward to see how Snowflakes road map is going to take us to the point off arrival, as I would call it in our own data revenge in >>today we live in this kind of multi cloud, multi cloud application world. What are some of the concerns you have as you transition from, you know, having stuff in a data center to using multiple clouds to using multiple tools? You know, what's what's some of the challenges you for? See having? What are the things that you're looking for from Snowflake to help you? Um, in that journey, >>there is always a reason why we basically make a change. And the reason is always mostly towards more efficiency, effectiveness and so on and so forth, right? I mean, basically, we have Catholics challenges on this. Catholic challenges can also be addressed with this move to the cloud, except but what We should be careful and should avoid us that the cost that which we have in terms of Camp X is just does not get re attributed into another cost called articulation, cost or arbitration cost. So having a multi cloud is definitely a challenge until you have a kind off orchestrator because we are doing a business here and we don't want to care about pretty much the orchestration. The are part off it on. This needs to be taken taken into account because there is this application cloud and there is this infrastructure cloud. You can have as many clothes as you want, whatever function that which is is supporting you. But that has to be encapsulate, er abstracted away from us so that we're able to focus on the business that we're here to do. And these are certain constraints that I really had as I was thinking about multi cloud or hybrid cloud and I was even focusing on how am I going toe orchestrate all of these different things Eso that you know, you kind of feel abstracted from those things. So well, those are the constraints that I think we still have toe conquer as we progress. I think we are evolving very fastly in that area. And you are the experts in that area, and you know exactly what you're doing there. But for me, what is very important is that uh, yeah, it gets abstracted away from us, and we just get the scalability that we need the elasticity that which we need the security by design the privacy by design on. Then I think this is perfect for us. >>Awesome. So? So I think a lot of customers that are listening to this are about to jump on the same journey that you're you're embarking on. What, is there a specific use case that you decided to kind of go? You know, you know, all in on Snowflake. What was the what was the kind of the initial driver for you to say? Hey, then the business driver on you saying, Hey, I'm gonna use this use case to drive transformation within within Ali and spend lakhs, >>I think virtualization, uh, it's the keep point that comes up the top of my head the moment you speak about what even did drive me to think about snowflake as an option, right? Why virtualization? Because obviously I don't want to move huge amount of data from left, right and center, because you know that when you start optimizing such a kind of an architectural, you end up creating pockets silos, which is totally against what we want to do. We want to break silos. But in the end, just because off the infrastructure needs in the computational needs, etcetera on the response rates and stuff like that, you start to create silos, bring with virtualization and especially with the performance that with Snowflake and provide us in that area. Now it seems like a possibility that we will be able to do that. I mean, it was not something that we just thought about, let's say, a few years back, but now it's definitely possible virtualization. It's one of the key points, but when you talk in the terms of use cases, we Italians monologues do not look at use cases. Actually, we look at business initiatives, so the reason why we don't look at it as use cases is because use cases used, kind off a start and stop. But we were not in the game. Off use cases were in the game off delivering future, that which our customer really wants to be secured. That's what the business we are in and that there are no use cases. There are initiatives there that which matches to the agenda for our customer. So when you start thinking about like that one of the most important things that snowflake offices is an opportunity is to obviously create on environment, so to say, on elastic scalable, uh, situation with the computer that which we need that which basically matches one on one with the agenda for our customer. So what I mean is the data warehousing on the cloud through data warehousing on the cloud is what waas on off our driving thought processes for We did not want to go and say that we will just do, uh, do Data Lake. We will just do data hub way don't belong toe religion. So to say, we basically are very opportunistic in this approach where we say we will have a data lake. We will have a data warehouse. We will have a data hub on. We will integrate it, you know, very a semantic way that which will match to the agenda of the customer and treat the customer as a sort of centric point. >>That's great. I appreciate that. So So, um, Suderman, thank you so much for for, you know, joining us today. Um, And again, thank you for your partnership. We snowflake is super excited. I'm I'm super excited Thio participate in this journey with you. Is there anything that you kind of like to let the audience know before we wrap up? >>Very happy about the way we started Toe talk. Converse. I think the proof of value as we did was a very good engagement with you guys. I mean, you guys were really there. I really appreciate the way that you took the proof of what I've worked with many other windows in terms of proof of value. But I think you had a marked difference in the way you you brought Snowflake. Tow us. Thank you so much and keep doing the good work. >>Thanks so much cinnamon for the partnership and were super pumped on, you know, making you very successful in your project. So thank you so much. >>Thank you.

>> We're here at the Data Cloud Summit 2020, tracking the rise of the data cloud. And we're talking about the ecosystem powering the next generation of innovation in cloud, you know, for decades, the technology industry has been powered by great products. Well, the cloud introduced a new type of platform that transcended point products and the next generation of cloud platforms is unlocking data-centric ecosystems where access to data is at the core of innovation, tapping the resources of many versus the capabilities of one. Casey McGee is here. He's the vice president of global ISV sales at Microsoft, and he's joined by Colleen Kapase, who is the VP of partnerships and global alliances at Snowflake. Folks, welcome to theCUBE. It's great to see you. >> Thanks Dave, good to see you. Thank you. >> Thanks for having us here. >> You're very welcome. So, Casey, let me start with you please. You know, Microsoft's got a long heritage, of course, working with partners, you're renowned in that regard, built a unbelievable ecosystem, the envy of many in the industry. So if you think about as enterprises, they're speeding up their cloud adoption, what are you seeing as the role and the importance of ecosystem, the ISV ecosystem specifically, in helping make customers' outcomes successful? >> Yeah, let me start by saying we have a 45 year history of partnership, so from our very beginning as a company, we invested to build these partnerships. And so let me start by saying from day one, we looked at a diverse ecosystem as one of the most important strategies for us, both to bring innovation to customers and also to drive growth. And so we're looking to build that environment even today. So 45 years later, focused on how do we zero in on the business outcomes that matter most to customers, usually identified by the industry that they're serving. So really building an ecosystem that helps us serve both the customers and the business outcomes they're looking to drive. And so we're building that ecosystem of ISVs on the Microsoft cloud and focused on bringing that innovation as a platform provider through those companies. >> So Casey, let's stay on that for a moment, if we can. I mean, you work with a lot of ISVs and you got a big portfolio of your own solutions. Now, sometimes they overlap with the ISV offerings of your partners. How do you balance the focus on first party solutions and third-party ISV partner solutions? >> Yeah, first and foremost, we're a platform company. So our whole intent is to bring value to that partner ecosystem. Well, sometimes that means we may have offers in market that may compliment one another. Our focus is really on serving the customer. So anytime we see that, we're looking at what is the most desired outcome for our customer, driving innovation into that specific business requirement. So for us, it's always focusing on the customer, and really zeroing in on making sure that we're solving their business problems. Sometimes we do that together with partners like Snowflake. Sometimes that means we do that on our own, but the key for us is really deeply understanding what's important to the customer and then bringing the best of the Microsoft and Snowflake scenarios to bear. >> You know, Casey, I appreciate that. A lot times people say "Dave, don't ask me that question. It's kind of uncomfortable." So Colleen, I want to bring you into the discussion. How does Snowflake view this dynamic, where you're simultaneously partnering and competing sometimes with some of the big cloud companies on the planet? >> Yeah, Dave, I think it's a great question, and really in this era of innovation, so many large companies like Microsoft are so diverse in their product set, it's almost impossible for them to not have some overlap with most of their ecosystem. But I think Casey said it really well, as long as we stay laser focused on the customer, and there are a lot of very happy Snowflake customers and happy Azure customers, we really win together. And I think we're finding ways in which we're working better and better together, from a technology standpoint, and from a field standpoint. And customers want to see us come together and bring best of breed solutions. So I think we're doing a lot better, and I'm looking forward to our future, too. >> So Casey, Snowflake, you know, they're really growing, they've got a pretty large footprint on Azure. You're talking hundreds of customers here that are active on that platform. I wonder if you could talk about the product integration points that you kind of completed initially, and then kind of what's on the horizon that you see as particularly important for your joint customers? >> You have to say, so one of the things that I love about this partnership is that, well, we start with what the customer wants. We bring that back into the engineering-level relationship that we have between the two companies. And so that's produced some pretty incredibly rich functionality together. So let me start by saying, you know, we've got eight Azure regions today with nine coming on soon. And so we have a geographic diversity that is important for many of our customers. We've also got a series of engineering-level integrations that we've already built. So that's functionality for Azure Private Link, as well as integration between Power BI, Azure Data Factory, and Azure Data Lake, all of this back again to serve the business outcomes that are required for our customers. So it's this level of integration that I think really speaks to the power of the partnership. So we are intently focused on the democratization of data. So we know that Snowflake is the premier partner to help us do that. So getting that right is key to enabling high concurrency use cases with large numbers of businesses, users coming together, and getting the performance they expect. >> Yeah, I appreciate that Casey, because a lot of times I'll, you know, I'll look at the press release. Sometimes we laugh, we call them Barney deals. You know, "I love you. You love me." But I listen for the word engineering and integration. Those are sort of important triggers. Colleen, or Casey too, but I want to start with Colleen. I mean, anything you would add to that, are there things that you guys have worked on together that you're particularly proud of, or maybe that have pushed the envelope and enabled new capabilities for customers where they've given you great feedback? Any examples you can share? >> Great question. And we're definitely focusing on making sure stability is a core value for both of us, so that what we offer, that our customers can trust, is going to work well and be dependable, so that's a key focus for us. We're also looking at how can we advance into the future, what can we do around machine learning, it's an area that's really exciting for a lot of the CXO-level leadership at our customers, so we're certainly focused on that. And also looking at Power BI and the visualization of how do we bring these solutions together as well. I'd also say at the same time, we're trying to make the buying experience frictionless for our customers, so we're also leveraging and innovating with Azure's Marketplace, so that our customers can easily acquire Snowflake together with Azure. And even that is being helpful for our customers. Casey, what are your thoughts, too? >> Yeah, let me add to that. I think the work that we've done with Power BI is pretty, pretty powerful. I mean, ultimately, we've got customers out there that are looking to better visualize the data, better inform decisions that they're making. So as much as AI and ML and the inherent power of the data that's being stored within Snowflake is important in and of itself, Power BI really unlocks that and helps drive better decisions, better visualization, and help drive to decision outcomes that are important to the customer. So I love the work that we're doing on Power BI and Snowflake. >> Yeah, and you guys both mentioned, you know, machine learning. I mean, they really are an ecosystem of tools. And the thing to me about Azure, it's all about optionality. You mentioned earlier, Casey, you guys are a platform. So, you know, customer A may want to use Power BI. Another customer might want to use another visualization tool, fine, from a platform perspective, you really don't care, do you? So I wonder Colleen, if we could, and again, maybe Casey can chime in afterwards. You guys, obviously everybody these days, but you in particular, you're focused on customer outcomes. That's the sort of starting point, and Snowflake for sure has built pretty significant experience working with large enterprises and working alongside of Microsoft to get other partners. In your experience, what are customers really looking for out of the two joint companies when they engage with Snowflake and Microsoft, so that one plus one is, you know, much bigger than two. Maybe Colleen, you could start. >> Yeah, I definitely think that what our customers are looking for is both trust and seamlessness. They just want the technology to work. The beauty of Snowflake is our ease of use. So many customers have questions about their business, more so now in this pandemic world than ever before. So the seamlessness, the ease of use, the frictionless, all of these things really matter to our joint customers, and seeing our teams come together, too, in the field, to show here's how Snowflake and Azure are better together, in your local area, and having examples of customers where we've had win-wins, which I'd say Casey, we're getting more and more of those every day, frankly, so it's pretty exciting times. And having our sales teams work as a partnership, even though we compete, we know where we play well together, and I see us doing that over and over again, more and more, around the world, too, which is really important as Snowflake pushes forward, beyond the North America geographies into stronger and stronger in the global regions, where frankly, Microsoft's had a long, storied history at. That's very exciting, especially in Europe and Asia. >> Casey, anything you'd add to that? >> Yeah. Colleen, it's well said. I think ultimately, what customers are looking for is that when our two companies come together, we bring new innovation, new ideas, new ways to solve old problems. And so I think what I love about this partnership is ultimately when we come together, whether it's engineering teams coming together to build new product, whether it's our sales and marketing teams out in front of the customers, across that spectrum, I think customers are looking for us to help bring new ideas. And I love the fact that we've engineered this partnership to do just that. And ultimately we're focused on how do we come together and build something new and different. And I think we can solve some of the most challenging problems with the power of the data and the innovation that we're bringing to the table. >> I mean, you know, Casey, I mean, everybody's really quite in awe and amazed at Microsoft's transformation, and really openness and willingness to really, change and lean into some of the big waves. I wonder if you could talk about your multi-platform strategy and what problems that you're solving in conjunction with Snowflake. >> Yeah, let me start by saying, you know, I think as much as we appreciate that feedback on the progress that we've been striving for, I mean, we're still learning every day, looking for new opportunities to learn from customers, from partners, and so a lot of what you see on the outside is the result of a really focused culture, really focusing on what's important to our customers, focusing on how do we build diversity and inclusion to everything we do, whether that's within Microsoft, with our partners, our customers, and ultimately, how do we show up as one Microsoft, I call one Microsoft kind of the partner's gift. It's ultimately how do our companies show up together? So I think if you look multi-platform, we have the same concept, right? We have the Microsoft cloud that we're offering out in the marketplace. The Microsoft cloud consists of what we're serving up as far as the platform, consists of what we're serving up for data and AI, modern workplace and business applications. And so this multi-cloud strategy for us is really focused on how do we bring innovation across each of the solution areas that matter most to customers. And so I see really the power of the Snowflake partnership playing in there. >> Awesome. Colleen, are there any examples you can share where, maybe this partnership has unlocked the customer opportunity or unique value? >> Yeah, I can't speak about the customer-specific, but what I can do and say is, Casey and I play very corporate roles in terms of we're thinking about the long-term partnership, we're driving the strategy. But hey, look, we'll get called in, we're working a deal right now, it's almost close of the quarter for us, we're literally working on an opportunity right now, how can we win together, how can we be competitive, the customers, the CIO has asked us to come together, to work on that solution. Very large, well-known brand. And we're able to get up to the very senior levels of our companies very quickly to make decisions on what do we need to do to be better and stronger together. And that's really what a partnership is about, you can do the long-term plans and the strategics and you can have great products, but when your executives can pick up the phone and call each other to work on a particular deal, for a particular customer's need, I think that's where the power of the partnership really comes together, and that's where we're at. And that's been a growth opportunity for us this year, is, wasn't necessarily where we were at, and I really have to thank Casey for that. He's done a ton, getting us the right glue between our executives, making sure the relationships are there, and making sure the trust is there, so when our customers need us to come together, that dialogue and that shared diction of putting customers first is there between both companies. So thank you, Casey. >> Oh, thanks, Colleen, the feeling's mutual. >> Well, I think this is key because as I said up front, we've gone from sort of very product-focused to platform-focused. And now we're tapping the power of the ecosystem. That's not always easy to get all the parts moving together, but we live in this API economy. You could say "Hey, I'm a company, everything's going to be homogeneous. Everything is going to be my stack." And maybe that's one way to solve the problem, but really that's not how customers want to solve the problem. Casey, I'll give you the last word. >> Yeah, let me just end by saying, you know, first off the cultures between our two companies couldn't be more well aligned. So I think ultimately when you ask yourself the question, "What do we do to best show up in front of our customers?" It is, focus on their business outcomes, focus on the things that matter most to them. And this partnership will show up well. And I think ultimately our greatest opportunity is to tap into that need, to that interest. And I couldn't be happier about the partnership and the fact that we are so well aligned. So thank you for that. >> Well guys, thanks very much for coming on theCUBE and unpacking some of the really critical aspects of the ecosystem. It was really a pleasure having you. >> Thank you so much for having us. >> Okay, and thank you for watching. Keep it right there. We've got more great content coming your way at the Data Cloud Summit.

>> Hello everybody. And welcome back to, theCUBE coverage of the Snowflake Data Cloud Summit 2020. We're tracking the rise of the Data Cloud, and fresh off the keynotes here, Frank Slootman, the Chairman and CEO of Snowflake and Anita Lynch, the Vice President of data governance at Disney streaming services. Folks Welcome. >> Thank you >> Thanks for having us Dave. >> Anita Disney plus awesome. You know, we signed up early, watched all the Marvel movies, Hamilton, the new Pixar movie soul. I haven't gotten it to the Mandalorian yet, your favorite. But really appreciate you guys coming on. Let me start with Frank. I'm glad you're putting forth this vision around the Data Cloud, because I never liked the term enterprise data warehouse. What you're doing is so different from the sort of that legacy world that I've known all these years. But start with why the Data Cloud? What problems are you trying to solve? And maybe some of the harder challenges you're seeing. >> Yeah, you know, we have a, we've come a long way in terms of workload execution. Right? In terms of scale and performance, and concurrent execution. We've really taken the lid off, sort of the physical constraints that have existed on these type of operations. But there's one problem that we're not yet solving, and that is the siloing and bunkering of data. And essentially, data is locked in applications, it's locked in data centers, it's locked in cloud, cloud regions. Incredibly hard for data science teams to really unlock the true value of data, when you can't address patterns that exist across data sets. So where we perpetuate a status we've had for forever since the beginning of computing. If we don't start to crack that problem now we have that opportunity. But the notion of a Data Cloud is like basically saying, "Look folks, we have to start on siloing and unlocking the data, and bring it into a place, where we can access it across all these perimeters, and boundaries that have historically existed. It's very much a step level function. Like the customers have always looked at things, one workload at a time, that mentality really has to go. You really have to have a Data Cloud mentality, as well as a workload orientation towards managing data. >> Anita, it was great hearing your role at Disney and in your keynote, and the work you're doing, the governance work. and you're serving a great number of stakeholders, enabling things like data sharing. You got really laser focused on trust, compliance, privacy. This idea of a data clean room is really interesting. Maybe you can expand on some of these initiatives here, and share what you're seeing as some of the biggest challenges to success, and of course, the opportunities that you're unlocking. >> Sure. In my role leading data governance, it's really critical to make sure that all of our stakeholders not only know what data is available and accessible to them. They can also understand really easily and quickly, whether or not the data that they're using is for the appropriate use case. And so that's a big part of how we scale data governance, and a lot of the work that we would normally have to do manually is actually done for us through the data clean rooms. >> Thank you for that. I wonder if you could talk a little bit more about the role of data and how your data strategy has evolved and maybe discuss some of the things that Frank mentioned about data silos. And I mean, obviously you can relate to that having been in the data business for a while, but I wonder if you can elucidate on that. >> Sure. I mean, data complexities are going to evolve over time in any traditional data architecture simply because you often have different teams at different periods and time trying to analyze and gather data across a whole lot of different sources. And the complexity that just arises out of that is due to the different needs of specific stakeholders. There are time constraints and quite often, it's not always clear how much value they're going to be able to extract from the data at the outset. So what we've tried to do to help break down those silos is allow individuals to see upfront how much value they're going to get from the data by knowing that it's trustworthy right away. By knowing that it's something that they can use in their specific use case right away. And by ensuring that essentially as they're continuing to kind of scale the use cases that they're focused on, they're no longer required to make multiple copies of the data, do multiple steps to reprocess the data. And that makes all the difference in the world. >> Yeah, for sure. I'm a copy Creek because it'd be the silent killer. Frank I followed you for a number of years, you're a big thinker, you and I have had a lot of conversations about the near-term, mid-term and long-term, I wonder if you could talk about, in your keynote you're talking about eliminating silos and connecting across data sources. Which is really powerful concept but really only if people are willing and able to connect and collaborate. Where do you see that happening? Maybe what are some of the blockers there? >> Well, there's certainly a natural friction there. I still remember when we first started to talk to, Salesforce, you know, they had discovered that we were a top three destination of Salesforce data and they were wondering why that was, and the reason is of course, that people take Salesforce data push it to snowflake because they want to overlay it with what data outside of Salesforce. Whether it's Adobe or any other marketing dataset. And then they want to run very highly scaled processes on it. But the reflexes in the world of SaaS is always like no, we're an Island, we're a planet down to ourselves. Everybody needs to come with us, as opposed to we go to a different platform to run these types of processes. It's no different for the public cloud vendor. They didn't only, they have massive moats around their storage to really prevent data from leaving their orbit. So there is natural friction in terms for this to happen. But on the other hand there is an enormous need. We can't deliver on the power and potential of data unless we allow it to come together. Snowflake is the platform that allows that to happen. We were pleased with our relationship with Salesforce because they did appreciate why this was important and why this was necessary. And we think, other parts of the industry will gradually come around to it as well. So the idea of a Data Cloud has really come, right. When people are recognizing why this matters now. It's not going to happen overnight. It is a step while will function a very big change in mentality and orientation. >> Yeah. It's almost as though the the SaaS suffocation of our industry sort of repeated some of the application silos and you build a hardened top around it, all the processes are hardened around it and okay, here we go. And you're really trying to break that, aren't you? >> Yep, exactly. >> Anita, again, I want to come back to this notion of governance. It's so it's so important. It's the first role in your title and it really underscores the importance of this. You know, Frank was just talking about some of the hurdles and this is a big one. I mean, we saw this in the early days of big data where governance was just afterthought. It was like bolted on the kind of wild wild West. I'm interested in your governance journey. And maybe you can share a little bit about what role snowflake has played there in terms of supporting that agenda and kind of what's next on that journey. >> Sure. Well, I've led data teams in numerous ways over my career. This is the first time that I've actually had the opportunity to focus on governance and what it's done is allowed for my organization to scale much more rapidly. And that's so critically important for our overall strategy as a company. >> Well, I mean, a big part of what you were talking about at least my inference in your talk was really that the business folks didn't have to care about, you know, wonder about they cared about it, but they don't have to wonder about, and about the privacy concerns, et cetera. You've taken care of all that it's sort of transparent to them. Is that right?| >> Yea That's right absolutely. So we focus on ensuring compliance across all of the different regions where we operate. We also partner very heavily with our legal and information security teams. They're critical to ensuring that we're able to do this. we don't do it alone. But governance includes not just the compliance and the privacy, it's also about data access, and it's also about ensuring data quality. And so all of that comes together under the governance umbrella. I also lead teams that focus on things like instrumentation, which is how we collect data. We focus on the infrastructure and making sure that we've architected for scale and all of these are really important components of our strategy. >> I got a...So I have a question maybe each of you can answer. I sort of see this, our industry moving from products, to then, to platforms and platforms even evolving into ecosystems. And then there's this ecosystem of data. You guys both talked a lot about data sharing but maybe Frank, you can start, Anita you can add on to Frank's answer. You're obviously both passionate about the use of data and trying to do so in a responsible way. That's critical but it's also going to have business impact. Frank, where's this passion come from on your side. And how are you putting into action in your own organization? >> Well, you know I'm really going to date myself here, but many, many years ago, I saw the first glimpse of multidimensional databases that were used for reporting really on IBM mainframes. And it was extraordinarily difficult. We didn't even have the words back then in terms of data warehouses and business. All these terms didn't exist. People just knew that they wanted to have a more flexible in way of reporting and being able to pivot data dimensionally and all these kinds of things. And I just bought whatever this predates windows 3.1, which really, set off the whole sort of graphical, way of dealing with systems which there's now a whole generations of people that don't know any different right? So I've lived the pain of this problem and sort of had a front row seat to watching this transpire over a very long period of time. And that's one of the reasons, why I'm here, because I finally seen, a glimpse of, I also, as an industry fully, fully just unleashing and unlocking to potential. We're now in a place where the technology is ahead of people's ability to harness it. Which we've never been there before. It was always like, we wanted to do things that technology wouldn't let us. It's different now. I mean, people are just, their heads are spinning with what's now possible, which is why you see markets evolve, very rapidly right now we were talking earlier about how you can't take past definitions and concepts and apply them to what's going on in the world. because the world's changing right in front of your eyes right now. >> So Anita maybe you could add on to what Frank just said and share some of the business impacts and outcomes that are notable since you've really applied your your love of data and maybe, maybe touch on, on culture. Data culture, any words of wisdom for folks in the audience who might be thinking about embarking on a Data Cloud journey, similar to what you've been on. >> Yeah sure. I think for me, I fell in love with technology first and then I fell in love with data. And I fell in love with data because of the impact that data can have on both the business and the technology strategy. And so it's sort of that nexus, between all three. And in terms of my career journey and some of the impacts that I've seen. I mean, I think with the advent of the cloud, before, well, how do I say that. Before the cloud actually became so prevalent and such a common part of the strategy that's required it was so difficult, you know, so painful. It took so many hours to actually be able to calculate the volumes of data that we had. Now we have that accessibility, and then on top of it, with the snowflake Data Cloud it's much more performance oriented from a cost perspective because you don't have multiple copies of the data, or at least you don't have to have multiple copies of the data. And I think moving beyond some of the traditional mechanisms for for measuring business impact, has only been possible with the volumes of data that we have available to us today. And it's just, it's phenomenal to see the speed at which we can operate. And really, truly understand our customer's interests and their preferences and then tailor the experiences that they really want and deserve for them. It's, been a great feeling to get to this point in time. >> That's fantastic. So, Frank, I got to ask you this. So in your spare time you decided to write a book, I'm loving it. I don't have a signed copy so I'm going to have to send it back and have you sign it. But, and you're, I love the inside baseball. It's just awesome. So really appreciate that. So, but why did you decide to write a book? >> Well, there were a couple of reasons, obviously we thought of as an interesting tale to tell for anybody, who is interested in what's going on, how did this come about? Who are the characters behind the scenes and all this stuff. But from a business standpoint because this is such a step function it's so non incremental, we felt like, we really needed quite a bit of real estate to really lay out what the full narrative and context is. And, we thought, the books titled the "Rise of the Data Cloud." That's exactly what it is. And we're trying to make the case for that mindset, that mentality, that strategy because all of us, I think as an industry, were at risk of, persisting, perpetuating where we've been since the beginning of computing. So we're really trying to make a pretty forceful case for a look. There's an enormous opportunity out there but there's some choices you have to make along the way. >> Guys, we got to leave it there. Frank, I know you and I are going to talk again Anita, I hope we have a chance to meet face to face and talk in theCUBE live someday. You're phenomenal guests and what a great story. Thank you both for coming on. And thank you for watching. Keep it right there. You're watching the, Snowflake Data Cloud Summit, on theCUBE.

>>Okay, >>listen, we're gearing up for the start of the snowflake Data Cloud Summit, and we wanna go back to the early roots of Snowflake. We've got some of the founding engineers here. Abdul Monir, Ashish Motive, Allah and Alison Lee There three individuals that were at snowflake in the early years and participated in many of the technical decisions that led to the platform and is making snowflake famous today. Folks, great to see you. Thanks so much for taking some time out of your busy schedules. Hey, it's gotta be really gratifying. Thio, See this platform that you've built, you know, taking off and changing businesses. So I'm sure it was always smooth sailing. Right? There were. There were no debates. Wherever. >>I've never seen an engineer get into the bed. >>Alright, So seriously so take us back to the early days. You guys, you know, choose whoever wants to start. But what was it like early on? We're talking 2013 here, right? >>When I think back to the early days of Snowflake, I just think of all of us sitting in one room at the time. You know, we just had an office that was one room with, you know, 12 or 13 engineers sitting there clacking away on our keyboards, uh, working really hard, turning out code, uh, punctuated by you know, somebody asking a question about Hey, what should we do about this, or what should we do about that? And then everyone kind of looking up from their keyboards and getting into discussions and debates about the work that we're doing. >>So so Abdul it was just kind of heads down headphones on, just coating or e think there was >>a lot of talking and followed by a lot of typing. Andi, I think there were periods of time where where you know, anyone could just walk in into the office and probably out of the office and all the here is probably people, uh, typing away at their keyboards. And one of my member vivid, most vivid memories is actually I used to sit right across from Alison, and there's these huge to two huge monitor monitors between us and I would just here typing away in our keyboard, and sometimes I was thinking and and and, uh and all that type and got me nervous because it seemed like Alison knew exactly what what, what she needed to do, and I was just still thinking about it. >>So she she was just like bliss for for you as a developer engineer was it was a stressful time. What was the mood? So when you don't have >>a whole lot of customers, there's a lot of bliss. But at the same time, there was a lot of pressure on us to make sure that we build the product. There was a time line ahead of us. We knew we had to build this in a certain time frame. Um, so one thing I'll add to what Alison and Abdulle said is we did a lot of white boarding as well. There are a lot of discussions, and those discussions were a lot of fun. They actually cemented what we wanted to build. They made sure everyone was in tune, and and there we have it. >>Yes, so I mean, it is a really exciting time doing any start up. But when you know when you have to make decisions and development, invariably you come to a fork in the road. So I'm curious as to what some of those forks might have been. How you guys decided You know which fork to take. Was there a Yoda in the room that served as the Jedi master? I mean, how are those decisions made? Maybe you could talk about that a little bit. >>Yeah, that's an interesting question. And I think one of a Zai think back. One of the memories that that sticks out in my mind is is this, uh, epic meeting and one of our conference rooms called Northstar. Many of our conference rooms are named after ski resorts because the founders, they're really into skiing. And that's why that's where the snowflake name comes from. So there was this epic meeting and I'm not even sure exactly what topic we were discussing. I think it was It was the sign up flow and and there were a few different options on the table and and and one of the options that that people were gravitating Teoh, one of the founders, didn't like it and and on, and they said a few times that there's this makes no sense. There's no other system in the world that does it this way, and and I think one of the other founders said, uh, that's exactly why we should do it this way. And or at least seriously, consider this option. So I think there was always this, um, this this, uh, this tendency and and and this impulse that that we needed to think big and think differently and and not see the world the way it is but the way we wanted it to be and then work our way backwards and try to make it happen. >>Alison, Any fork in the road moments that you remember. >>Well, I'm just thinking back to a really early meeting with sheesh! And and a few of our founders where we're debating something probably not super exciting to a lot of people outside of hardcore database people, which was how to represent our our column metadata. Andi, I think it's funny that you that you mentioned Yoda because we often make jokes about one of our founders. Teary Bond refer to him as Yoda because he hasn't its tendency to say very concise things that kind of make you scratch your head and say, Wow, why didn't I think of that? Or you know, what exactly does that mean? I never thought about it that way. So I think when I think of the Yoda in the room, it was definitely Terry, >>uh, excuse you. Anything you can add to this, this conversation >>I'll agree with Alison on the you're a comment for short. Another big fork in the road, I recall, was when we changed. What are meta store where we store our own internal metadata? We used >>to use >>a tool called my sequel and we changed it. Thio another database called Foundation TV. I think that was a big game changer for us. And, you know, it was a tough decision. It took us a long time. For the longest time, we even had our own little branch. It was called Foundation DB, and everybody was developing on that branch. It's a little embarrassing, but, you know, those are the kind of decisions that have altered altered the shape of snowflake. >>Yeah. I mean, these air, really, you know, down in the weeds, hardcore stuff that a lot of people that might not be exposed to What would you say was the least obvious technical decision that you had to make it the time. And I wanna ask you about the most obvious to. But what was the what was the one that was so out of the box? I mean, you kind of maybe mentioned it a little bit before, but what if we could double click on that? >>Well, I think one of the core decisions in our architectures the separation of compute and storage on Do you know that is really court architecture. And there's so many features that we have today, um, for instance, data sharing zero copy cloning that that we couldn't have without that architecture. Er, um and I think it was both not obvious. And when we told people about it in the early days, there was definitely skepticism about being able to make that work on being able Thio have that architecture and still get great performance. >>Anything? Yeah, anything that was, like, clearly obvious, that is, Maybe that maybe that was the least and the most that that separation from computing story because it allowed you toe actually take advantage of cloud native. But But was there an obvious one that, you know, it's sort of dogma that you, you know, philosophically lived behind. You know, to this day, >>I think one really obvious thing, um is the sort of no tuning, no knobs, ease of use story behind snowflake. Andi and I say it's really obvious because everybody wants their system to be easy to use. But then I would say there are tons of decisions behind that, that it's not always obvious three implications of of such a choice, right, and really sticking to that. And I think that that's really like a core principle behind Snowflake that that led to a lot of non obvious decisions as a result of sticking to that principle. So, yeah, I >>think to add to that now, now you've gotten us thinking I think another really interesting one was was really, um, should we start from scratch or or should we use something that already exists and and build on top of that? And I think that was one of these, um, almost philosophical kind of stances that we took that that a lot of the systems that were out there were the way they were because because they weren't built for the for the platforms that they were running on, and the big thing that we were targeting was the cloud. And so one of the big stances we took was that we were gonna build it from scratch, and we weren't gonna borrow a single line of code from many other database out there. And this was something that really shocked a lot of people and and many times that this was pretty crazy and it waas. But this is how you build great products. >>That's awesome. All right. She should give you the last word. We got, like, just like 30 seconds left to bring us home >>Your till date. Actually, one of those said shocks people when you talk to them and they say, Wow, you're not You're not really using any other database and you build this entirely yourself. The number of people who actually can build a database from scratch are fairly limited. The group is fairly small, and so it was really a humongous task. And as you mentioned, you know, it really changed the direction off how we design the database. What we what does the database really mean? Tow us right the way Snowflake has built a database. It's really a number of organs that come together and form the body and That's also a concept that's novel to the database industry. >>Guys, congratulations. You must be so proud. And, uh, there's gonna be awesome watching the next next decade, so thank you so much for sharing your stories. >>Thanks, dude. >>Thank you.

>>Hello, everyone. And welcome back to our wall to wall coverage of the data Cloud Summit. This is Dave a lot. And we're seeing the emergence of a next generation workload in the cloud were more facile access and governed. Sharing of data is accelerating. Time to insights and action. All right, allow me to introduce our next guest. Amy Irwin is here. She's the vice president of strategy for experience. And Matt Glickman is VP customer product strategy it snowflake with an emphasis on financial services. Folks, welcome to the Cube. Thanks so much for coming on. >>Thanks for >>having us >>nice to be here. Hey, >>So, Amy, I mean, obviously 2020 has been pretty unique and crazy and challenging time for a lot of people. I don't know why I've been checking my credit score a lot more for some reason. On the app I love the app I got hacked. I had a lock it the other day I locked my credit. Somebody tried to dio on and it worked. I was so happy. So thank you for that. But so we know experience, but there's a ton of data behind what you do. I wonder if you could share kind of where you sit in the data space and how you've seen organizations leverage data up to this point. And really, if you could address maybe some of the changes that you're seeing as a result of the pandemic, that would be great. >>Sure, sure. Well, Azaz, you mentioned experience Eyes best known as a credit bureau. Uh, I work in our marketing services business unit, and what we do is we really help brands leverage the power of data and technology to make the right marketing decisions and better understand and connect with consumers. Eso we offer markers products around data identity activation measurement. We have a consumer view data file that's based on off line P I and contains demographic interest, transaction data and other attributes on about 300 million people in the U. S. Uh, and on the identity side, we've always been known for our safe haven or privacy friendly matching that allows marketers to connect their first party data to experience or other third parties. Uh, but in today's world, with the growth and importance of digital advertising and consumer behavior shifting to digital, uh, experience also is working to connect that offline data to the digital world for a complete view of the customer you mentioned co vid, um, we actually we serve many different verticals. And what we're seeing from our clients during co vid is that there's a bearing impact of the pandemic. The common theme is that those that have successfully pivoted their businesses to digital are doing much better. Uh, as we all know, Kobe accelerated very strong trends to digital both in the commerce and immediate viewing habits. We work with a lot of retailers. Retail is a tale of two cities with big box and grocery growing and apparel retail really struggling. We've helped our clients leveraging our data to better understand the shifts in these consumer behaviors and better segment their customers during this really challenging time. Eso think about there's there's a group of customers that is still staying home that is sheltered in place. There's a group of customers starting that significantly varied their consumer behavior, but it's starting to venture out a little. And then there's a group of customers that's doing largely what they did before and a somewhat modified fashion. So we're helping our clients segment those customers into groups to try and understand the right messaging and right offers for each of those groups. And we're also helping them with at risk audiences. Eso That's more on the financial side. Which of your customers air really struggling? Do the endemic And how do you respond? >>It's awesome, thank you. You know, it's it's funny. I mean somebody I saw Twitter poll today asking if we measure our screen time and I said, Oh my no eso Matt, let me ask you. You spend a ton of time in financial services. You really kind of cut your teeth there, and it's always been very data oriented. You've seen a lot of changes tell us about how your customers are bringing together data, the skills that people obviously a big part of the equation and applications to really put data at the center of their universe. What's new and different that these companies were getting out of the investments in data and skills. >>That's a great question. Um, the acceleration that Amy mentioned Israel, Um, we're seeing it particularly this year, but I think even in the past few years, the reluctance of customers to embrace the cloud is behind us. And now there's this massive acceleration to be able to go faster on, and in some ways the new entrance into this category. Have an advantage versus, you know, the companies that have been in the space within its financial services or beyond. Um, and in a lot of ways they are are seeing the cloud and services like snowflake as a way toe not only catch up but leapfrog your competitors and really deliver a differentiated experience to your customers to your business, internally or externally. Um, and this past, you know, however long this crisis has been going on, has really only accelerated that, because now there's a new demand. Understand your customer better your your business better with with your traditional data sources and also new alternative data sources, Um, and also be able to take a pulse. One of things that we learned which was you know, I opening experience was as the crisis unfolded, one of our data partners decided to take the data sets about where the cases where were happening from the Johns Hopkins and World Health Organization and put that on our platform, and it became a runaway hit where now with thousands of our customers overnight, we're using this data to understand how their business was doing versus how the crisis was unfolding in real time. On this has been a game changer, and I think it's only it's only scratching the surface of what now the world will be able to do when data is really at their fingertips. You're not hindered by your legacy platforms. >>I wrote about that back in the early days of the pandemic when you guys did that and talked about some of the changes that you guys enabled and and, you know you're right about Cloud. I mean, financial services. Cloud used to be an evil word, and now it's almost become a mandate. Amy, I >>wonder if you >>could tell us a little bit more about what? What, you know your customers they're having to work through in order to achieve some of these outcomes. I mean, I'm interested in the starting point. I've been talking a lot and writing a lot on talking to practitioners about what I call the data lifecycle. Sometimes people call it the data pipeline. It za complicated matter, but those customers and companies that can put data at the center and really treat that pipeline is the heart of their organization, If you will, really succeeding. What are you seeing and what really is the starting point there? >>Yes, yes, that's a good question. And as you mentioned, first party, I mean, we start with first party data. Right? First party data is critical to understanding consumers on been in different verticals, different companies. Different brands have varying levels of first party data. So retailers gonna have a lot more first party data financial services company, then say an auto manufacturer. Uh, while many marketers have that first party data to really have a 3 60 view of the customer, they need third party data as well. And that's where experience comes in. We help brands connect those disparate data sets both 1st and 3rd party baked data to better understand consumers and create a single customer view, which has a number of applications. I think the last that I heard was that there's about eight devices on average per person. I always joke that we're gonna have these enormous. I mean, that that number is growing. We're gonna have these enormous charging stations in our house, and I think we're because all the different devices and way seamlessly move from device to device along our customer journey. And, um, if the brand doesn't understand who we are, it's much harder for the brand to connect with consumers and create a positive customer experience and way site that about 95% of companies are actually that they are looking to achieve that single customer view. They recognize, um, that they need that. And they've aligned various teams from e commerce to marketing to sales toe at a minimum in just their first party data and then connect that data to better understand, uh, consumers so consumers can interact with the brand through website and mobile app in store visits, um, by the phone, TV ads, etcetera. And a brand needs to use all of those touchpoints often collected by different parts of the organization and then adding that third party data to really understand the consumers in terms of specific use cases, Um, there's there's about three that come to mind, so there's first. There's relevant advertising and reaching the right customer. There's measurement s or being able to evaluate your advertising efforts. Uh, if you see an ad on the if I see it out of my mobile and then I by by visiting a desktop website understanding or get a direct mail piece, understanding that those connect those interactions are all connected to the same person is critical for measurement. And then there's, uh, there's personalization, um, which includes encourage customer experience amongst your own, um, touch points with that consumer personalized marketing communication and then, of course, um, analytics. So those are the use cases we're seeing? Great. >>Thank you, Amy. I'm out. You can't really talk about data without talking about, >>you know, >>governance and and and compliance. And I remember back in 2006, when the Federal Rules of Civil Procedure went in, it was easy. The lawyers just said, No, nobody can have access, but that's changed. One of things I like about what snowflakes doing with the data cloud is it's really about democratizing access, but doing so in a way that gives people confidence that they only have access to the right data. So maybe you could talk a little bit about how you're thinking about this topic, what you're doing to help customers navigate, which has traditionally been such a really challenging problem. >>No, it's another great question. Um, this is where I think the major disruption is happening. Um, and what Amy described being able to join together 1st and 3rd party data sets. Um, being able to do this was always a challenge because data had to be moved around, had a ship, my first party data to the other side. The third party data had to be shipped to me on being able to join those data sets together, um was problematic at best. And now, with the focus on privacy and protecting P, I, um, this is this is something that has to change. And the good news is with the data cloud data does not have to move. Data can stay where it belongs. Experiencing keep its data experience. Customers can hold on to their data. Yet the data can be joined together on this universal global platform that we call the data cloud. On top of that, and particularly with the regulations that are coming out that are gonna prevent data from being collected on either a mobile device or in wet warren as cookies and Web browsers, new approaches. And we're seeing this a lot in our space, both in financials and in media is to set up these data clean rooms where both sides can give access to one another, but not have to reveal any P i i to do that joint. Um, this is gonna be huge right now. You actually can protect your your customers, private your consumers, private identities, but still accomplish that. Join that Amy mentioned to be able to thio relate the cause and effect of these campaigns and really understand the signals. Um, that these data sets are trying to say about one another again without having to move data without having to reveal P. I We're seeing this happening now. This is this is the next big thing that we're gonna see explode over the next months and years to come. >>I totally agree. Massive changes coming in public policy in this area, and I wanted we only have a few minutes left. I wonder if for our audience members that you know, looking for some advice, what's the what's the one thing you'd recommend? They start doing differently or consider putting in place. That's going to set them up for success over the next decade. >>Yeah, that's a good question. Um, you know, I think e always say, you know, first harness all of your first party data across all touchpoints. Get that first party data in one place and working together Second back that data with trusted third parties and in mats, just in some ways to do that and then third, always with the customer first speak their language. Uh, where and when they want to be, uh, reached out thio on and use the information. You have to really create a better a better customer experience for your customers. >>Matt. What would you add to that? Bring us home if you would >>applications. Um, the idea that data can now be your data can now be pulled into your own business applications the same way that Netflix and Spotify are pulled into your consumer and lifestyle applications again without data moving these personalized applications experiences is what I encourage everyone to be thinking about from first principles. What would you do in your next app that you're gonna build? If you had all of your consumers, consumers had access to their data in the app and not having to think about things you know from scratch. Leverage the data cloud leverage these, you know, service providers like experience and build the applications of tomorrow. >>I'm super excited when I talked to practitioners like yourselves about the future of data Guys, Thanks so much for coming on. The Cube was really a pleasure having you and hope we can continue this conversation in the future. >>Thank you. >>All right. Thank you for watching. Keep it right there. We've got great content. Tons of content coming at the Snowflake Data Cloud Summit. This is Dave Volonte for the Cube. Keep it right there.

>> From theCUBE Studios in Palo Alto in Boston, bringing you data-driven insights from theCUBE in ETR. This is Breaking Analysis with Dave Vellante. >> Snowflake is not going to grow into its valuation by stealing the croissant from the breakfast table of the on-prem data warehouse vendors. Look, even if snowflake got 100% of the data warehouse business, it wouldn't come close to justifying its market cap. Rather Snowflake has to create an entirely new market based on completely changing the way organizations think about monetizing data. Every organization I talk to says it wants to be, or many say they already are data-driven. why wouldn't you aspire to that goal? There's probably nothing more strategic than leveraging data to power your digital business and creating competitive advantage. But many businesses are failing, or I predict, will fail to create a true data-driven culture because they're relying on a flawed architectural model formed by decades of building centralized data platforms. Welcome everyone to this week's Wikibon Cube Insights powered by ETR. In this Breaking Analysis, I want to share some new thoughts and fresh ETR data on how organizations can transform their businesses through data by reinventing their data architectures. And I want to share our thoughts on why we think Snowflake is currently in a very strong position to lead this effort. Now, on November 17th, theCUBE is hosting the Snowflake Data Cloud Summit. Snowflake's ascendancy and its blockbuster IPO has been widely covered by us and many others. Now, since Snowflake went public, we've been inundated with outreach from investors, customers, and competitors that wanted to either better understand the opportunities or explain why their approach is better or different. And in this segment, ahead of Snowflake's big event, we want to share some of what we learned and how we see it. Now, theCUBE is getting paid to host this event, so I need you to know that, and you draw your own conclusions from my remarks. But neither Snowflake nor any other sponsor of theCUBE or client of SiliconANGLE Media has editorial influence over Breaking Analysis. The opinions here are mine, and I would encourage you to read my ethics statement in this regard. I want to talk about the failed data model. The problem is complex, I'm not debating that. Organizations have to integrate data and platforms with existing operational systems, many of which were developed decades ago. And as a culture and a set of processes that have been built around these systems, and they've been hardened over the years. This chart here tries to depict the progression of the monolithic data source, which, for me, began in the 1980s when Decision Support Systems or DSS promised to solve our data problems. The data warehouse became very popular and data marts sprung up all over the place. This created more proprietary stovepipes with data locked inside. The Enron collapse led to Sarbanes-Oxley. Now, this tightened up reporting. The requirements associated with that, it breathed new life into the data warehouse model. But it remained expensive and cumbersome, I've talked about that a lot, like a snake swallowing a basketball. The 2010s ushered in the big data movement, and Data Lakes emerged. With a dupe, we saw the idea of no schema online, where you put structured and unstructured data into a repository, and figure it all out on the read. What emerged was a fairly complex data pipeline that involved ingesting, cleaning, processing, analyzing, preparing, and ultimately serving data to the lines of business. And this is where we are today with very hyper specialized roles around data engineering, data quality, data science. There's lots of batch of processing going on, and Spark has emerged to improve the complexity associated with MapReduce, and it definitely helped improve the situation. We're also seeing attempts to blend in real time stream processing with the emergence of tools like Kafka and others. But I'll argue that in a strange way, these innovations actually compound the problem. And I want to discuss that because what they do is they heighten the need for more specialization, more fragmentation, and more stovepipes within the data life cycle. Now, in reality, and it pains me to say this, it's the outcome of the big data movement, as we sit here in 2020, that we've created thousands of complicated science projects that have once again failed to live up to the promise of rapid cost-effective time to insights. So, what will the 2020s bring? What's the next silver bullet? You hear terms like the lakehouse, which Databricks is trying to popularize. And I'm going to talk today about data mesh. These are other efforts they look to modernize datalakes and sometimes merge the best of data warehouse and second-generation systems into a new paradigm, that might unify batch and stream frameworks. And this definitely addresses some of the gaps, but in our view, still suffers from some of the underlying problems of previous generation data architectures. In other words, if the next gen data architecture is incremental, centralized, rigid, and primarily focuses on making the technology to get data in and out of the pipeline work, we predict it's going to fail to live up to expectations again. Rather, what we're envisioning is an architecture based on the principles of distributed data, where domain knowledge is the primary target citizen, and data is not seen as a by-product, i.e, the exhaust of an operational system, but rather as a service that can be delivered in multiple forms and use cases across an ecosystem. This is why we often say the data is not the new oil. We don't like that phrase. A specific gallon of oil can either fuel my home or can lubricate my car engine, but it can't do both. Data does not follow the same laws of scarcity like natural resources. Again, what we're envisioning is a rethinking of the data pipeline and the associated cultures to put data needs of the domain owner at the core and provide automated, governed, and secure access to data as a service at scale. Now, how is this different? Let's take a look and unpack the data pipeline today and look deeper into the situation. You all know this picture that I'm showing. There's nothing really new here. The data comes from inside and outside the enterprise. It gets processed, cleanse or augmented so that it can be trusted and made useful. Nobody wants to use data that they can't trust. And then we can add machine intelligence and do more analysis, and finally deliver the data so that domain specific consumers can essentially build data products and services or reports and dashboards or content services, for instance, an insurance policy, a financial product, a loan, that these are packaged and made available for someone to make decisions on or to make a purchase. And all the metadata associated with this data is packaged along with the dataset. Now, we've broken down these steps into atomic components over time so we can optimize on each and make them as efficient as possible. And down below, you have these happy stick figures. Sometimes they're happy. But they're highly specialized individuals and they each do their job and they do it well to make sure that the data gets in, it gets processed and delivered in a timely manner. Now, while these individual pieces seemingly are autonomous and can be optimized and scaled, they're all encompassed within the centralized big data platform. And it's generally accepted that this platform is domain agnostic. Meaning the platform is the data owner, not the domain specific experts. Now there are a number of problems with this model. The first, while it's fine for organizations with smaller number of domains, organizations with a large number of data sources and complex domain structures, they struggle to create a common data parlance, for example, in a data culture. Another problem is that, as the number of data sources grows, organizing and harmonizing them in a centralized platform becomes increasingly difficult, because the context of the domain and the line of business gets lost. Moreover, as ecosystems grow and you add more data, the processes associated with the centralized platform tend to get further genericized. They again lose that domain specific context. Wait (chuckling), there are more problems. Now, while in theory organizations are optimizing on the piece parts of the pipeline, the reality is, as the domain requires a change, for example, a new data source or an ecosystem partnership requires a change in access or processes that can benefit a domain consumer, the reality is the change is subservient to the dependencies and the need to synchronize across these discrete parts of the pipeline or actually, orthogonal to each of those parts. In other words, in actuality, the monolithic data platform itself remains the most granular part of the system. Now, when I complain about this faulty structure, some folks tell me this problem has been solved. That there are services that allow new data sources to really easily be added. A good example of this is Databricks Ingest, which is, it's an auto loader. And what it does is it simplifies the ingestion into the company's Delta Lake offering. And rather than centralizing in a data warehouse, which struggles to efficiently allow things like Machine Learning frameworks to be incorporated, this feature allows you to put all the data into a centralized datalake. More so the argument goes, that the problem that I see with this, is while the approach does definitely minimizes the complexities of adding new data sources, it still relies on this linear end-to-end process that slows down the introduction of data sources from the domain consumer beside of the pipeline. In other words, the domain experts still has to elbow her way into the front of the line or the pipeline, in this case, to get stuff done. And finally, the way we are organizing teams is a point of contention, and I believe is going to continue to cause problems down the road. Specifically, we've again, we've optimized on technology expertise, where for example, data engineers, well, really good at what they do, they're often removed from the operations of the business. Essentially, we created more silos and organized around technical expertise versus domain knowledge. As an example, a data team has to work with data that is delivered with very little domain specificity, and serves a variety of highly specialized consumption use cases. All right. I want to step back for a minute and talk about some of the problems that people bring up with Snowflake and then I'll relate it back to the basic premise here. As I said earlier, we've been hammered by dozens and dozens of data points, opinions, criticisms of Snowflake. And I'll share a few here. But I'll post a deeper technical analysis from a software engineer that I found to be fairly balanced. There's five Snowflake criticisms that I'll highlight. And there are many more, but here are some that I want to call out. Price transparency. I've had more than a few customers telling me they chose an alternative database because of the unpredictable nature of Snowflake's pricing model. Snowflake, as you probably know, prices based on consumption, just like AWS and other cloud providers. So just like AWS, for example, the bill at the end of the month is sometimes unpredictable. Is this a problem? Yes. But like AWS, I would say, "Kill me with that problem." Look, if users are creating value by using Snowflake, then that's good for the business. But clearly this is a sore point for some users, especially for procurement and finance, which don't like unpredictability. And Snowflake needs to do a better job communicating and managing this issue with tooling that can predict and help better manage costs. Next, workload manage or lack thereof. Look, if you want to isolate higher performance workloads with Snowflake, you just spin up a separate virtual warehouse. It's kind of a brute force approach. It works generally, but it will add expense. I'm kind of reminded of Pure Storage and its approach to storage management. The engineers at Pure, they always design for simplicity, and this is the approach that Snowflake is taking. Usually, Pure and Snowflake, as I have discussed in a moment, is Pure's ascendancy was really based largely on stealing share from Legacy EMC systems. Snowflake, in my view, has a much, much larger incremental market opportunity. Next is caching architecture. You hear this a lot. At the end of the day, Snowflake is based on a caching architecture. And a caching architecture has to be working for some time to optimize performance. Caches work well when the size of the working set is small. Caches generally don't work well when the working set is very, very large. In general, transactional databases have pretty small datasets. And in general, analytics datasets are potentially much larger. Is it Snowflake in the analytics business? Yes. But the good thing that Snowflake has done is they've enabled data sharing, and it's caching architecture serves its customers well because it allows domain experts, you're going to hear this a lot from me today, to isolate and analyze problems or go after opportunities based on tactical needs. That said, very big queries across whole datasets or badly written queries that scan the entire database are not the sweet spot for Snowflake. Another good example would be if you're doing a large audit and you need to analyze a huge, huge dataset. Snowflake's probably not the best solution. Complex joins, you hear this a lot. The working set of complex joins, by definition, are larger. So, see my previous explanation. Read only. Snowflake is pretty much optimized for read only data. Maybe stateless data is a better way of thinking about this. Heavily right intensive workloads are not the wheelhouse of Snowflake. So where this is maybe an issue is real-time decision-making and AI influencing. A number of times, Snowflake, I've talked about this, they might be able to develop products or acquire technology to address this opportunity. Now, I want to explain. These issues would be problematic if Snowflake were just a data warehouse vendor. If that were the case, this company, in my opinion, would hit a wall just like the NPP vendors that proceeded them by building a better mouse trap for certain use cases hit a wall. Rather, my promise in this episode is that the future of data architectures will be really to move away from large centralized warehouses or datalake models to a highly distributed data sharing system that puts power in the hands of domain experts at the line of business. Snowflake is less computationally efficient and less optimized for classic data warehouse work. But it's designed to serve the domain user much more effectively in our view. We believe that Snowflake is optimizing for business effectiveness, essentially. And as I said before, the company can probably do a better job at keeping passionate end users from breaking the bank. But as long as these end users are making money for their companies, I don't think this is going to be a problem. Let's look at the attributes of what we're proposing around this new architecture. We believe we'll see the emergence of a total flip of the centralized and monolithic big data systems that we've known for decades. In this architecture, data is owned by domain-specific business leaders, not technologists. Today, it's not much different in most organizations than it was 20 years ago. If I want to create something of value that requires data, I need to cajole, beg or bribe the technology and the data team to accommodate. The data consumers are subservient to the data pipeline. Whereas in the future, we see the pipeline as a second class citizen, with a domain expert is elevated. In other words, getting the technology and the components of the pipeline to be more efficient is not the key outcome. Rather, the time it takes to envision, create, and monetize a data service is the primary measure. The data teams are cross-functional and live inside the domain versus today's structure where the data team is largely disconnected from the domain consumer. Data in this model, as I said, is not the exhaust coming out of an operational system or an external source that is treated as generic and stuffed into a big data platform. Rather, it's a key ingredient of a service that is domain-driven and monetizable. And the target system is not a warehouse or a lake. It's a collection of connected domain-specific datasets that live in a global mesh. What is a distributed global data mesh? A data mesh is a decentralized architecture that is domain aware. The datasets in the system are purposely designed to support a data service or data product, if you prefer. The ownership of the data resides with the domain experts because they have the most detailed knowledge of the data requirement and its end use. Data in this global mesh is governed and secured, and every user in the mesh can have access to any dataset as long as it's governed according to the edicts of the organization. Now, in this model, the domain expert has access to a self-service and obstructed infrastructure layer that is supported by a cross-functional technology team. Again, the primary measure of success is the time it takes to conceive and deliver a data service that could be monetized. Now, by monetize, we mean a data product or data service that it either cuts cost, it drives revenue, it saves lives, whatever the mission is of the organization. The power of this model is it accelerates the creation of value by putting authority in the hands of those individuals who are closest to the customer and have the most intimate knowledge of how to monetize data. It reduces the diseconomies at scale of having a centralized or a monolithic data architecture. And it scales much better than legacy approaches because the atomic unit is a data domain, not a monolithic warehouse or a lake. Zhamak Dehghani is a software engineer who is attempting to popularize the concept of a global mesh. Her work is outstanding, and it's strengthened our belief that practitioners see this the same way that we do. And to paraphrase her view, "A domain centric system must be secure and governed with standard policies across domains." It has to be trusted. As I said, nobody's going to use data they don't trust. It's got to be discoverable via a data catalog with rich metadata. The data sets have to be self-describing and designed for self-service. Accessibility for all users is crucial as is interoperability, without which distributed systems, as we know, fail. So what does this all have to do with Snowflake? As I said, Snowflake is not just a data warehouse. In our view, it's always had the potential to be more. Our assessment is that attacking the data warehouse use cases, it gave Snowflake a straightforward easy-to-understand narrative that allowed it to get a foothold in the market. Data warehouses are notoriously expensive, cumbersome, and resource intensive, but they're a critical aspect to reporting and analytics. So it was logical for Snowflake to target on-premise legacy data warehouses and their smaller cousins, the datalakes, as early use cases. By putting forth and demonstrating a simple data warehouse alternative that can be spun up quickly, Snowflake was able to gain traction, demonstrate repeatability, and attract the capital necessary to scale to its vision. This chart shows the three layers of Snowflake's architecture that have been well-documented. The separation of compute and storage, and the outer layer of cloud services. But I want to call your attention to the bottom part of the chart, the so-called Cloud Agnostic Layer that Snowflake introduced in 2018. This layer is somewhat misunderstood. Not only did Snowflake make its Cloud-native database compatible to run on AWS than Azure in the 2020 GCP, what Snowflake has done is to obstruct cloud infrastructure complexity and create what it calls the data cloud. What's the data cloud? We don't believe the data cloud is just a marketing term that doesn't have any substance. Just as SAS is Simplified Application Software and iOS made it possible to eliminate the value drain associated with provisioning infrastructure, a data cloud, in concept, can simplify data access, and break down fragmentation and enable shared data across the globe. Snowflake, they have a first mover advantage in this space, and we see a number of fundamental aspects that comprise a data cloud. First, massive scale with virtually unlimited compute and storage resource that are enabled by the public cloud. We talk about this a lot. Second is a data or database architecture that's built to take advantage of native public cloud services. This is why Frank Slootman says, "We've burned the boats. We're not ever doing on-prem. We're all in on cloud and cloud native." Third is an obstruction layer that hides the complexity of infrastructure. and fourth is a governed and secured shared access system where any user in the system, if allowed, can get access to any data in the cloud. So a key enabler of the data cloud is this thing called the global data mesh. Now, earlier this year, Snowflake introduced its global data mesh. Over the course of its recent history, Snowflake has been building out its data cloud by creating data regions, strategically tapping key locations of AWS regions and then adding Azure and GCP. The complexity of the underlying cloud infrastructure has been stripped away to enable self-service, and any Snowflake user becomes part of this global mesh, independent of the cloud that they're on. Okay. So now, let's go back to what we were talking about earlier. Users in this mesh will be our domain owners. They're building monetizable services and products around data. They're most likely dealing with relatively small read only datasets. They can adjust data from any source very easily and quickly set up security and governance to enable data sharing across different parts of an organization, or, very importantly, an ecosystem. Access control and governance is automated. The data sets are addressable. The data owners have clearly defined missions and they own the data through the life cycle. Data that is specific and purposely shaped for their missions. Now, you're probably asking, "What happens to the technical team and the underlying infrastructure and the cluster it's in? How do I get the compute close to the data? And what about data sovereignty and the physical storage later, and the costs?" All these are good questions, and I'm not saying these are trivial. But the answer is these are implementation details that are pushed to a self-service layer managed by a group of engineers that serves the data owners. And as long as the domain expert/data owner is driving monetization, this piece of the puzzle becomes self-funding. As I said before, Snowflake has to help these users to optimize their spend with predictive tooling that aligns spend with value and shows ROI. While there may not be a strong motivation for Snowflake to do this, my belief is that they'd better get good at it or someone else will do it for them and steal their ideas. All right. Let me end with some ETR data to show you just how Snowflake is getting a foothold on the market. Followers of this program know that ETR uses a consistent methodology to go to its practitioner base, its buyer base each quarter and ask them a series of questions. They focus on the areas that the technology buyer is most familiar with, and they ask a series of questions to determine the spending momentum around a company within a specific domain. This chart shows one of my favorite examples. It shows data from the October ETR survey of 1,438 respondents. And it isolates on the data warehouse and database sector. I know I just got through telling you that the world is going to change and Snowflake's not a data warehouse vendor, but there's no construct today in the ETR dataset to cut a data cloud or globally distributed data mesh. So you're going to have to deal with this. What this chart shows is net score in the y-axis. That's a measure of spending velocity, and it's calculated by asking customers, "Are you spending more or less on a particular platform?" And then subtracting the lesses from the mores. It's more granular than that, but that's the basic concept. Now, on the x-axis is market share, which is ETR's measure of pervasiveness in the survey. You can see superimposed in the upper right-hand corner, a table that shows the net score and the shared N for each company. Now, shared N is the number of mentions in the dataset within, in this case, the data warehousing sector. Snowflake, once again, leads all players with a 75% net score. This is a very elevated number and is higher than that of all other players, including the big cloud companies. Now, we've been tracking this for a while, and Snowflake is holding firm on both dimensions. When Snowflake first hit the dataset, it was in the single digits along the horizontal axis and continues to creep to the right as it adds more customers. Now, here's another chart. I call it the wheel chart that breaks down the components of Snowflake's net score or spending momentum. The lime green is new adoption, the forest green is customers spending more than 5%, the gray is flat spend, the pink is declining by more than 5%, and the bright red is retiring the platform. So you can see the trend. It's all momentum for this company. Now, what Snowflake has done is they grabbed a hold of the market by simplifying data warehouse. But the strategic aspect of that is that it enables the data cloud leveraging the global mesh concept. And the company has introduced a data marketplace to facilitate data sharing across ecosystems. This is all about network effects. In the mid to late 1990s, as the internet was being built out, I worked at IDG with Bob Metcalfe, who was the publisher of InfoWorld. During that time, we'd go on speaking tours all over the world, and I would listen very carefully as he applied Metcalfe's law to the internet. Metcalfe's law states that the value of the network is proportional to the square of the number of connected nodes or users on that system. Said another way, while the cost of adding new nodes to a network scales linearly, the consequent value scores scales exponentially. Now, apply that to the data cloud. The marginal cost of adding a user is negligible, practically zero, but the value of being able to access any dataset in the cloud... Well, let me just say this. There's no limitation to the magnitude of the market. My prediction is that this idea of a global mesh will completely change the way leading companies structure their businesses and, particularly, their data architectures. It will be the technologists that serve domain specialists as it should be. Okay. Well, what do you think? DM me @dvellante or email me at david.vellante@siliconangle.com or comment on my LinkedIn? Remember, these episodes are all available as podcasts, so please subscribe wherever you listen. I publish weekly on wikibon.com and siliconangle.com, and don't forget to check out etr.plus for all the survey analysis. This is Dave Vellante for theCUBE Insights powered by ETR. Thanks for watching. Be well, and we'll see you next time. (upbeat music)

>> Okay, listen, we're gearing up for the start of the Snowflake Data Cloud Summit and we want to go back to the early roots of Snowflake. We got some of the founding engineers here, Abdul Muneer, Ashish Modivala, and Alison Lee. They're three individuals that were at Snowflake in the early years and participated in many of the technical decisions that led to the platform that is making Snowflake famous today. Folks, great to see you. Thanks so much for taking some time out of your busy schedules. >> Than you for having us. >> Same. >> Hey, it's got to be really gratifying to see this platform that you've built, you know, taking off and changing businesses. So, I'm sure it was always smooth sailing, right? There were no debates, were there ever? >> Never. >> Now, I've never seen an engineer get into a debate. (laughter) >> All right, so seriously though, so take us back to the early days, you guys, you know, choose whoever wants to start but, what was it like early on? We're talking 2013 here, right? >> That's right. >> When I think back to the early days of Snowflake, I just think of all of us sitting in one room at the time you know, we just had an office that was one room with you know, 12 or 13 engineers sitting there, clacking away at our keyboards, working really hard, churning out code, punctuated by, you know, somebody asking a question about, "Hey, what should we do about this? Or what should we do about that?" And then everyone kind of looking up from their keyboards and getting into discussions and debates about, about the work that we were doing. >> So Abdul, it was just kind of heads down, headphones on, just coding, or >> I think there was a lot of talking and followed by a lot of typing. And, and I think there were periods of time where, you know, anyone could just walk in into the office and probably out of the office and all they'd hear is probably people typing away at their keyboards. And one of my vivid, most vivid memories is is actually I used to sit right across from Alison and there's these huge two, two huge monitors monitors between us. And I would just hear her typing away at our keyboard. And sometimes I was thinking and and all that typing got me nervous because it seemed like Alison knew exactly what, what she needed to do, and I was just still thinking about it. >> So Ashish was this like bliss for you as a developer, an engineer, or was it, was it a stressful time? What was the mood? >> When you don't have a whole lot of customers there's a lot of bliss, but at the same time, there's a lot of pressure on us to make sure that we build the product. There was a timeline ahead of us, we knew we had to build this in a certain timeframe. So one thing I'll add to what Alison and Abdul said is we did a lot of white boarding as well. There were a lot of discussions and those discussions were a lot of fun. They actually cemented what we wanted to build. They made sure that everyone was in tune and there we have it. >> (Dave) Yeah, so, I mean, it is a really exciting time doing any startup. When you have to make decisions in development and variably you come to a fork in the road. So I'm curious as to what some of those forks might've been, how you guys decided, you know, which fork to take. Was there a Yoda in the room that served as the Jedi master? I mean, how are those decisions made? Maybe you could talk about that a little bit. >> Yeah. That's an interesting question. And I think one of, as I think back, one of the memories that, that sticks out in my mind is this epic meeting in one of our conference rooms called North star. And many of our conference rooms are named after ski resorts because the founders are really into skiing and that's why, that's where the Snowflake names comes from. So there was this epic meeting and and I'm not even sure exactly what topic we were discussing. I think it was, it was the signup flow and there were a few different options on the table. and one of the options that, that people were gravitating to one of the founders didn't like it. And they said a few times that there's this makes no sense, there's no other system in the world that does it this way. And I think one of the other founders said that's exactly why we should do it this way. And, or at least seriously considered this option. So I think there was always this this tendency and this impulse that that we needed to think big and think differently and not see the world the way it is but the, the way we wanted it to be and then work our way backwards and try to make it happen. >> Alison, any fork in the road moments that you remember? >> Well, I'm just thinking back to a really early meeting with Ashish and a few of our founders where we were debating something, probably not super exciting to a lot of people outside of hardcore database people which was how to represent our column metadata. And I think it's funny that you, that you mentioned Yoda because we often make jokes about one of our founders Terry and referred to him as Yoda, because he has this tendency to say very concise things that kind of make you scratch your head and say, "Wow why didn't I think of that?" Or, you know, what exactly does that mean? I never thought about it that way. So I think when I think of the Yoda in the room, it was definitely Terry. >> Ashish, anything you can add to this conversation? >> I'll agree with Alison on the Yoda comment, for sure. Another big fork in the road I recall was when we changed one of our meta store where we store our on internal metadata. We used to use a tool called MySQL and we changed it to another database called FoundationDB, I think that was a big game changer for us. And, you know, it was a tough decision, it took us a long time. For the longest time we even had our own little branch it was called FoundationDB and everybody who was developing on that branch. It's a little embarrassing, but, you know, those are the kinds of decisions that alter the shape of Snowflake. >> Yeah, I mean, these are really, you know, down in the weeds hardcore stuff that a lot of people might not be exposed to. What would you say was the least obvious technical decision that you had to make at the time? And I want to ask you about the most obvious too, but what was the one that was so out of the box? I mean, you kind of maybe mentioned it a little bit before but I wonder if we could double click on that? >> Well, I think one of the core decisions in our architecture is the separation of compute and storage. And, you know, that is really core to our architecture, and there are so many features that we have today for instance, data sharing, zero copy cloning, that we couldn't have without that architecture. And I think it was both not obvious, and when we told people about it in the early days there was definitely skepticism about being able to make that work and being able to have that architecture and still get great performance. >> Exactly. >> Yeah. Anything that was like clearly obvious that maybe that, maybe that was the least and the most that, that separation from compute and store, because it allowed you to actually take advantage of Cloud native. But was there an obvious one that you know, is it sort of dogma that you, you know philosophically live by, you know, to this day? >> I think one really obvious thing is the sort of no tuning, no knobs, ease of use story behind Snowflake. And I say, it's really obvious because everybody wants their system to be easy to use. But then I would say there were tons of decisions behind that, that it's not always obvious, the implications, of such a choice, right? And really sticking to that. And I think that that's really like a core principle behind Snowflake, that led to a lot of non-obvious decisions as a result of sticking to that principle. >> So >> I think, to add to that, now you've grabbed us thinking. I think another really interesting one was really, should we start from scratch or should we use something that already exists and build on top of that? And I think that was one of these almost philosophical kind of stances that we took, that a lot of the systems that were out there were the way they were, because, because they weren't built for the, for the platforms that they were running on. And the big thing that we were targeting was the Cloud. And so one of the big stances we took was that we were going to build from scratch. And we weren't going to borrow a single line of code from many other database out there. And this was something that really shocked a lot of people and many times that this was pretty crazy, and it was, but this is how you build great products. >> That's awesome. All right Ashish, I should give you the last word. We got like just like 30 seconds left, bring us home. >> Till date, actually one of those said shocks people when you talk to them and they say, "Wow, you are naturally using any other database, and you build this entirely yourself." The number of people who actually can build a database from scratch are fairly limited, the group is fairly small. And so it was really a humongous task, and as you've mentioned, you know, it really changed the direction of how we designed a database. What we, what does the database really mean to us, right? The way Snowflake has built a database, it's really a number of organs that come together and form the body. And that's also a concept that's novel to the database industry. >> Guys, congratulations, you must be so proud and it's going to be awesome watching the next decade. So thank you so much for sharing your stories. >> Thanks too. >> Thank you. >> Thank you.

>> Hello everyone, we're here at the Data Cloud Summit, and we have a real treat for you. I call it the CMO Power Panel. And we're going to explore how data is transforming marketing, branding and promotion. And with me are three phenomenal marketing pros and chief marketing officers. Denise Persson is the CMO of Snowflake, Scott Holden of ThoughtSpot and Laura Langdon of Wipro. Folks, great to see you. Thanks so much for coming on "theCUBE." >> Great to be here with you David. >> Awesome, Denise, let's start with you. I want to talk about the role and the changing role of the CMOs, has changed a lot, you know, I suppose of course with all this data, but I wonder what you're experiencing and can you share with us why marketing especially is being impacted by data. >> Well data's really what has helped turn us marketers into revenue drivers, into call centers. And it's clearly a much better place to be. What I'm personally most excited about is the real time access we have to data today. In the past, I used to get a stale report a few weeks after a marketing program was over and at that time we couldn't make any changes to the investments we'd already made. Today, we get data in the midst of running a program. So it can reallocate investments at the time a program is up and running and that's really profound. Today as well, I would say that adaptability has truly become the true superpowers of marketing today and data is really what enables us to adapt to scale. We can adapt to customer's behavior and preferences at scale and that's truly a profound new way of working as well. >> That's interesting what you say cause you know, in tough times used to be okay, sales and engineering, put a brick wall around those and you know, you name it marketing, say, "Okay, cut." But now it's like, you go to marketing and say, "Okay, what's the data say, "how do we have to pivot?" And Scott, I wonder what have data and cloud really brought to the modern marketer that you might not have had before through to this modern era? >> Well, this era, I don't think there's ever been a better time to be a marketer than there is right now. And the primary reason is that we have access to data and insights like we've never had before and I'm not exaggerating when I say that I have a hundred times more access to data than I had a decade ago. It's just phenomenal. When you look at the power of cloud, search, AI, these new consumer experiences for analytics, we can do things in seconds that used to take days. And so it's become in us, as Denise said a super power for us to have access to so much data. And it's, you know, COVID has been hard. A lot of our marketing teams who never worked harder making this pivot from the physical world to the virtual world but they're, you know, at least we're working. And the other part of it is that digital has just created this phenomenal opportunity for us because the beauty of digital and digital transformation is that everything now is trackable, which makes it measurable and means that we can actually get insights that we can act on in a smarter way. And you know, it's worth giving an example. If you just look at this show, right? Like this event that we're viewing. In a physical world, all of you watching at home you'd be in front of us in a room and we'd be able to know if you're in the room, right? We'd track to the scanners when you walked in but that's basically it. At that point, we don't really get a good sense for how much you like, what we're saying. You know, maybe you filled out a survey, but only five to 10% of people ever do that. In a digital world, we know how long you stick around. And as a result, like it's easy, people can just with a click, you know, change the channel. And so the bar for content has gone way up as we do these events but we know how long people are sticking around. And that's, what's so special about it. You know, Denise and her team, as the host of this show they're going to know how long people watch this segment. And that knowing is powerful. I mean, it's simple as you know, using a product like ThoughtSpot, you could just ask a question, you know, how many, you know, what's the average view time by session and Bloomer chart pops up. You're going to know what's working and what's not. And that's something that you can take and act on in the future. And that's what our customers are doing. So, you know, Snowflake and ThoughtSpot, we share our customer with Hulu and they're tracking programs. So, what people are watching at home, how long they're watching, what they're watching next. And they're able to do that in a super granular way and improve their content as a result. And that's the power of this new world we live in that's made the cloud and data so accessible to folks like us. >> Well, thank you for that. And I want to come back to that notion and understand how you're bringing data into your marketing ops, but I want to bring Laura in. Laura, Wipro, you guys partner with a lot of brands, a lot of companies around the world. I mean, thousands of partners, obviously Snowflake in ThoughtSpot or two. How are you using data to optimize these co-marketing relationships? You know, specifically, what what are the trends that you're seeing around things like customer experience? >> So, you know, we use data for all of our marketing decisions, our own, as well as with our partners. And I think what's really been interesting about partner marketing data is we can feed that back to our sales team, right? So, it's very directional for them as well and their efforts moving forward. So, I think that's a place where specifically to partners, it's really powerful. We can also use our collected data to go out to customers to better effect. And then you know, regarding these trends, we just did a survey on the state of the intelligent enterprise. We interviewed 300 companies, US and UK, and there were three interesting I thought statistics relevant to this. Only 22% of the companies that we interviewed felt that their marketing was where it needed to be from an automation standpoint. So lots of room for us to grow, right? Lots of space for us to play. And 61% of them believe that it was critical that they implement this technology to become a more intelligent enterprise. But when they ranked on readiness by function, marketing came in six, right? So HR, RND, finance were all ahead of marketing followed by sales. You know, and then the final data point that I think was interesting was 40% of those agreed that the technology was the most important thing, that thought leadership was critical. You know, and I think that's where marketers really can bring our tried and true experience to bear and merge it with this technology. >> Great, thank you. So, Denise, I've been getting the Kool-Aid injection this week around Data Cloud. I've been pushing people but now that I have the CMO in front of me, I want to ask about the Data Cloud and what it means specifically for the customers and what are some of the learnings maybe that you've experienced that can support some of the things that that Laura and Scott were just discussing. >> Yeah, as Scott said before, idea of a hundred times more data than he ever has before. And that's again, if you look at all the companies we talked to around the world it's not about the amount of data that they have that is the problem, it's the ability to access that data. That data for most companies is trapped across silos, across the organization. It sits in data applications, systems or records. Some of that data sits with your partners that you want to access. And that's really what the data cloud comes in. Data cloud is really mobilizing that data for you. It brings all that data together for you in one place. So you can finally access that data and really provide ubiquitous access to that data to everyone in your organization that needs it and can truly unlock the value of that data. And from a marketing perspective, I mean, we are responsible for the customer experience you know, we provide to our customers and if you have access to all the data on your customers, that's when you have that to customer 360, that we've all been talking about for so many years. And if you have all that data, you can truly, you know, look at their, you know, buying behaviors, put all those dots together and create those exceptional customer experiences. You can do things such as the retailers do in terms of personal decision, for instance, right? And those are the types of experiences, you know, our customers are expecting today. They are expecting a 100% personalized experience for them you know, all the time. And if you don't have all the data, you can't really put those experiences together at scale. And that is really where the data cloud comes in. Again, the data cloud is not only about mobilizing your own data within your enterprise. It's also about having access to data from your partners or extending access to your own data in a secure way to your partners within your ecosystems. >> Yeah, so I'm glad you mentioned a couple of things. I've been writing about this a lot and in particularly the 360 that we were dying for, but haven't really been able to tap. I didn't call it the data cloud, I don't have a marketing gene. I had another sort of boring name for it, but I think there's similar vectors there. So I appreciate that. Scott, I want to come back to this notion of building data DNA in your marketing, you know, fluency and how you put data at the core of your marketing ops. I've been working with a lot of folks in banking and manufacturing and other industries that are that are struggling to do this. How are you doing it? What are some of the challenges that you can share and maybe some advice for your peers out there? >> Yeah, sure, you brought up this concept of data fluency and it's an important one. And there's been a lot of talk in the industry about data literacy and being able to read data. But I think it's more important to be able to speak data, to be fluent and as marketers, we're all storytellers. And when you combine data with storytelling, magic happens. And so, getting a data fluency is a great goal for us to have for all of the people in our companies. And to get to that end, I think one of the things that's happening is that people are hiring wrong and they're thinking about it, they're making some mistakes. And so a couple of things come to mind especially when I look at marketing teams that I'm familiar with. They're hiring a lot of data analysts and data scientists and those folks are amazing and every team needs them. But if you go too big on that, you do yourself a disservice. The second key thing is that you're basically giving your frontline folks, your marketing managers or people on the front lines, an excuse not to get involved with data. And then that's a big mistake because it used to be really hard. But with the technologies available to us now, these new consumer like experiences for data analytics, anybody can do it. And so we as leaders have to encourage them to do it. And I'll give you just a you know, an example, you know, I've got about 32 people on my marketing team and I don't have any data analysts on my team. Across our entire company, we have a couple of analysts and a couple of data engineers. And what's happening is the world is changing where those folks, they're enablers, they architect the system. They bring in the different data sources. They use technologies like Snowflake as being so great at making it easier for people to pull spectrum technology together and to get access to data out of it quickly, but they're pulling it together and then simple things like, "Hey I just want to see this "weekly instead of monthly." You don't need to waste your expensive data science talent. You know, Gardener puts a stat out there that 50% of data scientists are doing basic visualization work. That's not a good use of their time. The products are easy enough now that everyday marketing managers can do that. And when you have a marketing manager come to you and say, you know, "I just figured out "this campaign which looks great on the surface "is doing poorly from an ROI perspective. That's a magic moment. And so we all need to coach our teams to get there. And I would say, you know, lead by example, give them an opportunity to access data and turn it into a story, that's really powerful. And then lastly, praise people who do it, like, use it as something to celebrate inside our companies is a great way to kind of get this initiative. >> I love it. And talking about democratizing data and making it self service, people feel ownership. You know, Laura, Denise was talking about the ecosystem and you're kind of the ecosystem pro here. How does the ecosystem help marketers succeed? Maybe you can talk about the power of many versus the resource of one. >> Sure, you know, I think it's a game changer and it will continue to be. And I think it's really the next level for marketers to harness this power that's out there and use it, you know, and it's something that's important to us, but it's also something we're starting to see our customers demand. You know, we went from a one size fits all solution to they want to bring the best in class to their organization. We all need to be really agile and flexible right now. And I think this ecosystem allows that, you know, you think about the power of Snowflake, Snowflake mining data for you and then a ThoughtSpot really giving you the dashboard to have what you want. And then an implementation partner like a Wipro coming in, and really being able to plug in whatever else you need to deliver. And I think it's really super powerful and I think it gives us you know, it just gives us so much to play with and so much room to grow as marketers. >> Thank you, Denise, why don't you bring us home. We're almost out of time here, but marketing, art, science, both? What are your thoughts? >> Definitely both, I think that's the exciting part about marketing. It is a balancing act between art and science. Clearly, it's probably more science today than it used to be but the art part is really about inspiring change. It's about changing people's behavior and challenging the status quo, right? That's the art part. The science part, that's about making the right decisions all the time, right? It's making sure we are truly investing in what's going to drive revenue for us. >> Guys, thanks so much for coming on "theCUBE." Great discussion, I really appreciate it. Okay, and thank you for watching. Keep it right there. Wall-to-wall coverage of the Snowflake Data Cloud Summit on "theCUBE."

>> Hello everyone, and welcome back to our wall-to-wall coverage of the Datacloud summit, this is Dave Vellante, and we're seeing the emergence of a next generation workload in the cloud, more facile access, and governed sharing of data is accelerating time to insights and action. Alright, allow me to introduce our next guest. Aimee Irwin is here, she's the vice president of strategy for Experian, and Matt Glickman is VP of customer product strategy at Snowflake, with an emphasis on financial services, folks, welcome to theCUBE, thanks so much for coming on. >> Thanks Dave, nice to be here. >> Hey so Aimee, obviously 2020's been pretty unique and crazy and challenging time for a lot of people, I don't know why, I've been checking my credit score a lot more for some reason on the app, I love the app, I had to lock it the other day, I locked my credit, somebody tried to do, and it worked, I was so happy, so thank you for that. So, we know Experian, but there's a ton of data behind what you do, I wonder if you could share kind of where you sit in the data space, and how you've seen organizations leverage data up to this point, and really if you could address some of the changes you're seeing as a result of the pandemic, that would be great. >> Sure, sure. Well, as you mentioned, Experian is best known as a credit bureau. I work in our marketing services business unit, and what we do is we really help brands leverage the power of data and technology to make the right marketing decisions, and better understand and connect with consumers. So we offer marketers products around data, identity, activation, measurement, we have a consumer-view data file that's based on offline PII and contains demographic interest, transaction data, and other attributes on about 300 million people in the US. And on the identity side we've always been known for our safe haven, or privacy-friendly matching, that allows marketers to connect their first party data to Experian or other third parties, but in today's world, with the growth in importance of digital advertising, and consumer behavior shifting to digital, Experian also is working to connect that offline data to the digital world, for a complete view of the customer. You mentioned COVID, we actually, we serve many different verticals, and what we're seeing from our clients during COVID is that there's a varying impact of the pandemic. The common theme is that those who have successfully pivoted their businesses to digital are doing much better, as we all know, COVID accelerated very strong trends to digital, both in e-commerce and in media-viewing habits. We work with a lot of retailers, retail is a tale of two cities, with big box and grocery growing, and apparel retail really struggling. We've helped our clients, leveraging our data to better understand the shifts in these consumer behaviors, and better psych-map their customers during this really challenging time. So think about, there's a group of customers that is still staying home, that is sheltered in place, there's a group of customers starting to significantly vary their consumer behavior, but is starting to venture out a little, and then there's a group of customers that's doing largely what they did before, in a somewhat modified fashion, so we're helping our clients segment those customers into groups to try and understand the right messaging and right offers for each of those groups, and we're also helping them with at-risk audiences. So that's more on the financial side, which of your customers are really struggling due to the pandemic, and how do you respond. >> That's awesome, thank you. You know, it's funny, I saw a twitter poll today asking if we measure our screen time, and I said, "oh my, no." So, Matt, let me ask you, you spent a ton of time in financial services, you really kind of cut your teeth there, and it's always been very data-oriented, you're seeing a lot of changes, tell us about how your customers are bringing it together, data, the skills, the people, obviously a big part of the equation, and applications to really put data at the center of the universe, what's new and different that these companies are getting out of the investments in data and skills? >> That's a great question, the acceleration that Aimee mentioned is real. We're seeing, particularly this year, but I think even in the past few years, the reluctance of customers to embrace the cloud is behind us, and now there's this massive acceleration to be able to go faster, and in some ways, the new entrants into this category have an advantage versus the companies that have been in this space, whether it's financial services or beyond, and in a lot of ways, they all are seeing the cloud and services like Snowflake as a way to not only catch up, but leapfrog your competitors, and really deliver a differentiated experience to your customers, to your business, internally or externally. And this past, however long this crisis has been going on, has really only accelerated that, because now there's a new demand to understand your customer better, your business better, with your traditional data sources, and also new, alternative data sources, and also being able to take a pulse. One of the things that we learned, which was an eye-opening experience, was as the crisis unfolded, one of our data partners decided to take the datasets about where the cases were happening from the Johns Hopkins, and World Health Organization, and put that on our platform, and it became a runaway hit. Thousands of our customers overnight were using this data to understand how their business was doing, versus how the crisis was unfolding in real time. And this has been a game-changer, and it's only scratching the surface of what now the world will be able to do when data is really at their fingertips, and you're not hindered by your legacy platforms. >> I wrote about that back in the early days of the pandemic when you guys did that, and talked about some of the changes that you guys enabled, and you know, you're right about cloud, in financial services cloud used to be an evil word, and now it's almost, it's become a mandate. Aimee, I wonder if you could tell us a little bit more about what your customers are having to work through in order to achieve some of these outcomes. I mean, you know, I'm interested in the starting point, I've been talking a lot, and writing a lot, and talking to practitioners about what I call the data life cycle, sometimes people call it the data pipeline, it's a complicated matter, but those customers and companies that can put data at the center and really treat that pipeline as the heart of their organization, if you will, are really succeeding. What are you seeing, and what really is the starting point, there? >> Yes, yeah, that's a good question, and as you mentioned, first party, I mean we start with first party data, right? First party data is critical to understanding consumers. And different verticals, different companies, different brands have varying levels of first party data. So a retailers going to have a lot more first party data, a financial services company, than say, an auto manufacturer. And while many marketers have that first party data, to really have a 360 view of the customer, they need third party data as well, and that's where Experian comes in, we help brands connect those disparate datasets, both first and third party data to better understand consumers, and create a single customer view, which has a number of applications. I think the last stat I heard was that there's about eight devices, on average, per person. I always joke that we're going to have these enormous, and that number's growing, we're going to have these enormous charging stations in our house, and I think we already do, because of all the different devices. And we seamlessly move from device to device, along our customer journey, and, if the brand doesn't understand who we are, it's much harder for the brand to connect with consumers and create a positive customer experience. And we cite that about 95 percent of companies, they are looking to achieve that single customer view, they recognize that they need that, and they've aligned various teams from e-commerce, to marketing, to sales, to at a minimum adjust their first party data, and then connect that data to better understand consumers. So, consumers can interact with a brand through a website, a mobile app, in-store visits, you know, by the phone, TV ads, et cetera, and a brand needs to use all of those touchpoints, often collected by different parts of the organization, and then add in that third party data to really understand the consumers. In terms of specific use cases, there's about three that come to mind. So first there's relevant advertising, and reaching the right customer, there's measurement, so being able to evaluate your advertising efforts, if you see an ad on, if I see an ad on my mobile, and then I buy by visiting a desktop website, understanding, or I get a direct mail piece, understanding that those interactions are all connected to the same person is critical for measurement. And then there's personalization, which includes improved customer experience amongst your own touchpoints with that consumer, personalized marketing communication, and then of course analytics, so those are the use cases we're seeing. >> Great, thank you Aimee. Now Matt, you can't really talk about data without talking about governance and compliance, and I remember back in 2006, when the federal rules of civil procedure went in, it was easy, the lawyers just said, "no, nobody can have access," but that's changed, and one of the things I like about what Snowflake's doing with the data cloud is it's really about democratizing access, but doing so in a way that gives people confidence that they only have access to the right data. So maybe you could talk a little bit about how you're thinking about this topic, what you're doing to help customers navigate, which has traditionally been such a really challenging problem. >> Another great question, this is where I think the major disruption is happening. And what Aimee described, being able to join together first and third party datasets, being able to do this was always a challenge, because data had to be moved around, I had to ship my first party data to the other side, and the third party data had to be shipped to me, and being able to join those datasets together was problematic at best, and now with the focus on privacy and protecting PII, this is something that has to change, and the good news is, with the data cloud, data does not have to move. Data can stay where it belongs, Experian can keep its data, Experian's customers can hold onto their data, yet the data can be joined together on this universal, global platform that we call the data cloud. On top of that, and particularly with the regulations that are coming out that are going to prevent data from being collected on either a mobile device or as cookies on web browsers, new approaches, and we're seeing this a lot in our space, both in financials and media, is to set up these data clean rooms, where both sides can give access to one another, but not have to reveal any PII to do that join. This is going to be huge, now you actually can protect your customers' and your consumers' private identities, but still accomplish that join that Aimee mentioned, to be able to relate the cause and effect of these campaigns, and really understand the signals that these datasets are trying to say about one another, again without having to move data, without having to reveal PII, we're seeing this happening now, this is the next big thing, that we're going to see explode over the months and years to come. >> I totally agree, massive changes coming in public policy in this area, and we only have a few minutes left, and I wonder if for our audience members that are looking for some advice, what's the, Aimee, what's the one thing you'd recommend they start doing differently, or consider putting in place that's going to set them up for success over the next decade? >> Yeah, that's a good question. You know, I think, I always say, first, harness all of your first party data across all touchpoints, get that first party data in one place and working together, second, connect that data with trusted third parties, and Matt suggested some ways to do that, and then third, always put the customer first, speak their language, where and when they want to be reached out to, and use the information you have to really create a better customer experience for your customers. >> Matt, what would you add to that? Bring us home, if you would. >> Applications. The idea that data, your data can now be pulled into your own business applications the same way that Netflix and Spotify are pulled into your consumer and lifestyle applications, again, without data moving, these personalized application experiences is what I encourage everyone to be thinking about from first principles. What would you do in your next app that you're going to build, if you had all your consumers, if the consumers had access to their data in the app, and not having to think about things from scratch, leverage the data cloud, leverage these service providers like Experian, and build the applications of tomorrow. >> I'm super excited when I talk to practitioners like yourselves, about the future of data, guys, thanks so much for coming on theCUBE, it was a really a pleasure having you, and I hope we can continue this conversation in the future. >> Thank you. >> Thanks. >> Alright, thank you for watching, keep it right there, we got great content, and tons of content coming at the Snowflake data cloud summit, this is Dave Vellante for theCUBE, keep it right there.

>> My name is Dave Vellante. And with me are two world-class technologists, visionaries and entrepreneurs. Benoit Dageville, he co-founded Snowflake and he's now the President of the Product Division, and Florian Douetteau is the Co-founder and CEO of Dataiku. Gentlemen, welcome to the cube to first timers, love it. >> Yup, great to be here. >> Now Florian you and Benoit, you have a number of customers in common, and I've said many times on theCUBE, that the first era of cloud was really about infrastructure, making it more agile, taking out costs. And the next generation of innovation, is really coming from the application of machine intelligence to data with the cloud, is really the scale platform. So is that premise relevant to you, do you buy that? And why do you think Snowflake, and Dataiku make a good match for customers? >> I think that because it's our values that aligned, when it gets all about actually today, and knowing complexity of our customers, so you close the gap. Where we need to commoditize the access to data, the access to technology, it's not only about data. Data is important, but it's also about the impacts of data. How can you make the best out of data as fast as possible, as easily as possible, within an organization. And another value is about just the openness of the platform, building a future together. Having a platform that is not just about the platform, but also for the ecosystem of partners around it, bringing the level of accessibility, and flexibility you need for the 10 years of that. >> Yeah, so that's key, that it's not just data. It's turning data into insights. Now Benoit, you came out of the world of very powerful, but highly complex databases. And we know we all know that you and the Snowflake team, you get very high marks for really radically simplifying customers' lives. But can you talk specifically about the types of challenges that your customers are using Snowflake to solve? >> Yeah, so the challenge before snowflake, I would say, was really to put all the data in one place, and run all the computes, all the workloads that you wanted to run against that data. And of course existing legacy platforms were not able to support that level of concurrency, many workload, we talk about machine learning, data science, data engineering, data warehouse, big data workloads, all running in one place didn't make sense at all. And therefore be what customers did this to create silos, silos of data everywhere, with different system, having a subset of the data. And of course now, you cannot analyze this data in one place. So Snowflake, we really solved that problem by creating a single architecture where you can put all the data into cloud. So it's a really cloud native. We really thought about how solve that problem, how to create, leverage cloud, and the elasticity of cloud to really put all the data in one place. But at the same time, not run all workload at the same place. So each workload that runs in Snowflake, at its dedicated compute resources to run. And that makes it agile, right? Florian talked about data scientist having to run analysis, so they need a lot of compute resources, but only for a few hours. And with Snowflake, they can run these new workload, add this workload to the system, get the compute resources that they need to run this workload. And then when it's over, they can shut down their system, it will automatically shut down. Therefore they would not pay for the resources that they don't use. So it's a very agile system, where you can do this analysis when you need, and you have all the power to run all these workload at the same time. >> Well, it's profound what you guys built. I mean to me, I mean of course everybody's trying to copy it now, it was like, I remember that bringing the notion of bringing compute to the data, in the Hadoop days. And I think that, as I say, everybody is sort of following your suit now or trying to. Florian, I got to say the first data scientist I ever interviewed on theCUBE, it was the amazing Hillary Mason, right after she started at Bitly, and she made data sciences sounds so compelling, but data science is a hard. So same question for you, what do you see as the biggest challenges for customers that they're facing with data science? >> The biggest challenge from my perspective, is that once you solve the issue of the data silo, with Snowflake, you don't want to bring another silo, which will be a silo of skills. And essentially, thanks to the talent gap, between the talent available to the markets, or are released to actually find recruits, train data scientists, and what needs to be done. And so you need actually to simplify the access to technologies such as, every organization can make it, whatever the talent, by bridging that gap. And to get there, there's a need of actually backing up the silos. Having a collaborative approach, where technologies and business work together, and actually all puts up their ends into those data projects together. >> It makes sense, Florain let's stay with you for a minute, if I can. Your observation space, it's pretty, pretty global. And so you have a unique perspective on how can companies around the world might be using data, and data science. Are you seeing any trends, maybe differences between regions, or maybe within different industries? What are you seeing? >> Yeah, definitely I do see trends that are not geographic, that much, but much more in terms of maturity of certain industries and certain sectors. Which are, that certain industries invested a lot, in terms of data, data access, ability to store data. As well as experience, and know region level of maturity, where they can invest more, and get to the next steps. And it's really relying on the ability of certain leaders, certain organizations, actually, to have built these long-term data strategy, a few years ago when no stats reaping of the benefits. >> A decade ago, Florian, Hal Varian famously said that the sexy job in the next 10 years will be statisticians. And then everybody sort of changed that to data scientist. And then everybody, all the statisticians became data scientists, and they got a raise. But data science requires more than just statistics acumen. What skills do you see as critical for the next generation of data science? >> Yeah, it's a great question because I think the first generation of data scientists, became data scientists because they could have done some Python quickly, and be flexible. And I think that the skills of the next generation of data scientists will definitely be different. It will be, first of all, being able to speak the language of the business, meaning how you translates data insight, predictive modeling, all of this into actionable insights of business impact. And it would be about how you collaborate with the rest of the business. It's not just how fast you can build something, how fast you can do a notebook in Python, or do predictive models of some sorts. It's about how you actually build this bridge with the business, and obviously those things are important, but we also must be cognizant of the fact that technology will evolve in the future. There will be new tools, new technologies, and they will still need to keep this level of flexibility to understand quickly what are the next tools they need to use a new languages, or whatever to get there. >> As you look back on 2020, what are you thinking? What are you telling people as we head into next year? >> Yeah, I think it's very interesting, right? This crises has told us that the world really can change from one day to the next. And this has dramatic and perform the aspects. For example companies all of a sudden, show their revenue line dropping, and they had to do less with data. And some other companies was the reverse, right? All of a sudden, they were online like Instacart, for example, and their business completely changed from one day to the other. So this agility of adjusting the resources that you have to do the task, and need that can change, using solution like Snowflake really helps that. Then we saw both in our customers. Some customers from one day to the next, were growing like big time, because they benefited from COVID, and their business benefited. But others had to drop. And what is nice with cloud, it allows you to adjust compute resources to your business needs, and really address it in house. The other aspect is understanding what happening, right? You need to analyze. We saw all our customers basically, wanted to understand what is the going to be the impact on my business? How can I adapt? How can I adjust? And for that, they needed to analyze data. And of course, a lot of data which are not necessarily data about their business, but also they are from the outside. For example, COVID data, where is the States, what is the impact, geographic impact on COVID, the time. And access to this data is critical. So this is the premise of the data cloud, right? Having one single place, where you can put all the data of the world. So our customer obviously then, started to consume the COVID data from that our data marketplace. And we had delete already thousand customers looking at this data, analyzing these data, and to make good decisions. So this agility and this, adapting from one hour to the next is really critical. And that goes with data, with cloud, with interesting resources, and that doesn't exist on premise. So indeed I think the lesson learned is we are living in a world, which is changing all the time, and we have to understand it. We have to adjust, and that's why cloud some ways is great. >> Excellent thank you. In theCUBE we like to talk about disruption, of course, who doesn't? And also, I mean, you look at AI, and the impact that it's beginning to have, and kind of pre-COVID. You look at some of the industries that were getting disrupted by, everyone talks about digital transformation. And you had on the one end of the spectrum, industries like publishing, which are highly disrupted, or taxis. And you can say, okay, well that's Bits versus Adam, the old Negroponte thing. But then the flip side of, you say look at financial services that hadn't been dramatically disrupted, certainly healthcare, which is ripe for disruption, defense. So there a number of industries that really hadn't leaned into digital transformation, if it ain't broke, don't fix it. Not on my watch. There was this complacency. And then of course COVID broke everything. So Florian I wonder if you could comment, what industry or industries do you think are going to be most impacted by data science, and what I call machine intelligence, or AI, in the coming years and decade? >> Honestly, I think it's all of them, or at least most of them, because for some industries, the impact is very visible, because we have talking about brand new products, drones, flying cars, or whatever that are very visible for us. But for others, we are talking about a part from changes in the way you operate as an organization. Even if financial industry itself doesn't seem to be so impacted, when you look at it from the consumer side, or the outside insights in Germany, it's probably impacted just because the way you use data (mumbles) for flexibility you need. Is there kind of the cost gain you can get by leveraging the latest technologies, is just the numbers. And so it's will actually comes from the industry that also. And overall, I think that 2020, is a year where, from the perspective of AI and analytics, we understood this idea of maturity and resilience, maturity meaning that when you've got to crisis you actually need data and AI more than before, you need to actually call the people from data in the room to take better decisions, and look for one and a backlog. And I think that's a very important learning from 2020, that will tell things about 2021. And the resilience, it's like, data analytics today is a function transforming every industries, and is so important that it's something that needs to work. So the infrastructure needs to work, the infrastructure needs to be super resilient, so probably not on prem or not fully on prem, at some point. And the kind of resilience where you need to be able to blend for literally anything, like no hypothesis in terms of BLOs, can be taken for granted. And that's something that is new, and which is just signaling that we are just getting to a next step for data analytics. >> I wonder Benoir if you have anything to add to that. I mean, I often wonder, when are machines going to be able to make better diagnoses than doctors, some people say already. Will the financial services, traditional banks lose control of payment systems? What's going to happen to big retail stores? I mean, maybe bring us home with maybe some of your finals thoughts. >> Yeah, I would say I don't see that as a negative, right? The human being will always be involved very closely, but then the machine, and the data can really help, see correlation in the data that would be impossible for human being alone to discover. So I think it's going to be a compliment not a replacement. And everything that has made us faster, doesn't mean that we have less work to do. It means that we can do more. And we have so much to do, that I will not be worried about the effect of being more efficient, and bare at our work. And indeed, I fundamentally think that data, processing of images, and doing AI on these images, and discovering patterns, and potentially flagging disease way earlier than it was possible. It is going to have a huge impact in health care. And as Florian was saying, every industry is going to be impacted by that technology. So, yeah, I'm very optimistic. >> Great, guys, I wish we had more time. I've got to leave it there, but so thanks so much for coming on theCUBE. It was really a pleasure having you.

>> Hi and welcome to Data Cloud catalyst Women in Tech Round Table Panel discussion. I am so excited to have three fantastic female executives with me today, who have been driving transformations through data throughout their entire career. With me today is Lisa Davis, SVP and CIO OF Blue shield of California. We also have Nishita Henry who is the Chief Innovation Officer at Deloitte and Teresa Briggs who is on a variety of board of directors including our very own Snowflake. Welcome ladies. >> Thank you. >> So I am just going to dive right in, you all have really amazing careers and resumes behind you, am really curious throughout your career, how have you seen the use of data evolve throughout your career and Lisa am going to start with you. >> Thank you, having been in technology my entire career, technology and data has really evolved from being the province of a few in an organization to frankly being critical to everyone's business outcomes. Now every business leader really needs to embrace data analytics and technology. We've been talking about digital transformation, probably the last five, seven years, we've all talked about, disrupt or be disrupted, At the core of that digital transformation is the use of data. Data and analytics that we derive insights from and actually improve our decision making by driving a differentiated experience and capability into market. So data has involved as being I would say almost tactical, in some sense over my technology career to really being a strategic asset of what we leverage personally in our own careers, but also what we must leverage as companies to drive a differentiated capability to experience and remain relative in the market today. >> Nishita curious your take on, how you have seen data evolve? >> Yeah, I agree with Lisa, it has definitely become a the lifeblood of every business, right? It used to be that there were a few companies in the business of technology, every business is now a technology business. Every business is a data business, it is the way that they go to market, shape the market and serve their clients. Whether you're in construction, whether you're in retail, whether you're in healthcare doesn't matter, right? Data is necessary for every business to survive and thrive. And I remember at the beginning of my career, data was always important, but it was about storing data, it was about giving people individual reports, it was about supplying that data to one person or one business unit in silos. And it then evolved right over the course of time into integrating data into saying, alright, how does one piece of data correlate to the other and how can I get insights out of that data? Now, its gone to the point of how do I use that data to predict the future? How do I use that data to automate the future? How do I use that data not just for humans to make decisions, but for other machines to make decisions, right? Which is a big leap and a big change in how we use data, how we analyze data and how we use it for insights and involving our businesses. >> Yeah its really changed so tremendously just in the past five years, its amazing. So Teresa we've talked a lot about the Data Cloud, where do you think we are heading with that and also how can future leaders really guide their careers in data especially in those jobs where we don't traditionally think of them in the data science space? Teresa your thoughts on that. >> Yeah, well since I'm on the Snowflake Board, I'll talk a little bit about the Snowflake Data Cloud, we're getting your company's data out of the silos that exist all over your organization. We're bringing third party data in to combine with your own data and we're wrapping a governance structure around it and feeding it out to your employees so they can get their jobs done, as simple as that. I think we've all seen the pandemic accelerate the digitization of our work. And if you ever doubted that the future of work is here, it is here and companies are scrambling to catch up by providing the right amount of data, collaboration tools, workflow tools for their workers to get their jobs done. Now, it used to be as prior people have mentioned that in order to work with data you had to be a data scientist, but I was an auditor back in the day we used to work on 16 column spreadsheets. And now if you're an accounting major coming out of college joining an auditing firm, you have to be tech and data savvy because you're going to be extracting, manipulating, analyzing and auditing data, that massive amounts of data that sit in your clients IT systems. I'm on the board of Warby Parker, and you might think that their most valuable asset is their amazing frame collection, but it's actually their data, their 360 degree view of the customer. And so if you're a merchant, or you're in strategy, or marketing or talent or the Co-CEO, you're using data every day in your work. And so I think it's going to become a ubiquitous skill that any anyone who's a knowledge worker has to be able to work with data. >> Yeah I think its just going to be organic to every role going forward in the industry. So, Lisa curious about your thoughts about Data Cloud, the future of it and how people can really leverage it in their jobs for future leaders. >> Yeah, absolutely most enterprises today are, I would say, hybrid multicloud enterprises. What does that mean? That means that we have data sitting on-prem, we have data sitting in public clouds through software as a service applications. We have a data everywhere. Most enterprises have data everywhere, certainly those that have owned infrastructure or weren't born on the web. One of the areas that I love that Data Cloud is addressing is area around data portability and mobility. Because I have data sitting in various locations through my enterprise, how do I aggregate that data to really drive meaningful insights out of that data to drive better business outcomes? And at Blue Shield of California, one of our key initiatives is what we call an Experienced Cube. What does that mean? That means how do I drive transparency of data between providers, members and payers? So that not only do I reduce overhead on providers and provide them a better experience, our hospital systems are doctors, but ultimately, how do we have the member have it their power of their fingertips the value of their data holistically, so that we're making better decisions about their health care. One of the things Teresa was talking about, was the use of this data and I would drive to data democratization. We got to put the power of data into the hands of everyone, not just data scientists, yes we need those data scientists to help us build AI models to really drive and tackle these tough old, tougher challenges and business problems that we may have in our environments. But everybody in the company both on the IT side, both on the business side, really need to understand of how do we become a data insights driven enterprise, put the power of the data into everyone's hands so that we can accelerate capabilities, right? And leverage that data to ultimately drive better business results. So as a leader, as a technology leader, part of our responsibility, our leadership is to help our companies do that. And that's really one of the exciting things that I'm doing in my role now at Blue Shield of California. >> Yeah its really, really exciting time. I want to shift gears a little bit and focus on women in Tech. So I think in the past five to ten years there has been a lot of headway in this space but the truth is women are still under represented in the tech space. So what can we do to attract more women into technology quite honestly. So Nishita curious what your thoughts are on that? >> Great question and I am so passionate about this for a lot of reasons, not the least of which is I have two daughters of my own and I know how important it is for women and young girls to actually start early in their love for technology and data and all things digital, right? So I think it's one very important to start early started early education, building confidence of young girls that they can do this, showing them role models. We at Deloitte just partnered with LV Engineer to actually make comic books centered around young girls and boys in the early elementary age to talk about how heroes in tech solve everyday problems. And so really helping to get people's minds around tech is not just in the back office coding on a computer, tech is about solving problems together that help us as citizens, as customers, right? And as humanity, so I think that's important. I also think we have to expand that definition of tech, as we just said it's not just about right, database design, It's not just about Java and Python coding, it's about design, it's about the human machine interfaces, it's about how do you use it to solve real problems and getting people to think in that kind of mindset makes it more attractive and exciting. And lastly, I'd say look we have a absolute imperative to get a diverse population of people, not just women, but minorities, those with other types of backgrounds, disabilities, et cetera involved because this data is being used to drive decision making in all involved, right, and how that data makes decisions, it can lead to unnatural biases that no one intended but can happen just 'cause we haven't involved a diverse enough group of people around it. >> Absolutely, lisa curious about your thoughts on this. >> I agree with everything Nishita said, I've been passionate about this area, I think it starts with first we need more role models, we need more role models as women in these leadership roles throughout various sectors. And it really is it starts with us and helping to pull other women forward. So I think certainly it's part of my responsibility, I think all of us as female executives that if you have a seat at the table to leverage that seat at the table to drive change, to bring more women forward more diversity forward into the boardroom and into our executive suites. I also want to touch on a point Nishita made about women we're the largest consumer group in the company yet we're consumers but we're not builders. This is why it's so important that we start changing that perception of what tech is and I agree that it starts with our young girls, we know the data shows that we lose our like young girls by middle school, very heavy peer pressure, it's not so cool to be smart, or do robotics, or be good at math and science, we start losing our girls in middle school. So they're not prepared when they go to high school, and they're not taking those classes in order to major in these STEM fields in college. So we have to start the pipeline early with our girls. And then I also think it's a measure of what your boards are doing, what is the executive leadership in your goals around diversity and inclusion? How do we invite more diverse population to the decision making table? So it's really a combination of efforts. One of the things that certainly is concerning to me is during this pandemic, I think we're losing one in four women in the workforce now because of all the demands that our families are having to navigate through this pandemic. The last statistic I saw in the last four months is we've lost 850,000 women in the workforce. This pipeline is critical to making that change in these leadership positions. >> Yeah its really a critical time and now we are coming to the end of this conversation I want to ask you Teresa what would be a call to action to everyone listening both men and women since its to be solved by everyone to address the gender gap in the industry? >> I'd encourage each of you to become an active sponsor. Research shows that women and minorities are less likely to be sponsored than white men. Sponsorship is a much more active form than mentorship. Sponsorship involves helping someone identify career opportunities and actively advocating for them and those roles opening your network, giving very candid feedback. And we need men to participate too, there are not enough women in tech to pull forward and sponsor the high potential women that are in our pipelines. And so we need you to be part of the solution. >> Nishita real quickly what would be your call to action to everyone? >> I'd say look around your teams, see who's on them and make deliberate decisions about diversifying those teams, as positions open up, make sure that you have a diverse set of candidates, make sure that there are women that are part to that team and make sure that you are actually hiring and putting people into positions based on potential not just experience. >> And real quickly Lisa, we'll close it out with you what would your call to action be? >> Wow, it's hard to what Nishita and what Tricia shared I think we're very powerful actions. I think it starts with us. Taking action at our own table, making sure you're driving diverse panels and hiring setting goals for the company, having your board engaged and holding us accountable and driving to those goals will help us all see a better outcome with more women at the executive table and diverse populations. >> Great advice and great action for all of us to take. Thank you all so much for spending time with me today and talking about this really important issue, I really appreciate it. Stay with us.