>> Narrator: Live from San Jose, it's theCUBE. Presenting: Big Data Silicon Valley. Brought to you by SiliconANGLE Media, and its ecosystem partners. >> Welcome back, everyone, we're here live at San Jose for Big Data SV, Big Data Silicon Valley. I'm John Furrier, cohost of theCUBE. We're here with two great guests, Jaspreet Singh, founder and CEO of Druva, and Jake Burns, VP of Cloud Services of Live Nation Entertainment. Welcome to theCUBE, so what's going on with Cloud? Apps are out there, backup, recovery, what's going on? >> So, we went all in with AWS, and late 2015 and through 2016 we moved all of our corporate infrastructure into AWS, and I think we're a little bit unique in that situation, so in terms of our posture, we're 100% Cloud. >> John: Jaspreet, what's going on with you guys in the Cloud, because we've talked about this before, with a lot of the apps in the cloud, backup is really important. What's the key thing that you guys are doing together with Live Nation? >> Sure, so I think the notion of data is now pretty much everywhere. The data is captured, controlled in data center, now it's getting decentralized into getting into apps and ecosystems, and softwares and services deployed either at the edge or in the Cloud. As the data gets more and more decentralized, the notion of data management, bead backup, BD discovery. Anything has to get more and more centralized. And we strongly believe the epicenter of this whole data management has to move to Cloud. So, Druva is a size based provider for data management. And we work with Live Nation to predict the apps not just in the data center. But, also at the edge and also the Cloud data center. The applications deployed in the Cloud, be it Live Nation or Ticketmaster. >> And what are some of the workloads you guys are backing up? That's with Druva. >> Yeah so, it's pretty much all corporate, IT applications. You know, typical things you'd find in any IT shop really. So, you know, we have our financial systems and we have some of our smaller ticketing systems and you know, corporate websites. Things of that nature. So, it's like we have 120 applications that are running and it's just really kind of one of everything. >> We were talking before we came on camera about the history of computing and the Cloud has obviously changed the game. How would you compare the Cloud as a trend relative to operationalizing the role of data and obviously GDPR, Ransomware. These are things that now with the perimeter gone. There's worries. So now, how do you guys look at the Cloud? So Jake, I will start with you. If you can compare and contrast, where we have come from and where we are going. Role of the Cloud. Significant primary, expanding. How would you compare that? And how would you talk to someone who says Hey I'm still in the data center world? What's going on with Cloud? >> Well, yeah, it's significant and it's expanding, both. And you know, it's really transforming the way we do business. So you know just from a high level, things like shortening the time to market for applications, going from three to six months just to get a proof of concept started to today, you know, in the Cloud. Being able to innovate really by trying things trying to... we try 20 different things, decide what works, what doesn't work. And at very low cost. So, it allows us to really do things that just weren't possible before. So, also, we we move more quickly because, you know, we're not afraid of making mistakes. If we provision infrastructure and we don't get it right the first time, we just change it. You know, that's something that we would just never be able to do previously in the data center. So to answer your question, everything is different. >> And as a service model's been kind of key. Is the consumption on your end different like I mean radically different? Like give an example of like how much time would be saved or taken to use other the traditional approaches. >> Oh for sure. You know, in the role of IT has completely changed because you know, instead of worrying about nuts and bolts and servers and storage arrays and data centers. You know, we could really focus on the things that are important to the business. You know, those things delivering results for the business. So, bringing value, bringing applications online and trying things that are going to help you know, us do business rather than focusing on all the minutiae. All that stuff's now been outsourced to Cloud providers. So, really, we kind of have a similar head count and staff. But, we are focused on things that bring value rather than things that are just kind of frivolous. >> Jaspreet, you guys have been very successful startup growing rapidly. The Cloud been a good friend that trend is your friend with the Cloud. >> What's different operationally that you guys are tapping into? What's that tail wind for Druva that's making you guys successful? And is it the ease of use? Is it the ease of consumption? Is it the tech? What's the secret to success with Druva? >> Sure, so, we believe cloud is a very big business transformation trend more than a technology trend. It's how you consumer service with a fixed SLA, with a fixed service agreement across the globe. So, it's ease of consumption. It's simplicity of views. It's orchestration. It's cost control. All those things. So, our promise to our customers is the complexity of data management, backups, archives, data production, which is a risk mitigation project. You know, can be completely abstracted by a simple service. For example, you know, Live Nation consumers, consumer drove a service through Amazon Marketplace. So, think about consuming a critical service like data management through simplicity of marketplace, pay as you go, as you consume the service. Across the globe. In the US, in Australia, and Europe. And also, helps the vendors like us to innovate better. Because we have a control environment to understand how different customers are using the service and be able to orchestrate better security pusher, better threat prevention, better cost control. DevOps. So, it improves the pusher of the service being offered and helps the customer consumer. >> You both are industry veterans by today's standards unless you're like 24 doing some of the cryptocurrency stuff that, you know, doesn't know the old IT baggage. How would you guys view the multi-Cloud conversation? Because we hear that all the time. Multi-Cloud has come up so many times. What does it mean? Jake, what does multi-Cloud actually mean? Is it the same workload across multiple Clouds? Is it the fact that there is multiple Clouds? Certainly, there will be multiple Clouds? But, so, help us digest what that even means these days. >> Yeah, that's a great question and it's a really interesting topic. Multi-Cloud is one of those things where, you know, there's so many benefits to using more than one Cloud provider. But, there are also a lot of pitfalls. So, people really underestimate the difference in the technology and the complexity of managing the technology when you change Cloud providers. I'm talking primarily about infrastructure service providers like Amazon web services. So, you know, I think there's a lot of good reasons to be multi-Cloud to get the best features out of different providers, to not have, you know, the risk of having all your data in one place with one vendor. But, you know, it needs to be done in such a way where you don't take that hit in overhead and complexity and you know, I think that's kind of a prohibitive barrier for most enterprises. >> And what are the big pitfalls that you see? Is it mainly underestimating the stack complexity between them or is it more of just operational questions? I mean what is the pitfalls that you've observed? >> Yeah, so, moving from like a typical IT data center environment to public Cloud provider like AWS. You're essentially asking all your technical staff to start speaking in a new language. Now if you were to introduce a second Cloud provider to that environment, now you're asking them to learn a third language as well. And that's a lot to ask. So, you really have two scenarios where you can make that work today without using a third party. And that's ask all of your staff to know both and that's just not feasible. Or have two tech teams. One for each Cloud platform. That's really not something businesses want to do. So, I think the real answer is to rely on a third party that can come in and abstract one of those Cloud complexities Well, one of those Cloud providers out. So, you don't have to directly manage it. And in that way, you can get the benefit of being multi-Cloud, that data protection of being multi-Cloud. But, not have to introduce that complexity to your environment. >> To provide some abstraction layer. Some sort of software approach. >> Yeah, like for example, if you have your primary systems in AWS, and you use a software like Druva Phoenix to backup your data and you put that data into a second Cloud provider. You don't have to an account with that second Cloud provider. You don't have to have the risk of associating without a complexity associated without that is I think is a very >> And that's where you're looking for differentiation. We look at venues, say hey don't make me work harder. >> Right. >> And add new staff. Solve the problem. >> Yeah, it's all about solving problems right? And that's why we're doing this. >> So, Druva talk about this thing. Because we talked about it earlier about To me we could be oh we're on Azure. Well, they have Office 365 of course they're going to have Microsoft. A lot of people have a lot going on and AWS. So, maybe we're not there at the world where you can actually use provision across Clouds, the same workload, It would be nice to have that someday if it was seamless. But, I think that's might be the nirvana. But at the end of the day, an enterprise might have Office 365 and some Azure. But, I got some mostly Amazon over here I'm doing a lot of development on and doing a DevOps, and I'm on-prim. How do you talk to that? Because that's like you got to backup Office 365, you got to do the on-prim thing, you got to do the Amazon thing. How do you guys solve that problem? What's the conversation? >> Absolutely. I think over time we believe best of breed will win. So, people will deploy different type of cloud for different workloads. Pete's has hosted IaaS or platform like PaaS. When they do that, when they host multiple services, softwares to deploy services. I think its hard to control where the data will go. What we can orchestrate or anybody can orchestrate is the centralizing the data management part of it. So, Druva has the best pusher, has the best coverage across multiple heterogeneous Cloud breed. You know. Services like Office 365, Box, or Saleforce or B platforms like S3 or Dynono DB through our product called Apollo or hosted platforms like what Live Nation is using through our Phoenix product line. So getting the breadth of coverage, consistency of policies on a single platform is what will make enterprises adopt what's best out there without worrying about how you build abstraction for data management. >> Jake, what's the biggest thing you see people who are moving to the Cloud for the first time? What are they struggling with? Is it the idea that there's no perimeter? Is it staff training? I mean what are some of the as people move from Test Dev and or start to put in production the Cloud? What are some of the critical things they should think about? >> Yeah, there are so many of them. But first, really, its just getting buy in, you know, from your technical staff because, you know, in an enterprise environment you bring in a Cloud provider it's very easily framed to hold as if we're just being outsourced right? So, I think getting past that barrier first and really getting through to folks and letting them know that really this is good for you. This is not bad for you. You're going to be learning a new skill, very valuable skill, and you're going to be more effective at your job. So, I think that's the first thing. After that, once you start moving to the Cloud, then, the thing that becomes apparent very quickly is cost control. So, you know, the thing with public Cloud is you know, before you had this really kind of narrow range of what IT could cost. Now with the traditional data center, now we have this huge range. And yes, it can be cheaper than it was before. But, it can also be far more expensive than it was before. >> So, service is sprawled or just not paying attention? Both? >> Well, you essentially you're giving your engineers a blank check. So, you need to have some governance and, you know, you really need to think about things that you didn't have to think about before. You're paying for consumption. So, you really have to watch your consumption. >> So, take me thorough the mental model of D duplication in the Cloud. Because I'm trying to like visualize it or grok it a little bit. Okay, so, the Cloud is out there, data's everywhere. And do I move the compute to the data? How does the backup and recovery and data management work? And does D Doup change with Cloud? Because some people think I got my D Doup already and I'm on premise. I've been doing these old solutions. How does D Doup specifically change in the Cloud or does it? >> I know scale changes. You're looking at, you know, the best D Doup systems, if you look historically, you know, were 100 terabyte, 200 terabyte, Dedup indexes, data domain. The scale changes, you know, customers expect massive scale in Cloud. Our largest customer had 10 perabyte in a single Dedup index. It's 100x scale difference compared to what traditional systems could do. Number two, you could create a quality of service which is not really bound by a fixed, you know, algorithm like variable lent or whatever. So, you can optimize a Dedup very clearly for the right workload. The right Dedup for the right workload. So, you may Dedup off of 365 differently than your VMware instances, compared to your Oracle databases or your Endpoint workload. So, it helps you that as a service business model helps you create a custom, tailored solution for the right data. And bring the scale. We don't have the complexity of scale. But, to get the benefit of scale. All, you know, simply managing the cloud. >> Jake, what's it like working with Druve? What's the benefit that they bring to you guys? >> Yeah, so, specifically around backups for our enterprise systems, you know, that's a difficult challenge to solve natively in the Cloud. Especially if you're going to be limited to using Cloud native tools. So, it's really it's a really perfect use case for a third party provider. You know, people don't think about this much but in the old days, in the data center, you know, our backups went offsite into a vault. They were on tapes. It was very difficult for us to lose those or for them to be erased accidentally or even intentionally. Once you go into the Cloud, especially if you're all in with the Cloud, like we are. Everything is easier. And so, accidents are easier also. You know, deleting your data is easier. So, you know, what we really want and what a lot of enterprises want. >> And security too is a potential >> Absolutely, yeah. And so, what we want is we want to get some of that benefit, you know, back that we had from that inefficiency that we had beforehand. We love all the benefits of the Cloud. But, we want to have our data protected also. So, this is a great role for a company like Druva to come in and offer a product like Phoenix and say, you know, we're going to handle we're going to handle your backups for you essentially. So, you're going to put it in a safe place. We're going to secure it for you. And we're going to make sure it's secure for you. And doing it software is a service like Druva does with Phoenix. I think is the absolute right way to go. It's exactly what you need. >> Well, congratulations Jake Burns, Vice President in Cloud services. >> Thank you. >> At Live Nation entertainment. Jaspreet Singh, CEO of Druva, great to have you on. Congratulations on your success. >> Thank you. >> Inside the tornado called Cloud computing. A lot more stuff coming. More CUBE coverage coming up after this short break. Be right back. (electronic music)

