(uplifting music) >> Hello and welcome to this special CUBE Conversation. I'm John Furrier, here in Palo Alto at theCUBE studios for a special conversation with Tarun Thaker, general manager of Datos IO, part of Rubrik. Last time I interviewed you, you were the CEO. You guys got acquired, congratulations. >> Thank you, thank you, John. Very happy to be here. >> How'd that go? How'd the acquisition go? >> Excellent, excellent. I Met Bipul about August of last year and it was sort of perfect marriage waiting to happen. We were both going after the broader irresistible opportunity of data management. >> I've enjoyed our previous conversations because you guys were a hot, growing start up and then you look at Rubrik, if you look at the success that they've been having, just the growth in data protection, the growth in cloud, you guys were on with from the beginning with Datos. Now you got a management team, you got all this growth, it is pretty fun to watch and I'll see you locally in Palo Alto so it's been interesting to see you guys. Huge growth opportunity. Cloud people are realizing that this is not a side decision. >> No. >> It's got to be done centrally. The customers are re architecting to be cloud native. The on premises, we saw big industry movements happening with Amazon at VMworld announcing RDS on VMware on premises. >> Correct. >> Which validates that the enterprises want to have a cloud operation, both on premise. >> Yes. >> And in cloud. How has this shaped you guys? You have big news, but this is a big trend. >> No, absolutely. John, I think you rightly said, the pace of innovation at Rubrik and the pace of market adoption is beyond everybody's imagination, right? When I said that it was sort of a marriage waiting to be happened, is if you look at the data management tam it's close to 50 billion dollars, right? And you need to build a portfolio of products, right? You need to sort of think about the classical data center applications because on prem is still there and on premises is still a big part of spending. But if you look at where enterprises are racing to the cloud. They're racing given digital transformation. They're racing customer 360 experience. Every organization, whether it be financials, maybe healthcare, maybe commerce, wants to get closer to the end customers, right? And if you look underneath that macro trend, it's all this cloud native space. Whether it be Kubernetes and Docker based containers or it could be RDS which is natively built in the cloud or it could be, hey I want to now run Oracle in the cloud, right? Once you start thinking of this re architecting stack being built in the cloud, enterprises will not leap and spend those top dollars that they spend on prem if they don't get a true, durable data management stack. >> And one of the things I really was impressed when you Datos, now it's part of Rubrik, is you were cloud up and down the stack. You were early on cloud, you guys thought like cloud native. Your operations was very agile. >> Thank you. >> Everything about you, beyond the product, was cloud. This is a critical success now for companies. They have to not just do cloud with product. >> Correct. >> Their operational impact has to be adjusted, how they do business, the supply chains, the value chains. These things are changing. >> The licensing, the pricing. >> This is the new model. >> Yes. >> This is where the data comes in. This is where the support comes in. You guys have some hard news, Datos IO 3.0. What's the big news? >> John, as you said, we've been very squarely focused on what we called the NoSQL big data market, right? We, if you look at, you know you talked about Amazon RDS, if you go to the Amazon business, Amazon database business is about four billon dollars today, right? Just think about that. If you take a guess on number one data base in Amazon native, it's not Oracle, it's MySQL. Number two, it's not SQL Server, it's Mongo DB. So if you look at the cloud native stack, we made this observation four years ago, as you said, that underneath this was all NoSQL. We really found that blue ocean, as we call it, the green field opportunity and go build the next Veritas for that space. You know, with 3.0, Bipul likes to call it in accordance to his leadership, consolidate your gains. Once you find an island full of gold coins, you don't leave that island. (laughing) You go double down, triple down, right? You don't want to distract your focus so 3.0 is all about us focusing. Really sort of the announcements are rooted around three vectors, as we call it. Number one, if you look at why Rubrik was so successful, you know you went into a pretty gorilla market of backup but why Rubrik has been successful at the heart is this ease of use and simplicity. And we wanted to bring that culture into, not only Datos team, but also into our product, right? So that was simplicity. Large scale distributive systems are difficult to deploy and manage so that was the first part. Second part was all about, you know, if you look at Mongo. Mongo has gone from zero to four billion dollars in less than 10 years. Every Fortune 2000, 500, Global 2000 customer is using Mongo in some critical way. >> Why is that? I mean people were always, personally we love Mongo DB, but people were predicting their demise every year. "Oh, it's never going to scale," I've heard people say and again, this is the competition. >> Correct. >> We know who they are. But why is the success there? Obviously NoSQL and unstructured data's big tsunami and there's more data coming in than ever before. Why are they successful? >> Excellent. That's why I enjoy being here, you go to the why not the what and the how. And the why is rooted for why Mongo DB's so successful, is application developers. We've all read this book, developers are the king makers of the IT, not your IT and storage admins? And Mongo found that niche, that if I can go build a database which is easier for an application developer, I will build a company. And that was the trend they built the company around. Fast forward, it's stock that is trading at $80 a piece. >> Yeah. >> To four billion plus in market. >> Yeah and I think the other thing I would just add, just riffing on that, is that cloud helps. Because where Mongo DB horizontally scales-- >> Elastic. >> The old critics were saying, thinking vertical scale. >> Correct. >> Cloud really helps that. >> Absolutely, absolutely. Cloud is our elastic resources, right? You turn it out and you turn it down. What we found in the first, as you know in the last two to three years journey of 1.0, 2.0, that we were having a great reception with Mongo DB deployments and again, consolidate your gains towards Mongo so that was the second vector, making Datos get scale out for Mongo DB deployments. Number three, which is really my most favorite was really around multi cloud is here, right? No enterprise is going to really, bet only on one form of Amazon or one form of Google Cloud, they're going to bet it across these multiple clouds, right? We were always on Amazon, Google. We now announced Datos natively available on Amazon, so now if you have enterprise customers doing NoSQL applications in Amazon, you can protect that data natively to the cloud, being the Azure cloud. >> So which clouds are you guys supporting now with 3.0? Can you just give the list? >> Yep, yep. We supported Amazon from very early days, AWS. Majority of customers are on Amazon. Number two is Google Cloud, we have a great relationship with Google Cloud team, very entrepreneurial people also. And number three's Azure. The fourth, which is sort of a hidden Trojan horse is Oracle Cloud. We also announced Datos on Oracle Cloud. Why, you may ask? Because if you look at, again, NoSQL and data stacks in Cassandra, we saw a very healthy ecosystem building for Cassandra and Oracle Cloud, for obvious reasons. It was very good for us to follow that tailwind. >> Interestingly I was just at Oracle yesterday for a briefing, and I'm not going to reveal any confidential information, because it's all on the record. They're heavily getting to cloud native. They have to. >> They have to. There's no choice. They cannot be like tiptoeing, they have to go all in. >> And microservices are a big thing. This is something that you guys now have focus on. Talk about the microservices. How does that fit in? Because you look at Kubernetes, Kubernetes is becoming that kind of TCPIP moment for the cloud world or TCPIP powered networked and created inter working. The inter cloud or the multi cloud relationship? >> Correct, all the cloud native. >> Kubernetes is becoming that core catalyst. Got containers on one side, service meshes on the other. This brings in the data equation, stateful applications, stateless applications, this is going to change the game for developers. >> Absolutely. >> Actually now you have a backup equation, how do you know what to back up? >> Correct. >> What's the data? >> Correct. >> What's the impact? >> Yeah. So the announcement that we announced, just to cover that quickly, is we were seeing that trend. If you look at these developers or these DBAs or data base admins who are going to the cloud and racing to the cloud? They're not deploying OVA files. They're not deploying, as you said, IP network files, right? They want to deploy these as containerized applications. So running Mongo as a Docker container or Cassandra as a Docker container or Couch as a Docker container and you cannot go to them as a data management product as an age old mechanism of various bits and bytes. So we announced two things, Datos is now available as a Docker container, so you can just get a Docker file and run your way. And number two is we can also protect your NoSQL applications that are Dockerized or that are containerized, right? And that's really our first step into what you're seeing with Amazon EKS, right? Elastic Kubernetes Service. If you saw NetApp announced yesterday the acquisition of Kubernetes as a service, right? And so our next step, now that we've enabled Docker container of Datos, is to how do we bring Kubernetes as a service on top of Docker because Docker to deploy, orchestrate, manage that by itself is really still a challenge. >> Yeah containers is the stepping stone to orchestration. >> Correct, correct. >> You need Kubernetes to orchestrate the containers. >> That is correct, that is correct. >> Alright so summarize the announcements. If you had to boil this down, what's the 3.0? >> So if I were to sort come back and give you sort of the headline message, it is really our release to go crack open into the Fortune 500, Global 2000 enterprises. So if you remember, 60% of our customers are already what we call it internally, R2K, global 2000 customers so Datos, 60% of our customers who are large Fortune 500 customers. >> They're running mission critical? >> They're mission critical, no support applications. >> So you're supporting mission critical applications? >> Absolutely, some of our biggest customers, ACL Worldwide, one of the largest financial leading organization. Home Depot, that we have talked about in the past, right? Palo Alto Networks, the worlds largest cloud security networking company, right? If you look at these organizations they are running cloud native applications today. And so this release is really our double down into cracking open the Global 2000 enterprises and really staying focused at that market. >> And multi cloud is critical for you guys? >> Oh, absolutely. Any enterprise software company without, especially a data company, right? At the end of the day, it's all about data. >> Tarun, talk about why multi cloud, at some point. I'd love to get your expert opinion on this because you know Kubernetes, you see what's coming around the corner with service meshes and all this cool stuff because it impacts the infrastructure. With multi cloud, certainly what everyone's asking about, hybrid and multi cloud. Why is multi cloud important? What's the impact of multi cloud? >> Great question, John. You know, I think it's rooted in sort of three key reasons, right? Number one, if you look at what enterprises did back in the day, right history repeats itself, right? They never betted only on IBM servers. They bought Dell servers, they bought HP servers. Never anybody betted only on ESX as the virtual hypervisor platform. They betted on KBM and others, right? Similarly if you look at these enterprises, the ones that we talked about, Palo Alto Networks, they're going to run some of the applications natively on Amazon but they want DR in Google Cloud so think about a business use case being across clouds. So that's the one, right? I want to run some applications in Amazon because of elasticity, ease of use, orchestration but I want to keep my DR in a different site but I don't want to a colo, right? I want to do another cloud, so that's one. Number two is some of your application developers are, you know, in different regions, right? You want to enable sort of different cloud sites for them, right? So it's just locality, would be more of a reason and number three which is actually, probably I think the most important, is if you look at Amazon and what they have done with the book business, what they've done with others, e-commerce organizations like eBay, like Home Depot, like Foot Locker, they're very wary of betting the farm on a retail organization. Fundamentally Amazon is a retail organization, right? So they will go back, their use cases on Google cloud, they'll go back their use cases on Azure cloud so it's like vertical. Which vertical is prone or more applicable to a particular cloud, if that make sense? >> And so having multi vendors been around for a while in the enterprise, so multi vendor just translates to multi cloud? >> There you go, yes, yes. >> How about what's goin' on with you guys? Next week is Microsoft Ignite, their big cloud show from Microsoft. You guys have a relationship with them. In November you announced a partnership. >> Correct. >> Rubrik and you guys are doing that, so what's going on with them? You're co-selling together? Are they joint developing? What's the update? >> Ignite, so Microsoft, I'll give an update on Microsoft and then Ignite. As you know, John Thompson is on our board and you know fundamentally the product that we have built, Azure team, working with them, we have come to realize that it's a great product to bring data to the cloud. >> Right. >> And we have a very good, strong product relationship with Microsoft, we have a co-sell meaning their reps can sell Rubrik and get quota retirement, that's massive, right? Think for both the companies, right? And companies don't make those decisions, John, lightly. Those decisions are made very strictly. >> Quota relief is great. >> It's huge. >> It's a sales force for you guys. >> Exactly, yep. For us, specifically on Ignite, with this release we announced Azure. We worked very closely with the Azure storage division. When we pitched them, hey we are now, Datos is available on Azure, the respect that we got was amazing. We had a Microsoft quote in our press release. At Ignite next week we have dedicated sessions talking about NoSQL back ups on Microsoft, natively being protected on Azure Cloud. It's good for them, good for us, huge announcement next week. >> That's good. You guys have done the work in the cloud and it's interesting, early cloud adopters get some dividends on that. Just to summarize the chat here, if you had to talk to customer who's watching or interested and sees all this competition out there, a lot of noise in the industry, how would you summarize your value proposition? What's the value that you're bringing to the table? How do you guys compete on that value? Why Datos? >> Perfect, thank you. It's, again, simple order in one to three. Number one, we're helping you accelerate journey to the cloud. Right, you want to go the cloud, we understand Fortune 500 enterprises want to race to the cloud. You don't want to race without protection, without data management. It's your data, it needs to be in your control so that's one. We're helping you race to the cloud, yet keeping your data in your hands. Number two, you are buying a truly cloud native software not a software that was built 20 years ago and shrink wrapped into cloud. This is a product built into technologies which are cloud native, right? Elasticity, you can scale up Datos, you can scale down Datos, just like Amazon resources so you're truly buying an elastic technologies rooted data management product. And number three, you know if you really look at cloud, cloud to you as a customer is all about, hey can I build, not lift and shift, cloud native. And you're adopting these new technologies, you don't want to not think about protection, management, DR, those critical business use cases. >> And thinking differently about cloud operations is critical. Great to see you Tarun. Thanks for coming on and sharing the news on Datos 3.0, appreciate it. I'm John Furrier, here in Palo Alto Studios with the general manager of Datos IO, now part of Rubrik, formerly the CEO of Datos, Tarun Thaker, thanks for watching. I'm John Furrier, thanks for watching theCUBE. (uplifting music)

