(soft electronic music) >> Okay, we're back with Tim Yocum who is the Director of Engineering at InfluxData. Tim, welcome, good to see you. >> Good to see you, thanks for having me. >> You're really welcome. Listen, we've been covering opensource software on theCUBE for more than a decade and we've kind of watched the innovation from the big data ecosystem, the cloud is being built out on opensource, mobile, social platforms, key databases, and of course, InfluxDB. And InfluxData has been a big consumer and crontributor of opensource software. So my question to you is where have you seen the biggest bang for the buck from opensource software? >> So yeah, you know, Influx really, we thrive at the intersection of commercial services and opensource software, so OSS keeps us on the cutting edge. We benefit from OSS in delivering our own service from our core storage engine technologies to web services, templating engines. Our team stays lean and focused because we build on proven tools. We really build on the shoulders of giants. And like you've mentioned, even better, we contribute a lot back to the projects that we use, as well as our own product InfluxDB. >> But I got to ask you, Tim, because one of the challenge that we've seen, in particular, you saw this in the heyday of Hadoop, the innovations come so fast and furious, and as a software company, you got to place bets, you got to commit people, and sometimes those bets can be risky and not pay off. So how have you managed this challenge? >> Oh, it moves fast, yeah. That's a benefit, though, because the community moves so quickly that today's hot technology can be tomorrow's dinosaur. And what we tend to do is we fail fast and fail often; we try a lot of things. You know, you look at Kubernetes, for example. That ecosystem is driven by thousands of intelligent developers, engineers, builders. They're adding value every day, so we have to really keep up with that. And as the stack changes, we try different technologies, we try different methods. And at the end of the day, we come up with a better platform as a result of just the constant change in the environment. It is a challenge for us, but it's something that we just do every day. >> So we have a survey partner down in New York City called Enterprise Technology Research, ETR, and they do these quarterly surveys of about 1500 CIOs, IT practitioners, and they really have a good pulse on what's happening with spending. And the data shows that containers generally, but specifically Kubernetes, is one of the areas that is kind of, it's been off the charts and seen the most significant adoption and velocity particularly along with cloud, but really, Kubernetes is just, you know, still up and to the right consistently, even with the macro headwinds and all of the other stuff that we're sick of talking about. So what do you do with Kubernetes in the platform? >> Yeah, it's really central to our ability to run the product. When we first started out, we were just on AWS and the way we were running was a little bit like containers junior. Now we're running Kubernetes everywhere at AWS, Azure, Google cloud. It allows us to have a consistent experience across three different cloud providers and we can manage that in code. So our developers can focus on delivering services not trying to learn the intricacies of Amazon, Azure, and Google, and figure out how to deliver services on those three clouds with all of their differences. >> Just a followup on that, is it now, so I presume it sounds like there's a PaaS layer there to allow you guys to have a consistent experience across clouds and out to the edge, wherever. Is that correct? >> Yeah, so we've basically built more or less platform engineering is this the new, hot phrase. Kubernetes has made a lot of things easy for us because we've built a platform that our developers can lean on and they only have to learn one way of deploying their application, managing their application. And so that just gets all of the underlying infrastructure out of the way and lets them focus on delivering Influx cloud. >> And I know I'm taking a little bit of a tangent, but is that, I'll call it a PaaS layer, if I can use that term, are there specific attributes to InfluxDB or is it kind of just generally off-the-shelf PaaS? Is there any purpose built capability there that is value-add or is it pretty much generic? >> So we really build, we look at things with a build versus buy, through a build versus buy lens. Some things we want to leverage, cloud provider services, for instance, POSTGRES databases for metadata, perhaps. Get that off of our plate, let someone else run that. We're going to deploy a platform that our engineers can deliver on, that has consistency, that is all generated from code. that we can, as an SRE group, as an OPS team, that we can manage with very few people, really, and we can stamp out clusters across multiple regions in no time. >> So sometimes you build, sometimes you buy it. How do you make those decisions and what does that mean for the platform and for customers? >> Yeah, so what we're doing is, it's like everybody else will do. We're looking for trade-offs that make sense. We really want to protect our customers' data, so we look for services that support our own software with the most up-time reliability and durability we can get. Some things are just going to be easier to have a cloud provider take care of on our behalf. We make that transparent for our own team and of course, for our customers; you don't even see that. But we don't want to try to reinvent the wheel, like I had mentioned with SQL datasource for metadata, perhaps. Let's build on top of what of these three large cloud providers have already perfected and we can then focus on our platform engineering and we can help our developers then focus on the InfluxData software, the Influx cloud software. >> So take it to the customer level. What does it mean for them, what's the value that they're going to get out of all these innovations that we've been talking about today, and what can they expect in the future? >> So first of all, people who use the OSS product are really going to be at home on our cloud platform. You can run it on your desktop machine, on a single server, what have you, but then you want to scale up. We have some 270 terabytes of data across over four billion series keys that people have stored, so there's a proven ability to scale. Now in terms of the opensource software and how we've developed the platform, you're getting highly available, high cardinality time-series platform. We manage it and really, as I had mentioned earlier, we can keep up with the state of the art. We keep reinventing, we keep deploying things in realtime. We deploy to our platform every day, repeatedly, all the time. And it's that continuous deployment that allow us to continue testing things in flight, rolling things out that change, new features, better ways of doing deployments, safer ways of doing deployments. All of that happens behind the scenes and like we had mentioned earllier, Kubernetes, I mean, that allows us to get that done. We couldn't do it without having that platform as a base layer for us to then put our software on. So we iterate quickly. When you're on the Influx cloud platform, you really are able to take advantage of new features immediately. We roll things out every day and as those things go into production, you have the ability to use them. And so in the then, we want you to focus on getting actual insights from your data instead of running infrastructure, you know, let us do that for you. >> That makes sense. Are the innovations that we're talking about in the evolution of InfluxDB, do you see that as sort of a natural evolution for existing customers? Is it, I'm sure the answer is both, but is it opening up new territory for customers? Can you add some color to that? >> Yeah, it really is. It's a little bit of both. Any engineer will say, "Well it depends." So cloud-native technologies are really the hot thing, IoT, industrial IoT especially. People want to just shove tons of data out there and be able to do queries immediately and they don't want to manage infrastructure. What we've started to see are people that use the cloud service as their datastore backbone and then they use edge computing with our OSS product to ingest data from say, multiple production lines, and down-sample that data, send the rest of that data off to Influx cloud where the heavy processing takes place. So really, us being in all the different clouds and iterating on that, and being in all sorts of different regions, allows for people to really get out of the business of trying to manage that big data, have us take care of that. And, of course, as we change the platform, endusers benefit from that immediately. >> And so obviously you've taken away a lot of the heavy lifting for the infrastructure. Would you say the same things about security, especially as you go out to IoT at the edge? How should we be thinking about the value that you bring from a security perspective? >> We take security super seriously. It's built into our DNA. We do a lot of work to ensure that our platform is secure, that the data that we store is kept private. It's, of course, always a concern, you see in the news all the time, companies being compromised. That's something that you can have an entire team working on which we do, to make sure that the data that you have, whether it's in transit, whether it's at rest is always kept secure, is only viewable by you. You look at things like software bill of materials, if you're running this yourself, you have to go vet all sorts of different pieces of software and we do that, you know, as we use new tools. That's something, that's just part of our jobs to make sure that the platform that we're running has fully vetted software. And you know, with opensource especially, that's a lot of work, and so it's definitely new territory. Supply chain attacks are definitely happening at a higher clip that they used to but that is really just part of a day in the life for folks like us that are building platforms. >> And that's key, especially when you start getting into the, you know, that we talk about IoT and the operations technologies, the engineers running that infrastrucutre. You know, historically, as you know, Tim, they would air gap everything; that's how they kept it safe. But that's not feasible anymore. Everything's-- >> Can't do that. >> connected now, right? And so you've got to have a partner that is, again, take away that heavy lifting to R&D so you can focus on some of the other activities. All right, give us the last word and the key takeaways from your perspective. >> Well, you know, from my perspective, I see it as a two-lane approach, with Influx, with any time-series data. You've got a lot of stuff that you're going to run on-prem. What you had mentioned, air gapping? Sure, there's plenty of need for that. But at the end of the day, people that don't want to run big datacenters, people that want to entrust their data to a company that's got a full platform set up for them that they can build on, send that data over to the cloud. The cloud is not going away. I think a more hybrid approach is where the future lives and that's what we're prepared for. >> Tim, really appreciate you coming to the program. Great stuff, good to see you. >> Thanks very much, appreciate it. >> Okay in a moment, I'll be back to wrap up today's session. You're watching theCUBE. (soft electronic music)

>>Okay, we're back. I'm Dave Valante with The Cube and you're watching Evolving Influx DB into the smart data platform made possible by influx data. Anna East Otis Georgio is here. She's a developer advocate for influx data and we're gonna dig into the rationale and value contribution behind several open source technologies that Influx DB is leveraging to increase the granularity of time series analysis analysis and bring the world of data into realtime analytics. Anna is welcome to the program. Thanks for coming on. >>Hi, thank you so much. It's a pleasure to be here. >>Oh, you're very welcome. Okay, so IO X is being touted as this next gen open source core for Influx db. And my understanding is that it leverages in memory, of course for speed. It's a kilo store, so it gives you compression efficiency, it's gonna give you faster query speeds, it gonna use store files and object storages. So you got very cost effective approach. Are these the salient points on the platform? I know there are probably dozens of other features, but what are the high level value points that people should understand? >>Sure, that's a great question. So some of the main requirements that IOCs is trying to achieve and some of the most impressive ones to me, the first one is that it aims to have no limits on cardinality and also allow you to write any kind of event data that you want, whether that's lift tag or a field. It also wants to deliver the best in class performance on analytics queries. In addition to our already well served metrics queries, we also wanna have operator control over memory usage. So you should be able to define how much memory is used for buffering caching and query processing. Some other really important parts is the ability to have bulk data export and import, super useful. Also, broader ecosystem compatibility where possible we aim to use and embrace emerging standards in the data analytics ecosystem and have compatibility with things like sql, Python, and maybe even pandas in the future. >>Okay, so a lot there. Now we talked to Brian about how you're using Rust and and which is not a new programming language and of course we had some drama around Russ during the pandemic with the Mozilla layoffs, but the formation of the Russ Foundation really addressed any of those concerns. You got big guns like Amazon and Google and Microsoft throwing their collective weights behind it. It's really, adoption is really starting to get steep on the S-curve. So lots of platforms, lots of adoption with rust, but why rust as an alternative to say c plus plus for example? >>Sure, that's a great question. So Rust was chosen because of his exceptional performance and rebi reliability. So while rust is synt tactically similar to c c plus plus and it has similar performance, it also compiles to a native code like c plus plus. But unlike c plus plus, it also has much better memory safety. So memory safety is protection against bugs or security vulnerabilities that lead to excessive memory usage or memory leaks. And rust achieves this memory safety due to its like innovative type system. Additionally, it doesn't allow for dangling pointers and dangling pointers are the main classes of errors that lead to exploitable security vulnerabilities in languages like c plus plus. So Russ like helps meet that requirement of having no limits on card for example, because it's, we're also using the Russ implementation of Apache Arrow and this control over memory and also Russ, Russ Russ's packaging system called crates IO offers everything that you need out of the box to have features like AY and a weight to fixed race conditions to protect against buffering overflows and to ensure thread safe ay caching structures as well. So essentially it's just like has all the control, all the fine grain control, you need to take advantage of memory and all your resources as well as possible so that you can handle those really, really high ity use cases. >>Yeah, and the more I learned about the the new engine and the, and the platform IOCs et cetera, you know, you, you see things like, you know, the old days not even to even today you do a lot of garbage collection in these, in these systems and there's an inverse, you know, impact relative to performance. So it looks like you're really, you know, the community is modernizing the platform, but I wanna talk about Apache Arrow for a moment. It's designed to address the constraints that are associated with analyzing large data sets. We, we know that, but please explain why, what, what is Arrow and and what does it bring to Influx db? >>Sure, yeah. So Arrow is a, a framework for defining in memory calmer data and so much of the efficiency and performance of IOCs comes from taking advantage of calmer data structures. And I will, if you don't mind, take a moment to kind of illustrate why calmer data structures are so valuable. Let's pretend that we are gathering field data about the temperature in our room and also maybe the temperature of our stove. And in our table we have those two temperature values as well as maybe a measurement value, timestamp value, maybe some other tag values that describe what room and what house, et cetera we're getting this data from. And so you can picture this table where we have like two rows with the two temperature values for both our room and the stove. Well usually our room temperature is regulated so those values don't change very often. >>So when you have calm oriented st calm oriented storage, essentially you take each row, each column and group it together. And so if that's the case and you're just taking temperature values from the room and a lot of those temperature values are the same, then you'll, you might be able to imagine how equal values will then neighbor each other and when they neighbor each other in the storage format. This provides a really perfect opportunity for cheap compression. And then this cheap compression enables high cardinality use cases. It also enables for faster scan rates. So if you wanna define like the min and max value of the temperature in the room across a thousand different points, you only have to get those a thousand different points in order to answer that question and you have those immediately available to you. But let's contrast this with a row oriented storage solution instead so that we can understand better the benefits of calmer oriented storage. >>So if you had a row oriented storage, you'd first have to look at every field like the temperature in, in the room and the temperature of the stove. You'd have to go across every tag value that maybe describes where the room is located or what model the stove is. And every timestamp you'd then have to pluck out that one temperature value that you want at that one times stamp and do that for every single row. So you're scanning across a ton more data and that's why row oriented doesn't provide the same efficiency as calmer and Apache Arrow is in memory calmer data, calmer data fit framework. So that's where a lot of the advantages come >>From. Okay. So you've basically described like a traditional database, a row approach, but I've seen like a lot of traditional databases say, okay, now we've got, we can handle colo format versus what you're talking about is really, you know, kind of native it, is it not as effective as the, is the form not as effective because it's largely a, a bolt on? Can you, can you like elucidate on that front? >>Yeah, it's, it's not as effective because you have more expensive compression and because you can't scan across the values as quickly. And so those are, that's pretty much the main reasons why, why RO row oriented storage isn't as efficient as calm, calmer oriented storage. >>Yeah. Got it. So let's talk about Arrow data fusion. What is data fusion? I know it's written in rust, but what does it bring to to the table here? >>Sure. So it's an extensible query execution framework and it uses Arrow as its in memory format. So the way that it helps influx DB IOx is that okay, it's great if you can write unlimited amount of cardinality into influx cbis, but if you don't have a query engine that can successfully query that data, then I don't know how much value it is for you. So data fusion helps enable the, the query process and transformation of that data. It also has a PANDAS API so that you could take advantage of PDA's data frames as well and all of the machine learning tools associated with pandas. >>Okay. You're also leveraging par K in the platform course. We heard a lot about Par K in the middle of the last decade cuz as a storage format to improve on Hadoop column stores. What are you doing with Par K and why is it important? >>Sure. So Par K is the calm oriented durable file format. So it's important because it'll enable bulk import and bulk export. It has compatibility with Python and pandas so it supports a broader ecosystem. Parque files also take very little disc disc space and they're faster to scan because again they're column oriented in particular, I think PAR K files are like 16 times cheaper than CSV files, just as kind of a point of reference. And so that's essentially a lot of the, the benefits of par k. >>Got it. Very popular. So and these, what exactly is influx data focusing on as a committer to these projects? What is your focus? What's the value that you're bringing to the community? >>Sure. So Influx DB first has contributed a lot of different, different things to the Apache ecosystem. For example, they contribute an implementation of Apache Arrow and go and that will support clearing with flux. Also, there has been a quite a few contributions to data fusion for things like memory optimization and supportive additional SQL features like support for timestamp, arithmetic and support for exist clauses and support for memory control. So yeah, Influx has contributed a a lot to the Apache ecosystem and continues to do so. And I think kind of the idea here is that if you can improve these upstream projects and then the long term strategy here is that the more you contribute and build those up, then the more you will perpetuate that cycle of improvement and the more we will invest in our own project as well. So it's just that kind of symbiotic relationship and appreciation of the open source community. >>Yeah. Got it. You got that virtuous cycle going, the people call it the flywheel. Give us your last thoughts and kind of summarize, you know, where what, what the big takeaways are from your perspective. >>So I think the big takeaway is that influx data is doing a lot of really exciting things with Influx DB IOCs and I really encourage if you are interested in learning more about the technologies that Influx is leveraging to produce IOCs, the challenges associated with it and all of the hard work questions and I just wanna learn more, then I would encourage you to go to the monthly tech talks and community office hours and they are on every second Wednesday of the month at 8:30 AM Pacific time. There's also a community forums and a community Slack channel. Look for the influx D DB underscore IAC channel specifically to learn more about how to join those office hours and those monthly tech tech talks as well as ask any questions they have about IOCs, what to expect and what you'd like to learn more about. I as a developer advocate, I wanna answer your questions. So if there's a particular technology or stack that you wanna dive deeper into and want more explanation about how influx TB leverages it to build IOCs, I will be really excited to produce content on that topic for you. >>Yeah, that's awesome. You guys have a really rich community, collaborate with your peers, solve problems, and you guys super responsive, so really appreciate that. All right, thank you so much and East for explaining all this open source stuff to the audience and why it's important to the future of data. >>Thank you. I really appreciate it. >>All right, you're very welcome. Okay, stay right there and in a moment I'll be back with Tim Yokum. He's the director of engineering for Influx Data and we're gonna talk about how you update a SaaS engine while the plane is flying at 30,000 feet. You don't wanna miss this.

>>This past May, The Cube in collaboration with Influx data shared with you the latest innovations in Time series databases. We talked at length about why a purpose built time series database for many use cases, was a superior alternative to general purpose databases trying to do the same thing. Now, you may, you may remember the time series data is any data that's stamped in time, and if it's stamped, it can be analyzed historically. And when we introduced the concept to the community, we talked about how in theory, those time slices could be taken, you know, every hour, every minute, every second, you know, down to the millisecond and how the world was moving toward realtime or near realtime data analysis to support physical infrastructure like sensors and other devices and IOT equipment. A time series databases have had to evolve to efficiently support realtime data in emerging use cases in iot T and other use cases. >>And to do that, new architectural innovations have to be brought to bear. As is often the case, open source software is the linchpin to those innovations. Hello and welcome to Evolving Influx DB into the smart Data platform, made possible by influx data and produced by the Cube. My name is Dave Valante and I'll be your host today. Now, in this program, we're going to dig pretty deep into what's happening with Time series data generally, and specifically how Influx DB is evolving to support new workloads and demands and data, and specifically around data analytics use cases in real time. Now, first we're gonna hear from Brian Gilmore, who is the director of IOT and emerging technologies at Influx Data. And we're gonna talk about the continued evolution of Influx DB and the new capabilities enabled by open source generally and specific tools. And in this program, you're gonna hear a lot about things like Rust, implementation of Apache Arrow, the use of par k and tooling such as data fusion, which powering a new engine for Influx db. >>Now, these innovations, they evolve the idea of time series analysis by dramatically increasing the granularity of time series data by compressing the historical time slices, if you will, from, for example, minutes down to milliseconds. And at the same time, enabling real time analytics with an architecture that can process data much faster and much more efficiently. Now, after Brian, we're gonna hear from Anna East Dos Georgio, who is a developer advocate at In Flux Data. And we're gonna get into the why of these open source capabilities and how they contribute to the evolution of the Influx DB platform. And then we're gonna close the program with Tim Yokum, he's the director of engineering at Influx Data, and he's gonna explain how the Influx DB community actually evolved the data engine in mid-flight and which decisions went into the innovations that are coming to the market. Thank you for being here. We hope you enjoy the program. Let's get started. Okay, we're kicking things off with Brian Gilmore. He's the director of i t and emerging Technology at Influx State of Bryan. Welcome to the program. Thanks for coming on. >>Thanks Dave. Great to be here. I appreciate the time. >>Hey, explain why Influx db, you know, needs a new engine. Was there something wrong with the current engine? What's going on there? >>No, no, not at all. I mean, I think it's, for us, it's been about staying ahead of the market. I think, you know, if we think about what our customers are coming to us sort of with now, you know, related to requests like sql, you know, query support, things like that, we have to figure out a way to, to execute those for them in a way that will scale long term. And then we also, we wanna make sure we're innovating, we're sort of staying ahead of the market as well and sort of anticipating those future needs. So, you know, this is really a, a transparent change for our customers. I mean, I think we'll be adding new capabilities over time that sort of leverage this new engine, but you know, initially the customers who are using us are gonna see just great improvements in performance, you know, especially those that are working at the top end of the, of the workload scale, you know, the massive data volumes and things like that. >>Yeah, and we're gonna get into that today and the architecture and the like, but what was the catalyst for the enhancements? I mean, when and how did this all come about? >>Well, I mean, like three years ago we were primarily on premises, right? I mean, I think we had our open source, we had an enterprise product, you know, and, and sort of shifting that technology, especially the open source code base to a service basis where we were hosting it through, you know, multiple cloud providers. That was, that was, that was a long journey I guess, you know, phase one was, you know, we wanted to host enterprise for our customers, so we sort of created a service that we just managed and ran our enterprise product for them. You know, phase two of this cloud effort was to, to optimize for like multi-tenant, multi-cloud, be able to, to host it in a truly like sass manner where we could use, you know, some type of customer activity or consumption as the, the pricing vector, you know, And, and that was sort of the birth of the, of the real first influx DB cloud, you know, which has been really successful. >>We've seen, I think, like 60,000 people sign up and we've got tons and tons of, of both enterprises as well as like new companies, developers, and of course a lot of home hobbyists and enthusiasts who are using out on a, on a daily basis, you know, and having that sort of big pool of, of very diverse and very customers to chat with as they're using the product, as they're giving us feedback, et cetera, has has, you know, pointed us in a really good direction in terms of making sure we're continuously improving that and then also making these big leaps as we're doing with this, with this new engine. >>Right. So you've called it a transparent change for customers, so I'm presuming it's non-disruptive, but I really wanna understand how much of a pivot this is and what, what does it take to make that shift from, you know, time series, you know, specialist to real time analytics and being able to support both? >>Yeah, I mean, it's much more of an evolution, I think, than like a shift or a pivot. You know, time series data is always gonna be fundamental and sort of the basis of the solutions that we offer our customers, and then also the ones that they're building on the sort of raw APIs of our platform themselves. You know, the time series market is one that we've worked diligently to lead. I mean, I think when it comes to like metrics, especially like sensor data and app and infrastructure metrics, if we're being honest though, I think our, our user base is well aware that the way we were architected was much more towards those sort of like backwards looking historical type analytics, which are key for troubleshooting and making sure you don't, you know, run into the same problem twice. But, you know, we had to ask ourselves like, what can we do to like better handle those queries from a performance and a, and a, you know, a time to response on the queries, and can we get that to the point where the results sets are coming back so quickly from the time of query that we can like limit that window down to minutes and then seconds. >>And now with this new engine, we're really starting to talk about a query window that could be like returning results in, in, you know, milliseconds of time since it hit the, the, the ingest queue. And that's, that's really getting to the point where as your data is available, you can use it and you can query it, you can visualize it, and you can do all those sort of magical things with it, you know? And I think getting all of that to a place where we're saying like, yes to the customer on, you know, all of the, the real time queries, the, the multiple language query support, but, you know, it was hard, but we're now at a spot where we can start introducing that to, you know, a a limited number of customers, strategic customers and strategic availability zones to start. But you know, everybody over time. >>So you're basically going from what happened to in, you can still do that obviously, but to what's happening now in the moment? >>Yeah, yeah. I mean, if you think about time, it's always sort of past, right? I mean, like in the moment right now, whether you're talking about like a millisecond ago or a minute ago, you know, that's, that's pretty much right now, I think for most people, especially in these use cases where you have other sort of components of latency induced by the, by the underlying data collection, the architecture, the infrastructure, the, you know, the, the devices and you know, the sort of highly distributed nature of all of this. So yeah, I mean, getting, getting a customer or a user to be able to use the data as soon as it is available is what we're after here. >>I always thought, you know, real, I always thought of real time as before you lose the customer, but now in this context, maybe it's before the machine blows up. >>Yeah, it's, it's, I mean it is operationally or operational real time is different, you know, and that's one of the things that really triggered us to know that we were, we were heading in the right direction, is just how many sort of operational customers we have. You know, everything from like aerospace and defense. We've got companies monitoring satellites, we've got tons of industrial users, users using us as a processes storing on the plant floor, you know, and, and if we can satisfy their sort of demands for like real time historical perspective, that's awesome. I think what we're gonna do here is we're gonna start to like edge into the real time that they're used to in terms of, you know, the millisecond response times that they expect of their control systems. Certainly not their, their historians and databases. >>I, is this available, these innovations to influx DB cloud customers only who can access this capability? >>Yeah. I mean, commercially and today, yes. You know, I think we want to emphasize that's a, for now our goal is to get our latest and greatest and our best to everybody over time. Of course. You know, one of the things we had to do here was like we double down on sort of our, our commitment to open source and availability. So like anybody today can take a look at the, the libraries in on our GitHub and, you know, can ex inspect it and even can try to, you know, implement or execute some of it themselves in their own infrastructure. You know, we are, we're committed to bringing our sort of latest and greatest to our cloud customers first for a couple of reasons. Number one, you know, there are big workloads and they have high expectations of us. I think number two, it also gives us the opportunity to monitor a little bit more closely how it's working, how they're using it, like how the system itself is performing. >>And so just, you know, being careful, maybe a little cautious in terms of, of, of how big we go with this right away. Just sort of both limits, you know, the risk of, of, you know, any issues that can come with new software rollouts. We haven't seen anything so far, but also it does give us the opportunity to have like meaningful conversations with a small group of users who are using the products, but once we get through that and they give us two thumbs up on it, it'll be like, open the gates and let everybody in. It's gonna be exciting time for the whole ecosystem. >>Yeah, that makes a lot of sense. And you can do some experimentation and, you know, using the cloud resources. Let's dig into some of the architectural and technical innovations that are gonna help deliver on this vision. What, what should we know there? >>Well, I mean, I think foundationally we built the, the new core on Rust. You know, this is a new very sort of popular systems language, you know, it's extremely efficient, but it's also built for speed and memory safety, which goes back to that us being able to like deliver it in a way that is, you know, something we can inspect very closely, but then also rely on the fact that it's going to behave well. And if it does find error conditions, I mean, we, we've loved working with Go and, you know, a lot of our libraries will continue to, to be sort of implemented in Go, but you know, when it came to this particular new engine, you know, that power performance and stability rust was critical. On top of that, like, we've also integrated Apache Arrow and Apache Parque for persistence. I think for anybody who's really familiar with the nuts and bolts of our backend and our TSI and our, our time series merged Trees, this is a big break from that, you know, arrow on the sort of in MI side and then Par K in the on disk side. >>It, it allows us to, to present, you know, a unified set of APIs for those really fast real time inquiries that we talked about, as well as for very large, you know, historical sort of bulk data archives in that PARQUE format, which is also cool because there's an entire ecosystem sort of popping up around Parque in terms of the machine learning community, you know, and getting that all to work, we had to glue it together with aero flight. That's sort of what we're using as our, our RPC component. You know, it handles the orchestration and the, the transportation of the Coer data. Now we're moving to like a true Coer database model for this, this version of the engine, you know, and it removes a lot of overhead for us in terms of having to manage all that serialization, the deserialization, and, you know, to that again, like blurring that line between real time and historical data. It's, you know, it's, it's highly optimized for both streaming micro batch and then batches, but true streaming as well. >>Yeah. Again, I mean, it's funny you mentioned Rust. It is, it's been around for a long time, but it's popularity is, is, you know, really starting to hit that steep part of the S-curve. And, and we're gonna dig into to more of that, but give us any, is there anything else that we should know about Bryan? Give us the last word? >>Well, I mean, I think first I'd like everybody sort of watching just to like, take a look at what we're offering in terms of early access in beta programs. I mean, if, if, if you wanna participate or if you wanna work sort of in terms of early access with the, with the new engine, please reach out to the team. I'm sure you know, there's a lot of communications going out and, you know, it'll be highly featured on our, our website, you know, but reach out to the team, believe it or not, like we have a lot more going on than just the new engine. And so there are also other programs, things we're, we're offering to customers in terms of the user interface, data collection and things like that. And, you know, if you're a customer of ours and you have a sales team, a commercial team that you work with, you can reach out to them and see what you can get access to because we can flip a lot of stuff on, especially in cloud through feature flags. >>But if there's something new that you wanna try out, we'd just love to hear from you. And then, you know, our goal would be that as we give you access to all of these new cool features that, you know, you would give us continuous feedback on these products and services, not only like what you need today, but then what you'll need tomorrow to, to sort of build the next versions of your business. Because, you know, the whole database, the ecosystem as it expands out into to, you know, this vertically oriented stack of cloud services and enterprise databases and edge databases, you know, it's gonna be what we all make it together, not just, you know, those of us who were employed by Influx db. And then finally, I would just say please, like watch in ice in Tim's sessions, Like these are two of our best and brightest. They're totally brilliant, completely pragmatic, and they are most of all customer obsessed, which is amazing. And there's no better takes, like honestly on the, the sort of technical details of this, then there's, especially when it comes to like the value that these investments will, will bring to our customers and our communities. So encourage you to, to, you know, pay more attention to them than you did to me, for sure. >>Brian Gilmore, great stuff. Really appreciate your time. Thank you. >>Yeah, thanks Dave. It was awesome. Look forward to it. >>Yeah, me too. Looking forward to see how the, the community actually applies these new innovations and goes, goes beyond just the historical into the real time, really hot area. As Brian said in a moment, I'll be right back with Anna East Dos Georgio to dig into the critical aspects of key open source components of the Influx DB engine, including Rust, Arrow, Parque, data fusion. Keep it right there. You don't want to miss this.

>>This past May, The Cube in collaboration with Influx data shared with you the latest innovations in Time series databases. We talked at length about why a purpose built time series database for many use cases, was a superior alternative to general purpose databases trying to do the same thing. Now, you may, you may remember the time series data is any data that's stamped in time, and if it's stamped, it can be analyzed historically. And when we introduced the concept to the community, we talked about how in theory, those time slices could be taken, you know, every hour, every minute, every second, you know, down to the millisecond and how the world was moving toward realtime or near realtime data analysis to support physical infrastructure like sensors and other devices and IOT equipment. A time series databases have had to evolve to efficiently support realtime data in emerging use cases in iot T and other use cases. >>And to do that, new architectural innovations have to be brought to bear. As is often the case, open source software is the linchpin to those innovations. Hello and welcome to Evolving Influx DB into the smart Data platform, made possible by influx data and produced by the Cube. My name is Dave Valante and I'll be your host today. Now in this program we're going to dig pretty deep into what's happening with Time series data generally, and specifically how Influx DB is evolving to support new workloads and demands and data, and specifically around data analytics use cases in real time. Now, first we're gonna hear from Brian Gilmore, who is the director of IOT and emerging technologies at Influx Data. And we're gonna talk about the continued evolution of Influx DB and the new capabilities enabled by open source generally and specific tools. And in this program you're gonna hear a lot about things like Rust, implementation of Apache Arrow, the use of par k and tooling such as data fusion, which powering a new engine for Influx db. >>Now, these innovations, they evolve the idea of time series analysis by dramatically increasing the granularity of time series data by compressing the historical time slices, if you will, from, for example, minutes down to milliseconds. And at the same time, enabling real time analytics with an architecture that can process data much faster and much more efficiently. Now, after Brian, we're gonna hear from Anna East Dos Georgio, who is a developer advocate at In Flux Data. And we're gonna get into the why of these open source capabilities and how they contribute to the evolution of the Influx DB platform. And then we're gonna close the program with Tim Yokum, he's the director of engineering at Influx Data, and he's gonna explain how the Influx DB community actually evolved the data engine in mid-flight and which decisions went into the innovations that are coming to the market. Thank you for being here. We hope you enjoy the program. Let's get started. Okay, we're kicking things off with Brian Gilmore. He's the director of i t and emerging Technology at Influx State of Bryan. Welcome to the program. Thanks for coming on. >>Thanks Dave. Great to be here. I appreciate the time. >>Hey, explain why Influx db, you know, needs a new engine. Was there something wrong with the current engine? What's going on there? >>No, no, not at all. I mean, I think it's, for us, it's been about staying ahead of the market. I think, you know, if we think about what our customers are coming to us sort of with now, you know, related to requests like sql, you know, query support, things like that, we have to figure out a way to, to execute those for them in a way that will scale long term. And then we also, we wanna make sure we're innovating, we're sort of staying ahead of the market as well and sort of anticipating those future needs. So, you know, this is really a, a transparent change for our customers. I mean, I think we'll be adding new capabilities over time that sort of leverage this new engine, but you know, initially the customers who are using us are gonna see just great improvements in performance, you know, especially those that are working at the top end of the, of the workload scale, you know, the massive data volumes and things like that. >>Yeah, and we're gonna get into that today and the architecture and the like, but what was the catalyst for the enhancements? I mean, when and how did this all come about? >>Well, I mean, like three years ago we were primarily on premises, right? I mean, I think we had our open source, we had an enterprise product, you know, and, and sort of shifting that technology, especially the open source code base to a service basis where we were hosting it through, you know, multiple cloud providers. That was, that was, that was a long journey I guess, you know, phase one was, you know, we wanted to host enterprise for our customers, so we sort of created a service that we just managed and ran our enterprise product for them. You know, phase two of this cloud effort was to, to optimize for like multi-tenant, multi-cloud, be able to, to host it in a truly like sass manner where we could use, you know, some type of customer activity or consumption as the, the pricing vector, you know, And, and that was sort of the birth of the, of the real first influx DB cloud, you know, which has been really successful. >>We've seen, I think like 60,000 people sign up and we've got tons and tons of, of both enterprises as well as like new companies, developers, and of course a lot of home hobbyists and enthusiasts who are using out on a, on a daily basis, you know, and having that sort of big pool of, of very diverse and very customers to chat with as they're using the product, as they're giving us feedback, et cetera, has has, you know, pointed us in a really good direction in terms of making sure we're continuously improving that and then also making these big leaps as we're doing with this, with this new engine. >>Right. So you've called it a transparent change for customers, so I'm presuming it's non-disruptive, but I really wanna understand how much of a pivot this is and what, what does it take to make that shift from, you know, time series, you know, specialist to real time analytics and being able to support both? >>Yeah, I mean, it's much more of an evolution, I think, than like a shift or a pivot. You know, time series data is always gonna be fundamental and sort of the basis of the solutions that we offer our customers, and then also the ones that they're building on the sort of raw APIs of our platform themselves. You know, the time series market is one that we've worked diligently to lead. I mean, I think when it comes to like metrics, especially like sensor data and app and infrastructure metrics, if we're being honest though, I think our, our user base is well aware that the way we were architected was much more towards those sort of like backwards looking historical type analytics, which are key for troubleshooting and making sure you don't, you know, run into the same problem twice. But, you know, we had to ask ourselves like, what can we do to like better handle those queries from a performance and a, and a, you know, a time to response on the queries, and can we get that to the point where the results sets are coming back so quickly from the time of query that we can like limit that window down to minutes and then seconds. >>And now with this new engine, we're really starting to talk about a query window that could be like returning results in, in, you know, milliseconds of time since it hit the, the, the ingest queue. And that's, that's really getting to the point where as your data is available, you can use it and you can query it, you can visualize it, and you can do all those sort of magical things with it, you know? And I think getting all of that to a place where we're saying like, yes to the customer on, you know, all of the, the real time queries, the, the multiple language query support, but, you know, it was hard, but we're now at a spot where we can start introducing that to, you know, a a limited number of customers, strategic customers and strategic availability zones to start. But you know, everybody over time. >>So you're basically going from what happened to in, you can still do that obviously, but to what's happening now in the moment? >>Yeah, yeah. I mean if you think about time, it's always sort of past, right? I mean, like in the moment right now, whether you're talking about like a millisecond ago or a minute ago, you know, that's, that's pretty much right now, I think for most people, especially in these use cases where you have other sort of components of latency induced by the, by the underlying data collection, the architecture, the infrastructure, the, you know, the, the devices and you know, the sort of highly distributed nature of all of this. So yeah, I mean, getting, getting a customer or a user to be able to use the data as soon as it is available is what we're after here. >>I always thought, you know, real, I always thought of real time as before you lose the customer, but now in this context, maybe it's before the machine blows up. >>Yeah, it's, it's, I mean it is operationally or operational real time is different, you know, and that's one of the things that really triggered us to know that we were, we were heading in the right direction, is just how many sort of operational customers we have. You know, everything from like aerospace and defense. We've got companies monitoring satellites, we've got tons of industrial users, users using us as a processes storing on the plant floor, you know, and, and if we can satisfy their sort of demands for like real time historical perspective, that's awesome. I think what we're gonna do here is we're gonna start to like edge into the real time that they're used to in terms of, you know, the millisecond response times that they expect of their control systems, certainly not their, their historians and databases. >>I, is this available, these innovations to influx DB cloud customers only who can access this capability? >>Yeah. I mean commercially and today, yes. You know, I think we want to emphasize that's a, for now our goal is to get our latest and greatest and our best to everybody over time. Of course. You know, one of the things we had to do here was like we double down on sort of our, our commitment to open source and availability. So like anybody today can take a look at the, the libraries in on our GitHub and, you know, can ex inspect it and even can try to, you know, implement or execute some of it themselves in their own infrastructure. You know, we are, we're committed to bringing our sort of latest and greatest to our cloud customers first for a couple of reasons. Number one, you know, there are big workloads and they have high expectations of us. I think number two, it also gives us the opportunity to monitor a little bit more closely how it's working, how they're using it, like how the system itself is performing. >>And so just, you know, being careful, maybe a little cautious in terms of, of, of how big we go with this right away, just sort of both limits, you know, the risk of, of, you know, any issues that can come with new software rollouts. We haven't seen anything so far, but also it does give us the opportunity to have like meaningful conversations with a small group of users who are using the products, but once we get through that and they give us two thumbs up on it, it'll be like, open the gates and let everybody in. It's gonna be exciting time for the whole ecosystem. >>Yeah, that makes a lot of sense. And you can do some experimentation and, you know, using the cloud resources. Let's dig into some of the architectural and technical innovations that are gonna help deliver on this vision. What, what should we know there? >>Well, I mean, I think foundationally we built the, the new core on Rust. You know, this is a new very sort of popular systems language, you know, it's extremely efficient, but it's also built for speed and memory safety, which goes back to that us being able to like deliver it in a way that is, you know, something we can inspect very closely, but then also rely on the fact that it's going to behave well. And if it does find error conditions, I mean we, we've loved working with Go and, you know, a lot of our libraries will continue to, to be sort of implemented in Go, but you know, when it came to this particular new engine, you know, that power performance and stability rust was critical. On top of that, like, we've also integrated Apache Arrow and Apache Parque for persistence. I think for anybody who's really familiar with the nuts and bolts of our backend and our TSI and our, our time series merged Trees, this is a big break from that, you know, arrow on the sort of in MI side and then Par K in the on disk side. >>It, it allows us to, to present, you know, a unified set of APIs for those really fast real time inquiries that we talked about, as well as for very large, you know, historical sort of bulk data archives in that PARQUE format, which is also cool because there's an entire ecosystem sort of popping up around Parque in terms of the machine learning community, you know, and getting that all to work, we had to glue it together with aero flight. That's sort of what we're using as our, our RPC component. You know, it handles the orchestration and the, the transportation of the Coer data. Now we're moving to like a true Coer database model for this, this version of the engine, you know, and it removes a lot of overhead for us in terms of having to manage all that serialization, the deserialization, and, you know, to that again, like blurring that line between real time and historical data. It's, you know, it's, it's highly optimized for both streaming micro batch and then batches, but true streaming as well. >>Yeah. Again, I mean, it's funny you mentioned Rust. It is, it's been around for a long time, but it's popularity is, is you know, really starting to hit that steep part of the S-curve. And, and we're gonna dig into to more of that, but give us any, is there anything else that we should know about Bryan? Give us the last word? >>Well, I mean, I think first I'd like everybody sort of watching just to like take a look at what we're offering in terms of early access in beta programs. I mean, if, if, if you wanna participate or if you wanna work sort of in terms of early access with the, with the new engine, please reach out to the team. I'm sure you know, there's a lot of communications going out and you know, it'll be highly featured on our, our website, you know, but reach out to the team, believe it or not, like we have a lot more going on than just the new engine. And so there are also other programs, things we're, we're offering to customers in terms of the user interface, data collection and things like that. And, you know, if you're a customer of ours and you have a sales team, a commercial team that you work with, you can reach out to them and see what you can get access to because we can flip a lot of stuff on, especially in cloud through feature flags. >>But if there's something new that you wanna try out, we'd just love to hear from you. And then, you know, our goal would be that as we give you access to all of these new cool features that, you know, you would give us continuous feedback on these products and services, not only like what you need today, but then what you'll need tomorrow to, to sort of build the next versions of your business. Because you know, the whole database, the ecosystem as it expands out into to, you know, this vertically oriented stack of cloud services and enterprise databases and edge databases, you know, it's gonna be what we all make it together, not just, you know, those of us who were employed by Influx db. And then finally I would just say please, like watch in ICE in Tim's sessions, like these are two of our best and brightest, They're totally brilliant, completely pragmatic, and they are most of all customer obsessed, which is amazing. And there's no better takes, like honestly on the, the sort of technical details of this, then there's, especially when it comes to like the value that these investments will, will bring to our customers and our communities. So encourage you to, to, you know, pay more attention to them than you did to me, for sure. >>Brian Gilmore, great stuff. Really appreciate your time. Thank you. >>Yeah, thanks Dave. It was awesome. Look forward to it. >>Yeah, me too. Looking forward to see how the, the community actually applies these new innovations and goes, goes beyond just the historical into the real time really hot area. As Brian said in a moment, I'll be right back with Anna East dos Georgio to dig into the critical aspects of key open source components of the Influx DB engine, including Rust, Arrow, Parque, data fusion. Keep it right there. You don't wanna miss this >>Time series Data is everywhere. The number of sensors, systems and applications generating time series data increases every day. All these data sources producing so much data can cause analysis paralysis. Influx DB is an entire platform designed with everything you need to quickly build applications that generate value from time series data influx. DB Cloud is a serverless solution, which means you don't need to buy or manage your own servers. There's no need to worry about provisioning because you only pay for what you use. Influx DB Cloud is fully managed so you get the newest features and enhancements as they're added to the platform's code base. It also means you can spend time building solutions and delivering value to your users instead of wasting time and effort managing something else. Influx TVB Cloud offers a range of security features to protect your data, multiple layers of redundancy ensure you don't lose any data access controls ensure that only the people who should see your data can see it. >>And encryption protects your data at rest and in transit between any of our regions or cloud providers. InfluxDB uses a single API across the entire platform suite so you can build on open source, deploy to the cloud and then then easily query data in the cloud at the edge or on prem using the same scripts. And InfluxDB is schemaless automatically adjusting to changes in the shape of your data without requiring changes in your application. Logic. InfluxDB Cloud is production ready from day one. All it needs is your data and your imagination. Get started today@influxdata.com slash cloud. >>Okay, we're back. I'm Dave Valante with a Cube and you're watching evolving Influx DB into the smart data platform made possible by influx data. Anna ETOs Georgio is here, she's a developer advocate for influx data and we're gonna dig into the rationale and value contribution behind several open source technologies that Influx DB is leveraging to increase the granularity of time series analysis analysis and bring the world of data into real-time analytics and is welcome to the program. Thanks for coming on. >>Hi, thank you so much. It's a pleasure to be here. >>Oh, you're very welcome. Okay, so IX is being touted as this next gen open source core for Influx db. And my understanding is that it leverages in memory of course for speed. It's a kilo store, so it gives you a compression efficiency, it's gonna give you faster query speeds, you store files and object storage, so you got very cost effective approach. Are these the salient points on the platform? I know there are probably dozens of other features, but what are the high level value points that people should understand? >>Sure, that's a great question. So some of the main requirements that IOx is trying to achieve and some of the most impressive ones to me, the first one is that it aims to have no limits on cardinality and also allow you to write any kind of event data that you want, whether that's live tag or a field. It also wants to deliver the best in class performance on analytics queries. In addition to our already well served metrics queries, we also wanna have operator control over memory usage. So you should be able to define how much memory is used for buffering caching and query processing. Some other really important parts is the ability to have bulk data export and import super useful. Also broader ecosystem compatibility where possible we aim to use and embrace emerging standards in the data analytics ecosystem and have compatibility with things like sql, Python, and maybe even pandas in the future. >>Okay, so lot there. Now we talked to Brian about how you're using Rust and which is not a new programming language and of course we had some drama around Rust during the pandemic with the Mozilla layoffs, but the formation of the Rust Foundation really addressed any of those concerns. You got big guns like Amazon and Google and Microsoft throwing their collective weights behind it. It's really, the adoption is really starting to get steep on the S-curve. So lots of platforms, lots of adoption with rust, but why rust as an alternative to say c plus plus for example? >>Sure, that's a great question. So Russ was chosen because of his exceptional performance and reliability. So while Russ is synt tactically similar to c plus plus and it has similar performance, it also compiles to a native code like c plus plus. But unlike c plus plus, it also has much better memory safety. So memory safety is protection against bugs or security vulnerabilities that lead to excessive memory usage or memory leaks. And rust achieves this memory safety due to its like innovative type system. Additionally, it doesn't allow for dangling pointers. And dangling pointers are the main classes of errors that lead to exploitable security vulnerabilities in languages like c plus plus. So Russ like helps meet that requirement of having no limits on ality, for example, because it's, we're also using the Russ implementation of Apache Arrow and this control over memory and also Russ Russ's packaging system called crates IO offers everything that you need out of the box to have features like AY and a weight to fix race conditions, to protection against buffering overflows and to ensure thread safe async cashing structures as well. So essentially it's just like has all the control, all the fine grain control, you need to take advantage of memory and all your resources as well as possible so that you can handle those really, really high ity use cases. >>Yeah, and the more I learn about the, the new engine and, and the platform IOCs et cetera, you know, you, you see things like, you know, the old days not even to even today you do a lot of garbage collection in these, in these systems and there's an inverse, you know, impact relative to performance. So it looks like you really, you know, the community is modernizing the platform, but I wanna talk about Apache Arrow for a moment. It it's designed to address the constraints that are associated with analyzing large data sets. We, we know that, but please explain why, what, what is Arrow and and what does it bring to Influx db? >>Sure, yeah. So Arrow is a, a framework for defining in memory calmer data. And so much of the efficiency and performance of IOx comes from taking advantage of calmer data structures. And I will, if you don't mind, take a moment to kind of of illustrate why column or data structures are so valuable. Let's pretend that we are gathering field data about the temperature in our room and also maybe the temperature of our stove. And in our table we have those two temperature values as well as maybe a measurement value, timestamp value, maybe some other tag values that describe what room and what house, et cetera we're getting this data from. And so you can picture this table where we have like two rows with the two temperature values for both our room and the stove. Well usually our room temperature is regulated so those values don't change very often. >>So when you have calm oriented st calm oriented storage, essentially you take each row, each column and group it together. And so if that's the case and you're just taking temperature values from the room and a lot of those temperature values are the same, then you'll, you might be able to imagine how equal values will then enable each other and when they neighbor each other in the storage format, this provides a really perfect opportunity for cheap compression. And then this cheap compression enables high cardinality use cases. It also enables for faster scan rates. So if you wanna define like the men and max value of the temperature in the room across a thousand different points, you only have to get those a thousand different points in order to answer that question and you have those immediately available to you. But let's contrast this with a row oriented storage solution instead so that we can understand better the benefits of calmer oriented storage. >>So if you had a row oriented storage, you'd first have to look at every field like the temperature in, in the room and the temperature of the stove. You'd have to go across every tag value that maybe describes where the room is located or what model the stove is. And every timestamp you'd then have to pluck out that one temperature value that you want at that one time stamp and do that for every single row. So you're scanning across a ton more data and that's why Rowe Oriented doesn't provide the same efficiency as calmer and Apache Arrow is in memory calmer data, commoner data fit framework. So that's where a lot of the advantages come >>From. Okay. So you basically described like a traditional database, a row approach, but I've seen like a lot of traditional database say, okay, now we've got, we can handle colo format versus what you're talking about is really, you know, kind of native i, is it not as effective? Is the, is the foreman not as effective because it's largely a, a bolt on? Can you, can you like elucidate on that front? >>Yeah, it's, it's not as effective because you have more expensive compression and because you can't scan across the values as quickly. And so those are, that's pretty much the main reasons why, why RO row oriented storage isn't as efficient as calm, calmer oriented storage. Yeah. >>Got it. So let's talk about Arrow Data Fusion. What is data fusion? I know it's written in Rust, but what does it bring to the table here? >>Sure. So it's an extensible query execution framework and it uses Arrow as it's in memory format. So the way that it helps in influx DB IOCs is that okay, it's great if you can write unlimited amount of cardinality into influx Cbis, but if you don't have a query engine that can successfully query that data, then I don't know how much value it is for you. So Data fusion helps enable the, the query process and transformation of that data. It also has a PANDAS API so that you could take advantage of PANDAS data frames as well and all of the machine learning tools associated with Pandas. >>Okay. You're also leveraging Par K in the platform cause we heard a lot about Par K in the middle of the last decade cuz as a storage format to improve on Hadoop column stores. What are you doing with Parque and why is it important? >>Sure. So parque is the column oriented durable file format. So it's important because it'll enable bulk import, bulk export, it has compatibility with Python and Pandas, so it supports a broader ecosystem. Par K files also take very little disc disc space and they're faster to scan because again, they're column oriented in particular, I think PAR K files are like 16 times cheaper than CSV files, just as kind of a point of reference. And so that's essentially a lot of the, the benefits of par k. >>Got it. Very popular. So and he's, what exactly is influx data focusing on as a committer to these projects? What is your focus? What's the value that you're bringing to the community? >>Sure. So Influx DB first has contributed a lot of different, different things to the Apache ecosystem. For example, they contribute an implementation of Apache Arrow and go and that will support clearing with flux. Also, there has been a quite a few contributions to data fusion for things like memory optimization and supportive additional SQL features like support for timestamp, arithmetic and support for exist clauses and support for memory control. So yeah, Influx has contributed a a lot to the Apache ecosystem and continues to do so. And I think kind of the idea here is that if you can improve these upstream projects and then the long term strategy here is that the more you contribute and build those up, then the more you will perpetuate that cycle of improvement and the more we will invest in our own project as well. So it's just that kind of symbiotic relationship and appreciation of the open source community. >>Yeah. Got it. You got that virtuous cycle going, the people call the flywheel. Give us your last thoughts and kind of summarize, you know, where what, what the big takeaways are from your perspective. >>So I think the big takeaway is that influx data is doing a lot of really exciting things with Influx DB IOx and I really encourage, if you are interested in learning more about the technologies that Influx is leveraging to produce IOCs, the challenges associated with it and all of the hard work questions and you just wanna learn more, then I would encourage you to go to the monthly Tech talks and community office hours and they are on every second Wednesday of the month at 8:30 AM Pacific time. There's also a community forums and a community Slack channel look for the influx DDB unders IAC channel specifically to learn more about how to join those office hours and those monthly tech tech talks as well as ask any questions they have about iacs, what to expect and what you'd like to learn more about. I as a developer advocate, I wanna answer your questions. So if there's a particular technology or stack that you wanna dive deeper into and want more explanation about how INFLUX DB leverages it to build IOCs, I will be really excited to produce content on that topic for you. >>Yeah, that's awesome. You guys have a really rich community, collaborate with your peers, solve problems, and, and you guys super responsive, so really appreciate that. All right, thank you so much Anise for explaining all this open source stuff to the audience and why it's important to the future of data. >>Thank you. I really appreciate it. >>All right, you're very welcome. Okay, stay right there and in a moment I'll be back with Tim Yoakum, he's the director of engineering for Influx Data and we're gonna talk about how you update a SAS engine while the plane is flying at 30,000 feet. You don't wanna miss this. >>I'm really glad that we went with InfluxDB Cloud for our hosting because it has saved us a ton of time. It's helped us move faster, it's saved us money. And also InfluxDB has good support. My name's Alex Nada. I am CTO at Noble nine. Noble Nine is a platform to measure and manage service level objectives, which is a great way of measuring the reliability of your systems. You can essentially think of an slo, the product we're providing to our customers as a bunch of time series. So we need a way to store that data and the corresponding time series that are related to those. The main reason that we settled on InfluxDB as we were shopping around is that InfluxDB has a very flexible query language and as a general purpose time series database, it basically had the set of features we were looking for. >>As our platform has grown, we found InfluxDB Cloud to be a really scalable solution. We can quickly iterate on new features and functionality because Influx Cloud is entirely managed, it probably saved us at least a full additional person on our team. We also have the option of running InfluxDB Enterprise, which gives us the ability to even host off the cloud or in a private cloud if that's preferred by a customer. Influx data has been really flexible in adapting to the hosting requirements that we have. They listened to the challenges we were facing and they helped us solve it. As we've continued to grow, I'm really happy we have influx data by our side. >>Okay, we're back with Tim Yokum, who is the director of engineering at Influx Data. Tim, welcome. Good to see you. >>Good to see you. Thanks for having me. >>You're really welcome. Listen, we've been covering open source software in the cube for more than a decade, and we've kind of watched the innovation from the big data ecosystem. The cloud has been being built out on open source, mobile, social platforms, key databases, and of course influx DB and influx data has been a big consumer and contributor of open source software. So my question to you is, where have you seen the biggest bang for the buck from open source software? >>So yeah, you know, influx really, we thrive at the intersection of commercial services and open, so open source software. So OSS keeps us on the cutting edge. We benefit from OSS in delivering our own service from our core storage engine technologies to web services temping engines. Our, our team stays lean and focused because we build on proven tools. We really build on the shoulders of giants and like you've mentioned, even better, we contribute a lot back to the projects that we use as well as our own product influx db. >>You know, but I gotta ask you, Tim, because one of the challenge that that we've seen in particular, you saw this in the heyday of Hadoop, the, the innovations come so fast and furious and as a software company you gotta place bets, you gotta, you know, commit people and sometimes those bets can be risky and not pay off well, how have you managed this challenge? >>Oh, it moves fast. Yeah, that, that's a benefit though because it, the community moves so quickly that today's hot technology can be tomorrow's dinosaur. And what we, what we tend to do is, is we fail fast and fail often. We try a lot of things. You know, you look at Kubernetes for example, that ecosystem is driven by thousands of intelligent developers, engineers, builders, they're adding value every day. So we have to really keep up with that. And as the stack changes, we, we try different technologies, we try different methods, and at the end of the day, we come up with a better platform as a result of just the constant change in the environment. It is a challenge for us, but it's, it's something that we just do every day. >>So we have a survey partner down in New York City called Enterprise Technology Research etr, and they do these quarterly surveys of about 1500 CIOs, IT practitioners, and they really have a good pulse on what's happening with spending. And the data shows that containers generally, but specifically Kubernetes is one of the areas that has kind of, it's been off the charts and seen the most significant adoption and velocity particularly, you know, along with cloud. But, but really Kubernetes is just, you know, still up until the right consistently even with, you know, the macro headwinds and all, all of the stuff that we're sick of talking about. But, so what are you doing with Kubernetes in the platform? >>Yeah, it, it's really central to our ability to run the product. When we first started out, we were just on AWS and, and the way we were running was, was a little bit like containers junior. Now we're running Kubernetes everywhere at aws, Azure, Google Cloud. It allows us to have a consistent experience across three different cloud providers and we can manage that in code so our developers can focus on delivering services, not trying to learn the intricacies of Amazon, Azure, and Google and figure out how to deliver services on those three clouds with all of their differences. >>Just to follow up on that, is it, no. So I presume it's sounds like there's a PAs layer there to allow you guys to have a consistent experience across clouds and out to the edge, you know, wherever is that, is that correct? >>Yeah, so we've basically built more or less platform engineering, This is the new hot phrase, you know, it, it's, Kubernetes has made a lot of things easy for us because we've built a platform that our developers can lean on and they only have to learn one way of deploying their application, managing their application. And so that, that just gets all of the underlying infrastructure out of the way and, and lets them focus on delivering influx cloud. >>Yeah, and I know I'm taking a little bit of a tangent, but is that, that, I'll call it a PAs layer if I can use that term. Is that, are there specific attributes to Influx db or is it kind of just generally off the shelf paths? You know, are there, is, is there any purpose built capability there that, that is, is value add or is it pretty much generic? >>So we really build, we, we look at things through, with a build versus buy through a, a build versus by lens. Some things we want to leverage cloud provider services, for instance, Postgres databases for metadata, perhaps we'll get that off of our plate, let someone else run that. We're going to deploy a platform that our engineers can, can deliver on that has consistency that is, is all generated from code that we can as a, as an SRE group, as an ops team, that we can manage with very few people really, and we can stamp out clusters across multiple regions and in no time. >>So how, so sometimes you build, sometimes you buy it. How do you make those decisions and and what does that mean for the, for the platform and for customers? >>Yeah, so what we're doing is, it's like everybody else will do, we're we're looking for trade offs that make sense. You know, we really want to protect our customers data. So we look for services that support our own software with the most uptime, reliability, and durability we can get. Some things are just going to be easier to have a cloud provider take care of on our behalf. We make that transparent for our own team. And of course for customers you don't even see that, but we don't want to try to reinvent the wheel, like I had mentioned with SQL data stores for metadata, perhaps let's build on top of what of these three large cloud providers have already perfected. And we can then focus on our platform engineering and we can have our developers then focus on the influx data, software, influx, cloud software. >>So take it to the customer level, what does it mean for them? What's the value that they're gonna get out of all these innovations that we've been been talking about today and what can they expect in the future? >>So first of all, people who use the OSS product are really gonna be at home on our cloud platform. You can run it on your desktop machine, on a single server, what have you, but then you want to scale up. We have some 270 terabytes of data across, over 4 billion series keys that people have stored. So there's a proven ability to scale now in terms of the open source, open source software and how we've developed the platform. You're getting highly available high cardinality time series platform. We manage it and, and really as, as I mentioned earlier, we can keep up with the state of the art. We keep reinventing, we keep deploying things in real time. We deploy to our platform every day repeatedly all the time. And it's that continuous deployment that allows us to continue testing things in flight, rolling things out that change new features, better ways of doing deployments, safer ways of doing deployments. >>All of that happens behind the scenes. And like we had mentioned earlier, Kubernetes, I mean that, that allows us to get that done. We couldn't do it without having that platform as a, as a base layer for us to then put our software on. So we, we iterate quickly. When you're on the, the Influx cloud platform, you really are able to, to take advantage of new features immediately. We roll things out every day and as those things go into production, you have, you have the ability to, to use them. And so in the end we want you to focus on getting actual insights from your data instead of running infrastructure, you know, let, let us do that for you. So, >>And that makes sense, but so is the, is the, are the innovations that we're talking about in the evolution of Influx db, do, do you see that as sort of a natural evolution for existing customers? I, is it, I'm sure the answer is both, but is it opening up new territory for customers? Can you add some color to that? >>Yeah, it really is it, it's a little bit of both. Any engineer will say, well, it depends. So cloud native technologies are, are really the hot thing. Iot, industrial iot especially, people want to just shove tons of data out there and be able to do queries immediately and they don't wanna manage infrastructure. What we've started to see are people that use the cloud service as their, their data store backbone and then they use edge computing with R OSS product to ingest data from say, multiple production lines and downsample that data, send the rest of that data off influx cloud where the heavy processing takes place. So really us being in all the different clouds and iterating on that and being in all sorts of different regions allows for people to really get out of the, the business of man trying to manage that big data, have us take care of that. And of course as we change the platform end users benefit from that immediately. And, >>And so obviously taking away a lot of the heavy lifting for the infrastructure, would you say the same thing about security, especially as you go out to IOT and the Edge? How should we be thinking about the value that you bring from a security perspective? >>Yeah, we take, we take security super seriously. It, it's built into our dna. We do a lot of work to ensure that our platform is secure, that the data we store is, is kept private. It's of course always a concern. You see in the news all the time, companies being compromised, you know, that's something that you can have an entire team working on, which we do to make sure that the data that you have, whether it's in transit, whether it's at rest, is always kept secure, is only viewable by you. You know, you look at things like software, bill of materials, if you're running this yourself, you have to go vet all sorts of different pieces of software. And we do that, you know, as we use new tools. That's something that, that's just part of our jobs to make sure that the platform that we're running it has, has fully vetted software and, and with open source especially, that's a lot of work. And so it's, it's definitely new territory. Supply chain attacks are, are definitely happening at a higher clip than they used to, but that is, that is really just part of a day in the, the life for folks like us that are, are building platforms. >>Yeah, and that's key. I mean especially when you start getting into the, the, you know, we talk about IOT and the operations technologies, the engineers running the, that infrastructure, you know, historically, as you know, Tim, they, they would air gap everything. That's how they kept it safe. But that's not feasible anymore. Everything's >>That >>Connected now, right? And so you've gotta have a partner that is again, take away that heavy lifting to r and d so you can focus on some of the other activities. Right. Give us the, the last word and the, the key takeaways from your perspective. >>Well, you know, from my perspective I see it as, as a a two lane approach with, with influx, with Anytime series data, you know, you've got a lot of stuff that you're gonna run on-prem, what you had mentioned, air gaping. Sure there's plenty of need for that, but at the end of the day, people that don't want to run big data centers, people that want torus their data to, to a company that's, that's got a full platform set up for them that they can build on, send that data over to the cloud, the cloud is not going away. I think more hybrid approach is, is where the future lives and that's what we're prepared for. >>Tim, really appreciate you coming to the program. Great stuff. Good to see you. >>Thanks very much. Appreciate it. >>Okay, in a moment I'll be back to wrap up. Today's session, you're watching The Cube. >>Are you looking for some help getting started with InfluxDB Telegraph or Flux Check >>Out Influx DB University >>Where you can find our entire catalog of free training that will help you make the most of your time series data >>Get >>Started for free@influxdbu.com. >>We'll see you in class. >>Okay, so we heard today from three experts on time series and data, how the Influx DB platform is evolving to support new ways of analyzing large data sets very efficiently and effectively in real time. And we learned that key open source components like Apache Arrow and the Rust Programming environment Data fusion par K are being leveraged to support realtime data analytics at scale. We also learned about the contributions in importance of open source software and how the Influx DB community is evolving the platform with minimal disruption to support new workloads, new use cases, and the future of realtime data analytics. Now remember these sessions, they're all available on demand. You can go to the cube.net to find those. Don't forget to check out silicon angle.com for all the news related to things enterprise and emerging tech. And you should also check out influx data.com. There you can learn about the company's products. You'll find developer resources like free courses. You could join the developer community and work with your peers to learn and solve problems. And there are plenty of other resources around use cases and customer stories on the website. This is Dave Valante. Thank you for watching Evolving Influx DB into the smart data platform, made possible by influx data and brought to you by the Cube, your leader in enterprise and emerging tech coverage.

>>This past May, The Cube in collaboration with Influx data shared with you the latest innovations in Time series databases. We talked at length about why a purpose built time series database for many use cases, was a superior alternative to general purpose databases trying to do the same thing. Now, you may, you may remember the time series data is any data that's stamped in time, and if it's stamped, it can be analyzed historically. And when we introduced the concept to the community, we talked about how in theory, those time slices could be taken, you know, every hour, every minute, every second, you know, down to the millisecond and how the world was moving toward realtime or near realtime data analysis to support physical infrastructure like sensors and other devices and IOT equipment. A time series databases have had to evolve to efficiently support realtime data in emerging use cases in iot T and other use cases. >>And to do that, new architectural innovations have to be brought to bear. As is often the case, open source software is the linchpin to those innovations. Hello and welcome to Evolving Influx DB into the smart Data platform, made possible by influx data and produced by the Cube. My name is Dave Valante and I'll be your host today. Now in this program we're going to dig pretty deep into what's happening with Time series data generally, and specifically how Influx DB is evolving to support new workloads and demands and data, and specifically around data analytics use cases in real time. Now, first we're gonna hear from Brian Gilmore, who is the director of IOT and emerging technologies at Influx Data. And we're gonna talk about the continued evolution of Influx DB and the new capabilities enabled by open source generally and specific tools. And in this program you're gonna hear a lot about things like Rust, implementation of Apache Arrow, the use of par k and tooling such as data fusion, which powering a new engine for Influx db. >>Now, these innovations, they evolve the idea of time series analysis by dramatically increasing the granularity of time series data by compressing the historical time slices, if you will, from, for example, minutes down to milliseconds. And at the same time, enabling real time analytics with an architecture that can process data much faster and much more efficiently. Now, after Brian, we're gonna hear from Anna East Dos Georgio, who is a developer advocate at In Flux Data. And we're gonna get into the why of these open source capabilities and how they contribute to the evolution of the Influx DB platform. And then we're gonna close the program with Tim Yokum, he's the director of engineering at Influx Data, and he's gonna explain how the Influx DB community actually evolved the data engine in mid-flight and which decisions went into the innovations that are coming to the market. Thank you for being here. We hope you enjoy the program. Let's get started. Okay, we're kicking things off with Brian Gilmore. He's the director of i t and emerging Technology at Influx State of Bryan. Welcome to the program. Thanks for coming on. >>Thanks Dave. Great to be here. I appreciate the time. >>Hey, explain why Influx db, you know, needs a new engine. Was there something wrong with the current engine? What's going on there? >>No, no, not at all. I mean, I think it's, for us, it's been about staying ahead of the market. I think, you know, if we think about what our customers are coming to us sort of with now, you know, related to requests like sql, you know, query support, things like that, we have to figure out a way to, to execute those for them in a way that will scale long term. And then we also, we wanna make sure we're innovating, we're sort of staying ahead of the market as well and sort of anticipating those future needs. So, you know, this is really a, a transparent change for our customers. I mean, I think we'll be adding new capabilities over time that sort of leverage this new engine, but you know, initially the customers who are using us are gonna see just great improvements in performance, you know, especially those that are working at the top end of the, of the workload scale, you know, the massive data volumes and things like that. >>Yeah, and we're gonna get into that today and the architecture and the like, but what was the catalyst for the enhancements? I mean, when and how did this all come about? >>Well, I mean, like three years ago we were primarily on premises, right? I mean, I think we had our open source, we had an enterprise product, you know, and, and sort of shifting that technology, especially the open source code base to a service basis where we were hosting it through, you know, multiple cloud providers. That was, that was, that was a long journey I guess, you know, phase one was, you know, we wanted to host enterprise for our customers, so we sort of created a service that we just managed and ran our enterprise product for them. You know, phase two of this cloud effort was to, to optimize for like multi-tenant, multi-cloud, be able to, to host it in a truly like sass manner where we could use, you know, some type of customer activity or consumption as the, the pricing vector, you know, And, and that was sort of the birth of the, of the real first influx DB cloud, you know, which has been really successful. >>We've seen, I think like 60,000 people sign up and we've got tons and tons of, of both enterprises as well as like new companies, developers, and of course a lot of home hobbyists and enthusiasts who are using out on a, on a daily basis, you know, and having that sort of big pool of, of very diverse and very customers to chat with as they're using the product, as they're giving us feedback, et cetera, has has, you know, pointed us in a really good direction in terms of making sure we're continuously improving that and then also making these big leaps as we're doing with this, with this new engine. >>Right. So you've called it a transparent change for customers, so I'm presuming it's non-disruptive, but I really wanna understand how much of a pivot this is and what, what does it take to make that shift from, you know, time series, you know, specialist to real time analytics and being able to support both? >>Yeah, I mean, it's much more of an evolution, I think, than like a shift or a pivot. You know, time series data is always gonna be fundamental and sort of the basis of the solutions that we offer our customers, and then also the ones that they're building on the sort of raw APIs of our platform themselves. You know, the time series market is one that we've worked diligently to lead. I mean, I think when it comes to like metrics, especially like sensor data and app and infrastructure metrics, if we're being honest though, I think our, our user base is well aware that the way we were architected was much more towards those sort of like backwards looking historical type analytics, which are key for troubleshooting and making sure you don't, you know, run into the same problem twice. But, you know, we had to ask ourselves like, what can we do to like better handle those queries from a performance and a, and a, you know, a time to response on the queries, and can we get that to the point where the results sets are coming back so quickly from the time of query that we can like limit that window down to minutes and then seconds. >>And now with this new engine, we're really starting to talk about a query window that could be like returning results in, in, you know, milliseconds of time since it hit the, the, the ingest queue. And that's, that's really getting to the point where as your data is available, you can use it and you can query it, you can visualize it, and you can do all those sort of magical things with it, you know? And I think getting all of that to a place where we're saying like, yes to the customer on, you know, all of the, the real time queries, the, the multiple language query support, but, you know, it was hard, but we're now at a spot where we can start introducing that to, you know, a a limited number of customers, strategic customers and strategic availability zones to start. But you know, everybody over time. >>So you're basically going from what happened to in, you can still do that obviously, but to what's happening now in the moment? >>Yeah, yeah. I mean if you think about time, it's always sort of past, right? I mean, like in the moment right now, whether you're talking about like a millisecond ago or a minute ago, you know, that's, that's pretty much right now, I think for most people, especially in these use cases where you have other sort of components of latency induced by the, by the underlying data collection, the architecture, the infrastructure, the, you know, the, the devices and you know, the sort of highly distributed nature of all of this. So yeah, I mean, getting, getting a customer or a user to be able to use the data as soon as it is available is what we're after here. >>I always thought, you know, real, I always thought of real time as before you lose the customer, but now in this context, maybe it's before the machine blows up. >>Yeah, it's, it's, I mean it is operationally or operational real time is different, you know, and that's one of the things that really triggered us to know that we were, we were heading in the right direction, is just how many sort of operational customers we have. You know, everything from like aerospace and defense. We've got companies monitoring satellites, we've got tons of industrial users, users using us as a processes storing on the plant floor, you know, and, and if we can satisfy their sort of demands for like real time historical perspective, that's awesome. I think what we're gonna do here is we're gonna start to like edge into the real time that they're used to in terms of, you know, the millisecond response times that they expect of their control systems, certainly not their, their historians and databases. >>I, is this available, these innovations to influx DB cloud customers only who can access this capability? >>Yeah. I mean commercially and today, yes. You know, I think we want to emphasize that's a, for now our goal is to get our latest and greatest and our best to everybody over time. Of course. You know, one of the things we had to do here was like we double down on sort of our, our commitment to open source and availability. So like anybody today can take a look at the, the libraries in on our GitHub and, you know, can ex inspect it and even can try to, you know, implement or execute some of it themselves in their own infrastructure. You know, we are, we're committed to bringing our sort of latest and greatest to our cloud customers first for a couple of reasons. Number one, you know, there are big workloads and they have high expectations of us. I think number two, it also gives us the opportunity to monitor a little bit more closely how it's working, how they're using it, like how the system itself is performing. >>And so just, you know, being careful, maybe a little cautious in terms of, of, of how big we go with this right away, just sort of both limits, you know, the risk of, of, you know, any issues that can come with new software rollouts. We haven't seen anything so far, but also it does give us the opportunity to have like meaningful conversations with a small group of users who are using the products, but once we get through that and they give us two thumbs up on it, it'll be like, open the gates and let everybody in. It's gonna be exciting time for the whole ecosystem. >>Yeah, that makes a lot of sense. And you can do some experimentation and, you know, using the cloud resources. Let's dig into some of the architectural and technical innovations that are gonna help deliver on this vision. What, what should we know there? >>Well, I mean, I think foundationally we built the, the new core on Rust. You know, this is a new very sort of popular systems language, you know, it's extremely efficient, but it's also built for speed and memory safety, which goes back to that us being able to like deliver it in a way that is, you know, something we can inspect very closely, but then also rely on the fact that it's going to behave well. And if it does find error conditions, I mean we, we've loved working with Go and, you know, a lot of our libraries will continue to, to be sort of implemented in Go, but you know, when it came to this particular new engine, you know, that power performance and stability rust was critical. On top of that, like, we've also integrated Apache Arrow and Apache Parque for persistence. I think for anybody who's really familiar with the nuts and bolts of our backend and our TSI and our, our time series merged Trees, this is a big break from that, you know, arrow on the sort of in MI side and then Par K in the on disk side. >>It, it allows us to, to present, you know, a unified set of APIs for those really fast real time inquiries that we talked about, as well as for very large, you know, historical sort of bulk data archives in that PARQUE format, which is also cool because there's an entire ecosystem sort of popping up around Parque in terms of the machine learning community, you know, and getting that all to work, we had to glue it together with aero flight. That's sort of what we're using as our, our RPC component. You know, it handles the orchestration and the, the transportation of the Coer data. Now we're moving to like a true Coer database model for this, this version of the engine, you know, and it removes a lot of overhead for us in terms of having to manage all that serialization, the deserialization, and, you know, to that again, like blurring that line between real time and historical data. It's, you know, it's, it's highly optimized for both streaming micro batch and then batches, but true streaming as well. >>Yeah. Again, I mean, it's funny you mentioned Rust. It is, it's been around for a long time, but it's popularity is, is you know, really starting to hit that steep part of the S-curve. And, and we're gonna dig into to more of that, but give us any, is there anything else that we should know about Bryan? Give us the last word? >>Well, I mean, I think first I'd like everybody sort of watching just to like take a look at what we're offering in terms of early access in beta programs. I mean, if, if, if you wanna participate or if you wanna work sort of in terms of early access with the, with the new engine, please reach out to the team. I'm sure you know, there's a lot of communications going out and you know, it'll be highly featured on our, our website, you know, but reach out to the team, believe it or not, like we have a lot more going on than just the new engine. And so there are also other programs, things we're, we're offering to customers in terms of the user interface, data collection and things like that. And, you know, if you're a customer of ours and you have a sales team, a commercial team that you work with, you can reach out to them and see what you can get access to because we can flip a lot of stuff on, especially in cloud through feature flags. >>But if there's something new that you wanna try out, we'd just love to hear from you. And then, you know, our goal would be that as we give you access to all of these new cool features that, you know, you would give us continuous feedback on these products and services, not only like what you need today, but then what you'll need tomorrow to, to sort of build the next versions of your business. Because you know, the whole database, the ecosystem as it expands out into to, you know, this vertically oriented stack of cloud services and enterprise databases and edge databases, you know, it's gonna be what we all make it together, not just, you know, those of us who were employed by Influx db. And then finally I would just say please, like watch in ICE in Tim's sessions, like these are two of our best and brightest, They're totally brilliant, completely pragmatic, and they are most of all customer obsessed, which is amazing. And there's no better takes, like honestly on the, the sort of technical details of this, then there's, especially when it comes to like the value that these investments will, will bring to our customers and our communities. So encourage you to, to, you know, pay more attention to them than you did to me, for sure. >>Brian Gilmore, great stuff. Really appreciate your time. Thank you. >>Yeah, thanks Dave. It was awesome. Look forward to it. >>Yeah, me too. Looking forward to see how the, the community actually applies these new innovations and goes, goes beyond just the historical into the real time really hot area. As Brian said in a moment, I'll be right back with Anna East dos Georgio to dig into the critical aspects of key open source components of the Influx DB engine, including Rust, Arrow, Parque, data fusion. Keep it right there. You don't wanna miss this >>Time series Data is everywhere. The number of sensors, systems and applications generating time series data increases every day. All these data sources producing so much data can cause analysis paralysis. Influx DB is an entire platform designed with everything you need to quickly build applications that generate value from time series data influx. DB Cloud is a serverless solution, which means you don't need to buy or manage your own servers. There's no need to worry about provisioning because you only pay for what you use. Influx DB Cloud is fully managed so you get the newest features and enhancements as they're added to the platform's code base. It also means you can spend time building solutions and delivering value to your users instead of wasting time and effort managing something else. Influx TVB Cloud offers a range of security features to protect your data, multiple layers of redundancy ensure you don't lose any data access controls ensure that only the people who should see your data can see it. >>And encryption protects your data at rest and in transit between any of our regions or cloud providers. InfluxDB uses a single API across the entire platform suite so you can build on open source, deploy to the cloud and then then easily query data in the cloud at the edge or on prem using the same scripts. And InfluxDB is schemaless automatically adjusting to changes in the shape of your data without requiring changes in your application. Logic. InfluxDB Cloud is production ready from day one. All it needs is your data and your imagination. Get started today@influxdata.com slash cloud. >>Okay, we're back. I'm Dave Valante with a Cube and you're watching evolving Influx DB into the smart data platform made possible by influx data. Anna ETOs Georgio is here, she's a developer advocate for influx data and we're gonna dig into the rationale and value contribution behind several open source technologies that Influx DB is leveraging to increase the granularity of time series analysis analysis and bring the world of data into real-time analytics and is welcome to the program. Thanks for coming on. >>Hi, thank you so much. It's a pleasure to be here. >>Oh, you're very welcome. Okay, so IX is being touted as this next gen open source core for Influx db. And my understanding is that it leverages in memory of course for speed. It's a kilo store, so it gives you a compression efficiency, it's gonna give you faster query speeds, you store files and object storage, so you got very cost effective approach. Are these the salient points on the platform? I know there are probably dozens of other features, but what are the high level value points that people should understand? >>Sure, that's a great question. So some of the main requirements that IOx is trying to achieve and some of the most impressive ones to me, the first one is that it aims to have no limits on cardinality and also allow you to write any kind of event data that you want, whether that's live tag or a field. It also wants to deliver the best in class performance on analytics queries. In addition to our already well served metrics queries, we also wanna have operator control over memory usage. So you should be able to define how much memory is used for buffering caching and query processing. Some other really important parts is the ability to have bulk data export and import super useful. Also broader ecosystem compatibility where possible we aim to use and embrace emerging standards in the data analytics ecosystem and have compatibility with things like sql, Python, and maybe even pandas in the future. >>Okay, so lot there. Now we talked to Brian about how you're using Rust and which is not a new programming language and of course we had some drama around Rust during the pandemic with the Mozilla layoffs, but the formation of the Rust Foundation really addressed any of those concerns. You got big guns like Amazon and Google and Microsoft throwing their collective weights behind it. It's really, the adoption is really starting to get steep on the S-curve. So lots of platforms, lots of adoption with rust, but why rust as an alternative to say c plus plus for example? >>Sure, that's a great question. So Russ was chosen because of his exceptional performance and reliability. So while Russ is synt tactically similar to c plus plus and it has similar performance, it also compiles to a native code like c plus plus. But unlike c plus plus, it also has much better memory safety. So memory safety is protection against bugs or security vulnerabilities that lead to excessive memory usage or memory leaks. And rust achieves this memory safety due to its like innovative type system. Additionally, it doesn't allow for dangling pointers. And dangling pointers are the main classes of errors that lead to exploitable security vulnerabilities in languages like c plus plus. So Russ like helps meet that requirement of having no limits on ality, for example, because it's, we're also using the Russ implementation of Apache Arrow and this control over memory and also Russ Russ's packaging system called crates IO offers everything that you need out of the box to have features like AY and a weight to fix race conditions, to protection against buffering overflows and to ensure thread safe async cashing structures as well. So essentially it's just like has all the control, all the fine grain control, you need to take advantage of memory and all your resources as well as possible so that you can handle those really, really high ity use cases. >>Yeah, and the more I learn about the, the new engine and, and the platform IOCs et cetera, you know, you, you see things like, you know, the old days not even to even today you do a lot of garbage collection in these, in these systems and there's an inverse, you know, impact relative to performance. So it looks like you really, you know, the community is modernizing the platform, but I wanna talk about Apache Arrow for a moment. It it's designed to address the constraints that are associated with analyzing large data sets. We, we know that, but please explain why, what, what is Arrow and and what does it bring to Influx db? >>Sure, yeah. So Arrow is a, a framework for defining in memory calmer data. And so much of the efficiency and performance of IOx comes from taking advantage of calmer data structures. And I will, if you don't mind, take a moment to kind of of illustrate why column or data structures are so valuable. Let's pretend that we are gathering field data about the temperature in our room and also maybe the temperature of our stove. And in our table we have those two temperature values as well as maybe a measurement value, timestamp value, maybe some other tag values that describe what room and what house, et cetera we're getting this data from. And so you can picture this table where we have like two rows with the two temperature values for both our room and the stove. Well usually our room temperature is regulated so those values don't change very often. >>So when you have calm oriented st calm oriented storage, essentially you take each row, each column and group it together. And so if that's the case and you're just taking temperature values from the room and a lot of those temperature values are the same, then you'll, you might be able to imagine how equal values will then enable each other and when they neighbor each other in the storage format, this provides a really perfect opportunity for cheap compression. And then this cheap compression enables high cardinality use cases. It also enables for faster scan rates. So if you wanna define like the men and max value of the temperature in the room across a thousand different points, you only have to get those a thousand different points in order to answer that question and you have those immediately available to you. But let's contrast this with a row oriented storage solution instead so that we can understand better the benefits of calmer oriented storage. >>So if you had a row oriented storage, you'd first have to look at every field like the temperature in, in the room and the temperature of the stove. You'd have to go across every tag value that maybe describes where the room is located or what model the stove is. And every timestamp you'd then have to pluck out that one temperature value that you want at that one time stamp and do that for every single row. So you're scanning across a ton more data and that's why Rowe Oriented doesn't provide the same efficiency as calmer and Apache Arrow is in memory calmer data, commoner data fit framework. So that's where a lot of the advantages come >>From. Okay. So you basically described like a traditional database, a row approach, but I've seen like a lot of traditional database say, okay, now we've got, we can handle colo format versus what you're talking about is really, you know, kind of native i, is it not as effective? Is the, is the foreman not as effective because it's largely a, a bolt on? Can you, can you like elucidate on that front? >>Yeah, it's, it's not as effective because you have more expensive compression and because you can't scan across the values as quickly. And so those are, that's pretty much the main reasons why, why RO row oriented storage isn't as efficient as calm, calmer oriented storage. Yeah. >>Got it. So let's talk about Arrow Data Fusion. What is data fusion? I know it's written in Rust, but what does it bring to the table here? >>Sure. So it's an extensible query execution framework and it uses Arrow as it's in memory format. So the way that it helps in influx DB IOCs is that okay, it's great if you can write unlimited amount of cardinality into influx Cbis, but if you don't have a query engine that can successfully query that data, then I don't know how much value it is for you. So Data fusion helps enable the, the query process and transformation of that data. It also has a PANDAS API so that you could take advantage of PANDAS data frames as well and all of the machine learning tools associated with Pandas. >>Okay. You're also leveraging Par K in the platform cause we heard a lot about Par K in the middle of the last decade cuz as a storage format to improve on Hadoop column stores. What are you doing with Parque and why is it important? >>Sure. So parque is the column oriented durable file format. So it's important because it'll enable bulk import, bulk export, it has compatibility with Python and Pandas, so it supports a broader ecosystem. Par K files also take very little disc disc space and they're faster to scan because again, they're column oriented in particular, I think PAR K files are like 16 times cheaper than CSV files, just as kind of a point of reference. And so that's essentially a lot of the, the benefits of par k. >>Got it. Very popular. So and he's, what exactly is influx data focusing on as a committer to these projects? What is your focus? What's the value that you're bringing to the community? >>Sure. So Influx DB first has contributed a lot of different, different things to the Apache ecosystem. For example, they contribute an implementation of Apache Arrow and go and that will support clearing with flux. Also, there has been a quite a few contributions to data fusion for things like memory optimization and supportive additional SQL features like support for timestamp, arithmetic and support for exist clauses and support for memory control. So yeah, Influx has contributed a a lot to the Apache ecosystem and continues to do so. And I think kind of the idea here is that if you can improve these upstream projects and then the long term strategy here is that the more you contribute and build those up, then the more you will perpetuate that cycle of improvement and the more we will invest in our own project as well. So it's just that kind of symbiotic relationship and appreciation of the open source community. >>Yeah. Got it. You got that virtuous cycle going, the people call the flywheel. Give us your last thoughts and kind of summarize, you know, where what, what the big takeaways are from your perspective. >>So I think the big takeaway is that influx data is doing a lot of really exciting things with Influx DB IOx and I really encourage, if you are interested in learning more about the technologies that Influx is leveraging to produce IOCs, the challenges associated with it and all of the hard work questions and you just wanna learn more, then I would encourage you to go to the monthly Tech talks and community office hours and they are on every second Wednesday of the month at 8:30 AM Pacific time. There's also a community forums and a community Slack channel look for the influx DDB unders IAC channel specifically to learn more about how to join those office hours and those monthly tech tech talks as well as ask any questions they have about iacs, what to expect and what you'd like to learn more about. I as a developer advocate, I wanna answer your questions. So if there's a particular technology or stack that you wanna dive deeper into and want more explanation about how INFLUX DB leverages it to build IOCs, I will be really excited to produce content on that topic for you. >>Yeah, that's awesome. You guys have a really rich community, collaborate with your peers, solve problems, and, and you guys super responsive, so really appreciate that. All right, thank you so much Anise for explaining all this open source stuff to the audience and why it's important to the future of data. >>Thank you. I really appreciate it. >>All right, you're very welcome. Okay, stay right there and in a moment I'll be back with Tim Yoakum, he's the director of engineering for Influx Data and we're gonna talk about how you update a SAS engine while the plane is flying at 30,000 feet. You don't wanna miss this. >>I'm really glad that we went with InfluxDB Cloud for our hosting because it has saved us a ton of time. It's helped us move faster, it's saved us money. And also InfluxDB has good support. My name's Alex Nada. I am CTO at Noble nine. Noble Nine is a platform to measure and manage service level objectives, which is a great way of measuring the reliability of your systems. You can essentially think of an slo, the product we're providing to our customers as a bunch of time series. So we need a way to store that data and the corresponding time series that are related to those. The main reason that we settled on InfluxDB as we were shopping around is that InfluxDB has a very flexible query language and as a general purpose time series database, it basically had the set of features we were looking for. >>As our platform has grown, we found InfluxDB Cloud to be a really scalable solution. We can quickly iterate on new features and functionality because Influx Cloud is entirely managed, it probably saved us at least a full additional person on our team. We also have the option of running InfluxDB Enterprise, which gives us the ability to even host off the cloud or in a private cloud if that's preferred by a customer. Influx data has been really flexible in adapting to the hosting requirements that we have. They listened to the challenges we were facing and they helped us solve it. As we've continued to grow, I'm really happy we have influx data by our side. >>Okay, we're back with Tim Yokum, who is the director of engineering at Influx Data. Tim, welcome. Good to see you. >>Good to see you. Thanks for having me. >>You're really welcome. Listen, we've been covering open source software in the cube for more than a decade, and we've kind of watched the innovation from the big data ecosystem. The cloud has been being built out on open source, mobile, social platforms, key databases, and of course influx DB and influx data has been a big consumer and contributor of open source software. So my question to you is, where have you seen the biggest bang for the buck from open source software? >>So yeah, you know, influx really, we thrive at the intersection of commercial services and open, so open source software. So OSS keeps us on the cutting edge. We benefit from OSS in delivering our own service from our core storage engine technologies to web services temping engines. Our, our team stays lean and focused because we build on proven tools. We really build on the shoulders of giants and like you've mentioned, even better, we contribute a lot back to the projects that we use as well as our own product influx db. >>You know, but I gotta ask you, Tim, because one of the challenge that that we've seen in particular, you saw this in the heyday of Hadoop, the, the innovations come so fast and furious and as a software company you gotta place bets, you gotta, you know, commit people and sometimes those bets can be risky and not pay off well, how have you managed this challenge? >>Oh, it moves fast. Yeah, that, that's a benefit though because it, the community moves so quickly that today's hot technology can be tomorrow's dinosaur. And what we, what we tend to do is, is we fail fast and fail often. We try a lot of things. You know, you look at Kubernetes for example, that ecosystem is driven by thousands of intelligent developers, engineers, builders, they're adding value every day. So we have to really keep up with that. And as the stack changes, we, we try different technologies, we try different methods, and at the end of the day, we come up with a better platform as a result of just the constant change in the environment. It is a challenge for us, but it's, it's something that we just do every day. >>So we have a survey partner down in New York City called Enterprise Technology Research etr, and they do these quarterly surveys of about 1500 CIOs, IT practitioners, and they really have a good pulse on what's happening with spending. And the data shows that containers generally, but specifically Kubernetes is one of the areas that has kind of, it's been off the charts and seen the most significant adoption and velocity particularly, you know, along with cloud. But, but really Kubernetes is just, you know, still up until the right consistently even with, you know, the macro headwinds and all, all of the stuff that we're sick of talking about. But, so what are you doing with Kubernetes in the platform? >>Yeah, it, it's really central to our ability to run the product. When we first started out, we were just on AWS and, and the way we were running was, was a little bit like containers junior. Now we're running Kubernetes everywhere at aws, Azure, Google Cloud. It allows us to have a consistent experience across three different cloud providers and we can manage that in code so our developers can focus on delivering services, not trying to learn the intricacies of Amazon, Azure, and Google and figure out how to deliver services on those three clouds with all of their differences. >>Just to follow up on that, is it, no. So I presume it's sounds like there's a PAs layer there to allow you guys to have a consistent experience across clouds and out to the edge, you know, wherever is that, is that correct? >>Yeah, so we've basically built more or less platform engineering, This is the new hot phrase, you know, it, it's, Kubernetes has made a lot of things easy for us because we've built a platform that our developers can lean on and they only have to learn one way of deploying their application, managing their application. And so that, that just gets all of the underlying infrastructure out of the way and, and lets them focus on delivering influx cloud. >>Yeah, and I know I'm taking a little bit of a tangent, but is that, that, I'll call it a PAs layer if I can use that term. Is that, are there specific attributes to Influx db or is it kind of just generally off the shelf paths? You know, are there, is, is there any purpose built capability there that, that is, is value add or is it pretty much generic? >>So we really build, we, we look at things through, with a build versus buy through a, a build versus by lens. Some things we want to leverage cloud provider services, for instance, Postgres databases for metadata, perhaps we'll get that off of our plate, let someone else run that. We're going to deploy a platform that our engineers can, can deliver on that has consistency that is, is all generated from code that we can as a, as an SRE group, as an ops team, that we can manage with very few people really, and we can stamp out clusters across multiple regions and in no time. >>So how, so sometimes you build, sometimes you buy it. How do you make those decisions and and what does that mean for the, for the platform and for customers? >>Yeah, so what we're doing is, it's like everybody else will do, we're we're looking for trade offs that make sense. You know, we really want to protect our customers data. So we look for services that support our own software with the most uptime, reliability, and durability we can get. Some things are just going to be easier to have a cloud provider take care of on our behalf. We make that transparent for our own team. And of course for customers you don't even see that, but we don't want to try to reinvent the wheel, like I had mentioned with SQL data stores for metadata, perhaps let's build on top of what of these three large cloud providers have already perfected. And we can then focus on our platform engineering and we can have our developers then focus on the influx data, software, influx, cloud software. >>So take it to the customer level, what does it mean for them? What's the value that they're gonna get out of all these innovations that we've been been talking about today and what can they expect in the future? >>So first of all, people who use the OSS product are really gonna be at home on our cloud platform. You can run it on your desktop machine, on a single server, what have you, but then you want to scale up. We have some 270 terabytes of data across, over 4 billion series keys that people have stored. So there's a proven ability to scale now in terms of the open source, open source software and how we've developed the platform. You're getting highly available high cardinality time series platform. We manage it and, and really as, as I mentioned earlier, we can keep up with the state of the art. We keep reinventing, we keep deploying things in real time. We deploy to our platform every day repeatedly all the time. And it's that continuous deployment that allows us to continue testing things in flight, rolling things out that change new features, better ways of doing deployments, safer ways of doing deployments. >>All of that happens behind the scenes. And like we had mentioned earlier, Kubernetes, I mean that, that allows us to get that done. We couldn't do it without having that platform as a, as a base layer for us to then put our software on. So we, we iterate quickly. When you're on the, the Influx cloud platform, you really are able to, to take advantage of new features immediately. We roll things out every day and as those things go into production, you have, you have the ability to, to use them. And so in the end we want you to focus on getting actual insights from your data instead of running infrastructure, you know, let, let us do that for you. So, >>And that makes sense, but so is the, is the, are the innovations that we're talking about in the evolution of Influx db, do, do you see that as sort of a natural evolution for existing customers? I, is it, I'm sure the answer is both, but is it opening up new territory for customers? Can you add some color to that? >>Yeah, it really is it, it's a little bit of both. Any engineer will say, well, it depends. So cloud native technologies are, are really the hot thing. Iot, industrial iot especially, people want to just shove tons of data out there and be able to do queries immediately and they don't wanna manage infrastructure. What we've started to see are people that use the cloud service as their, their data store backbone and then they use edge computing with R OSS product to ingest data from say, multiple production lines and downsample that data, send the rest of that data off influx cloud where the heavy processing takes place. So really us being in all the different clouds and iterating on that and being in all sorts of different regions allows for people to really get out of the, the business of man trying to manage that big data, have us take care of that. And of course as we change the platform end users benefit from that immediately. And, >>And so obviously taking away a lot of the heavy lifting for the infrastructure, would you say the same thing about security, especially as you go out to IOT and the Edge? How should we be thinking about the value that you bring from a security perspective? >>Yeah, we take, we take security super seriously. It, it's built into our dna. We do a lot of work to ensure that our platform is secure, that the data we store is, is kept private. It's of course always a concern. You see in the news all the time, companies being compromised, you know, that's something that you can have an entire team working on, which we do to make sure that the data that you have, whether it's in transit, whether it's at rest, is always kept secure, is only viewable by you. You know, you look at things like software, bill of materials, if you're running this yourself, you have to go vet all sorts of different pieces of software. And we do that, you know, as we use new tools. That's something that, that's just part of our jobs to make sure that the platform that we're running it has, has fully vetted software and, and with open source especially, that's a lot of work. And so it's, it's definitely new territory. Supply chain attacks are, are definitely happening at a higher clip than they used to, but that is, that is really just part of a day in the, the life for folks like us that are, are building platforms. >>Yeah, and that's key. I mean especially when you start getting into the, the, you know, we talk about IOT and the operations technologies, the engineers running the, that infrastructure, you know, historically, as you know, Tim, they, they would air gap everything. That's how they kept it safe. But that's not feasible anymore. Everything's >>That >>Connected now, right? And so you've gotta have a partner that is again, take away that heavy lifting to r and d so you can focus on some of the other activities. Right. Give us the, the last word and the, the key takeaways from your perspective. >>Well, you know, from my perspective I see it as, as a a two lane approach with, with influx, with Anytime series data, you know, you've got a lot of stuff that you're gonna run on-prem, what you had mentioned, air gaping. Sure there's plenty of need for that, but at the end of the day, people that don't want to run big data centers, people that want torus their data to, to a company that's, that's got a full platform set up for them that they can build on, send that data over to the cloud, the cloud is not going away. I think more hybrid approach is, is where the future lives and that's what we're prepared for. >>Tim, really appreciate you coming to the program. Great stuff. Good to see you. >>Thanks very much. Appreciate it. >>Okay, in a moment I'll be back to wrap up. Today's session, you're watching The Cube. >>Are you looking for some help getting started with InfluxDB Telegraph or Flux Check >>Out Influx DB University >>Where you can find our entire catalog of free training that will help you make the most of your time series data >>Get >>Started for free@influxdbu.com. >>We'll see you in class. >>Okay, so we heard today from three experts on time series and data, how the Influx DB platform is evolving to support new ways of analyzing large data sets very efficiently and effectively in real time. And we learned that key open source components like Apache Arrow and the Rust Programming environment Data fusion par K are being leveraged to support realtime data analytics at scale. We also learned about the contributions in importance of open source software and how the Influx DB community is evolving the platform with minimal disruption to support new workloads, new use cases, and the future of realtime data analytics. Now remember these sessions, they're all available on demand. You can go to the cube.net to find those. Don't forget to check out silicon angle.com for all the news related to things enterprise and emerging tech. And you should also check out influx data.com. There you can learn about the company's products. You'll find developer resources like free courses. You could join the developer community and work with your peers to learn and solve problems. And there are plenty of other resources around use cases and customer stories on the website. This is Dave Valante. Thank you for watching Evolving Influx DB into the smart data platform, made possible by influx data and brought to you by the Cube, your leader in enterprise and emerging tech coverage.

>> Okay, so we heard today from three experts on time series and data, how the InfluxDB platform is evolving to support new ways of analyzing large data sets very efficiently and effectively in realtime. And we learned that key open source components like Apache Arrow and the Rust Programming environment DataFusion parquet are being leveraged to support realtime data analytics at scale. We also learned about the contributions and importance of open source software and how the InfluxDB community is evolving the platform with minimal disruption to support new workloads, new use cases in the future of realtime data analytics. Now remember these sessions, they're all available on demand. You can go to thecube.net to find those. Don't forget to check out siliconangle.com for all the news related to things enterprise and emerging tech. And you should also check out influxdata.com. There you can learn about the company's products, you'll find developer resources like free courses, you can join the developer community and work with your peers to learn and solve problems, and there are plenty of other resources around use cases and customer stories on the website. This is Dave Vellante. Thank you for watching Evolving InfluxDB into the Smart Data Platform, made possible by InfluxData and brought to you by theCUBE, your leader in enterprise and emerging tech coverage.

>> This past May, the Cube, in collaboration with Influx Data shared with you the latest innovations in Time series databases. We talked at length about why a purpose-built time series database for many use cases, was a superior alternative to general purpose databases trying to do the same thing. Now, you may, you may remember that time series data is any data that's stamped in time and if it's stamped, it can be analyzed historically. And when we introduced the concept to the community we talked about how in theory those time slices could be taken, you know every hour, every minute, every second, you know, down to the millisecond and how the world was moving toward realtime or near realtime data analysis to support physical infrastructure like sensors, and other devices and IOT equipment. Time series databases have had to evolve to efficiently support realtime data in emerging use, use cases in IOT and other use cases. And to do that, new architectural innovations have to be brought to bear. As is often the case, open source software is the linchpin to those innovations. Hello and welcome to Evolving Influx DB into the Smart Data platform, made possible by influx data and produced by the cube. My name is Dave Vellante, and I'll be your host today. Now, in this program, we're going to dig pretty deep into what's happening with Time series data generally, and specifically how Influx DB is evolving to support new workloads and demands and data, and specifically around data analytics use cases in real time. Now, first we're going to hear from Brian Gilmore who is the director of IOT and emerging technologies at Influx Data. And we're going to talk about the continued evolution of Influx DB and the new capabilities enabled by open source generally and specific tools. And in this program, you're going to hear a lot about things like rust implementation of Apache Arrow, the use of Parquet and tooling such as data fusion, which are powering a new engine for Influx db. Now, these innovations, they evolve the idea of time series analysis by dramatically increasing the granularity of time series data by compressing the historical time slices if you will, from, for example minutes down to milliseconds. And at the same time, enabling real time analytics with an architecture that can process data much faster and much more efficiently. Now, after Brian, we're going to hear from Anais Dotis-Georgiou who is a developer advocate at Influx Data. And we're going to get into the "why's" of these open source capabilities, and how they contribute to the evolution of the Influx DB platform. And then we're going to close the program with Tim Yocum. He's the director of engineering at Influx Data, and he's going to explain how the Influx DB community actually evolved the data engine in mid-flight and which decisions went into the innovations that are coming to the market. Thank you for being here. We hope you enjoy the program. Let's get started.

from the cube studios in palo alto in boston bringing you data driven insights from the cube and etr this is breaking analysis with dave vellante earnings season has shown a conflicting mix of signals for software companies well virtually all firms are expressing caution over so-called macro headwinds we're talking about ukraine inflation interest rates europe fx headwinds supply chain just overall i.t spend mongodb along with a few other names appeared more sanguine thanks to a beat in the recent quarter and a cautious but upbeat outlook for the near term hello and welcome to this week's wikibon cube insights powered by etr in this breaking analysis ahead of mongodb world 2022 we drill into mongo's business and what etr survey data tells us in the context of overall demand and the patterns that we're seeing from other software companies and we're seeing some distinctly different results from major firms these days we'll talk more about [ __ ] in this session which beat eps by 30 cents in revenue by more than 18 million dollars salesforce had a great quarter and its diversified portfolio is paying off as seen by the stocks noticeable uptick post earnings uipath which had been really beaten down prior to this quarter it's brought in a new co-ceo and it's business is showing a nice rebound with a small three cent eps beat and a nearly 20 million dollar top line beat crowdstrike is showing strength as well meanwhile managements at microsoft workday and snowflake expressed greater caution about the macroeconomic climate and especially on investors minds his concern about consumption pricing models snowflake in particular which had a small top-line beat cited softness and effects from reduced consumption especially from certain consumer-facing customers which has analysts digging more deeply into the predictability of their models in fact barclays analyst ramo lenchow published an especially thoughtful piece on this topic concluding that [ __ ] was less susceptible to consumption headwinds than for example snowflake essentially for a few reasons one because atlas mongo's cloud managed service which is the consumption model comprises only about 60 percent of mongo's revenue second is the premise that [ __ ] is supporting core operational applications that can't be easily dialed down or turned off and three that snowflake customers it sounds like has a more concentrated customer base and due to that fact there's a preponderance of its revenue is consumption driven and would be more sensitive to swings in these consumption patterns now i'll say this first consumption pricing models are here to stay and the much preferred model for customers is consumption the appeal of consumption is i can actually dial down turn off if i need to and stop spending for a while which happened or at least happened to a certain extent this quarter for certain companies but to the point about [ __ ] supporting core applications i do believe that over time you're going to see the increased emergence of data products that will become core monetization drivers in snowflake along with other data platforms is going to feed those data products and services and become over time maybe less susceptible and less sensitive to these consumption patterns it'll always be there but i think increasingly it's going to be tied to operational revenue last two points here in this slide software evaluations have reverted to their historical mean which is a good thing in our view we've taken some air out of the bubble and returned to more normalized valuations was really predicted and looked forward to look we're still in a lousy market for stocks it's really a bear market for tech the market tends to be at least six months ahead of the economy and often not always but often is a good predictor we've had some tough compares relative to the pandemic days in tech and we'll be watching next quarter very closely because the macro headwinds have now been firmly inserted into the guidance of software companies okay let's have a look at how certain names have performed relative to a software index benchmark so far this year here's a year-to-date chart comparing microsoft salesforce [ __ ] and snowflake to the igv software heavy etf which is shown in the darker blue line which by the way it does not own the ctf does not own snowflake or [ __ ] you can see that these big super caps have fared pretty well whereas [ __ ] and especially snowflake those higher growth companies have been much more negatively impacted year to date from a stock price standpoint now let's move on let's take a financial snapshot of [ __ ] and put it next to snowflake so we can compare these two higher growth names what we've done here in this chart has taken the most recent quarters revenue and multiplied it by 4x to get a revenue run rate and we've parenthetically added a projection for the full year revenue [ __ ] as you see will do north of a billion dollars in revenue while snowflake will begin to approach three billion dollars 2.7 and run right through that that four quarter run rate that they just had last quarter and you can see snowflake is growing faster than [ __ ] at 85 percent this past quarter and we took now these most of these profit of these next profitability ratios off the current quarter with one exception both companies have high gross margins of course you'd expect that but as we've discussed not as high as some traditional software companies in part because of their cloud costs but also you know their maturity or lack thereof both [ __ ] and snowflake because they are in high growth mode have thin operating margins they spend nearly half or more than half of their revenue on growth that's the sg a line mostly the s the sales and marketing is really where they're spending money uh and and they're specialists so they spend a fair amount of their revenue on r d but maybe not as high as you might think but a pretty hefty percentage the free cash flow as a percentage of revenue line we calculated off the full year projections because there was a kind of an anomaly this quarter in the in the snowflake numbers and you can see snowflakes free cash flow uh which again was abnormally high this quarter is going to settle in around 16 this year versus mongo's six percent so strong focus by snowflake on free cash flow and its management snowflake is about four billion dollars in cash and marketable securities on its balance sheet with little or no debt whereas [ __ ] has about two billion dollars on its balance sheet with a little bit of longer term debt and you can see snowflakes market cap is about double that of mongos so you're paying for higher growth with snowflake you're paying for the slootman scarpelli execution engine the expectation there a stronger balance sheet etc but snowflake is well off its roughly 100 billion evaluation which it touched during the peak days of tech during the pandemic and just that as an aside [ __ ] has around 33 000 customers about five times the number of customers snowflake has so a bit of a different customer mix and concentration but both companies in our view have no lack of market in terms of tam okay now let's dig a little deeper into mongo's business and bring in some etr data this colorful chart shows the breakdown of mongo's net score net score is etr's proprietary methodology that measures the percent of customers in the etr survey that are adding the platform new that's the lime green at nine percent existing customers that are spending six percent or more on the platform that's the forest green at 37 spending flat that's the gray at 46 percent decreasing spend that's the pinkish at around 5 and churning that's only 3 that's the bright red for [ __ ] subtract the red from the greens and you net out to a 38 which is a very solid net score figure note this is a survey of 1500 or so organizations and it includes 150 mongodb customers which includes by the way 68 global 2000 customers and they show a spending velocity or a net score of 44 so notably higher among the larger clients and while it's a smaller sample only 27 emea's net score for [ __ ] is 33 now that's down from 60 last quarter note that [ __ ] cited softness in its european business on its earning calls so that aligns to the gtr data okay now let's plot [ __ ] relative to some other data platforms these don't all necessarily compete head to head with [ __ ] but they are in data and database platforms in the etr data set and that's what this chart shows it's an xy graph with net score or as we say spending momentum on the vertical axis and overlap or presence or pervasiveness in the data set on the horizontal axis see that red dotted line there at 40 that indicates an elevated level of spending anything above that is highly elevated we've highlighted [ __ ] in that red box which is very close to that 40 percent line it has a pretty strong presence on the x-axis right there with gcp snowflake as we've reported has come down to earth but still well elevated again that aligns with the earnings releases uh aws and microsoft they have many data platforms especially aws so their plot position reflects their broad portfolio massive size on the x-axis um that's the presence and and very impressive on the vertical axis so despite that size they have strong spending momentum and you can see the pack of others including cockroach small on the verdict on the horizontal but elevated on the vertical couch base is creeping up since its ipo redis maria db which was launched the day that oracle bought sun and and got my sequel and some legacy platforms including the leader in database oracle as well as ibm and teradata's both cloud and on-prem platforms now one interesting side note here is on mongo's earning call it clearly cited the advantages of its increasingly all-in-one approach relative to others that offer a portfolio of bespoke or what we some sometimes call horses for courses databases [ __ ] cited the advantages of its simplicity and lower costs as it adds more and more functionality this is an argument often made by oracle and they often target aws as the company with too many databases and of course [ __ ] makes that argument uh as well but they also make the argument that oracle they don't necessarily call them out but they talk about traditional relational databases of course they're talking about oracle and others they say that's more complex less flexible and less appealing to developers than is [ __ ] now oracle of course would retur we retort saying hey we now support a mongodb api so why go anywhere else we're the most robust and the best for mission critical but this gives credence to the fact that if oracle is trying to capture business by offering a [ __ ] api for example that [ __ ] must be doing something right okay let's look at why they buy [ __ ] here's an etr chart that addresses that question it's it's mongo's feature breadth is the number one reason lower cost or better roi is number two integrations and stack alignment is third and mongo's technology lead is fourth those four kind of stand out with notice on the right hand side security and vision much lower there in the right that doesn't necessarily mean that [ __ ] doesn't have good security and and good vision although it has been cited uh security concerns um and and so we keep an eye on that but look [ __ ] has a document database it's become a viable alternative to traditional relational databases meaning you have much more flexibility over your schema um and in fact you know it's kind of schema-less you can pretty much put anything into a document database uh developers seem to love it generally it's fair to say mongo's architecture would favor consistency over availability because it uses a single master architecture as a primary and you can create secondary nodes in the event of a primary failure but you got to think about that and how to architect availability into the platform and got to consider recovery more carefully now now no schema means it's not a tables and rows structure and you can again shove anything you want into the database but you got to think about how to optimize performance um on queries now [ __ ] has been hard at work evolving the platform from the early days when you go back and look at its roadmap it's been you know started as a document database purely it added graph processing time series it's made search you know much much easier and more fundamental it's added atlas that fully managed cloud database uh service which we said now comprises 60 of its revenue it's you know kubernetes integrations and kind of the modern microservices stack and dozens and dozens and dozens of other features mongo's done a really fine job we think of creating a leading database platform today that is loved by customers loved by developers and is highly functional and next week the cube will be at mongodb world and we'll be looking for some of these items that we're showing here and this this chart this always going to be main focus on developers [ __ ] prides itself on being a developer friendly platform we're going to look for new features especially around security and governance and simplification of configurations and cluster management [ __ ] is likely going to continue to advance its all-in-one appeal and add more capabilities that reduce the need to to spin up bespoke platforms and we would expect enhance enhancements to atlas further enhancements there is atlas really is the future you know maybe adding you know more cloud native features and integrations and perhaps simplified ways to migrate to the cloud to atlas and improve access to data sources generally making the lives of developers and data analysts easier that's going to be we think a big theme at the event so these are the main things that we'll be scoping out at the event so please stop by if you're in new york city new york city at mongodb world or tune in to thecube.net okay that's it for today thanks to my colleagues stephanie chan who helps research breaking analysis from time to time alex meyerson is on production as today is as is andrew frick sarah kenney steve conte conte anderson hill and the entire team in palo alto thank you kristen martin and cheryl knight helped get the word out and rob hof is our editor-in-chief over there at siliconangle remember all these episodes are available as podcasts wherever you listen just search breaking analysis podcast we do publish each week on wikibon.com and siliconangle.com want to reach me email me david.velante siliconangle.com or dm me at divalante or a comment on my linkedin post and please do check out etr.ai for the best survey data in the enterprise tech business this is dave vellante for the cube insights powered by etr thanks for watching see you next time [Music] you

>>Hey, everyone, Thanks for taking them to join the story. Hope you and your loved ones are safe during these tough times. Let me start by introducing myself. My name is Michelle. When I walk for GlaxoSmithKline, GSK as an engineering manager in my current role, A little protocol platform A P s, which is part of the already data platform here in G S, K R and D Tech. I live in Dallas, Texas. I have a Masters degree in computer science on a bachelor's in electronics and communication engineering. I started my career as a software developer on over these years again a lot of experience in leading and building, not scale and predicts products and solutions. I also have a complete accountability for container platforms here at GSK or any tick. I've been working very closely with Dr Enterprise, which is no Miranda's for more than three years to enable container platforms that yes, came on mainly in our own Itek. So that's me. Let >>me give you a quick overview on agenda for today's talk. I'll start with what we do here at GSK on what is RND data platform. Then I'll give you an overview on What are the business drivers that >>motivated US toe? Take this container Germany on some insight into learnings on accomplishments over these years. Working with Dr Enterprise on the container platforms Lately, you must have seen a lot of articles off there which talk about how ts case liberating technologies like artificial intelligence, mission learning, UN data and analytics for the Douglas Corey process. I'm very excited to see the progress we have made in technology, but what makes us truly unique is our commitment to the patient. >>We're G escape, help millions of people, do more, feel better and live longer. Wear a global company that is focused on three were tickles pharmaceuticals vaccines on consumer healthcare. Our main intent is to lower the >>burden on the impact of diseases on the patients. Here at GSK, we allow science to drive the technology. This helps us toe build innovative products. That's helps our scientists to make better and faster additions throughout the drug discovery by plane. >>With that, let me give you some >>context on what currently data platform is how it is enabled. A T escape started in mid 2016. What used to be called us are any information platform whose main focus was to centralize curate on rationalized all the data produced within the others are in the business systems in orderto drive, a strategic business value, standardization of clinical trials, Genome Wide Association Study Analysis, also known as Jesus Storage and Crossing Off Rheal. World Evidence data some of the examples off how the only platform was used to deliver the business value four years later. No, a new set off business rivals of changing our landscape. The irony Information Platform is evolving to be a hybrid, multi cloud solution and is known as already did a platform refering to 20 >>19 GSK's annual report. These are the four teams that there are any platform will be mainly focused on. We're expanding our data capabilities to support the use. Escape by a former company on evolving into a hybrid medical platform is one of the many steps that we're taking to be future ready. Our key focus will still be making >>greater recommendations better and faster by using that wants us. We're making the areas like artificial intelligence and machine learning. No doc brings us toe. What is Germany is important. Why are we taking this German with that? Let me take you to the next topic off. Like the process of discovery, Francisco is not an easy process. Talking about the recent events occurred over the last few months on the way. How all our lives are impacted. It is a lot of talk on information going about. Why did drug discovery process is so tough working for a global health care company? I get asked this question very frequently. From many people I interact with. Question is like, Why is that? This car is so tough on why it takes so much time. Drug discovery is a complex process that involves multiple different stages on at each and every stage. There is huge amounts of data that the scientists have took process to make some decisions. Studies have shown that only 3% off small molecules entering the human studies actually become medicines. If you're new to drug discovery, you may ask, like what is the targets? Targets so low? We humans are very complex species, >>not going into the details of the process. We're G escape >>have made a lot of investments into technology that enabled us to make data river conditions. Throw the drug Discovery pipeline >>as we implement. As we started implementing these tools and technologies to enable already did a platform, we started to get a better appreciation off how these tools in track on integrate >>with each other. Our goal wants to make this platform a jail, the platform that can work at scale so that we can provide a great user experience and contribute back to the bread discovery pipeline so that the scientists can make faster editions. We want our ardently users to consume the data, and the service is available on the platform seamlessly in a self service fashion. And we also have to accomplish this by establishing trust. And then we have to end also enable the academic partnerships, acquisitions, collaborations that DSK has, which actually brings a lot of data on value to our scientists. So when we talk about so many collaborations and a lot of these systems, what this brings in is wide range off systems and platforms that are fundamentally built on different infrastructure. This is where Doctor comes into fiction on our containers significance. >>We have realized the power of containers on how we can simplify this complex ecosystem by using containers and provide a faster access off data to war scientists who didn't go >>back and contribute back to the drug discovery by play. >>With that, let me take talk to you about >>the containers journey and she escaped. So we started our container journey in late 2017. We started working with Dr Enterprise to enable the container platform. This is on our on prem infrastructure Back then, or first year or so we walked through multiple Pelosis did a lot of testing to make sure our platform is stable before we onboard either the data or the user applications. I was part of this complete journey on Dr Stream has worked with us very closely towards you. The first milestone off establishing a stable container platform. A tsk. Now, getting into 2019 we started deploying our applications in production environment. I cannot go into the details of what this Absar, but they do include both data pipelines as well as Web services. You know, initial days we have worked a lot on swamp, but in 2019 is when we started looking into communities in the same year, we enable kubernetes orchestration on the doctor and replace platform here at GSK and also made it as a de facto orchestra coming into 2020. All our micro service applications are undead. A pipelines are migrated to the container platforms on all of these are orchestrated by Cuban additional on these air applications that are running in production. As of today, we have made the container forced approach as an architectural standard across already taking GSK. We also started deploying our AML training models onto containers on All this work is happening on our Doctor Enterprise platform. Also as part off are currently platforms hybrid multicolored journey. We started enabling container and kubernetes based platforms on public clubs. Now going into 2021 on future. Enabling our RND users to easily access data and applications in a platform agnostic way is very crucial for our success because previously we had only onto him. Now we have public clothes that are getting involved on One of >>the many steps we're taking through this journey is to >>watch allies the data on ship data and containers or kubernetes volumes on demand to our our end users of scientists. And this allows us to deliver data to our scientists wherever they want in a very security on. We're leveraging doctor to do it. So that's >>our future. Learning on with that, let's take a deep dive into fuel for >>our accomplishments over these years. I want to start with a general demand and innovative one very interesting use case that we developed on Dr. This is a rapid prototyping capability that enabled our scientists seamlessly to Monday cluster communication. This was one off the biggest challenges which way his face for a long time and with the help of containers, were able to solve this on provide this as a capability to our scientists. We actually have shockers this capability in one of the doctor conferences before next. As I've said before, by migrating all over web services into containers, we not only achieved horizontal scalability for those specific services, but also saved more than 50% in support costs for the applications which we have migrated by making Docker image as an immutable artifact In our bill process, we are now able to deploy our APS or models in any container or Cuban, its base platform, either in on Prem or in a public club. We also made significant improvements towards the process. A not a mission By leveraging docker containers, containers have played a significant role in keeping US platform agnostic and thus enabling our hybrid multi cloud Germany valuable for out already did scientists. As I mentioned before, data virtualization is another viewpoint we have in terms off our next steps off where we want to take kubernetes on where we wanna leverage open it. Us. What you see here are just a few off many accomplishments which we have our, um, achieved by using containers for the past three years or so. So with that before I close all the time and acknowledge all our internal partners who has contributed a lot to this journey mainly are in the business are on the deck on the broader take. Organizations that escape also want to time document present Miranda's for being such a great partner throughout this journey and also giving us an opportunity to share this success story today. Lastly, thanks for everyone to listening to the stop and please feel free to reach out. If you have any questions or suggestions, let's be fit safe. Thank you

from our studios in the heart of Silicon Valley Palo Alto California this is a cute conversation hi I'm Peter Burris analyst wiki Bond welcome to another wiki Bond the cube digital community event this one's sponsored by HPE like all of our digital community events this one will feature about 25 minutes of video followed by a crowd chat which will be your opportunity to ask your questions share your experiences and push forward the community's thinking on important issues facing business today so what are we talking about today over the course of the last say six months or so we've had a lot of conversations with our customers about the core issues that multi-cloud is going to engender with in business one of them clearly is how do we bring greater intelligence to how we move manage and administer data within the enterprise some of the more interesting conversations we've had turns out to have been with HPE and that's what we're going to talk about today we're going to be spending a few minutes with a number of HPE professionals as well as wiki bond professionals and thought leaders talking about the challenges that enterprises face as a consider intelligent data platforms so let's get started the first conversation that we're going to talk about is with Sandeep Singh who is the vice president at HPE Sandeep let's have that conversation about the challenges facing business today as it pertains to data so Sandeep I started off by making the observation that we've got this mountain of data coming in a lot of enterprises at the same time there seems to be a the the notion of how data is going to create new classes of business value seems to be pretty deeply ingrained and acculturated to a lot of decision-makers so they want more value out of their data but they're increasingly concerned about the volume of data that's going to hit them how in your conversations with customers are you hearing them talk about this fundamental challenge so that that's a great question you know across the board data is at the heart of applications pretty much everything that organizations do and when they look at it in conversations with customers it really boils down to a couple of areas one is how is my data just effortlessly available all the time it's always fast because fundamentally that's driving the speed of my business and that's incredibly important and how can my various audiences including developers just consume it like the public cloud in a self-service fashion and then the second part of that conversation is really about this massive data storm or mountain of data that's coming and it's gonna be available how do how do I Drive a competitive advantage how do i unlock these hidden insights in that data to uncover new revenue streams new customer experiences those are the areas that we hear about and fundamentally underlying it the challenge for customers is boy I have a lot of complexity and how do I ensure that I have the necessary insights in a the infrastructure management so I am not beholden am or my IT staff isn't beholden to fighting the IT fires that can cause disruptions and delays to projects so fundamentally we want to be able to push time and attention in the infrastructure in the administration of those devices that handle the data and move that time and attention up into how we deliver the data services and ideally up into the applications that are going to actually generate a new class of work within a digital business so I got that right absolutely it's about infrastructure that just runs seamlessly it's always on it's always fast people don't have to worry about what is it gonna go down is my data available or is it gonna slow down people don't want sometimes faster one always fast right I and that's governing the application performance that ultimately I can deliver and you talked about while geez if it if the data infrastructure just work seamlessly then can I eventually get to the applications and building the right pipelines ultimately for mining that data drive doing the AI and the machine learning analytics driven insides from there great discussion about the importance of data in the enterprise and how it's changing the way we think about business we're going to come back to Sandeep shortly but first let's spend some time talking with David floor who's the wiki bond analyst about the new mindset that is required to take advantage of some of these technologies and solve some of these problems specifically we need to think increasingly about data services let's hear what David has to say explain what that new mindset is yes I completely agree that that new mindset is required and it starts with you want to be able to deal with data wherever it's gonna be you in we are in a hybrid world hybrid cloud world your own clouds other public clouds partner clouds all of these need to be integrated and data is at the core of it so that the requirement then is to have rather than think about each individual piece is to think about services which are going to be applied to that data and can be applied not only to the data in one place but across all of that data and there isn't such a thing is just one set of services there going to be multiple sets of these services available but hope we will see some degree of conversion so they'll be the same lexicon and conceptual etcetera there'll be the same levels of things that are needed within each of these architectures but there'll be different emphasis on different areas we need to look at the way we administer data as a set of services that create outcomes for the business and as opposed to that are then translated into individual devices let me so let's jump into this notion of of what those services look like it seems as though we can list off a couple of them sure yeah so we must have of data reduction techniques so you must have deduplication compression type of techniques and you want to apply that our crosses bigger an amount of data as you can the more data you apply those the higher the levels of compression and deduplication you can get so that's clearly you've got those sort of sets of services across there you must backup and restore data in another place and be able to restore it quickly and easily there's that again is a service how quickly how integrated that recovery again that's going to be a variable that's a differentiation in the service exactly you're going to need data data protection in general end to end protection of once or another for example you need end-to-end encryption across there it's no longer good enough to say this bits been encrypted and then this bits the encrypted has got to be an end-to-end from one location to another location seamlessly provided that sort of thing well let me let me let me press on it cuz I think it's a really important point and and and it's you know the notion that the weakest link determines the strength of the chain right the what you just described says if you have encryption here and you don't have encryption there but because of the nature of digital you can start you start bringing that data together guess what the weakest link determines the protection of the overall data absolutely yes and then you need services like snapshots like like other services which provide much better usage of that data one of the great things about flash and that's brought about this about is that you can take a copy of that in real time and use that first totally different purpose and have that being changed in a different way so there are some really significantly great improvements you can have with services like snapshots and then you need some other services which are becoming even more important in my opinion the advent of [Music] bad actors in the in the world has really bought about the requirement for things like air gaps to have your data with the metadata all in one place and completely separated from everything else there are such things as called logical air gaps I think they as long as they're real in the real sense that the two paths can't interfere with each other those are going to be services which become very very important that's generally as an example of a general class of security data services they require so ultimately what we're describing is we're describing a new mindset that says that a storage administrator has to think about the services that the applications in the business requires and then seek out technologies that can provide those services at the price point with the degree of power consumption in the space or the environmental or with the type of maintenance and services related support that required based on the physical location the degree to which is under their control etc so that kind of what how we're thinking about this I think absolutely and the again if there's going to be multiple of these around in the marketplace one size is not going to fit all yeah you if you're wanting super fast response time at an edge and and if you don't get that response in time it's going to be no use whatsoever you're going to take you're going to have a different architecture a different way of doing it then if you need to be a hundred percent certain that every bit is captured and you know in a financial sort of environment but from a service standpoint you want to be able to look at that specific solution in a common way current policies current bilities correct great observations by David Flor it's very clear that for enterprises to get more control over their data their data assets and how they create value out of data they have to take a services mentality but the challenge that we all face is just taking a service mentality is not going to be enough we have to think about how we're going to organize those services into a platform that is pertinent and relevant to how business operates in a digital sense so let's go back to Sandeep saying and talk to him a little bit about this HPE notion of the intelligent data platform you've been one of the leaders in the complex systems arena for a long time and that includes storage where are you guys taking some of these technologies yeah so our strategy is to deliver an intelligent data platform and that intelligent data platform begins with workload optimized composable systems that can span the mission critical workloads general purpose secondary Big Data ai workloads we also deliver cloud data services that enable you to embrace hybrid cloud all of these systems including all the way to cloud data services are plumbed with data mobility and so for example use cases of even modernizing protection and going all the way to protecting cost effectively in the public cloud are enabled but really all of these systems then are imbued with a level of intelligence with a global intelligence engine that begins with predicting and proactively resolving issues before they occur but it goes way beyond that in delivering these prescriptive insights that are built on top of global learning across hundreds of thousands of systems with over a billion data points coming in on a daily basis to be able to deliver at the information at the fingertips of even the virtual machine admins to say this virtual machine is sapping the performance of this node and if you were to move it to this other node the performance or the SLA for all of the virtual machine farm will be even better we build on top of that to deliver pre-built automation so that it's hooked in with a REST API for strategy so that developers can consume it in a containerized application that's orchestrated with kubernetes or they can leverage it as an infrastructure as code whether it's with ansible puppet or chef we accelerate all of the application workloads and bring up where data protection and so it's available for the traditional business applications whether they're built on sa P or Oracle or sequel or the virtual machine farms or the new stack containerized applications and then customers can build their AI and big data pipelines on top of the infrastructure with a plethora of tools whether they're using basically Kafka lastic map our h2o that complete flexibility exists and within HPE were then able to turn around and deliver all of this with an as a service experience with HPE Greenlake to customers so that's where I want to take you next so how invasive is this going to be to a large shop well it is completely seamless in that way so with Greenlake we're able to deliver a fully managed service experience where the a cloud like page you go consumption model and combining it with HPE financial services we're also able to transform their organization in terms of this journey and make it a fully self-funding journey as well so today the typical administrator the typical shop has got a bunch of administrators that are administrating devices that's starting to change they've introduced automation that typically is associated with those devices but if we think three to five years out folks going to be thinking more in terms of data services and how those services get consumed and that's going to be what the storage part of I t's going to be thinking about they can almost become day to administrators if I got that right yes intelligence is fundamentally changing everything not only on the consumer side but on the business side of it a lot of what we've been talking about is intelligence is the game changer we actually see the dawn of the intelligence era and through this AI driven experience what it means for customers as a it enables a support experience that they just absolutely love secondly it means that the infrastructure is always on it's always fast it's always optimized in that sense and thirdly in terms of making these data services that are available and data insights that are being unlocked it's all about how can you enable your innovators and the data scientists and the data analysts to shrink that time to deriving insights from months literally down to minutes today there's this chasm that exists where there's a great concept of how can i leverage the AI technology and between that concept to making it real to thinking about a where can I actually fit and then how do i implement an end-to-end solution and a technology stack so then I just have a pipeline that's available to me that chasm literally is a matter of months and what we're able to deliver for example with HPE blue data is literally a catalog self-service experience where you can select and seamlessly build a pipeline literally in a matter of minutes and it's just all completely hosted seamlessly so making AI and machine learning essentially available for the mainstream through so the ontology data platform makes it possible to see these new classes of applications become routine without forcing the underlying storage administrators themselves to become data scientists absolutely all right the intelligent data platform is a very great concept but it's got to be made real and it's being made real today by HP Calvin Zito's a thought leader at HPE and he's done a series of chalk talks as it pertains to improving storage improving data management one of the more interesting ones was specifically on the intelligent data platform let's watch Calvin Zito's chalk talk hey guys I love it's time for another around the storage black chalk talk in this chalk top we're gonna look at the intelligent Data Platform let me set up the discussion at HP we see the dawn of the intelligence error the flatshare brought a speed with flash flash is now table stakes the cloud era brought new levels of agility and everyone expects as a service experience going forward the intelligence era with an AI driven experience for infrastructure operations in AI enabled unlocking of insights is poised to catapult businesses forward so the intelligent era will see the rise of the intelligent enterprise the enterprise will be always on always fast always agile to respond to different challenges but most of all the intelligent enterprise will be built for innovation innovation that can ilish new services revenue streams and business models every enterprise will need to have an intelligent data strategy where your data is always on and always fast automated an on-demand hybrid by design and applies global intelligence for visibility and lifecycle management our strategy is to deliver an intelligent data platform that turns your data challenges into business opportunities it begins with workload optimized composable systems for multiple workloads and we deliver cloud services for a hybrid cloud environment so that you can seamlessly move data throughout its lifecycle I'll have more on this in a moment the global intelligence engine infuses the entire infrastructure with intelligence it starts with predicting and proactively resolving issues before they occur it creates a unique workload fingerprint and these workload fingerprints combined with global learning enable us to drive recommendations to keep your app workloads and supporting infrastructure always optimized and delivering predictable speed we have a REST API first strategy and offer pre build automation connectors we bring Apple wear protection for both traditional and modern new stack application workloads and you can use the intelligent data platform to build and deliver flexible big data and AI pipelines for driving real-time analytics let's take a quick look at the portfolio of workload optimized composable systems these are systems across mission-critical general-purpose workloads as well secondary data and solutions for the emerging big data and AI applications because our portfolio is built for the cloud we offer comprehensive cloud data services for both production workloads and backup and archive in the cloud HPE info site provides the global intelligence across the portfolio and we give you flexibility of consuming these solutions as a service with HPE Greenlake I want to close with one more thing the HPE intelligent data platform has three main attributes first it's AI driven it removes the burden of managing infrastructure so that IT can focus on innovating and not administrating second it's built for cloud and it enables easy data and workload mobility across hybrid cloud environments finally the intelligent data platform delivers and as a service experience so you can be your own cloud provider to learn more go to hp.com intelligent data always love to hear from you on Twitter where you can find me as calvin zito you can find my blog at hp.com slash blog until next time thanks for joining me on this around the storage black chalk talk I think Calvin makes a compelling case that the opportunity to use these technologies is available today not something that we're just going to wait for in the future and that's good because one of the most important things that business has to think about is how are they going to utilize some of these new AI and related technologies to alter the way that they engage their customers run their businesses and handle their operations and ultimately improve their overall efficiency and effectiveness in the marketplaces it's very clear that this intelligent data platform is required to do many of the advanced AI things that business wants to do but it also requires AI in the platform itself so let's go back to Sandeep Singh and talk to Sandeep about how HPE foresees AI being embedded in them into the intelligent data platform so it can make possible greater utilization of AI and the rest of the application portfolio so we've got the significant problem we now have to figure out how to architect because we want predictability and certainty and and cost clarity and to how we're going to do this part of the challenge or part of the pushers new use cases for AI so we're trying to push data up so that we can build these new use cases but it seems that we have to also have to take some of those very same technologies and drive them down into the infrastructure so we get greater intelligence greater self meter and greater self management self administration within the infrastructure itself I got that right yes absolutely what becomes important for customers is when you think about data and ultimately storage that underlies the data is you can build and deploy fast and reliable storage but that's only solving half the problem greater than 50% of the issues actually end up arising from the higher layers for example you could change the firmware on the host bus adapter inside a server that can trickle down and cause a data unavailability or a performance slowdown issue you need to be able to predict that all the way at that higher level and then prevent that from occurring or your virtual machines might be in a state of over memory commitment at the server level or you CPU over commitment how do you discover those issues and prevent them from happening the other area that's becoming important is when we talk about this whole notion of cloud and hybrid cloud right that complexity tends to multiply exponentially so when the smarts you guys are going after building that hybrid cloud infrastructure fundamental challenges even as I've got a new workload and I want to place that you even on premises because you've had lots of silos how do you even figure out where should I place a workload a and how it'll react with workloads B and C on a given system and now you multiply that across hundreds of systems multiple clouds and the challenge you can see that it's multiplying exponentially oh yeah well I would say that having you know where do I put workload a the right answer today maybe here but the right answer tomorrow maybe some where else and you want to make sure that the service is right required to perform workload a our resident and available without a lot of administrative work necessary to ensure that there's commonality that's kind of what we mean by this hybrid multi cloud world isn't it absolutely and you when you start to think about it basically you end up in requiring and fundamentally needing the data mobility aspect of it because without the data you can't really move your workloads and you need consistency of data services so that your app if it's architected for reliability and a set of data services those just go along with the application and then you need building on top of that the portability for your actual application workload consistently managed with a hybrid management interface there so we want to use an intelligent data platform that's capable of assuring performance assuring availability and assuring security and going beyond that to then deliver a simplified automated experience right so that everything is just available through a self-service interface and then it brings along a level of intelligence that's just built into it globally so that in instead of trying to manually predict and landing in a world of reactive after IT fires have occurred is that there are sea of sensors and it's automatic the infrastructures automatically for predicting and preventing issues before they ever occur and then going beyond that how can you actually fingerprint the individual application workloads to then deliver prescriptive insights right to keep the infrastructure always optimized in that sense so discerning the patterns of data utilization so that the administrative costs of making sure the data is available where it needs to be number one number two assuring that data as assets is made available to developers as they create new applications new new things that create new work but also working very closely with the administrators so that they are not bound [Music] as you know an explosion in the number of tasks adapt to perform to keep this all working across the board yes I want to thank Sandeep Singh and calvin zito both of HPE as well as wiki bonds David Floyd for sharing their ideas on this crucially important topic of how we're going to take more of a platform approach to do a better job of managing crucial data assets in today's and tomorrow's digital businesses I'm Peter Burris and this has been another wiki bomb the cube digital community event sponsored by HPE now stay tuned for our crowd chat which will be your opportunity to ask your questions share your experiences and push for the community's thinking on important issues facing business today thank you very much for watching and now let's crouch [Music]

>> Hi. This is Dave Vellante with theCUBE, and we're running a series of events with various episodes. The first one is that the intelligence data platform. I'm here with Terry Richardson of HPE. Terry, what's that all about? >> So intelligent in a platform is really the rebranding of our complete storage offering, but it transcends into our infrastructure compute infrastructure. So what you'LL learn on this particular session is what makes HPE absolutely unique in this marketplace, leveraging are for the data center technology. >> So watch this CrowdChat will be holding events. We said we have episodes will be flowing in how twos and white papers and other great content will see you in the CrowdChat.

(upbeat music) >> Welcome back everyone to The Cubes coverage here in Seattle, Washington. For AWS's Marketplace Seller Conference. It's the big news within the Amazon partner network, combining with marketplace, forming the Amazon partner organization. Part of a big reorg as they grow to the next level, NextGen cloud, mid-game on the chessboard. Cube's got it covered. I'm John Furry, your host at Cube. Great guests here from Data bricks. Both cube alumni's. Jack Anderson, GM and VP of the Databricks partnership team for AWS. You handle that relationship and Joel Minick vice president of product and partner marketing. You guys have the keys to the kingdom with Databricks and AWS. Thanks for joining. Good to see you again. >> Thanks for having us back. >> Yeah, John, great to be here. >> So I feel like we're at Reinvent 2013. Small event, no stage, but there's a real shift happening with procurement. Obviously it's a no brainer on the micro, you know, people should be buying online. Self-service, Cloud Scale. But Amazon's got billions being sold through their marketplace. They've reorganized their partner network. You can see kind of what's going on. They've kind of figured it out. Like let's put everything together and simplify and make it less of a website, marketplace. Merge our partner organizations, have more synergy and frictionless experiences so everyone can make more money and customer's are going to be happier. >> Yeah, that's right. >> I mean, you're running relationship. You're in the middle of it. >> Well, Amazon's mental model here is that they want the world's best ISVs to operate on AWS so that we can collaborate and co architect on behalf of customers. And that's exactly what the APO and marketplace allow us to do, is to work with Amazon on these really, you know, unique use cases. >> You know, I interviewed Ali many times over the years. I remember many years ago, maybe six, seven years ago, we were talking. He's like, "we're all in on AWS." Obviously now the success of Databricks, you've got multiple clouds, see that. Customers have choice. But I remember the strategy early on. It was like, we're going to be deep. So this is, speaks volumes to the relationship you have. Years. Jack, take us through the relationship that Databricks has with AWS from a partner perspective. Joel, and from a product perspective. Because it's not like you guys are Johnny come lately, new to the scene. >> Right. >> You've been there, almost president creation of this wave. What's the relationship and how does it relate to what's going on today? >> So most people may not know that Databricks was born on AWS. We actually did our first $100 million of revenue on Amazon. And today we're obviously available on multiple clouds. But we're very fond of our Amazon relationship. And when you look at what the APN allows us to do, you know, we're able to expand our reach and co-sell with Amazon, and marketplace broadens our reach. And so, we think of marketplace in three different aspects. We've got the marketplace private offer business, which we've been doing for a number of years. Matter of fact, we were driving well over a hundred percent year over year growth in private offers. And we have a nine figure business. So it's a very significant business. And when a customer uses a private offer, that private offer counts against their private pricing agreement with AWS. So they get pricing power against their private pricing. So it's really important it goes on their Amazon bill. In may we launched our pay as you go, on demand offering. And in five short months, we have well over a thousand subscribers. And what this does, is it really reduces the barriers to entry. It's low friction. So anybody in an enterprise or startup or public sector company can start to use Databricks on AWS, in a consumption based model, and have it go against their monthly bill. And so we see customers, you know, doing rapid experimentation, pilots, POCs. They're really learning the value of that first, use case. And then we see rapid use case expansion. And the third aspect is the consulting partner, private offer, CPPO. Super important in how we involve our partner ecosystem of our consulting partners and our resellers that are able to work with Databricks on behalf of customers. >> So you got the big contracts with the private offer. You got the product market fit, kind of people iterating with data, coming in with the buyers you get. And obviously the integration piece all fitting in there. >> Exactly. >> Okay, so those are the offers, that's current, what's in marketplace today. Is that the products... What are people buying? >> Yeah. >> I mean, I guess what's the... Joel, what are people buying in the marketplace? And what does it mean for them? >> So fundamentally what they're buying is the ability to take silos out of their organization. And that is the problem that Databricks is out there to solve. Which is, when you look across your data landscape today, you've got unstructured data, you've got structured data, you've got real time streaming data. And your teams are trying to use all of this data to solve really complicated problems. And as Databricks, as the Lakehouse Company, what we're helping customers do is, how do they get into the new world? How do they move to a place where they can use all of that data across all of their teams? And so we allow them to begin to find, through the marketplace, those rapid adoption use cases where they can get rid of these data warehousing, data lake silos they've had in the past. Get their unstructured and structured data onto one data platform, an open data platform, that is no longer adherent to any proprietary formats and standards and something they can, very much, very easily, integrate into the rest of their data environment. Apply one common data governance layer on top of that. So that from the time they ingest that data, to the time they use that data, to the time they share that data, inside and outside of their organization, they know exactly how it's flowing. They know where it came from. They know who's using it. They know who has access to it. They know how it's changing. And then with that common data platform, with that common governance solution, they'd being able to bring all of those use cases together. Across their real time streaming, their data engineering, their BI, their AI. All of their teams working on one set of data. And that lets them move really, really fast. And it also lets them solve challenges they just couldn't solve before. A good example of this, you know, one of the world's now largest data streaming platforms runs on Databricks with AWS. And if you think about what does it take to set that up? Well, they've got all this customer data that was historically inside of data warehouses. That they have to understand who their customers are. They have all this unstructured data, they've built their data science model, so they can do the right kinds of recommendation engines and forecasting around. And then they've got all this streaming data going back and forth between click stream data, from what the customers are doing with their platform and the recommendations they want to push back out. And if those teams were all working in individual silos, building these kinds of platforms would be extraordinarily slow and complex. But by building it on Databricks, they were able to release it in record time and have grown at a record pace to now be the number one platform. >> And this product, it's impacting product development. >> Absolutely. >> I mean, this is like the difference between lagging months of product development, to like days. >> Yes. >> Pretty much what you're getting at. >> Yes. >> So total agility. >> Mm-hmm. >> I got that. Okay, now, I'm a customer I want to buy in the marketplace, but you got direct Salesforce up there. So how do you guys look at this? Is there channel conflict? Are there comp programs? Because one of the things I heard today in on the stage from AWS's leadership, Chris, was up there speaking, and Mona was, "Hey, he's a CRO conference chief revenue officer" conversation. Which means someone's getting compensated. So, if I'm the sales rep at Databricks, what's my motion to the customer? Do I get paid? Does Amazon sell it? Take us through that. Is there channel conflict? Or, how do you handle it? >> Well, I'd add what Joel just talked about with, you know, with the solution, the value of the solution our entire offering is available on AWS marketplace. So it's not a subset, it's the entire Data Bricks offering. And- >> The flagship, all the, the top stuff. >> Everything, the flagship, the complete offering. So it's not segmented. It's not a sub segment. >> Okay. >> It's, you know, you can use all of our different offerings. Now when it comes to seller compensation, we view this two different ways, right? One is that AWS is also incented, right? Versus selling a native service to recommend Databricks for the right situation. Same thing with Databricks, our sales force wants to do the right thing for the customer. If the customer wants to use marketplace as their procurement vehicle. And that really helps customers because if you get Databricks and five other ISVs together, and let's say each ISV is spending, you're spending a million dollars. You have $5 million of spend. You put that spend through the flywheel with AWS marketplace, and then you can use that in your negotiations with AWS to get better pricing overall. So that's how we view it. >> So customers are driving. This sounds like. >> Correct. For sure. >> So they're looking at this as saying, Hey, I'm going to just get purchasing power with all my relationships. Because it's a solution architectural market, right? >> Yeah. It makes sense. Because if most customers will have a primary and secondary cloud provider. If they can consolidate, you know, multiple ISV spend through that same primary provider, you get pricing power. >> Okay, Joel, we're going to date ourselves. At least I will. So back in the old days, (group laughter) It used to be, do a Barney deal with someone, Hey, let's go to market together. You got to get paper, you do a biz dev deal. And then you got to say, okay, now let's coordinate our sales teams, a lot of moving parts. So what you're getting at here is that the alternative for Databricks, or any company is, to go find those partners and do deals, versus now Amazon is the center point for the customer. So you can still do those joint deals, but this seems to be flipping the script a little bit. >> Well, it is, but we still have vars and consulting partners that are doing implementation work. Very valuable work, advisory work, that can actually work with marketplace through the CPPO offering. So the marketplace allows multiple ways to procure your solution. >> So it doesn't change your business structure. It just makes it more efficient. >> That's correct. >> That's a great way to say it. >> Yeah, that's great. >> Okay. So, that's it. So that's just makes it more efficient. So you guys are actually incented to point customers to the marketplace. >> Yes. >> Absolutely. >> Economically. >> Economically, it's the right thing to do for the customer. It's the right thing to do for our relationship with Amazon. Especially when it comes back to co-selling, right? Because Amazon now is leaning in with ISVs and making recommendations for, you know, an ISV solution. And our teams are working backwards from those use cases, you know, to collaborate and land them. >> Yeah. I want to get that out there. Go ahead, Joel. >> So one of the other things I might add to that too, you know, and why this is advantageous for companies like Databricks to work through the marketplace. Is it makes it so much easier for customers to deploy a solution. It's very, literally, one click through the marketplace to get Databricks stood up inside of your environment. And so if you're looking at how do I help customers most rapidly adopt these solutions in the AWS cloud, the marketplace is a fantastic accelerator to that. >> You know, it's interesting. I want to bring this up and get your reaction to it because to me, I think this is the future of procurement. So from a procurement standpoint, I mean, again, dating myself, EDI back in the old days, you know, all that craziness. Now this is all the internet, basically through the console. I get the infrastructure side, you know, spin up and provision some servers, all been good. You guys have played well there in the marketplace. But now as we get into more of what I call the business apps, and they brought this up on stage. A little nuanced. Most enterprises aren't yet there of integrating tech, on the business apps, into the stack. This is where I think you guys are a use case of success where you guys have been successful with data integration. It's an integrators dilemma, not an innovator's dilemma. So like, I want to integrate. So now I have integration points with Databricks, but I want to put an app in there. I want to provision an application, but it has to be built. It's not, you don't buy it. You build, you got to build stuff. And this is the nuance. What's your reaction to that? Am I getting this right? Or am I off because, no one's going to be buying software like they used to. They buy software to integrate it. >> Yeah, no- >> Because everything's integrated. >> I think AWS has done a great job at creating a partner ecosystem, right? To give customers the right tools for the right jobs. And those might be with third parties. Databricks is doing the same thing with our partner connect program, right? We've got customer partners like Five Tran and DBT that, you know, augment and enhance our platform. And so you're looking at multi ISV architectures and all of that can be procured through the AWS marketplace. >> Yeah. It's almost like, you know, bundling and un bundling. I was talking about this with, with Dave Alante about Supercloud. Which is why wouldn't a customer want the best solution in their architecture? Period. In its class. If someone's got API security or an API gateway. Well, you know, I don't want to be forced to buy something because it's part of a suite. And that's where you see things get sub optimized. Where someone dominates a category and they have, oh, you got to buy my version of this. >> Joel and I were talking, we were actually saying, what's really important about Databricks, is that customers control the data, right? You want to comment on that? >> Yeah. I was going to say, you know, what you're pushing on there, we think is extraordinarily, you know, the way the market is going to go. Is that customers want a lot of control over how they build their data stack. And everyone's unique in what tools are the right ones for them. And so one of the, you know, philosophically, I think, really strong places, Databricks and AWS have lined up, is we both take an approach that you should be able to have maximum flexibility on the platform. And as we think about the Lakehouse, one thing we've always been extremely committed to, as a company, is building the data platform on an open foundation. And we do that primarily through Delta Lake and making sure that, to Jack's point, with Databricks, the data is always in your control. And then it's always stored in a completely open format. And that is one of the things that's allowed Databricks to have the breadth of integrations that it has with all the other data tools out there. Because you're not tied into any proprietary format, but instead are able to take advantage of all the innovation that's happening out there in the open source ecosystem. >> When you see other solutions out there that aren't as open as you guys, you guys are very open by the way, we love that too. We think that's a great strategy, but what am I foreclosing if I go with something else that's not as open? What's the customer's downside as you think about what's around the corner in the industry? Because if you believe it's going to be open, open source, which I think open source software is the software industry, and integration is a big deal. Because software's going to be plentiful. >> Sure. >> Let's face it. It's a good time to be in software business. But Cloud's booming. So what's the downside, from your Databricks perspective? You see a buyer clicking on Databricks versus that alternative. What's potentially should they be a nervous about, down the road, if they go with a more proprietary or locked in approach? >> Yeah. >> Well, I think the challenge with proprietary ecosystems is you become beholden to the ability of that provider to both build relationships and convince other vendors that they should invest in that format. But you're also, then, beholden to the pace at which that provider is able to innovate. >> Mm-hmm. >> And I think we've seen lots of times over history where, you know, a proprietary format may run ahead, for a while, on a lot of innovation. But as that market control begins to solidify, that desire to innovate begins to degrade. Whereas in the open formats- >> So extract rents versus innovation. (John laughs) >> Exactly. Yeah, exactly. >> I'll say it. >> But in the open world, you know, you have to continue to innovate. >> Yeah. >> And the open source world is always innovating. If you look at the last 10 to 15 years, I challenge you to find, you know, an example where the innovation in the data and AI world is not coming from open source. And so by investing in open ecosystems, that means you are always going to be at the forefront of what is the latest. >> You know, again, not to date myself again, but you look back at the eighties and nineties, the protocol stacked with proprietary. >> Yeah. >> You know, SNA and IBM, deck net was digital. You know the rest. And then TCPIP was part of the open systems interconnect. >> Mm-hmm. >> Revolutionary (indistinct) a big part of that, as well as my school did. And so like, you know, that was, but it didn't standardize the whole stack. It stopped at IP and TCP. >> Yeah. >> But that helped inter operate, that created a nice defacto. So this is a big part of this mid game. I call it the chessboard, you know, you got opening game and mid-game, then you get the end game. You're not there at the end game yet at Cloud. But Cloud- >> There's, always some form of lock in, right? Andy Jazzy will address it, you know, when making a decision. But if you're going to make a decision you want to reduce- You don't want to be limited, right? So I would advise a customer that there could be limitations with a proprietary architecture. And if you look at what every customer's trying to become right now, is an AI driven business, right? And so it has to do with, can you get that data out of silos? Can you organize it and secure it? And then can you work with data scientists to feed those models? >> Yeah. >> In a very consistent manner. And so the tools of tomorrow will, to Joel's point, will be open and we want interoperability with those tools. >> And choice is a matter too. And I would say that, you know, the argument for why I think Amazon is not as locked in as maybe some other clouds, is that they have to compete directly too. Redshift competes directly with a lot of other stuff. But they can't play the bundling game because the customers are getting savvy to the fact that if you try to bundle an inferior product with something else, it may not work great at all. And they're going to be, they're onto it. This is the- >> To Amazon's credit by having these solutions that may compete with native services in marketplace, they are providing customers with choice, low price- >> And access to the core value. Which is the hardware- >> Exactly. >> Which is their platform. Okay. So I want to get you guys thought on something else I see emerging. This is, again, kind of Cube rumination moment. So on stage, Chris unpacked a lot of stuff. I mean this marketplace, they're touching a lot of hot buttons here, you know, pricing, compensation, workflows, services behind the curtain. And one of those things he mentioned was, they talk about resellers or channel partners, depending upon what you talk about. We believe, Dave and I believe on the Cube, that the entire indirect sales channel of the industry is going to be disrupted radically. Because those players were selling hardware in the old days and software. That game is going to change. You mentioned you guys have a program, let me get your thoughts on this. We believe that once this gets set up, they can play in this game and bring their services in. Which means that the old reseller channels are going to be rewritten. They're going to be refactored with this new kinds of access. Because you've got scale, you've got money and you've got product. And you got customers coming into the marketplace. So if you're like a reseller that sold computers to data centers or software, you know, a value added reseller or VAB or business. >> You've got to evolve. >> You got to, you got to be here. >> Yes. >> Yeah. >> How are you guys working with those partners? Because you say you have a product in your marketplace there. How do I make money if I'm a reseller with Databricks, with Amazon? Take me through that use case. >> Well I'll let Joel comment, but I think it's pretty straightforward, right? Customers need expertise. They need knowhow. When we're seeing customers do mass migrations to the cloud or Hadoop specific migrations or data transformation implementations. They need expertise from consulting and SI partners. If those consulting and SI partners happen to resell the solution as well. Well, that's another aspect of their business. But I really think it is the expertise that the partners bring to help customers get outcomes. >> Joel, channel big opportunity for Amazon to reimagine this. >> For sure. Yeah. And I think, you know, to your comment about how do resellers take advantage of that, I think what Jack was pushing on is spot on. Which is, it's becoming more and more about the expertise you bring to the table. And not just transacting the software. But now actually helping customers make the right choices. And we're seeing, you know, both SIs begin to be able to resell solutions and finding a lot of opportunity in that. >> Yeah. And I think we're seeing traditional resellers begin to move into that SI model as well. And that's going to be the evolution that this goes. >> At the end of the day, it's about services, right? >> For sure. Yeah. >> I mean... >> You've got a great service. You're going to have high gross profits. >> Yeah >> Managed service provider business is alive and well, right? Because there are a number of customers that want that type of a service. >> I think that's going to be a really hot, hot button for you guys. I think being the way you guys are open, this channel, partner services model coming in, to the fold, really kind of makes for kind of that Supercloud like experience, where you guys now have an ecosystem. And that's my next question. You guys have an ecosystem going on, within Databricks. >> For sure. >> On top of this ecosystem. How does that work? This is kind of like, hasn't been written up in business school and case studies yet. This is new. What is this? >> I think, you know, what it comes down to is, you're seeing ecosystems begin to evolve around the data platforms. And that's going to be one of the big, kind of, new horizons for us as we think about what drives ecosystems. It's going to be around, well, what's the data platform that I'm using? And then all the tools that have to encircle that to get my business done. And so I think there's, you know, absolutely ecosystems inside of the AWS business on all of AWS's services, across data analytics and AI. And then to your point, you are seeing ecosystems now arise around Databricks in its Lakehouse platform as well. As customers are looking at well, if I'm standing these Lakehouses up and I'm beginning to invest in this, then I need a whole set of tools that help me get that done as well. >> I mean you think about ecosystem theory, we're living a whole nother dream. And I'm not kidding. It hasn't yet been written up and for business school case studies is that, we're now in a whole nother connective tissue, ecology thing happening. Where you have dependencies and value proposition. Economics, connectedness. So you have relationships in these ecosystems. >> And I think one of the great things about the relationships with these ecosystems, is that there's a high degree of overlap. >> Yeah. >> So you're seeing that, you know, the way that the cloud business is evolving, the ecosystem partners of Databricks, are the same ecosystem partners of AWS. And so as you build these platforms out into the cloud, you're able to really take advantage of best of breed, the broadest set of solutions out there for you. >> Joel, Jack, I love it because you know what it means? The best ecosystem will win, if you keep it open. >> Sure, sure. >> You can see everything. If you're going to do it in the dark, you know, you don't know the outcome. I mean, this is really kind of what we're talking about. >> And John, can I just add that when I was at Amazon, we had a theory that there's buyers and builders, right? There's very innovative companies that want to build things themselves. We're seeing now that that builders want to buy a platform. Right? >> Yeah. >> And so there's a platform decision being made and that ecosystem is going to evolve around the platform. >> Yeah, and I totally agree. And the word innovation gets kicked around. That's why, you know, when we had our Supercloud panel, it was called the innovators dilemma, with a slash through it, called the integrater's dilemma. Innovation is the digital transformation. So- >> Absolutely. >> Like that becomes cliche in a way, but it really becomes more of a, are you open? Are you integrating? If APIs are connective tissue, what's automation, what's the service messages look like? I mean, a whole nother set of, kind of thinking, goes on in these new ecosystems and these new products. >> And that thinking is, has been born in Delta Sharing, right? So the idea that you can have a multi-cloud implementation of Databricks, and actually share data between those two different clouds, that is the next layer on top of the native cloud solution. >> Well, Databricks has done a good job of building on top of the goodness of, and the CapEx gift from AWS. But you guys have done a great job taking that building differentiation into the product. You guys have great customer base, great growing ecosystem. And again, I think a shining example of what every enterprise is going to do. Build on top of something, operating model, get that operating model, driving revenue. >> Mm-hmm. >> Yeah. >> Whether, you're Goldman Sachs or capital one or XYZ corporation. >> S and P global, NASDAQ. >> Yeah. >> We've got, you know, the biggest verticals in the world are solving tough problems with Databricks. I think we'd be remiss because if Ali was here, he would really want to thank Amazon for all of the investments across all of the different functions. Whether it's the relationship we have with our engineering and service teams. Our marketing teams, you know, product development. And we're going to be at Reinvent. A big presence at Reinvent. We're looking forward to seeing you there, again. >> Yeah. We'll see you guys there. Yeah. Again, good ecosystem. I love the ecosystem evolutions happening. This NextGen Cloud is here. We're seeing this evolve, kind of new economics, new value propositions kind of scaling up. Producing more. So you guys are doing a great job. Thanks for coming on the Cube and taking the time. Joel, great to see you at the check. >> Thanks for having us, John. >> Okay. Cube coverage here. The world's changing as APN comes together with the marketplace for a new partner organization at Amazon web services. The Cube's got it covered. This should be a very big, growing ecosystem as this continues. Billions of being sold through the marketplace. And of course the buyers are happy as well. So we've got it all covered. I'm John Furry. your host of the cube. Thanks for watching. (upbeat music)

>>Welcome back everyone to the cubes coverage here in Seattle, Washington, AWS's marketplace seller conference. It's the big news within the Amazon partner network, combining with marketplaces, forming the Amazon partner organization, part of a big reorg as they grow the next level NextGen cloud mid-game on the chessboard. Cube's got cover. I'm John fur, host of Cub, a great guests here from data bricks, both cube alumnis, Jack Anderson, GM of the and VP of the data bricks partnership team. For ADOS, you handle that relationship and Joel Minick vice president of product and partner marketing. You guys are the, have the keys to the kingdom with data, bricks, and AWS. Thanks for joining. Thanks for good to see you again. Thanks for >>Having us back. Yeah, John, great to be here. >>So I feel like we're at reinvent 2013 small event, no stage, but there's a real shift happening with procurement. Obviously it makes it's a no brainer on the micro, you know, people should be buying online self-service cloud scale, but Amazon's got billions being sold to their marketplace. They've reorganized their partner network. You can see kind of what's going on. They've kind of figured it out. Like let's put everything together and simplify and make it less of a website marketplace merge our partner to have more synergy and friction, less experiences so everyone can make more money and customer's gonna be happier. >>Yeah, that's right. >>I mean, you're run relationship. You're in the middle of it. >>Well, Amazon's mental model here is that they want the world's best ISVs to operate on AWS so that we can collaborate and co architect on behalf of customers. And that's exactly what the APO and marketplace allow us to do is to work with Amazon on these really, you know, unique use cases. >>You know, I interviewed Ali many times over the years. I remember many years ago, I think six, maybe six, seven years ago, we were talking. He's like, we're all in ons. Obviously. Now the success of data bricks, you've got multiple clouds. See that customers have choice, but I remember the strategy early on. It was like, we're gonna be deep. So this is speaks volumes to the, the relationship you have years. Jack take us through the relationship that data bricks has with AWS from a, from a partner perspective, Joel, and from a product perspective, because it's not like you got to Johnny come lately new to the new, to the scene, right? We've been there almost president creation of this wave. What's the relationship and has it relate to what's going on today? >>So, so most people may not know that data bricks was born on AWS. We actually did our first 100 million of revenue on Amazon. And today we're obviously available on multiple clouds, but we're very fond of our Amazon relationship. And when you look at what the APN allows us to do, you know, we're able to expand our reach and co-sell with Amazon and marketplace broadens our reach. And so we think of marketplace in three different aspects. We've got the marketplace, private offer business, which we've been doing for a number of years. Matter of fact, we we're driving well over a hundred percent year over year growth in private offers and we have a nine figure business. So it's a very significant business. And when a customer uses a private offer that private offer counts against their private pricing agreement with AWS. So they get pricing power against their, their private pricing. >>So it's really important. It goes on their Amazon bill in may. We launched our pay as you go on demand offering. And in five short months, we have well over a thousand subscribers. And what this does is it really reduces the barriers to entry it's low friction. So anybody in an enterprise or startup or public sector company can start to use data bricks on AWS and pay consumption based model and have it go against their monthly bill. And so we see customers, you know, doing rapid experimentation pilots, POCs, they're, they're really learning the value of that first use case. And then we see rapid use case expansion. And the third aspect is the consulting partner, private offers C P O super important in how we involve our partner ecosystem of our consulting partners and our resellers that are able to work with data bricks on behalf of customers. >>So you got the big contracts with the private offer. You got the product market fit, kind of people iterating with data coming in with, with the buyers you go. And obviously the integration piece all fitting in there. Exactly. Exactly. Okay. So that's that those are the offers that's current and what's in marketplace today. Is that the products, what are, what are people buying? I mean, I guess what's the Joel, what are, what are people buying in the marketplace and what does it mean for >>Them? So fundamentally what they're buying is the ability to take silos out of their organization. And that's, that is the problem that data bricks is out there to solve, which is when you look across your data landscape today, you've got unstructured data, you've got structured data, you've got real time streaming data, and your teams are trying to use all of this data to solve really complicated problems. And as data bricks as the lake house company, what we're helping customers do is how do they get into the new world? How do they move to a place where they can use all of that data across all of their teams? And so we allow them to begin to find through the marketplace, those rapid adoption use cases where they can get rid of these data, warehousing data lake silos they've had in the past, get their unstructured and structured data onto one data platform and open data platform that is no longer adherent to any proprietary formats and standards and something. >>They can very much, very easily integrate into the rest of their data environment, apply one common data governance layer on top of that. So that from the time they ingest that data to the time they use that data to the time they share that data inside and outside of their organization, they know exactly how it's flowing. They know where it came from. They know who's using it. They know who has access to it. They know how it's changing. And then with that common data platform with that common governance solution, they'd being able to bring all of those use cases together across their real time, streaming their data engineering, their BI, their AI, all of their teams working on one set of data. And that lets them move really, really fast. And it also lets them solve challenges. They just couldn't solve before a good example of this, you know, one of the world's now largest data streaming platforms runs on data bricks with AWS. >>And if you think about what does it take to set that up? Well, they've got all this customer data that was historically inside of data warehouses, that they have to understand who their customers are. They have all this unstructured data, they've built their data science model, so they can do the right kinds of recommendation engines and forecasting around. And then they've got all this streaming data going back and forth between click stream data from what the customers are doing with their platform and the recommendations they wanna push back out. And if those teams were all working in individual silos, building these kinds of platforms would be extraordinarily slow and complex, but by building it on data bricks, they were able to release it in record time and have grown at, at record pace >>To not be that's product platform that's impacting product development. Absolutely. I mean, this is like the difference between lagging months of product development to like days. Yes. Pretty much what you're getting at. Yeah. So total agility. I got that. Okay. Now I'm a customer I wanna buy in the marketplace, but I also, you got direct Salesforce up there. So how do you guys look at this? Is there channel conflict? Are there comp programs? Because one of the things I heard today in on the stage from a Davis's leadership, Chris was up there speaking and, and, and moment I was, Hey, he's a CRO conference, chief revenue officer conversation, which means someone's getting compensated. So if I'm the sales rep at data bricks, what's my motion to the customer. Do I get paid? Does Amazon sell it? Take us through that. Is there channel conflict? Is there or an audio lift? >>Well, I I'd add what Joel just talked about with, with, you know, what the solution, the value of the solution our entire offering is available on AWS marketplace. So it's not a subset, the entire data bricks offering and >>The flagship, all the, the top, >>Everything, the flagship, the complete offering. So it's not, it's not segmented. It's not a sub segment. It's it's, you know, you can use all of our different offerings. Now when it comes to seller compensation, we, we, we view this two, two different ways, right? One is that AWS is also incented, right? Versus selling a native service to recommend data bricks for the right situation. Same thing with data bricks. Our Salesforce wants to do the right thing for the customer. If the customer wants to use marketplace as their procurement vehicle. And that really helps customers because if you get data bricks and five other ISVs together, and let's say each ISV is spending, you're spending a million dollars, you have $5 million of spend, you put that spend through the flywheel with AWS marketplace. And then you can use that in your negotiations with AWS to get better pricing overall. So that's how we, >>We do it. So customers are driving. This sounds like, correct. For sure. So they're looking at this as saying, Hey, I'm gonna just get purchasing power with all my relationships because it's a solution architectural market, right? >>Yeah. It makes sense. Because if most customers will have a primary and secondary cloud provider, if they can consolidate, you know, multiple ISV spend through that same primary provider, you get pricing >>Power, okay, Jill, we're gonna date ourselves. At least I will. So back in the old days, it used to be, do a Barney deal with someone, Hey, let's go to market together. You gotta get paper, you do a biz dev deal. And then you gotta say, okay, now let's coordinate our sales teams, a lot of moving parts. So what you're getting at here is that the alternative for data bricks or any company is to go find those partners and do deals versus now Amazon is the center point for the customer so that you can still do those joint deals. But this seems to be flipping the script a little bit. >>Well, it is, but we still have VAs and consulting partners that are doing implementation work very valuable work advisory work that can actually work with marketplace through the C PPO offering. So the marketplace allows multiple ways to procure your >>Solution. So it doesn't change your business structure. It just makes it more efficient. That's >>Correct. >>That's a great way to say it. Yeah, >>That's great. So that's so that's it. So that's just makes it more efficient. So you guys are actually incented to point customers to the marketplace. >>Yes, >>Absolutely. Economically. Yeah. >>E economically it's the right thing to do for the customer. It's the right thing to do for our relationship with Amazon, especially when it comes back to co-selling right? Because Amazon now is leaning in with ISVs and making recommendations for, you know, an ISV solution and our teams are working backwards from those use cases, you know, to collaborate, land them. >>Yeah. I want, I wanna get that out there. Go ahead, Joel. >>So one of the other things I might add to that too, you know, and why this is advantageous for, for companies like data bricks to, to work through the marketplace, is it makes it so much easier for customers to deploy a solution. It's, it's very, literally one click through the marketplace to get data bricks stood up inside of your environment. And so if you're looking at how do I help customers most rapidly adopt these solutions in the AWS cloud, the marketplace is a fantastic accelerator to that. You >>Know, it's interesting. I wanna bring this up and get your reaction to it because to me, I think this is the future of procurement. So from a procurement standpoint, I mean, again, dating myself EDI back in the old days, you know, all that craziness. Now this is all the, all the internet, basically through the console, I get the infrastructure side, you know, spin up and provision. Some servers, all been good. You guys have played well there in the marketplace. But now as we get into more of what I call the business apps, and they brought this up on stage little nuance, most enterprises aren't yet there of integrating tech on the business apps, into the stack. This is where I think you guys are a use case of success where you guys have been successful with data integration. It's an integrator's dilemma, not an innovator's dilemma. So like, I want to integrate, so now I have integration points with data bricks, but I want to put an app in there. I want to provision an application, but it has to be built. It's not, you don't buy it. You build, you gotta build stuff. And this is the nuance. What's your reaction to that? Am I getting this right? Or, or am I off because no, one's gonna be buying software. Like they used to, they buy software to integrate it. >>Yeah, >>No, I, cause everything's integrated. >>I think AWS has done a great job at creating a partner ecosystem, right. To give customers the right tools for the right jobs. And those might be with third parties, data bricks is doing the same thing with our partner connect program. Right. We've got customer, customer partners like five tra and D V T that, you know, augment and enhance our platform. And so you, you're looking at multi ISV architectures and all of that can be procured through the AWS marketplace. >>Yeah. It's almost like, you know, bundling and unbundling. I was talking about this with, with Dave ante about Supercloud, which is why wouldn't a customer want the best solution in their architecture period. And it's class. If someone's got API security or an API gateway. Well, you know, I don't wanna be forced to buy something because it's part of a suite and that's where you see things get suboptimized where someone dominates a category and they have, oh, you gotta buy my version of this. Yeah. >>Joel, Joel. And that's Joel and I were talking, we're actually saying what what's really important about Databricks is that customers control the data. Right? You wanna comment on that? >>Yeah. I was say the, you know what you're pushing on there we think is extraordinarily, you know, the way the market is gonna go is that customers want a lot of control over how they build their data stack. And everyone's unique in what tools are the right ones for them. And so one of the, you know, philosophically I think really strong places, data, bricks, and AWS have lined up is we both take an approach that you should be able to have maximum flexibility on the platform. And as we think about the lake house, one thing we've always been extremely committed to as a company is building the data platform on an open foundation. And we do that primarily through Delta lake and making sure that to Jack's point with data bricks, the data is always in your control. And then it's always stored in a completely open format. And that is one of the things that's allowed data bricks to have the breadth of integrations that it has with all the other data tools out there, because you're not tied into any proprietary format, but instead are able to take advantage of all the innovation that's happening out there in the open source ecosystem. >>When you see other solutions out there that aren't as open as you guys, you guys are very open by the way, we love that too. We think that's a great strategy, but what's the, what am I foreclosing? If I go with something else that's not as open what what's the customer's downside as you think about what's around the corner in the industry. Cuz if you believe it's gonna be open, open source, which I think opens our software is the software industry and integration is a big deal, cuz software's gonna be plentiful. Let's face it. It's a good time to be in software business, but cloud's booming. So what's the downside from your data bricks perspective, you see a buyer clicking on data bricks versus that alternative what's potentially is should they be a nervous about down the road if they go with a more proprietary or locked in approach? Well, >>I think the challenge with proprietary ecosystems is you become beholden to the ability of that provider to both build relationships and convince other vendors that they should invest in that format. But you're also then beholden to the pace at which that provider is able to innovate. And I think we've seen lots of times over history where, you know, a proprietary format may run ahead for a while on a lot of innovation. But as that market control begins to solidify that desire to innovate begins to, to degrade, whereas in the open format. So >>Extract rents versus innovation. Exactly. >>Yeah, exactly. >>But >>I'll say it in the open world, you know, you have to continue to innovate. Yeah. And the open source world is always innovating. If you look at the last 10 to 15 years, I challenge you to find, you know, an example where the innovation in the data and AI world is not coming from open source. And so by investing in open ecosystems, that means you were always going to be at the forefront of what is the >>Latest, you know, again, not to date myself again, but you look back at the eighties and nineties, the protocol stacked for proprietary. Yeah. You know, SNA at IBM deck net was digital, you know, the rest is, and then TCP, I P was part of the open systems, interconnect, revolutionary Oly, a big part of that as well as my school did. And so like, you know, that was, but it didn't standardize the whole stack. It stopped at IP and TCP. Yeah. But that helped interoperate, that created a nice defacto. So this is a big part of this mid game. I call it the chessboard, you know, you got opening game and mid game. Then you got the end game and we're not there. The end game yet cloud the cloud. >>There's, there's always some form of lock in, right. Andy jazzy will, will address it, you know, when making a decision. But if you're gonna make a decision you want to reduce as you don't wanna be limited. Right. So I would advise a customer that there could be limitations with a proprietary architecture. And if you look at what every customer's trying to become right now is an AI driven business. Right? And so it has to do with, can you get that data outta silos? Can you, can you organize it and secure it? And then can you work with data scientists to feed those models? Yeah. In a, in a very consistent manner. And so the tools of tomorrow will to Joel's point will be open and we want interoperability with those >>Tools and, and choice is a matter too. And I would say that, you know, the argument for why I think Amazon is not as locked in as maybe some other clouds is that they have to compete directly too. Redshift competes directly with a lot of other stuff, but they can't play the bundling game because the customers are getting savvy to the fact that if you try to bundle an inferior product with something else, it may not work great at all. And they're gonna be they're onto it. This is >>The Amazon's credit by having these, these solutions that may compete with native services in marketplace, they are providing customers with choice, low >>Price and access to the S and access to the core value. Exactly. Which the >>Hardware, which is their platform. Okay. So I wanna get you guys thought on something else. I, I see emerging, this is again kind of cube rumination moment. So on stage Chris unpacked, a lot of stuff. I mean this marketplace, they're touching a lot of hot buttons here, you know, pricing compensation, workflows services behind the curtain. And one of the things he mentioned was they talk about resellers or channel partners, depending upon what you talk about. We believe Dave and I believe on the cube that the entire indirect sales channel of the industry is gonna be disrupted radically because those players were selling hardware in the old days and software, that game is gonna change. You know, you mentioned you guys have a program, want to get your thoughts on this. We believe that once this gets set up, they can play in this game and bring their services in which means that the old reseller channels are gonna be rewritten. They're gonna be refactored with this new kinds of access. Cuz you've got scale, you've got money and you've got product and you got customers coming into the marketplace. So if you're like a reseller that sold computers to data centers or software, you know, value added reseller or V or business, >>You've gotta evolve. >>You gotta, you gotta be here. Yes. How are you guys working with those partners? Cuz you say you have a part in your marketplace there. How do I make money? If I'm a reseller with data bricks with eight Amazon, take me through that use case. >>Well I'll let Joel comment, but I think it's, it's, it's pretty straightforward, right? Customers need expertise. They need knowhow. When we're seeing customers do mass migrations to the cloud or Hadoop specific migrations or data transformation implementations, they need expertise from consulting and SI partners. If those consulting SI partners happen to resell the solution as well. Well, that's another aspect of their business, but I really think it is the expertise that the partners bring to help customers get outcomes. >>Joel, channel big opportunity for re re Amazon to reimagine this. >>For sure. Yeah. And I think, you know, to your comment about how to resellers take advantage of that, I think what Jack was pushing on is spot on, which is it's becoming more about more and more about the expertise you bring to the table and not just transacting the software, but now actually helping customers make the right choices. And we're seeing, you know, both SI begin to be able to resell solutions and finding a lot of opportunity in that. Yeah. And I think we're seeing traditional resellers begin to move into that SI model as well. And that's gonna be the evolution that >>This gets at the end of the day. It's about services for sure, for sure. You've got a great service. You're gonna have high gross profits. And >>I think that the managed service provider business is alive and well, right? Because there are a number of customers that want that, that type of a service. >>I think that's gonna be a really hot, hot button for you guys. I think being the way you guys are open this channel partner services model coming in to the fold really kind of makes for kind of that super cloudlike experience where you guys now have an ecosystem. And that's my next question. You guys have an ecosystem going on within data bricks for sure. On top of this ecosystem, how does that work? This is kinda like hasn't been written up in business school and case studies yet this is new. What is this? >>I think, you know, what it comes down to is you're seeing ecosystems begin to evolve around the data platforms and that's gonna be one of the big kind of new horizons for us as we think about what drives ecosystems it's going to be around. Well, what is the, what's the data platform that I'm using and then all the tools that have to encircle that to get my business done. And so I think there's, you know, absolutely ecosystems inside of the AWS business on all of AWS's services, across data analytics and AI. And then to your point, you are seeing ecosystems now arise around data bricks in its Lakehouse platform, as well as customers are looking at well, if I'm standing these Lakehouse up and I'm beginning to invest in this, then I need a whole set of tools that help me get that done as well. >>I mean you think about ecosystem theory, we're living a whole nother dream and I'm, and I'm not kidding. It hasn't yet been written up and for business school case studies is that we're now in a whole nother connective tissue ecology thing happening where you have dependencies and value proposition economics connectedness. So you have relationships in these ecosystems. >>And I think one of the great things about relationships with these ecosystems is that there's a high degree of overlap. Yeah. So you're seeing that, you know, the way that the cloud business is evolving, the, the ecosystem partners of data bricks are the same ecosystem partners of AWS. And so as you build these platforms out into the cloud, you're able to really take advantage of best of breed, the broadest set of solutions out there for >>You. Joel, Jack, I love it because you know what it means the best ecosystem will win. If you keep it open. Sure. You can see everything. If you're gonna do it in the dark, you know, you don't know the outcome. I mean, this is really kind we're talking about. >>And John, can I just add that when I was in Amazon, we had a, a theory that there's buyers and builders, right? There's very innovative companies that want to build things themselves. We're seeing now that that builders want to buy a platform. Right? Yeah. And so there's a platform decision being made and that ecosystem gonna evolve around the >>Platform. Yeah. And I totally agree. And, and, and the word innovation get kicks around. That's why, you know, when we had our super cloud panel was called the innovators dilemma with a slash through it called the integrated dilemma, innovation is the digital transformation. So absolutely like that becomes cliche in a way, but it really becomes more of a, are you open? Are you integrating if APIs are the connective tissue, what's automation, what's the service message look like. I mean, a whole nother set of kind of thinking goes on and these new ecosystems and these new products >>And that, and that thinking is, has been born in Delta sharing. Right? So the idea that you can have a multi-cloud implementation of data bricks, and actually share data between those two different clouds, that is the next layer on top of the native cloud >>Solution. Well, data bricks has done a good job of building on top of the goodness of, and the CapEx gift from AWS. But you guys have done a great job taking that building differentiation into the product. You guys have great customer base, great grow ecosystem. And again, I think in a shining example of what every enterprise is going to do, build on top of something operating model, get that operating model, driving revenue. >>Yeah. >>Well we, whether whether you're Goldman Sachs or capital one or XYZ corporation >>S and P global NASDAQ, right. We've got, you know, these, the biggest verticals in the world are solving tough problems with data breaks. I think we'd be remiss cuz if Ali was here, he would really want to thank Amazon for all of the investments across all of the different functions, whether it's the relationship we have with our engineering and service teams. Yeah. Our marketing teams, you know, product development and we're gonna be at reinvent the big presence of reinvent. We're looking forward to seeing you there again. >>Yeah. We'll see you guys there. Yeah. Again, good ecosystem. I love the ecosystem evolutions happening this next gen cloud is here. We're seeing this evolve kind of new economics, new value propositions kind of scaling up, producing more so you guys are doing a great job. Thanks for coming on the Cuban, taking time. Chill. Great to see you at the check. Thanks for having us. Thanks. Going. Okay. Cube coverage here. The world's changing as APN comes to give the marketplace for a new partner organization at Amazon web services, the Cube's got a covered. This should be a very big growing ecosystem as this continues, billions of being sold through the marketplace. Of course the buyers are happy as well. So we've got it all covered. I'm John furry, your host of the cube. Thanks for watching.

>>Hey everyone. Welcome to this cube conversation featuring Carto I'm Lisa Martin. And today we're excited to be joined by Javier Delatorre, the founder and chief strategy officer at Carto. We're going to be talking about how Carto is bringing cloud native spatial analysis to the cloud with AWS. How do you are great to have you on the program? Talk to us about cartel. What do you guys do? >>Great. So, uh, part two is a location intelligence platform, but we really use some neighboring organizations to work with location data on the AWS cloud. So essentially enabling organizations to analyze what do they, what should they open new stores? Whereas today probably the new internet, in essence, understanding the locations. I mentioned just helping them to figure out where to do things >>From Carter's perspective. Talk to me about why spatial analysis, location data is important. What power does it give to businesses in any industry? >>Right. I mean, we like to say that everything happens somewhere, right? So we understand that, you know, like the physical world is a very important dimension. So understanding where things happens and the relation within space is a pretty fundamental dimension when it comes to another. I like to put examples of, um, before your neighbors, uh, install alarms in their phones, the likelihood that you will get an alarm is also versus quite a lot. So that's eight years old, says that we are influenced by things that happens around us. And if you can model and understand those spacial relations, you can then look to optimize or predict what is going to happen based on where things are happening. And this is something that we've seen a lot, for example, with the pandemic, but now we're seeing, you know, like many organizations utilizing it for yeah. For finding out where they can find new customers, stores, like say, where did they deploy the new infrastructure? Everything that the ANZ has a spatial component. And that's what is spatial analytics and location intelligence allows you to do? >>Give me some examples of spatial data. And the first thing that pops into my mind is GPS. But I know that there's a lot more than that. >>Uh, GPS has been one of the most important types of data for, so since you know, the inability of GPS and, and with mobile and different sensors are staring at it, we've seen an incredible amount of location data coming into place, but you're right. There's many other types of location data that people tend not to be so aware. I'd say any company that is handling customers, you know, they're likely going to have their addresses. So we have the address of the customer. You have a location already, we'll have, we'll call that the process of geocoding. We transform an address that coordinates, right? But you also have the same, you know, with bees, you have the same, uh, with many different sip codes, it's many different ways that you can represent location. And once you identify those, uh, location bits in your data, then you can start thinking about what type of analysis you can do with them. So it is, like I said, like in many, many places, but definitely the, the rise of, uh, GPS and sensors have been very dramatic. Now we see in also like acute stream of location data coming, for example, from satellites, you know, with all these constellations of satellites, capturing daily images on from earlier, that is also giving us a lot of contextual information. But so it is, you know, mobile phones, when you connect to cell towers, there's many different businesses that are now kind of giving us location data. >>So you alluded to that earlier, a lot more businesses are using location data in their strategies. Talk to me about the acceleration that you seen of that in the last couple of years alone. >>Yeah. So I think one thing that we see in, you know, like massively on the industry obviously is these companies are going through the digital transformation. They are applying analytics to bigger and bigger areas of their, of their, of their business, right. And in a way to showcase, to kind of came as while the last time I mentioned that a lot of organizations started to look at, and over the last few years, we've seen that change in a lot. We've seen it within the many more organized spaces. Now making the questions around where things happens, how does actually matter to my business. So this is celebration, you know, has the sensitive men that many more people are now starting to look at, not only seeing things on a map, like, you know, where my customers are, where my warehouses are, my logistics supply chain, where is it located? >>Now, we're starting to see many more organizations looking at questions about how can I predict where something is going to happen, or how can I optimize my business process so that, um, you know, I, I try to reduce the number of kilometers that I have to drive miles. So, um, I guess it's a mix of the need for sustainability optimizing the business process. And the fact that more and more organizations are starting to do much more deep transformation that now location data has become a much more interesting aspect for many more organizations. So I think all these things together has to make in a way that perfect storm. And now we've seen a lot of the men too, um, for companies that want to go will be John seeing things in a map to understanding why things happen in those spaces. And that's, I think that like, again, a multitude of drivers, you know, that is supposed to in this industry. >>Can you talk about some of the key use cases and maybe some of the vertical industries where you've really seen this takeoff in the last couple of years? >>Yes. And I think he's just in a way, one of the most interesting factors of our industry traditional industries have been on the area around security in the public sector was very much on the military and the, in the, in the, uh, intelligence ecosystem. But now we've seen tremendous adoption on industries like retail, right, where they are lying now consolidating what is their, what is their physical presence? Where do they open stores? You know, like, uh, food chains, what do they open restaurants? And it's a much more analytical process now towards making businesses because, and that involves the usage of location intelligence and space analytics. We do touch one, but we still also like tremendous increase in usage on things like telcos telecommunication. Now with all the deployment of 5g networks, fiber optics, most of those operators require a very good understanding of where you should apply your networks, which, which areas you want to go start first tablet, smart CapEx car, like a strategy. >>So that's telco, I would say it's also has been a tremendous increase. Um, the public secretary is obviously very important, you know, especially, you know, with a lot of the, in a way we all got to master or do you know why geography matters? You know, how to understand your location. Um, and the last one that I would say that it's also connected very much with climate change, transportation and logistics are very, very important factor now. So understanding what is the best strategies for last mile delivery, how to organize your warehouses to better meet your needs. Those are the places that now we're seeing really growing really fast. >>So tremendous amount of use cases, a lot of opportunity there for optimization. How have companies traditionally analyze spatial data and why does that need to change? >>Yeah, so, um, I mean, to a certain extent, I would like to say that there's not been, um, that much use of location data. And that I think is one of the most exciting parts that for many organizations, this is the first time that they're looking at location as a, as a need. I mentioned that they need to understand. So there were, there were several organizations doing already a spatial analytics, but right now it's really, we really see in the expansion of our industry and you're not catching up in, in major, uh, major companies. So those are not like more advanced, you know, we'll have used so-called the traditional GIS systems. GIS is a, is a type of software. That's been existing for many years, but it's only the second used by a very small needs of analysts. You have to go almost four years to school, you know, to become a GIS expert and then do GIS analyst. >>This is right now trending dramatically. And I think, you know, Carter's part of that, uh, transition to necessity, making best patient analysis and GIS part of just the generic general analytics. And I think this is one of the most exciting times that we have, because we've seen the demo by station of his face. And it takes now to imagine why there are, so now we've seen, you know, like analysts that, you know, used to be just to know how to make a map. So things are not with a map, you know, where, where something was happening. Now we starting to see them making much more interesting plastics. So I'm like, okay, if it happens here, where else could they be happened? Right. So that's what I, right now, they, the, the, the huge statements, I'd say, I'd say like many organizations is the first time they go into jail. People like me for being very passionate about the possibilities of really improving processes. I mean, this is super, super exciting time. >>I can definitely feel your passion here through zoom, or talk to me a little bit about how cartel and AWS are helping organizations to embrace the democratization of spatial data and really unlock its super powers. >>Yeah. Well, I mean, obviously, you know, that AWS as the leader on the cloud, in a way that has fundamentally changed the way that we think about like analytics, right? So, um, not only the clouds provide us with the scalability, scalability, affordable the scale of anything. So that's one of the things that, you know, has been incredibly, um, transformative in our industry, uh, with AWS. Now we can do analysis at the scale that wasn't possible before. So that's, that's, that's one thing. So for us, you know, what we've embarked with AWS is rethinking how we can do a spatial analytics in the cloud. We're calling it car to cloud native is providing a full cloud native approach towards performing the spatial analytics, traditional GIS. And for us to utilize this game, even as huge amount of scalability, we use services like Retsef the now with their server last capabilities, we like a, an organization have their data already on that data warehouse on breaths test and using Kartra space. >>now they can do a special ethics directly on the warehouse. This is one of the biggest characteristics of cartel made by being the first cloud data platform. Every computing that we do actually gets pushed down to the warehouse. So the customer is already using the computing engine that they're already, they've been using it for many other things they're paying for already. And they give us scalability. Uh, also very cost-effectiveness this storage competed in separation that the rest of service provides. It makes it very competitive from a call like a cost perspective, and then also is very convenient. So it means that you can use just traditional sequel that are many analysts, know how to use it within the tools that they've been using for many. So I think the participation is essential to read safe, and then also with incorporating the Amazon location services. So we can talk to, and it certainly provides a cloud native it's scalable, affordable, efficient, and much more easy to use solution to performance, space analytics that anything that has been done before. >>It's a tremendous amount of opportunity. It sounds like we're just scratching the surface, but really interesting things that cartoon was doing and how you're enabling organizations in every industry to accelerate the use of spatial data. Javier, thank you so much for joining me on the program today. Fascinating information and best of luck to you. >>Thank you very much >>For Javier Delatorre I'm Lisa Martin. You're watching the cubes stay right here for more coverage of the hybrid tech event world.

>>Uh, hi, I'm Joe Rodriguez, managing director of financial services at Cloudera. Uh, welcome to the fight fraud with a data session, uh, at Cloudera, we believe that fighting fraud with, uh, uh, begins with data. Um, so financial services is Cloudera's largest industry vertical. We have approximately 425 global financial services customers, uh, which consists of 82 out of a hundred of the largest global banks of which we have 27 that are globally systemic banks, uh, four out of the five top, uh, stock exchanges, uh, eight out of the top 10 wealth management firms and all four of the top credit card networks. So as you can see most financial services institutions, uh, utilize Cloudera for data analytics and machine learning, uh, we also have over 20 central banks and a dozen or so financial regulators. So it's an incredible footprint which gives Cloudera lots of insight into the many innovations, uh, that our customers are coming up with. Uh, criminals can steal thousands of dollars before a fraudulent transaction is detected. So the cost of, uh, to purchase a, your account data is well worth the price to fraudsters. Uh, according to Experian credit and debit card account information sells on the dark web for a mere $5 with the CVV number and up to $110. If it comes with all the bank information, including your name, social security number, date of birth, uh, complete account numbers and, and other personal data. >>Um, our customers have several key data and analytics challenges when it comes to fighting financial crime. The volume of data that they need to deal with is, is huge and growing exponentially. Uh, all this data needs to be evaluated in real time. Uh, there is, uh, there are new sources of, of streaming data that need to be integrated with existing, uh, legacy data sources. This includes, um, biometrics data and enhanced, uh, authentication, uh, video surveillance call center data. And of course all that needs to be integrated with existing legacy data sources. Um, there is an analytics arms race between the banks and the criminals and the criminal networks never stop innovating. They also we'll have to deal with, uh, disjointed security and governance, security and governance policies are often set per data source, uh, or application requiring redundant work, work across workloads. And, and they have to deal with siloed environments, um, the specialized nature of platforms and people results in disparate data sources and data management processes, uh, this duplicates efforts and, uh, divides the, the business risk and crime teams, limiting collaboration opportunities between CDP enhances financial crime solutions, uh, to be holistic by eliminating data gaps between siloed solutions with, uh, an enterprise data approach, uh, advanced, uh, data analytics and machine learning, uh, by deploying an enterprise wide data platform, you reduce siloed divisions between business risk and crime teams and enable better collaboration through industrialized machine learning. >>Uh, you tighten up the loop between, uh, detection and new fraud patterns. Cloudera provides the data platform on which a best of breed applications can run and leverage integrated machine learning cloud Derrick stands rather than replaces your existing fraud modeling applications. So Oracle SAS Actimize to, to name a few, uh, integrate with an enterprise data hub to scale the data increased speed and flexibility and improve efficacy of your entire fraud system. It also centralizes the fraud workload on data that can be used for other use cases in applications like enhanced KYC and a customer 360 4 example. >>I just, I wanted to highlight a couple of our partners in financial crime prevention, uh, semi dine, and Quintex, uh, uh, so send me nine provides fraud simulation using agent-based modeling, uh, machine learning techniques, uh, to generate synthetic transaction data. This data simulates potential fraud scenarios in a cost-effective, uh, GDPR compliant, virtual environment, significantly improved financial crime detection systems, semi dine identifies future fraud topologies, uh, from millions of, of simulations that can be used to dynamically train, uh, new machine learning algorithms for enhanced fraud identification and context, um, uh, connects the dots within your data, using dynamic entity resolution, and advanced network analytics to create context around your customers. Um, this enables you to see the bigger picture and automatically assesses potential criminal beads behavior. >>Now let's go some of our, uh, customers, uh, and how they're using cloud caldera. Uh, first we'll talk about, uh, United overseas bank, or you will be, um, you'll be, is a leading full service bank in, uh, in Asia. It, uh, with, uh, a network of more than 500 offices in, in 19 countries and territories in Asia, Pacific, Western Europe and north America UA, um, UOB built a modern data platform on Cloudera that gives it the flexibility and speed to develop new AI and machine learning solutions and to create a data-driven enterprise. Um, you'll be set up, uh, set up it's big data analytics center in 2017. Uh, it was Singapore's first centralized big data unit, uh, within a bank to deepen the bank's data analytic capabilities and to use data insights to enhance, uh, the banks, uh, uh, performance essential to this work was implementing a platform that could cost efficiently, bring together data from dozens of separate systems and incorporate a range of unstructured data, including, uh, voice and text, um, using Cloudera CDP and machine learning. >>UOB gained a richer understanding of its customer preferences, uh, to help make their, their banking experience simpler, safer, and more reliable. Working with Cloudera UOB has a big data platform that gives business staff and data scientists faster access to relevant and quality data for, for self-service analytics, machine learning and, uh, emerging artificial intelligence solutions. Um, with new self-service analytics and machine learning driven insights, you'll be, uh, has realized improvements in, in digital banking, asset management, compliance, AML, and more, uh, advanced AML detection capabilities, help analysts detect suspicious transactions either based on hidden relationships of shell companies and, uh, high risk individuals, uh, with, uh, Cloudera and machine learning, uh, technologies. You you'll be, uh, was able to enhance AML detection and reduce the time to identify new links from months 2, 3, 3 weeks. >>Excellent mass let's speak about MasterCard. So MasterCard's principle businesses to process payments between banks and merchants and the credit issuing banks and credit unions of the purchasers who use the MasterCard brand debit and credit cards to make purchases MasterCard chose Cloudera enterprise for fraud detection, and to optimize their DW infrastructure, delivering deepens insights and best practices in big data security and compliance. Uh, next let's speak about, uh, bank Rakka yet, uh, in Indonesia or Bri. Um, it, VRI is one of the largest and oldest banks in Indonesia and engages in the provision of general banking services. Uh, it's headquartered in Jakarta Indonesia. Uh, Bri is well known for its focus on financing initiatives and serves over 75 million customers through it's more than 11,000 offices and rural service outposts. Uh, Bri required better insight to understand customer activity and identify fraudulent transactions. Uh, the bank needed a solid foundation that allowed it to leverage the power of advanced analytics, artificial intelligence, and machine learning to gain better understanding of customers and the market. >>Uh, Bri used, uh, Cloudera enterprise data platform to build an agile and reliable, predictive augmented intelligence solution, uh, to enhance its credit scoring system and to address the rising concern around data security from regulators, uh, and customers, uh, Bri developed a real-time fraud detection service, uh, powered by Cloudera and Kafka. Uh, Bri's data scientists developed a machine learning model for fraud detection by creating a behavioral scoring model based on customer savings, uh, loan transactions, deposits, payroll and other financial, um, uh, real-time time data. Uh, this led to improvements in its fraud detection and credit scoring capabilities, as well as the development of a, of a new digital microfinancing product, uh, with the enablement of real-time fraud detection, VRI was able to reduce the rate of fraud by 40%. Uh, it improved, uh, relationship manager productivity by two and a half fold. Uh, it improved the credit score scoring system to cut down on micro-financing loan processing times from two weeks to two days to now two minutes. So fraud prevention is a good area to start with a data focus. If you haven't already, it offers a quick return on investment, uh, and it's a focused area. That's not too entrenched across the company, uh, to learn more about fraud prevention, uh, go to kroger.com and to schedule, and you should schedule a meeting with Cloudera, uh, to learn even more. Uh, and with that, thank you for listening and thank you for your time. >>Welcome to the customer. Obsession begins with data session. Uh, thank you for, for attending. Um, at Cloudera, we believe that a custom session begins with, uh, with, with data, um, and, uh, you know, financial services is Cloudera is largest industry vertical. We have approximately 425 global financial services customers, uh, which consists of 82 out of a hundred of the largest global banks of which we have 27 that are globally systemic banks, uh, four out of the five top stock exchanges, eight out of the 10 top wealth management firms and all four of the top credit card networks. Uh, so as you can see most financial services institutions utilize Cloudera for data analytics and machine learning. Uh, we also have over 20 central banks and it doesn't or so financial regulators. So it's an incredible footprint, which glimpse Cloudera, lots of insight into the many innovations that our customers are coming up with. >>Customers have grown more independent and demanding. Uh, they want the ability to perform many functions on their own and, uh, be able to do it. Uh, he do them on their mobile devices, uh, in a recent Accenture study, more than 50% of customers, uh, are focused on, uh, improving their customer experience through more personalized offers and advice. The study found that 75% of people are actually willing to share their data for better personalized offers and more efficient and intuitive services to get it better, better understanding of your customers, use all the data available to develop a complete view of your customer and, uh, and better serve them. Uh, this also breaks down, uh, costly silos, uh, shares data in, in accordance with privacy laws and assists with regulatory advice. It's so different organizations are going to be at different points in their data analytics and AI journey. >>Uh, there are several degrees of streaming and batch data, both structured and unstructured. Uh, you need a platform that can handle both, uh, with common, with a common governance layer, um, near real time. And, uh, real-time sources help make data more relevant. So if you look at this graphic, looking at it from left to right, uh, normal streaming and batch data comes from core banking and, uh, and lending operations data in pretty much a structured format as financial institutions start to evolve. Uh, they start to ingest near real-time streaming data that comes not only from customers, but also from, from newsfeeds for example, and they start to capture more behavioral data that they can use to evolve their models, uh, and customer experience. Uh, ultimately they start to ingest more real time streaming data, not only, um, standard, uh, sources like market and transaction data, but also alternative sources such as social media and connected sources, such as wearable devices, uh, giving them more, more data, better data, uh, to extract intelligence and drive personalized actions based on data in real time at the right time, um, and use machine learning and AI, uh, to drive anomaly detection and protect and predict, uh, present potential outcomes. >>So this is another way to look at it. Um, this slide shows the progression of the big data journey as it relates to a customer experience example, um, the dark blue represents, um, visibility or understanding your customer. So we have a data warehouse and are starting to develop some analytics, uh, to know your customer and start to provide a better customer 360 experience. Uh, the medium blue area, uh, is a customer centric or where we learn, uh, the customer's behavior. Uh, at this point we're improving our analytics, uh, gathering more customer centric information to perform, uh, some more exploratory, uh, data sciences. And we can start to do things like cross sell or upsell based on the customer's behavior, which should improve, uh, customer retention. The light blue area is, uh, is proactive customer inter interactions, or where we now have the ability, uh, to predict customers needs and wants and improve our interaction with the customer, uh, using applied machine learning and, and AI, uh, the Cloudera data platform, um, you know, business use cases require enabling, uh, the end-to-end journey, which we referred to as the data life cycle, uh, what the data life cycle, what is the data life cycle that our customers want, uh, to take their data through, to enable the end to end data journey. >>If you ask our customers, they want different types of analytics, uh, for their diverse user bases to help them implement their, their, their use cases while managed by a centralized security and governance later layer. Uh, in other words, um, the data life cycle to them provides multifunction analytics, uh, at each stage, uh, within the data journey, uh, that, uh, integrated and centralized, uh, security, uh, and governance, for example, uh, enterprise data consists of real time and transactional type type data. Examples include, uh, click stream data, web logs, um, machine generated, data chat bots, um, call center interactions, uh, transactions, uh, within legacy applications, market data, et cetera. We need to manage, uh, that data life cycle, uh, to provide real enterprise data insights, uh, for use cases around enhanced them, personalized customer experience, um, customer journey analytics next best action, uh, sentiment and churn analytics market, uh, campaign optimization, uh, mortgage, uh, processing optimization and so on. >>Um, we bring a diverse set of data then, um, and then enrich it with other data about our customers and products, uh, provide reports and dashboards such as customer 360 and use predictions from machine models to provide, uh, business decisions and, and offers of, uh, different products and services to customers and maintain customer satisfaction, um, by using, um, sentiment and churn analytics. These examples show that, um, the whole data life cycle is involved, um, and, uh, is in continuous fashion in order to meet these types of use cases, uh, using a single cohesive platform that can be, uh, that can be served by CDP, uh, the data, the Cloudera data platform. >>Okay. Uh, let's talk about, uh, some of the experiences, uh, from our customers. Uh, first we'll talk about Bunco suntan there. Um, is a major global bank headquartered in Spain, uh, with, uh, major operations and subsidiaries all over Europe and north and, and south America. Uh, one of its subsidiaries, something there UK wanted to revolutionize the customer experience with the use of real time data and, uh, in app analytics, uh, for mobile users, however, like many financial institutions send them there had a, he had a, had a large number of legacy data warehouses spread across many business use, and it's within consistent data and different ways of calculating the same metrics, uh, leading to different results. As a result, the company couldn't get the comprehensive customer insights it needed. And, uh, and business staff often worked on multiple versions of the truth. Sometime there worked with Cloudera to improve a single data platform that could support all its workloads, including self-service analytics, uh, operational analytics and data science processes, processing processing, 10 million transactions daily or 30,000 transactions per second at peak times. >>And, uh, bringing together really, uh, nearly two to two petabytes of data. The platform provides unprecedented, uh, customer insight and business value across the organization, uh, over 80 cents. And there has realized impressive, uh, benefits spanning, uh, new revenues, cost savings and risk reductions, including creating analytics for, for corporate customers with near real-time shopping behavior, um, and, and helping identify 7,000 new corporate, uh, customer prospects, uh, reducing capital expenditures by, uh, 3.2 million annually and decreasing operating expenses by, uh, 650,000, um, enabling marketing to realize, uh, 2.4 million in annual savings on, on cash, on commercial transactions, um, and protecting 3.7 million customers from financial crime impacts through 95, new proactive control alerts, improving risk and capital calculations to reduce the amount of money. It must set aside, uh, as part of a, as part of risk mandates. Uh, for example, in one instance, the risk team was able to release a $5.2 million that it had withheld for non-performing credit card loans by properly identifying healthy accounts miscategorized as high risk next, uh, let's uh, talk about, uh, Rabobank. >>Um, Rabobank is one of the largest banks in the Netherlands, uh, with approximately 8.3 million customers. Uh, it was founded by farmers in the late 19th century and specializes in agricultural financing and sustainability oriented banking, uh, in order to help its customers become more self-sufficient and, uh, improve their financial situations such as debt settlement, uh, rebel bank needed to access, uh, to a varied mix of high quality, accurate, and timely customer data, the talent, uh, to provide this insight, however, was the ability to execute sophisticated and timely data analytics at scale Rabobank was also faced with the challenge of, uh, shortening time to market. Uh, it needed easier access to customer data sets to ensure that they were using and receiving the right financial support at the right time with, with, uh, data quality and speed of processing. Um, highlighted as two vital areas of improvement, Rabobank was looking to incorporate, um, or create new data in an environment that would not only allow the organization to create a centralized repository of high quality data, but also allow them to stream and, uh, conduct data analytics on the fly, uh, to create actionable insights and deliver a strong customer experience bank level Cloudera due to its ability to cope with heavy pressures on data processing and its capability of ingesting large quantities of real time streaming data. >>They were able to quickly create a new data lake that allowed for faster queries of both historical and real time data to analyze customer loan repayment patterns, uh, to up to the minute transaction records, um, Robert bank and, and its customers could now immediately access, uh, the valuable data needed to help them understand, um, the status of their financial situation in this enabled, uh, rebel bank to spot financial disasters before they happened, enabling them to gain deep and timely insights into which customers were at risk of defaulting on loans. Um, having established the foundation of a modern data architecture Rabobank is now able to run sophisticated machine learning algorithms and, uh, financial models, uh, to help customers manage, um, financial, uh, obligations, um, including, uh, long repayments and are able to generate accurate, uh, current real liquidity. I refuse, uh, next, uh, let's uh, speak about, um, uh, OVO. >>Uh, so OVO is the leading digital payment rewards and financial services platform in Indonesia, and is present in 115 million devices across the company across the country. Excuse me. Um, as the volume of, of products within Obos ecosystem increases, the ability to ensure marketing effectiveness is critical to avoid unnecessary waste of time and resources, unlike competitors, uh, banks, w which use traditional mass marketing, uh, to reach customers over, oh, decided to embark on a, on a bold new approach to connect with customers via, uh, ultra personalized marketing, uh, using the Cloudera stack. The team at OVO were able to implement a change point detection algorithm, uh, to discover customer life stage changes. This allowed OVO, uh, to, uh, build a segmentation model of one, uh, the contextual offer engine Bill's recommendation algorithms on top of the product, uh, including collaborative and context-based filters, uh, to detect changes in consumer consumption patterns. >>As a result, OVO has achieved a 15% increase in revenue, thanks to this, to this project, um, significant time savings through automation and eliminating the chance of human error and have reduced engineers workloads by, by 30%. Uh, next let's talk about, uh, bank Bri, uh, bank Bri is one of the largest and oldest, uh, banks in Indonesia, um, engaging in, in general banking services, uh, for its customers. Uh, they are headquartered in, in Jakarta Indonesia, uh, PR is a well-known, uh, for its, uh, focused on micro-financing initiative initiatives and serves over 75 million customers through more than 11,000 offices and rural outposts, um, Bri needed to gain better understanding of their customers and market, uh, to improve the efficiency of its operations, uh, reduce losses from non-performing loans and address the rising concern around data security from regulators and consumers, uh, through enhanced fraud detection. This would require the ability to analyze the vast amounts of, uh, historical financial data and use those insights, uh, to enhance operations and, uh, deliver better service. >>Um, Bri used Cloudera's enterprise data platform to build an agile and reliable, uh, predictive augmented intelligence solution. Uh, Bri was now able to analyze 124 years worth of historical financial data and use those insights to enhance its operations and deliver better services. Um, they were able to, uh, enhance their credit scoring system, um, the solution analyzes customer transaction data, and predicts the probability of a customer defaulting on, on payments. Um, the following month, it also alerts Bri's loan officers, um, to at-risk customers, prompting them to take the necessary action to reduce the likelihood of the net profit lost, uh, this resulted in improved credit, improved credit scoring system, uh, that cut down the approval of micro financing loans, uh, from two weeks to two days to, to two minutes and, uh, enhanced fraud detection. >>All right. Uh, this example shows a tabular representation, uh, the evolution of a customer retention use case, um, the evolution of data and analytics, uh, journey that, uh, that for that use case, uh, from aware, uh, text flirtation, uh, to optimization, to being transformative, uh, with every level, uh, data sources increase. And, uh, for the most part, uh, are, are less, less standard, more dynamic and less structured, but always adding more value, more insights into the customer, uh, allowing us to continuously improve our analytics, increase the velocity of the data we ingest, uh, from, from batch, uh, to, uh, near real time, uh, to real-time streaming, uh, the volume of data we ingest continually increases and we progress, uh, the value of the data on our customers, uh, is continuously improving, allowing us to interact more proactively and more efficiently. And, and with that, um, I would, uh, you know, ask you to consider and assess if you are using all the, uh, the data available to understand, uh, and service your customers, and to learn more about, about this, um, you know, visit cloudera.com and schedule a meeting with Cloudera to learn more. And with that, thank you for your time. And thank you for listening.

>>from around the globe. It's the Cube presenting Cuban cloud brought to you by silicon angle. Okay, >>we're now going to explore the vision of the future of cloud computing From the perspective of one of the leaders in the field, J G >>Share >>a pure off is the vice president of As Your Data ai and Edge at Microsoft G. Welcome to the Cuban cloud. Thanks so much for participating. >>Well, thank you, Dave, and it's a real pleasure to be here with you. And I just wanna welcome the audience as well. >>Well, jg judging from your title, we have a lot of ground to cover, and our audience is definitely interested in all the topics that are implied there. So let's get right into it. You know, we've said many times in the Cube that the new innovation cocktail comprises machine intelligence or a I applied to troves of data. With the scale of the cloud. It's it's no longer, you know, we're driven by Moore's law. It's really those three factors, and those ingredients are gonna power the next wave of value creation and the economy. So, first, do you buy into that premise? >>Yes, absolutely. we do buy into it. And I think, you know, one of the reasons why we put Data Analytics and Ai together is because all of that really begins with the collection of data and managing it and governing it, unlocking analytics in it. And we tend to see things like AI, the value creation that comes from a I as being on that continues off, having started off with really things like analytics and proceeding toe. You know, machine learning and the use of data. Interesting breaks. Yes. >>I'd like to get some more thoughts around a data and how you see the future data and the role of cloud and maybe how >>Microsoft, you >>know, strategy fits in there. I mean, you, your portfolio, you got you got sequel server, Azure, Azure sequel. You got arc, which is kinda azure everywhere for people that aren't familiar with that. You've got synapse. Which course that's all the integration a data warehouse, and get things ready for B I and consumption by the business and and the whole data pipeline and a lot of other services as your data bricks you got You got cosmos in their, uh, Blockchain. You've got open source services like Post Dress and my sequel. So lots of choices there. And I'm wondering, you know, how do you think about the future of Of of Cloud data platforms? It looks like your strategies, right tool for the right job? Is that fair? >>It is fair, but it's also just to step back and look at it. It's fundamentally what we see in this market today is that customer was the Sikh really a comprehensive proposition? And when I say a comprehensive proposition, it is sometimes not just about saying that. Hey, listen way No, you're a sequel server company. We absolutely trust that you have the best Azure sequel database in the cloud, but tell us more. We've got data that's sitting in her group systems. We've got data that's sitting in Post Press in things like mongo DB, right? So that open source proposition today and data and data management and database management has become front and center, so are really sort of push. There is when it comes to migration management, modernization of data to present the broadest possible choice to our customers so we can meet them where they are. However, when it comes to analytics. One of the things they asked for is give us a lot more convergence use. You know it, really, it isn't about having 50 different services. It's really about having that one comprehensive service that is converged. That's where things like synapse Fitzer, where in just land any kind of data in the leg and then use any compute engine on top of it to drive insights from it. So, fundamentally, you know, it is that flexibility that we really sort of focus on to meet our customers where they are and really not pushing our dogma and our beliefs on it. But to meet our customers according to the way they have deployed stuff like this. >>So that's great. I want to stick on this for a minute because, you know, I know when when I have guests on like yourself, do you never want to talk about you know, the competition? But that's all we ever talk about. That's all your customers ever talk about, because because the counter to that right tool for the right job and that I would say, is really kind of Amazon's approach is is that you got the single unified data platform, the mega database that does it all. And that's kind of Oracle's approach. It sounds like you wanna have your cake and eat it, too, so you you got the right tool for the right job approach. But you've got an integration layer that allows you to have that converge database. I wonder if you could add color to that and you confirm or deny what I just said. >>No, that's a That's a very fair observation, but I I say there's a nuance in what I sort of describe when it comes to data management. When it comes to APS, we have them customers with the broadest choice. Even in that, even in that perspective, we also offer convergence. So, case in point, when you think about Cosmos TV under that one sort of service, you get multiple engines, but with the same properties, right global distribution, the five nines availability. It gives customers the ability to basically choose when they have to build that new cloud native AB toe, adopt cosmos Davey and adopted in a way that it's and choose an engine that is most flexible. Tow them, however you know when it comes to say, you know, writing a sequel server, for example from organizing it you know you want. Sometimes you just want to lift and shift it into things. Like I asked In other cases, you want to completely rewrite it, so you need to have the flexibility of choice there that is presented by a legacy off What's its on premises? When it moved into things like analytics, we absolutely believe in convergence, right? So we don't believe that look, you need to have a relation of data warehouse that is separate from a loop system that is separate from, say, a B I system. That is just, you know, it's a bolt on for us. We love the proposition off, really building things that are so integrated that once you land data, once you prep it inside the lake, you can use it for analytics. You can use it for being. You can use it for machine learning. So I think you know, are sort of differentiated. Approach speaks for itself there. Well, >>that's that's interesting, because essentially, again, you're not saying it's an either or, and you're seeing a lot of that in the marketplace. You got some companies say no, it's the Data Lake and others saying No, no put in the data warehouse and that causes confusion and complexity around the data pipeline and a lot of calls. And I'd love to get your thoughts on this. Ah, lot of customers struggled to get value out of data and and specifically data product builders of frustrated that it takes too long to go from. You know, this idea of Hey, I have an idea for a data service and it could drive monetization, but to get there, you gotta go through this complex data lifecycle on pipeline and beg people to add new data sources. And do you do you feel like we have to rethink the way that we approach data architectures? >>Look, I think we do in the cloud, and I think what's happening today and I think the place where I see the most amount of rethink the most amount of push from our customers to really rethink is the area of analytics in a I. It's almost as if what worked in the past will not work going forward. Right? So when you think about analytics on in the Enterprise today, you have relational systems, you have produced systems. You've got data marts. You've got data warehouses. You've got enterprise data warehouses. You know, those large honking databases that you use, uh, to close your books with right? But when you start to modernize it, what deep you are saying is that we don't want to simply take all of that complexity that we've built over say, you know, 34 decades and simply migrated on mass exactly as they are into the cloud. What they really want is a completely different way of looking at things. And I think this is where services like synapse completely provide a differentiated proposition to our customers. What we say there is land the data in any way you see shape or form inside the lake. Once you landed inside the lake, you can essentially use a synapse studio toe. Prep it in the way that you like, use any compute engine of your choice and and operate on this data in any way that you see fit. So, case in point, if you want to hydrate relation all data warehouse, you can do so if you want to do ad hoc analytics using something like spark. You can do so if you want to invoke power. Bi I on that data or b i on that data you can do so if you want to bring in a machine learning model on this breath data you can do so, so inherently. So when customers buy into this proposition, what it solves for them and what it gives them is complete simplicity, right? One way to land the data, multiple ways to use it. And it's all eso. >>Should we think of synapse as an abstraction layer that abstracts away the complexity of the underlying technology? Is that a fair way toe? Think about it. >>Yeah, you can think of it that way. It abstracts away, Dave a couple of things. It takes away the type of data, you know, sort of the complexities related to the type of data. It takes away the complexity related to the size of data. It takes away the complexity related to creating pipelines around all these different types of data and fundamentally puts it in a place where it can be now consumed by any sort of entity inside the actual proposition. And by that token, even data breaks. You know, you can, in fact, use data breaks in in sort off an integrated way with a synapse, Right, >>Well, so that leads me to this notion of and then wonder if you buy into it s Oh, my inference is that a data warehouse or a data lake >>could >>just be a node in inside of a global data >>mesh on. >>Then it's synapses sort of managing, uh, that technology on top. Do you buy into that that global data mesh concept >>we do. And we actually do see our customers using synapse and the value proposition that it brings together in that way. Now it's not where they start. Often times when a customer comes and says, Look, I've got an enterprise data warehouse, I want to migrate it or I have a group system. I want to migrate it. But from there, the evolution is absolutely interesting to see. I give you an example. You know, one of the customers that we're very proud off his FedEx And what FedEx is doing is it's completely reimagining its's logistics system that basically the system that delivers What is it? The three million packages a day on in doing so in this covert times, with the view of basically delivering our covert vaccines. One of the ways they're doing it is basically using synapse. Synapse is essentially that analytic hub where they can get complete view into their logistic processes. Way things are moving, understand things like delays and really put all that together in a way that they can essentially get our packages and these vaccines delivered as quickly as possible. Another example, you know, is one of my favorite, uh, we see once customers buy into it, they essentially can do other things with it. So an example of this is, uh is really my favorite story is Peace Parks Initiative. It is the premier Air White Rhino Conservancy in the world. They essentially are using data that has landed in azure images in particular. So, basically, you know, use drones over the vast area that they patrol and use machine learning on this data to really figure out where is an issue and where there isn't an issue so that this part with about 200 rangers can scramble surgically versus having to read range across the last area that they cover. So What do you see here is you know, the importance is really getting your data in order. Landed consistently. Whatever the kind of data ideas build the right pipelines and then the possibilities of transformation are just endless. >>Yeah, that's very nice how you worked in some of the customer examples. I appreciate that. I wanna ask you, though, that that some people might say that putting in that layer while it clearly adds simplification and e think a great thing that they're begins over time to be be a gap, if you will, between the ability of that layer to integrate all the primitives and all the peace parts on that, that you lose some of that fine grain control and it slows you down. What would you say to that? >>Look, I think that's what we excel at, and that's what we completely sort of buy into on. It's our job to basically provide that level off integration that granularity in the way that so it's an art, absolutely admit it's an art. There are areas where people create simplicity and not a lot of you know, sort of knobs and dials and things like that. But there are areas where customers want flexibility, right? So I think just to give you an example of both of them in landing the data inconsistency in building pipelines, they want simplicity. They don't want complexity. They don't want 50 different places to do this. Just 100 to do it. When it comes to computing and reducing this data analyzing this data, they want flexibility. This is one of the reasons why we say, Hey, listen, you want to use data breaks? If you're you're buying into that proposition and you're absolutely happy with them, you can plug plug it into it. You want to use B I and no, essentially do a small data mart. You can use B I If you say that. Look, I've landed in the lake. I really only want to use em melt, bringing your animal models and party on. So that's where the flexibility comes in. So that's sort of really sort of think about it. Well, >>I like the strategy because, you know, my one of our guest, Jim Octagon, e E. I think one of the foremost thinkers on this notion of off the data mesh and her premises that that that data builders, data product and service builders air frustrated because the the big data system is generic to context. There's no context in there. But by having context in the big data architecture and system, you could get products to market much, much, much faster. So but that seems to be your philosophy. But I'm gonna jump ahead to do my ecosystem question. You've mentioned data breaks a couple of times. There's another partner that you have, which is snowflake. They're kind of trying to build out their own, uh, data cloud, if you will, on global mesh in and the one hand, their partner. On the other hand, there are competitors. How do you sort of balance and square that circle? >>Look, when I see snowflake, I actually see a partner. You know that when we essentially you know, we are. When you think about as you know, this is where I sort of step back and look at Azure as a whole and in azure as a whole. Companies like snowflakes are vital in our ecosystem, right? I mean, there are places we compete, but you know, effectively by helping them build the best snowflake service on Asia. We essentially are able toe, you know, differentiate and offer a differentiated value proposition compared to, say, a Google or on AWS. In fact, that's being our approach with data breaks as well, where you know they are effectively on multiple club, and our opportunity with data breaks is toe essentially integrate them in a way where we offer the best experience. The best integrations on Azure Barna That's always been a focus. >>That's hard to argue with. Strategy. Our data with our data partner eat er, shows Microsoft is both pervasive and impressively having a lot of momentum spending velocity within the budget cycles. I wanna come back thio ai a little bit. It's obviously one of the fastest growing areas in our in our survey data. As I said, clearly, Microsoft is a leader in this space. What's your what's your vision of the future of machine intelligence and how Microsoft will will participate in that opportunity? >>Yeah, so fundamentally, you know, we've built on decades of research around, you know, around, you know, essentially, you know, vision, speech and language that's being the three core building blocks and for the for a really focused period of time we focused on essentially ensuring human parody. So if you ever wondered what the keys to the kingdom are it, czar, it's the most we built in ensuring that the research posture that we've taken there, what we then done is essentially a couple of things we focused on, essentially looking at the spectrum. That is a I both from saying that, Hollis and you know it's gotta work for data. Analysts were looking toe basically use machine learning techniques, toe developers who are essentially, you know, coding and building a machine learning models from scratch. So for that select proposition manifesto us, as you know, really a. I focused on all skill levels. The other court thing we've done is that we've also said, Look, it will only work as long as people trust their data and they can trust their AI models. So there's a tremendous body of work and research we do in things like responsibility. So if you ask me where we sort of push on is fundamentally to make sure that we never lose sight of the fact that the spectrum off a I, and you can sort of come together for any skill level, and we keep that responsibly. I proposition. Absolutely strong now against that canvas, Dave. I'll also tell you that you know, as edge devices get way more capable, right where they can input on the edge, see a camera or a mike or something like that, you will see us pushing a lot more of that capability onto the edge as well. But to me, that's sort of a modality. But the core really is all skill levels and that responsible denia. >>Yeah, So that that brings me to this notion of wanna bring an edge and and hybrid cloud Understand how you're thinking about hybrid cloud multi cloud. Obviously one of your competitors, Amazon won't even say the word multi cloud you guys have, Ah, you know, different approach there. But what's the strategy with regard? Toe, toe hybrid. You know, Do you see the cloud you bringing azure to the edge? Maybe you could talk about that and talk about how you're different from the competition. >>Yeah, I think in the edge from Annette, you know, I live in I'll be the first one to say that the word nge itself is conflated. Okay, It's, uh but I will tell you, just focusing on hybrid. This is one of the places where you know I would say the 2020 if I would have looked back from a corporate perspective. In particular, it has Bean the most informative because we absolutely saw customers digitizing moving to the cloud. And we really saw hybrid in action. 2020 was the year that hybrid sort of really became really from a cloud computing perspective and an example of this is we understood it's not all or nothing. So sometimes customers want azure consistency in their data centers. This is where things like Azure stack comes in. Sometimes they basically come to us and say, We want the flexibility of adopting flexible pattern, you know, platforms like, say, containers orchestra, Cuban Pettis, so that we can essentially deployed wherever you want. And so when we design things like art, it was built for that flexibility in mind. So here is the beauty of what's something like our can do for you. If you have a kubernetes endpoint anywhere we can deploy and as your service onto it, that is the promise, which means if for some reason, the customer says that. Hey, I've got this kubernetes endpoint in AWS and I love as your sequel. You will be able to run as your sequel inside AWS. There's nothing that stops you from doing it so inherently you remember. Our first principle is always to meet our customers where they are. So from that perspective, multi cloud is here to stay. You know, we're never going to be the people that says, I'm sorry, we will never see a But it is a reality for our customers. >>So I wonder if we could close. Thank you for that by looking, looking back and then and then ahead. And I wanna e wanna put forth. Maybe it's, Ah criticism, but maybe not. Maybe it's an art of Microsoft, but But first you know, you get Microsoft an incredible job of transitioning. It's business as your nominee president Azzawi said. Our data shows that so two part question First, Microsoft got there by investing in the cloud, really changing its mind set, I think, in leveraging its huge software state and customer base to put Azure at the center of its strategy, and many have said me included that you got there by creating products that air Good enough. You know, we do a 1.0, it's not that great. And the two Dato, and maybe not the best, but acceptable for your customers. And that's allowed you to grow very rapidly expanding market. >>How >>do you respond to that? Is that is that a fair comment? Ume or than good enough? I wonder if you could share your >>thoughts, gave you? You hurt my feelings with that question. I don't hate me, g getting >>it out there. >>So there was. First of all, thank you for asking me that. You know, I am absolutely the biggest cheerleader. You'll find a Microsoft. I absolutely believe you know that I represent the work off almost 9000 engineers and we wake up every day worrying about our customer and worrying about the customer condition and toe. Absolutely. Make sure we deliver the best in the first time that we do. So when you take the platter off products we've delivered in nausea, be it as your sequel, be it as your cosmos TV synapse as your data breaks, which we did in partnership with data breaks, a za machine learning and recently when we prevail, we sort off, you know, sort of offered the world's first comprehensive data government solution in azure purview. I would humbly submit to you that we're leading the way and we're essentially showing how the future off data ai and the actual work in the cloud. >>I'd be disappointed if you if you had If you didn't, if you capitulated in any way J g So so thank you for that. And the kind of last question is, is looking forward and how you're thinking about the future of cloud last decade. A lot about your cloud migration simplifying infrastructure management, deployment SAS if eyeing my enterprise, lot of simplification and cost savings. And, of course, the redeployment of resource is toward digital transformation. Other other other valuable activities. How >>do >>you think this coming decade will will be defined? Will it be sort of more of the same? Or is there Is there something else out there? >>I think I think that the coming decade will be one where customers start one law outside value out of this. You know what happened in the last decade when people leave the foundation and people essentially looked at the world and said, Look, we've got to make the move, you know, the largely hybrid, but we're going to start making steps to basically digitize and modernize our platforms. I would tell you that with the amount of data that people are moving to the cloud just as an example, you're going to see use of analytics ai for business outcomes explode. You're also going to see a huge sort of focus on things like governance. You know, people need to know where the data is, what the data catalog continues, how to govern it, how to trust this data and given all other privacy and compliance regulations out there. Essentially, they're complying this posture. So I think the unlocking of outcomes versus simply Hey, I've saved money Second, really putting this comprehensive sort off, you know, governance, regime in place. And then, finally, security and trust. It's going to be more paramount than ever before. Yeah, >>nobody's gonna use the data if they don't trust it. I'm glad you brought up your security. It's It's a topic that hits number one on the CEO list. J G. Great conversation. Obviously the strategy is working, and thanks so much for participating in Cuba on cloud. >>Thank you. Thank you, David. I appreciate it and thank you to. Everybody was tuning in today. >>All right? And keep it right there. I'll be back with our next guest right after this short break.

>>From around the globe. It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS. >>Welcome to cube three 60 fives coverage of the Accenture executive summit. Part of AWS reinvent. I'm your host Rebecca Knight. Today we are joined by a cube alum Karthik NurAin. He is Accenture senior managing director and lead Accenture cloud. First, welcome back to the show Karthik. >>Thank you. Thanks for having me here. >>Always a pleasure. So I want to talk to you. You are an industry veteran, you've been in Silicon Valley for decades. Um, I want to hear from your perspective what the impact of the COVID-19 pandemic has been, what are you hearing from clients? What are they struggling with? What are their challenges that they're facing day to day? >>I think, um, COVID-19 is being a eye-opener from, you know, various facets, you know, um, first and foremost, it's a, it's a head, um, situation that everybody's facing, which is not just, uh, highest economic bearings to it. It has enterprise, um, an organization with bedding to it. And most importantly, it's very personal to people, um, because they themselves and their friends, family near and dear ones are going to this challenge, uh, from various different dimension. But putting that aside, when you come to it from an organization enterprise standpoint, it has changed everything well, the behavior of organizations coming together, working in their campuses, working with each other as friends, family, and, uh, um, near and dear colleagues, all of them are operating differently. So that's what big change to get things done in a completely different way, from how they used to get things done. >>Number two, a lot of things that were planned for normal scenarios, like their global supply chain, how they interact with their client customers, how they coordinate with their partners on how that employees contribute to the success of an organization at all changed. And there are no data models that give them a hint of something like this for them to be prepared for this. So we are seeing organizations, um, that have adapted to this reasonably okay, and are, you know, launching to innovate faster in this. And there are organizations that have started with struggling, but are continuing to struggle. And the gap, uh, between the leaders and legs are widening. So this is creating opportunities in a different way for the leaders, um, with a lot of pivot their business, but it's also creating significant challenge for the lag guides, uh, as we defined in our future systems research that we did a year ago, uh, and those organizations are struggling further. So the gap is actually whitening. >>So you've just talked about the widening gap. I've talked about the tremendous uncertainty that so many companies, even the ones who have adapted reasonably well, uh, in this, in this time, talk a little bit about Accenture cloud first and why, why now? >>I think it's a great question. Um, we believe that for many of our clients COVID-19 has turned, uh, cloud from an experimentation aspiration to an origin mandate. What I mean by that is everybody has been doing something on the other end cloud. There's no company that says we don't believe in cloud. Uh, our, we don't want to do cloud. It was how much they did in cloud. And they were experimenting. They were doing the new things in cloud. Um, but they were operating a lot of their core business outside the cloud or not in the cloud. Those organizations have struggled to operate in this new normal, in a remote fashion as with us, uh, that ability to pivot to all the changes the pandemic has brought to them. But on the other hand, the organizations that had a solid foundation in cloud were able to collect faster and not actually gone into the stage of innovating faster and driving a new behavior in the market, new behavior within their organization. >>So we are seeing that spend to make is actually fast-forwarded something that we always believed was going to happen. This, uh, uh, moving to cloud over the next decade is fast, forwarded it to, uh, happen in the next three to five years. And it's created this moment where it's a once in an era, really replatforming of businesses in the cloud that we are going to see. And we see this moment as a cloud first moment where organizations will use cloud as the, the canvas and the foundation with which they're going to reimagine their business after they were born in the cloud. Uh, and this requires a whole new strategy. Uh, and as Accenture, we are getting a lot in cloud, but we thought that this is the moment where we bring all of that capabilities together because we need a strategy for addressing, moving to cloud are embracing cloud in a holistic fashion. And that's what Accenture cloud first brings together a holistic strategy, a team that's 70,000 plus people that's coming together with rich cloud skills, but investing to tie in all the various capabilities of cloud to Delaware, that holistic strategy to our clients. So I want you to >>Delve into a little bit more about what this strategy actually entails. I mean, it's clearly about embracing change and being willing to experiment and, and having capabilities to innovate. Can you tell us a little bit more about what this strategy entails? >>Yeah. The reason why we say that there's a need for the strategy is, like I said, COVID is not new. There's almost every customer client is doing something with the cloud, but all of them have taken different approaches to cloud and different boundaries to cloud. Some organizations say, I just need to consolidate my multiple data centers to a small data center footprint and move the nest to cloud. Certain other organizations say that well, I'm going to move certain workloads to cloud. Certain other organizations said, well, I'm going to build this Greenfield application or workload in cloud. Certain other said, um, I'm going to use the power of AI ML in the cloud to analyze my data and drive insights. But a cloud first strategy is all of this tied with the corporate strategy of the organization with an industry specific cloud journey to say, if in this current industry, if I were to be reborn in the cloud, would I do it in the exact same passion that I did in the past, which means that the products and services that they offer need to be the matching, how they interact with that customers and partners need to be revisited, how they bird and operate their IP systems need to be the, imagine how they unearthed the data from all the systems under which they attract need to be liberated so that you could drive insights of cloud. >>First strategy. Hans is a corporate wide strategy, and it's a C-suite responsibility. It doesn't take the ownership away from the CIO or CIO, but the CIO is, and CDI was felt that it was just their problem and they were to solve it. And everyone as being a customer, now, the center of gravity is elevated to it becoming a C-suite agenda on everybody's agenda, where probably the CDI is the instrument to execute that that's a holistic cloud-first strategy >>And it, and it's a strategy, but the way you're describing it, it sounds like it's also a mindset and an approach, as you were saying, this idea of being reborn in the cloud. So now how do I think about things? How do I communicate? How do I collaborate? How do I get done? What I need to get done. Talk a little bit about how this has changed, the way you support your clients and how Accenture cloud first is changing your approach to cloud services. >>Wonderful. Um, you know, I did not color one very important aspect in my previous question, but that's exactly what you just asked me now, which is to do all of this. I talked about all of the vehicles, uh, an organization or an enterprise is going to go to, but the good part is they have one constant. And what is that? That is their employees, uh, because you do, the employees are able to embrace this change. If they are able to, uh, change them, says, pivot them says retool and train themselves to be able to operate in this new cloud. First one, the ability to reimagine every function of the business would be happening at speed. And cloud first approach is to do all of this at speed, because innovation is deadly proposed there, do the rate of probability on experimentation. You need to experiment a lot for any kind of experimentation. >>There's a probability of success. Organizations need to have an ability and a mechanism for them to be able to innovate faster for which they need to experiment a lot. The more the experiment and the lower cost at which they experiment is going to help them experiment a lot and experiment demic speed, fail fast, succeed more. And hence, they're going to be able to operate this at speed. So the cloud-first mindset is all about speed. I'm helping the clients fast track that innovation journey, and this is going to happen. Like I said, across the enterprise and every function across every department, I'm the agent of this change is going to be the employee's weapon, race, this change through new skills and new grueling and new mindset that they need to adapt to. >>So Karthik what you're describing it, it sounds so exciting. And yet for a pandemic wary workforce, that's been working remotely that may be dealing with uncertainty if for their kid's school and for so many other aspects of their life, it sounds hard. So how are you helping your clients, employees get onboard with this? And because the change management is, is often the hardest part. >>Yeah, I think it's, again, a great question. A bottle has only so much capacity. Something got to come off for something else to go in. That's what you're saying is absolutely right. And that is again, the power of cloud. The reason why cloud is such a fundamental breakthrough technology and capability for us to succeed in this era, because it helps in various forms. What we talked so far is the power of innovation that could create, but cloud can also simplify the life of the employees in an enterprise. There are several activities and tasks that people do in managing their complex infrastructure, complex ID landscape. They used to do certain jobs and activities in a very difficult, uh, underground about with cloud has simplified. And democratised a lot of these activities. So that things which had to be done in the past, like managing the complexity of the infrastructure, keeping them up all the time, managing the, um, the obsolescence of the capabilities and technologies and infrastructure, all of that could be offloaded to the cloud. >>So that the time that is available for all of these employees can be used to further innovate. Every organization is good to spend almost the same amount of money, but rather than spending activities, by looking at the rear view mirror on keeping the lights on, they're going to spend more money, more time, more energy, and spend their skills on things that are going to add value to their organization. Because you, every innovation that an enterprise can give to their end customer need not come from that enterprise. The word of platform economy is about democratising innovation. And the power of cloud is to get all of these capabilities from outside the four walls of the enterprise, >>It will add value to the organization, but I would imagine also add value to that employee's life because that employee, the employee will be more engaged in his or her job and therefore bring more excitement and energy into her, his or her day-to-day activities too. >>Absolutely. Absolutely. And this is, this is a normal evolution we would have seen everybody would have seen in their lives, that they keep moving up the value chain of what activities that, uh, gets performed buying by those individuals. And there's this, um, you know, no more true than how the United States, uh, as an economy has operated where, um, this is the power of a powerhouse of innovation, where the work that's done inside the country keeps moving up to that. You change. And, um, us leverages the global economy for a lot of things that is required to power the United States and that global economic, uh, phenomenon is very proof for an enterprise as well. There are things that an enterprise needs to do them soon. There are things an employee needs to do themselves. Um, but there are things that they could leverage from the external innovation and the power of innovation that is coming from technologies like cloud. >>So at Accenture, you have long, long, deep Stan, sorry, you have deep and long standing relationships with many cloud service providers, including AWS. How does the Accenture cloud first strategy, how does it affect your relationships with those providers? >>Yeah, we have great relationships with cloud providers like AWS. And in fact, in the cloud world, it was one of the first, um, capability that we started about years ago, uh, when we started developing these capabilities. But five years ago, we hit a very important milestone where the two organizations came together and said that we are forging a pharma partnership with joint investments to build this partnership. And we named that as a Accenture, AWS business group ABG, uh, where we co-invest and brought skills together and develop solutions. And we will continue to do that. And through that investment, we've also made several acquisitions that you would have seen in the recent times, like, uh, an invoice and gecko that we made acquisitions in in Europe. But now we're taking this to the next level. What we are saying is two cloud first and the $3 billion investment that we are bringing in, uh, through cloud first, we are going to make specific investment to create unique joint solution and landing zones foundation, um, cloud packs with which clients can accelerate their innovation or their journey to cloud first. >>And one great example is what we are doing with Takeda, uh, billable, pharmaceutical giant, um, between we've signed a five-year partnership. And it was out in the media just a month ago or so, where we are, the two organizations are coming together. We have created a partnership as a power of three partnership where the three organizations are jointly hoarding hats and taking responsibility for the innovation and the leadership position that Decatur wants to get to with this. We are going to simplify their operating model and organization by providing it flexibility. We're going to provide a lot more insights. Tequila has a 230 year old organization. Imagine the amount of trapped data and intelligence that is there. How about bringing all of that together with the power of AWS and Accenture and Takeda to drive more customer insights, um, come up with breakthrough, uh, R and D uh, accelerate clinical trials and improve the patient experience using AI ML and edge technologies. So all of these things that we will do through this partnership with joint investment from Accenture cloud first, as well as partner like AWS, so that Takeda can realize their gain. And, uh, they're seeing you actually made a statement that five years from now, every ticket an employee will have an AI assistant. That's going to make that beginner employee move up the value chain on how they contribute and add value to the future of tequila with the AI assistant, making them even more equipped and smarter than what they could be otherwise. >>So, one last question to close this out here. What is your future vision for, for Accenture cloud first? What are we going to be talking about at next year's Accenture executive summit? Yeah, the future >>Is going to be, um, evolving, but the part that is exciting to me, and this is, uh, uh, a fundamental belief that we are entering a new era of industrial revolution from industry first, second, and third industry. The third happened probably 20 years ago with the advent of Silicon and computers and all of that stuff that happened here in the Silicon Valley. I think the fourth industrial revolution is going to be in the cross section of, uh, physical, digital and biological boundaries. And there's a great article, um, in what economic forum that, that people, uh, your audience can Google and read about it. Uh, but the reason why this is very, very important is we are seeing a disturbing phenomenon that over the last 10 years, they are seeing a Blackwing of the, um, labor productivity and innovation, which has dropped to about 2.1%. When you see that kind of phenomenon over that longer period of time, there has to be breakthrough innovation that needs to happen to come out of this barrier and get to the next base camp, as I would call it to further this productivity, um, lack that we are seeing, and that is going to happen in the intersection of the physical, digital and biological boundaries. >>And I think cloud is going to be the connective tissue between all of these three, to be able to provide that where it's the edge, especially is going to come closer to the human lives. It's going to come from cloud pick totally in your mind, you can think about cloud as central, either in a private cloud, in a data center or in a public cloud, you know, everywhere. But when you think about edge, it's going to be far reaching and coming close to where we live and maybe work and very, um, get entertained and so on and so forth. And there's going to be, uh, intervention in a positive way in the field of medicine, in the field of entertainment, in the field of, um, manufacturing in the field of, um, uh, you know, mobility. When I say mobility, human mobility, people, transportation, and so on and so forth with all of this stuff, cloud is going to be the connective tissue and the vision of cloud first is going to be, uh, you know, blowing through this big change that is going to happen. And the evolution that is going to happen where, you know, the human grace of mankind, um, our person kind of being very gender neutral in today's world. Um, go first needs to be that beacon of, uh, creating the next generation vision for enterprises to take advantage of that kind of an exciting future. And that's why it, Accenture. We say, let there be change as our, as a purpose. >>I genuinely believe that cloud first is going to be in the forefront of that change agenda, both for Accenture as well as for the rest of the world. Excellent. Let there be change, indeed. Thank you so much for joining us Karthik. A pleasure I'm Rebecca night's stay tuned for more of Q3 60 fives coverage of the Accenture executive summit >>From around the globe. It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS >>Welcome everyone to the Q virtual and our coverage of the Accenture executive summit, which is part of AWS reinvent 2020. I'm your host Rebecca Knight. Today, we are talking about the green, the cloud and joining me is Kishor Dirk. He is Accenture senior managing director cloud first global services lead. Thank you so much for coming on the show. Kishor nice to meet you. So I want to start by asking you what it is that we mean when we say green cloud, we know that sustainability is a business imperative. So many organizations around the world are committing to responsible innovation, lowering carbon emissions, but what's this, what is it? What does it mean when they talk about cloud from a sustainability perspective? I think it's about responsible innovation being cloud is a cloud first approach that has profits and benefit the clients by helping reduce carbon emissions. >>Think about it this way. You have a large number of data centers. Each of these data centers are increasing by 14% every year. And this double digit growth. What you're seeing is these data centers and the consumption is nearly coolant to the kind of them should have a country like Spain. So the magnitude of the problem that is out there and how do we pursue a green approach. If you look at this, our Accenture analysis, in terms of the migration to public cloud, we've seen that we can reduce that by 59 million tons of CO2 per year with just the 5.9% reduction in total ID emissions and equates this to 22 million cars off the road. And the magnitude of reduction can go a long way in meeting climate change commitments, particularly for data sensitive. >>Wow, that's incredible. What the numbers that you're putting forward are, are absolutely mind blowing. So how does it work? Is it a simple cloud migration? So, you know, when companies begin their cloud journey and then they confront, uh, with them a lot of questions, the decision to make, uh, this particular, uh, element sustainable in the solution and benefits they drive and they have to make wise choices, and then they will be unprecedented level of innovation leading to both a greener planet, as well as, uh, a greener balance sheet, I would say, uh, so effectively it's all about ambition data, the ambition, greater the reduction in carbon emissions. So from a cloud migration perspective, we look at it as a, as a simple solution with approaches and sustainability benefits, uh, that vary based on things it's about selecting the right cloud provider, a very carbon thoughtful provider and the first step towards a sustainable cloud journey. >>And here we're looking at cloud operators, obviously they have different corporate commitments towards sustainability, and that determines how they plan, how they build, uh, their, uh, uh, the data centers, how they are consumed and assumptions that operate there and how they, or they retire their data centers. Then, uh, the next element that you want to do is how do you build it ambition, you know, for some of the companies, uh, and average on-prem, uh, drives about 65% energy reduction and the carbon emissions and reduction number was 84%, which is kind of good, I would say. But then if you could go up to 98% by configuring applications to the cloud, that is significant benefit for, uh, for the board. And obviously it's a, a greener cloud that we're talking about. And then the question is, how far can you go? And, uh, you know, the, obviously the companies have to unlock greater financial societal environmental benefits, and Accenture has this cloud based circular operations and sustainable products and services that we bring into play. So it's a, it's a very thoughtful, broader approach that w bringing in, in terms of, uh, just a simple concept of cloud migration, >>We know that in the COVID era, shifting to the cloud has really become a business imperative. How is Accenture working with its clients at a time when all of this movement has been accelerated? How do you partner and what is your approach in terms of helping them with their migration? >>Yeah, I mean, let, let me talk a little bit about the pandemic and the crisis that is there today. And if you really look at that in terms of how we partnered with a lot of our clients in terms of the cloud first approach, I'll give you a couple of examples. We worked with rolls Royce, McLaren, DHL, and others, as part of the ventilator challenge consortium, again, to, uh, coordinate production of medical ventilator surgically needed for the UK health service. Many of these farms I've taken similar initiatives in, in terms of, uh, you know, from a few manufacturers hand sanitizers and to hand sanitizers, and again, leading passionate labels, making PPE, and again, at the UN general assembly, we launched the end-to-end integration guide that helps company essentially to have a sustainable development goals. And that's how we have parking at a very large scale. >>Uh, and, and if you really look at how we work with our clients and what is Accenture's role there, uh, you know, from, in terms of our clients, you know, there are multiple steps that we look at. One is about, uh, planning, building, deploying, and managing an optimal green cloud solution. And Accenture has this concept of, uh, helping clients with a platform to kind of achieve that goal. And here we are having, we are having a platform or a mine app, which has a module called BGR advisor. And this is a capability that helps you provide optimal green cloud, uh, you know, a business case, and obviously a blueprint for each of our clients and right from the start in terms of how do we complete cloud migration recommendation to an improved solution, accurate accuracy to obviously bringing in the end to end perspective, uh, you know, with this green card advisor capability, we're helping our clients capture what we call as a carbon footprint for existing data centers and provide, uh, I would say the current cloud CO2 emission score that, you know, obviously helps them, uh, with carbon credits that can further that green agenda. >>So essentially this is about recommending a green index score, reducing carbon footprint for migration migrating for green cloud. And if we look at how Accenture itself is practicing what we preach, 95% of our applications are in the cloud. And this migration has helped us, uh, to lead to about $14.5 million in benefit. And in the third year and another 3 million analytics costs that are saved through right-sizing a service consumption. So it's a very broad umbrella and a footprint in terms of how we engage societaly with the UN or our clients. And what is it that we exactly bring to our clients in solving a specific problem? >>Accenture isn't is walking the walk, as you say yes. >>So that's that instead of it, we practice what we preach, and that is something that we take it to heart. We want to have a responsible business and we want to practice it. And we want to advise our clients around that >>You are your own use case. And so they can, they know they can take your advice. So talk a little bit about, um, the global, the cooperation that's needed. We know that conquering this pandemic is going to take a coordinated global effort and talk a little bit about the great reset initiative. First of all, what is that? Why don't we, why don't we start there and then we can delve into it a little bit more. >>Okay. So before we get to how we are cooperating, the great reset, uh, initiative is about improving the state of the world. And it's about a group of global stakeholders cooperating to simultaneously manage the direct consequences of their COVID-19 crisis. Uh, and in spirit of this cooperation that we're seeing during COVID-19, uh, which will obviously either to post pandemic, to tackle the world's pressing issues. As I say, uh, we are increasing companies to realize a combined potential of technology and sustainable impact to use enterprise solutions, to address with urgency and scale, and, um, obviously, uh, multiple challenges that are facing our world. One of the ways that you're increasing, uh, companies to reach their readiness cloud with Accenture's cloud core strategy is to build a solid foundation that is resilient and will be able to faster to the current, as well as future times. Now, when you think of cloud as the foundation, uh, that drives the digital transformation, it's about scale speed, streamlining your operations, and obviously reducing costs. >>And as these businesses seize the construct of cloud first, they must remain obviously responsible and trusted. Now think about this, right, as part of our analysis, uh, that profitability can co-exist with responsible and sustainable practices. Let's say that all the data centers, uh, migrated from on-prem to cloud based, we estimate that would reduce carbon emissions globally by 60 million tons per year. Uh, and think about it this way, right? Easier metric would be taking out 22 million cars off the road. Um, the other examples that you've seen, right, in terms of the NHS work that they're doing, uh, in, in UK to build, uh, uh, you know, uh, Microsoft teams in based integration. And, uh, the platform rolled out for 1.2 million in interest users, uh, and got 16,000 users that we were able to secure, uh, instant messages, obviously complete audio video calls and host virtual meetings across India. So, uh, this, this work that we did with NHS is something that we have are collaborating with a lot of tools and powering businesses. >>Well, you're vividly describing the business case for sustainability. What do you see as the future of cloud when thinking about it from this lens of sustainability, and also going back to what you were talking about in terms of how you are helping your, your fostering cooperation within these organizations. >>Yeah, that's a very good question. So if you look at today, right, businesses are obviously environmentally aware and they are expanding efforts to decrease power consumption, carbon emissions, and they want to run a sustainable operational efficiency across all elements of their business. And this is an increasing trend, and there is that option of energy efficient infrastructure in the global market. And this trend is the cloud first thinking. And with the right cloud migration that we've been discussing is about unlocking new opportunity, like clean energy foundations enable enabled by cloud based geographic analysis, material, waste reductions, and better data insights. And this is something that, uh, uh, we'll we'll drive, uh, with obviously faster analytics platform that is out there. Now, the sustainability is actually the future of business, which is companies that are historically different, the financial security or agility benefits to cloud. Now sustainability becomes an imperative for them. And I would on expedience Accenture's experience with cloud migrations, we have seen 30 to 40% total cost of ownership savings. And it's driving a greater workload, flexibility, better service, your obligation, and obviously more energy efficient, uh, public clouds that cost we'll see that, that drive a lot of these enterprise own data centers. So in our view, what we are seeing is that this, this, uh, sustainable cloud position helps, uh, helps companies to, uh, drive a lot of the goals in addition to their financial and other goods. >>So what should organizations who are, who are watching this interview and saying, Hey, I need to know more, what, what do you recommend to them? And what, where should they go to get more information on Greenplum? >>No, if you you're, if you are a business leader and you're thinking about which cloud provider is good, or how, how should applications be modernized to meet our day-to-day needs, which cloud driven innovations should be priorities. Uh, you know, that's why Accenture, uh, formed up the cloud first organization and essentially to provide the full stack of cloud services to help our clients become a cloud first business. Um, you know, it's all about excavation, uh, the digital transformation innovating faster, creating differentiated, uh, and sustainable value for our clients. And we're powering it up at 70,000 cloud professionals, $3 billion investment, and, uh, bringing together and services for our clients in terms of cloud solutions. And obviously the ecosystem partnership that we have that we are seeing today, uh, and the assets that help our clients realize their goals. Um, and again, to do reach out to us, uh, we can help them determine obviously, an optimal, sustainable cloud for solution that meets the business needs and being unprecedented levels of innovation. Our experience will be our advantage. And now more than ever, Rebecca, >>Just closing us out here. Do you have any advice for these companies who are navigating a great deal of uncertainty? We, what, what do you think the next 12 to 24 months? What do you think that should be on the minds of CEOs as they go through? >>So, as CEO's are thinking about rapidly leveraging cloud, migrating to cloud, uh, one of the elements that we want them to be thoughtful about is can they do that, uh, with unprecedent level of innovation, but also build a greener planet and a greener balance sheet, if we can achieve this balance and kind of, uh, have a, have a world which is greener, I think the world will win. And we all along with Accenture clients will win. That's what I would say, uh, >>Optimistic outlook. And I will take it. Thank you so much. Kishor for coming on the show >>That was >>Accenture's Kishor Dirk, I'm Rebecca Knight stay tuned for more of the cube virtuals coverage of the Accenture executive summit >>Around the globe. >>It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS. >>Welcome everyone to the cube virtual and our coverage of the Accenture executive summit. Part of AWS reinvent 2020. I'm your host Rebecca Knight. Today, we are talking about the power of three. And what happens when you bring together the scientific know-how of a global bias biopharmaceutical powerhouse in Takeda, a leading cloud services provider in AWS, and Accenture's ability to innovate, execute, and deliver innovation. Joining me to talk about these things. We have Aaron, sorry, Arjun, baby. He is the senior managing director and chairman of Accenture's diamond leadership council. Welcome Arjun Karl hick. He is the chief digital and information officer at Takeda. >>What is your bigger, thank you, Rebecca >>And Brian bowhead, global director, and head of the Accenture AWS business group at Amazon web services. Thanks so much for coming on. Thank you. So, as I said, we're talking today about this relationship between, uh, your three organizations. Carl, I want to talk with you. I know you're at the beginning of your cloud journey. What was the compelling reason? What, what, why, why move to the cloud and why now? >>Yeah, no, thank you for the question. So, you know, as a biopharmaceutical leader, we're committed to bringing better health and a brighter future to our patients. We're doing that by translating science into some really innovative and life transporting therapies, but throughout, you know, we believe that there's a responsible use of technology, of data and of innovation. And those three ingredients are really key to helping us deliver on that promise. And so, you know, while I think, uh, I'll call it, this cloud journey is already always been a part of our strategy. Um, and we've made some pretty steady progress over the last years with a number of I'll call it diverse approaches to the digital and AI. We just weren't seeing the impact at scale that we wanted to see. Um, and I think that, you know, there's a, there's a need ultimately to, you know, accelerate and, uh, broaden that shift. >>And, you know, we were commenting on this earlier, but there's, you know, it's been highlighted by a number of factors. One of those has been certainly a number of the large acquisitions we've made Shire, uh, being the most pressing example, uh, but also the global pandemic, both of those highlight the need for us to move faster, um, at the speed of cloud, ultimately. Uh, and so we started thinking outside of the box because it was taking us too long and we decided to leverage this strategic partner model. Uh, and it's giving us a chance to think about our challenges very differently. We call this the power of three, uh, and ultimately our focus is singularly on our patients. I mean, they're waiting for us. We need to get there faster. It can take years. And so I think that there is a focus on innovation, um, at a rapid speed, so we can move ultimately from treating conditions to keeping people healthy. >>So as you are embarking on this journey, what are some of the insights you want to share about, about what you're seeing so far? >>Yeah, no, it's a great question. So, I mean, look, maybe right before I highlight some of the key insights, uh, I would say that, you know, with cloud now as the, as the launchpad for innovation, you know, our vision all along has been that in less than 10 years, we want every single to kid, uh, associate we're employed to be empowered by an AI assistant. And I think that, you know, that's going to help us make faster, better decisions. That'll help us, uh, fundamentally deliver transformative therapies and better experiences to, to that ecosystem, to our patients, to physicians, to payers, et cetera, much faster than we previously thought possible. Um, and I think that technologies like cloud and edge computing together with a very powerful I'll call it data fabric is going to help us to create this, this real-time, uh, I'll call it the digital ecosystem. >>The data has to flow ultimately seamlessly between our patients and providers or partners or researchers, et cetera. Uh, and so we've been thinking about this, uh, I'll call it legal, hold up, sort of this pyramid, um, that helps us describe our vision. Uh, and a lot of it has to do with ultimately modernizing the foundation, modernizing and rearchitecting, the platforms that drive the company, uh, heightening our focus on data, which means that there's an accelerated shift towards enterprise data platforms and digital products. And then ultimately, uh, uh, P you know, really an engine for innovation sitting at the very top. Um, and so I think with that, you know, there's a few different, uh, I'll call it insights that, you know, are quickly kind of come zooming into focus. I would say one is this need to collaborate very differently. Um, you know, not only internally, but you know, how do we define ultimately, and build a connected digital ecosystem with the right partners and technologies externally? >>I think the second, uh, component that maybe people don't think as much about, but, you know, I find critically important is for us to find ways of really transforming our culture. We have to unlock talent and shift the culture certainly as a large biopharmaceutical very differently. And then lastly, you've touched on it already, which is, you know, innovation at the speed of cloud. How do we re-imagine that, you know, how do ideas go from getting tested and months to kind of getting tested in days? You know, how do we collaborate very differently? Uh, and so I think those are three, uh, perhaps of the larger I'll call it, uh, insights that, you know, the three of us are spending a lot of time thinking about right now. >>So Arjun, I want to bring you into this conversation a little bit. Let's, let's delve into those a bit. Talk first about the collaboration, uh, that Carl was referencing there. How, how have you seen that it is enabling, uh, colleagues and teams to communicate differently and interact in new and different ways? Uh, both internally and externally, as Carl said, >>No, th thank you for that. And, um, I've got to give call a lot of credit, because as we started to think about this journey, it was clear, it was a bold ambition. It was, uh, something that, you know, we had all to do differently. And so the, the concept of the power of three that Carl has constructed has become a label for us as a way to think about what are we going to do to collectively drive this journey forward. And to me, the unique ways of collaboration means three things. The first one is that, um, what is expected is that the three parties are going to come together and it's more than just the sum of our resources. And by that, I mean that we have to bring all of ourselves, all of our collective capabilities, as an example, Amazon has amazing supply chain capabilities. >>They're one of the best at supply chain. So in addition to resources, when we have supply chain innovations, uh, that's something that they're bringing in addition to just, uh, talent and assets, similarly for Accenture, right? We do a lot, uh, in the talent space. So how do we bring our thinking as to how we apply best practices for talent to this partnership? So, um, as we think about this, so that's, that's the first one, the second one is about shared success very early on in this partnership, we started to build some foundations and actually develop seven principles that all of us would look at as the basis for this success shared success model. And we continue to hold that sort of in the forefront, as we think about this collaboration. And maybe the third thing I would say is this one team mindset. So whether it's the three of our CEOs that get together every couple of months to think about, uh, this partnership, or it is the governance model that Carl has put together, which has all three parties in the governance and every level of leadership, we always think about this as a collective group, so that we can keep that front and center. >>And what I think ultimately has enabled us to do is it allowed us to move at speed, be more flexible. And ultimately all we're looking at the target the same way, the North side, the same way. >>Brian, what about you? What have you observed and what are you thinking about in terms of how this is helping teams collaborate differently? >>Yeah, absolutely. And RJ made some, some great points there. And I think if you really think about what he's talking about, it's that, that diversity of talent, diversity of skill and viewpoint and even culture, right? And so we see that in the power of three. And then I think if we drill down into what we see at Takeda, and frankly, Takeda was, was really, I think, pretty visionary and on their way here, right. And taking this kind of cross-functional approach and applying it to how they operate day to day. So moving from a more functional view of the world to more of a product oriented view of the world, right? So when you think about we're going to be organized around a product or a service or a capability that we're going to provide to our customers or our patients or donors in this case, it implies a different structure, although altogether, and a different way of thinking, right? >>Because now you've got technical people and business experts and marketing experts, all working together in this is sort of cross collaboration. And what's great about that is it's really the only way to succeed with cloud, right? Because the old ways of thinking where you've got application people and infrastructure, people in business, people is suboptimal, right? Because we can all access this tool was, and these capabilities and the best way to do that, isn't across kind of a cross collaborative way. And so this is product oriented mindset. It's a keto was already on. I think it's allowed us to move faster in those areas. >>Carl, I want to go back to this idea of unlocking talent and culture. And this is something that both Brian and Arjun have talked about too. People are, are an essential part of their, at the heart of your organization. How will their experience of work change and how are you helping re-imagine and reinforce a strong organizational culture, particularly at this time when so many people are working remotely. >>Yeah. It's a great question. And it's something that, you know, I think we all have to think a lot about, I mean, I think, um, you know, driving this, this call it, this, this digital and data kind of capability building, uh, takes a lot of, a lot of thinking. So, I mean, there's a few different elements in terms of how we're tackling this one is we're recognizing, and it's not just for the technology organization or for those actors that, that we're innovating with, but it's really across all of the Cato where we're working through ways of raising what I'll call the overall digital leaders literacy of the organization, you know, what are the, you know, what are the skills that are needed almost at a baseline level, even for a global bio-pharmaceutical company and how do we deploy, I'll call it those learning resources very broadly. >>And then secondly, I think that, you know, we're, we're very clear that there's a number of areas where there are very specialized skills that are needed. Uh, my organization is one of those. And so, you know, we're fostering ways in which, you know, we're very kind of quickly kind of creating, uh, avenues excitement for, for associates in that space. So one example specifically, as we use, you know, during these very much sort of remote, uh, sort of days, we, we use what we call global it days, and we set a day aside every single month and this last Friday, um, you know, we, we create during that time, it's time for personal development. Um, and we provide active seminars and training on things like, you know, robotic process automation, data analytics cloud, uh, in this last month we've been doing this for months and months now, but in his last month, more than 50% of my organization participated, and there's this huge positive shift, both in terms of access and excitement about really harnessing those new skills and being able to apply them. >>Uh, and so I think that that's, you know, one, one element that, uh, can be considered. And then thirdly, um, of course, every organization to work on, how do you prioritize talent, acquisition and management and competencies that you can't rescale? I mean, there are just some new capabilities that we don't have. And so there's a large focus that I have with our executive team and our CEO and thinking through those critical roles that we need to activate in order to kind of, to, to build on this, uh, this business led cloud transformation. And lastly, probably the hardest one, but the one that I'm most jazzed about is really this focus on changing the mindsets and behaviors. Um, and I think there, you know, this is where the power of three is, is really, uh, kind of coming together nicely. I mean, we're working on things like, you know, how do we create this patient obsessed curiosity, um, and really kind of unlock innovation with a real, kind of a growth mindset. >>Uh, and the level of curiosity that's needed, not to just continue to do the same things, but to really challenge the status quo. So that's one big area of focus we're having the agility to act just faster. I mean, to worry less, I guess I would say about kind of the standard chain of command, but how do you make more speedy, more courageous decisions? And this is places where we can emulate the way that a partner like AWS works, or how do we collaborate across the number of boundaries, you know, and I think, uh, Arjun spoke eloquently to a number of partnerships that we can build. So we can break down some of these barriers and use these networks, um, whether it's within our own internal ecosystem or externally to help, to create value faster. So a lot of energy around ways of working and we'll have to check back in, but I mean, we're early in on this mindset and behavioral shift, um, but a lot of good early momentum. >>Carl you've given me a good segue to talk to Brian about innovation, because you said a lot of the things that I was the customer obsession and this idea of innovating much more quickly. Obviously now the world has its eyes on drug development, and we've all learned a lot about it, uh, in the past few months and accelerating drug development is all, uh, is of great interest to all of us. Brian, how does a transformation like this help a company's, uh, ability to become more agile and more innovative and at a quicker speed to, >>Yeah, no, absolutely. And I think some of the things that Carl talked about just now are critical to that, right? I think where sometimes folks fall short is they think, you know, we're going to roll out the technology and the technology is going to be the silver bullet where we're, in fact it is the culture. It is, is the talent. And it's the focus on that. That's going to be, you know, the determinant of success. And I will say, you know, in this power of three arrangement and Carl talked a little bit about the pyramid, um, talent and culture and that change, and the kind of thinking about that has been a first-class citizen since the very beginning, right. That absolutely is critical for, for being there. Um, and, and so that's been, that's been key. And so we think about innovation at Amazon and AWS, and Carl mentioned some of the things that, you know, partner like AWS can bring to the table is we talk a lot about builders, right? >>So kind of obsessive about builders. Um, and, and we meet what we mean by that is we at Amazon, we hire for builders, we cultivate builders and we like to talk to our customers about it as well. And it also implies a different mindset, right? When you're a builder, you have that, that curiosity, you have that ownership, you have that stake in whatever I'm creating, I'm going to be a co-owner of this product or this service, right. Getting back to that kind of product oriented mindset. And it's not just the technical people or the it people who are builders. It is also the business people as, as Carl talked about. Right. So when we start thinking about, um, innovation again, where we see folks kind of get into a little bit of a innovation pilot paralysis, is that you can focus on the technology, but if you're not focusing on the talent and the culture and the processes and the mechanisms, you're going to be putting out technology, but you're not going to have an organization that's ready to take it and scale it and accelerate it. >>Right. And so that's, that's been absolutely critical. So just a couple of things we've been doing with, with Takeda and Decatur has really been leading the way is, think about a mechanism and a process. And it's really been working backward from the customer, right? In this case, again, the patient and the donor. And that was an easy one because the key value of Decatur is to be a patient focused bio-pharmaceutical right. So that was embedded in their DNA. So that working back from that, that patient, that donor was a key part of that process. And that's really deep in our DNA as well. And Accenture's, and so we were able to bring that together. The other one is, is, is getting used to experimenting and even perhaps failing, right. And being able to iterate and fail fast and experiment and understanding that, you know, some decisions, what we call it at Amazon or two-way doors, meaning you can go through that door, not like what you see and turn around and go back. And cloud really helps there because the costs of experimenting and the cost of failure is so much lower than it's ever been. You can do it much faster and the implications are so much less. So just a couple of things that we've been really driving, uh, with the cadence around innovation, that's been really critical. Carl, where are you already seeing signs of success? >>Yeah, no, it's a great question. And so we chose, you know, uh, with our focus on innovation to try to unleash maybe the power of data digital in, uh, in focusing on what I call sort of a Maven. And so we chose our, our, our plasma derived therapy business, um, and you know, the plasma-derived therapy business unit, it develops critical life-saving therapies for patients with rare and complex diseases. Um, but what we're doing is by bringing kind of our energy together, we're focusing on creating, I'll call it state of the art digitally connected donation centers. And we're really modernizing, you know, the, the, the donor experience right now, we're trying to, uh, improve also I'll call it the overall plasma collection process. And so we've, uh, selected a number of alcohol at a very high speed pilots that we're working through right now, specifically in this, in this area. And we're seeing >>Really great results already. Um, and so that's, that's one specific area of focus are Jen, I want you to close this out here. Any ideas, any best practices advice you would have for other pharmaceutical companies that are, that are at the early stage of their cloud journey? Yes. Sorry. Arjun. >>Yeah, no, I was breaking up a bit. No, I think they, um, the key is what what's sort of been great for me to see is that when people think about cloud, you know, you always think about infrastructure technology. The reality is that the cloud is really the true enabler for innovation and innovating at scale. And, and if you think about that, right, in all the components that you need, uh, ultimately that's where the value is for the company, right? Because yes, you're going to get some cost synergies and that's great, but the true value is in how do we transform the organization in the case of the Qaeda and the life sciences clients, right. We're trying to take a 14 year process of research and development that takes billions of dollars and compress that right. Tremendous amounts of innovation opportunity. You think about the commercial aspect, lots of innovation can come there. The plasma derived therapy is a great example of how we're going to really innovate to change the trajectory of that business. So I think innovation is at the heart of what most organizations need to do. And the formula, the cocktail that Takeda has constructed with this Fuji program really has all the ingredients, um, that are required for that success. >>Great. Well, thank you so much. Arjun, Brian and Carl was really an enlightening conversation. >>Thank you. Yeah, it's been fun. Thanks Rebecca. >>And thank you for tuning into the cube. Virtual is coverage of the Accenture executive summit >>From around the globe. It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS. >>Welcome everyone to the cubes coverage of Accenture executive summit here at AWS reinvent. I'm your host Rebecca Knight for this segment? We have two guests. First. We have Helen Davis. She is the senior director of cloud platform services, assistant director for it and digital for the West Midlands police. Thanks so much for coming on the show, Helen, and we also have Matthew lb. He is Accenture health and public service associate director and West Midlands police account lead. Thanks so much for coming on the show. Matthew, thank you for joining us. So we are going to be talking about delivering data-driven insights to the West Midlands police force. Helen, I want to start with >>You. Can you tell us a little bit about the West Midlands police force? How big is the force and also what were some of the challenges that you were grappling with prior to this initiative? >>Yeah, certainly. So Westerners police is the second largest police force in the UK, outside of the metropolitan police in London. Um, we have an excessive, um, 11,000 people work at Westman ins police serving communities, um, through, across the Midlands region. So geographically, we're quite a big area as well, as well as, um, being population, um, density, having that as a, at a high level. Um, so the reason we sort of embarked on the data-driven insights platform and it, which was a huge change for us was for a number of reasons. Um, namely we had a lot of disparate data, um, which was spread across a range of legacy systems that were many, many years old, um, with some duplication of what was being captured and no single view for offices or, um, support staff. Um, some of the access was limited. You have to be in a, in an actual police building on a desktop computer to access it. Um, other information could only reach the offices on the front line, through a telephone call back to one of our enabling services where they would do a manual checkup, um, look at the information, then call the offices back, um, and tell them what they needed to know. So it was a very long laborious, um, process and not very efficient. Um, and we certainly weren't exploiting the data that we had in a very productive way. >>So it sounds like as you're describing, and I'm old clunky system that needed a technological, uh, reimagination. So what was the main motivation for, for doing, for making this shift? >>It was really, um, about making us more efficient and more effective in how we do how we do business. So, um, you know, certainly as a, as an it leader and some of my operational colleagues, we recognize the benefits, um, that data analytics could bring in, uh, in a policing environment, not something that was, um, really done in the UK at the time. You know, we have a lot of data, so we're very data rich and the information that we have, but we needed to turn it into information that was actionable. So that's where we started looking for, um, technology partners and suppliers to help us and sort of help us really with what's the art of the possible, you know, this hasn't been done before. So what could we do in this space? That's appropriate, >>Helen. I love that idea. What is the art of the possible, can you tell us a little bit about why you chose AWS? >>I think really, you know, as with all things and when we're procuring a partner in the public sector that, you know, there are many rules and regulations quite rightly as you would expect that to be because we're spending public money. So we have to be very, very careful and, um, it's, it's a long process and we have to be open to public scrutiny. So, um, we sort of look to everything, everything that was available as part of that process, but we recognize the benefits that Clyde would provide in this space because, you know, we're like moving to a cloud environment. We would literally be replacing something that was legacy with something that was a bit more modern. Um, that's not what we wanted to do. Our ambition was far greater than that. So I think, um, in terms of AWS, really, it was around scalability, interoperability, you know, just us things like the disaster recovery service, the fact that we can scale up and down quickly, we call it dialing up and dialing back. Um, you know, it's it's page go. So it just sort of ticked all the boxes for us. And then we went through the full procurement process, fortunately, um, it came out on top for us. So we were, we were able to move forward, but it just sort of had everything that we were looking for in that space. >>Matthew, I want to bring you into the conversation a little bit here. How are you working with a wet with the West Midlands police, sorry. And helping them implement this cloud-first >>Yeah, so I guess, um, by January the West Midlands police started, um, favorite five years ago now. So, um, we set up a partnership with the fools. I wanted to operate in a way that was very different to a traditional supplier relationship. Um, secretary that the data difference insights program is, is one of many that we've been working with last on, um, over the last five years, um, as having said already, um, cloud gave a number of, uh, advantages certainly from a big data perspective and things that, that enabled us today. Um, I'm from an Accenture perspective that allowed us to bring in a number of the different teams that we have say, cloud teams, security teams, um, and drafted from an insurance perspective, as well as the more traditional services that people would associate with the country. >>I mean, so much of this is about embracing comprehensive change to experiment and innovate and try different things. Matthew, how, how do you help, uh, an entity like West Midlands police think differently when they are, there are these ways of doing things that people are used to, how do you help them think about what is the art of the possible, as Helen said, >>There's a few things to that enable those being critical is trying to co-create solutions together. Yeah. There's no point just turning up with, um, what we think is the right answer, try and say, um, collectively work three, um, the issues that the fullest is seeing and the outcomes they're looking to achieve rather than simply focusing on a long list of requirements, I think was critical and then being really open to working together to create the right solution. Um, rather than just, you know, trying to pick something off the shelf that maybe doesn't fit the forces requirements in the way that it should too, >>Right. It's not always a one size fits all. >>Obviously, you know, today what we believe is critical is making sure that we're creating something that met the forces needs, um, in terms of the outcomes they're looking to achieve the financial envelopes that were available, um, and how we can deliver those in a, uh, iterative agile way, um, rather than spending years and years, um, working towards an outcome, um, that is gonna update before you even get that. >>So Helen, how, how are things different? What kinds of business functions and processes have been re-imagined in, in light of this change and this shift >>It's, it's actually unrecognizable now, um, in certain areas of the business as it was before. So to give you a little bit of, of context, when we, um, started working with essentially an AWS on the data driven insights program, it was very much around providing, um, what was called locally, a wizzy tool for our intelligence analyst to interrogate data, look at data, you know, decide whether they could do anything predictive with it. And it was very much sort of a back office function to sort of tidy things up for us and make us a bit better in that, in that area or a lot better in that area. And it was rolled out to a number of offices, a small number on the front line. Um, and really it was, um, in line with a mobility strategy that we, hardware officers were getting new smartphones for the first time, um, to do sort of a lot of things on, on, um, policing apps and things like that to again, to avoid them, having to keep driving back to police stations, et cetera. >>And the pilot was so successful. Every officer now has access to this data, um, on their mobile devices. So it literally went from a handful of people in an office somewhere using it to do sort of clever whizzbang things to, um, every officer in the force, being able to access that level of data at their fingertips. Literally. So what they were touched we've done before is if they needed to check and address or check details of an individual, um, just as one example, they would either have to, in many cases, go back to a police station to look it up themselves on a desktop computer. Well, they would have to make a call back to a centralized function and speak to an operator, relay the questions, either, wait for the answer or wait for a call back with the answer when those people are doing the data interrogation manually. >>So the biggest change for us is the self-service nature of the data we now have available. So officers can do it themselves on their phone, wherever they might be. So the efficiency savings from that point of view are immense. And I think just parallel to that is the quality of our, because we had a lot of data, but just because you've got a lot of data and a lot of information doesn't mean it's big data and it's valuable necessarily. Um, so again, it was having the single source of truth as we, as we call it. So you know that when you are completing those safe searches and getting the responses back, that it is the most accurate information we hold. And also you're getting it back within minutes, as opposed to, you know, half an hour, an hour or a drive back to a station. So it's making officers more efficient and it's also making them safer. The more efficient they are, the more time they have to spend out with the public doing what they, you know, we all should be doing, >>Seen that kind of return on investment, because what you were just describing with all the steps that we needed to be taken in prior to this, to verify an address say, and those are precious seconds when someone's life is on the line in, in sort of in the course of everyday police work. >>Absolutely. Yeah, absolutely. It's difficult to put a price on it. It's difficult to quantify. Um, but all the, you know, the minutes here and that certainly add up to a significant amount of efficiency savings, and we've certainly been able to demonstrate the officers are spending less time up police stations as a result or more time out on the front frontline also they're safer because they can get information about what may or may not be and address what may or may not have occurred in an area before very, very quickly without having to wait. >>Thank you. I want to hear your observations of working so closely with this West Midlands police. Have you noticed anything about changes in its culture and its operating model in how police officers interact with one another? Have you seen any changes since this technology change? >>What's unique about the Western new misplaces, the buy-in from the top down, the chief and his exact team and Helen as the leader from an IOT perspective, um, the entire force is bought in. So what is a significant change program? Uh, I'm not trickles three. Um, everyone in the organization, um, change is difficult. Um, and there's a lot of time effort. That's been put into both the technical delivery and the business change and adoption aspects around each of the projects. Um, but you can see the step change that is making in each aspect to the organization, uh, and where that's putting West Midlands police as a leader in, um, technology I'm policing in the UK. And I think globally, >>And this is a question for both of you because Matthew, as you said, change is difficult and there is always a certain intransigence in workplaces about this is just the way we've always done things and we're used to this and don't try us to get us. Don't try to get us to do anything new here. It works. How do you get the buy-in that you need to do this kind of digital transformation? >>I think it, it would be wrong to say it was easy. Um, um, we also have to bear in mind that this was one program in a five-year program. So there was a lot of change going on, um, both internally for some of our back office functions, as well as front Tai, uh, frontline offices. So with DDI in particular, I think the stat change occurred when people could see what it could do for them. You know, we had lots of workshops and seminars where we all talk about, you know, big data and it's going to be great and it's data analytics and it's transformational, you know, and quite rightly people that are very busy doing a day job that not necessarily technologists in the main and, you know, are particularly interested quite rightly so in what we are not dealing with the cloud, you know? >>And it was like, yeah, okay. It's one more thing. And then when they started to see on that, on their phones and what teams could do, that's when it started to sell itself. And I think that's when we started to see, you know, to see the stat change, you know, and, and if we, if we have any issues now it's literally, you know, our help desks in meltdown. Cause everyone's like, well, we call it manage without this anymore. And I think that speaks for itself. So it doesn't happen overnight. It's sort of incremental changes and then that's a step change in attitude. And when they see it working and they see the benefits, they want to use it more. And that's how it's become fundamental to all policing by itself, really, without much selling >>You, Helen just made a compelling case for how to get buy in. Have you discovered any other best practices when you are trying to get everyone on board for this kind of thing? >>We've um, we've used a lot of the traditional techniques, things around comms and engagement. We've also used things like, um, the 30 day challenge and nudge theory around how can we gradually encourage people to use things? Um, I think there's a point where all of this around, how do we just keep it simple and keep it user centric from an end user perspective? I think DDI is a great example of where the, the technology is incredibly complex. The solution itself is, um, you know, extremely large and, um, has been very difficult to, um, get delivered. But at the heart of it is a very simple front end for the user to encourage it and take that complexity away from them. Uh, I think that's been critical through the whole piece of DDR. >>One final word from Helen. I want to hear, where do you go from here? What is the longterm vision? I know that this has made productivity, um, productivity savings equivalent to 154 full-time officers. Uh, what's next, >>I think really it's around, um, exploiting what we've got. Um, I use the phrase quite a lot, dialing it up, which drives my technical architects crazy. But so, because it's apparently not that simple, but, um, you know, we've, we've been through significant change in the last five years and we are still continuing to batch all of those changes into everyday, um, operational policing. But what we need to see is we need to exploit and build on the investments that we've made in terms of data and claims specifically, the next step really is about expanding our pool of data and our functions. Um, so that, you know, we keep getting better and better at this. And the more we do, the more data we have, the more refined we can be, the more precise we are with all of our actions. Um, you know, we're always being expected to, again, look after the public purse and do more for less. >>And I think this is certainly an and our cloud journey and, and cloud first by design, which is where we are now, um, is helping us to be future-proofed. So for us, it's very much an investment. And I see now that we have good at embedded in operational policing for me, this is the start of our journey, not the end. So it's really exciting to see where we can go from here. Exciting times. Indeed. Thank you so much. Lily, Helen and Matthew for joining us. I really appreciate it. Thank you. And you are watching the cube stay tuned for more of the cubes coverage of the AWS reinvent Accenture executive summit. I'm Rebecca Knight from around the globe. It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS. >>Welcome to the cube virtual coverage of the executive summit at AWS reinvent 2020 virtual. This is the cube virtual. We can't be there in person like we are every year we have to be remote. This executive summit is with special programming supported by Accenture where the cube virtual I'm your host John for a year, we had a great panel here called uncloud first digital transformation from some experts, Stuart driver, the director of it and infrastructure and operates at lion Australia, Douglas Regan, managing director, client account lead at lion for Accenture as a deep Islam associate director application development lead for Centure gentlemen, thanks for coming on the cube virtual that's a mouthful, all that digital, but the bottom line it's cloud transformation. This is a journey that you guys have been on together for over 10 years to be really a digital company. Now, some things have happened in the past year that kind of brings all this together. This is about the next generation organization. So I want to ask Stuart you first, if you can talk about this transformation at lion has undertaken some of the challenges and opportunities and how this year in particular has brought it together because you know, COVID has been the accelerant of digital transformation. Well, if you're 10 years in, I'm sure you're there. You're in the, uh, on that wave right now. Take a minute to explain this transformation journey. >>Yeah, sure. So a number of years back, we, we looked at kind of our infrastructure in our landscape trying to figure out where we >>Wanted to go next. And we were very analog based and stuck in the old it groove of, you know, Capitol reef rash, um, struggling to transform, struggling to get to a digital platform and we needed to change it up so that we could become very different business to the one that we were back then obviously cloud is an accelerant to that. And we had a number of initiatives that needed a platform to build on. And a cloud infrastructure was the way that we started to do that. So we went through a number of transformation programs that we didn't want to do that in the old world. We wanted to do it in a new world. So for us, it was partnering up with a dried organizations that can take you on the journey and, uh, you know, start to deliver bit by bit incremental progress, uh, to get to the, uh, I guess the promise land. >>Um, we're not, not all the way there, but to where we're on the way along. And then when you get to some of the challenges like we've had this year, um, it makes all of the hard work worthwhile because you can actually change pretty quickly, um, provide capacity and, uh, and increase your environments and, you know, do the things that you need to do in a much more dynamic way than we would have been able to previously where we might've been waiting for the hardware vendors, et cetera, to deliver capacity. So for us this year, it's been a pretty strong year from an it perspective and delivering for the business needs >>Before I hit the Douglas. I want to just real quick, a redirect to you and say, you know, if all the people said, Oh yeah, you got to jump on cloud, get in early, you know, a lot of naysayers like, well, wait till to mature a little bit, really, if you got in early and you, you know, paying your dues, if you will taking that medicine with the cloud, you're really kind of peaking at the right time. Is that true? Is that one of the benefits that comes out of this getting in the cloud? Yeah, >>John, this has been an unprecedented year, right. And, um, you know, Australia, we had to live through Bush fires and then we had covert and, and then we actually had to deliver a, um, a project on very nice transformational project, completely remote. And then we also had had some, some cyber challenges, which is public as well. And I don't think if we weren't moved into and enabled through the cloud, we would have been able to achieve that this year. It would have been much different and would have been very difficult to do the backing. We're able to work and partner with Amazon through this year, which is unprecedented and actually come out the other end and we've delivered a brand new digital capability across the entire business. Um, in many, you know, wouldn't have been impossible if we could, I guess, stayed in the old world. The fact that we were moved into the new Naval by the new allowed us to work in this unprecedented year. >>Just quilt. What's your personal view on this? Because I've been saying on the Cuban reporting necessity is the mother of all invention and the word agility has been kicked around as kind of a cliche, Oh, it'd be agile. You know, we're going to get the city, you get a minute on specifically, but from your perspective, uh, Douglas, what does that mean to you? Because there is benefits there for being agile. And >>I mean, I think as Stuart mentioned, right, in a lot of these things we try to do and, you know, typically, you know, hardware and, uh, the last >>To be told and, and, and always on the critical path to be done, we really didn't have that in this case, what we were doing with our projects in our deployments, right. We were able to move quickly able to make decisions in line with the business and really get things going. Right. So you see a lot of times in a traditional world, you have these inhibitors, you have these critical path, it takes weeks and months to get things done as opposed to hours and days, and, and truly allowed us to, we had to, you know, VJ things, move things. And, you know, we were able to do that in this environment with AWS to support and the fact that they can kind of turn things off and on as quickly as we needed. >>Yeah. Cloud-scale is great for speed. So DECA, Gardez get your thoughts on this cloud first mission, you know, it, you know, the dev ops world, they saw this early, that jumping in there, they saw the, the, the agility. Now the theme this year is modern applications with the COVID pandemic pressure, there's real business pressure to make that happen. How did you guys learn to get there fast? And what specifically did you guys do at Accenture and how did it all come together? Can you take us inside kind of how it played out? >>Right. So, yeah, we started off with, as we do in most cases with a much more bigger group, and we worked with lions functional experts and, uh, the lost knowledge that allowed the infrastructure had. Um, we then applied our journey to cloud strategy, which basically revolves around the seminars and, and, uh, you know, the deep three steps from our perspective, uh, assessing the current and bottom and setting up the new cloud environment. And as we go modernizing and, and migrating these applications to the cloud now, you know, one of the key things that, uh, you know, we learned along this journey was that, you know, you can have the best plans, but bottom line that we were dealing with, we often than not have to make changes, uh, what a lot of agility and also work with a lot of collaboration with the, uh, lion team, as well as, uh, uh, AWS. I think the key thing for me was being able to really bring it all together. It's not just, uh, you know, we want to hear it's all of us working together to make this happen. >>What were some of the learnings real quick journey there? >>So I think perspective, the key learnings were that, you know, uh, you know, work, when you look back at, uh, the, the infrastructure that was that we were trying to migrate over to the cloud. A lot of the documentation, et cetera, was not, uh, available. We were having to, uh, figure out a lot of things on the fly. Now that really required us to have, uh, uh, people with deep expertise who could go into those environments and, and work out, uh, you know, the best ways to, to migrate the workloads to the cloud. Uh, I think, you know, the, the biggest thing for me was making sure all the had on that real SMEs across the board globally, that we could leverage across the various technologies, uh, uh, and, and, and, you know, that would really work in our collaborative and agile environment with line. >>Let's do what I got to ask you. How did you address your approach to the cloud and what was your experience? >>Yeah, for me, it's around getting the foundations right. To start with and then building on them. Um, so, you know, you've got to have your, your, your process and you've got to have your, your kind of your infrastructure there and your blueprints ready. Um, AWS do a great job of that, right. Getting the foundations right. And then building upon it, and then, you know, partnering with Accenture allows you to do that very successfully. Um, I think, um, you know, the one thing that was probably surprising to us when we started down this journey and kind of after we got a long way down the track and looking backwards is actually how much you can just turn off. Right? So a lot of stuff that you, uh, you get electric with a legacy in your environment, and when you start to work through it with the types of people that civic just mentioned, you know, the technical expertise working with the business, um, you can really rationalize your environment and, uh, you know, cloud is a good opportunity to do that, to drive that legacy out. >>Um, so you know, a few things there, the other thing is, um, you've got to try and figure out the benefits that you're going to get out of moving here. So there's no point in just taking something that is not delivering a huge amount of value in the traditional world, moving it into the cloud, and guess what is going to deliver the same limited amount of value. So you've got to transform it, and you've got to make sure that you build it for the future and understand exactly what you're trying to gain out of it. So again, you need a strong collaboration. You need a good partners to work with, and you need good engagement from the business as well, because the kind of, uh, you know, digital transformation, cloud transformation, isn't really an it project, I guess, fundamentally it is at the core, but it's a business project that you've got to get the whole business aligned on. You've got to make sure that your investment streams are appropriate and that's, uh, you're able to understand the benefits and the value that say, you're going to drive back towards the business. >>Let's do it. If you don't mind me asking, what was some of the obstacles you encountered or learnings, um, that might different from the expectation we all been there, Hey, you know, we're going to change the world. Here's the sales pitch, here's the outcome. And then obviously things happen, you know, you learn legacy, okay. Let's put some containerization around that cloud native, um, all that rational. You're talking about what are, and you're going to have obstacles. That's how you learn. That's how perfection has developed. How, what obstacles did you come up with and how are they different from your expectations going in? >>Yeah, they're probably no different from other people that have gone down the same journey. If I'm totally honest, the, you know, 70 or 80% of what you do is relatively easy of the known quantity. It's relatively modern architectures and infrastructures, and you can upgrade, migrate, move them into the cloud, whatever it is, rehost, replatform, rearchitect, whatever it is you want to do, it's the other stuff, right? It's the stuff that always gets left behind. And that's the challenge. It's, it's getting that last bit over the line and making sure that you haven't been invested in the future while still carrying all of your legacy costs and complexity within your environment. So, um, to be quite honest, that's probably taken longer and has been more of a challenge than we thought it would be. Um, the other piece I touched on earlier on in terms of what was surprising was actually how much of, uh, your environment is actually not needed anymore. >>When you start to put a critical eye across it and understand, um, uh, ask the tough questions and start to understand exactly what, what it is you're trying to achieve. So if you ask a part of a business, do they still need this application or this service a hundred percent of the time, they will say yes until you start to lay out to them, okay, now I'm going to cost you this to migrate it or this, to run it in the future. And, you know, here's your ongoing costs and, you know, et cetera, et cetera. And then, uh, for a significant amount of those answers, you get a different response when you start to layer on the true value of it. So you start to flush out those hidden costs within the business, and you start to make some critical decisions as a company based on, uh, based on that. So that was a little tougher than we first thought and probably broader than we thought there was more of that than we anticipated, um, which actually results in a much cleaner environment, post post migration, >>You know, the old expression, if it moves automated, you know, it's kind of a joke on government, how they want to tax everything, you know, you want to automate, that's a key thing in cloud, and you've got to discover those opportunities to create value Stuart and Siddique. Mainly if you can weigh in on this love to know the percentage of total cloud that you have now, versus when you started, because as you start to uncover whether it's by design for purpose, or you discover opportunity to innovate, like you guys have, I'm sure it kind of, you took on some territory inside Lyon, what percentage of cloud now versus start? >>Yeah. And at the start it was minimal, right. You know, close to zero, right. Single and single digits. Right. It was mainly SAS environments that we had, uh, sitting in clouds when we, uh, when we started, um, Doug mentioned earlier on a really significant transformation project, um, that we've undertaken and recently gone live on a multi-year one. Um, you know, that's all stood up on AWS and is a significant portion of our environment, um, in terms of what we can move to cloud. Uh, we're probably at about 80 or 90% now. And the balance bit is, um, legacy infrastructure that is just going to retire as we go through the cycle rather than migrate to the cloud. Um, so we are significantly cloud-based and, uh, you know, we're reaping the benefits of it in a year, like 2020, and makes you glad that you did all of the hard yards in the previous years when you started that business challenges thrown out as, >>So do you any common reaction still the cloud percentage penetration? >>Sorry, I didn't, I didn't guys don't, but I, I was going to say it was, I think it's like the 80 20 rule, right? We, we, we worked really hard in the, you know, I think 2018, 19 to get any person off, uh, after getting onto the cloud and, or the last year is the 20% that we have been migrating. And Stuart said like a non-athlete that is also, that's going to be the diet. And I think our next big step is going to be obviously, you know, the icing on the cake, which is to decommission all these apps as well. Right. So, you know, to get the real benefits out of, uh, the whole conservation program from a, uh, from a >>Douglas and Stewart, can you guys talk about the decision around the cloud because you guys have had success with AWS, why AWS how's that decision made? Can you guys give some insight into some of those thoughts? >>I can, I can start, start off. I think back when the decision was made and it was, Oh, it was a while back, um, you know, there's some clear advantages of moving relay, Ws, a lot of alignment with some of the significant projects and, uh, the trend, that particular one big transformation project that we've alluded to as well. Um, you know, we needed some, um, some very robust and, um, just future proof and, um, proven technology. And AWS gave that to us. We needed a lot of those blueprints to help us move down the path. We didn't want to reinvent everything. So, um, you know, having a lot of that legwork done for us and an AWS gives you that, right. And particularly when you partner up with, uh, with a company like Accenture as well, you get combinations of the technology and the skills and the knowledge to, to move you forward in that direction. >>So, um, you know, for us, it was a, uh, uh, it was a decision based on, you know, best of breed, um, you know, looking forward and, and trying to predict the future needs and, and, and kind of the environmental that we might need. Um, and, you know, partnering up with organizations that can take you on the journey. Yeah. And just to build on it. So obviously, you know, lion's like an NWS, but, you know, we knew it was a very good choice given that, um, uh, the skills and the capability that we had, as well as the assets and tools we had to get the most out of, um, out of AWS. And obviously our, our CEO globally is just spending, you know, announcement about a huge investment that we're making in cloud. Um, but you know, we've, we've worked very well. AWS, we've done some joint workshops and joint investments, um, some joint POC. So yeah, w we have a very good working relationship, AWS, and I think, um, one incident to reflect upon whether it's cyber it's and again, where we actually jointly, you know, dove in with, um, with Amazon and some of their security experts and our experts. And we're able to actually work through that with mine quite successful. So, um, you know, really good behaviors as an organization, but also really good capabilities. >>Yeah. As you guys, you're essential cloud outcomes, research shown, it's the cycle of innovation with the cloud. That's creating a lot of benefits, knowing what you guys know now, looking back certainly COVID is impacted a lot of people kind of going through the same process, knowing what you guys know now, would you advocate people to jump on this transformation journey? If so, how, and what tweaks they make, which changes, what would you advise? >>Uh, I might take that one to start with. Um, I hate to think where we would have been when, uh, COVID kicked off here in Australia and, you know, we were all sent home, literally were at work on the Friday, and then over the weekend. And then Monday, we were told not to come back into the office and all of a sudden, um, our capacity in terms of remote access and I quadrupled, or more four, five X, what we had on the Friday we needed on the Monday. And we were able to stand that up during the day Monday into Tuesday, because we were cloud-based and, uh, you know, we just spun up your instances and, uh, you know, sort of our licensing, et cetera. And we had all of our people working remotely, um, within, uh, you know, effectively one business day. Um, I know peers of mine in other organizations and industries that are relying on kind of a traditional wise and getting hardware, et cetera, that were weeks and months before they could get there the right hardware to be able to deliver to their user base. >>So, um, you know, one example where you're able to scale and, uh, um, get, uh, get value out of this platform beyond probably what was anticipated at the time you talk about, um, you know, less the, in all of these kinds of things. And you can also think of a few scenarios, but real world ones where you're getting your business back up and running in that period of time is, is just phenomenal. There's other stuff, right? There's these programs that we've rolled out, you do your sizing, um, and in the traditional world, you would just go out and buy more servers than you need. And, you know, probably never realize the full value of those, you know, the capability of those servers over the life cycle of them. Whereas, you know, in a cloud world, you put in what you think is right. And if it's not right, you pump it up a little bit when, when all of your metrics and so on, tell you that you need to bump it up. And conversely you scale it down at the same rate. So for us, with the types of challenges and programs and, uh, uh, and just business need, that's come at as this year, uh, we wouldn't have been able to do it without a strong cloud base, uh, to, uh, to move forward. >>You know, Douglas, one of the things I talked to, a lot of people on the right side of history who have been on the right wave with cloud, with the pandemic, and they're happy, they're like, and they're humble. Like, well, we're just lucky, you know, luck is preparation meets opportunity. And this is really about you guys getting in early and being prepared and readiness. This is kind of important as people realize, then you gotta be ready. I mean, it's not just, you don't get lucky by being in the right place, the right time. And there were a lot of companies were on the wrong side of history here who might get washed away. This is a super important, I think, >>To echo and kind of building on what Stewart said. I think that the reason that we've had success and I guess the momentum is we didn't just do it in isolation within it and technology. It was actually linked to broader business changes, you know, creating basically a digital platform for the entire business, moving the business, where are they going to be able to come back stronger after COVID, when they're actually set up for growth, um, and actually allows, you know, a line to achievements growth objectives, and also its ambitions as far as what it wants to do, uh, with growth in whatever they make, do with acquiring other companies and moving into different markets and launching new products. So we've actually done it in a way that is, you know, real and direct business benefit, uh, that actually enables line to grow >>General. I really appreciate you coming. I have one final question. If you can wrap up here, uh, Stuart and Douglas, you don't mind weighing in what's the priorities for the future. What's next for lion in a century >>Christmas holidays, I'll start Christmas holidays. I spent a good year and then a, and then a reset, obviously, right? So, um, you know, it's, it's figuring out, uh, transform what we've already transformed, if that makes sense. So God, a huge proportion of our services sitting in the cloud. Um, but we know we're not done even with the stuff that is in there. We need to take those next steps. We need more and more automation and orchestration. We need to, um, our environment is more future proof. We need to be able to work with the business and understand what's coming at them so that we can, um, you know, build that into, into our environment. So again, it's really transformation on top of transformation is the way that I'll describe it. And it's really an open book, right? Once you get it in and you've got the capabilities and the evolving tool sets that AWS continue to bring to the market based, um, you know, working with the partners to, to figure out how we unlock that value, um, you know, drive our costs down efficiency, uh, all of those kind of, you know, standard metrics. >>Um, but you know, we're looking for the next things to transform and showed value back out to our customer base, um, that, uh, that we continue to, you know, sell our products to and work with and understand how we can better meet their needs. Yeah, I think just to echo that, I think it's really leveraging this and then did you capability they have and getting the most out of that investment. And then I think it's also moving to, uh, and adopting more new ways of working as far as, you know, the speed of the business, um, is getting up to speed in the market is changing. So being able to launch and do things quickly and also, um, competitive and efficient operating costs, uh, now that they're in the cloud, right? So I think it's really leveraging the most out of the platform and then, you know, being efficient in launching things. So putting them with >>Siddique, any word from you on your priorities by you see this year in folding, >>There's got to say like e-learning squares, right, for me around, you know, just journey. This is a journey to the cloud, right? >>And, uh, you know, as well dug into sort of Saturday, it's getting all, you know, different parts of the organization along the journey business to it, to your, uh, product lenders, et cetera. Right. And it takes time. It is tough, but, uh, uh, you know, you got to get started on it. And, you know, once we, once we finish off, uh, it's the realization of the benefits now that, you know, looking forward, I think for, from Alliance perspective, it is, uh, you know, once we migrate all the workloads to the cloud, it is leveraging, uh, all stack drive. And as I think Stewart said earlier, uh, with, uh, you know, the latest and greatest stuff that AWS it's basically working to see how we can really, uh, achieve more better operational excellence, uh, from a, uh, from a cloud perspective. >>Well, Stewart, thanks for coming on with a and sharing your environment and what's going on and your journey you're on the right wave. Did the work you're in, it's all coming together with faster, congratulations for your success, and, uh, really appreciate Douglas with Steve for coming on as well from essential. Thank you for coming on. Thanks, John. Okay. Just the cubes coverage of executive summit at AWS reinvent. This is where all the thought leaders share their best practices, their journeys, and of course, special programming with Accenture and the cube. I'm Sean ferry, your host, thanks for watching from around the globe. It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS. >>Welcome everyone to the cube virtuals coverage of the Accenture executive summit. Part of AWS reinvent 2020. I'm your host Rebecca Knight. We are talking today about reinventing the energy data platform. We have two guests joining us. First. We have Johan Krebbers. He is the GM digital emerging technologies and VP of it. Innovation at shell. Thank you so much for coming on the show, Johan you're welcome. And next we have Liz Dennett. She is the lead solution architect for O S D U on AWS. Thank you so much, Liz, maybe here. So I want to start our conversation by talking about OSD. You like so many great innovations. It started with a problem. Johann, what was the problem you were trying to solve at shell? We go back a couple of years, we started summer 2017, where we had a meeting with the guys from exploration in shell, and the main problem they had, of course, they got lots of lots of data, but are unable to find the right data. They need to work from all over the place and told him >>To, and we'll probably try to solve is how that person working exploration could find their proper date, not just a day, but also the date you really needed that we did probably talked about is summer 2017. And we said, okay, the only way ABC is moving forward is to start pulling that data into a single data platform. And that, that was at the time that we called it as the, you, the subsurface data universe in there was about the shell name was so in, in January, 2018, we started a project with Amazon to start grating a co fricking that building, that Stu environment, that the, the universe, so that single data level to put all your exploration and Wells data into that single environment that was intent. And every cent, um, already in March of that same year, we said, well, from Michele point of view, we will be far better off if we could make this an industry solution and not just a shelf solution, because Shelby, Shelby, if you can make an industry solution, but people are developing applications for it. >>It also is far better than for shell to say we haven't shell special solution because we don't make money out of how we start a day that we can make money out of it. We have access to the data, we can explore the data. So storing the data we should do as efficiently possibly can. So we monitor, we reach out to about eight or nine other last, uh, or I guess operators like the economics, like the tutorials, like the shepherds of this world and say, Hey, we inshallah doing this. Do you want to join this effort? And to our surprise, they all said, yes. And then in September, 2018, we had our kickoff meeting with your open group where we said, we said, okay, if you want to work together and lots of other companies, we also need to look at, okay, how, how we organize that. >>Or if you started working with lots of large companies, you need to have some legal framework around some framework around it. So that's why we went to the open group and say, okay, let's, let's form the old forum as we call it at the time. So it's September, 2080, where I did a Galleria in Houston, but the kickoff meeting for the OT four with about 10 members at the time. So that's just over two years ago, we started an exercise for me called ODU. They kicked it off. Uh, and so that's really them will be coming from and how we've got there. Also >>The origin story. Um, what, so what digging a little deeper there? What were some of the things you were trying to achieve with the OSU? >>Well, a couple of things we've tried to achieve with you, um, first is really separating data from applications for what is, what is the biggest problem we have in the subsurface space that the data and applications are all interlinked or tied together. And if, if you have them and a new company coming along and say, I have this new application and he's access to the data that is not possible because the data often interlinked with the application. So the first thing we did is really breaking the link between the application, the data as those levels, the first thing we did, secondly, put all the data to a single data platform, take the silos out what was happening in the sub-service space. They got all the data in what we call silos in small little islands out there. So what we're trying to do is first break the link to great, great. >>They put the data single day, the bathroom, and the third part, put a standard layer on top of that, it's an API layer on top to equate a platform. So we could create an ecosystem out of companies to start a valving Schoff application on top of dev data platform across you might have a data platform, but you're only successful if have a rich ecosystem of people start developing applications on top of that. And then you can export the data like small companies, last company, university, you name it, we're getting after create an ecosystem out here. So the three things were first break the link between application data, just break it and put data at the center and also make sure that data, this data structure would not be managed by one company, but it would only be met. It would be managed the data structures by the ODI forum. Secondly, then put a, the data, a single data platform certainly then has an API layer on top and then create an ecosystem. Really go for people, say, please start developing applications, because now you had access to the data. I've got the data no longer linked to somebody whose application was all freely available, but an API layer that was, that was all September, 2018, more or less. >>And hear a little bit. Can you talk a little bit about some of the imperatives from the AWS standpoint in terms of what you were trying to achieve with this? Yeah, absolutely. And this whole thing is Johann said started with a challenge that was really brought out at shell. The challenges that geoscientists spend up to 70% of their time looking for data. I'm a geologist I've spent more than 70% of my time trying to find data in these silos. And from there, instead of just figuring out how we could address that one problem, we worked together to really understand the root cause of these challenges and working backwards from that use case OSU and OSU on AWS has really enabled customers to create solutions that span, not just this in particular problem, but can really scale to be inclusive of the entire energy value chain and deliver value from these use cases to the energy industry and beyond. Thank you, Lee, uh, Johann. So talk a little bit about Accenture's cloud first approach and how it has, uh, helped shell work faster and better with speed. >>Well, of course, access a cloud first approach only works together. It's been an Amazon environment, AWS environment. So we're really looking at, uh, at, at Accenture and others altogether helping shell in this space. Now the combination of the two is what we're really looking at, uh, where access of course can be recent knowledge student to that environment operates support knowledge, do an environment. And of course, Amazon will be doing that to today's environment that underpinning their services, et cetera. So, uh, we would expect a combination, a lot of goods when we started rolling out and put in production, the old you are three and bug because we are anus. Then when the release feed comes to the market in Q1, next year of ODU have already started going to Audi production inside shell. But as the first release, which is ready for prime time production across an enterprise will be released just before Christmas, last year when he's still in may of this year. But really three is the first release we want to use for full scale production deployment inside shell, and also the operators around the world. And there is one Amazon, sorry, at that one. Um, extensive can play a role in the ongoing, in the, in deployment building up, but also support environment. >>So one of the other things that we talk a lot about here on the cube is sustainability. And this is a big imperative at so many organizations around the world in particular energy companies. How does this move to OSD you, uh, help organizations become, how is this a greener solution for companies? >>Well, first we make it's a greatest solution because you start making a much more efficient use of your resources, which is already an important one. The second thing we're doing is also, we started ODU in framers, in the oil and gas space in the expert development space. We've grown, uh, OTU in our strategy of growth. I was, you know, also do an alternative energy sociology. We'll all start supporting next year. Things like solar farms, wind farms, uh, the, the dermatomal environment hydration. So it becomes an and an open energy data platform, not just what I want to get into sleep. That's what new industry, any type of energy industry. So our focus is to create, bring the data of all those various energy data sources to get me to a single data platform you can to use AI and other technologies on top of that, to exploit the data, to meet again into a single data platform. >>Liz, I want to ask you about security because security is, is, is such a big concern when it comes to data. How secure is the data on OSD? You, um, actually, can I talk, can I do a follow up on this sustainability talking? Oh, absolutely. By all means. I mean, I want to interject though security is absolutely our top priority. I don't mean to move away from that, but with sustainability, in addition to the benefits of the OSU data platform, when a company moves from on-prem to the cloud, they're also able to leverage the benefits of scale. Now, AWS is committed to running our business in the most environmentally friendly way possible. And our scale allows us to achieve higher resource utilization and energy efficiency than a typical data center. >>Now, a recent study by four 51 research found that AWS is infrastructure is 3.6 times more energy efficient than the median of surveyed enterprise data centers. Two thirds of that advantage is due to higher, um, server utilization and a more energy efficient server population. But when you factor in the carbon intensity of consumed electricity and renewable energy purchases for 51 found that AWS performs the same task with an 88% lower carbon footprint. Now that's just another way that AWS and OSU are working to support our customers is they seek to better understand their workflows and make their legacy businesses less carbon intensive. >>That's that's incorrect. Those are those statistics are incredible. Do you want to talk a little bit now about security? Absolutely. And security will always be AWS is top priority. In fact, AWS has been architected to be the most flexible and secure cloud computing environment available today. Our core infrastructure is built to satisfy. There are the security requirements for the military, local banks and other high sensitivity organizations. And in fact, AWS uses the same secure hardware and software to build and operate each of our regions. So that customers benefit from the only commercial cloud that's hat hits service offerings and associated supply chain vetted and deemed secure enough for top secret workloads. That's backed by a deep set of cloud security tools with more than 200 security compliance and governmental service and key features as well as an ecosystem of partners like Accenture, that can really help our customers to make sure that their environments for their data meet and or exceed their security requirements. Johann, I want you to talk a little bit about how OSD you can be used today. Does it only handle subsurface data? >>Uh, today it's Honda's subserves or Wells data, we go to add to that production around the middle of next year. That means that the whole upstate business. So we've got goes from exploration all the way to production. You've made it together into a single data platform. So production will be added around Q3 of next year. Then a principal. We have a difficult, the elder data that single environment, and we want to extend them to other data sources or energy sources like solar farms, wind farms, uh, hydrogen, hydro, et cetera. So we're going to add a whore, a whole list of audit day energy source to them and be all the data together into a single data club. So we move from a falling guest data platform to an aniseed data platform. That's really what our objective is because the whole industry, if you look it over, look at our companies are all moving in. That same two acts of quantity of course, are very strong in oil and gas, but also increased the, got into the other energy sources like, like solar, like wind, like th like highly attended, et cetera. So we would be moving exactly. But that same method that, that, that the whole OSU can't really support at home. And as a spectrum of energy sources, >>Of course, and Liz and Johan. I want you to close us out here by just giving us a look into your crystal balls and talking about the five and 10 year plan for OSD. You we'll start with you, Liz. What do you, what do you see as the future holding for this platform? Um, honestly, the incredibly cool thing about working at AWS is you never know where the innovation and the journey is going to take you. I personally am looking forward to work with our customers, wherever their OSU journeys, take them, whether it's enabling new energy solutions or continuing to expand, to support use cases throughout the energy value chain and beyond, but really looking forward to continuing to partner as we innovate to slay tomorrow's challenges, Johann first, nobody can look at any more nowadays, especially 10 years own objective is really in the next five years, you will become the key backbone for energy companies for storing your data. You are efficient intelligence and optimize the whole supply energy supply chain in this world down here, you'll uncovers Liz Dennett. Thank you so much for coming on the cube virtual I'm Rebecca Knight stay tuned for more of our coverage of the Accenture executive summit >>From around the globe. It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS. >>Welcome everyone to the cubes coverage of the Accenture executive summit. Part of AWS reinvent. I'm your host Rebecca Knight today we're welcoming back to Kubila. We have Kishor Dirk. He is the Accenture senior managing director cloud first global services lead. Welcome back to the show Kishore. Thank you very much. Nice to meet again. And, uh, Tristan moral horse set. He is the managing director, Accenture cloud first North America growth. Welcome back to you to trust and great to be back in grapes here again, Rebecca. Exactly. Even in this virtual format, it is good to see your faces. Um, today we're going to be talking about my nav and green cloud advisor capability. Kishor I want to start with you. So my nav is a platform that is really celebrating its first year in existence. Uh, November, 2019 is when Accenture introduced it. Uh, but it's, it has new relevance in light of this global pandemic that we are all enduring and suffering through. Tell us a little bit about the lineup platform, what it is that cloud platform to help our clients navigate the complexity of cloud and cloud decisions to make it faster. And obviously, you know, we have in the cloud, uh, you know, with >>The increased relevance and all the, especially over the last few months with the impact of COVID crisis and exhibition of digital transformation, you know, we are seeing the transformation or the acceleration to cloud much faster. This platform that you're talking about has enabled and 40 clients globally across different industries. You identify the right cloud solution, navigate the complexity, provide a cloud specific solution simulate for our clients to meet the strategy business needs, and the clients are loving it. >>I want to go to you now trust and tell us a little bit about how mine nav works and how it helps companies make good cloud choice. >>Yeah, so Rebecca, we we've talked about cloud is, is more than just infrastructure and that's what mine app tries to solve for it. It really looks at a variety of variables, including infrastructure operating model and fundamentally what client's business outcomes, um, uh, our clients are, are looking for and, and identifies the optimal solution for what they need. And we assign this to accelerate and we mentioned the pandemic. One of the big focus now is to accelerate. And so we worked through a three-step process. The first is scanning and assessing our client's infrastructure, their data landscape, their application. Second, we use our automated artificial intelligence engine to interact with. We have a wide variety and library of a collective plot expertise. And we look to recommend what is the enterprise architecture and solution. And then third, before we aligned with our clients, we look to simulate and test this scaled up model. And the simulation gives our clients a way to see what cloud is going to look like, feel like and how it's going to transform their business before they go there. >>Tell us a little bit about that in real life. Now as a company, so many of people are working remotely having to collaborate, uh, not in real life. How is that helping them right now? >>So, um, the, the pandemic has put a tremendous strain on systems, uh, because of the demand on those systems. And so we talk about resiliency. We also now need to collaborate across data across people. Um, I think all of us are calling from a variety of different places where our last year we were all at the VA cube itself. Um, and, and cloud technologies such as teams, zoom that we're we're leveraging now has fundamentally accelerated and clients are looking to onboard this for their capabilities. They're trying to accelerate their journey. They realize that now the cloud is what is going to become important for them to differentiate. Once we come out of the pandemic and the ability to collaborate with their employees, their partners, and their clients through these systems is becoming a true business differentiator for our clients. >>Keisha, I want to talk with you now about my navs multiple capabilities, um, and helping clients design and navigate their cloud journeys. Tell us a little bit about the green cloud advisor capability and its significance, particularly as so many companies are thinking more deeply and thoughtfully about sustainability. >>Yes. So since the launch of my lab, we continue to enhance, uh, capabilities for our clients. One of the significant, uh, capabilities that we have enabled is the being taught advisor today. You know, Rebecca, a lot of the businesses are more environmentally aware and are expanding efforts to decrease power consumption, uh, and obviously carbon emissions and, uh, and run a sustainable operations across every aspect of the enterprise. Uh, as a result, you're seeing an increasing trend in adoption of energy, efficient infrastructure in the global market. And one of the things that we did a lot of research we found out is that there's an ability to influence our client's carbon footprint through a better cloud solution. And that's what the internet brings to us, uh, in, in terms of a lot of the client connotation that you're seeing in Europe, North America and others, lot of our clients are accelerating to a green cloud strategy to unlock beta financial, societal and environmental benefit, uh, through obviously cloud-based circular, operational, sustainable products and services. That is something that we are enhancing my now, and we are having active client discussions at this point of time. >>So Tristan, tell us a little bit about how this capability helps clients make greener decisions. >>Yeah. Um, well, let's start about the investments from the cloud providers in renewable and sustainable energy. Um, they have most of the hyperscalers today, um, have been investing significantly on data centers that are run on renewable energy, some incredibly creative constructs on the how to do that. And sustainability is there for a key, um, key item of importance for the hyperscalers and also for our clients who now are looking for sustainable energy. And it turns out this marriage is now possible. I can, we marry the, the green capabilities of the comm providers with a sustainability agenda of our clients. And so what we look into the way the mine EF works is it looks at industry benchmarks and evaluates our current clients, um, capabilities and carpet footprint leveraging their existing data centers. We then look to model from an end-to-end perspective, how the, their journey to the cloud leveraging sustainable and, um, and data centers with renewable energy. We look at how their solution will look like and, and quantify carbon tax credits, um, improve a green index score and provide quantifiable, um, green cloud capabilities and measurable outcomes to our clients, shareholders, stakeholders, clients, and customers. Um, and our green plot advisers sustainability solutions already been implemented at three clients. And in many cases in two cases has helped them reduce the carbon footprint by up to 400% through migration from their existing data center to green cloud. Very, very, >>That is remarkable. Now tell us a little bit about the kinds of clients. Is this, is this more interesting to clients in Europe? Would you say that it's catching on in the United States? Where, what is the breakdown that you're seeing right now? >>Sustainability is becoming such a global agenda and we're seeing our clients, um, uh, tie this and put this at board level, um, uh, agenda and requirements across the globe. Um, Europe has specific constraints around data sovereignty, right, where they need their data in country, but from a green, a sustainability agenda, we see clients across all our markets, North America, Europe, and our growth markets adopt this. And we have seen case studies and all three months. >>Keisha, I want to bring you back into the conversation. Talk a little bit about how MindUP ties into Accenture's cloud first strategy, your Accenture's CEO, Julie Sweet has talked about post COVID leadership requiring every business to become a cloud first business. Tell us a little bit about how this ethos is in Accenture and how you're sort of looking outward with it too. >>So Rebecca mine is the launch pad, uh, to a cloud first transformation for our clients. Uh, Accenture, see your jewelry suite, uh, you know, shared the Accenture cloud first and our substantial investment demonstrate our commitment and is delivering greater value for our clients when they need it the most. And with the digital transformation requiring cloud at scale, you know, we're seeing that in the post COVID leadership, it requires that every business should become a cloud business. And my nap helps them get there by evaluating the cloud landscape, navigating the complexity, modeling architecting and simulating an optimal cloud solution for our clients. And as Justin was sharing a greener cloud. >>So Tristan, talk a little bit more about some of the real life use cases in terms of what are we, what are clients seeing? What are the results that they're having? >>Yes. Thank you, Rebecca. I would say two key things right around my neck. The first is the iterative process. Clients don't want to wait, um, until they get started, they want to get started and see what their journey is going to look like. And the second is fundamental acceleration, dependent make, as we talked about, has accelerated the need to move to cloud very quickly. And my nav is there to do that. So how do we do that? First is generating the business cases. Clients need to know in many cases that they have a business case by business case, we talk about the financial benefits, as well as the business outcomes, the green, green clot impact sustainability impacts with minus. We can build initial recommendations using a basic understanding of their environment and benchmarks in weeks versus months with indicative value savings in the millions of dollars arranges. >>So for example, very recently, we worked with a global oil and gas company, and in only two weeks, we're able to provide an indicative savings for $27 million over five years. This enabled the client to get started, knowing that there is a business case benefit and then iterate on it. And this iteration is, I would say the second point that is particularly important with my nav that we've seen in bank, the clients, which is, um, any journey starts with an understanding of what is the application landscape and what are we trying to do with those, these initial assessments that used to take six to eight weeks are now taking anywhere from two to four weeks. So we're seeing a 40 to 50% reduction in the initial assessment, which gets clients started in their journey. And then finally we've had discussions with all of the hyperscalers to help partner with Accenture and leverage mine after prepared their detailed business case module as they're going to clients. And as they're accelerating the client's journey, so real results, real acceleration. And is there a journey? Do I have a business case and furthermore accelerating the journey once we are by giving the ability to work in iterative approach. >>I mean, it sounds as though that the company that clients and and employees are sort of saying, this is an amazing time savings look at what I can do here in, in so much in a condensed amount of time, but in terms of getting everyone on board, one of the things we talked about last time we met, uh, Tristan was just how much, uh, how one of the obstacles is getting people to sign on and the new technologies and new platforms. Those are often the obstacles and struggles that companies face. Have you found that at all? Or what is sort of the feedback that you're getting from employers? >>Sorry. Yes. We clearly, there are always obstacles to a cloud journey. If there were an obstacles, all our clients would be, uh, already fully in the cloud. What man I gives the ability is to navigate through those, to start quickly. And then as we identify obstacles, we can simulate what things are going to look like. We can continue with certain parts of the journey while we deal with that obstacle. And it's a fundamental accelerator. Whereas in the past one, obstacle would prevent a class from starting. We can now start to address the obstacles one at a time while continuing and accelerating the contrary. That is the fundamental difference. >>Kishor I want to give you the final word here. Tell us a little bit about what is next for Accenture might have and what we'll be discussing next year at the Accenture executive summit >>Sort of echo, we are continuously evolving with our client needs and reinventing, reinventing for the future. For mine, as I've been taught advisor, our plan is to help our clients reduce carbon footprint and again, migrate to a green cloud. Uh, and additionally, we're looking at, you know, two capabilities, uh, which include sovereign cloud advisor, uh, with clients, especially in, in Europe and others are under pressure to meet, uh, stringent data norms that Kristen was talking about. And the sovereign cloud advisor health organization to create an architecture cloud architecture that complies with the green. Uh, I would say the data sovereignty norms that is out there. The other element is around data to cloud. We are seeing massive migration, uh, for, uh, for a lot of the data to cloud. And there's a lot of migration hurdles that come within that. Uh, we have expanded mine app to support assessment capabilities, uh, for, uh, assessing applications, infrastructure, but also covering the entire state, including data and the code level to determine the right cloud solution. So we are, we are pushing the boundaries on what mine app can do with mine. Have you created the ability to take the guesswork out of cloud navigate the complexity? We are roaring risks costs, and we are, you know, achieving client's static business objectives while building a sustainable alerts with being cloud >>Any platform that can take some of the guesswork out of the future. I'm I'm onboard with. Thank you so much, Tristin and Kishore. This has been a great conversation. >>Thank you. >>Stay tuned for more of the cubes coverage of the Accenture executive summit. I'm Rebecca Knight from around the globe. It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS. >>Hey, welcome back to the cubes coverage of 80 us reinvent 2020 virtual centric executive summit. The two great guests here to break down the analysis of the relationship with cloud and essential Brian bowhead director ahead of a century 80. It was business group at Amazon web services. And Andy T a B G the M is essentially Amazon business group lead managing director at Accenture. Uh, I'm sure you're super busy and dealing with all the action, Brian. Great to see you. Thanks for coming on. So thank you. You guys essentially has been in the spotlight this week and all through the conference around this whole digital transformation, essentially as business group is celebrating its fifth anniversary. What's new, obviously the emphasis of next gen post COVID generation, highly digital transformation, a lot happening. You got your five-year anniversary, what's new. >>Yeah, it, you know, so if you look back, it's exciting. Um, you know, so it was five years ago. Uh, it was actually October where we, where we launched the Accenture AWS business group. And if we think back five years, I think we're still at the point where a lot of customers were making that transition from, you know, should I move to cloud to how do I move to cloud? Right? And so that was one of the reasons why we launched the business group. And since, since then, certainly we've seen that transition, right? Our conversations today are very much around how do I move to cloud, help me move, help me figure out the business case and then pull together all the different pieces so I can move more quickly, uh, you know, with less risk and really achieve my business outcomes. And I would say, you know, one of the things too, that's, that's really changed over the five years. >>And what we're seeing now is when we started, right, we were focused on migration data and IOT as the big three pillars that we launched with. And those are still incredibly important to us, but just the breadth of capability and frankly, the, the, the breadth of need that we're seeing from customers. And obviously as AWS has matured over the years and launched our new capabilities, we're Eva with Accenture and in the business group, we've broadened our capabilities and deepened our capabilities over the, over the last five years as well. For instance, this year with, with COVID, especially, it's really forced our customers to think differently about their own customers or their citizens, and how do they service those citizens? So we've seen a huge acceleration around customer engagement, right? And we powered that with Accenture customer engagement platform powered by ADA, Amazon connect. And so that's been a really big trend this year. And then, you know, that broadens our capability from just a technical discussion to one where we're now really reaching out and, and, um, and helping transform and modernize that customer and citizen experience as well, which has been exciting to see. >>Yeah, Andy, I want to get your thoughts here. We've been reporting and covering essentially for years. It's not like it's new to you guys. I mean, five years is a great anniversary. You know, check is good relationship, but you guys have been doing the work you've been on the trend line. And then this hits and Andy said on his keynote and I thought he said it beautifully. And he even said it to me in my one-on-one interview with them was it's on full display right now, the whole digital transformation, everything about it is on full display and you're either were prepared for it or you kind of word, and you can see who's there. You guys have been prepared. This is not new. So give us the update from your perspective, how you're taking advantage of this, of this massive shift, highly accelerated digital transformation. >>Well, I think, I think you can be prepared, but you've also got to be prepared to always sort of, I think what we're seeing in, in, um, in, in, in, in recent times and particularly 20 w what is it I think today there are, um, full sense of the enterprise workloads, the cloud, um, you know, that leaves 96 percentile now for him. Um, and I, over the next four to >>Five years, um, we're going to see that sort of, uh, acceleration to the, to the cloud pick up, um, this year is, as Andy touched on, I think, uh, uh, on Tuesday in his, I think the pandemic is a forcing function, uh, for companies to, to really pause and think about everything from, from, you know, how they, um, manage that technology to infrastructure, to just to carotenoids where the data sets to what insights and intelligence that getting from that data. And then eventually even to, to the talent, the talent they have in the organization and how they can be competitive, um, their culture, their culture of innovation, of invention and reinvention. And so I think, I think, you know, when you, when you think of companies out there faced with these challenges, it, it forces us, it forces AWS, it forces AEG to come together and think through how can we help create value for them? How can we help help them move from sort of just causing and rethinking to having real plans in an action and that taking them, uh, into, into implementation. And so that's, that's what we're working on. Um, I think over the next five years, we're looking to just continue to come together and help these, these companies get to the cloud and get the value from the cloud because it's beyond just getting to the cloud attached to them and living in the cloud and, and getting the value from it. >>It's interesting. Andy was saying, don't just put your toe in the water. You got to go beyond the toe in the water kind of approach. Um, I want to get to that large scale cause that's the big pickup this week that I kind of walked away with was it's large scale. Acceleration's not just toe in the water experimentation. Can you guys share, what's causing this large scale end to end enterprise transformation? And what are some of the success criteria have you seen for the folks who have done that? >>Yeah. And I'll, I'll, I'll start. And at the end you can buy a lawn. So, you know, it's interesting if I look back a year ago at re-invent and when I did the cube interview, then we were talking about how the ABG, we were starting to see this shift of customers. You know, we've been working with customers for years on a single of what I'll call a single-threaded programs, right. We can do a migration, we could do SAP, we can do a data program. And then even last year, we were really starting to see customers ask. The question is like, what kind of synergies and what kind of economies of scale do I get when I start bringing these different threads together, and also realizing that it's, you know, to innovate for the business and build new applications, new capabilities. Well, that then is going to inform what data you need to, to hydrate those applications, right? Which then informs your data strategy while a lot of that data is then also embedded in your underlying applications that sit on premises. So you should be thinking through how do you get those applications into the cloud? So you need to draw that line through all of those layers. And that was already starting last year. And so last year we launched the joint transformation program with AEG. And then, so we were ready when this year happened and then it was just an acceleration. So things have been happening faster than we anticipated, >>But we knew this was going to be happening. And luckily we've been in a really good position to help some of our customers really think through all those different layers of kind of pyramid as we've been calling it along with the talent and change pieces, which are also so important as you make this transformation to cloud >>Andy, what's the success factors. Andy Jassy came on stage during the partner day, a surprise fireside chat with Doug Hume and talking about this is really an opportunity for partners to, to change the business landscape with enablement from Amazon. You guys are in a pole position to do that in the marketplace. What's the success factors that you see, >>Um, really from three, three fronts, I'd say, um, w one is the people. Um, and, and I, I, again, I think Andy touched on sort of eight, uh, success factors, uh, early in the week. And for me, it's these three areas that it sort of boils down to these three areas. Um, one is the, the, the, the people, uh, from the leaders that it's really important to set those big, bold visions point the way. And then, and then, you know, set top down goals. How are we going to measure Z almost do get what you measure, um, to be, you know, beyond the leaders, to, to the right people in the right position across the company. We we're finding a key success factor for these end to end transformations is not just the leaders, but you haven't poached across the company, working in a, in a collaborative, shared, shared success model, um, and people who are not afraid to, to invent and fail. >>And so that takes me to perhaps the second point, which is the culture, um, it's important, uh, with finding for the right conditions to be set in the company that enabled, uh, people to move at pace, move at speed, be able to fail fast, um, keep things very, very simple and just keep iterating and that sort of culture of iteration and improvement versus seeking perfection is, is super important for, for success. And then the third part of maybe touch on is, is partners. Um, I think, you know, as we move forward over the next five years, we're going to see an increasing number of players in the ecosystem in the enterprise and state. Um, you're going to see more and more SAS providers. And so it's important for companies and our joint clients out there to pick partners like, um, like AWS or, or Accenture or others, but to pick partners who have all worked together and you have built solutions together, and that allows them to get speed to value quicker. It allows them to bring in pre-assembled solutions, um, and really just drive that transformation in a quicker, it sorts of manner. >>Yeah, that's a great point worth calling out, having that partnership model that's additive and has synergy in the cloud, because one of the things that came out of this this week, this year is reinvented, is there's new things going on in the public cloud, even though hybrid is an operating model, outpost and super relevant. There, there are benefits for being in the cloud and you've got partners API, for instance, and have microservices working together. This is all new, but I got, I got to ask that on that thread, Andy, where did you see your customers going? Because I think, you know, as you work backwards from the customers, you guys do, what's their needs, how do you see them? W you know, where's the puck going? Where can they skate where the puck's going, because you can almost look forward and say, okay, I've got to build modern apps. I got to do the digital transformation. Everything is a service. I get that, but what are they, what solutions are you building for them right now to get there? >>Yeah. And, and of course, with, with, you know, industries blurring and multiple companies, it's always hard to boil down to the exact situations, but you could probably look at it from a sort of a thematic lens. And what we're seeing is as the cloud transformation journey picks up, um, from us perspective, we've seen a material shift in the solutions and problems that we're trying to address with clients that they are asking for us, uh, to, to help, uh, address is no longer just the back office, where you're sort of looking at cost and efficiency and, um, uh, driving gains from that perspective. It's beyond that, it's now materially the top line. It's, how'd you get the driving to the, you know, speed to insights, how'd you get them decomposing, uh, their application set in order to derive those insights. Um, how'd you get them, um, to, to, um, uh, sort of adopt leading edge industry solutions that give them that jump start, uh, and that accelerant to winning the customers, winning the eyeballs. >>Um, and then, and then how'd, you help drive the customer experience. We're seeing a lot of push from clients, um, or ask for help on how do I optimize my customer experience in order to retain my eyeballs. And then how do I make sure I've got a soft self-learning ecosystem of play, um, where, uh, you know, it's not just a practical experience that I can sort of keep learning and iterating, um, how I treat my, my customers, um, and a lot of that, um, that still self-learning, that comes from, you know, putting in intelligence into your, into your systems, getting an AI and ML in there. And so, as a result of that work, we're seeing a lot of push and a lot of what we're doing, uh, is pouring investment into those areas. And then finally, maybe beyond the bottom line, and the top line is how do you harden that and protect that with, um, security and resilience? So I'll probably say those are the three areas. John, >>You know, the business model side, obviously the enablement is what Amazon has. Um, we see things like SAS factory coming on board and the partner network, obviously a century is a big, huge partner of you guys. Um, the business models there, you've got I, as, as doing great with chips, you have this data modeling this data opportunity to enable these modern apps. We heard about the partner strategy for me and D um, talking to me now about how can partners within even Accenture, w w what's the business model, um, side on your side that you're enabling this. Can you just share your thoughts on that? >>Yeah, yeah. And so it's, it's interesting. I think I'm going to build it and then build a little bit on some of the things that Andy really talked about there, right? And that we, if you think of that from the partnership, we are absolutely helping our customers with kind of that it modernization piece. And we're investing a lot and there's hard work that needs to get done there. And we're investing a lot as a partnership around the tools, the assets and the methodology. So in AWS and Accenture show up together as AEG, we are executing office single blueprint with a single set of assets, so we can move fast. So we're going to continue to do that with all the hybrid announcements from this past week, those get baked into that, that migration modernization theme, but the other really important piece here as we go up the stack, Andy mentioned it, right? >>The data piece, like so much of what we're talking about here is around data and insights. Right? I did a cube interview last week with, uh, Carl hick. Um, who's the CIO from Takeda. And if you hear Christophe Weber from Takeda talk, he talks about Takeda being a data company, data and insights company. So how do we, as a partnership, again, build the capabilities and the platforms like with Accenture's applied insights platform so that we can bootstrap and really accelerate our client's journey. And then finally, on the innovation on the business front, and Andy was touching on some of these, we are investing in industry solutions and accelerators, right? Because we know that at the end of the day, a lot of these are very similar. We're talking about ingesting data, using machine learning to provide insights and then taking action. So for instance, the cognitive insurance platform that we're working together on with Accenture, if they give out property and casualty claims and think about how do we enable touchless claims using machine learning and computer vision that can assess based on an image damage, and then be able to triage that and process it accordingly, right? >>Using all the latest machine learning capabilities from AWS with that deep, um, AI machine learning data science capability from Accenture, who knows all those algorithms that need to get built and build that library by doing that, we can really help these insurance companies accelerate their transformation around how they think about claims and how they can speed those claims on behalf of their policy holder. So that's an example of a, kind of like a bottom to top, uh, view of what we're doing in the partnership to address these new needs. >>That's awesome. Andy, I want to get back to your point about culture. You mentioned it twice now. Um, talent is a big part of the game here. Andy Jassy referenced Lambda. The next generation developers were using Lambda. He talked about CIO stories around, they didn't move fast enough. They lost three years. A new person came in and made it go faster. This is a new, this is a time for a certain kind of, um, uh, professional and individual, um, to, to be part of, um, this next generation. What's the talent strategy you guys have to attract and attain the best and retain the people. How do you do it? >>Um, you know, it's, it's, um, it's an interesting one. It's, it's, it's oftentimes a, it's, it's a significant point and often overlooked. Um, you know, people, people really matter and getting the right people, um, in not just in AWS or it, but then in our customers is super important. We often find that much of our discussions with, with our clients is centered around that. And it's really a key ingredient. As you touched on, you need people who are willing to embrace change, but also people who are willing to create new, um, to invent new, to reinvent, um, and to, to keep it very simple. Um, w we're we're we're seeing increasingly that you need people that have a sort of deep learning and a deep, uh, or deep desire to keep learning and to be very curious as, as they go along. Most of all, though, I find that, um, having people who are not willing or not afraid to fail is critical, absolutely critical. Um, and I think that that's, that's, uh, a necessary ingredient that we're seeing, um, our clients needing more off, um, because if you can't start and, and, and you can't iterate, um, you know, for fear of failure, you're in trouble. And, and I think Andy touched on that you, you know, where that CIO, that you referred to last three years, um, and so you really do need people who are willing to start not afraid to start, uh, and, uh, and not afraid to lead >>Was a gut check there. I just say, you guys have a great team over there. Everyone at the center I've interviewed strong, talented, and not afraid to lean in and, and into the trends. Um, I got to ask on that front cloud first was something that was a big strategic focus for Accenture. How does that fit into your business group? That's an Amazon focused, obviously they're cloud, and now hybrid everywhere, as I say, um, how does that all work it out? >>We're super excited about our cloud first initiative, and I think it fits it, um, really, uh, perfectly it's it's, it's what we needed. It's, it's, it's a, it's another accelerant. Um, if you think of count first, what we're doing is we're, we're putting together, um, uh, you know, capability set that will help enable him to and transformations as Brian touched on, you know, help companies move from just, you know, migrating to, to, to modernizing, to driving insights, to bringing in change, um, and, and, and helping on that, on that talent side. So that's sort of component number one is how does Accenture bring the best, uh, end to end transformation capabilities to our clients? Number two is perhaps, you know, how do we, um, uh, bring together pre-assembled as Brian touched on pre-assembled industry offerings to help as an accelerant, uh, for our, for our customers three years, as we touched on earlier is, is that sort of partnership with the ecosystem. >>We're going to see an increasing number of SAS providers in an estate, in the enterprise of snakes out there. And so, you know, panto wild cloud first, and our ABG strategy is to increase our touch points in our integrations and our solutions and our offerings with the ecosystem partners out there, the ISP partners out, then the SAS providers out there. And then number four is really about, you know, how do we, um, extend the definition of the cloud? I think oftentimes people thought of the cloud just as sort of on-prem and prem. Um, but, but as Andy touched on earlier this week, you know, you've, you've got this concept of hybrid cloud and that in itself, um, uh, is, is, is, you know, being redefined as well. You know, when you've got the intelligent edge and you've got various forms of the edge. Um, so that's the fourth part of, of, uh, of occupied for strategy. And for us was super excited because all of that is highly relevant for ABG, as we look to build those capabilities as industry solutions and others, and as when to enable our customers, but also how we, you know, as we, as we look to extend how we go to market, I'll join tele PS, uh, in, uh, in our respective skews and products. >>Well, what's clear now is that people now realize that if you contain that complexity, the upside is massive. And that's great opportunity for you guys. We got to get to the final question for you guys to weigh in on, as we wrap up next five years, Brian, Andy weigh in, how do you see that playing out? What do you see this exciting, um, for the partnership and the cloud first cloud, everywhere cloud opportunities share some perspective. >>Yeah, I, I think, you know, just kinda building on that cloud first, right? What cloud first, and we were super excited when cloud first was announced and you know, what it signals to the market and what we're seeing in our customers, which has cloud really permeates everything that we're doing now. Um, and so all aspects of the business will get infused with cloud in some ways, you know, it, it touches on, on all pieces. And I think what we're going to see is just a continued acceleration and getting much more efficient about pulling together the disparate, what had been disparate pieces of these transformations, and then using automation using machine learning to go faster. Right? And so, as we started thinking about the stack, right, well, we're going to get, I know we are, as a partnership is we're already investing there and getting better and more efficient every day as the migration pieces and the moving the assets to the cloud are just going to continue to get more automated, more efficient. And those will become the economic engines that allow us to fund the differentiated, innovative activities up the stack. So I'm excited to see us kind of invest to make those, those, um, those bets accelerated for customers so that we can free up capital and resources to invest where it's going to drive the most outcome for their end customers. And I think that's going to be a big focus and that's going to have the industry, um, you know, focus. It's going to be making sure that we can >>Consume the latest and greatest of AWS as capabilities and, you know, in the areas of machine learning and analytics, but then Andy's also touched on it bringing in ecosystem partners, right? I mean, one of the most exciting wins we had this year, and this year of COVID is looking at the universe, looking at Massachusetts, the COVID track and trace solution that we put in place is a partnership between Accenture, AWS, and Salesforce, right? So again, bringing together three really leading partners who can deliver value for our customers. I think we're going to see a lot more of that as customers look to partnerships like this, to help them figure out how to bring together the best of the ecosystem to drive solutions. So I think we're going to see more of that as well. >>All right, Andy final word, your take >>Thinks of innovation is, is picking up, um, dismiss things are just going faster and faster. I'm just super excited and looking forward to the next five years as, as you know, the technology invention, um, comes out and continues to sort of set new standards from AWS. Um, and as we, as Accenture wringing, our industry capabilities, we marry the two. We, we go and help our customers super exciting time. >>Well, congratulations on the partnership. I want to say thank you to you guys, because I've reported a few times some stories around real successes around this COVID pandemic that you guys worked together on with Amazon that really changed people's lives. Uh, so congratulations on that too as well. I want to call that out. Thanks for coming >>Up. Thank you. Thanks for coming on. >>Okay. This is the cubes coverage, essentially. AWS partnership, part of a century executive summit at Atrius reinvent 2020 I'm John for your host. Thanks. >>You're watching from around the globe. It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS. >>Hello, and welcome back to the cubes coverage of AWS reinvent 2020. This is special programming for the century executive summit, where all the thought leaders going to extract the signal from the nose to share with you their perspective of this year's reinvent conference, as it respects the customers' digital transformation. Brian Bohan is the director and head of a center. ADA was business group at Amazon web services. Brian, great to see you. And Chris Wegman is the, uh, center, uh, Amazon business group technology lead at Accenture. Um, guys, this is about technology vision, this, this conversation, um, Chris, I want to start with you because you, Andy Jackson's keynote, you heard about the strategy of digital transformation, how you gotta lean into it. You gotta have the guts to go for it, and you got to decompose. He went everywhere. So what, what did you hear? What was striking about the keynote? Because he covered a lot of topics. Yeah. You know, it >>Was Epic, uh, as always for Mandy, a lot of topics, a lot to cover in the three hours. Uh, there was a couple of things that stood out for me, first of all, hybrid, uh, the concept, the new concept of hybrid and how Andy talked about it, you know, uh, bringing the compute and the power to all parts of the enterprise, uh, whether it be at the edge or are in the big public cloud, uh, whether it be in an outpost or wherever it might be right with containerization now, uh, you know, being able to do, uh, Amazon containerization in my data center and that that's, that's awesome. I think that's gonna make a big difference, all that being underneath the Amazon, uh, console and billing and things like that, which is great. Uh, I'll also say the, the chips, right. And I know compute is always something that, you know, we always kind of take for granted, but I think again, this year, uh, Amazon and Andy really focused on what they're doing with the chips and PR and compute, and the compute is still at the heart of everything in cloud. And that continued advancement is, is making an impact and will make a continue to make a big impact. >>Yeah, I would agree. I think one of the things that really, I mean, the container thing was, I think really kind of a nuanced point when you got Deepak sing on the opening day with Andy Jassy and he's, he runs a container group over there, you know, small little team he's on the front and front stage. That really is the key to the hybrid. And I think this showcases this new layer and taking advantage of the graviton two chips that, which I thought was huge. Brian, this is really a key part of the platform change, not change, but the continuation of AWS higher level servers building blocks that provide more capabilities, heavy lifting as they say, but the new services that are coming on top really speaks to hybrid and speaks to the edge. >>It does. Yeah. And it, it, you know, I think like Andy talks about, and we talk about, I, you know, we really want to provide choice to our customers, uh, first and foremost, and you can see that and they re uh, services. We have, we can see it in the, the hybrid options that Chris talked about, being able to run your containers through ECS or EKS anywhere I just get to the customer's choice. And one of the things that I'm excited about as you talk about going up the stack and on the edge are things will certainly outpost. Um, right. So now I'll post those launched last year, but then with the new form factors, uh, and then you look at services like Panorama, right? Being able to take computer vision and embed machine learning and computer vision, and do that as a managed capability at the edge, um, for customers. >>And so we see this across a number of industries. And so what we're really thinking about is customers no longer have to make trade-offs and have to think about those, those choices that they can really deploy, uh, natively in the cloud. And then they can take those capabilities, train those models, and then deploy them where they need to, whether that's on premises or at the edge, you know, whether it be in a factory or retail environment. When we start, I think we're really well positioned when, um, you know, hopefully next year we started seeing the travel industry rebound, um, and the, the need, you know, more than ever really to, uh, to kind of rethink about how we kind of monitor and make those environments safe. Having this kind of capability at the edge is really going to help our customers as, as we come out of this year and hopefully rebound next year. >>Yeah. Chris, I want to go back to you for a second. It's hard to hard to pick your favorite innovation from the keynote, because, you know, just reminded me that Brian just reminded me of some things I forgot happened. It was like a buffet of innovation. Some keynotes have one or two, it was like 20, you got the industrial piece that was huge. Computer vision machine learning. That's just a game changer. The connect thing came out of nowhere, in my opinion, I mean, it's a call center technology. This is boring as hell. What are you gonna do with that? It turns out it's a game changer. It's not about the calls with the contact and that's discern intermediating, um, in the stack as well. So again, a feature that looks old is actually new and relevant. What's your, what was your favorite, um, innovation? >>Uh, it it's, it's, it's hard to say. I will say my personal favorite was the, the maca last. I, I just, I think that is a phenomenal, um, uh, just addition, right? And the fact that AWS is, has worked with Apple to integrate the Nitra chip into, into, uh, you know, the iMac and offer that out. Um, you know, a lot of people are doing development, uh, on for ILS and that stuff. And that there's just gonna be a huge benefit, uh, for the development teams. But, you know, I will say, I'll come back to connect you. You mentioned it. Um, you know, but you're right. It was a, it's a boring area, but it's an area that we've seen huge success with since, since connect was launched and the additional features and the Amazon continues to bring, you know, um, obviously with, with the pandemic and now that, you know, customer engagement through the phone, uh, through omni-channel has just been critical for companies, right. >>And to be able to have those agents at home, working from home versus being in the office, it was a huge, huge advantage for, for several customers that are using connect. You know, we, we did some great stuff with some different customers, but the continue technology, like you said, the, you know, the call translation and during a call to be able to pop up those key words and have a, have a supervisor, listen is awesome. And a lot of that was some of that was already being done, but we were stitching multiple services together. Now that's right out of the box. Um, and that Google's location is only going to make that go faster and make us to be able to innovate faster for that piece of the business. >>It's interesting, you know, not to get all nerdy and, and business school life, but you've got systems of records, systems of engagement. If you look at the call center and the connect thing, what got my attention was not only the model of disintermediating, that part of the engagement in the stack, but what actually cloud does to something that's a feature or something that could be an element, like say, call center, you old days of, you know, calling an 800 number, getting some support you got in chip, you have machine learning, you actually have stuff in the, in the stack that actually makes that different now. So you w you know, the thing that impressed me was Andy was saying, you could have machine learning, detect pauses, voice inflections. So now you have technology making that more relevant and better and different. So a lot going on, this is just one example of many things that are happening from a disruption innovation standpoint. W what do you guys, what do you guys think about that? And is that like getting it right? Can you share it? >>I think, I think, I think you are right. And I think what's implied there and what you're saying, and even in the, you know, the macro S example is the ability if we're talking about features, right. Which by themselves, you're saying, Oh, wow, what's, what's so unique about that, but because it's on AWS and now, because whether you're a developer working on, you know, w with Mac iOS and you have access to the 175 plus services, that you can then weave into your new applications, talk about the connect scenario. Now we're embedding that kind of inference and machine learning to do what you say, but then your data Lake is also most likely running in AWS, right? And then the other channels, whether they be mobile channels or web channels, or in store physical channels, that data can be captured in that same machine learning could be applied there to get that full picture across the spectrum. Right? So that's the, that's the power of bringing together on AWS to access to all those different capabilities of services, and then also the where the data is, and pulling all that together, that for that end to end view, okay, >>You guys give some examples of work you've done together. I know this stuff we've reported on. Um, in the last session we talked about some of the connect stuff, but that kind of encapsulates where this, where this is all going with respect to the tech. >>Yeah. I think one of the, you know, it was called out on Doug's partner summit was, you know, is there a, uh, an SAP data Lake accelerator, right? Almost every enterprise has SAP, right. And SAP getting data out of SAP has always been a challenge, right. Um, whether it be through, you know, data warehouses and AWS, sorry, SAP BW, you know, what we've focused on is, is getting that data when you're on have SAP on AWS getting that data into the data Lake, right. And getting it into, into a model that you can pull the value out of the customers can pull the value out, use those AI models. Um, so that was one thing we worked on in the last 12 months, super excited about seeing great success with customers. Um, you know, a lot of customers had ideas. They want to do this. They had different models. What we've done is, is made it very, uh, simplified, uh, framework that allows customers to do it very quickly, get the data out there and start getting value out of it and iterating on that data. Um, we saw customers are spending way too much time trying to stitch it all together and trying to get it to work technically. Uh, and we've now cut all that out and they can immediately start getting down to, to the data and taking advantage of those, those different, um, services are out there by AWS. >>Brian, you want to weigh in as things you see as relevant, um, builds that you guys done together that kind of tease out the future and connect the dots to what's coming. >>Uh, I, you know, I'm going to use a customer example. Uh, we worked with, um, and it just came out with, with Unilever around their blue air connected, smart air purifier. And what I think is interesting about that, I think it touches on some of the themes we're talking about, as well as some of the themes we talked about in the last session, which is we started that program before the pandemic. Um, and, but, you know, Unilever recognized that they needed to differentiate their product in the marketplace, move to more of a services oriented business, which we're seeing as a trend. We, uh, we enabled this capability. So now it's a smart air purifier that can be remote manage. And now in the pandemic head, they are in a really good position, obviously with a very relevant product and capability, um, to be used. And so that data then, as we were talking about is going to reside on the cloud. And so the learning that can now happen about usage and about, you know, filter changes, et cetera, can find its way back into future iterations of that valve, that product. And I think that's, that's keeping with, you know, uh, Chris was talking about where we might be systems of record, like in SAP, how do we bring those in and then start learning from that data so that we can get better on our future iterations? >>Hey, Chris, on the last segment we did on the business mission, um, session, Andy Taylor from your team, uh, talked about partnerships within a century and working with other folks. I want to take that now on the technical side, because one of the things that we heard from, um, Doug's, um, keynote and that during the partner day was integrations and data were two big themes. When you're in the cloud, technically the integrations are different. You're going to get unique things in the public cloud that you're just not going to get on premise access to other cloud native technologies and companies. How has that, how do you see the partnering of Accenture with people within your ecosystem and how the data and the integration play together? What's your vision? >>Yeah, I think there's two parts of it. You know, one there's from a commercial standpoint, right? So marketplace, you know, you, you heard Dave talk about that in the, in the partner summit, right? That marketplace is now bringing together this ecosystem, uh, in a very easy way to consume by the customers, uh, and by the users and bringing multiple partners together. And we're working with our ecosystem to put more products out in the marketplace that are integrated together, uh, already. Um, you know, I think one from a technical perspective though, you know, if you look at Salesforce, you know, we talked a little earlier about connect another good example, technically underneath the covers, how we've integrated connect and Salesforce, some of it being prebuilt by AWS and Salesforce, other things that we've added on top of it, um, I think are good examples. And I think as these ecosystems, these IFCs put their products out there and start exposing more and more API APIs, uh, on the Amazon platform, make opening it up, having those, those prebuilt network connections there between, you know, the different VPCs and the different areas within, within a customer's network. >>Um, and having them, having that all opened up and connected and having all that networking done underneath the covers. You know, it's one thing to call the API APIs. It's one thing to have access to those. And that's been a big focus of a lot of, you know, ISBNs and customers to build those API APIs and expose them, but having that network infrastructure and being able to stay within the cloud within AWS to make those connections, the past that data, we always talk about scale, right? It's one thing if I just need to pass like a, you know, a simple user ID back and forth, right? That's, that's fine. We're not talking massive data sets, whether it be seismic data or whatever it be passing those of those large, those large data sets between customers across the Amazon network is going to, is going to open up the world. >>Yeah. I see huge possibilities there and love to keep on this story. I think it's going to be important and something to keep track of. I'm sure you guys will be on top of it. You know, one of the things I want to, um, dig into with you guys now is Andy had kind of this philosophy philosophical thing in his keynote, talk about societal change and how tough the pandemic is. Everything's on full display. Um, and this kind of brings out kind of like where we are and the truth. You look at the truth, it's a virtual event. I mean, it's a website and you got some sessions out there with doing remote best weekend. Um, and you've got software and you've got technology and, you know, the concept of a mechanism it's software, it does something, it does a purpose. Essentially. You guys have a concept called living systems where growth strategy powered by technology. How do you take the concept of a, of a living organism or a system and replace the mechanism, staleness of computing and software. And this is kind of an interesting, because we're on the cusp of a, of a major inflection point post COVID. I get the digital transformation being slow that's yes, that's happening. There's other things going on in society. What do you guys think about this living systems concept? >>Yeah, so I, you know, I'll start, but, you know, I think the living system concept, um, you know, it started out very much thinking about how do you rapidly change the system, right? And, and because of cloud, because of, of dev ops, because of, you know, all these software technologies and processes that we've created, you know, that's where it started it, making it much easier to make it a much faster being able to change rapidly, but you're right. I think as you now bring in more technologies, the AI technology self-healing technologies, again, you're hurting Indian in his keynote, talk about, you know, the, the systems and services they're building to the tech problems and, and, and, and give, uh, resolve those problems. Right. Obviously automation is a big part of that living systems, you know, being able to bring that all together and to be able to react in real time to either what a customer, you know, asks, um, you know, either through the AI models that have been generated and turning those AI models around much faster, um, and being able to get all the information that came came in in the last 20 minutes, right. >>You know, society's moving fast and changing fast. And, you know, even in one part of the world, if, um, something, you know, in 10 minutes can change and being able to have systems to react to that, learn from that and be able to pass that on to the next country, especially in this world with COVID and, you know, things changing very quickly with quickly and, and, and, um, diagnosis and, and, um, medical response, all that so quickly to be able to react to that and have systems pass that information learned from that information is going to be critical. >>That's awesome. Brian, one of the things that comes up every year is, Oh, the cloud scalable this year. I think, you know, we've, we've talked on the cube before, uh, years ago, certainly with the censure and Amazon, I think it was like three or four years ago. Yeah. The clouds horizontally scalable, but vertically specialized at the application layer. But if you look at the data Lake stuff that you guys have been doing, where you have machine learning, the data's horizontally scalable, and then you got the specialization in the app changes that changes the whole vertical thing. Like you don't need to have a whole vertical solution or do you, so how has this year's um, cloud news impacted vertical industries because it used to be, Oh, the oil and gas financial services. They've got a team for that. We've got a stack for that. Not anymore. Is it going away? What's changing. Wow. >>I, you know, I think it's a really good question. And I don't think, I think what we're saying, and I was just on a call this morning talking about banking and capital markets. And I do think the, you know, the, the challenges are still pretty sector specific. Um, but what we do see is the, the kind of commonality, when we start looking at the, and we talked about it as the industry solutions that we're building as a partnership, most of them follow the pattern of ingesting data, analyzing that data, and then being able to, uh, provide insights and an actions. Right. So if you think about creating that yeah. That kind of common chassis of that ingest the data Lake and then the machine learning, can you talk about, you know, the announces around SageMaker and being able to manage these models, what changes then really are the very specific industries algorithms that you're, you're, you're writing right within that framework. And so we're doing a lot in connect is a good example of this too, where you look at it. Yeah. Customer service is a horizontal capability that we're building out, but then when you stop it into insurance or retail banking or utilities, there are nuances then that we then extend and build so that we meet the unique needs of those, those industries. And that's usually around those, those models. >>Yeah. And I think this year was the first reinvented. I saw real products coming out that actually solve that problem. And that was their last year SageMaker was kinda moving up the stack, but now you have apps embedding machine learning directly in, and users don't even know it's in there. I mean, Christmas is kind of where it's going. Right. I mean, >>Yeah. Announcements. Right. How many, how many announcements where machine learning is just embedded in? I mean, so, you know, code guru, uh, dev ops guru Panorama, we talked about, it's just, it's just there. >>Yeah. I mean, having that knowledge about the linguistics and the metadata, knowing the, the business logic, those are important specific use cases for the vertical and you can get to it faster. Right. Chris, how is this changing on the tech side, your perspective? Yeah. >>You know, I keep coming back to, you know, AWS and cloud makes it easier, right? None of this stuff, you know, all of this stuff can be done, uh, and has some of it has been, but you know, what Amazon continues to do is make it easier to consume by the developer, by the, by the customer and to actually embedded into applications much easier than it would be if I had to go set up the stack and build it all on that and, and, and, uh, embed it. Right. So it's, shortcutting that process. And again, as these products continue to mature, right. And some of the stuff is embedded, um, it makes that process so much faster. Uh, it makes it reduces the amount of work required by the developers, uh, the engineers to get there. So I I'm expecting, you're going to see more of this. >>Right. I think you're going to see more and more of these multi connected services by AWS that has a lot of the AIML, um, pre-configured data lakes, all that kind of stuff embedded in those services. So you don't have to do it yourself and continue to go up the stack. And we was talking about, Amazon's built for builders, right. But, you know, builders, you know, um, have been super specialized in, or we're becoming, you know, as engineers, we're being asked to be bigger and bigger and to be, you know, uh, be able to do more stuff. And I think, you know, these kinds of integrated services are gonna help us do that >>And certainly needed more. Now, when you have hybrid edge that are going to be operating with microservices on a cloud model, and with all those advantages that are going to come around the corner for being in the cloud, I mean, there's going to be, I think there's going to be a whole clarity around benefits in the cloud with all these capabilities and benefits cloud guru. Thanks my favorite this year, because it just points to why that could happen. I mean, that happens because of the cloud data. If you're on premise, you may not have a little cloud guru, you got to got to get more data. So, but they're all different edge certainly will come into your vision on the edge. Chris, how do you see that evolving for customers? Because that could be complex new stuff. How is it going to get easier? >>Yeah. It's super complex now, right? I mean, you gotta design for, you know, all the different, uh, edge 5g, uh, protocols are out there and, and, and solutions. Right. You know, Amazon's simplifying that again, to come back to simplification. Right. I can, I can build an app that, that works on any 5g network that's been integrated with AWS. Right. I don't have to set up all the different layers to get back to my cloud or back to my, my bigger data side. And I was kind of choking. I don't even know where to call the cloud anymore, big cloud, which is a central and I go down and then I've got a cloud at the edge. Right. So what do I call that? >>Exactly. So, you know, again, I think it is this next generation of technology with the edge comes, right. And we put more and more data at the edge. We're asking for more and more compute at the edge, right? Whether it be industrial or, you know, for personal use or consumer use, um, you know, that processing is gonna get more and more intense, uh, to be able to manage and under a single console, under a single platform and be able to move the code that I develop across that entire platform, whether I have to go all the way down to the, you know, to the very edge, uh, at the, at the 5g level, right? Or all the way into the bigger cloud and how that process, isn't there be able to do that. Seamlessly is going to be allow the speed of development that's needed. >>Well, you guys done a great job and no better time to be a techie or interested in technology or computer science or social science for that matter. This is a really perfect storm, a lot of problems to solve a lot of things, a lot of change happening, positive change opportunities, a lot of great stuff. Uh, final question guys, five years working together now on this partnership with AWS and Accenture, um, congratulations, you guys are in pole position for the next wave coming. Um, what's exciting. You guys, Chris, what's on your mind, Brian. What's, what's getting you guys pumped up >>Again. I come back to G you know, Andy mentioned it in his keynote, right? We're seeing customers move now, right. We're seeing, you know, five years ago we knew customers were going to get a new, this. We built a partnership to enable these enterprise customers to make that, that journey. Right. But now, you know, even more, we're seeing them move at such great speed. Right. Which is super excites me. Right. Because I can see, you know, being in this for a long time, now I can see the value on the other end. And I really, we've been wanting to push our customers as fast as they can through the journey. And now they're moving out of, they're getting, they're getting the religion, they're getting there. They see, they need to do it to change your business. So that's what excites me is just the excites me. >>It's just the speed at which we're, we're in a single movement. Yeah, yeah. I'd agree with, yeah, I'd agree with that. I mean, so, you know, obviously getting, getting customers to the cloud is super important work, and we're obviously doing that and helping accelerate that, it's it, it's what we've been talking about when we're there, all the possibilities that become available right. Through the common data capabilities, the access to the 175 some-odd AWS services. And I also think, and this is, this is kind of permeated through this week at re-invent is the opportunity, especially in those industries that do have an industrial aspect, a manufacturing aspect, or a really strong physical aspect of bringing together it and operational technology and the business with all these capabilities, then I think edge and pushing machine learning down to the edge and analytics at the edge is really going to help us do that. And so I'm super excited by all that possibility is I feel like we're just scratching the surface there, >>Great time to be building out. And you know, this is the time for re reconstruction. Re-invention big themes. So many storylines in the keynote, in the events. It's going to keep us busy here. It's looking at angle in the cube for the next year. Gentlemen, thank you for coming out. I really appreciate it. Thanks. Thank you. All right. Great conversation. You're getting technical. We could've go on another 30 minutes. Lot to talk about a lot of storylines here at AWS. Reinvent 2020 at the Centure executive summit. I'm John furrier. Thanks for watching.

>> Narrator: From around the globe it's theCUBE, with digital coverage of AWS re:Invent 2020. Special coverage sponsored by AWS Global Partner Network. >> Hello and welcome to theCUBE Virtual and our coverage of AWS re:Invent 2020 with special coverage of APN partner experience. We are theCUBE Virtual and I'm your host, Justin Warren. And today I'm joined by Ed Walsh, CEO of ChaosSearch. Ed, welcome to theCUBE. >> Well thank you for having me, I really appreciate it. >> Now, this is not your first time here on theCUBE. You're a regular here and I've loved it to have you back. >> I love the platform you guys are great. >> So let's start off by just reminding people about what ChaosSearch is and what do you do there? >> Sure, the best way to say is so ChaosSearch helps our clients know better. We don't do that by a special wizard or a widget that you give to your, you know, SecOp teams. What we do is a hard work to give you a data platform to get insights at scale. And we do that also by achieving the promise of data lakes. So what we have is a Chaos data platform, connects and indexes data in a customer's S3 or glacier accounts. So inside your data lake, not our data lake but renders that data fully searchable and available for analysis using your existing tools today 'cause what we do is index it and publish open API, it's like API like Elasticsearch API, and soon SQL. So give you an example. So based upon those capabilities were an ideal replacement for a commonly deployed, either Elasticsearch or ELK Stack deployments, if you're hitting scale issues. So we talk about scalable log analytics, and more and more people are hitting these scale issues. So let's say if you're using Elasticsearch ELK or Amazon Elasticsearch, and you're hitting scale issues, what I mean by that is like, you can't keep enough retention. You want longer retention, or it's getting very expensive to keep that retention, or because the scale you hit where you have availability, where the cluster is hard to keep up running or is crashing. That's what we mean by the issues at scale. And what we do is simply we allow you, because we're publishing the open API of Elasticsearch use all your tools, but we save you about 80% off your monthly bill. We also give you an, and it's an and statement and give you unlimited retention. And as much as you want to keep on S3 or into Glacier but we also take care of all the hassles and management and the time to manage these clusters, which ends up being on a database server called leucine. And we take care of that as a managed service. And probably the biggest thing is all of this without changing anything your end users are using. So we include Kibana, but imagine it's an Elastic API. So if you're using API or Kibana, it's just easy to use the exact same tools used today, but you get the benefits of a true data lake. In fact, we're running now Elasticsearch on top of S3 natively. If that makes it sense. >> Right and natively is pretty cool. And look, 80% savings, is a dramatic number, particularly this year. I think there's a lot of people who are looking to save a few quid. So it'd be very nice to be able to save up to 80%. I am curious as to how you're able to achieve that kind of saving though. >> Yeah, you won't be the first person to ask me that. So listen, Elastic came around, it was, you know we had Splunk and we also have a lot of Splunk clients, but Elastic was a more cost effective solution open source to go after it. But what happens is, especially at scale, if it's fall it's actually very cost-effective. But underneath last six tech ELK Stack is a leucine database, it's a database technology. And that sits on our servers that are heavy memory count CPU count in and SSDs. So you can do on-prem or even in the clouds, so if you do an Amazon, basically you're spinning up a server and it stays up, it doesn't spin up, spin down. So those clusters are not one server, it's a cluster of those servers. And typically if you have any scale you're actually having multiple clusters because you don't dare put it on one, for different use cases. So our savings are actually you no longer need those servers to spin up and you don't need to pay for those seen underneath. You can still use Kibana under API but literally it's $80 off your bill that you're paying for your service now, and it's hard dollars. So it's not... And we typically see clients between 70 and 80%. It's up to 80, but it's literally right within a 10% margin that you're saving a lot of money, but more importantly, saving money is a great thing. But now you have one unified data lake that you can have. You used to go across some of the data or all the data through the role-based access. You can give different people. Like we've seen people who say, hey give that, help that person 40 days of this data. But the SecOp up team gets to see across all the different law. You know, all the machine generated data they have. And we can give you a couple of examples of that and walk you through how people deploy if you want. >> I'm always keen to hear specific examples of how customers are doing things. And it's nice that you've thought of drawn that comparison there around what what cloud is good for and what it isn't is. I'll often like to say that AWS is cheap to fail in, but expensive to succeed. So when people are actually succeeding with this and using this, this broad amount of data so what you're saying there with that savings I've actually got access to a lot more data that I can do things with. So yeah, if you could walk through a couple of examples of what people are doing with this increased amount of data that they have access to in EKL Search, what are some of the things that people are now able to unlock with that data? >> Well, literally it's always good for a customer size so we can go through and we go through it however it might want, Kleiner, Blackboard, Alert Logic, Armor Security, HubSpot. Maybe I'll start with HubSpot. One of our good clients, they were doing some Cloud Flare data that was one of their clusters they were using a lot to search for. But they were looking at to look at a denial service. And they were, we find everyone kind of at scale, they get limited. So they were down to five days retention. Why? Well, it's not that they meant to but basically they couldn't cost-effectively handle that in the scale. And also they're having scale issues with the environment, how they set the cluster and sharding. And when they also denial service tech, what happened that's when the influx of data that is one thing about scale is how fast it comes out, yet another one is how much data you have. But this is as the data was coming after them at denial service, that's when the cluster would actually go down believe it or not, you know right. When you need your log analysis tools. So what we did is because they're just using Kibana, it was easy swap. They ran in parallel because we published the open API but we took them from five days to nine days. They could keep as much as they want but nine days for denial services is what they wanted. And then we did save them in over $4 million a year in hard dollars, What they're paying in their environment from really is the savings on the server farm and a little bit on the Elasticsearch Stack. But more importantly, they had no outages since. Now here's the thing. Are you talking about the use case? They also had other clusters and you find everyone does it. They don't dare put it on one cluster, even though these are not one server, they're multiple servers. So the next use case for CloudFlare was one, the next QS and it was a 10 terabyte a day influx kept it for 90 days. So it's about a petabyte. They brought another use case on which was NetMon, again, Network Monitoring. And again, I'm having the same scale issue, retention area. And what they're able to do is easily roll that on. So that's one data platform. Now they're adding the next one. They have about four different use cases and it's just different clusters able to bring together. But now what they're able to do give you use cases either they getting more cost effective, more stability and freedom. We say saves you a lot of time, cost and complexity. Just the time they manage that get the data in the complexities around it. And then the cost is easy to kind of quantify but they've got better but more importantly now for particular teams they only need their access to one data but the SecOP team wants to see across all the data. And it's very easy for them to see across all the data where before it was impossible to do. So now they have multiple large use cases streaming at them. And what I love about that particular case is at one point they were just trying to test our scale. So they started tossing more things at it, right. To see if they could kind of break us. So they spiked us up to 30 terabytes a day which is for Elastic would even 10 terabytes a day makes things fall over. Now, if you think of what they just did, what were doing is literally three steps, put your data in S3 and as fast as you can, don't modify, just put it there. Once it's there three steps connect to us, you give us readability access to those buckets and a place to write the indexy. All of that stuff is in your S3, it never comes out. And then basically you set up, do you want to do live or do you want to do real time analysis? Or do you want to go after old data? We do the rest, we ingest, we normalize the schema. And basically we give you our back and the refinery to give the right people access. So what they did is they basically throw a whole bunch of stuff at it. They were trying to outrun S3. So, you know, we're on shoulders of giants. You know, if you think about our platform for clients what's a better dental like than S3. You're not going to get a better cross curve, right? You're not going to get a better parallelism. And so, or security it's in your, you know a virtual environment. But if you... And also you can keep data in the right location. So Blackboard's a good example. They need to keep that in all the different regions and because it's personal data, they, you know, GDPR they got to keep data in that location. It's easy, we just put compute in each one of the different areas they are. But the net net is if you think that architecture is shoulders of giants if you think you can outrun by just sheer volume or you can put in more cost-effective place to keep long-term or you think you can out store you have so much data that S3 and glacier can't possibly do it. Then you got me at your bigger scale at me but that's the scale we'r&e talking about. So if you think about the spiked our throughput what they really did is they try to outrun S3. And we didn't pick up. Now, the next thing is they tossed a bunch of users at us which were just spinning up in our data fabric different ways to do the indexing, to keep up with it. And new use cases in case they're going after everyone gets their own worker nodes which are all expected to fail in place. So again, they did some of that but really they're like you guys handled all the influx. And if you think about it, it's the shoulders of giants being on top of an Amazon platform, which is amazing. You're not going to get a more cost effective data lake in the world, and it's continuing to fall in price. And it's a cost curve, like no other, but also all that resiliency, all that security and the parallelism you can get, out of an S3 Glacier is just a bar none is the most scalable environment, you can build an environment. And what we do is a thin layer. It's a data platform that allows you to have your data now fully searchable and queryable using your tools >> Right and you, you mentioned there that, I mean you're running in AWS, which has broad experience in doing these sorts of things at scale but on that operational management side of things. As you mentioned, you actually take that off, off the hands of customers so that you run it on their behalf. What are some of the areas that you see people making in trying to do this themselves, when you've gone into customers, and brought it into the EKL Search platform? >> Yeah, so either people are just trying their best to build out clusters of Elasticsearch or they're going to services like Logz.io, Sumo Logic or Amazon Elasticsearch services. And those are all basically on the same ELK Stack. So they have the exact same limits as the same bits. Then we see people trying to say, well I really want to go to a data lake. I want to get away from these database servers and which have their limits. I want to use a data Lake. And then we see a lot of people putting data into environments before they, instead of using Elasticsearch, they want to use SQL type tools. And what they do is they put it into a Parquet or Presto form. It's a Presto dialect, but it into Parquet and structure it. And they go a lot of other way to, Hey it's in the data lake, but they end up building these little islands inside their data lake. And it's a lot of time to transform the data, to get it in a format that you can go after our tools. And then what we do is we don't make you do that. Just literally put the data there. And then what we do is we do the index and a polish API. So right now it's Elasticsearch in a very short time we'll publish Presto or the SQL dialect. You can use the same tool. So we do see people, either brute forcing and trying their best with a bunch of physical servers. We do see another group that says, you know, I want to go use an Athena use cases, or I want to use a there's a whole bunch of different startups saying, I do data lake or data lake houses. But they are, what they really do is force you to put things in the structure before you get insight. True data lake economics is literally just put it there, and use your tools natively to go after it. And that's where we're unique compared to what we see from our competition. >> Hmm, so with people who have moved into ChaosSearch, what's, let's say pick one, if you can, the most interesting example of what people have started to do with, with their data. What's new? >> That's good. Well, I'll give you another one. And so Armor Security is a good one. So Armor Security is a security service company. You know, thousands of clients doing great I mean a beautiful platform, beautiful business. And they won Rackspace as a partner. So now imagine thousand clients, but now, you know massive scale that to keep up with. So that would be an example but another example where we were able to come in and they were facing a major upgrade of their environment just to keep up, and they expose actually to their customers is how their customers do logging analytics. What we're able to do is literally simply because they didn't go below the API they use the exact same tools that are on top and in 30 days replaced that use case, save them tremendous amount of dollars. But now they're able to go back and have unlimited retention. They used to restrict their clients to 14 days. Now they have an opportunity to do a bunch of different things, and possible revenue opportunities and other. But allow them to look at their business differently and free up their team to do other things. And now they're, they're putting billing and other things into the same environment with us because one is easy it's scale but also freed up their team. No one has enough team to do things. And then the biggest thing is what people do interesting with our product is actually in their own tools. So, you know, we talk about Kibana when we do SQL again we talk about Looker and Tableau and Power BI, you know, the really interesting thing, and we think we did the hard work on the data layer which you can say is, you know I can about all the ways you consolidate the performance. Now, what becomes really interesting is what they're doing at the visibility level, either Kibana or the API or Tableau or Looker. And the key thing for us is we just say, just use the tools you're used to. Now that might be a boring statement, but to me, a great value proposition is not changing what your end users have to use. And they're doing amazing things. They're doing the exact same things they did before. They're just doing it with more data at bigger scale. And also they're able to see across their different machine learning data compared to being limited going at one thing at a time. And that getting the correlation from a unified data lake is really what we, you know we get very excited about. What's most exciting to our clients is they don't have to tell the users they have to use a different tool, which, you know, we'll decide if that's really interesting in this conversation. But again, I always say we didn't build a new algorithm that you going to give the SecOp team or a new pipeline cool widget that going to help the machine learning team which is another API we'll publish. But basically what we do is a hard work of making the data platform scalable, but more importantly give you the APIs that you're used to. So it's the platform that you don't have to change what your end users are doing, which is a... So we're kind of invisible behind the scenes. >> Well, that's certainly a pretty strong proposition there and I'm sure that there's plenty of scope for customers to come and and talk to you because no one's creating any less data. So Ed, thanks for coming out of theCUBE. It's always great to see you here. >> Know, thank you. >> You've been watching theCUBE Virtual and our coverage of AWS re:Invent 2020 with special coverage of APN partner experience. Make sure you check out all our coverage online, either on your desktop, mobile on your phone, wherever you are. I've been your host, Justin Warren. And I look forward to seeing you again soon. (soft music)