>> Narrator: From the SiliconANGLE Media office in Boston, Massachusetts, it's the Cube. Now here's your host, Dave Vellante. >> Hi everybody, welcome to this special Cube conversation with a practitioner, a real-world enterprise journey to the Cloud. I'm here with Jake Burns, who's the Vice President of Cloud Services at Live Nation Entertainment, in from L.A. Jake, thanks for coming in to our Marlborough Studio, appreciate you having in. >> I'm glad to be here. >> So tell me about your role. >> So, I'm head of cloud services for Live Nation, and what that means is, me and my team are in charge of infrastructure for IT, including cloud infrastructure, as well as the move to the cloud, which we completed early 2017, enterprise messaging, which includes e-corporate email, DNS, database services, and storage management. >> So, recent journey. How did it start? Was it a top-down push, did you go to management and say, "Hey, we got to do this," describe that dynamic. >> Yeah, so it started off as kind of a bottom-up push. >> Dave: Really? >> For a number of years I've been really wanting to get us involved in public cloud, at least in some level. But, it really didn't hit critical mass until our CEO, late 2015, had a mandate that we're going to move 100% to cloud, and modernize all of IT. And that's when we really hit the ground running. >> Why did, from a bottom-up standpoint, why did you guys want to do that? Was it because cloud's cool, that's where all the action is, the developers want to be there, or was it something else? >> We spent a lot of time managing infrastructure and data centers, and it's just not part of our core business. We wanted to focus more on satisfying the business, and providing value to the business. And, our time could be better spent really helping solve their problems, rather than deal with hardware and systems. Another thing is just business agility in general. If we want to stand up a new system, the typical lifecycle could be three to six months, just to get an application up and running. With cloud, we can do that in days, weeks, worst case. So, being able to respond quickly to business needs is something that's really important to us, and we saw with public cloud that we could do that a lot more efficiently. >> And when you think about the early cloud days, the rhetoric was all about agility, and it actually, that really was the main business benefit. You guys of course saved a lot of money too, and I want to get into that, but how did you get started? It must have been, kind of a little nervous, like the first time you jumped off a high cliff or something. Right, because you have an existing business to run, and yet you're going to migrate everything. Migrate's like this evil word, so how did you get started? >> For us, we realized very early on that this was a big technology change for us, and it was going to require new skills that we didn't have, so the first thing we did, was we really just got training across the board. We brought trainers from AWS to our offices, and we did every training program that they offered. Got the certifications. And made sure that we really understood what we were dealing with before we got started. So that was really step number one. >> And how did that go? Were they really supportive? Everybody says AWS, really not hands-on, they just send me an email. How did that go? >> In the beginning, there's resistance. Just like all projects like this, people are concerned they're going to lose their jobs. >> Dave: Resistance from your guys. >> Oh, yeah, yeah- >> Not the AWS people, they were- >> Oh, no, of course, right. No no, our guys, before they really understand the situation, it looks like we're being outsourced. We're moving all of our infrastructure. This is our job. We're managing hardware, we're managing servers, we're managing data centers, and all that stuff's going to go away, so what are we going to do, right? So, really, even before the training, the priority for me was to get people to understand that this is not something that's a danger for your career. Quite the contrary. This is going to make you more valuable. You're going to get trained on this technology. You're going to get real world experience, moving a Fortune 500 company to the cloud, and at the end of this, someone is going to need to maintain it. So not only will you have job security, but you're probably not going to care about job security at the end of this, because you're going to be so valuable in the marketplace. >> So, we're all in sales, aren't we? So you had to sell them a little bit on the concept, but then they responded positively, it sounds like. >> Yeah, and part of that is because it's the truth. I was telling them the truth, so it was an easy sell. But it's a very important component of any cloud migration project like this. If you don't have support from your people, it's not going to succeed. >> Okay, so you get through the training. Your guys are onboard, you have alignment there, and then take us through sort of the journey. How long did it take, what were some of the challenges that you faced? >> The target was 12 months to move everything, and we're talking about 668 servers, 118 applications, including Oracle, SAP, some really things that are not trivial to move to the cloud. We were able to move 90% of everything in 12 months, and then the long tail took an additional five months, so that's 17 months in total to move everything. >> And that long tail, was that the Oracle apps? >> Yeah, so our strategy was to move the easy stuff first, as we learned, because we learned along the way. We really didn't know what we were doing when we started. By the end of the project, we knew exactly how to do the project. >> Easy stuff like messaging? >> Like single server applications that are running supported software, where we have a business stakeholder that's cooperative. >> Dave: Web stuff? >> Yeah, like internal stuff, like our monitoring systems, things that we completely control. >> Dave: Things that were under the control of IT, didn't involve a lot of politics, and ... >> Jake: Exactly. >> Learn there, okay. >> Right, so the idea was, get real world experience moving live production systems on the easy stuff, and it kind of builds up our skillset, but at the same time it builds forward momentum, which is critical for a project like this. There's a lot of people that are just waiting for the first failure to kind of put a stop to the whole thing, right? There's a lot of skepticism as to whether this can even be accomplished or not. So, getting, I truly believe a key component for a project like this is to get momentum on your side early on, and the way you do that is by attacking the easy problems first, and then get progressively more difficult as you go along. And so at the end, you end up with the most difficult applications to move, but at that point, you have full buy in from everyone because you've been successful so far, and you and your team are practiced and accomplished, and have the skillsets necessary through moving all the more easy stuff before that. >> Okay, and just a quick aside, I have to ask. So, Oracle is kind of using licensing as a weapon, especially, there's this, I call it urinary Olympics, sorry, with Oracle and AWS. You may not have visibility on it, if you don't we can move on, but was that a concern? >> Absolutely, yeah. So this was a major problem that we've had to deal with, and Oracle doesn't make it easy. They don't necessarily want their customers moving to AWS. So, that was part of the challenge. Part of the challenge was, how do we move this without having to pay more in licensing? And what it really comes down to, is you have to make your Oracle databases run more efficiently in AWS, in order to lower the core count, which is what the licensing is based on, in order to keep your costs neutral, because Oracle will charge you double for your database, per processor, in the cloud in AWS than they will on prem. So, really the only way around that, besides negotiating with Oracle if you're able to do that, if you're not able to do that, then your only option is to make it run twice as efficiently from a processor standpoint. >> Thank you for sharing that with our audience. We've written a lot about ways to reduce your core count. Ways to make IO optimized, and if you can do that, you can actually save a lot of money. Maybe we'll have you back on at Reinvent, and we can talk more about that. But so, back to your story here. You got a huge budget to do this, right? Big bag of money to say, go move to AWS? >> Unfortunately, we didn't have that luxury. So, we run very lean. So we had essentially a flat budget, 2016, when we did the majority of these moves. So we just had to find a way to do it without spending money. And so, it was a bit of a juggling act. We were decommissioning systems in the data center, and canceling support contracts, so we were able to kind of use some of that money and repurpose some of that money for moving to AWS, but we really didn't have a budget for hiring consultants, or to buy expensive software, or anything like that. So, what we had to do was, basically become the consultants, to do the cloud migration. And so, that's where that training comes into play. So by training the team, and getting them up to speed, and essentially creating cloud engineers, we were able to be internal consultants to the business, perform the move internally at a very low cost. >> All within that sort of 12/17 month timeframe, you were able to affect that skills transition. >> Right, so we were simultaneously maintaining the old infrastructure, moving the infrastructure to AWS, and maintaining the infrastructure in AWS. So there were a lot of long hours. >> I'll bet. That's weekends. >> But, we were enthusiastic about doing it. Everyone was very excited once we got going, and so people were willing to do it. You talk about the people challenges. I think we've addressed that a little bit anyway. What were some of the other challenges? You got a reasonably sized application portfolio, you got data, you got your backup systems. What were some of the challenges that you faced, and how did you address them? >> Yeah, so that's a great question. One thing that people don't realize is that AWS isn't necessarily designed for enterprise applications. It's getting a lot better. But, there are some things where it just doesn't fit automatically. So, one area where that's especially true is with storage. AWS has a fantastic storage offering, especially with S3, their object storage. But unfortunately, most enterprise applications, they can't utilize. Legacy enterprise applications won't utilize object stores, they want block storage. >> They don't want get put, they want block storage, okay. >> Yeah exactly. And then the block storage in AWS is different than the block storage than what you're used to in the data center, typically. So, kind of allowing these applications, like Oracle, to work on AWS's block storage can be a challenge. It can be expensive, and there can be some risk there, just because of the way that it works. So, this is where using a third party makes sense. This is one of the rare circumstances where I think using a third party makes sense. We found a company called Actifio that does virtual storage in AWS, and one of the great things about this product is it essentially mimics the way that the old storage worked in our old environment, in our data center. So the application continued to function. So we're able to take snapshots, we're able to clone environments, we're able to do all of these things that we are not able to do in AWS natively, with the Actifio product. And it saved us a lot of money, and allowed us to avoid a lot of having to change our workflows to get around some of the delays with doing snapshots and stuff natively. >> And is your strategy to have this sort of hybrid approach between on prem and public cloud, or multiple public clouds? Is that part of the strategy, and how does this capability fit into that? >> Yeah, it's a great question. Our initial strategy was 100% going all in with AWS, and officially that's still our strategy. I am a proponent of multi-cloud in certain circumstances. For example, disaster recovery and backups, I think it makes sense, if your 100% in the cloud, to have a second cloud provider to hold your backup data, just so you don't have everything in one place. I think, for the same reason, hybrid cloud makes a lot of sense. And I think also hybrid cloud makes a lot of sense, just because not all applications are a good fit for a public cloud, and Oracle, SAP, would be two of those examples. Now we were forced to move everything to AWS, and it was a fun challenge, and we were able to accomplish that. But doing it over again, if we had the option of doing hybrid cloud, there may be a couple applications that I would say keep it on prem, because it just works better that way. >> And, can you double click on the storage virtualization capability that you talked about. Kind of how does that work, and how do you have to ... Were there any kind of things that you had to do to prepare for that? Any sort of out of scope expectations that customers should be aware of? >> With Actifio it's a pretty turnkey solution. So, there's a little bit of a learning curve, but there's a learning curve with using the AWS native tools as well. So I would say probably less of a learning curve if you use a product like Actifio, because it's more familiar to the people that are already working on these systems. So if you have existing staff, and they're used to doing things in the data center, and they're used to doing things with traditional enterprise storage, the Actifio tools is going to look a bit more familiar than the AWS tools. So, there's a learning curve either way, but I would say look at a product like Actifio if you're an enterprise trying to do this. >> So what was the business impact of using Actifio? Then I want to ask you about the whole move to AWS. Did it speed the time to deployment for AWS? Did it help you cut cost? What was the business impact? >> Unfortunately, we didn't become aware of this product until after we had moved. So, we're in the process now of replacing some of our storage devices with virtual storage with Actifio. But I wish we had found this product sooner. I advise anyone who's new at this, anyone who's doing a migration, to leverage something like this to actually move their data, because it's a much more efficient way to do it. So, if I could go back in time, I would do that. >> What would have been the business impact? Is this time and money? >> Yeah, time and money, for sure. So, the moving of the data is one of the biggest challenges that you're going to have moving to cloud. We had a petabyte of data that we had to move, and that's no small task to get that moved in 12 months. So, any tool that you can use that can make that more efficient, is going to shorten the amount of time you're going to be doing the migration. And, consequently, shorten the amount of money that you spend doing the migration. Also it would have saved us a lot of time, because now we're going back and having to change things, and put things under Actifio. If we would have done it like that to begin with, we wouldn't have to spend that effort after the fact. >> Why does Actifio make it more efficient? Is it data reduction? Is it automation? >> So essentially the biggest benefit is that it allows you to not have duplicates of your data. So, if you have a dozen or so copies of your database, for different types of environments, test, UAT, dev, etc., and you're duplicating those, and storing each one of those separately, you're going to pay for each one of those separately, and have to manage each one of those separately. If you're able to use virtual storage, then you really have one copy of the data, or however many copies of data you really need to be protected, and the rest of those can be virtual copies. And those don't cost you anything from a storage point of view. The other benefit is, if you want to clone an environment, or copy an environment, or take a snapshot of an environment, it can happen instantaneously, rather than wait for the hours or days that it would take to copy a large dataset. >> So it becomes the single point of control, with a catalog, and give you visibility over all your data, and your copies, and allows you to manage that, is that correct? >> Yeah, and the management becomes a lot easier, because you have software that's keeping track of your snapshots, and keeping track of all your copies of data, rather than try to track that all manually. >> Okay. Let's bring it back to the big AWS picture. So you move to the cloud. What was the business impact of that? You mentioned agility. Did you save money? How much? Maybe give us some visibility on that. >> Because we're so cost conscious, saving money was a priority. I don't think it's necessarily something to expect, especially initially, if you're an enterprise moving to the cloud. Cost shouldn't be the driver. Agility should be the driver. But, in our case, we were able to achieve 18% reduction in TCO, on year one. And, that's just because we were just very focused on cost. We're very cost sensitive, and it's very important for us to be efficient, and to not spend money unnecessarily. I know that's a priority for everyone, but it's a top priority for us. And so, my point is it can be done. You can move to the cloud. You can move 100% to public cloud if you're an enterprise, and you could make it cost neutral, or even favorable. It is possible. >> So you hear a lot of stuff in the press about how the cloud is very expensive. You could actually do it cheaper on prem. Based on your experience, you don't buy that. >> Well, I wouldn't say that's false. You can, in a lot of circumstances, do it cheaper on prem. It really depends on the workload. So I mentioned earlier that I think hybrid is probably the right approach for most people. So just because we're saving money by going 100% cloud, doesn't mean we wouldn't save more money if we went hybrid cloud, and put the more expensive things that run in cloud, on prem. So, because it's pay for what you use, the things that you very heavily utilize, those are good candidates to keep on prem. The things that are more bursty, those are the things that are better candidates to put in the cloud. The easiest things, candidates to put in the cloud, are disaster recovery and backups, those are no-brainers. DR because that's only something you need to scale up when you use it. So anything that you need to scale up when you use it, or anything that scales up and down, those are the best candidates for cloud. >> Okay, now I understand you're kind of an expert at cutting the AWS utility bill. Maybe you could give us some advice on how to do that, and how'd you learn how to do that? >> Yeah, so that's kind of my area of focus now, is now that we're in the cloud, getting those costs reduced as much as possible. So, there's a lot of ways to do this, but I like to keep it simple, and attack the things that have the biggest impact first. So, people like fancy solutions, but it's really simple. The biggest thing you can do is delete things you're not using. You're paying for consumption, so find things that are not being used, and simply delete them. After that, then find things that are oversized, and right-size them. And then, another big thing is, in the cloud, you have such an easy access to spin things up. To take snapshots of data, to copy data, and it's the classic problem in IT, where everyone requests what they want, and they never tell you when they're done with it. So, it needs to be a full-time effort, to be actively looking for resources that are unused. Snapshots that are no longer needed, volumes that are no longer needed, instances that are no longer needed, and be cleaning those things up on a continuous basis. I find that that's a large percentage of what my team does now, and that's one of the things that keeps our costs in line. >> That's interesting. We always talk here about GRS, getting rid of stuff. Not only did you get rid of a bunch of stuff when you moved in the cloud, you said 600 servers, you got rid of unused capacity, you got rid of a bunch of data, which must have made your general counsel happy, but you're now actively continuing to get rid of stuff. Like you said, it's volumes, it's snaps, and so the things, now you're in the cloud, that GRS mentality is sort of ingrained. >> It has to be. I think that anyone who's in the cloud for some time is going to realize this. You're going to have inflation of costs, simply by doing nothing. So, just to keep your cost neutral, you're going to have to be deleting things on a continuous basis. Now if you want your costs to go down, that's even more difficult. You have to be more aggressive with it. But, just as it's easier to spin things up in the cloud, the good news is it's easier to keep track of what you have, and find things that can be deleted in the cloud, because you don't have to go in the data center and track things down. Everything is virtual. It all can be automated. It's all done, it can be scripted. So, everything's easier. Spinning things up's easier. Cleaning things up is easier, you just have to make it a priority, and make sure it gets done. >> So, some of the financial people in our audience might be listening and saying, "Eh, you know, okay, year one. Roughly 20% savings. It's not that exciting." But we haven't quantified the sort of other business impacts in terms of agility, and that's a harder thing to quantify, but it's early days for you still. Do you expect to get on that S curve, and really start to see a major business impact, beyond that 17, 18%? >> That's a great question. That 18% reduction in TCO, that's just infrastructure costs, so that's not taking into account things like how long does it take for us to spin up an application, and what does that cost the business, that delay? We're not taking that into account. How about the opportunity cost of, we want to try something, but it's too expensive because we've got to buy servers, and we got to hire people to build the application, and install the operating system, all that kind of stuff. Those opportunity costs, they're not captured either. Now, we can try as many things as we want, very inexpensively, and only keep the things that work. So I think there's a lot of hidden cost savings, a lot of hidden value that's very difficult to capture. But, we certainly have those benefits, even if we're not articulating it, and counting it very well, the business feels it, and it's certainly a superior level of service. >> Well it's kind of like when we first got email. Nobody really quantified it, but the productivity impact was enormous. Or the first local area network that you ever installed, and the collaboration that that brought, it's one of those things that's, it's probably telephone numbers, but it's hard to quantify, right? You said the business people see it. Do the finance people see it as well, and are they supportive of this? >> Yeah, it takes a while I think for the non-technical teams to catch up, and really get to where we're at in terms of an understanding of what we're dealing with at this point. So, they're starting to see it. But, all the financial models have to change. All the budgeting needs to change. There's a lot of things that, beyond IT, this kind of transformation affects, and those processes have to change, and those processes generally change more slowly. So procurement needs to change, finance needs to change, security needs to change. Everything really, it's a new world. And once they catch up and kind of really grasp what we're dealing with, I think the whole business is going to be transformed. >> So two last questions. You talked about maybe things you'd do differently. Maybe some advice. But let's focus clearly on advice to your colleagues that are trying to do something similar, get to the cloud, what would you tell them? >> Invest in your people. Focus on cost savings day one. Don't look at doing that after the fact. And don't get too caught up in all the fancy methodologies, and fancy tools. Everybody's going to try to sell you something. Everybody's going to try to tell you they have the best way to do it. But, in general, those things are just going to add complexity to your project. I say keep it simple, keep it lean. Leverage your own people. Because at the end of the day, somebody's going to have to support this environment as well, and if you're relying too much on outside help, then they're not going to be there when it's all said and done. So, consider the endgame. Consider the end state, and how you're going to support that, because it's one thing to be successful migrating to the cloud, but then you have a whole new set of challenges after that. And you're going to have to live with that moving forward. And, I'm not saying it's a bad thing. It's a great thing. But it's something different, and you're going to have to be prepared for that. >> Own it. >> Jake: Own it. >> Yeah, okay. And then, last question, just sort of what's next for you guys? You're just sort of getting started here. You've made a tremendous amount of progress in a year and a half. What's next? Where do you want to take this thing? >> Like I said, right now we're really focused on cost optimization. I think that, like you alluded to earlier, the cloud could be very expensive. The range of how much it can cost is, it's amazing, right? So, this is uncharted territory. We don't know how expensive it should be, how cheap it should be. We just now that we can affect that, to a large degree. So I'm interested in seeing to what degree we can affect that, and I want to see how efficient we can make this. 18% favorable TCO is one thing. Let's see if we can get 30% or 40%. So, really I'm focused on optimizing for cost, security, which is a whole new world in the cloud, and going from there. >> Jake Burns, awesome having you on. Thanks very much for your insights. >> Jake: My pleasure. >> Really appreciate your time. And thank you for watching, everybody. This is Dave Vellante. We'll see you next time. (upbeat music)