>> Announcer: Live from Las Vegas, it's the CUBE. Covering AWS re:Invent 2017. Presented by: AWS, Intel, and our ecosystem of partners. >> Well, welcome back to the Sands Expo. Here we are in Las Vegas in re:Invent with just about 50 000 of our closest friends. Big AWS community gathering here all week long and it's a pleasure to be here with you on the CUBE, along with Keith Townsend. I'm John Walls and we're now joined by Peter Smails, who is the vice president of marketing and business developing at Datos IO. Peter, good to see ya. >> Thanks for having me and glad to be back. I love being on the CUBE. >> You were just last week, right? >> Keith: Yeah. >> CUBE conversations with John Fury or so we're going to have to start charging you rent. (laughs) >> I only have two numbers in my head right now: 18 billion, 40% CAGR. Those are the only two numbers I have in my head right now. For those of you not in the know, those are the numbers that AWS was talking about in terms of revenue and growth. Crazy times, crazy show, good stuff. >> This show really does embody that. It certainly illustrates that. We've only been here for... the doors have been open for about a half hour or so. Already wall-to-wall traffic. >> People were queuing up to get into the expo floor, which I don't think I've seen that. >> I swung by our booth, 2825. I swung by there at 11:20 and it was standing room only. It's great. I mean, the buzz, you can feel it. If you're not down on the floor, come down to the floor, cause you can just feel the energy. >> And even still, just walking up here, if you've been here to the Sands, you've got these giant hallways. I was here probably two hours ago and it was already wall-to-wall people and it was just packed. I was really impressed. >> The conference started in full tilt at seven o'clock this morning. People were just out and just engaging. >> So you guys, you're here, your relationship obviously at AWS, we're gonna get into that >> Yeah. You got the booth here, 2825? >> 2825. Yes sir. >> So let's talk about, first off, about your presence here. >> Peter: Yeah >> What brings you into this community? You've been here for a while now. >> Peter: Yeah. >> And maybe the evolution of that from the three or four years-- >> Sure. back to where you are now. Yeah, so our view of the world aligns incredibly well with AWS. The whole notion of the world's moving to the cloud. We've been in business since 2014. We are a cloud data management company with primary use cases around backup and recovery. There's all those things like data mobility and essentially our view of the world and our strategy is that as the world moves to the cloud, organizations are building net new applications. They're building modern applications that they're running on hybrid cloud environments. Those applications need a fundamentally new approach to data management. That's what we do. About 50% of our customers run natively on AWS. So this is a very logical show for us. We've got customers building these new modern applications. They're hosting them natively in AWS. They need backup and recovery. They need data mobility. That's what we do. It's just a perfect fit for us. >> So Peter, let's talk a little bit about data mobility. You guys are unapologetically cloud first. We've had this conversation in the past just offline. Talk to me about that conversation with customers. How that's evolved from three, four years ago to now. >> (chuckles) I'll use another quote from Andy, from earlier this week, or I guess this is from Jeff Basil, so theoretically it's the whole thing about they're willing to be misunderstood for a while. You go back four years, early days, yeah, we were doing cloud first, backup and recovery for modern applications built on the MongoDB's, the Cassandra's, the non relational databases. It's going to a non relational world. In the early days people would laugh and they'd be like, "Why you doing that?" We were steadfastly believing then, as we do now, that the world is moving to the cloud. The world is moving largely to a non relational world and so there's going to be a huge opportunity to provide data management solutions. Data aware, data management solutions for that. So we've stuck to that. We've been steadfast in that. But your point about maturity, what's been really exciting for us as an organization is that, I go back even a year, and you talk about, so what do you do? And you give 'em the pitch and there was a fair amount of nuance to it and they'd be like (garbles). They'd sort of give you the "hmm". They'd kind of ask questions or whatever and then once you talk through it, maybe it was a 10 minute elevator pitch, if you will. You had to go like 20 floors. They got it but it was a little bit more nuanced. Now it's, okay great, are you moving to the cloud? No brainer. Are you building modern applications? Are you importing your old applications, building these new modern applications in a non relational world. Absolutely. Are they running a production? Yes. How are you protecting those applications? We have no idea, kinda thing or we're using native tools or we're scripting or we're not doing anything. So it varied to your point. The conversation has become much less, it's not even nuanced anymore. The qualifying questions are incredibly simple and our value proposition is incredibly easy. If you're running applications, if you've built net new modern applications running in the cloud, or on-prem that you want to back up to the cloud, you need modern data protection. That's what we do. >> Let's talk about this hybrid IT scenario. I was at dinner last night with a couple Fortune 500 AWS customers and I was talking to them about the excitement of this whole category, data protection. They were like, backup? How is that sexy at at all? Then we got into this use case of data mobility, of I've built something really big on-prem and I need John Hastings term: "I need a multi-cloud strategy." >> Yeah, John's not a huge multi... He pressed me last week on the whole multi-cloud. >> Kevin: Fourier is-- Yeah, oh yeah, sorry (laughs) >> John: I don't want you to reach over and back slap me here. >> Peter: So you're all in on multi-cloud. It's Fourier we gotta worry about. >> John: My whole life. >> Talk to us about the importance of using what we would have traditionally called backup as a data mobility strategy. >> Cool. Absolutely. It all kinda comes down to for us, being data aware. If you think about it, we're a cloud data management company. Our number one use case is backup and recovery because the first thing you have to do is you gotta capture the data, you've gotta. >> Backup recovery of my VMs right? >> Good question. We are unlike traditional backup and recovery. We're not infrastructure-centric. We're application-centric. We're actually agnostic to the underlying infrastructure. So if you're running bare metal on-prem, if you're running on EC2, if you're leveraging S3, wherever you're running, we're fine because we integrated the application level, the database level. Hence our focus on non relational. Our number one use case is protecting that data. Because we are application aware, because we're data aware and we integrated the database level, we understand the underlying scheme. We are aware of the data structures within the databases that people are protecting first and foremost. But in the context of data mobility to your point, the number two use case for us is that organizations want to protect their data but then they want to do things like, I wanna spin up copies or sub-copies of my data, of my backup copies for test F, for QA, for performance testing, for cloud instantiation, for archiving, for BI, for whatever I want to do. The key is, we're not a migration company. AWS has migration services. If you need to move two petabytes of data from on-prem and you're now gonna host it in the cloud, that's not us, but if you built these new applications and you want to basically intelligently use subsets of your data for those workloads I was talking about, we enable you to be incredibly intelligent about only recovering if you will or only moving the data that you need. For example, simple things like, with our RecoverX 2.5 that we just announced. We do something called quierably recovery. What that means is, I can do everything from star dot Peter star or I can pick individual rows and columns. >> John: Just pick and choose? >> I can pick and choose based upon my database scheme. I can mast columns of data if I have to do GDPR compliance or PII. So from a used case standpoint, it's all about being aware of the data that you actually in the first place you're backing up, but then what data you wanna move so that you can be incredibly intelligent and efficient about the data that you're moving. >> So in traditional systems, I can encrypt data at rest. I can back it up. My tapes can be encrypted. My discs that's holding that back up data can be encrypted. When I think about that, when it comes to backing up object storing into the cloud, how do I do that with...? >> Great question. Again, because we're not infrastructure based, we're not LUN based, we're not block based, we integrate at the database level. We're completely transparent to encryption. We work perfectly fine with encrypted data. We work perfectly fine with compressed data. We invented something called semantic de-duplication. If you're familiar with traditional de-duplication. >> Keith: Right. >> It works in a block level. Fixture varying length block. In a clustered database environment or in a compressed or encrypted data environment, it kinda throws the capabilities of traditional de-dup out the window. Semantic de-duplication understands the scheme of the underlying database. We are highly efficient de-duplication for encrypted data, for compressed data. We're transparent to that, if you will. So again, back to our cloud first model, we built that in from day one. It's a fundament, our underlying architecture, the platform that we've built is fundamentally unlike anything else from a traditional backup and recovery or data management platform. >> So make sure I get it right before we say good-bye. Datos IO 2825? >> 2825, correct. www.DatosIO If you are running applications in the cloud and need to protect those apps, please talk to us. We'd love to help you out. If you're looking for data mobility solutions, come talk to us. >> John: There's the pitch. >> Love to chat. >> Peter, thanks for being with us. Next week you're off, all right? >> We'll have to cancel that one because I'm back next week. >> John: Back to back cupers, but maybe we'll give you a week off. >> Thanks for having me, always like being here. Appreciate it. >> Thanks for being with us. Back for more here at re:Invent. We're in Las Vegas live here on the CUBE. Back with more right after this.

(light orchestral music) >> Hello, everyone, and welcome to the Cube Conversation here at the Palo Alto studios for theCUBE. I'm John Furrier, the co-founder of SiliconANGLE Media. We're here for some news analysis with Peter Smails, the CMO of Datos.IO D-a-t-o-s dot I-O. Hot new start up with some news. Peter was just here for a thought leader segment with Chris Cummings talking about the industry breakdown. But the news is hot, prior to re:Invent which you will be at? >> Absolutely. >> RecoverX is the product. 2.5, it's a release. So, you've got a point release on your core product. >> Correct. >> Welcome to this conversation. >> Thanks for having me. Yeah, we're excited to share the news. Big day for us. >> All right, so let's get into the hard news. You guys are announcing a point release of the latest product which is your core flagship, RecoverX. >> Correct. >> Love the name. Love the branding of the X in there. It reminds me of the iPhone, so makes me wanna buy one. But you know ... >> We can make that happen, John. >> You guys are the X Factor. So, we've been pretty bullish on what you guys are doing. Obviously, like the positioning. It's cloud. You're taking advantage of the growth in the cloud. What is this new product release? Why? What's the big deal? What's in it for the customer? >> So, I'll start with the news, and then we'll take a small step back and sort of talk about why exactly we're doing what we're doing. So, RecoverX 2.5 is the latest in our flagship RecoverX line. It's a cloud data management platform. And the market that we're going after and the market we're disrupting is the traditional data management space. The proliferation of modern applications-- >> John: Which includes which companies? >> So, the Veritas' of the world, the Commvault's of the world, the Dell EMC's of the world. Anybody that was in the traditional-- >> 20-year-old architected data backup and recovery software. >> You stole my fun fact. (laughs) But very fair point which is that the average age approximately of the leading backup and recovery software products is approximately 20 years. So, a lot's changed in the last 20 years, not the least of which has been this proliferation of modern applications, okay? Which are geo-distributed microservices oriented and the rapid proliferation of multicloud. That disrupts that traditional notion of data management specifically backup and recovery. That's what we're going after with RecoverX. RecoverX 2.5 is the most recent version. News on three fronts. One is on our advanced recovery, and we can double-click into those. But it's essentially all about giving you more data awareness, more granularity to what data you wanna recover and where you wanna put it, which becomes very important in the multicloud world. Number two is what we call data center aware backup and recovery. That's all about supporting geo-distributed application environments, which again, is the new normal in the cloud. And then number three is around enterprise hardening, specifically around security. So, it's all about us increased flexibility and new capabilities for the multicloud environment and continue to enterprise-harden the product. >> Okay, so you guys say significant upgrade. >> Peter: Yep. >> I wanna just look at that. I'm also pretty critical, and you know how I feel on this so don't take it personal, multicloud is not a real deal yet. It's in statement of value that customers are saying-- It's coming! But cloud is here today, regular cloud. So, multicloud ... Well, what is multicloud actually mean? I mean, I can have multiple clouds but I'm not actually moving workloads across clouds, yet. >> I disagree. >> Okay. >> I actually disagree. We have multiple customers. >> All right, debunk that. >> I will debunk that. Number one use case for RecoverX is backup and recovery. But with a twist of the fact that it's for these modern applications running these geo-distributed environments. Which means it's not about backing up my data center, it's about, I need to make a copy of my data but I wanna back it up in the cloud. I'm running my application natively in the cloud, so I want a backup in the cloud. I'm running my application in the cloud but I actually wanna backup from the cloud back to my private cloud. So, that in lies a backup and recovery, and operation recovery use case that involves multicloud. That's number one. Number two use case for RecoverX is what we talk about on data mobility. >> So, you have a different definition of multicloud. >> Sorry, what was your-- Our definition of multicloud is fundamentally a customer using multiple clouds, whether it be a private on-prem GCP, AWS, Oracle, any mix and match. >> I buy that. I buy that. Where I was getting critical of was a workload. >> Okay. >> I have a workload and I'm running it on Amazon. It's been architected for Amazon. Then I also wanna run that same workload on Azure and Google. >> Okay. >> Or Oracle or somewhere else. >> Yep. >> I have to re-engineer it (laughs) to move, and I can't share the data. So, to me what multicloud means, I can run it anywhere. My app anywhere. Backup is a little bit different. You're saying the cloud environments can be multiple environments for your solution. >> That is correct. >> So, you're looking at it from the other perspective. >> Correct. The way we define ourselves is application-centric data management. And what that essentially means is we don't care what the underlying infrastructure is. So, if you look at traditional backup and recovery products they're LUN-based. So, I'm going to backup my storage LUN. Or they're VM-based. And a lot of big companies made a lot of money doing that. The problem is they are no LUN's and VM's in hybrid cloud or multicloud environment. The only thing that's consistent across application, across cloud-environments is the data and the applications that are running. Where we focus is we're 100% application-centric. So, we integrate at the database level. The database is the foundation of any application you create. We integrate there, which makes us agnostic to the underlying infrastructure. We run, just as examples, we have customers running next generation applications on-prem. We have customers running next generation applications on AWS in GCP. Any permutation of the above, and to your point about back to the multicloud we've got organizations doing backup with us but then we also have organizations using us to take copies of their backup data and put them on whatever clouds they want for things like test and refresh. Or performance testing or business analytics. Whatever you might wanna do. >> So, you're pretty flexible. I like that. So, we talked before on other segments, and certainly even this morning about modern stacks. >> Yeah. >> Modern applications. This is the big to-do item for all CXOs and CIOs. I need a modern infrastructure. I need modern applications. I need modern developers. I need modern everything. Hyper, micro, ultra. >> Whatever buzz word you use. >> But you guys in this announcement have a couple key things I wanna just get more explanation on. One, advanced recovery, backup anywhere, recover anywhere, and you said enterprise-grade security is the third thing. >> Yep. >> So, let's just break them down one at a time. Advanced recovery for Datos 2.5, RecoverX 2.5. >> Yep. >> What is advanced recovery? >> It's very specifically about providing high levels of granularity for recovering your data, on two fronts. So, the use case is, again, backup. I need to recover data. But I don't wanna necessarily recover everything. I wanna get smarter about the data I wanna recover. Or it could be for non-operational use cases, which is I wanna spin up a copy of data to run test dev or to do performance testing on. What advanced recovery specifically means is number one, we've introduced the notion of queryble recovery. And what that means is that I can say things like star dot John star. And the results returning from that, because we're application-centric, and we integrated the database, we give you visibility to that. I wanna see everything star dot John star. Or I wanna recover data from a very specific row, in a very specific column. Or I want to mask data that I do not wanna be recovered and I don't want people to see. The implications of that are think about that from a performance standpoint. Now, I only recover the data I need. So, I'm very, very high levels of granularity based upon a query. So, I'm fast from an RTO standpoint. The second part of it is for non-operational requirements I only move the data that is select to that data set. And number three is it helps you with things like GDPR compliance and PII compliance because you can mask data. So, that's query-based recovery. That's number one. The second piece of advanced recovery is what we call incremental recovery. That is granular recovery based upon a time stamp. So, you can get within individual points in time. So, you can get to a very high level of granularity based upon time. So, it's all about visibility. It's your data and getting very granular in a smart way to what you wanna recover. So, if I kind of hear what you're saying, what you're saying is essentially you built in the operational effectiveness of being effective operationally. You know, time to backup recovery, all that good RTO stuff. Restoring stuff operationally >> Peter: Very quickly. >> very fast. >> Peter: In a smart way. >> So, there's a speed game there which is table stakes. But you're real value here is all these compliance nightmares that are coming down the pike, GDPR and others. There's gonna be more. >> Peter: Absolutely. I mean, it could be HIPPA, it could be GDPR, anything that involves-- >> Policy. >> Policies. Anything that requires, we're completely policy-driven. And you can create a policy to mask certain data based upon the criteria you wanna put in. So, it's all about-- >> So you're the best of performance, and you got some tunability. >> And it's all about being data aware. It's all about being data aware. So, that's what advanced recovery is. >> Okay, backup anywhere, recover anywhere. What does that mean? >> So, what that means is the old world of backup and recovery was I had a database running in my data center. And I would say database please take a snapshot of yourself so I can make a copy. The new world of cloud is that these microservices-based modern applications typically run, they're by definition distributed, And in many cases they run distributed across they're geo-distributed. So, what data center aware backup and recovery is, use a perfect example. We have a customer. They're running their eCommerce. So, leading online restaurant reservations company. They're running their eCommerce application on-prem, interestingly enough, but it's based on Cassandra distributed database. Excuse me, MongoDB. Sorry. They're running geo-distributed, sharded MongoDB clusters. Anybody in the traditional backup and recovery their head would explode when you say that. In the modern application world, that's a completely normal use case. They have a data center in the U.S. They have a data center in the U.K. What they want is they wanna be able to do local backup and recovery while maintaining complete global consistency of their data. So again, it's about recovery time ultimately but it's also being data aware and focusing only on the data that you need to backup and recovery. So, it's about performance but then it's also about compliance. It's about governance. That's what data center aware backup is. >> And that's a global phenomenon people are having with the GO. >> Absolutely. Yeah, you could be within country. It could be any number of different things that drive that. We can do it because we're data aware-- >> And that creates complexity for the customer. You guys can take that complexity away >> Correct. >> From the whole global, regional where the data can sit. >> Correct. I'd say two things actually. To give the customers credit, the customers building these apps or actually getting a lot smarter about what they're data is and where they're data is. >> So they expect this feature? >> Oh, absolutely. Absolutely. I wouldn't call it table stakes cause we're the only kids on the block that can do it. But this is in direct response to our customers that are building these new apps. I wanna get into some of the environmental and customer drivers in a second. I wanna nail the last segment down. Cause I wanna unpack the whole why is this trend happening? What's the gestation period? What's the main enabler for you? But okay, final point on the significant announcements. My favorite topic enterprise-grade security. What the hell does that mean? First of all, from your standpoint the industry's trying to solve the same thing. Enterprise-grade security, what are you guys providing in this? >> Number one, it's basically security protocol. So, TLS and SSL. This is weed stuff. TLS, SSL, so secure protocol support. It's integration with LDAP. So, if organizations are running, primarily if they're running on-prem and they're running in an LDAP environment, we're support there. And then we've got Kerberos support for Kerberos authentication. So, it's all about just checking the boxes around the different security >> So, this is like in between >> and transport protocol. >> the toes, the details around compliance, identity management. >> Peter: Bingo. >> I mean we just had Centrify's CyberConnect conference, and you're seeing a lot of focus on identity. >> Absolutely. And the reason that that's sort of from a market standpoint the reason that these are very important now is because the applications that we're supporting these are not science experiments. These are eCommerce applications. These are core business applications that mainstream enterprises are running, and they need to be protected and they're bringing the true, classic enterprise security, authentication, authorization requirements to the table. >> Are you guys aligning with those features? Or is there anything significant in that section? >> From an enterprise security standpoint? It's primarily about we provide the support, so we integrate with all of those environments and we can check the boxes. Oh, absolutely TLS. Absolutely, we've got that box checked because-- >> So, you're not competing with other cybersecurity? >> No, this is purely we need to do this. This is part of our enterprise-- >> This is where you partner. >> Peter: Well, no. For these things it's literally just us providing the protocol support. So, LDAP's a good example. We support LDAP. So, we show up and if somebody's using my data management-- >> But you look at the other security solutions as a way to integrate with? >> Yeah. >> Not so much-- >> Absolutely, no. This has nothing to do with the competition. It's just supporting ... I mean Google has their own protocol, you know, security protocols, so we support those. So, does Amazon. >> I really don't want to go into the customer benefits. We'll let the folks go to the Datos website, d-a-t-o-s dot i-o is the website, if you wanna check out all their customer references. I don't wanna kind of drill on that. I kind of wanna really end this segment on the real core issue for me is reading the tea leaves. You guys are different. You're now kind of seeing some traction and some growth. You're a new kind of animal in the zoo, if you will. (Peter laughs) You've got a relevant product. Why is it happening now? And I'm trying to get to understanding Cloud Oss is enabling a lot of stuff. You guys are an effect of that, a data point of what the cloud is enabled as a venture. Everything that you're doing, the value you create is the function of the cloud. >> Yes. >> And how data is moving. Where's this coming from? Is it just recently? Is it a gestation period of a few years? Where did this come from? You mentioned some comparisons like Oracle. >> So, I'll answer that in sort of, we like to use history as our guide. So, I'll answer that both in macro terms, and then I'll answer it in micro terms. From a macro term standpoint, this is being driven by the proliferation of new data sources. It's the easiest way to look at it. So, if you let history be your guide. There was about a seven to eight year proliferation or gap between proliferation of Oracle as the primary traditional relational database data source and the advent of Veritas who really defined themselves as the defacto standard for traditional on-prem data center relational data management. You look at that same model, you'll look at the proliferation of VMware. In the late 90s, about a seven to eight year gestation with the rapid adoption of Veeam. You know the early days a lot of folks laughed at Veeam, like, "Who's gonna backup VMs? People aren't gonna use VMs in the enterprise. Now, you looked at Veeam, great company. They've done some really tremendous things carving out much more than a niche providing backup and recovery and availability in a VM-based environment. The exact same thing is happening now. If you go back six to seven years from now, you had the early adoption of the MongoDBs, the Cassandras, the Couches. More recently you've got a much faster acceleration around the DynamoDBs and the cloud databases. We're riding that same wave to support that. >> This is a side effect of the enabling of the growth of cloud. >> Yes. >> So, similar to what you did in VMware with VMs and database for Oracle you guys are taking it to the next level. >> These new data sources are completely driven by the fact that the cloud is enabling this completely distributed, far more agile, far more dynamic, far less expensive application deployment model, and a new way of providing data management is required. That's what we do. >> Yeah, I mean it's a function of maturity, one. As Jeff Rickard, General Manager of theCube, always says, when the industry moves to it's next point of failure, in this case failure is problem and you solve. So, the headaches that come from the awesomeness of the growth. >> Absolutely. And to answer that micro-wise briefly. So, that was the macro. The micro is the proliferation of, the movement from monolithic apps to microservices-based app, it's happening. And the cloud is what's enabling them. The move from traditional on-prem to hybrid cloud is absolutely happening. That's by definition the cloud. The third piece which is cloud-centric is the world's moving from a scale up world to an elastic-compute, elastic storage model. We call that the modern IT stack. Traditional backup and recovery, traditional data management doesn't work in the new modern IT stack. That's the market we're planning. That's the market we're disrupting is all that traditional stuff moving to the modern IT stack. >> Okay, Datos IO announcing a 2.5 release of RecoverX, their flagship product, their start up growing out of Los Gatos. Peter Smails here, the CMO. Where ya gonna be next? What's going on-- I know we're gonna see you re:Invent in a week in a half. >> Absolutely. So, we've got two stops. Well, actually the next stop on the tour is re:Invent. So, absolutely looking forward to being back on theCUBE at re:Invent. >> And the company feels good about those things are good. You've got good money in the bank. You're growing. >> We feel fantastic. It's fascinating to watch as things develop. The conversations we have now versus even six months ago. It's sort of the tipping point of people get it. You sort of explain, "Oh, yeah it's data management from modern applications. Are you deploying modern applications?" Absolutely. >> Share one example to end this segment on what you hear over and over again from customers that illuminates what you guys are about as a company, the DNA, the value preposition, and their impact on results and value for customers. >> So, I'll use a case study as an example. You know, we're the world's largest home improvement retailers. Old way, was they ran their multi-billion dollar eCommerce infrastructure. Running on IBM Db2 database. Running in their on-prem data center. They've moved their world. They're now running, they've re-architected their application. It's now completely microservices-based running on Cassandra, deployed 100% in Google cloud platform. And they did that because they wanted to be more agile. They wanted to be more flexible. It's a far more cost effective deployment model. They are all in on the cloud. And they needed a next generation backup and recovery data protection, data management solution which is exactly what we do. So, that's the value. Backup's not a new problem. People need to protect data and they need to be able to take better advantage of the data. >> All right, so here's the final, final question. I'm a customer watching this video. Bottom line maybe, I'm kind of hearing all this stuff. When do I call you? What are the signals? What are the little smoke signals I see in my organization burning? When do I need to call you guys, Datos? >> You should call Datos IO anytime, if you're doing anything with development of modern applications, number one. If you're doing anything with hybrid cloud you should call us. Because you're gonna need to reevaluate your overall data management strategy it's that simple. >> All right, Peter Smails, the CMO of Datos, one of the hot companies here in Silicon Valley, out of Los Gatos, California. Of course, we're in Palo Alto at theCube Studios. I'm John Furrier. This is theCUBE conversation. Thanks for watching. (upbeat techno music)

(motivating electronic music) >> Hello everyone, welcome to theCUBE. I'm John Furrier, the co-host and co-founder of Silicon Angle Media. We're here for a CUBE Conversation in our studios in Palo Alto, California. Here with two great guests inside the industry, to help illuminate the cloud computing conversation, really around what's coming up with Amazon re:Invent. But more importantly, the major advances happening in the digital transformation around IT and around developers and around cloud, and how that's impacting business. Our guests are Chris Comings, who's with the Chasm Group, consult and they help people, and former industry executive at NetApp, and (mumbles) the storage company. Peter Smails, the CMO of Datos.io data, and then he's the CMO there. Now, new progressive solutions. So guys, great solution. And Peter, I know you got news. We're gonna do another segment on your big news coming out, so we're gonna hold that off. >> Cool. >> The game has changed, right? >> Mm-hmm (affirmative). >> And we talked, with Chris and I had a one on one about this. But the industry conversation, there's people that are in the know, and people who are trying to figure out what's happening and how it impacts their business. CIO, CEOs, CDOs, chief data officers, chief security officers. There's a lot of things on the plate of businesses. >> Right. >> Big time. >> Right. >> So let's unpack this, and let's illuminate what it means. So cloud computing, Peter, what's your take on this, because Datos just takes a unique approach? I love your solution. A lot of people are liking this solution, but it's nuanced, because it's cloud-- >> Yeah. >> That's driving you. >> Yeah. >> What's the big driver? >> So the big driver, you said at the top of the discussion, the big driver is digital transformation. Digital transformation. Organizations are trying to be more data-driven. Okay, this is completely throwing, throwing traditional IT amok, because we're not living in the traditional world anymore of all my data sits within a single data center, I run my traditional monolithic applications. That's changed. The world is no longer running in a traditional four wall data center, and the world's moved away from the traditional view of scale-up architectures to elastic compute, shared nothing, elastic storage environment. So what's happening is, you've got the challenge of trying to essentially support traditional transformation initiatives, and it's just throwing all the underlying infrastructure foundations that an entire generation of IT professionals has known (laughs) into disarray. So everything's a little bit caddywhompus right now. >> Mm-hmm (affirmative), Chris? >> Well, and like you said, those people all have gone from being implementers to, they're moving to being developers. >> Right. >> And it completely changes their, it has to be a big change in their mindset. And it changes the management folks, the CIOs, the CDOs, the people that you interact with on a daily basis, right? >> Absolutely. >> Because these people are all trying to kind of come up to the next generation and get there. >> So you talked about, we got re:Invent coming up in a couple of weeks and, I think reinvent's a perfect term for this entire conversation, because everybody is reinventing themselves. The customer's reinventing themselves, the IT organizations are reinventing themselves, the individual roles within organizations are changing, and the whole evolution of dev ops versus traditional roles, so it is really-- >> And the vendors are all trying to reinvent themselves, too. >> Yeah, absolutely, absolutely. >> Well there's a lot of noise, so the customer's being bombarded with pitches. And if I here one more digital transformation pitch, without substance, I still don't understand. So in the spirit of trying to understand, first of all, I believe in digital transformation, but you can't just say the word, you gotta to prove it. But there's hard to prove a new approach or they've never seen it before. It's kind of like Steve Jobs would say, "If you want a Blackberry, that's a phone, "but the iPhone's not what you've seen before." But everyone loved it, changed the industry. That dynamic's happening in the cloud where for instance, your solution, some might not have seen before, but it's highly relevant to the user behavior expectations of the new environment. Okay, so this is the issue. What is the new environment specifically around digital transformation? Because I have an investment in storage. If I'm a customer, I bought a zillion drives from NetApp and EMC. I got data domain backup and, I got a perimeter, I have all this stuff, and now I've got this cloud thing bursting, and I got some analytics running there, and then I got the hot shot young developers banging out apps, and they want to put it in the cloud and... and security, I mean, what's going on? >> You wanna take that one first? And then I'll jump in. >> Can't I just buy more storage? >> Yeah. (Men laugh) Hey, just, no John, you don't just buy more storage, you upgrade from spinning to flash. I mean, that's really, >> There you go. >> That's really, really cutting edge right there. No I think what a lot of you see what they're doing is basically saying listen, for all this secondary, tertiary, quaternary, I mean, I didn't even know what that word was. But your second, your third, your fourth cuts of that data, move that all to the cloud, get that out of my environment. I'm not gonna be submersed in dealing with all of that anymore. Then maybe I can clear out some of my headaches, so I can actually focus on that primary cut, and what do I do about that primary cut? And that's where these completely new approaches come into play, and I, Peter I don't know if you call that hybrid, or multi-aire or what? But it is basically just trying to get some of that noise out of their system, so they can focus on the thing that's most valuable. >> So the way I would make that tangible John, is sort of, to us it all rolls down to the notion of the modern IT stack, okay? So essentially, the way you respond to digital transformation which, is all about being more agile, and some of the buzzwords you hear, but they're trying to be more, customers are trying to be, vendors are trying to be, or excuse me, customers or organizations are trying to be more customer-centric. They're trying to be more business driven, more data driven, okay great. If that's their initiative-- >> That's a mission. That's a mission. >> That's a mission. >> Yep. >> What that means for IT specifically is a fundamental rearchitecture of the underlying stack, okay, along a couple vectors, which is, organizations are building these new applications. They're fundamentally rearchitecting applications. What used to be a monolithic-oriented, traditional, relational, on-prem database is now running in a microservices, highly distributed configuration. That's vector number one, implication. Implication number two is we're absolutely in the mainstream of hybrid cloud, okay? You may be running all your apps on-prem, but you're still connected in some way to the cloud, for archiving, for BI, for TASDAV, whatever the case may be. And number three is the world just moved completely to an elastic, compute, shared nothing world. So we call that the modern IT stack. So the modern IT stack, modern infrastructure today-- >> Share nothing, you said? >> Shared nothing, the cloud is-- >> Oh, shared nothing. >> Yeah, shared nothing, shared nothing storage, shared nothing compute, that's that's, those are the foundations of a cloud based architecture. >> Is that called serverless? >> You could call it serverless as well. >> Okay. >> But, if you look at the modern IT stack, so to your point, the modern IT stack, modern infrastructure today is EC2. >> Mm-hmm (affirmative). >> Modern storage is S3. It could be object prem, object storage sitting on-prem. You know, modern applications are IOT. Modern, or our customer 360, IOT. Modern databases are dynamo DB. It's MongoDB, it's the number two-- >> Right. >> database in the cloud. So to answer your question very specifically, to make it tangible, that's to us the fundamental indication is, that new modern IT stack, throws storage into disarray, it throws data management into disarray-- >> It's an operational disruption. >> It's an operational disruption. >> All right, so let's backup for a second, because I think you nailed the thread I was trying to connect on. So let's take MongoDB, your reference to that being, where'd that come from? We all know why, the LAMP stack, it was one of the drivers. But developers drove that. >> That's right. >> So it wasn't the IT department recommending Mango. >> Right (laughs). >> so the developers were driving that because of ease of use. Now there's some scalability with Mango, we all know about, but what that means is, no one gives a crap if it can scale, because you already hit your product market fit. Then you could rearchitect, so you're seeing this use case of developers driving some of the behavior. >> Yes. >> Yes. >> Mm-hmm (affirmative). >> Hence containers, docker containers, and the role of Kubernetes. >> Kubernetes, yep. >> So if that's the case, how does an enterprise customer deal with that vector? Because now the developers are dictating the stacks. >> Mm-hmm (affirmative). >> Well, I-- >> Is it a free-for-all right now? I mean, this is... >> I think both of those guys are, think of it as they used to be warring factions, dev and ops, and the fact that we say the word dev ops right now is kind of a, it's kind of an oxymoron, right? Because they don't actually know each other and actually don't naturally talk to one another, and they go, "That's the other guy who's holding me back." >> Yeah, it's the old-- >> They look at, yeah, yeah. >> Goes over the fence. >> And so now, you've got folks that are really trying to, trying to bring it together a little bit more on that front and I think that, we're starting to see some technologies where people can say, "Not only can I use that "to accelerate my developments," so meets the dev criteria, but also the ops people say, "You know what, that stuff's not so bad. "I could actually work with that." >> Right, and then there's IT going, "Uh-oh," because they're basically sitting there on the catcher's side, so to your point it's, the dev ops, it is very much of an application-led environment. The tip of the spear for the new IT stack is absolutely application-led. And IT is challenged with essentially aligning to that, collaborating with that, and keeping up with that pace of change. >> And John, on this point, I think this is where, back to re:Invent, and really the role of AWS. This all started because of that. When a developer can just say, "I don't even know who those IT people are over there, "But I can spin up my S3 instance, "and I can start working against it." They start moving down the path, they show it to somebody, someone says, "Wow, that's great stuff, I want that." >> John: Yeah, right. >> Guess what? We need to make sure that that's enterprise class and scalable and then that's where that whole thing starts, and then it becomes that pull-ya-apart, "Oh God, what did these developer people do? "I'm gonna inherit this? "What the heck am I gonna do with it?" Now it's, we've gotta move that to be more symbiotic up front. >> I remember talking to both Pat Gelsinger and Andy Jassy years ago, I think maybe five years ago, and I asked the question, "What enables developers?" What is enabling point? Does infrastructure dictate developer behavior? Or do developers dictate infrastructure behavior? This was years ago, when the dev ops was an early-on movement. Clearly the vote is there. Developers are driving infrastructure. Hence the dev ops infrastructure, >> Absolutely. >> Yeah. >> as code model, that's proven. Jassy was interesting because he looked at it that way and said, "Yeah, we saw the same thing," and they've never wavered, Amazon's stayed on the course, and they've just been running like a machine, like a, just pounding it out. I asked Pat Gelsinger, he once positioned the AWS as the developer cloud. Kinda in, I wouldn't say depositioning them, but he was basically pointing out, they have a developer cloud. Now Amazon's the enterprise cloud. >> Mm-hmm (affirmative). >> Because they've developers are now a big driver of that, and the scale with data is actually turning out to be a better security environment. >> Right. >> For cyber. >> Right, it might just-- >> So it's cloud's winning. >> Cloud is winning and just sort of just take that one step further. It's always ultimately, the winner's going to, it's Darwinism, it's like the winner's gonna be the one with the richest ecosystem. And AWS is becoming that enterprise eco. And you could argue, I mean, GCP's fighting to be in there, Oracle's not going to go quietly into that dark night. You've got multiple public cloud vendors. >> That's right. >> Yeah. >> But the reality is that he who has the biggest, he or she who has the biggest ecosystem is gonna win, and that's right now is AWS driving that bus. >> All right, so I need to see those glasses for a second, and then want to go into another line of question here. (men laugh) >> You may use those. >> Oh who's, oh you put them on, all right good, as long as he's wearing them. >> He that wear-- >> You know, on that front too, on that front too, I would think we started back where VM was the big new thing, and here we go with VM's, and then all of a sudden we're coming up and we're saying, "Yeah, now there's containers." And so now we're gonna see this move to, we want to micro-package these services, and be able to aggregate them. Well you know the average IT shop that I would be talking to out there is just still trying to figure out, how do they put together their on-prem and their AWS instance? So this notion of hybrid is where most of these large enterprises are. We see a lot of terminology out there and a lot of vendors talking about multi-cloud. But multi-cloud is really just taking an option on the future and saying, "I'm not locked into you, AWS, "even though I am locked into you 100% right now. "I don't want to be forever in the future." >> It's a value statement that they're gesturing. >> That's right. >> Good segue. >> Chris: But it's not a practical implementation piece. >> I got my nerd glasses on so-- >> Peter: Strap in for something, here we go. I got my nerd glasses, so next question, we'll go a little nerdy, because this is important one. I put out at my crowd chat for Amazon, so to crowdchat.net/awsreinvent it's open, I have a lot of questions on there. Feel free to weigh in, it's an influencer-only chat, so no consumers, so I asked the question, and this is to the value statement, because multi-cloud is basically telegraphing lock-in. We don't want lock-in. >> Right. >> But we want love choice. If you have good choice and good value, we'll go there so it's a value equation. So the question I said is, where do you, this is a question I put on crowd-chat, I'll ask you guys. Where do you see the value that cloud creates for customers in the next 24 months? #cloud So the first response was from Subbu Allamaraju, who's the CIO at Expedia. He writes, "Agility from the service "ecosystem and rapid second-order architecture "architectural changes thereby clearing technical debt." And the second one from Grant Chase, "Born on the cloud apps already here. "Next wave migrating of existing apps." And then Maddoux Tsukahara said, "Legacy SASS applications will be disrupted "by cloud microservices, serverless, "and AI and machine learning." So we start to see the pattern. Your thoughts? Value creation, in the cloud, is gonna be what? >> So I think they're hitting on the right trends. I would go back to the first one which is "How do I get this on-prem stuff "that's driving me crazy, consuming all of my resources "in terms of maintenance and upgrades? "And then optimizing my environment for that." Which ones of those are core? And which ones of those are really kind of ancillary? I've gotta have them, but I really don't want them. If I didn't have to use them, I'd get rid of them. Take all, just do that homework. Separate the two cleanly. Move ancillary to the cloud, and move on. >> Peter: Yeah, yeah. >> So service ecosystem he nailed, I love, by the way, I agree with you, that was my favorite answer. And rapid second-order architecture changes. This speaks to what datos.io is doing. Because you guys, what you're in, the tornado that you're in, kind of just a play on the Chasm group here. You guys have a solution that has got visibility into some of the real dynamics of the environmental environment. >> Check. >> People, tech, stack, et cetera. >> Yeah, yeah. >> So what are some of the things that you're seeing that point to these second or level architectural changes? >> Well you mentioned, a couple different things, which is, you mentioned the notion of technical debt, which is indirectly what you were just talking about, the ability to get rid of my technical debt. It's an easy way, it eliminates my barrier to answering to creating net new applications. So without having to sort of, I avoid the innovator's dilemma if you will, because I can build these net new applications, which are the things I have to to drive my digital transformation, et cetera. I can do that in a very cost-effective and agile way. Meanwhile, sort of ignoring the old world. Then what I'll do is I'll go back, and I'll worry about the old stuff, and I'll start migrating some of that old stuff to the cloud. So in the context of, yeah, so what we see from a Datos IO perspective, in the context of data management, is that one, applications drive the stack, like you said earlier, it's absolutely, the application's at the tip of the spear, driving the stack. Organizations are building net new applications that are cloud native, okay? And they're built on the new modern IT stack, and at the same time, they're also taking their legacy application, so I like that second answer as well which is, modern cloud applications are here. The interesting thing is, you say modern cloud apps, modern cloud apps don't have to run in the cloud. >> That's right. >> We've got customers that are running their next gen app-- >> It's an operating model. >> It's an operating model. We've got customers running 100% on-prem. Their econ number stuff runs on-prem, then you have people that run in the cloud. So it's a mindset, it's an operating model. So you've got folks absolutely deploying these cloud-native apps. >> Well, it's an architectural model too, it's how they are deploying and servicing apps. >> And ultimately, it comes down to the architectural model. That's what shifted, and that world is very infrastructure. The other thing I would add to the cloud thing is if you do it right, the cloud actually can give you architectural independence and cloud independence, but you can't be focused on the infrastructure level. You've gotta focus at the application level, because then you can be agnostic, until they're online. >> So Peter you, you guys are disrupting a very large space, backup and recovery in the cloud which you guys are doing. >> Check. >> And the application database layer is a very progressive solution. So I love your approach, but you're talking about disrupting the data domains of the world. We're talking about big whales. >> Yeah. >> Big incumbents that are built around four walls in the data center. >> Check. >> Mm-hmm (affirmative), yep. >> What are you seeing? What's the makeup? What's the personnel of the customers look like? If dev ops is happening, which we agree it is, and the the evidence is there clearly, they're not 50 year old backup and recovery guys. They're young guns, they're probably not thinking about waking up every day with their coffee, say, "Hmm, what am I gonna do with backup today?" >> Yeah. >> Mm-hmm (affirmative). >> They're waking up saying, "Hey, I'm gonna drive some more machine learning "and AI in my apps." >> Yep. >> "And I'm gonna provide workflow movement to--" >> And you said breakfast was some, you said that. >> Adopt this microservice. >> I had the craziest dream last night. It was microservices, what? >> Yeah. >> Yeah, so I can answer that two ways. There's the technology side of it. Fun little tidbit, average age of the traditional backup and recovery software architecture, about 20 years. >> Hmm. >> Architected well before the mainstream advent of the cloud or certainly modern applications. >> Hold on, the person's 20 years old? Or it's 20 years of architecture? >> No, the architecture of the software. >> Okay. >> The solutions, or come up, the point is they've been around for awhile. >> It's old. It's old. >> It's old, fair enough. >> Yeah, and 20 years-- >> So on the technology side, that's a dilemma. On the persona side, you're absolutely right as well. These are, it's the application folks that are driving the conversation, that our applications dictate the IT stack. They're building these new architectures, which have all these implications on the infrastructure. >> All right, so I'm gonna play devil's advocate, just because I want to connect the dots. And again, illuminate what I think the problem is that you have. One is, okay I'm a CIO. Hey, he's my storage guy. Who the hell are you, young gun? Complaining about your backup and recovery. He recommends all flash arrays in the data center provisioned in a VSAN environment, whatever that's going on. Who are you? You're just nothing to me. You don't make that decision. >> I'm the guy that can give you all the visibility to your data to make you smarter and more agile as a company. I can save you money. I can make this company more market-- >> So what do I need to do differently? If I'm the CIO, I don't want to make these, or these architectural calls based upon old dogma or old reporting lines. This is an example. I go to him, he's my storage guy. Who are you? I already built you the dev ops environment. He runs storage and so, you're impacted as a developer. So how do you guys talk to that guy? What does the CXO have to do differently to adapt to the new environment? >> I'll take that and then you can-- >> Please. >> You know, jump in. So I think what you see is, you see the proliferation of new personas. Like you see chief transformation officers, you see chief digital officers. You see system architects and DBAs getting a more prominent role in the conversation. So the successful CIOs and technology officers are the ones that are essentially gonna get the cowboys and the Indians to collaborate more closely, because they have to, because the folks that were over in the corner that used to get laughed at, building these, oh mangos and these new applications and such, they're the ones holding the keys to the future. So the successful technologists are gonna be the ones that marry those personas from the application side of the house with the traditional storage, infrastructure folks as well. You successfully do that, then you can be more, then you can move more quickly forward. >> Yeah, that's right. >> What do you think? >> Well I think some of it's gonna come back down to economics, too. And I agree with that move which is, I talked to over a hundred CIOs and their staff in the last year. I had one conversation where the person said, "You know what? "The chief complaint about me as CIO "is I'm not spending enough money." And I thought to myself, "Sounds like a company that I should put some bucks into, "because they must be doing really, really well." Everybody else is looking at it saying, "You know what? "I'm under pressure to adopt the cloud, "because there's a belief out there "that the cloud is gonna be so much less expensive "than what they've done in the past." And then I think they find that it's not, that it's not just the one size fits all answer to that. >> Right. >> And so as a consequence, you're gonna have people say, Listen, this money printing operation, or this funnel out the door to, whether it's EMC or NetApp 4, or whatever it may be, whatever storage vendor for backup architecture, they've got to stop that funnel. Because they've got to take what they were spending there and move it to the things that are going to make money for them, not just gonna hold on to it, and de-risk their enterprise. >> I'm here with two industry leaders, Chris Comings and Peter Smails, talking about the impact of infrastructure technologies, and app development in the cloud for businesses. It's a great conversation, and our final point, I wanna just get to, I know we're running on some time here but we wanna go a little further. I think this is awesome. That's for taking the time to share it out. >> It's great. >> One of my other questions I put on my crowd chat was, a true or false and comment question. Here's the statement: Serverless computing will become mainstream, will come to mainstream private cloud, true or false, comment. Subbu said, "False, adoption and success "of serverless patterns depend almost entirely "on the strength of the ecosystem "that the data center lacks." Interesting comment. I was kinda leaning, I go, "I was leaning towards true." But I don't have enough insight on this, because I'm waffling between true or false. I love serverless, I love the idea of, notion of resources that are just programmable. But what is the state of serverless? I mean, is he right? Is that that there's not enough ecosystem in the data center areas or... >> You wanna go first? >> Well, I'd just say that I would, I would just call out two things on that front. One is, I think you need a lot more germination of microservices that are out there in order to be able to put that all together. That's one aspect. We're seeing that growth come rapidly. The other thing is, now your security is beholden to the lowest common denominator. The security of that individual microservice. So I think you're gonna have some fits and starts here as we move down that path because, boy oh boy, the last thing I wanna do is get all modern but at the same time, put myself at a greater amount of risk. >> I thought the comment at the end was, I think it's true. I thought it was interesting what he said at the end. He said, "The ecosystem that the data center lacks." I would contend that potentially, the ecosystem that the cloud has would support that. >> Yeah. >> Because the cloud, by definition is, it's a shared-nothing world. >> Right. >> You know? >> So, he also comments, someone said, Lambda, "My Expedia is that Lambda's growth "is almost entirely due to the power "of the ecosystem of services, "which is one of the key points," and he points to his blog post. Stu Miniman, our Wikibon analyst weighed in, because Stu's on this big time. "Service will definitely be used for edge applications. "Currently don't see use case for general data center usage." >> Mm-hmm (affirmative). >> So edge of the network. Again, good point? This edge of the network thing helps you, because most people are using cloud for edge. >> Peter: Right. >> So this IOT, which is, an iterative things, is an edge of the network. >> Yeah, yeah. >> Whether it's devices, sensors, industrial equipment, or people's devices on their bodies. >> Yeah. >> It's a huge data source. >> Absolutely. >> Cloud's rolling that up. Or a cloud-like infrastructure. >> Well but it's not necessarily rolling it up. It's just connecting all the dots as to where you can put storage and you can put compute where the data is. Or you can move the data to where the storage and the compute is. So it's not, I mean, yes there's core and edge, that's absolutely true, but the notion of rollup isn't necessarily true. It's not necessarily the cloud enables me to do all this colossal aggregation. It's I basically distribute my compute, I distribute my storage. >> Well, when I say rollup, I'm assuming there's some sort of architectural thing. >> Okay, fair. >> But this fits into your wheelhouse, I think. But I just connecting the dots. That's why it's a question for you is, it would make sense for a solution like DATOS to be there because, That's a application so you-- >> Absolutely. >> You back up IOT? >> Oh absolutely. We backup IOT, but we basically backup any modern cloud application. And by definition, what does that mean? >> So IOT's and app for you. >> IOT, absolutely IOT's-- >> Not necessarily a-- >> So the technically where we plug in is, we plugin at the database level. And the databases basically, are the underlying infrastructure that support the applications. So in the case of IOT, those are typically very highly distributed across GIOS, absolutely we protect them. >> So we were just talking earlier about the words flexibility, manageability, agility. That's kind of vanilla words that everyone uses these days. But in essence, you're actually really doing it. Right, so. >> Thanks for that setup. Yes, we actually do all those buzz words. >> So Chris recommends, I recommend that you call it, hyper flexibility. >> Yeah. >> Or microflexibility. >> Or ultra. >> Or ultra flexibility. >> Or go mega. Just go mega right now. Or uber and steal a little of that, although that's kind of out of favor right now. >> Not, uber is-- >> Uber we wanna let that one kind of fly by. >> But remember we also talked before, we thought we were spot on with our product being branded RecoverX. We thought we were really in the spot with the whole, you know. >> Your name is awesome. RecoverX is a great brand. >> So we're gonna stick with that for now before we-- >> Good branding, RecoverX, Data IOS. Chris, thanks for coming on. Final comment, any words on the storage industry as it evolved? You mentioned earlier, just call it flash. Certainly, all flash arrays are doing well. Pure Storage went public. Flash is a standard. >> Yeah. >> It has benefits. Where does the flash storage go with all this cloud value coming over the top? >> Well I think, you know, there's gonna be a couple. I have one comment on that which is, we see what flash is doing at the array level, and now we're gonna see what NVME does at the cash layer, for allowing this access to information. You think about, I want to run a singular query, but some of that data is here, there, everywhere, but I've gotta have a level of performance that allows me to actually run it, and get an answer from it. And so that's where that comes into play. I think we're gonna see a whole host of folks flooding into that space, to try and improve performance, but not only improve performance, but enable that whole distribution model. >> Yeah, and I would just pick up on more persona-centric thing which is, the message to the traditional IT shops is it is all about collaboration. The folks over in the corner, the application folks, it is absolutely all about getting more closely aligned, because cloud is here. >> Yeah. >> Multicloud, hybrid cloud, call it whatever you want, is here. The traditional IT stack is absolutely being disrupted, and it's all about embracing this application-centric, data-driven view of the world. That's the future, traditional IT's got to align with that, and collaborate and drive that whole thing forward. >> That's a great, I agree 100% what you guys just said, great comment. I would just say Wikibon calls it unigrid, which is, I'll rename it hypergrid, meaning it's just one system, to your point. Private, public, it's all cloud-like. >> Absolutely. >> Yeah, it doesn't matter where it goes. Okay guys, thanks for the thought leadership. Peter Smails and Chris Cummings here, breaking down the industry landscape on storage infrastructure, application developers, in context the cloud. This is theCUBE conversation. I'm John Furrier, thanks for watching. (motivating electronic music)

(uplifting music) >> Hello, everyone. Welcome to theCUBE Conversations here at the Palo Alto Studios for theCUBE. I'm John Furrier the co-host of theCUBE, co-founder of SiliconANGLE. We're here for Thought Leader Thursday, and my guest here to talk about the cloud, earnings in the industry, and also all the mega trends happening is Tarun Thakur, who is the co-founder and CEO of Datos.IO, hot start up out of Los Gatos, California. Welcome back to theCUBE, great to see you. >> Thank you, John, thank you, good to be back. >> We love having entrepreneurs come in because you guys are on the cutting edge, you're sweating bullets, you're stressing out, you're building the company. You guys are still in a growth mode, which is great, congratulations. >> Thank you. >> But you're also playing in the cloud game. You're in the ecosystem. We're seeing massive visibility now into the numbers. You see the cloud earnings just came out. Amazon continues to crush it. Microsoft, they're bundling 365 and they're juicing the numbers up but we all know what's going on there, but still, they're looking good. >> Correct. >> And then Google's a dark horse with really that developer platform looking good. So the big three are popping. But, you know, Facebook just announced a $10 billion quarter. They're a cloud too, not to be reckoned with, but kind of not in the pure infrastructures of service. So clearly the market has shown that there is some stability. We're in the second, third inning maybe of this cloud game. What's your take on the marketplace? >> No, I think this is an excellent topic. Thank you, John, for again having us back. Always great to be here. So, you know, the way I think about what's happening really in the cloud is really from three dimensions. Number one, you know, you rightly said $20 billion is what Amazon is on a run rate business of. We personally believe it's still the first innings. It's not the second or the third. You know, they've seen a massive adoption as its called the product market for developilabilty, where the developers, where the application developers, where the SMBs of the world, but the enterprises are just starting to scratch the surface of the cloud. We believe the cloud is in the first innings. The real growth. >> Enterprise cloud. >> Enterprise cloud is just beginning. Just beginning, right. I was, you know, I'll give you quickly an example. I was out in Denver visiting a customer, which is the world's largest, one of the world's largest, shipping companies. They are moving as fast as possible to the cloud, but this is their first foray. But their first foray is not five terabytes or 50 terabytes. Their first foray is 50 petabytes of data. >> So they're moving big time. >> Oh, they're moving big time. >> This is not a toe in the water. >> No, they took two years to evaluate it, and then they go big. >> Right, so talk about the trends here because let's tease through the numbers. I looked at all the earnings, and again, Microsoft is doing well, but remember, they're bundling Office 365, which kind of puts Google unnoticed because Google's got a huge presence that they could roll in. So there's a lot of number games going on that the analysts are kind of pointing out, and we're pointing out, but Amazon has just been crushing it on overall performance. >> Right. >> I mean look at the compute that's going on, the scale, they've got thousands of enterprise customers, and still there's a lot more growth there because the on-prem, true private cloud, is still growing. >> That's correct. >> So what is the state of the enterprise now, and who is using the public cloud more, and who's using it less, and why are they doing that? Is it a makeup, is it a DNA culture? Is it just evolution? >> No, it's just evolution, John. I think the enterprises are finally latching on to this, I think they are, but they're latching on it in a big way. Right, and so that's the second point that I sort of wanted to highlight that while you call Google the Trojan horse, and Amazon being the lead, and then Microsoft somewhere in the middle, let's not forget about Oracle cloud. Larry Ellison is a formidable competitive spirit. He's not going to give up. He has not given up so far. They are going to build an Oracle cloud. There will be a-- >> Well they have an Oracle cloud. >> They have an Oracle cloud. But, you know, having versus really truly-- >> It's so funny, Larry Ellison called Salesforce a fake cloud, but a lot of people are calling Oracle a fake cloud. >> A fake cloud. >> But Oracle on Oracle, we've entered Dave Donatelli, Larry is the only one that hasn't come on theCUBE. Oracle cloud works great with Oracle. >> Correct. >> They're trying to put the message out there that Oracle is working well with cloud native. They're in the Cloud Native Foundation now. >> Sure, sure. >> CNCF, so you stayed in Oracle amidst Avery and folks over there doing a great job, so, but they're not getting the word out. Oracle's not getting the job done because no one sees Oracle as a cool cloud native company. >> No, and they're not. And I think that's a very valid point. But what I'm saying is that there will be room There is oxygen in this market to get the fourth and the fifth cloud provider. There will be specialized clouds. And there will be places for that. Because Amazon is not an answer for all. It is definitely an answer for majority of your workloads, but the HPC, the high performance computing workloads, the GPU workloads, the Oracle. You know, you look at the number one database in the cloud that Amazon claims openly is MySQL. It's not Oracle. An Amazon database business, if they're making 20 billion in total AWS, I will tell you about 40% or 50% of their business is database. And that's not Oracle. So think of five to $10 billion of revenue and money that Amazon is making is not Oracle. >> What's that mean? Does that mean Oracle's losing money or. That's leakage on Oracle's model? Is that Oracle still has an opportunity? Cause they still control a lot of databases. >> Thank you and, thus, thank you, thank you for asking that. It's not that Oracle is losing money, it's the next generation applications, it's the cloud enabled applications. >> So it's growth, it's pure growth. >> It's the new oxygen, it's the new wealth creation. >> So it's like the classic example when the internet started. Web traffic increased because more people were using the internet. >> Correct. >> So what you're saying is that cloud has created a more database market. Amazon's getting a big chuck of it there, but Oracle still has the database market. >> For example if you look-- >> And SAP too. >> And look at the third reason of these clouds, if you look at AIML, right, these applications, the Alexa, the Siri-like applications, and the applications that will be built on top of this, will be built in the cloud. You're not going to start building Alexa AI application on prem infrastructure. That is not happening. And that's the third part of this whole cloud. We say it's $20 billion and we have barely scratched the surface on AI, ML, and blockchain. And all those applications that will be built, will be built on cloud elastic infrastructure. >> Alright, so what's your take? I mean, right now Amazon's winning the cloud game, Oracle, I wouldn't call them number four, but they're trying to juice the numbers up as well, but they clearly have an installed base, and they're not going anywhere. >> Tarun: Captive audience. >> SAP is going multi-cloud, so you're seeing SAP starting to put their, looking at saying, hey, we want our customers to run Oracle SAP on any cloud, so they're clearly thinking multi-cloud. Who else is out there? Alibaba cloud is now coming to the US in San Mateo, so they're number seven cloud but four worldwide, right? >> Tarun: Correct. >> So, pure worldwide numbers, Alibaba's four. >> Yes, so I'll start with Ali cloud. You know, you talk about Alibaba, their cloud is called Ali cloud, and fortunately, as you're building a company, as you talked about earlier on in our offline conversation, you get to meet all the way from governed DoD's and DIA's of the world too. We worked with Ali cloud executive team just a few weeks ago and they were out here in the bay area. Didi is the de facto car hailing company, it's not Uber, in China. We believe Ali cloud will be that in China. There will be a fifth cloud, there will be a sixth cloud. To my point, there will be specialized clouds. Amazon's not going to win this entire pie. And there will be clouds outside of US markets. >> Well I had a chance to tell Karen Lu and Dr. Min Wen Li as well as Dr. Wong at Alibaba in China a few weeks ago, and if you look at what they're doing in China, it's not just cloud. They've got eCommerce, they've got the city brain project. They're looking at holistically around data. Data's fundamental to their vision. I think that's consistent with what we're seeing in the US. A little bit more broader scope because IT here is a little bit more, has more legacy. China's got much more focus and got some government controls in there to get some latitude to do the right things. But the consumers are moving faster in China. If you look at the mobile growth. >> Absolutely. >> John: Huge indicator. >> Look at the Didi's growth. Didi's growth is more faster than Uber's growth. Right, and they've built a massive, massive company out there. >> IoT is pretty hot in China, you're starting to see that. I mean, this is a re-imagining of cloud, so you guys are in the middle of it with back on the road recovery. So as a CEO you're in the body swerving, car's that are flying by you, you're trying not to get run over. You've got a good market opportunity with the cloud because GDPR's coming right around the corner. >> Yes, yes, absolutely. >> So what's your strategy? Are you, I mean, I'm paraphrasing, not dodging cars, but, I mean, as a start up you've got to worry about your success might kill you, but how do you manage the business? I mean, how are you looking at this? Because you've got a great opportunity, and it's a growth market. >> Thank you, thank you. No we're lucky and fortunate that some of the decisions we made back four years ago people used to laugh, why are you going in this market of cloud data applications and isn't eight out of $10 dollars being spent on Oracle. Why would you go off to that. And, we're like, guys that's today. Where the puck is going. The puck is going towards the cloud and cloud applications. And to answer your question, we've found beautiful beautiful excellent product market fit. A little bit about the company. >> John: What's the use case? >> We're just classically going backup in recovery use cases. Built for cloud native applications. So, for example, I talked about the number one database in the cloud is MySQL. The number two database on prem is SQL Server. Take a guess on number two database in the cloud. It's MongoDB, they just went IPO two weeks ago. Number two database on Amazon is MongoDB. Who thought that five years ago? >> Well Lamp Stack its just open stores driving a lot of this action. >> So, I'll give you an example, one of our biggest, biggest customers which we're going to be announcing very soon, but take the liberty to share here, OpenTable. OpenTable, we are protecting OpenTable. 2.5 billion documents. That's yours and my reservation. That's your and my reservation that we make for a beautiful restaurant. >> Yeah, and if I change that reservation I've got to have that backed up, but want to bring it back. You guys are doing that. So what's the scale of the OpenTable? Ballpark it. >> So all their entire reservation applications. >> The whole thing. >> I probably will not talk about the datasets. You know, but their entire geo-distributed applications. You could be sitting in New York or you could be in London. >> And in which cloud are they using? >> They are all Google cloud, they're on prem. So they're truly private cloud and public cloud. So I call that a multi cloud data management space. They've a ton of stuff still on prem. They're not going to diverge away from that very quickly. >> What's the Google situation? Sam Ramji is over there doing a great job. Google Next is coming up soon, next year. Great traction, but still people aren't considering Google as the white glove service because, well, Amazon's not really known for that either, but at least they have a lot more, thousands more customers than Google does. >> Yeah so I think that the problem is twofold, in my humble opinion. Or the observation is twofold. One, I think Google needs to amp up their game around cloud and cloud messaging. You open Amazon AWS.cloud website, and you open GCP website, you could just see the differences. How Amazon talks about cloud. You're still selling compute storage network, but they talk business agility. What took a month for SQL Server now takes two hours. That's what you're selling, right? >> You're selling speed and you're selling automation, and you're selling value. >> Orchestration. So I think Google has to amp up their game, and amp up their game around that. >> Are they too technical, too geeky? >> Too nerdy, too geeky and still talking about infrastructure. >> Yeah sure, and I think Sam knows that too. >> And I think second part, which is, you know, they absolutely need to amp up their game not go head on and follow Amazon, find the newer applications and new use cases, where they can go ahead of Amazon. Whenever you're playing Art of War, either you can follow somebody or you go establish your own base. >> If they go frontal attack on these guys they'll lose, they've got to play the shadows. I think they can slingshot around them. I think the developer traction they have is strong, even though Amazon's got strong developer traction. Google's got some goodness with TensorFlow, they've got some great technology, but they've got to stop the game of we're Google, go with us. Enterprises don't work that way even though I get why they say that cause it's true. At some level from a alpha geek perspective, but this isn't the land of alpha geeks, these are real people that have jobs and enterprise IT that won't transform. >> They're real enterprises, who have real DBAs, and real server admins who really care about data services. Going back to the comment-- >> Not just the shiny new toy. I need reliability, proof. >> I want durability of this data. Don't just tell me I can get compute 10 times cheaper than Amazon. That's not what I care about. Change my, talk my language. I care about data services. I called data driven enterprises. >> Okay, as you guys go out and talk to customers, give me the anecdotal view of the landscape of customers. Because obviously the earnings came out. We saw, again, Amazon continuing to do well. But they've got some competition. We just laid and unpacked that. Customers now see this. What's kind of the the conversations in the boardrooms, and then in the trenches in IT and enterprise as they transform because IT is not a department anymore in the future enterprise. It's now a fabric of all things in cloud native. What are the conversations? Are they slowing down, obviously they want to go faster, is it a personnel issue? What are some of the conversations? >> I'll give you real example. We presented recently to a big, massive federal government agency. We cannot take their name out of legal. >> John: They spend a lot of money. >> Out of Washington, D.C. out here in the Bay area. >> CIA. Or, NSA. >> You're looking at the start-ups in the Bay area, and they were like, look why had we ever adopted the IBMs, the mainframes, and the EMCs, and the Dells of the world. We also know the wealth of the innovation is here in Silicon Valley. Right, so they come out once a year. And I can tell you, John, spending two hours that we did with them earlier in the week, and they are accelerating their journey to the cloud. Things that were foreign terms like micro services, that's how they want to build these federal agencies now. Every application has to have microservices. They are not truly there. I'll tell you that. They are not there, but that is top of mind for the CIA. >> And gov cloud has grown very fast, fedramp, all these services. >> Amazon called it Commercial Cloud Service, c2s, built for the government. And that entire team was here. >> Well Tarun great job. Congratulations on your opportunity we just talked about. Datos.IO. You guys, it's Datos.IO if you want to check out the website. You're going to be at Reinvent, you're going to come on theCUBE, we'll be there with two sets. Again, I have 50, you're doing Amazon, love the community there, they do a great job, Andy Jassy comes on, great group, Trace Carlson, among others. What are you expecting to see this year at Amazon? Besides the fact that it's going to be crowded and certainly the show of the year in terms of cloud. >> Momentum, they're going to accelerate the momentum. The amount of services they're planning to announce from, because we work with the team very closely, and the amount of acceleration they're showing, the new partners coming on board, and the partners like us who had one customer, and now we have 20 in Amazon cloud. You know, we just became an advanced technology partner, they understand that. >> So you're happy with how they're working with partners? >> Oh we love Amazon team. We became an advanced technology partner. They drilled us down for three months to prove themselves, yes, Datos can run on their infrastructure. You know, they want to go fast, but they want to go diligent fast. >> Yeah, we love Amazon too, of course. Our crowd chat solver's on their website as a case study using some of their stuff. Thanks so much for coming on, your final thoughts. Earnings, cloud, where are we? >> This is unstoppable force. It's an unstoppable force, we're in the first innings. There's so much opportunity ahead of us. And we couldn't have picked a beautiful market to than what we did. >> And true private cloud as we keep pointing out, turns out that's playing out. On prem activity's high. Your thoughts on on prem? True private cloud? >> It's going to survive, it's going to survive. But it's not going to be the growth place. >> But we think it will grow with the SaaS. >> With the Saas, I agree, but infrastructure. Infrastructure is not going to be growing. So that's our two cents, but you know, we'll be back in a couple of weeks, we have a phenomenal exciting product launch coming up. >> I just tweeted on Twitter this morning $1.5 billion is going to be coming out of on premise, non-differentiated labor operations. Which basically means, the rack and stacking some of these jobs are going to go away. But the growth is in automation, AI, and machine learning, and some SaaS tooling. >> Cloud applications. >> Cloud operations business models growing on premise. >> And those dollars are going to leak to the cloud. >> Yeah, and cloud, it's all to the cloud. Tarun, thanks so much. >> Thank you. >> Co-founder and CEO of Datos.IO. I'm John Furrier here for CUBE Conversation in Palo Alto at our studios, thanks for watching. (techno music)

>> Announcer: Live from Las Vegas, it's theCUBE, covering Dell EMC World 2017. Brought to you by Dell EMC. >> Okay, welcome back everyone. We are here live at Dell EMC World 2017. This is our eighth year of coverage of formerly known as EMC World but is now Dell World. First year of the combined companies. Some say Dell bought EMC, some say EMC bought Dell. Either way, the merger and the acquisition, or combination, however you want to call it, certainly working out. This is Cube coverage of the first year. I'm John Furrier with my co-host, Keith Townsend, CTO advisor. Our next guest is Tarun Thakur, co-Founder and CEO of Datos IO, big news and as well, Peter Smails, Vice President of Marketing and Business Development, a former EMCer, been in the industry. Guys, congratulations, welcome to The Cube. >> Thank you, John. Thank you Keith. >> Thank you very much. >> It's a pleasure to be here. >> Big bang news at the Dell-E, so tons of stories here. Obviously the big story is the combination, but you guys have some really amazing news. Funding, traction, give us the update on the hard news. >> Excellent, thank you, John. First, thank you guys. Thank you very much for the opportunity to be here. The last couple of weeks have been just amazing for us. Last week was all about product, which Peter is going to talk about. Our journey from our one portal to our two portals. That journey is all driven by customers and where the market is headed. But this week was all about enterprise adoption. It's a&bout enterprise activity. You have these two industry stallworths, 200 billion dollars of market cap, recognizing the value of what we have been-- >> John: And so the hard news is, what, Cisco and NetApp have invested? >> Cisco and Neuron Motor invested in Datos today. >> So this is a round of funding from corporate investors. Any VC's coming in as well, or-- >> Both, you know, the investors were already in the company, they claimed their ownership-- >> John: Okay, so they did their pro-rata. They re-upped. Okay so, new corporate investors, that's validation. >> Yes, yes, yes. >> Why are they investing? My masses wants to know, why the hell are they investing? Why don't they just do it themselves? >> Yeah, so you know, look, I think this looks very, very clear that this industry of the data management, or this industry of enterprise with option to the cloud is just massive-paced right now, right? The acceleration is at it's highest gear, so to speak, and we've been working with both those companies for the last few months. They recognize at fundamental level what we've built, like, the application-centric nature of the product, build it fundamentally for cloud ready applications, helping existing customers mobilize their applications to the cloud. You know, you have to-- we have, now, three year lead, into the space, right, and it's best to join forces. >> Well, we had our Cube conversation in our studio in Palo Alto too, and you kind of smiling then, certainly smiling now. The big funding, big fat financing, as they say, but you really kind of coy about not sharing the news to me, which I thought was cool, kept the secret, but you guys have shell-- >> Tarun: I had valid reasons. >> But, the cloud is certainly accelerating. You guys have the tiger by the tail. But, if you look at the VC funding landscape, we were saying yesterday on our opening that, it's a canary in a coal mine. It's a really leading indicator of what's going on in the marketplace. If you're a storage start-up, you're DOA. No one is funding that. They're re-pivoting always. You see, "I got scale out, scale up storage," pivot, pivot, pivot but all of these companies, data management, data backup, and protection are all booming. Massive up, Rubrik, Cohesity, billion dollar valuations. Why are these companies getting such big funding? Why are you guys being so-- Is cloud just creating massive scale for what was normally a white space? >> No, sir. The answer-- I'll go first. >> Go for it. I'll jump in. >> Because you come from this all most recently. (laughter) >> Look, John, there has been no innovation in the space of backup and recovery for the last three years. We've been still living in the world of four-wall data center media-server based architectures, and backup and recovery products that were truly return for tape architectures. That world ain't exist in this cloud world. There has been no innovation, and now you see complete replacing of good companies. Great follow up companies to be p6art of. All of us recognize the disruption of opportunity, and recognize what we all do for the next 10, 20 years. >> And I'll jump on that. So, if you net it out, there's really two things happening. You know, 70% of CIO's have a cloud-first strategy. So, enterprise, one of the reason we're here. Enterprises have a cloud-first strategy. They're moving to the cloud. They're doing two things. One, they're either building net, new applications in the cloud. Geo-distributed, highly scaled applications. You need a fundamentally different approach for protecting those applications. That's number one. Number two is those same customers are saying, "I want to move as many of my non-recovery workloads from my traditional four wall data center off prim. I want to leverage the cloud. I want to put my data where I want to put it when I want to put it there." There has not been any good solution to do that. So, for us, that's cloud data management. We're about protect. If you have stuff in the cloud, we'll protect it. If you want to move stuff to the cloud, from the cloud, within the cloud, that's mobility to us. That's what we do. Ultimately, this is why there's so much attention being paid to cloud data management, because everybody's moving to the cloud. The one thing we have heard consistently-- >> John: It never existed before, really. >> They're not taking traditional tools to the cloud, simply put. >> You know what, go to the website, I don't see anything about backup. I don't see anything about, you know, there's data protection, but in an enterprise, when we go to the cloud for the first time, a couple of things we figure out first. Backup is hard, because, you know, I can't point my data domain to S3, and backup S3 or some type of &object storage. I also find out that these traditional architectures within the data center just don't translate to the cloud. So, where are you guys at in the education cycle of the enterprise, and helping them understand the value of the application-centric model, and where do you need to go? >> Yeah, so... Keith, that's a good question. You actually hit the nail on the head. You have these proprietary backup appliances. We used to call data domain, really a PPB appliance. You have these media-server based architectures with the likes of Vericlass and Condor. Perfect for four walls, right, in the cloud geo-distributor applications, right? You look at those, sort, that scale, the application centricity, and we started, what we did in our strategy, we started with absolutely green field. What does that mean? That means the cloud-native applications, the non-relatable databases, right? The analytics, the IO key applications. So you go towards the use-case where the world and the customers are already thinking cloud-native. Coaching and training customers, as you rightly called, is a very hard journey. It is a crossing the chasm. It takes time. You need to start with earlier doctors, the innovators, who will then latch onto you and take you forward. So, our strategy of picking the space, which was completely green field ablution, couldn't have served us better. >> So, what's that next step after we've figured out backup, because we have to back the data up. Data management is way more than backup. Now, as I've blown away the limits of my data center, and I can access data from anywhere in the world, what have you helped customers understand that they can do with their applications and data, now that I can access it anywhere in the world? >> Tarun: Excellent question. >> Yeah, so, I can take that. So, to your point, if you look at protect-- our three pillars: protect, mobilize, monetize. You'll hear us say that over and over and over again. We started with protection. It's a business-critical use case. You cannot have a cloud-first strategy if you don't protect your data. Got it. Second piece around the mobility piece is, like you said, giving. What have we done by being application-centric data management? What do we do that nobody else does,6 is we enable you to, very intelligently and very efficiently, move data sets, in native format, where ever you want. To any cloud that you want. We don't normalize data. We don't change formats. So, for example, I'll give you one great example of application centricity. I have an on-prim workload. I want to run a query against that. Star, not Peter star. That resulting data said, "That's all I want to move to the cloud, "because I want to run BIA against it. "I want to do something that helps me "monetize my data in the cloud. "That data set, I want to move." One, you can run a query against that database. Two, we'll intelligently and efficiently only move that data, in native format. Spin it up in the cloud as metadata set. All your metadata's there. Do whatever you want to that data. When you're done, move it back if you want. Do whatever you want. So, essentially, we've eliminated any silos from a cloud standpoint. So what we've done is, we've given people complete cloud freedom to move what they want when they want, where they need to. That's the essence of what we've done. >> Let's talk about the monetize portion of-- cause, you guys have me curious. If I can move the data to the cloud natively, that's great. That's really value add, but on top of that, I need to figure out really tough problem, which is metadata. I have global data, worldwide. I have data scientists wanting to pound against that in a completely new way. Do you guys provide a new way to access this data other than my legacy tools? >> Absolutely, Keith. So I really hit on those two points in the statement you made. Moving data efficiently, Keith, is a very hard problem. What we have done by being, only protecting what you need to protect, why back up an entire database when you only care about a couple of tables? Remember, we're going from traditional monalithic architectures to micro-services in the cloud, right? DBAs and augments, they only care about couple of tables. I want to run a BI query against certain part of the data. What we have fundamentally done, to the first part of your question, move data very highly efficient, which is 10x dedup of what data domain could do. We have significantly modified to be protected around that decon. The second piece around metadata question. What we've really done, Keith, in our, sort of, scale-out elastic data protection, to the tune of elastic compute and elastic storage, you need to extend that to elastic data management, is your metadata catalog can't back up, at the end of the day hasn't catalog. The golden nugget. >> Right. >> That catalog used to be siloed. If I had 10 media servers, I had that catalog siloed around that. >> Keith: No value met. >> No value met. >> Correct. >> Our catalog log is now distributed, stretched across cloud boundaries. If I have a Datos running on prim, and a Datos running on Amazon, those are two instances of the same software, two nodes, the metadata catalog can see each other. You back up here. John can see that backup in the cloud. He can spin up his sequence already in the cloud. You couldn't do that past. You couldn't do that back in the old world. The golden nugget. You need to stretch your metadata catalog and you need to make it distribute it across cloud boundaries, which is fundamentally what-- >> What's the impact to the application developers, because now, are you freeing up-- What is the ultimate value to the customers? I mean you're basically freeing up the hassles for the app developer to say, "whatever?" Give us the bottom line. >> So, you know, absolutely John. Look, I'll give you a customer's real scenario, okay? A world's leading e-commerce platform where we go, and wife's go spend a lot of money buying clothes, so I'm just going to leave it at that, right? They are moving from a monolithic architecture, the Oracle DB2, to the cloud-native architecture. Application developers want to take their CICD. I'm writing new code, I want to bring new catalog items on the website. I want to test my code changes, and I want to go from the data, not two days ago, which was the old backup world, every day you bring a backup. Now they want what we call, to your question of we don't call it backup, what we call it versioning. I want a version one hour ago, because I want to test my code changes. I want to deploy those code changes on the e-commerce platform driving a billion dollars in revenue, so-- >> So you're enabling more and more coolness with the developer from a data, stale verses fresh data. I mean to certain levels, I mean not-- >> But I want to jump on that as well, because the thing that sometimes goes over looked is that, one of the things that the cloud has done that people sort of don't always acknowledge, is it's created, we've pushed the silo problem from on-prim to the cloud. Clouds don't talk to each other. You know, the notion of that. So the notion of the universal file system, such as the cloud, which some of the competitive landscape tries to-- >> John: Wait a minute. We're supposed to have multi-clouds. >> Yeah we're supposed to, but no. To your point, we do have multi-cloud. But its amazing how difficult it is to deal with that. So to your point-- >> In the future they might be talking to each other, but today they're not. >> But, but, and my point is that we enable you to do that. So, the ultimate value to the customer? I'm the marketing guy, yes, but the notion of cloud freedom is a direct business value to the customer-- >> John: So that's legit from your standpoint. Cloud freedom... >> Put it where you need to put it, when you want to put it there. Bring it back when you want to bring it back. So, from an app standpoint, a lot more flexibility. A lot more agility in terms of app development. From a cost standpoint, from an IT standpoint, I can dramatically reduce my cost, cause I can leverage the cloud versus having everything on prim. From an operational standpoint, I ensure everything's protected, so-- >> And we know cloud-native developers are very, like, they won't tolerate a lot of the old baggage and dogma of IT. >> Peter: Right, right. Are ya freakin' kidding me? >> Tarun: Well, well all-- >> Peter: That's actually, can I take that one? >> Tarun: Please, please. >> That's actually a good-- >> You see how fired up he is? >> I don't know how many hours we have to talk on The Cube because that's a fascinating topic. >> Just pause. Can I pause you for a second? >> Yes. >> That's only 30 days since he left EMC. (laughter) >> Alright, alright. Anyway, the point is, but the problem is new, but there is a persona, what I refer to as basically like a persona innovator's dilemma, that we're also helping address, because there's a convergence of personalities of people involved in the protection and management of data. So, to your point, we've been dealing with a lot of the new personas going after cloud-native data protection, but you're watching the organizations. The enterprises, they're going through it and they are rapidly transforming these personas. So, part of our jobs, to your education point earlier, is making sure that the left hand knows what the right hand is doing,% and marrying those two different pieces. That's ultimately, and that's value to the customer, and we help drive that process. >> Well, Tarun and Peter, congratulations, and good to see the journey continuing to accelerate. >> Thank you. Thank you. >> Entrepreneurial journey, and we'll keep in touch. Love the name, Datos OS. We believe, and Wikibon believes, and they're firm on this, that the business value of data is ultimately going to be a major, major disruptor for business. Not necessarily technology, but having that data operating system, that Datos, as you call it, is going to be fundamental. Congratulations. >> Thank you, John. >> Just keep it live here at Dell EMC World 2017. More live coverage, stay with us. More after this short break. (upbeat music)

(The Cube Theme) >> Voiceover: Live from Silicon Valley, it's the Cube, covering Google Cloud Next '17. >> Hey, welcome back here, and we're here live in Palo Alto for a special two days of coverage of Google Next 2017. I've John Furrier here in The Cube. We have reporters and analysts on the ground who are calling in, getting reaction on all the great news, and of course, Google's march to the enterprise cloud really is the big story, of course, they have their cloud they've been powering with their infrastructure and it had great presence, powering their own stuff, just like Amazon.com had Amazon webservices, Google Cloud now powering Google and others. Diane Green, new CEO, taking the reins, making things happen, we covered that news, and for an entrepreneurial perspective we have Tarun Thakur who is a co-founder and CEO Datos.io, former entrepreneur at Data Domain, been in the business, newly funded, Series A entrepreneur funded with True Ventures and Lightspeed. >> That is correct, John, thank you. >> Thanks for coming on. Tell us what you guys do first. Explain what you guys as a company are doing. >> Absolutely. I'd love to first thank you for the opportunity. It's a pleasure to be here. About Datos, I'll sort of zoom out a little bit and if you really see what's really happening out in the industry, our founding premise, me and my co-founder, Prasenjit, our founding principle is very simple. There are some transformative changes happening in the application era. I was just listening to Akash talk rom SAP, and enterprise workloads are moving to the cloud. That was our founding premise, that not only do you not have those IOT workloads, these SAS workloads, the real time analytics workloads, being born in the cloud, but you have all these traditional workloads that are moving as fast as they can to the cloud. So if you really look at that transformative change, we have a very simple founding premise: applications define the choice of the IT stack underneath it. What do we mean by that? The choice of the database, the choice of the storage, the choice of all the data management tooling around it, starting with protection, starting with governance, compliance, and so on and so forth, right? So if the application workloads are under disruption, and they're moving to the cloud, the impact it has on the IT stack underneath is phenomenal. >> So Tarun, you guys had a great write-up in the Register, Chris Miller, who is well known in the story, 'cause we all follow him, he's a great guy, and very fair, but he can be critical, too, he's very snarky. We like his columns. He called you guys the Tesla of the backup world. What does he mean by that? Does he mean it like you have all the bells and whistles of a modern thing, or is there a specific nuance to why he's calling you the Tesla of the backup world? >> No, this is excellent, John. You know, we are fortunate and we're honored. >> Electric backup? I mean, what's happening here? (laughing) I mean, what does he mean by that? What's the meaning? >> Couldn't have given us a better privilege than what he gave. Had a chance to host him in the office, small office, much smaller than what you have here, in December, and a 45 minute session became a two hour session and really he dug into why the Tesla, and essentially it goes back to, John, you had the traditional workloads running on your traditional databases, classical scale-operational databases like Oracle and SQL. Now, you're dealing with these next generation, hyperscale distributed applications. IOT real time analytic is building on that team, those are being deployed fundamentally on distributed architectures. Your Apache Cassandra, your Amazon Dynamo DB, your Google Spanner, now that we're talking in the context of Google Cloud Next, right? When you look at those distributed architectures, there's so much fundamental shift. You don't run them on shared storage, you don't have media servers anymore in the cloud- >> You have the edge. You have the edge out there. >> You have the edge computing. Given all those changes, you have to fundamentally rethink of backup, and that's essentially what we did. Just going back to Tesla, Tesla was started with a fundamentally seminal architecture. >> So you thought this from the ground up. That's essentially one point, and the other one is that it's modern in the sense of it's really taken advantage of the new architecture. >> That's absolutely right, you know, when we started, again, back in June of 2014, we really started with the end in mind, ten years, the next ten years ahead of us, and the end in mind was, "Look, it's going to be distributed architectures, "it's going to be your hyperscale applications, the webscale applications, and you need to be able to understand data and protect it and recover it and manage your data at that scale. >> Okay, so you guys are also Google partners, so you have an interesting perspective. You're on the front lines, Series A entrepreneur, you haven't cleared the runway yet. You still have to prove yourself. The game is just starting; you don't end it with the financing. That's just validation for the vision and the mission, and you've had some good press so far from Chris, now as you execute, you have a partner in Google. What's your analysis of Google, and as someone who's close to them, certainly as an entrepreneur, you're nimble, you're fast, you understand the tech, you mentioned Spanner, great horizontal scale of opportunity, but some of the enterprises might be a little slower, and they have different orientation, so help us understand what's Google doing? What's their main focus? >> I'll give you an answer in three part series. Number one, we are, again, a start-up, seriously, as you said, we have a lot ahead of us, even though we've been out here for three years, it feels like yesterday. (laughing) >> John: It's a grind. >> It is a grind, but to partner Google Cloud, one of our key marquee customers, a Fortune 100 home improvement retailer, under NDA, cannot take their name out of respect. >> John: Well the register says Home Depot. (laughing) >> Okay. >> Okay, so- >> I'll let Chris do the honor, but it's a Fortune 100 home improvement retailer, John, and their line of business, their entire e-commerce platform, the CIO down has moved their entire platform, migrated from DB2 to Google Cloud. It's not running on DB2 on Google Cloud platform, it's running all on a distributed massive scale- >> So did they sunset DB2 or did they completely- >> Tarun: Completely migrated away from DB2. >> Okay. >> It's part of the digital transformation journey Home Depot is at. They are three years in, they have two more years to go, and as part of the digital transformation journey they're on, they are now running their e-commerce website, which, think of you and I going to Thanksgiving and buying your home tools, and that application runs on a highly scalable Apache Cassandra database on Google Cloud. Now, second part, going back to large-scale enterprises, Home Depot, being how progressive they are, they understood cloud does not mean recoverability. Cloud gives me the scale, cloud gives me the economics, cloud gives me the availability, but it doesn't give me the point in time, and I need myself to be covered against that "what if" moment. We have hold-the-delta moments, we have hold-the-gitlack moments, SalesForce.com down with that human error, right? You don't want to be in that position as a Home Depot. >> You mean Amazon went down? >> Tarun: And Amazon. >> Yeah, Amazon went down. >> And if you read the analysis, the analysis was, "We're sorry guys, there was a human error. "Somebody was meant to change this directory; "he changed that directory." >> So this is a whole new game. One of the fears that the enterprises have is that in a new architecture, besides security, which is a huge issue, we'll have another segment on that shortly, but is that I want to leverage the capabilities of the partner in the cloud, because manageability, certain things, I don't want to build on my own, and so I can see you guys being a new modern piece because the data piece is so important because I'm storing at the edge, I'm not moving data around, so there's no data in motion as much as it is on premise. Is that a big part of this? >> It is, from a, I'll zoom out again, from a CIO perspective, we pitched this to about 100+ CIOs so far. From there it is truly, and I hate to use this word, but it's truly a multi-cloud world, John. They have invested in private clouds and an on-prem infrastructure that ain't going anywhere anytime soon. They are moving some of their SAP instances to a CenturyLink, MSPs, the managed service providers, but they know, as a CIO, I have my application developers and I have my lines of businesses- >> John: And they have their operations guys, too. >> Who want to go as fast as they can. I'll come back to the operations in a second because you'll be very surprised to hear this, but again from a CIO down, he wants to make his application developers to go as fast as they can, and he wants the lines of business just to go open up the next applications- >> John: Because that's top-line revenue right there. >> That's top-line revenue right there. So they want scale, they want agility, but they don't want to sacrifice that insurance piece. Going back to the IT ops and the dev-ops and the classical ops, you'll be surprised, we've been working with this team, our lead-in to the Fortune 100 home improvement retailer was a line of business, but right now it's all about their core IT team. Their IT ops team, the database admins, the database ops people, they are the ones who are really running this product day-to-day, day in and day out, and scaling it, and using it at the pace they need to. >> What's the big misconception, if you could point to, about Google, because one of the things we're trying to surface is that Amazon and Google, it's not apples to apples comparison, they're different clouds, and it is multi-cloud, I want to get you to that question today, but we can get to that in a second, what your definition of that means, but for now, what is the big misconception in your mind, people might misconstrue with Google? >> That's a great question, John, and I was hearing your previous interview with Akash, and again, I'll give you our partner-centric view; a young start-up built something disruptive for that platform. We got Amazon as the first platform. We have a good set of customers running on Amazon, and of course, this home improvement retailer took us to Google Cloud, "Hey guys, if you want to work with us, "you have to support Google Cloud." We went to Google Cloud, and the amount of pull that we got from Google Cloud folks to make it happen in less than three months was phenomenal. They didn't stop at that. They brought their solution architect team, Google Cloud, wrote a paper about Datos, their team, and posted it on their website. "How to use Datos on Google Cloud." Fascinating. Amazon has never done that. It, again, speaks to if you see all the announcements that came out yesterday, Google Cloud has been a significant- >> Well Google's partnering, Google's partnering, one of the things that came out of today's news that has been teased out is Diane Green said in the keynote, "I like partnering." She used the word, "I like partnering," meaning Google, and she has that DNA. She's from VM, where she knows the valley game, she understands ecosystems. She also likes to work on some cool stuff, which could be a double-edged sword. She's always been innovating. But Google has the tech, and she knows enterprise, so they're marching down that road. What areas would you say Google needs to sharpen up a little bit to kind of move faster on? I mean, obviously there's no critique on them; they're pedaling as fast as they can, but in the areas you think they should work on, is it security, is it the data side, what are the things that you think they've got to pedal a little faster on. >> I would definitely start with enterprising touch. I think they need to really amp up the game around enterprise. >> John: You mean the people, the process? >> The people, the processes, the onboarding, the deployment, giving them the blue templates, giving them reference architectures, giving them, hand ruling them a little bit, and I think that'll go a long ways- >> John: The basic enterprise motions. >> Yes, you need that. You're a cloud; that doesn't mean my database guy is not going to need the help of a Google Cloud admin to help me onboard. They need that wrap-up. From their point on they build phenomenal scalable services. Snap invested two billion dollars in Google Cloud. They understand- >> And Amazon got the other half, but- >> The underlying infrastructure is there. >> Yeah but this is the thing. The problem that, the problem is that there's two perspectives of what we see. One is people want to run like Google in the sense of how they're scaling, but not everyone has Google-like infrastructure, so I think Google has to kind of, they want the developers, in my mind, they get a A+ there, with open source, what they do with Kubernetes and whatnot, the operational orientation is something they've got to work on, SLAs are more important than price. >> Managing the orchestration piece, giving them the visibility, letting them come on and come off, and going back to multi-cloud, I'll tell you again, the same customer took us to a use case, which is so fascinating, John. They want on-prem backup and recovery. Remember, protection is the Trojan horse. Protection, it all starts with protection. >> It's always one of those things that's always been front and center. You saw that. It used to be kind of a throw-away thing. "Oh, what about backup? "Oh, we didn't factor in." Now it's front and center, certainly cloud is going to be impacted because data's everywhere. Data's going to be highly frictionless. Okay, question, and final question on this piece, where we talk about what you guys are doing, what does multi-cloud mean, or two questions: what is the definition of multi-cloud, and what does cloud-native mean to you? Define those terms. >> Absolutely. Those two terms are very, very close to us. So multi-cloud, I'll begin with that. I'll give you a customer use case that will hopefully ground the conversation. A multi-cloud essentially means from a customer perspective, I'm going to run on-prem infrastructure, I want to be able to recover or manage that data in the cloud, I don't want to make multiple copies, I don't want to duplicate data, I want to recover a version of that data in the cloud, why? Because I have my application developers who want to test staff. I want my DR to be in a different cloud. I do not want to put all my eggs in one basket. So again, it is truly- >> John: It's a diversity issue. >> It is, and they want multiple-use cases to be spread across clouds. Some clouds have strength in DR, some clouds, like Amazon, have strength in orchestration, and onboarding, and some cloud platforms like Google Cloud have strengths in, hey, you can bring your application developers and you don't have to worry about retail. Some of the retailers, like Gap, like Safeway, like eBay, those guys will hesitate to go to Amazon because they know Amazon, at the heart, is a retail business. >> So conflict there. Now, cloud-native. Define cloud-native. >> Cloud-native, to us, is you have Oracle running that database natively within the services of the cloud. For example, take Amazon Dynamo DB. It's a beautiful example of a cloud-native service. You don't run Dynamo DB on-prem. It was built ultimately for the cloud. Cloud Spanner, another example of cloud-native. It is built for that infrastructure, floor ground up, and has been nurtured for the last ten years for the elastic infrastructure. >> Alright, Tarun, great to have you on. Quick plug for what you guys are doing. What's next? You got the Series A, you're getting customers, you got a big customer you can't talk about, but it's in the Register article, Home Depot. What other things are you working on? What's the key priorities? Hiring? You've got some new announcements coming up I hear. Rumor mill, I won't say who they are, but you're partnering. What's the key focus? What's your key objectives? >> No, we only stay focused on building, and as you early on said, it's still early for us. We want to stay focused on getting customer acquisition, customer momentum, deploying those customers, making them happy customers, having them become referenceable customers for us, and of course, the next big focus for me personally is going to be bringing some of the people in the team, some of the people who can help me scale the company- >> John: Engineering- >> Engineering, marketing, business development, sales, go to market, so that's going to be second we're to focus, and third, and again, you'll hear the announcement coming very quickly, we're going to be partnering with some of the leading enterprise infrastructure companies, both on their enterprise traditional storage companies, and some of the leading, I'm just going to leave it at that. >> And True Ventures is the seed investor and Lightspeed on the Series A, the True company on the Series A with them. 'Cause they tend to follow, they don't leave you hanging. >> Yeah, Puneet is excellent. I love him. >> Yeah, John Callahan's company's got great stuff. And they had some great eggs, they had FitBit and they've got a lot of great stuff going on. >> Well they're excellent, excellent pro-entrepreneur people. Great to work with as well. >> High integrity, great people. Tarun, thanks for coming on and sharing the entrepreneurial perspective, the innovation perspective, certainly as a Google partner, good to have your reaction and analysis. >> Thank you, John. >> It's The Cube, bringing you all the action from Google Next here in our studio. More Google Next coverage after this short break. (The Cube Theme)