(gentle music) >> Welcome back to our coverage here on theCUBE of AWS re:Invent 22. We are on day three, starting to wind down, but still a lot of exciting topics to cover here on the AWS Global Showcase, part of the startup program there at AWS. Joining us now, two representatives from LTI Mindtree. You say LTI Mindtree? I thought they were two different companies. Well, they're actually one and the same. Been together just a mere two weeks now. We'll hear more about that from Sid Bohra, who is the Chief Business Officer at LTI Mindtree and Ashish Varerkar, who is the Vice President of Cloud Success at LTI Mindtree. Gentlemen, thanks for being with us here on theCUBE. >> Pleasures all ours. >> Thank you. >> And congratulations. So two weeks in the making in its infancy, still in the honeymoon period, but how's the two weeks been? Everything all right? >> Well, two weeks have been very exciting. >> I'll bet. >> Well, I would say the period prior to that was just as exciting as you can imagine. >> John: Oh, sure. And we are super excited about what the future holds for this company because we truly believe that we have a remarkable opportunity to create value for our clients as one company. >> Well let's talk about LTI Mind tree then a little bit. Ashish, I'll let you carry the ball on this. Tell us about your services, about your core focus, and about those opportunities that Siddharth was just telling us about. >> So I think with the two companies coming together, we have a larger opportunity to like go to market with our end to end business transformation services and leveraging cloud platforms, right? So, and that's what we do. My responsibility particularly is to see to it that what customers are deploying on cloud is aligned to their business outcomes and then take it forward from there. >> Yeah, Vice President of Cloud Success, that gives you a lot of runway, right? Does it not? I mean, how do you define success in the cloud? Because there are a lot of different areas of complexity with which companies are dealing. >> So I think you would agree that in today's scenario, customers are not looking for a platform, right? But they're looking for a platform which can deliver business value. They're looking at business value and resiliency and then at the end, the cost, right? So if you're able to deliver these three things to the customer through the cloud implementation, I think that's success for us. >> Right. We've talked about transformation a lot this week and modernization, right, which is those are two pretty key buzzwords right now we're hearing a lot of. So when you see said, you know, companies come to you and they say, okay, it's time for us to make this commitment. Do they make it generally wholeheartedly? Is there still some trepidation of the unknown? Because there's a lot of, as we've said, complexity to this, it's multidimensional. We can go public, we can go hybrid, we can go multicloud. I mean, we got a lot of flavors. >> Yeah >> Absolutely. >> No, we see a spectrum. There are customers who are very early in the journey of getting onto cloud and are a little uncertain about what value they can get out of it. And on the other end of the spectrum, there are companies who are well into the journey who have understood what are the benefits of truly leveraging cloud who also understand what are the challenges they will face in getting onto the journey. So we get to meet a spectrum of customers, I would say. If you ask me where do bulk of them lie, I would say early in their journey. I would say there are only a handful who have that maturity where they can predict what's exactly going to happen on the cloud journey, what value they will accumulate through the process. So there's a lot of hand holding to be done, a lot of, you know, solving together to be done with our clients. >> You know, it is such a dynamic environment too, right? You have new opportunities that seem to be developed and released on a daily basis, almost, right? There's a large amount of flexibility, I would think, that has to be in place because where you think you're going to go today might not be where you wind up in six months. >> That's true. >> Is that fair? >> Absolutely fair. And I think from that perspective, if you look at the number of services that AWS provides, right? And what customers are looking for is how can they compose their business processes using this multiple services in a very seamless manner. And most of the announcements that we have seen during the re:Invent as well, they're talking about seamless connectivity between their services. They're talking about security, they're talking about creating a data fabric, the data zone that they announced. I think all these things put together, if you're able to kind of connect the dots and drive the business processes, I think that's what we want to do for our customers. >> And the value to AWS, it just can't be underscored enough I would assume, because there's comfort there, there's confidence there. When you bring that to the table as well along with your services, what kind of magnitude are we talking about here? What kind of force do you think? How would you characterize that? >> Well I think, you know, firstly, I would say that most of our engagements are not just services. Ashish and team and the company have invested heavily in building IP that we pair with our services so that we bring non-linearity and more, I would say, certainty to the outcomes that our customers get. And I can share some examples in the course of the conversation, but to answer your question in terms of magnitude, what we are collaborating with AWS on for our clients ranges from helping customers build more resiliency. And I'm talking about life sciences companies build more resiliency in the manufacturing R and D processes. That's so critical. It was even more critical during the pandemic times because we were working with some of the pharma companies who were contributing to the efforts in the pandemic. That's one end of the spectrum. On the other side, we are helping streaming companies and media companies digitize their supply chain, and their supply chains, the media supply chain, so that it is more effective, it's more efficient, it's more real time, again, using the power of the cloud. We are helping pharmaceutical companies drive far greater speed in the R and D processes. We are helping banking companies drive far more compliance in their anti-money laundering efforts and all of those things. So if you look at the magnitude, we judge the magnitude by the business impact that it's creating and we are very excited about what AWS, LTI Mindtree, and the customer are able to create in terms of those business impacts. >> And these are such major decisions. >> That's right. >> For a company, right, to make, and there are a number of factors that come into play here. What are you hearing from the C-Suite with regard to what weighs the most in their mind and is there, is it a matter of, you know, fear missing out? Or is it about trying to stay ahead of your competition, catching up the competition? I mean, generally speaking, you know, where are the, where's the C-Suite weighing in on this? >> I think in the current times, I think there is a certain level of adoption of cloud that's already happened in most enterprises. So most CIOs in the C-suite- >> They already get it. They already get it. >> They kind of get it, but I would say that they're very cagey about a bunch of things. They're very cagey about, am I going to end up spending too much for too little? Am I going to be able to deliver this transformation at the speed that I'm hoping to achieve? What about security? Compliance? What about the cost of running in the cloud? So those are some really important factors that sometimes end up slowing the cloud transformation journeys down because customers end up solving for them or not knowing for them. So while there is a decent amount of awareness about what cloud can do, there are some, a whole bunch of important factors that they continue to solve for as they go down that journey. >> And so what kind of tools do you provide them then? >> Primarily, what we do is, to Siddharth's point, right? So on one end, we want to see to it that we are doing the business transformation and all our cloud journeys start with a business North Star. So we align, we have doubled down on, say, five to six business domains. And for each of these business domains industries, we have created business North Star. For these business North Star, we define the use cases. And these use cases then get lit up through our platform. So what we have done is we have codified everything onto our platform. We call it Infinity. So primarily business processes from level one, level two, level three, level, and then the KPIs which are associated with these business processes, the technical KPIs and the business KPIs, and then tying it back to what you have deployed on cloud. So we have end to end cloud transformation journeys enabled for customers through the business North Star. >> And Infinity is your product. >> Can I add something? >> Please do. Yeah, please. >> Yeah so, you know, Ashish covered the part about demystifying if I were to do this particular cloud initiative, it's not just modernizing the application. This is about demystifying what business benefit will accrue to you. Very rare to find unless you do a very deep dive assessment. But what the platform we built also accelerates, you talked about modernization early in the conversation, accelerates the modernization process by automating a whole bunch of activities that are often manual. It bakes insecurity and compliance into everything it does. It automates a whole bunch of cloud operations including things like finops. So this is a life cycle platform that essentially codifies best practices so that you are not getting success by coincidence, you're getting success by design. So that's really what, that's really how we've approached the topic of realizing the true power of cloud by making sure that it's repeatedly delivered. >> Right. You know, I want to hit on security too because you brought that up just a few moments ago. Obviously, you know, we all, and I'd say we, we can do a better job, right? I mean, there's still problems, there's still challenges, there are a lot of bad actors out there that are staying ahead of the game. So as people come to you, clients come to you, and they raise these security concerns, what's your advice to them in terms of, you know, what kind of environment they're going into and what precautions or protections they can put in place to try to give themselves a little bit of peace of mind about how they're going to operate? >> You want to take it? >> So I think primarily, if you are going to cloud, you are going with an assumption that you are moving out of your firewalls, right? You're putting something out of your network area. So and from that perspective, the parameter security from the cloud perspective is very, very important. And then each and every service or the interactions between the services and what you integrate out of your organization, everything needs to be secured through the right guard rates. And we integrate all those things into our platform so that whatever new apps that get deployed or build or any cost product that gets deployed on cloud, everything is secure from a 360 degree perspective. So primarily, maintaining a good security posture, which on a hybrid cloud, I would not say only cloud, but extending your on-prem security posture to cloud is very, very important to when you go to implementing anything on could. >> If you had a crystal ball and we were sitting down here a year from now, you know, what do you think we'd be talking about with regard to, you know, developing these end-to-end opportunities that you are, what's the, I wouldn't say missing piece, but a piece that you would like to have refined to the point where you come back next year and say, John, guess what we did? Look what we were able to accomplish. Anything that you're looking at that you want to tackle here in 2023? Or is there some fine tuning somewhere that you think could even tighten your game even more than it is already? >> We have a long, long way to go, I would say. I think my core takeaway in terms of where the world of technology is headed because cloud is, you know, is essentially a component of what customers want to achieve. It's a medium through which they want to achieve. I think we live in a highly change oriented economy. Every industry is what I call getting re-platformed, right? New processes, new experiences, new products, new efficiency. So a year from now, and I can tell you even for few years from now, we would be constantly looking at our success in terms of how did cloud move the needle on releasing products faster? How did cloud move the needle on driving better experience and better consumer loyalty, for example. How did cloud move the needle on a more efficient supply chain? So increasingly, the technology metrics like, you know, keeping the lights on, or solving tickets, or releasing code on time, would move towards business metrics because that's really the ultimate goal of technology or cloud. So I would say that my crystal ball says we will increasingly be talking business language and business outcomes. Jeff Bezos is an incredible example, right? One of his annual letters, he connected everything back into how much time did consumers save by using Amazon. And I think that's really where in the world, that's the world we are headed towards. >> Ashish, any thoughts on that? >> I think Siddharth put it quite well. I would say if you are able to make a real business impact for our customers in next one year, helping them in driving some of their newer services on cloud through cloud, that would be a success factor for us. >> Well gentlemen, congratulations on the merger. I said two weeks. Still very much in the honeymoon phase and I'm sure it's going to go very well and I look forward to seeing you back here in a year. We'll sit down, same spot, let's remember, fifth floor, and we'll give it a shot and see how accurate you were on that. >> Absolutely. >> Wonderful. It's been a pleasure. >> Thank you gentlemen. >> Thank you for joining us. >> Thank you. >> Very good. Ashish, good to see you, sir. >> Thank you. >> A pleasure. We'll continue here. We're at the Venetian at AWS re:Invent 22, continue at the AWS Global Showcase startup. I'm John Walls. You're watching theCUBE, the leader in high tech coverage. (gentle music)

>>Hello everyone. Welcome to the Special Cube presentation of Accelerating Business Transformation on vmc on aws. I'm John Furrier, host of the Queue. We have Chief Dawan, Director of global sales, and go to market for VMware Cloud Ons. This is a great showcase and should be a lot of fun. Ashish, thanks for coming on. >>Hi, John. Thank you so much. >>So VMware cloud on AWS has been well documented as this big success for VMware and aws. As customers move their workloads into the cloud IT operations of VMware customers has signaling a lot of change. This is changing the landscape globally as on cloud migration and beyond. What's your take on this? Can you open this up with the most important story around VMC on aws? >>Yes, John. The most important thing for our customers today is the how they can safely and swiftly move their ID infrastructure and applications to the cloud. Now, VMware Cloud AWS is a service that allows all vSphere based workloads to move to cloud safely, swiftly, and reliably. Banks can move their core, core banking platforms, insurance companies move their core insurance platforms, telcos move their GOs, bss, plat platforms, government organizations are moving their citizen engagement platforms using VMC on aws because this is one platform that allows you to move it, move their VMware based platforms very fast. Migrations can happen in a matter of days instead of months, extremely securely. It's a VMware managed service. It's very secure and highly reliably. It gets the, the reliability of the underlyings infrastructure along with it. So win-win from our customer's >>Perspective. You know, we reported on this big news in 2016 with Andy Chassis and Pat Geling at the time, a lot of people said it was a bad deal. It turned out to be a great deal because not only could VMware customers actually have a cloud migrate to the cloud, do it safely, which was their number one concern. They didn't want to have disruption to their operations, but also position themselves for what's beyond just shifting to the cloud. So I have to ask you, since you got the finger on the pulse here, what are we seeing in the market when it comes to migrating and modern modernizing in the cloud? Because that's the next step. They go to the cloud, you guys have done that, doing it, then they go, I gotta modernize, which means kind of upgrading or refactoring. What's your take on that? >>Yeah, absolutely. Look, the first step is to help our customers assess their infrastructure and licensing and entire ID operations. Once we've done the assessment, we then create their migration plans. A lot of our customers are at that inflection point. They're, they're looking at their real estate data center, real estate. They're looking at their contracts with colocation vendors. They really want to exit their data centers, right? And VMware cloud and AWS is a perfect solution for customers who wanna exit their data centers, migrate these applications onto the AWS platform using VMC on aws, get rid of additional real estate overheads, power overheads, be socially and environmentally conscious by doing that as well, right? So that's the migration story, but to your point, it doesn't end there, right? Modernization is a critical aspect of the entire customer journey is as well. Customers, once they've migrated their ID applications and infrastructure on cloud, get access to all the modernization services that AWS has. They can correct easily to our data lake services, to our AIML services, to custom databases, right? They can decide which applications they want to keep and which applications they wanna refactor. They want to take decisions on containerization, take decisions on service computing once they've come to the cloud. But the most important thing is to take that first step, you know, exit their data centers, come to AWS using VMC or aws, and then a whole host of modernization options available to them. >>Yeah, I gotta say, we had this right on this, on this story because you just pointed out a big thing, which was first order of business is to make sure to leverage the on-prem investments that those customers made and then migrate to the cloud where they can maintain their applications, their data, their infrastructure operations that they're used to, and then be in position to start getting modern. So I have to ask you, how are you guys specifically, or how is VMware cloud ons addressing these needs of the customers? Because what happens next is something that needs to happen faster, and sometimes the skills might not be there because if they're running old school IT ops now they gotta come in and jump in. They're gonna use data cloud, they're gonna want to use all kinds of machine learning, and there's a lot of great goodness going on above the stack there. So as you move with the higher level services, you know, it's a no brainer, obviously, but they're not, it's not yesterday's higher level services in the cloud. So how are, how is this being addressed? >>Absolutely. I think you hit up on a very important point, and that is skills, right? When our customers are operating, some of the most critical applications I just mentioned, core banking, core insurance, et cetera, they're most of the core applications that our customers have across industries, even even large scale ERP systems, they're actually sitting on VMware's vSphere platform right now. When the customer wants to migrate these to cloud, one of the key bottlenecks they face is skill sets. They have the trained manpower for these core applications, but for these high level services, they may not, right? So the first order of business is to help them ease this migration pain as much as possible by not wanting them to, to upscale immediately. And v VMware clouds exactly does that. I mean, you don't have to do anything. You don't have to create new skill set for doing this, right? Their existing skill sets suffice, but at the same time, it gives them that, that leeway to build that skills roadmap for their team. And AWS is invested in that, right? We want to help them build those skills in the high level services, be it aml, be it, be it iot, be it data lake and analytics. We want to invest in them, and we help our customers through that. So that ultimately the ultimate goal of making them draw data is, is, is front and center. >>I wanna get into some of the use cases and success stories, but I want to just reiterate, hit back your point on the skill thing. Because if you look at what you guys have done at aws, you've essentially, and Andy Chassey used to talk about this all the time when I would interview him, and now last year Adam was seeing the same thing. You guys do all the heavy lifting, but if you're a VMware customer user or operator, you are used to things. You don't have to be relearn to be a cloud architect. Now you're already in the game. So this is like almost like a instant path to cloud skills for the VMware, and there's hundreds of thousands of, of VMware architects and operators that now instantly become cloud architects, literally overnight. Can you respond to that? Do you agree with that? And then give an example. >>Yes, absolutely. You know, if you have skills on the VMware platform, you know, migrating to AWS using via by cloud and AWS is absolutely possible. You don't have to really change the skills. The operations are exactly the same. The management systems are exactly the same. So you don't really have to change anything, but the advantages that you get access to all the other AWS services. So you are instantly able to integrate with other AWS services, and you become a cloud architect immediately, right? You're able to solve some of the critical problems that your underlying IT infrastructure has immediately using this. And I think that's a great value proposition for our customers to use this service. >>And just one more point, I wanna just get into something that's really kind of inside baseball or nuanced VMC or VMware cloud on AWS means something. Could you take a minute to explain what on AWS means? Just because you're like hosting and using Amazon as a, as a work workload? Being ONS means something specific in your world, being VMC on AWS mean? >>Yes. This is a great question, by the way, You know, on AWS means that, you know, VMware's vSphere platform is, is a, is an iconic enterprise virtualization software. It's got, you know, a disproportionately high market share across industries. So when we wanted to create a cloud product along with them, obviously our aim was for them, for the, for this platform to have the goodness of the AWS underlying infrastructure, right? And, and therefore, when we created this VMware cloud solution, it, it literally used the AWS platform under the eighth, right? And that's why it's called VMs, VMware cloud on AWS, using, using the, the, the wide portfolio of our regions across the world and the strength of the underlying infrastructure, the reliability and, and, and sustainability that it offers. And therefore this product is called VMC on aws. >>It's a distinction I think is worth noting, and it does reflect engineering and some levels of integration that go well beyond just having a SASS app and, and basic platform as a service or past services. So I just wanna make sure that now super cloud, we'll talk about that a little bit in another interview, but I gotta get one more question in before we get into the use cases and customer success stories is in, in most of the VM world, VMware world, in that IT world that used to, when you heard migration, people would go, Oh my God, that's gonna take months. And when I hear about moving stuff around and doing cloud native, the first reaction people might have is complexity. So two questions for you before we move on to the next talk. Track complexity. How are you addressing the complexity issue and how long do these migrations take? Is it easy, is it hard? I mean, you know, the knee jerk reaction is month, You're very used to that. If they're dealing with Oracle or other old school vendors, like, they're, like the old guard would be like, takes a year to move stuff around. So can you comment on complexity and speed? >>Yeah. So the first, first thing is complexity. And you know, what makes what makes anything complex is if you're, if you're required to acquire new skill sets or you've gotta, if you're required to manage something differently, and as far as VMware cloud on AWS on both these aspects, you don't have to do anything, right? You don't have to acquire new skill sets. Your existing ideal operations skill sets on, on VMware's platforms are absolutely fine and you don't have to manage it any differently. Like Dan, what you're managing your, your ID infrastructure today. So in both these aspects, it's exactly the same. And therefore it is absolutely not complex as far as, as far as, as far as ve VMware, cloud and AWS is concerned. And the other thing is speed. Now, this is where the huge differentiation is. You have seen that, you know, large banks and large telcos have now moved their workloads, you know, literally in days instead of months. >>Because because of VMware cloud and aws, a lot of time customers come to us with specific deadlines because they want to exit their data centers on a particular date. And what happens, VMware cloud and AWS is called upon to do that migration, right? So speed is absolutely critical. The reason is also exactly the same because you are using the exactly the same platform, the same management systems, people are available to you, you're able to migrate quickly, right? I would just reference recently we got an award from President Linsky of Ukraine for, you know, migrating their entire ID digital infrastructure and, and that that happened because they were using VMware cloud radio based and happened very swiftly. >>That's not a great example. I mean, that's one political, but the economic advantage of getting outta the data center could be national security. You mentioned Ukraine, I mean I bombing and death over there. So clearly that's a critical crown jewel for their running their operations, which is, you know, world mission critical. So great stuff. I love the speed thing. I think that's a huge one. Let's get into some of the use cases. One of them is, the first one I wanted to talk about was we, you just hit on data, data center migration. It could be financial reasons on a downturn or our, or a market growth. People can make money by shifting to the cloud, either saving money or making money. You win on both sides. It's a, it's a, it's almost a recession proof, if you will. Cloud is so use case for number one data center migration. Take us through what that looks like. Give it an example of a success. Take us through a day in the life of a data center migration in, in a couple minutes. >>Yeah. You know, I can give you an example of, of a, of a large bank who decided to migrate, you know, their, all their data centers outside their existing interest. And they had, they had a set timeline, right? They had a set timeline to migrate the, they were coming up on a deal and they wanted to make sure that this set timeline is met. We did a, a complete assessment of their infrastructure. We did a complete assessment of their IT applications, more than 80% of their IT applications, underlying v vSphere platform. And we, we thought that the right solution for them in the timeline that they wanted, right, is VMware cloud gas. And obviously it was a large bank, it wanted to do it safely and securely. It wanted to have it completely managed, and therefore VMware cloud and aws, you know, ticked all the boxes as far as that is concerned. >>I'll be happy to report that the large bank has moved to most of their applications on AWS exiting three of their data centers, and they'll be exiting 12 more very soon. So that's a great example of, of, of the large bank exiting data centers. There's another gallery to that. Not only did they manage to manage to exit their data centers and of course be more agile, but they also met their sustainability goals. Their board of directors had given them goals to be carbon neutral by 2025. They found out that 35% of all their carbon F footprint was in their data centers. And if they moved their, their ID infrastructure to cloud, they would severely reduce the, the carbon footprint, which is 35% down to 17 to 18%. Right? And that met their, their, their, their sustainability targets and their commitment to the, to being carbon neutral as well. >>And that they, and they shift that to you guys. Would you guys take that burden? A heavy lifting there and you guys have a sustainability story, which is a whole nother showcase in and of itself. >>We can exactly. And, and cause of the scale of our, of our operations, we are able to, we are able to work on that really well as well. >>All right. So love the data migration. I think that's got real proof points. You got, I can save money, I can, I can and move and position my applications into the cloud for that reason and other reasons as a lot of other reasons to do that. But now it gets into what you mentioned earlier was, okay, data migration, clearly a use case and you laid out some successes. I'm sure there's a zillion others. But then the next step comes, now you got cloud architects becoming minted every, and you got managed services and higher level services. What happens next? Can you give us an example of the use case of the modernization around the NextGen workloads, NextGen applications? We're starting to see, you know, things like data clouds, not data warehouses. We're not gonna have data clouds. It's gonna be all kinds of clouds. These NextGen apps are pure digital transformation in action. Take us through a use case of how you guys make that happen with a success story. >>Yes, absolutely. And this is, this is an amazing success story and the customer here is s and p global ratings. As you know, s and p global ratings is, is the world leader as far as global ratings, global credit ratings is concerned. And for them, you know, the last couple of years have been tough as far as hardware procurement is concerned, right? The pandemic has really upended the, the supply chain. And it was taking a lot of time to procure hardware, you know, configure it in time, make sure that that's reliable. And then, you know, distributed in the wide variety of, of, of offices and locations that they have. And they came to us. We, we did, again, a, a a a alar, a fairly large comprehensive assessment of their ID infrastructure and their licensing contracts. And we also found out that VMware cloud and AWS is the right solution for them. >>So we worked there, migrated all their applications, and as soon as we migrated all their applications, they got, they got access to, you know, our high level services be a analytics services, our machine learning services, our, our, our, our artificial intelligence services that have been critical for them, for their growth. And, and that really is helping them, you know, get towards their next level of modern applications. Right Now, obviously going forward, they will have, they will have the choice to, you know, really think about which applications they want to, you know, refactor or which applications they want to go ahead with. That is really a choice in front of them. And, but you know, the, we VMware cloud and AWS really gave them the opportunity to first migrate and then, you know, move towards modernization with speed. >>You know, the speed of a startup is always the kind of the Silicon Valley story where you're, you know, people can make massive changes in 18 months, whether that's a pivot or a new product. You see that in startup world. Now, in the enterprise, you can see the same thing. I noticed behind you on your whiteboard, you got a slogan that says, are you thinking big? I know Amazon likes to think big, but also you work back from the customers. And, and I think this modern application thing's a big deal because I think the mindset has always been constrained because back before they moved to the cloud, most IT, and, and, and on-premise data center shops, it's slow. You gotta get the hardware, you gotta configure it, you gotta, you gotta stand it up, won't make sure all the software is validated on it, and loading a database and loading oss, I mean, yeah, it got easier and with scripting and whatnot, but when you move to the cloud, you have more scale, which means more speed, which means it opens up their capability to think differently and build product. What are you seeing there? Can you share your opinion on that epiphany of, Wow, things are going fast, I got more time to actually think about maybe doing a cloud native app or transforming this or that. What's your, what's your reaction to that? Can you share your opinion? >>Well, ultimately we, we want our customers to utilize, you know, most of our modern services, you know, applications should be microservices based when desired, they should use serverless, applic, serverless technology. They should not have monolithic, you know, relational database contracts. They should use custom databases. They should use containers when needed, right? So ultimately, we want our customers to use these modern technologies to make sure that their IT infrastructure, their licensing, their, their entire IT spend is completely native to cloud technologies. They work with the speed of a startup, but it's important for them to, to, to get to the first step, right? So that's why we create this journey for our customers, where you help them migrate, give them time to build the skills, they'll help them modernize, take our partners along with their, along with us to, to make sure that they can address the need for our customers. That's, that's what our customers need today, and that's what we are working backwards from. >>Yeah, and I think that opens up some big ideas. I'll just say that, you know, we were joking, I was joking the other night with someone here in, in Palo Alto around serverless, and I said, you know, soon you're gonna hear words like architecture lists. And that's a criticism on one hand, but you might say, Hey, you know, if you don't really need an architecture, you know, storage list, I mean, at the end of the day, infrastructure is code means developers can do all the it in the coding cycles and then make the operations cloud based. And I think this is kind of where I see the dots connecting. Final thought here, take us through what you're thinking around how this new world is evolving. I mean, architecture kind of a joke, but the point is, you know, you have to some sort of architecture, but you don't have to overthink it. >>Totally. Now, that's a great thought, by the way. I know it's a joke, but it's a great thought because at the end of the day, you know, what do the customers really want? They want outcomes, right? Why did service technology come? It was because there was an outcome that they needed. They didn't want to get stuck with, you know, the, the, the real estate of, of a, of a server. They wanted to use compute when they needed to, right? Similarly, what you're talking about is, you know, outcome based, you know, desire of our customers and, and, and that's exactly where the word is going to, Right? Cloud really enforces that, right? We are actually, you know, working backwards from a customer's outcome and using our area, the breadth and depth of our services to, to deliver those outcomes, right? And, and most of our services are in that path, right? When we use VMware cloud and aws, the outcome is a, to migrate then to modernize, but doesn't stop there, use our native services, you know, get the business outcomes using this. So I think that's, that's exactly what we are going through. >>Actually, I say she the director of global sales and go to market for VMware cloud on Aus. I wanna thank you for coming on, but I'll give you the final minute. Give a plug, explain what is the VMware cloud on Aus, Why is it great? Why should people engage with you and, and the team, and what ultimately is this path look like for them going forward? >>Yeah, at the end of the day, we want our customers to have the best parts to the cloud, right? The, the best parts to the cloud is making sure that they migrate safely, reliably, and securely as well as with speed, right? And then, you know, use that cloud platform to, to utilize AWS's native services to make sure that they modernize their IT infrastructure and applications, right? We want, ultimately that our customers, customers, customer get the best out of, you know, utilizing that, that whole application experience is enhanced tremendously by using our services. And I think that's, that's exactly what we are working towards VMware cloud AWS is, is helping our customers in that journey towards migrating, modernizing, whether they want to exit a data center or whether they wanna modernize their applications. It's in the central first step that we wanna help our customers with >>Wan, director of global sales and go to market with VMware cloud on neighbors. He's with aws sharing his thoughts on accelerating business transformation on aws. This is showcase, We're talking about the future path. We're talking about use cases with success stories from customers as she's thank you for spending time today on this showcase. >>Thank you, John. I >>Appreciate it. Okay. This is the cube, special coverage, special presentation of the AWS Showcase. I'm John Furrier, thanks for watching.

(upbeat music) >> Hello everyone. Welcome to the Special Cube presentation of Accelerating Business Transformation on VMC on AWS. I'm John Furrier, host of the Cube. We have Ashish Dhawan, Director of Global Sales and go to market for VMware Cloud on AWS. This is a great showcase and should be a lot of fun. Ashish, thanks for coming on. >> Hi, John. Thank you so much. >> So VMware Cloud on AWS has been well documented as this big success for VMware and AWS. As customers move their workloads into the cloud, IT operations of VMware customers has signaling a lot of change. This is changing the landscape globally on cloud migration and beyond. What's your take on this? Can you open this up with the most important story around VMC on AWS? >> Yes, John. The most important thing for our customers today is, how they can safely and swiftly move their ID infrastructure and applications to the cloud. Now, VMware Cloud AWS is a service that allows all vSphere based workloads to move the cloud safely, swiftly, and reliably. Banks can move their core banking platforms, insurance companies move their core insurance platforms, telcos move their GOSS, BSS platforms, government organizations are moving their citizen engagement platforms using VMC on AWS because this is one platform that allows you to move it, move their VMware based platforms very fast. Migrations can happen in a matter of days instead of months, extremely securely. It's a VMware managed service. It's very secure and highly reliably gets the reliability of the underlying AWS infrastructure along with it. So win-win from a customer's perspective. >> You know, we reported on this big news in 2016 with Andy Jassy and Pat Gelsinger at the time, a lot of people said it was a bad deal. It turned out to be a great deal because not only could VMware customers actually have a cloud, migrate to the cloud, do it safely, which was their number one concern. They didn't want to have disruption to their operations, but also position themselves for what's beyond just shifting to the cloud. So I have to ask you, since you got the finger on the pulse here. What are we seeing in the market when it comes to migrating and modernizing in the cloud? Because that's the next step. They go to the cloud, you guys have done that, doing it, then they go, "I got to modernize" which means kind of upgrading or refactoring. What's your take on that? >> Yeah, absolutely. Look, the first step is to help our customers assess their infrastructure and licensing and entire ID operations. Once we've done the assessment, we then create their migration plans. A lot of our customers are at that inflection point. They're, they're looking at their real estate, data center real estate. They're looking at their contracts with co-location vendors. They really want to exit their data centers, right? And VMware cloud or AWS is a perfect solution for customers who want to exit their data centers, migrate these applications onto the AWS platform using VMC on AWS, get rid of additional real estate overheads, power overheads, be socially and environmentally conscious by doing that as well. Right? So that's the migration story, but to your point, it doesn't end there, right? Modernization is a critical aspect of the entire customer journey as well. Customers, once they've migrated their ID applications and infrastructure on cloud, get access to all the modernization services that AWS has. They can connect easily to our data lake services, to our AIML services, to custom databases, right? They can decide which applications they want to keep and which applications they want to refactor. They want to take decisions on containerization, take decisions on service computing once they've come to the cloud. But the most important thing is to take that first step. You know, exit their data centers come to AWS using VMC on AWS, and then the whole host of modernization options are available to them. >> Yeah, I got to say, we had this right on this story because you just pointed out a big thing, which was first order of business is to make sure to leverage the on-prem investments that those customers made and then migrate to the cloud where they can maintain their applications, their data, their infrastructure operations that they're used to, and then be in position to start getting modern. So I have to ask you, how are you guys specifically, or how is VMware cloud on AWS, addressing these needs of the customers? Because what happens next is something that needs to happen faster, and sometimes the skills might not be there because if they're running old school IT ops now they got to come in and jump in. They're going to use data cloud, they're going to want to use all kinds of machine learning, and there's a lot of great goodness going on above the stack there. So as you move with a higher level services, you know, it's a no-brainer, obviously, but they're not, it's not yesterday's higher level services in the cloud. So how are, how is this being addressed? >> Absolutely. I think you hit upon a very important point, and that is skills, right? When our customers are operating some of the most critical applications I just mentioned, core banking, core insurance, et cetera, there, most of the core applications that our customers have across industries, like even large scale ERP systems, they're actually sitting on VMware's vSphere platform, right? Now, when the customer wants to migrate these to cloud, one of the key bottlenecks they face is skill sets. They have the trained manpower for these core applications, but for these high level services, they may not, right? So the first order of business is to help them ease this migration pain as much as possible by not wanting them to upscale immediately. And VMware cloud with AWS exactly does that. I mean, you don't have to do anything. You don't have to create new skill set for doing this, right? Their existing skill set suffice, but at the same time, it gives them that leeway to build that skills roadmap for their team. And AWS is invested in that, right? We want to help them build those skills in the high level services, be AML, be it, be it IoT, be it data lake and analytics. We want to invest in them and we help our customers through that. So that ultimately, the ultimate goal of making them draw data is, is, is front and center. >> I want to get into some of the use cases and success stories, but I want to just reiterate, hit back your point on the skill thing because, if you look at what you guys have done at AWS, you've essentially, and Andy Jassy used to talk about this all the time when I would interview him, and now last year Adam was saying the same thing. You guys do all the heavy lifting, but if you're a VMware customer, user or operator, you're used to things. You don't have to be relearn to be a cloud architect. Now, you're already in the game. So this is like almost like a instant path to cloud skills for the VMware, and there's hundreds of thousands of VMware architects and operators, that now instantly become cloud architects, literally overnight. Can you respond to that? Do you agree with that? And then, give an example. >> Yes, absolutely. You know, if you have skills on the VMware platform, you know, migrating to AWS using VMware cloud or AWS is absolutely possible. You don't have to really change the skills. The operations are exactly the same. The management systems are exactly the same. So you don't really have to change anything but, the advantages, that you get access to all the other AWS services. So you are instantly able to integrate with other AWS services, and you become a cloud architect immediately, right? You are able to solve some of the critical problems that your underlying IT infrastructure has immediately using this. And I think that's a great value proposition for our customers to use this service. >> And just one more point, I want to just get into something that's really kind of inside baseball or nuanced, VMC or VMware cloud on AWS means something. Could you take a minute to explain what "on AWS" means? Just because you're like hosting and using Amazon as a workload? Being on AWS means something specific in your world, what does being VMC on AWS mean? >> Yes. This is a great question, by the way. You know, on AWS means that, VMware's vSphere platform is an iconic enterprise virtualization software. It's, you know, a disproportionately high market share across industries. So when we wanted to create a cloud product along with them, obviously our aim was for them, for this platform, to have the goodness of the AWS underlying infrastructure, right? And therefore, when we created this VMware cloud solution, it literally used the AWS platform under the name, right? And that's why it's called VMware cloud on AWS, using the wide portfolio of our regions across the world and the strength of the underlying infrastructure, the reliability and sustainability that it offers. And therefore this product is called VMC on AWS. >> It's a distinction I think is worth noting, and it does reflect engineering and some levels of integration that go well beyond just having a SAS app and basically platform as a service or past services. So I just make sure that now Supercloud, we'll talk about that a little bit in another interview, but I got to get one more question in before we get into the use cases in customer success stories is in most of the VMware world, in that IT world, it used to, when you heard migration, people would go, oh my God, that's going to take months. And when I hear about moving stuff around and doing cloud native, the first reaction people might have is complexity. So two questions for you before we move on to the next talk track. Complexity, how you addressing the complexity issue and how long do these migrations take? Is it easy, is it hard? I mean, you know, the, the knee-jerk reaction is month very used to that. If they're dealing with Oracle or other old school vendors, they're like the old guard would be like, takes a year to move stuff around. So can you comment on complexity and speed? >> Yeah. So the first, first thing is complexity. And you know, what makes anything complex is if you're required to acquire new skill sets or you've got to, if you're required to manage something differently. And as far as VMware cloud and AWS, on both these aspects, you don't have to do anything, right? You don't have to acquire new skill sets. You existing ID operation skill sets on, VMware's platforms are absolutely fine, and you don't have to manage it any differently. Like, dang what you're managing your ID infrastructure today. So in both these aspects, it's exactly the same and therefore it is absolutely not complex as far as VMware cloud and AWS is concerned. And the other thing is speed. Now, this is where the huge differentiation is. You have seen that, you know, large banks and large telcos have now moved their workloads, you know, literally in days instead of months because of VMware cloud and AWS. A lot of times customers come to us with specific deadlines because they want to exit their data centers on a particular date. And what happens? VMware cloud and AWS is called upon to do that migration, right? Speed is absolutely critical. The reason is also exactly the same, because you are using the exactly the same platform, the same management systems, people are available to you, you're able to migrate quickly, right? I would just reference recently we got an award from President Zelinsky of Ukraine for, you know, migrating their entire ID digital infrastructure and that happened because they were using VMware cloud radar base and happened very swiftly. >> That's a great example. I mean, that's one political, but the economic advantage of getting out of the data center could be national security. You mentioned Ukraine, I mean obstacles, bombing and death over there. So clearly that's a critical crown jewel for their running their operations, which is, you know, world mission critical. So great stuff. I love the speed thing. I think that's a huge one. Let's get into some of the use cases. One of them is, the first one I wanted to talk about, was when you hit on data data center migration. It could be financial reasons on a downturn or market growth, people can make money by shifting to the cloud, either saving money or making money. You win on both sides. It's a, almost a recession proof, if you will, cloud is. So use case for number one data center migration. Take us through what that looks like. Give an example of a success. Take us through a day in the life of a data center migration in a couple minutes. >> Yeah. You know, I can give you an example of a large bank who decided to migrate all their data centers outside their existing interest. (static) And they had a set timeline, right? They had a set timeline to migrate the data, they were coming up on a review and they wanted to make sure that this set timeline is met. We did a complete assessment of their infrastructure. We did a complete assessment of their IT applications, more than 80 percent of their ID applications, (static) underlying vSphere platform. And we thought that the right solution for them in the timeline that they wanted, right, is VMware cloud and AWS. And obviously it was a large bank. It wanted to do it safely and securely. It wanted to have it completely managed and therefore VMware cloud and AWS, you know, ticked all the boxes as far as that is concerned. I'll be happy to report that the large bank has moved most of their applications on AWS exiting three of their data centers and they'll be exiting 12 more very soon. So that's a great example of the large bank exiting data centers. There's another corollary to that. Not only did they manage to manage to exit their data centers and of course use and be more agile, but they also met their sustainability goals. Their board of directors had given them goals to be carbon neutral by 2025. They found out that 35 percent of all their carbon footprint was in their data centers. And if they moved their ID infrastructure to cloud, they would severely reduce the carbon footprint, which is 35 percent down to 17 or 18 percent. Right? And that met their sustainability targets and their commitment to being carbon neutral as well. >> And that they, and they shift that to you guys. Which you guys take that burden, a heavy lifting there, and you guys have a sustainability story, which is a whole nother showcase in and of itself. >> Exactly. And, because of the scale of our operations, we are able to work on that really well as well. >> All right. So love the data migration. I think that's got real proof points. You got, I can save money and move and position my applications into the cloud for that reason and other reasons. There's a lot of other reasons to do that. But now it gets into what you mentioned earlier was, okay, data migration, clearly a use case and you laid out some successes. I'm sure there's a zillion others. But then the next step comes, now you got cloud architects becoming minted and you got managed services and higher level services. What happens next? Can you give us an example of the use case of the modernization around the next gen workloads, NextGen applications? We're starting to see, you know, things like data clouds, not data warehouses. We're not going to data clouds, it's going to be all kinds of clouds. These NextGen apps are pure digital transformation in action. Take us through a use case of how you guys make that happen with a success story. >> Yes, absolutely. And this is, this is an amazing success story and the customer here is S&P Global Ratings. As you know, S&P Global Ratings is the world leader as far as global ratings, global credit ratings is concerned. And for them, you know, the last couple of years have been tough as far as hardware procurement is concerned, right? The pandemic has really upended the supply chain. And it was taking a lot of time to procure hardware, you know, configure it in time, make sure that that's reliable. And then, you know, distributed in the wide variety of of offices and locations that they have. And they came to us. We did, again a very large comprehensive assessment of their ID infrastructure and their licensing contracts. And we also found out that VMware cloud and AWS is the right solution for them. So we worked there, migrated all their applications, and as soon as we migrated all their applications, they got access to, you know, our high level services. Be it our analytics services, our machine learning services, our artificial intelligence services that have been critical for them, for their growth. And that really is helping them, you know, get towards their next level of modern applications. Right? Now, obviously going forward, they will have, the choice to, you know, really think about which applications they want to, you know, refactor or which applications they want to go ahead with. That is really a choice in front of them. But you know, the VMware cloud and AWS really gave them the opportunity to first migrate and then, you know, move towards modernization with speed. >> The speed of a startup is always the kind of the Silicon Valley story where you know, people can make massive changes in 18 months, whether it's a pivot or a new product. You see that in the startup world. Now, in the enterprise, you can see the same thing. I noticed behind you on your whiteboard, you got a slogan that says, "are you thinking big?" I know Amazon likes to think big, but also you work back from the customers and I think this modern application thing's a big deal, because I think the mindset has always been constrained, because back before they moved to the cloud, most IT, and on-premise data center shops, it's slow. You got to get the hardware, you got to configure it, you got to stand it up, you got to make sure all the softwares validated on it, and loading and database and loading OSs, I mean, yeah, it got easier and with scripting and whatnot, but when you move to the cloud, you have more scale, which means more speed, which means it opens up their capability to think differently and build product. What are you seeing there? Can you share your opinion on that epiphany of, "wow, things are going fast, I got more time to actually think about maybe doing a cloud native app or transforming this or that." What's your reaction to that? Can you share your opinion? >> Well, ultimately we, we want our customers to utilize, you know, most of our modern services, you know, obligations should be microservices based. When desired, they should use serverless technology. They should not have monolithic, you know, relational database contracts. They should use custom databases. They should use containers when needed, right? So ultimately, we want our customers to use these modern technologies to make sure that their IT infrastructure, their licensing, their entire IT spend is completely native to cloud technologies that work for the speed of a startup. But it's important for them to get to the first step, right? So that's why we create this journey for our customers where you help them migrate, give them time to build the skills, they'll help them modernize, take our partners along with us to make sure that they can address the need for our customers. That's what our customers need today and that's what we are working backwards from. >> Yeah, and I think that opens up some big ideas. I'll just say that, you know, we're joking, I was joking the other night with someone here in Palo Alto around serverless, and I said, you know, soon you're going to hear words like architectureless. And that's a criticism on one hand, but you might say, hey, you know, if you don't really need an architecture, you know, storage list. I mean, at the end of the day, infrastructure is code means developers can do all the IT in the coding cycles and then make the operations cloud based. And I think this is kind of where I see the dots connecting. Final thought here, take us through what you're thinking around how this new world is evolving. I mean, architectural a joke, but the point is, you know, you have to some sort of architecture, but you don't have to overthink it. >> Totally. That's a great thought, by the way, I know it's a joke, but it's a great thought because at the end of the day, you know, what do your customers really want? They want outcomes, right? Why did service technology come? It was because there was an outcome that they needed. They didn't want to get stuck with, you know, the real estate of a server. They wanted to use computer when they needed to, right? Similarly, what you're talking about is, you know, outcome based, you know, desire of our customers and that's exactly where the world is going to, right? Cloud really enforces that, right? We are actually, you know, working backwards from a customer's outcome and using our area, the breadth and depth of our services to deliver those outcomes, right? And most of our services are in that path, right? When we use VMware cloud and AWS, the outcome is A. to migrate, then to modernize, but doesn't stop there, use our native services, you know, get the business outcomes using this. So I think that's, that's exactly what we are going through. >> Ashish Dhawan director of global sales and go to market for VMware cloud and AWS. I want to thank you for coming on, but I'll give you the final minute. Give a plug, explain what is the VMware cloud on AWS. Why is it great? Why should people engage with you and the team, and what ultimately is this path look like for them going forward? >> Yeah. At the end of the day, we want our customers to have the best path to the cloud, right? The best path to the cloud is making sure that they migrate safely, reliably, and securely as well as with speed, right? And then, you know, use that cloud platform to utilize AWS's native services to make sure that they modernize their IT infrastructure and applications, right? We want, ultimately that our customer's, customer's, customer get the best out of, you know, utilizing that whole application experience is enhanced tremendously by using our services. And I think that's exactly what we are working towards VMware cloud on AWS is helping our customers in that journey towards migrating, modernizing, whether they want to exit a data center or whether they want to modernize their applications. It's in this central first step that we want to help our customers with. >> Ashish Dhawan, director of global sales and go to market with VMware cloud on AWS. He's with AWS sharing his thoughts on accelerating business transformation on AWS. This is showcase. We're talking about the future path. We're talking about use cases with success stories from customers. Ashish, thank you for spending time today on this showcase. >> Thank you, John. I appreciate it. >> Okay. This is the cube, special coverage, special presentation of the AWS Showcase. I'm John Furrier. Thanks for watching. (techno tones)

(upbeat music) >> Okay, we're back covering AWS Storage Day 2022 with Ashish Palekar. Who's the general manager of AWS EBS Snapshot and Edge and Cami Tavares. Who's the head of product at Amazon EBS. Thanks for coming back in theCube guys. Great to see you again. >> Great to see you as well, Dave. >> Great to see you, Dave. Ashish, we've been hearing a lot today about companies all kinds of applications to the cloud and AWS and using their data in new ways. Resiliency is always top of mind for companies when they think about just generally their workloads and specifically the clouds. How should they think about customers think about data resiliency? >> Yeah, when we think about data resiliency it's all about making sure that your application data, the data that your application needs is available when it needs it. It's really the ability for your workload to mitigate disruptions or recover from them. And to build that resilient architecture you really need to understand what kinds of disruptions your applications can experience. How broad the impact of those disruptions is, and then how quickly you need to recover. And a lot of this is a function of what the application does, how critical it is. And the thing that we constantly tell customers is, this works differently in the cloud than it does in a traditional on-premises environment. >> What's different about the cloud versus on-prem? Can you explain how it's different? >> Yeah, let me start with a video on-premises one. And in the on-premises one, building resilient architectures is really the customer's responsibility, and it's very challenging. You'll start thinking about what your single points of failure are. To avoid those, you have to build in redundancy, you might build in replication as an example for storage and doing this now means you have to have provision more hardware. And depending on what your availability requirements are, you may even have to start looking for multiple data centers, some in the same regions, some in different geographical locations. And you have to ensure that you're fully automated, so that your recovery processes can take place. And as you can see that's a lot of owners being placed on the customer. One other thing that we hear about is really elasticity and how elasticity plays into the resiliency for applications. As an example, if you experience a sudden spike in workloads, in a on-premises environment, that can lead to resource saturation. And so really you have two choices. One is to sort of throttle the workload and experience resiliency, or your second option becomes buying additional hardware and securing more capacity and keeping it fair low in case of experiencing such a spike. And so your two propositions that are either experiencing resiliency, challenges or paying really to have infrastructure that's lying around. And both of those are different really when you start thinking about the cloud. >> Yeah, there's a third option too, which is lose data, which is not an option. Go ahead- >> Which is not, yeah, I pretty much as a storage person, that is not an option. The reason about that that we think is reasonable for customers to take. The big contrast in the cloud really comes with how we think about capacity. And fundamentally the the cloud gives you that access to capacity so you are not managing that capacity. The infrastructure complexity and the cost associated with that are also just a function of how infrastructure is built really in the cloud. But all of that really starts with the bedrock of how we design for avoiding single points of failure. The best way to explain this is really to start thinking about our availability zones. Typically these availability zones consist of multiple data centers, located in the same regional area to enable high throughput and low latency for applications. But the availability zones themselves are physically independent. They have independent connections to utility power, standalone backup power resources, independent mechanical services and independent network connectivity. We take availability zone independence extremely seriously, so that when customers are building the availability of their workload, they can architect using these multiple zones. And that is something that when I'm talking to customers or Tami is talking to customers, we highly encourage customers to keep in mind as they're building resiliency for their applications. >> Right, so you can have within an availability zone, you can have, you know, instantaneous, you know when you're doing it right. You've got, you've captured that data and you can asynchronously move to outside of that in case there's, the very low probability, but it does happen, you get some disasters. You're minimizing that RPO. And I don't have to worry about that as a customer and figuring out how to do three site data centers. >> That's right. Like that even further, now imagine if you're expanding globally. All those things that we described about like creating new footprint and creating a new region and finding new data centers. As a customer in an on-premises environment, you take that on yourself. Whereas with AWS, because of our global presence, you can expand to a region and bring those same operational characteristics to those environments. And so again, bringing resiliency as you're thinking about expanding your workload, that's another benefit that you get from using the availability zone region architecture that AWS has. >> And as Charles Phillips, former CEO of Infor said, "Friends, don't let friends build data center," so I don't have to worry about building the data center. Let's bring Cami into the discussion here. Cami, think about elastic block storage, it gives, you know customers, you get persistent block storage for EC2 instances. So it's foundational for any mission critical or business critical application that you're building on AWS. How do you think about data resiliency in EBS specifically? I always ask the question, what happens if something goes wrong? So how should we think about data resiliency in EBS specifically? >> Yeah, you're right Dave, block storage is a really foundational piece. When we talk to customers about building in the cloud or moving an application to the cloud, and data resiliency is something that comes up all the time. And with EBS, you know EBS is a very large distributed system with many components. And we put a lot of thought and effort to build resiliency into EBS. So we design those components to operate and fail independently. So when customers create an EBS volume for example, we'll automatically choose the best storage nodes to address the failure domain and the data protection strategy for each of our different volume types. And part of our resiliency strategy also includes separating what we call a volume life cycle control plane. Which are things like creating a volume, or attaching a volume to an EC2 instance. So we separate that control plane, from the storage data plane, which includes all the components that are responsible for serving IO to your instance, and then persisting it to durable media. So what that means is once a volume is created and attached to the instance, the operations on that volume they're independent from the control point function. So even in the case of an infrastructure event, like a power issue, for example, you can recreate an EBS volume from a snapshot. And speaking of snapshots, that's the other core pillar of resiliency in EBS. Snapshots are point in time copies of EBS volumes that would store in S3. And snapshots are actually a regional service. And that means internally we use multiple of the availability zones that Ashish was talking about to replicate your data so that the snapshots can withstand the failure of an availability zone. And so thanks to that availability zone independence, and then this builtin component independence, customers can use that snapshot and recreate an EBS following another AZO or even in another region if they need to. >> Great so, okay, so you touched on some of the things EBS does to build resiliency into the service. Now thinking about over your right shoulders, you know, Joan Deviva, so what can organizations do to build more resilience into their applications on EBS so they can enjoy life without anxiety? >> (laughs) That is a great question. Also something that we love to talk to customers about. And the core thing to think about here is that we don't believe in a one size fits all approach. And so what we are doing in EBS is we give customers different tools so that they can design a resiliency strategy that is custom tailored for their data. And so to do this, this resiliency assessment, you have to think about the context of this specific workload and ask questions like what other critical services depend on this data and what will break if this data's not available and how long can can those systems withstand that, for example. And so the most important step I'll mention it again, snapshots, that is a very important step in a recovery plan. Make sure you have a backup of your data. And so we actually recommend that customers take the snapshots at least daily. And we have features that make that easier for you. For example, Data Lifecycle Manager which is a feature that is entirely free. It allows you to create backup policies, and then you can automate the process of creating the snapshot, so it's very low effort. And then when you want to use that backup to recreate a volume, we have a feature called Fast Snapshot Restore, that can expedite the creation of the volume. So if you have a more, you know a shorter recovery time objective you can use that feature to expedite the recovery process. So that's backup. And then the other pillar we talked to customers about is data replication. Just another very important step when you're thinking about your resiliency and your recovery plans. So with EBS, you can use replication tools that work at the level of the operating system. So that's something like DRBD for example. Or you can use AWS Elastic Disaster Recovery, and that will replicate your data across availability zones or nearby regions too. So we talked about backup and replication, and then the last topic that we recommend customers think about is having a workload monitoring solution in place. And you can do that in EBS, using cloud watch metrics. So you can monitor the health of your EBS volume using those metrics. We have a lot of tips in our documentation on how to measure that performance. And then you can use those performance metrics as triggers for automated recovery workflows that you can build using tools like auto scaling groups for example. >> Great, thank you for that advice. Just quick follow up. So you mentioned your recommendation, at least daily, what kind of granularity, if I want to compress my RPO can I go at a more granular level? >> Yes, you can go more granular and you can use again the daily lifecycle manager to define those policies. >> Great, thank you. Before we go, I want to just quickly cover what's new with EBS. Ashish, maybe you could talk about, I understand you've got something new today. You've got an announcement, take us through that. >> Yeah, thanks for checking in and I'm so glad you asked. We talked about how snapshots help resilience and are a critical part of building resilient architectures. So customers like the simplicity of backing up their EC2 instances, using multi volume snapshots. And what they're looking for is the ability to back up only to exclude specific volumes from the backup, especially those that don't need backup. So think of applications that have cash data, or applications that have temporary data that really doesn't need backup. So today we are adding a new parameter to the create snapshots API, which creates a crash consistent set of snapshots for volumes attached to an EC2 instance. Where customers can now exclude specific volumes from an instance backup. So customers using data life cycle manager that can be touched on, can automate their backups. And again they also get to exclude these specific volumes. So really the feature is not just about convenience, but it's also to help customers save on cost. As many of these customers are managing tens of thousands of snapshots. And so we want to make sure they can take it at the granularity that they need it. So super happy to bring that into the hands of customers as well. >> Yeah, that's a nice option. Okay, Ashish, Cami thank you so much for coming back in theCube, helping us learn about what's new and what's cool and EBS, appreciate your time. >> Thank you for having us Dave. >> Thank you for having us Dave. >> You're very welcome now, if you want to learn more about EBS resilience, stay right here because coming up, we've got a session which is a deep dive on protecting mission critical workloads with Amazon EBS. Stay right there, you're watching theCube's coverage of AWS Storage Day 2022. (calm music)

(upbeat music) >> Welcome back to theCUBE's continuous coverage of AWS storage day. My name is Dave Vellante and we're here from Seattle. And we're going to look at the really hard workloads, those business and mission critical workloads, the most sensitive data. They're harder to move to the cloud. They're hardened. They have a lot of technical debt. And the blocker in some cases has been storage. Ashish Palekar is here. He's the general manager of EBS snapshots, and he's joined by Cami Tavares who's a senior manager of product management for Amazon EBS. Folks, good to see you. >> Ashish: Good to see you again Dave. >> Dave: Okay, nice to see you again Ashish So first of all, let's start with EBS. People might not be familiar. Everybody knows about S3 is famous, but how are customers using EBS? What do we need to know? >> Yeah, it's super important to get the basics, right? Right, yeah. We have a pretty broad storage portfolio. You talked about S3 and S3 glacier, which are an object and object and archival storage. We have EFS and FSX that cover the file site, and then you have a whole host of data transfer services. Now, when we think about block, we think of a really four things. We think about EBS, which is the system storage for EC2 volumes. When we think about snapshots, which is backups for EBS volumes. Then we think about instant storage, which is really a storage that's directly attached to an instance and manages and then its life cycle is similar to that of an instance. Last but not the least, data services. So things like our elastic volumes capability of fast snapshot restore. So the answer to your question really is EBS is persistent storage for EC2 volumes. So if you've used EC2 instances, you'll likely use EBS volumes. They service boot volumes and they service data volumes, and really cover a wide gamut of workloads from relational databases, no SQL databases, file streaming, media and coding. It really covers the gamut of workloads. >> Dave: So when I heard SAN in the cloud, I laughed out loud. I said, oh, because I could think about a box, a bunch of switches and this complicated network, and then you're turning it into an API. I was like, okay. So you've made some announcements that support SAN in the cloud. What, what can you tell us about? >> Ashish: Yeah, So SANs and for customers and storage, those are storage area networks, really our external arrays that customers buy and connect their performance critical and mission critical workloads. With block storage and with EBS, we got a bunch of customers that came to us and said, I'm thinking about moving those kinds of workloads to the cloud. What do you have? And really what they're looking for and what they were looking for is performance availability and durability characteristics that they would get from their traditional SANs on premises. And so that's what the team embarked on and what we launched at reinvent and then at GEd in July is IO2 block express. And what IO2 block express does is it's a complete ground app, really the invention of our storage product offering and gives customers the same availability, durability, and performance characteristics that can, we'll go into little later about that they're used to in their on premises. The other thing that we realized is that it's not just enough to have a volume. You need an instance that can drive that kind of throughput and IOPS. And so coupled with our trends in EC2 we launched our R5b that now triples the amount of IOPS and throughput that you can get from a single instance to EBS storage. So when you couple the sub millisecond latency, the capacity and the performance that you get from IO2 block express with R5b, what we hear from customers is that gives them enough of the performance availability characteristics and durability characteristics to move their workloads from on premises, into the cloud, for the mission critical and business critical apps. >> Dave: Thank you for that. So Cami when I, if I think about how the prevailing way in which storage works, I drop off a box at the loading dock and then I really don't know what happens. There may be a service organization that's maybe more intimate with the customer, but I don't really see the innovations and the use cases that are applied clouds, different. You know, you live it every day. So you guys always talk about customer inspired innovation. So what are you seeing in terms of how people are using this capability and what innovations they're driving? >> Cami: Yeah, so I think when we look at the EBS portfolio and this, the evolution over the years, you can really see that it was driven by customer need and we have different volume types and they have very specific performance characteristics, and they're built to meet these unique needs of customer workloads. So I'll tell you a little bit about some of our specific volume types to kind of illustrate this evolution over the years. So starting with our general purpose volumes, we have many customers that are using these volumes today. They really are looking for high performance at a low cost, and you have all kinds of transactional workloads and low-latency interactive applications and boot volumes, as Ashish mentioned. And they tell us, the customer is using these general purpose volumes, they tell us that they really like this balanced cost and performance. And customers also told us, listen, I have these more demanding applications that need higher performance. I need more IOPS, more throughput. And so looking at that customer need, we were really talking about these IO intensive applications like SAP HANA and Oracle and databases that require just higher durability. And so we looked at that customer feedback and we launched our provisioned IOPS IO2 volume. And with that volume, you get five nines of durability and four times the IOPS that you would get with general purpose volumes. So it's a really compelling offering. Again, customers came to us and said, this is great. I need more performance, I need more IOPS, more throughput, more storage than I can get with a single IO2 volume. And so these were talking about, you mentioned mission critical applications, SAP HANA, Oracle, and what we saw customers doing often is they were striping together multiple IO2 volumes to get the maximum performance, but very quickly with the most demanding applications, it got to a point where we have more IO2 volumes that you want to manage. And so we took that feedback to heart and we completely reinvented the underlying EBS hardware and the software and networking stacks. And we'll launched block express. With block express, you can get four times the IOPS throughput and storage that you would get with a single io2 volume. So it's a really compelling offering for customers. >> Dave: If I had to go back and ask you, what was the catalyst, what was the sort of business climate that really drove the decision here. Was that people were just sort of fed up with you know, I'll use the phrase, the undifferentiated, heavy lifting around SAN, what was it, was it COVID driven? What was the climate? >> You know, it's important to recognize when we are talking about business climate today, every business is a data business and block storage is really a foundational part of that. And so with SAN in the cloud specifically, we have seen enterprises for several years, buying these traditional hardware arrays for on premises SANs. And it's a very expensive investment. Just this year alone, they're spending over $22 billion on SANs. And with this old model on premises SANs, you would probably spend a lot of time doing this upfront capacity planning, trying to figure out how much storage you might need. And in the end, you'd probably end up overbuying for peak demand because you really don't want to get stuck, not having what you need to scale your business. And so now with block express, you don't have to do that anymore. You pay for what you need today, and then you can increase your storage as your business needs change. So that's cost and cost is a very important factor. But really when we're talking to customers and enterprises that are looking for SAN in the cloud, the number one reason that they want to move to the cloud with their SANs and these mission, critical workloads is agility and speed. And it's really transformational for businesses to be able to change the customer experience for their customers and innovate at a much faster pace. And so with the block express product, you get to do that much faster. You can go from an idea to an implementation orders of magnitude faster. Whereas before if you had these workloads on premises, it would take you several weeks just to get the hardware. And then you have to build all this surrounding infrastructure to get it up and running. Now, you don't have to do that anymore. You get your storage in minutes, and if you change your mind, if your business needs change, if your workloads change, you can modify your EBS volume types without interrupting your workload. >> Dave: Thank you for that. So Cami kind of addressed some of this, but I know store admins say, don't touch my SAN, I'm not moving it. This is a big decision for a lot of people. So kind of a two-part question, you know, why now, what do people need to know? And give us the north star close it out with, with where you see the future. >> Ashish: Yeah, so let's, I'll kick things off and then Cami, do jump in. So first of the volume is one part of the story, right? And with IO2 block express, I think we've given customers an extremely compelling offering to go build their mission critical and business critical applications on. We talked about the instance type R5b in terms of giving that instance level performance, but all this is on the foundation of AWS in terms of availability zones and regions. So you think about the constructs and we talk them in terms of building blocks, but our building blocks are really availability zones and regions. And that gives you that core availability infrastructure that you need to build your mission critical and business critical applications. You then take layer on top of that our regional footprint, right. And now you can spin up those workloads globally, if you need to. And then last but not the least, once you're in AWS, you have access to other services. Be it AI, be it ML, be it our relational database services that you can start to think about undifferentiated, heavy lifting. So really you get the smorgasbord really from the availability footprint to global footprint and all the way up to sort of our service stack that you get access to. >> Dave: So that's really thinking out of the box. We're out of time. Cami we'll give you the last word. >> Cami: I just want to say, if you want to learn more about EBS, there's a deep dive session with our principal engineer, Marc Olson later today. So definitely join that. >> Dave: Folks, thanks so much for coming to theCUBE. (in chorus )Thank you. >> Thank you for watching. Keep it right there for more great content from AWS storage day from Seattle.

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

>>This is Dave Violante. We're here at a W s with the Keep talking About Storage palate cars. Here is the director of product management for E B s Elastic block storage. Welcome. Good to see again. >>Nice to see it. If >>so, let's talk about E b s. You know, it all started with us. Three and course customers demand Maur. What do we need to know about E b s? Like, what are the options that you provide? Give us the late low down. >>Yeah. So the way to think about block storage in the AWS eight abreast constructors. Really two kinds of offerings. One is around instant storage, which is a form of block strategy. And then you have a block started service, which is E. B s Andi. Sort of. The key thing they're from customer standpoint of different shit between the two is if you warn your storage like cycle to be coincident with your instance like cycle, then you use instant surgeon. That's why we see a lot of our customers using since storage, because they won't want that experience if you want. On the other hand, it's storage life cycle that's different from your instance life cycle. So the ability to change instances, the ability to grow size is the ability to to take back ups. Then you want to choose the obvious experience. And there we have a series of volume types that customers can consume. Be a GP two we have, I want. We have our stream volumes, which are a C one and C one. >>So she's when you talk to customers of block stores. What did they tell you that they most care about? >>Yeah, uh, it is. It is a Lord around performance. It is a lot around. Availability is a lot on your ability. He's a fuse. Those of the core characteristics that that customers care about earlier this year as an example, one of the things that we launched for customers was the ability to encrypt their volumes by default on you. Say, Well, why is that important? So security becomes a big concern for customers a day as they think about their environment and with encryption by default. We just made it simple. With a single setting, you can now, at an account level, ensure that all your PBS volumes created from that point on our fully encrypted. >>Okay, let's talk about snapshots. So how o r r. Snapshots in the cloud? Different. And how are your customers using stamps? >>Yeah, that's great. Great. Great. Cigarette in tow. Common conversation. Customers who are coming from on premises environment are used to snapshots is being sort of this copy on right type attack volumes. The way to think about aws snapshot. Devious snapshots in particular are really to think of them as backup. And so that is the one sort of key thing that I always tell customers is to think of what we call snapshots, really as backups. Especially if you're coming from a non premises environment. >>Okay, um, how about things you're doing to really improve? Uh, EBS snapshots. I mean, is it more performance? Is it making simple Are expanding use cases. Yeah. >>Yeah. Let's talk about the use case scenario Is that that snapshots get use, and snapshots are really the underlying storage for water called Amazon machine images. Our aim eyes. That is how snaps that is, how our instances boot. That is also the way that customers create CBS Williams from, so you can create an obvious volume from a snapshot. So on that on that particular use case, one of the things that we're we're now launching is a capability via calling far snapshot restored. So you can now take a knee, be a snapshot and then within an availability is soon. Make it such that you can. You can now launch volumes from it without encountering any Leighton sing and back on DDE. That we think is a tremendously powerful capability for customs. Because if you can, it takes away all the undifferentiated heavy lifting that they had to do in order to lure the data from the snapshot into the volume completely out of the picture and allows them to focus on getting their data to their applications. That's right. >>All right, we'll give you the last word. Final thoughts on the innovations that you had. Congratulations on all the hard work. >>No, actually, this is the team has done a tremendous amount of work in art launches. Couldn't be happier to see this in the hands of customers. We look forward to seeing what they build from from the things that we provided them so excited to see that happen. >>That's actually quite amazing. It started all very simple with us three. And now we've seen service is just become more granular. Higher performance. Really meeting customer demands. She's thanks so much. Thank you so much. All right. Thanks for watching. Your body will be back right after this short break.

>> Presenter: Live from San Francisco, it's theCUBE, covering Oracle OpenWorld 2016. Brought to you by Oracle. Now, here's your hosts, John Furrier and Peter Burris. >> Welcome back, everyone. We are here live in San Francisco, for three days of wall-to-wall coverage of Oracle OpenWorld 2016. The big story, Oracle moving through the cloud. I'm John Furrier with SiliconANGLE. My cohost this week, Peter Burris, head of Research at SiliconANGLE Media, General Manager of Wikibon Research. Our next guest is Ashish Mohindroo, who is the Vice President of Oracle Cloud on the good old market side. Welcome to theCUBE, good to see you. >> Thanks John, same here. >> John: We have a mutual friend from Prasada. (laughter) Say hello. >> Hi Prakash! >> John: Prakash! He's good. Okay, entrepreneurs are all moving to the cloud, obviously it's a green field for them. But Oracle is a big company, this is clearly the mandate, this isn't cloud washing. People are saying oh they're cloud washing, but not really, Oracle is putting the effort in, we've been watching and documenting it. Obviously some critical analysis that's due here and there but for the most part, the progression is good, they're moving to the cloud. Can you give us an update because SaaS business, everyone sees that, knows that, the Platform as a Service, last year, was the big push, a lot of progress, so give us a quick one minute overview of what's the update on PaaS, Platform as a Service, and what's different this year about Infrastructure as a Service. >> Definitely, well thanks John, I think you hit the nail on the head with the fact that Oracle is the biggest secret in the industry, being the biggest cloud company, right, the most exciting cloud company in the valley. What we've really done is if you look at our numbers, we just announced our Q1 earnings, our business SaaS and PaaS business grew about 77%. It's the fastest growing SaaS and PaaS growth rate in the industry, compared to any other vendor, including Amazon, including Microsoft, and if you compare that to the Q4 numbers, where we grew at 66%, that was again faster than Amazon and Microsoft. So the market is expanding and Oracle is the fastest growing business in there. In addition to that-- >> John: By revenue or by percentage growth? >> By percentage growth. So we're close to about a $4 billion run rate on SaaS and PaaS as of Q1 FY17. >> That's across all the different, as a service? >> It's primarily SaaS, PaaS infrastructure and overall cloud revenue for us. >> John: Okay, got it. >> A big chunk of that is attributed to SaaS and PaaS. Now I want to give you some other statistics in terms of the size of our cloud business. You know there are about 98 million plus daily active users on a cloud. In addition, we do about 50 billion plus transactions a day on Oracle Cloud, right, so the massive scale, but we are operating across 195 different countries and growing, we have 19 plus regional data centers, I mean expanding more into China and Middle East, so the growth and the pace and the expansion of the business is massive and we believe that this market is growing at such an unprecedented rate that Oracle is well positioned to take advantage of that and really provide and end-to-end offerings to our customers. >> Larry Ellison in his key note last night and Rob Hope, our Editor in Chief at SiliconANGLE, who runs our editorial, grabbed the head line, his quote was Amazon, talking to Amazon, Amazon, your lead is over. Okay, what does that mean? What does that mean? Saying that your lead is over in the sense that we're closing the gap or enjoy it while you have it, we're coming after you? >> A number of things. One is that we're really making new exciting announcements into the infrastructure of the service play market. So you're going to hear within the next couple of days in terms of new offerings. We today announced the fact that we expanded our infrastructure's service capabilities from virtualized environments to also bare metal, which is something that Amazon doesn't offer. And the advantage of that is that companies can now run more high performance applications on bare metal service, versus being bothered by having to share that capacity to compute space with other applications and other customers. The other big thing what Oracle is doing is providing an end-to-end offering. So if you think about it, right, Amazon started out being with a compute layer. They said look, if you want to spin up a server, and just have to compute capacity, storage capacity, great, you don't need to invest in that, you don't need to buy it on premise, you can go to us. What customers are really looking for is yes, you can spin up a server, then what do you do next? You got to be able to build an application, you got to be able to scale that application, monitor that application, integrate that application, run analytics on that, and then at some point, do an end-of-life. So you want to have a complete application life cycle and management so you need an integrated capabilities. Today if you look at the public cloud offerings, you got to piece that together for multiple vendors. Even in Amazon, they provide you the basic services, but then you have to go to their partners to kind of fill in those pieces, manage multiple contracts, worry about integration, Oracle is providing an end-to-end capability. So today we also announced 19 plus additional services on our PaaS layer, from databases to integration, to IOT, so we are really providing you everything you need to not only get your data center moving towards the cloud but also your application development, integration, and management capabilities, that have not been available in the market today from a single vendor. So Oracle, with Larry, what he was really claiming was the market is up for grabs, we are the only vendor providing everything from end-to-end and we are going to be aggressively competing in the core infrastructure space with our new expanded offerings. >> What do you think Oracle's biggest advantage is? >> Sorry? >> What do you think Oracle's biggest advantage in the cloud is? I mean, you talked about the size of it, what do you think, fundamentally, is going to set Oracle apart from everybody else in the cloud? >> So part of that is the comprehensive nature of our offerings. From IAS to PaaS to SaaS. There's no other vendor that has that breadth. Customers are looking for a single throat to choke, in some ways, or a single vendor to deal with for a majority of the services, so we have a big advantage there. The second is our application ecosystem. If you look at the number of customers we have, the size of our offerings from ERP to CRM, to ACM, you can see that we provide everything, there's an economy around that, so customers want to build extensions, they want to integrate through these applications, and they really want to drive their business to one primary vendor, so Oracle has that advantage. The other stuff as we look at the cloud environment today, only 6% of all workloads are running on public infrastructure. That's growing at about 50% year over year. Now, 90% plus of workloads are still relying on on-premise environments, where do you think those are running on? Those are primarily running on Oracle infrastructures, whether it's Oracle databases, Oracle metalware, or also on-premise Oracle applications. So we believe customers want to have the same enterprise-grade capabilities on the cloud, which we've been working on for 40 years, now we learn from that experience, we learned from what our competitors have done over the last ten years, we bring that together to our new cloud infrastructure, PaaS and SaaS offerings. So from a technology perspective, the breadth perspective, and the customer experience perspective, we believe Oracle has a tremendous advantage, which is kind of hard to close a gap for it in terms of other competitors. >> The declining revenue on licenses, and the earnings call was pointed out, some color was given by Mark Heard on that but the growth in cloud was higher than the decline in on-prem licenses. And then Larry came over the top and said well, Microsoft has been moving all their customers to the cloud, we really haven't moved our people over. And then Mark Heard said we're in the long game, I'm kind of playing at that I want to get to a question, which is interesting, the database is very sticky. You guys have an in to all of your applications so it seems to me that the core of the show here is talking about infrastructure as a service, seem to be table stays low cost, high performance, comodotize the IaaS, and then move your customers over. Is that the strategy, is that just the timing? Am I over-reading into this thing, is it a conspiracy theory? >> What it is actually is that customers want high-quality, high-performance capabilities in the cloud, right? They've been used to building their own data centers. There's a reason for that. They could choose the infrastructure that they wanted, the servers that they wanted, the stories they wanted, the compute capacity they really needed, and they want the same experience on the public cloud. But cost was a big factor. So if you look at Amazon, it's very easy to get started but as your application scales, the cost starts to ramp, accelerate really fast, and customers are very wary of that fact that is this really a cost benefit for me in the long run to move to Amazon. One example is a company like Dropbox. That was in the news that brought back the infrastructure from Amazon to in-house, right? Couple of things for that, one was they wanted a better infrastructure and secondly they wanted to lower the costs. With Oracle, what we are saying is cost is a big factor for you to move to the cloud. We're going to take that away. We're going to make sure that you're getting the best performance, the best infrastructure, at the lowest cost possible in the industry, then we're going to give you capabilities to brace moving to the cloud, to migrate to the cloud. You're not going to say only build cloud-native applications in the cloud, but how do you take all these critical business applications, the core infrastructure that you're running today, and be able to transition that to the cloud, so we have new capabilities that we're introducing and infrastructures to servers, called Ravello Cloud Service, for example, that can literally do a lift and shift of all your V-Ems, of virtualized environment workloads, to the cloud. You don't have to rewrite them, you don't have to reconfigure them, all it does is simply point and click and you got them moving there. Nobody in the industry has that native cability coming with us. So we understand the challenges that other companies are going through, and we're giving them the capabilities and a path to move there. On top of that, Oracle went through a similar transition, so we learned a lot from our own internal transition. We went from on-premise systems to actually moving our internal systems to the Oracle Cloud. So we understood the pain, the challenges, and the opportunities that provided us to get that and we bring that same experience back to our customers. >> And as my final question for you, if you could take a minute and explain kind of what you do at Oracle but mainly, what going on in the field. As you guys take this to the customers, what are some of the things you're working on, do you have any events coming up, what's your road map for activities, and how are customers are engaging with Oracle? >> Very good questions, so my responsibility is go to market for Oracle Cloud, so especially for IaaS and PaaS. What we're noticing with our customers is every single conversation that we engage in, any size customer, whether it's a Fortune 500 customer, mid-size, or even a small company, they're all interested in either building out new applications in the cloud, migrating to the cloud, or really retiring their entire data center, and then moving all the workloads into the cloud. So we are noticing the tremendous amount of interest. They're all figuring out strategies of how do you get there. A lot of interest in hybrid clouds. So customers are going to start with new applications, up their applications in the cloud, but they'll still want to retain, because of regulatory compliance, security purposes, some applications in-house, so they want to know how do you kind of built out these hybrid cloud capabilities where you can have the same business model of subscription, metered offerings, within their own data center, and at the same time have the same flexibility to move to the cloud. So for that, we got to introduce our Oracle Cloud machine, or cloud customer capabilities that gives them that option, the flexibility to decide and move at their own pace. >> John: So a lot of education. >> Sorry? >> So you're doing a lot of education. >> Tremendous amount of education, we're actually going to be doing about a 50 plus city roadshow with our Cloud Days and Cloud World, close to OpenWorld. We're doing a lot of virtual-- >> So Cloud World is going to continue, we did the Cloud World in DC with theCUBE there, that was great. You going to do more of those regionally? >> We're going to do a global tour starting in October. We're actually going to be covering AMIA, APAC, North America, and even Latin America and South America so we're going across the world, going to different countries, I think we're covering about 50 plus countries in those events and basically spreading the word out and engaging with every kind of customer to educate them on Oracle and also give them a-- >> So big tent events in regions and then city events, satellite events to hub and spoke off those kinds of activities. >> Absolutely, yes. And doing a lot on the virtual as well, online. >> Yeah. Any virtual reality, walk into an Oracle database with my headset, look at this scheme, it's all screwed up! >> Ashish: That will be the next time around, we aren't there yet for that one. >> Thanks so much for sharing your insight and good luck with your activities, great to see you, thanks for coming on. >> Thanks John, thanks man. >> Alright, we are here live at Oracle OpenWorld and if you want to join the conversation, go to Twitter and check out the hashtag #thecube, go to siliconangle.com and check out the research at wikibon.com and of course, go to siliconangle.tv, I'm John Furrier, Peter Burris live here in San Francisco for Oracle OpenWorld 2016. In fact, there's more after this short break. (techno music)

>>Hi everyone. Welcome to the Cube special presentation here in Palo Alto, California. I'm John Foer, host of the Cube. We've got two great guests, one for calling in from Germany, our videoing in from Germany, one from Maryland. We've got VMware and aws. This is the customer successes with VMware cloud on AWS showcase, accelerating business transformation here in the showcase with Samir Candu Worldwide. VMware strategic alliance solution, architect leader with AWS Samir. Great to have you and Daniel Re Myer, principal architect global AWS synergy at VMware. Guys, you guys are, are working together. You're the key players in the re relationship as it rolls out and continues to grow. So welcome to the cube. >>Thank you. Greatly appreciate it. >>Great to have you guys both on, As you know, we've been covering this since 2016 when Pat Geling, then CEO and then then CEO AWS at Andy Chasy did this. It kind of got people by surprise, but it really kind of cleaned out the positioning in the enterprise for the success. OFM workloads in the cloud. VMware's had great success with it since, and you guys have the great partnerships. So this has been like a really strategic, successful partnership. Where are we right now? You know, years later we got this whole inflection point coming. You're starting to see, you know, this idea of higher level services, more performance are coming in at the infrastructure side. More automation, more serverless, I mean, and a, I mean it's just getting better and better every year in the cloud. Kinda a whole nother level. Where are we, Samir? Let's start with you on, on the relationship. >>Yeah, totally. So I mean, there's several things to keep in mind, right? So in 2016, right, that's when the partnership between AWS and VMware was announced, and then less than a year later, that's when we officially launched VMware cloud on aws. Years later, we've been driving innovation, working with our customers, jointly engineering this between AWS and VMware day in, day out. As far as advancing VMware cloud on aws. You know, even if you look at the innovation that takes place with a solution, things have modernized, things have changed, there's been advancements, you know, whether it's security focus, whether it's platform focus, whether it's networking focus, there's been modifications along the way, even storage, right? More recently, one of the things to keep in mind is we're looking to deliver value to our customers together. These are our joint customers. So there's hundreds of VMware and AWS engineers working together on this solution. >>And then factor in even our sales teams, right? We have VMware and AWS sales teams interacting with each other on a constant daily basis. We're working together with our customers at the end of the day too. Then we're looking to even offer and develop jointly engineered solutions specific to VMware cloud on aws, and even with VMware's, other platforms as well. Then the other thing comes down to is where we have dedicated teams around this at both AWS and VMware. So even from solutions architects, even to our sales specialists, even to our account teams, even to specific engineering teams within the organizations, they all come together to drive this innovation forward with VMware cloud on AWS and the jointly engineered solution partnership as well. And then I think one of the key things to keep in mind comes down to we have nearly 600 channel partners that have achieved VMware cloud on AWS service competency. So think about it from the standpoint there's 300 certified or validated technology solutions, they're now available to our customers. So that's even innovation right off the top as well. >>Great stuff. Daniel, I wanna get to you in a second. Upon this principal architect position you have in your title, you're the global a synergy person. Synergy means bringing things together, making it work. Take us through the architecture, because we heard a lot of folks at VMware explore this year, formerly world, talking about how the, the workloads on it has been completely transforming into cloud and hybrid, right? This is where the action is. Where are you? Is your customers taking advantage of that new shift? You got AI ops, you got it. Ops changing a lot, you got a lot more automation edges right around the corner. This is like a complete transformation from where we were just five years ago. What's your thoughts on the >>Relationship? So at at, at first, I would like to emphasize that our collaboration is not just that we have dedicated teams to help our customers get the most and the best benefits out of VMware cloud on aws. We are also enabling US mutually. So AWS learns from us about the VMware technology, where VMware people learn about the AWS technology. We are also enabling our channel partners and we are working together on customer projects. So we have regular assembled globally and also virtually on Slack and the usual suspect tools working together and listening to customers, that's, that's very important. Asking our customers where are their needs? And we are driving the solution into the direction that our customers get the, the best benefits out of VMware cloud on aws. And over the time we, we really have involved the solution. As Samia mentioned, we just added additional storage solutions to VMware cloud on aws. We now have three different instance types that cover a broad range of, of workload. So for example, we just added the I four I host, which is ideally for workloads that require a lot of CPU power, such as you mentioned it, AI workloads. >>Yeah. So I wanna guess just specifically on the customer journey and their transformation. You know, we've been reporting on Silicon angle in the queue in the past couple weeks in a big way that the OPS teams are now the new devs, right? I mean that sounds OP a little bit weird, but operation IT operations is now part of the, a lot more data ops, security writing code composing, you know, with open source, a lot of great things are changing. Can you share specifically what customers are looking for when you say, as you guys come in and assess their needs, what are they doing? What are some of the things that they're doing with VMware on AWS specifically that's a little bit different? Can you share some of and highlights there? >>That, that's a great point because originally VMware and AWS came from very different directions when it comes to speaking people at customers. So for example, aws very developer focused, whereas VMware has a very great footprint in the IT ops area. And usually these are very different, very different teams, groups, different cultures, but it's, it's getting together. However, we always try to address the customers, right? There are customers that want to build up a new application from the scratch and build resiliency, availability, recoverability, scalability into the application. But there are still a lot of customers that say, well we don't have all of the skills to redevelop everything to refactor an application to make it highly available. So we want to have all of that as a service, recoverability as a service, scalability as a service. We want to have this from the infrastructure. That was one of the unique selling points for VMware on premise and now we are bringing this into the cloud. >>Samir, talk about your perspective. I wanna get your thoughts, and not to take a tangent, but we had covered the AWS remar of, actually it was Amazon res machine learning automation, robotics and space. It was really kinda the confluence of industrial IOT software physical. And so when you look at like the IT operations piece becoming more software, you're seeing things about automation, but the skill gap is huge. So you're seeing low code, no code automation, you know, Hey Alexa, deploy a Kubernetes cluster. Yeah, I mean, I mean that's coming, right? So we're seeing this kind of operating automation meets higher level services meets workloads. Can you unpack that and share your opinion on, on what you see there from an Amazon perspective and how it relates to this? >>Yeah, totally. Right. And you know, look at it from the point of view where we said this is a jointly engineered solution, but it's not migrating to one option or the other option, right? It's more or less together. So even with VMware cloud on aws, yes it is utilizing AWS infrastructure, but your environment is connected to that AWS VPC in your AWS account. So if you wanna leverage any of the native AWS services, so any of the 200 plus AWS services, you have that option to do so. So that's gonna give you that power to do certain things, such as, for example, like how you mentioned with iot, even with utilizing Alexa or if there's any other service that you wanna utilize, that's the joining point between both of the offerings. Right off the top though, with digital transformation, right? You, you have to think about where it's not just about the technology, right? There's also where you want to drive growth in the underlying technology. Even in your business leaders are looking to reinvent their business. They're looking to take different steps as far as pursuing a new strategy. Maybe it's a process, maybe it's with the people, the culture, like how you said before, where people are coming in from a different background, right? They may not be used to the cloud, they may not be used to AWS services, but now you have that capability to mesh them together. Okay. Then also, Oh, >>Go ahead, finish >>Your thought. No, no, I was gonna say, what it also comes down to is you need to think about the operating model too, where it is a shift, right? Especially for that VS four admin that's used to their on-premises at environment. Now with VMware cloud on aws, you have that ability to leverage a cloud, but the investment that you made and certain things as far as automation, even with monitoring, even with logging, yeah. You still have that methodology where you can utilize that in VMware cloud on AWS two. >>Danielle, I wanna get your thoughts on this because at at explore and, and, and after the event, now as we prep for Cuban and reinvent coming up the big AWS show, I had a couple conversations with a lot of the VMware customers and operators and it's like hundreds of thousands of, of, of, of users and millions of people talking about and and peaked on VM we're interested in v VMware. The common thread was one's one, one person said, I'm trying to figure out where I'm gonna put my career in the next 10 to 15 years. And they've been very comfortable with VMware in the past, very loyal, and they're kind of talking about, I'm gonna be the next cloud, but there's no like role yet architects, is it Solution architect sre. So you're starting to see the psychology of the operators who now are gonna try to make these career decisions, like how, what am I gonna work on? And it's, and that was kind of fuzzy, but I wanna get your thoughts. How would you talk to that persona about the future of VMware on, say, cloud for instance? What should they be thinking about? What's the opportunity and what's gonna happen? >>So digital transformation definitely is a huge change for many organizations and leaders are perfectly aware of what that means. And that also means in, in to to some extent, concerns with your existing employees. Concerns about do I have to relearn everything? Do I have to acquire new skills? And, and trainings is everything worthless I learned over the last 15 years of my career? And the, the answer is to make digital transformation a success. We need not just to talk about technology, but also about process people and culture. And this is where VMware really can help because if you are applying VMware cloud on a, on AWS to your infrastructure, to your existing on-premise infrastructure, you do not need to change many things. You can use the same tools and skills, you can manage your virtual machines as you did in your on-premise environment. You can use the same managing and monitoring tools. If you have written, and many customers did this, if you have developed hundreds of, of scripts that automate tasks and if you know how to troubleshoot things, then you can use all of that in VMware cloud on aws. And that gives not just leaders, but but also the architects at customers, the operators at customers, the confidence in, in such a complex project, >>The consistency, very key point, gives them the confidence to go and, and then now that once they're confident they can start committing themselves to new things. Samir, you're reacting to this because you know, on your side you've got higher level services, you got more performance at the hardware level. I mean, lot improvement. So, okay, nothing's changed. I can still run my job now I got goodness on the other side. What's the upside? What's in it for the, for the, for the customer there? >>Yeah, so I think what it comes down to is they've already been so used to or entrenched with that VMware admin mentality, right? But now extending that to the cloud, that's where now you have that bridge between VMware cloud on AWS to bridge that VMware knowledge with that AWS knowledge. So I will look at it from the point of view where now one has that capability and that ability to just learn about the cloud, but if they're comfortable with certain aspects, no one's saying you have to change anything. You can still leverage that, right? But now if you wanna utilize any other AWS service in conjunction with that VM that resides maybe on premises or even in VMware cloud on aws, you have that option to do so. So think about it where you have that ability to be someone who's curious and wants to learn. And then if you wanna expand on the skills, you certainly have that capability to do so. >>Great stuff. I love, love that. Now that we're peeking behind the curtain here, I'd love to have you guys explain, cuz people wanna know what's goes on in behind the scenes. How does innovation get happen? How does it happen with the relationship? Can you take us through a day in the life of kind of what goes on to make innovation happen with the joint partnership? You guys just have a zoom meeting, Do you guys fly out, you write go do you ship thing? I mean I'm making it up, but you get the idea, what's the, what's, how does it work? What's going on behind the scenes? >>So we hope to get more frequently together in person, but of course we had some difficulties over the last two to three years. So we are very used to zoom conferences and and Slack meetings. You always have to have the time difference in mind if we are working globally together. But what we try, for example, we have reg regular assembled now also in person geo based. So for emia, for the Americas, for aj. And we are bringing up interesting customer situations, architectural bits and pieces together. We are discussing it always to share and to contribute to our community. >>What's interesting, you know, as, as events are coming back to here, before you get, you weigh in, I'll comment, as the cube's been going back out to events, we are hearing comments like what, what pandemic we were more productive in the pandemic. I mean, developers know how to work remotely and they've been on all the tools there, but then they get in person, they're happy to see people, but there's no one's, no one's really missed the beat. I mean it seems to be very productive, you know, workflow, not a lot of disruption. More if anything, productivity gains. >>Agreed, right? I think one of the key things to keep in mind is, you know, even if you look at AWS's and even Amazon's leadership principles, right? Customer obsession, that's key. VMware is carrying that forward as well. Where we are working with our customers, like how Daniel said met earlier, right? We might have meetings at different time zones, maybe it's in person, maybe it's virtual, but together we're working to listen to our customers. You know, we're taking and capturing that feedback to drive innovation and VMware cloud on AWS as well. But one of the key things to keep in mind is yes, there have been, there has been the pandemic, we might have been disconnected to a certain extent, but together through technology we've been able to still communicate work with our customers. Even with VMware in between, with AWS and whatnot. We had that flexibility to innovate and continue that innovation. So even if you look at it from the point of view, right? VMware cloud on AWS outposts, that was something that customers have been asking for. We've been been able to leverage the feedback and then continue to drive innovation even around VMware cloud on AWS outposts. So even with the on premises environment, if you're looking to handle maybe data sovereignty or compliance needs, maybe you have low latency requirements, that's where certain advancements come into play, right? So the key thing is always to maintain that communication track. >>And our last segment we did here on the, on this showcase, we listed the accomplishments and they were pretty significant. I mean go, you got the global rollouts of the relationship. It's just really been interesting and, and people can reference that. We won't get into it here, but I will ask you guys to comment on, as you guys continue to evolve the relationship, what's in it for the customer? What can they expect next? Cuz again, I think right now we're in at a, an inflection point more than ever. What can people expect from the relationship and what's coming up with reinvent? Can you share a little bit of kind of what's coming down the pike? >>So one of the most important things we have announced this year, and we will continue to evolve into that direction, is independent scale of storage. That absolutely was one of the most important items customer asked us for over the last years. Whenever, whenever you are requiring additional storage to host your virtual machines, you usually in VMware cloud on aws, you have to add additional notes. Now we have three different note types with different ratios of compute, storage and memory. But if you only require additional storage, you always have to get also additional compute and memory and you have to pay. And now with two solutions which offer choice for the customers, like FS six one, NetApp onap, and VMware cloud Flex Storage, you now have two cost effective opportunities to add storage to your virtual machines. And that offers opportunities for other instance types maybe that don't have local storage. We are also very, very keen looking forward to announcements, exciting announcements at the upcoming events. >>Samir, what's your, what's your reaction take on the, on what's coming down on your side? >>Yeah, I think one of the key things to keep in mind is, you know, we're looking to help our customers be agile and even scale with their needs, right? So with VMware cloud on aws, that's one of the key things that comes to mind, right? There are gonna be announcements, innovations and whatnot with outcoming events. But together we're able to leverage that to advance VMware cloud on AWS to Daniel's point storage, for example, even with host offerings. And then even with decoupling storage from compute and memory, right now you have the flexibility where you can do all of that. So to look at it from the standpoint where now with 21 regions where we have VMware cloud on AWS available as well, where customers can utilize that as needed when needed, right? So it comes down to, you know, transformation will be there. Yes, there's gonna be maybe where workloads have to be adapted where they're utilizing certain AWS services, but you have that flexibility and option to do so. And I think with the continuing events that's gonna give us the options to even advance our own services together. >>Well you guys are in the middle of it, you're in the trenches, you're making things happen, you've got a team of people working together. My final question is really more of a kind of a current situation, kind of future evolutionary thing that you haven't seen this before. I wanna get both of your reaction to it. And we've been bringing this up in, in the open conversations on the cube is in the old days it was going back this generation, you had ecosystems, you had VMware had an ecosystem they did best, had an ecosystem. You know, we have a product, you have a product, biz dev deals happen, people sign relationships and they do business together and they, they sell to each other's products or do some stuff. Now it's more about architecture cuz we're now in a distributed large scale environment where the role of ecosystems are intertwining. >>And this, you guys are in the middle of two big ecosystems. You mentioned channel partners, you both have a lot of partners on both sides. They come together. So you have this now almost a three dimensional or multidimensional ecosystem, you know, interplay. What's your thoughts on this? And, and, and because it's about the architecture, integration is a value, not so much. Innovation is only, you gotta do innovation, but when you do innovation, you gotta integrate it, you gotta connect it. So what is, how do you guys see this as a, as an architectural thing, start to see more technical business deals? >>So we are, we are removing dependencies from individual ecosystems and from individual vendors. So a customer no longer has to decide for one vendor and then it is a very expensive and high effort project to move away from that vendor, which ties customers even, even closer to specific vendors. We are removing these obstacles. So with VMware cloud on aws moving to the cloud, firstly it's, it's not a dead end. If you decide at one point in time because of latency requirements or maybe it's some compliance requirements, you need to move back into on-premise. You can do this if you decide you want to stay with some of your services on premise and just run a couple of dedicated services in the cloud, you can do this and you can mana manage it through a single pane of glass. That's quite important. So cloud is no longer a dead and it's no longer a binary decision, whether it's on premise or the cloud. It it is the cloud. And the second thing is you can choose the best of both works, right? If you are migrating virtual machines that have been running in your on-premise environment to VMware cloud on aws, by the way, in a very, very fast cost effective and safe way, then you can enrich later on enrich these virtual machines with services that are offered by aws. More than 200 different services ranging from object based storage, load balancing and so on. So it's an endless, endless possibility. >>We, we call that super cloud in, in a, in a way that we be generically defining it where everyone's innovating, but yet there's some common services. But the differentiation comes from innovation where the lock in is the value, not some spec, right? Samir, this is gonna where cloud is right now, you guys are, are not commodity. Amazon's completely differentiating, but there's some commodity things. Having got storage, you got compute, but then you got now advances in all areas. But partners innovate with you on their terms. Absolutely. And everybody wins. >>Yeah. And a hundred percent agree with you. I think one of the key things, you know, as Daniel mentioned before, is where it it, it's a cross education where there might be someone who's more proficient on the cloud side with aws, maybe more proficient with the viewers technology, but then for partners, right? They bridge that gap as well where they come in and they might have a specific niche or expertise where their background, where they can help our customers go through that transformation. So then that comes down to, hey, maybe I don't know how to connect to the cloud. Maybe I don't know what the networking constructs are. Maybe I can leverage that partner. That's one aspect to go about it. Now maybe you migrated that workload to VMware cloud on aws. Maybe you wanna leverage any of the native AWS services or even just off the top 200 plus AWS services, right? But it comes down to that skill, right? So again, solutions architecture at the back of, back of the day, end of the day, what it comes down to is being able to utilize the best of both worlds. That's what we're giving our customers at the end of the >>Day. I mean, I just think it's, it's a, it's a refactoring and innovation opportunity at all levels. I think now more than ever, you can take advantage of each other's ecosystems and partners and technologies and change how things get done with keeping the consistency. I mean, Daniel, you nailed that, right? I mean, you don't have to do anything. You still run the fear, the way you working on it and now do new things. This is kind of a cultural shift. >>Yeah, absolutely. And if, if you look, not every, not every customer, not every organization has the resources to refactor and re-platform everything. And we gave, we give them a very simple and easy way to move workloads to the cloud. Simply run them and at the same time they can free up resources to develop new innovations and, and grow their business. >>Awesome. Samir, thank you for coming on. Danielle, thank you for coming to Germany, Octoberfest, I know it's evening over there, your weekend's here. And thank you for spending the time. Samir final give you the final word, AWS reinvents coming up. Preparing. We're gonna have an exclusive with Adam, but Fry, we do a curtain raise, a dual preview. What's coming down on your side with the relationship and what can we expect to hear about what you got going on at reinvent this year? The big show? >>Yeah, so I think, you know, Daniel hit upon some of the key points, but what I will say is we do have, for example, specific sessions, both that VMware's driving and then also that AWS is driving. We do have even where we have what I call a chalk talks. So I would say, and then even with workshops, right? So even with the customers, the attendees who are there, whatnot, if they're looking for to sit and listen to a session, yes that's there. But if they wanna be hands on, that is also there too. So personally for me as an IT background, you know, been in CIS admin world and whatnot, being hands on, that's one of the key things that I personally am looking forward. But I think that's one of the key ways just to learn and get familiar with the technology. Yeah, >>Reinvents an amazing show for the in person. You guys nail it every year. We'll have three sets this year at the cube. It's becoming popular. We more and more content. You guys got live streams going on, a lot of content, a lot of media, so thanks, thanks for sharing that. Samir Daniel, thank you for coming on on this part of the showcase episode of really the customer successes with VMware Cloud Ons, really accelerating business transformation withs and VMware. I'm John Fur with the cube, thanks for watching. Hello everyone. Welcome to this cube showcase, accelerating business transformation with VMware cloud on it's a solution innovation conversation with two great guests, Fred and VP of commercial services at aws and NA Ryan Bard, who's the VP and general manager of cloud solutions at VMware. Gentlemen, thanks for joining me on this showcase. >>Great to be here. >>Hey, thanks for having us on. It's a great topic. You know, we, we've been covering this VMware cloud on abus since, since the launch going back and it's been amazing to watch the evolution from people saying, Oh, it's the worst thing I've ever seen. It's what's this mean? And depress work were, we're kind of not really on board with kind of the vision, but as it played out as you guys had announced together, it did work out great for VMware. It did work out great for a D and it continues two years later and I want just get an update from you guys on where you guys see this has been going. I'll see multiple years. Where is the evolution of the solution as we are right now coming off VMware explorer just recently and going in to reinvent, which is only a couple weeks away, feels like tomorrow. But you know, as we prepare a lot going on, where are we with the evolution of the solution? >>I mean, first thing I wanna say is, you know, PBO 2016 was a someon moment and the history of it, right? When Pat Gelsinger and Andy Jessey came together to announce this and I think John, you were there at the time I was there, it was a great, great moment. We launched the solution in 2017, the year after that at VM Word back when we called it Word, I think we have gone from strength to strength. One of the things that has really mattered to us is we have learned froms also in the processes, this notion of working backwards. So we really, really focused on customer feedback as we build a service offering now five years old, pretty remarkable journey. You know, in the first years we tried to get across all the regions, you know, that was a big focus because there was so much demand for it. >>In the second year we started going really on enterprise grade features. We invented this pretty awesome feature called Stretch clusters, where you could stretch a vSphere cluster using VSA and NSX across two AZs in the same region. Pretty phenomenal four nine s availability that applications start started to get with that particular feature. And we kept moving forward all kinds of integration with AWS direct connect transit gateways with our own advanced networking capabilities. You know, along the way, disaster recovery, we punched out two, two new services just focused on that. And then more recently we launched our outposts partnership. We were up on stage at Reinvent, again with Pat Andy announcing AWS outposts and the VMware flavor of that VMware cloud and AWS outposts. I think it's been significant growth in our federal sector as well with our federal and high certification more recently. So all in all, we are super excited. We're five years old. The customer momentum is really, really strong and we are scaling the service massively across all geos and industries. >>That's great, great update. And I think one of the things that you mentioned was how the advantages you guys got from that relationship. And, and this has kind of been the theme for AWS since I can remember from day one. Fred, you guys do the heavy lifting as as, as you always say for the customers here, VMware comes on board, takes advantage of the AWS and kind of just doesn't miss a beat, continues to move their workloads that everyone's using, you know, vSphere and these are, these are big workloads on aws. What's the AWS perspective on this? How do you see it? >>Yeah, it's pretty fascinating to watch how fast customers can actually transform and move when you take the, the skill set that they're familiar with and the advanced capabilities that they've been using on Preem and then overlay it on top of the AWS infrastructure that's, that's evolving quickly and, and building out new hardware and new instances we'll talk about. But that combined experience between both of us on a jointly engineered solution to bring the best security and the best features that really matter for those workloads drive a lot of efficiency and speed for the, for the customer. So it's been well received and the partnership is stronger than ever from an engineering standpoint, from a business standpoint. And obviously it's been very interesting to look at just how we stay day one in terms of looking at new features and work and, and responding to what customers want. So pretty, pretty excited about just seeing the transformation and the speed that which customers can move to bmc. Yeah, >>That's what great value publish. We've been talking about that in context too. Anyone building on top of the cloud, they can have their own supercloud as we call it. If you take advantage of all the CapEx and and investment Amazon's made and AWS has made and, and and continues to make in performance IAS and pass all great stuff. I have to ask you guys both as you guys see this going to the next level, what are some of the differentiations you see around the service compared to other options on the market? What makes it different? What's the combination? You mentioned jointly engineered, what are some of the key differentiators of the service compared to others? >>Yeah, I think one of the key things Fred talked about is this jointly engineered notion right from day one. We were the earlier doctors of AWS Nitro platform, right? The reinvention of E two back five years ago. And so we have been, you know, having a very, very strong engineering partnership at that level. I think from a VMware customer standpoint, you get the full software defined data center or compute storage networking on EC two, bare metal across all regions. You can scale that elastically up and down. It's pretty phenomenal just having that consistency globally, right on aws EC two global regions. Now the other thing that's a real differentiator for us that customers tell us about is this whole notion of a managed service, right? And this was somewhat new to VMware, but we took away the pain of this undifferentiated heavy lifting where customers had to provision rack, stack hardware, configure the software on top, and then upgrade the software and the security batches on top. >>So we took, took away all of that pain as customers transitioned to VMware cloud and aws. In fact, my favorite story from last year when we were all going through the lock for j debacle industry was just going through that, right? Favorite proof point from customers was before they put even race this issue to us, we sent them a notification saying we already patched all of your systems, no action from you. The customers were super thrilled. I mean these are large banks, many other customers around the world, super thrilled they had to take no action, but a pretty incredible industry challenge that we were all facing. >>Nora, that's a great, so that's a great point. You know, the whole managed service piece brings up the security, you kind of teasing at it, but you know, there's always vulnerabilities that emerge when you are doing complex logic. And as you grow your solutions, there's more bits. You know, Fred, we were commenting before we came on camera, there's more bits than ever before and, and at at the physics layer too, as well as the software. So you never know when there's gonna be a zero day vulnerability out there. Just, it happens. We saw one with fornet this week, this came outta the woodwork. But moving fast on those patches, it's huge. This brings up the whole support angle. I wanted to ask you about how you guys are doing that as well, because to me we see the value when we, when we talk to customers on the cube about this, you know, it was a real, real easy understanding of how, what the cloud means to them with VMware now with the aws. But the question that comes up that we wanna get more clarity on is how do you guys handle support together? >>Well, what's interesting about this is that it's, it's done mutually. We have dedicated support teams on both sides that work together pretty seamlessly to make sure that whether there's a issue at any layer, including all the way up into the app layer, as you think about some of the other workloads like sap, we'll go end to end and make sure that we support the customer regardless of where the particular issue might be for them. And on top of that, we look at where, where we're improving reliability in, in as a first order of, of principle between both companies. So from an availability and reliability standpoint, it's, it's top of mind and no matter where the particular item might land, we're gonna go help the customer resolve. That works really well >>On the VMware side. What's been the feedback there? What's the, what are some of the updates? >>Yeah, I think, look, I mean, VMware owns and operates the service, but we have a phenomenal backend relationship with aws. Customers call VMware for the service for any issues and, and then we have a awesome relationship with AWS on the backend for support issues or any hardware issues. The BASKE management that we jointly do, right? All of the hard problems that customers don't have to worry about. I think on the front end, we also have a really good group of solution architects across the companies that help to really explain the solution. Do complex things like cloud migration, which is much, much easier with VMware cloud aws, you know, we are presenting that easy button to the public cloud in many ways. And so we have a whole technical audience across the two companies that are working with customers every single day. >>You know, you had mentioned, I've got a list here, some of the innovations the, you mentioned the stretch clustering, you know, getting the GOs working, Advanced network, disaster recovery, you know, fed, Fed ramp, public sector certifications, outposts, all good. You guys are checking the boxes every year. You got a good, good accomplishments list there on the VMware AWS side here in this relationship. The question that I'm interested in is what's next? What recent innovations are you doing? Are you making investments in what's on the lists this year? What items will be next year? How do you see the, the new things, the list of accomplishments, people wanna know what's next. They don't wanna see stagnant growth here, they wanna see more action, you know, as as cloud kind of continues to scale and modern applications cloud native, you're seeing more and more containers, more and more, you know, more CF C I C D pipe pipelining with with modern apps, put more pressure on the system. What's new, what's the new innovations? >>Absolutely. And I think as a five yearold service offering innovation is top of mind for us every single day. So just to call out a few recent innovations that we announced in San Francisco at VMware Explorer. First of all, our new platform i four I dot metal, it's isolate based, it's pretty awesome. It's the latest and greatest, all the speeds and feeds that we would expect from VMware and aws. At this point in our relationship. We announced two different storage options. This notion of working from customer feedback, allowing customers even more price reductions, really take off that storage and park it externally, right? And you know, separate that from compute. So two different storage offerings there. One is with AWS Fsx, with NetApp on tap, which brings in our NetApp partnership as well into the equation and really get that NetApp based, really excited about this offering as well. >>And the second storage offering for VMware cloud Flex Storage, VMware's own managed storage offering. Beyond that, we have done a lot of other innovations as well. I really wanted to talk about VMware cloud Flex Compute, where previously customers could only scale by hosts and a host is 36 to 48 cores, give or take. But with VMware cloud Flex Compute, we are now allowing this notion of a resource defined compute model where customers can just get exactly the V C P memory and storage that maps to the applications, however small they might be. So this notion of granularity is really a big innovation that that we are launching in the market this year. And then last but not least, talk about ransomware. Of course it's a hot topic in industry. We are seeing many, many customers ask for this. We are happy to announce a new ransomware recovery with our VMware cloud DR solution. >>A lot of innovation there and the way we are able to do machine learning and make sure the workloads that are covered from snapshots and backups are actually safe to use. So there's a lot of differentiation on that front as well. A lot of networking innovations with Project Knot star for ability to have layer flow through layer seven, you know, new SaaS services in that area as well. Keep in mind that the service already supports managed Kubernetes for containers. It's built in to the same clusters that have virtual machines. And so this notion of a single service with a great TCO for VMs and containers and sort of at the heart of our office, >>The networking side certainly is a hot area to keep innovating on. Every year it's the same, same conversation, get better, faster networking, more, more options there. The flex computes. Interesting. If you don't mind me getting a quick clarification, could you explain the Drew screen resource defined versus hardware defined? Because this is kind of what we had saw at Explore coming out, that notion of resource defined versus hardware defined. What's the, what does that mean? >>Yeah, I mean I think we have been super successful in this hardware defined notion. We we're scaling by the hardware unit that we present as software defined data centers, right? And so that's been super successful. But we, you know, customers wanted more, especially customers in different parts of the world wanted to start even smaller and grow even more incrementally, right? Lower their costs even more. And so this is the part where resource defined starts to be very, very interesting as a way to think about, you know, here's my bag of resources exactly based on what the customers request for fiber machines, five containers, its size exactly for that. And then as utilization grows, we elastically behind the scenes, we're able to grow it through policies. So that's a whole different dimension. It's a whole different service offering that adds value and customers are comfortable. They can go from one to the other, they can go back to that post based model if they so choose to. And there's a jump off point across these two different economic models. >>It's kind of cloud of flexibility right there. I like the name Fred. Let's get into some of the examples of customers, if you don't mind. Let's get into some of the ex, we have some time. I wanna unpack a little bit of what's going on with the customer deployments. One of the things we've heard again on the cube is from customers is they like the clarity of the relationship, they love the cloud positioning of it. And then what happens is they lift and shift the workloads and it's like, feels great. It's just like we're running VMware on AWS and then they would start consuming higher level services, kind of that adoption next level happens and because it it's in the cloud, so, So can you guys take us through some recent examples of customer wins or deployments where they're using VMware cloud on AWS on getting started, and then how do they progress once they're there? How does it evolve? Can you just walk us through a couple of use cases? >>Sure. There's a, well there's a couple. One, it's pretty interesting that, you know, like you said, as there's more and more bits you need better and better hardware and networking. And we're super excited about the I four and the capabilities there in terms of doubling and or tripling what we're doing around a lower variability on latency and just improving all the speeds. But what customers are doing with it, like the college in New Jersey, they're accelerating their deployment on a, on onboarding over like 7,400 students over a six to eight month period. And they've really realized a ton of savings. But what's interesting is where and how they can actually grow onto additional native services too. So connectivity to any other services is available as they start to move and migrate into this. The, the options there obviously are tied to all the innovation that we have across any services, whether it's containerized and with what they're doing with Tanu or with any other container and or services within aws. >>So there's, there's some pretty interesting scenarios where that data and or the processing, which is moved quickly with full compliance, whether it's in like healthcare or regulatory business is, is allowed to then consume and use things, for example, with tech extract or any other really cool service that has, you know, monthly and quarterly innovations. So there's things that you just can't, could not do before that are coming out and saving customers money and building innovative applications on top of their, their current app base in, in a rapid fashion. So pretty excited about it. There's a lot of examples. I think I probably don't have time to go into too, too many here. Yeah. But that's actually the best part is listening to customers and seeing how many net new services and new applications are they actually building on top of this platform. >>Nora, what's your perspective from the VMware sy? So, you know, you guys have now a lot of headroom to offer customers with Amazon's, you know, higher level services and or whatever's homegrown where's being rolled out? Cuz you now have a lot of hybrid too, so, so what's your, what's your take on what, what's happening in with customers? >>I mean, it's been phenomenal, the, the customer adoption of this and you know, banks and many other highly sensitive verticals are running production grade applications, tier one applications on the service over the last five years. And so, you know, I have a couple of really good examples. S and p Global is one of my favorite examples. Large bank, they merge with IHS market, big sort of conglomeration. Now both customers were using VMware cloud and AWS in different ways. And with the, with the use case, one of their use cases was how do I just respond to these global opportunities without having to invest in physical data centers? And then how do I migrate and consolidate all my data centers across the global, which there were many. And so one specific example for this company was how they migrated thousand 1000 workloads to VMware cloud AWS in just six weeks. Pretty phenomenal. If you think about everything that goes into a cloud migration process, people process technology and the beauty of the technology going from VMware point A to VMware point B, the the lowest cost, lowest risk approach to adopting VMware, VMware cloud, and aws. So that's, you know, one of my favorite examples. There are many other examples across other verticals that we continue to see. The good thing is we are seeing rapid expansion across the globe that constantly entering new markets with the limited number of regions and progressing our roadmap there. >>Yeah, it's great to see, I mean the data center migrations go from months, many, many months to weeks. It's interesting to see some of those success stories. So congratulations. One >>Of other, one of the other interesting fascinating benefits is the sustainability improvement in terms of being green. So the efficiency gains that we have both in current generation and new generation processors and everything that we're doing to make sure that when a customer can be elastic, they're also saving power, which is really critical in a lot of regions worldwide at this point in time. They're, they're seeing those benefits. If you're running really inefficiently in your own data center, that is just a, not a great use of power. So the actual calculators and the benefits to these workloads is, are pretty phenomenal just in being more green, which I like. We just all need to do our part there. And, and this is a big part of it here. >>It's a huge, it's a huge point about the sustainability. Fred, I'm glad you called that out. The other one I would say is supply chain issues. Another one you see that constrains, I can't buy hardware. And the third one is really obvious, but no one really talks about it. It's security, right? I mean, I remember interviewing Stephen Schmidt with that AWS and many years ago, this is like 2013, and you know, at that time people were saying the cloud's not secure. And he's like, listen, it's more secure in the cloud on premise. And if you look at the security breaches, it's all about the on-premise data center vulnerabilities, not so much hardware. So there's a lot you gotta to stay current on, on the isolation there is is hard. So I think, I think the security and supply chain, Fred is, is another one. Do you agree? >>I I absolutely agree. It's, it's hard to manage supply chain nowadays. We put a lot of effort into that and I think we have a great ability to forecast and make sure that we can lean in and, and have the resources that are available and run them, run them more efficiently. Yeah, and then like you said on the security point, security is job one. It is, it is the only P one. And if you think of how we build our infrastructure from Nitro all the way up and how we respond and work with our partners and our customers, there's nothing more important. >>And naron your point earlier about the managed service patching and being on top of things, it's really gonna get better. All right, final question. I really wanna thank you for your time on this showcase. It's really been a great conversation. Fred, you had made a comment earlier. I wanna kind of end with kind of a curve ball and put you eyes on the spot. We're talking about a modern, a new modern shift. It's another, we're seeing another inflection point, we've been documenting it, it's almost like cloud hitting another inflection point with application and open source growth significantly at the app layer. Continue to put a lot of pressure and, and innovation in the infrastructure side. So the question is for you guys each to answer is what's the same and what's different in today's market? So it's kind of like we want more of the same here, but also things have changed radically and better here. What are the, what's, what's changed for the better and where, what's still the same kind of thing hanging around that people are focused on? Can you share your perspective? >>I'll, I'll, I'll, I'll tackle it. You know, businesses are complex and they're often unique that that's the same. What's changed is how fast you can innovate. The ability to combine manage services and new innovative services and build new applications is so much faster today. Leveraging world class hardware that you don't have to worry about that's elastic. You, you could not do that even five, 10 years ago to the degree you can today, especially with innovation. So innovation is accelerating at a, at a rate that most people can't even comprehend and understand the, the set of services that are available to them. It's really fascinating to see what a one pizza team of of engineers can go actually develop in a week. It is phenomenal. So super excited about this space and it's only gonna continue to accelerate that. That's my take. All right. >>You got a lot of platform to compete on with, got a lot to build on then you're Ryan, your side, What's your, what's your answer to that question? >>I think we are seeing a lot of innovation with new applications that customers are constant. I think what we see is this whole notion of how do you go from desktop to production to the secure supply chain and how can we truly, you know, build on the agility that developers desire and build all the security and the pipelines to energize that motor production quickly and efficiently. I think we, we are seeing, you know, we are at the very start of that sort of of journey. Of course we have invested in Kubernetes the means to an end, but there's so much more beyond that's happening in industry. And I think we're at the very, very beginning of this transformations, enterprise transformation that many of our customers are going through and we are inherently part of it. >>Yeah. Well gentlemen, I really appreciate that we're seeing the same thing. It's more the same here on, you know, solving these complexities with distractions. Whether it's, you know, higher level services with large scale infrastructure at, at your fingertips. Infrastructures, code, infrastructure to be provisioned, serverless, all the good stuff happen in Fred with AWS on your side. And we're seeing customers resonate with this idea of being an operator, again, being a cloud operator and developer. So the developer ops is kind of, DevOps is kind of changing too. So all for the better. Thank you for spending the time and we're seeing again, that traction with the VMware customer base and of us getting, getting along great together. So thanks for sharing your perspectives, >>I appreciate it. Thank you so >>Much. Okay, thank you John. Okay, this is the Cube and AWS VMware showcase, accelerating business transformation. VMware cloud on aws, jointly engineered solution, bringing innovation to the VMware customer base, going to the cloud and beyond. I'm John Fur, your host. Thanks for watching. Hello everyone. Welcome to the special cube presentation of accelerating business transformation on vmc on aws. I'm John Furrier, host of the Cube. We have dawan director of global sales and go to market for VMware cloud on adb. This is a great showcase and should be a lot of fun. Ashish, thanks for coming on. >>Hi John. Thank you so much. >>So VMware cloud on AWS has been well documented as this big success for VMware and aws. As customers move their workloads into the cloud, IT operations of VMware customers has signaling a lot of change. This is changing the landscape globally is on cloud migration and beyond. What's your take on this? Can you open this up with the most important story around VMC on aws? >>Yes, John. The most important thing for our customers today is the how they can safely and swiftly move their ID infrastructure and applications through cloud. Now, VMware cloud AWS is a service that allows all vSphere based workloads to move to cloud safely, swiftly and reliably. Banks can move their core, core banking platforms, insurance companies move their core insurance platforms, telcos move their goss, bss, PLA platforms, government organizations are moving their citizen engagement platforms using VMC on aws because this is one platform that allows you to move it, move their VMware based platforms very fast. Migrations can happen in a matter of days instead of months. Extremely securely. It's a VMware manage service. It's very secure and highly reliably. It gets the, the reliability of the underlyings infrastructure along with it. So win-win from our customers perspective. >>You know, we reported on this big news in 2016 with Andy Chas, the, and Pat Geling at the time, a lot of people said it was a bad deal. It turned out to be a great deal because not only could VMware customers actually have a cloud migrate to the cloud, do it safely, which was their number one concern. They didn't want to have disruption to their operations, but also position themselves for what's beyond just shifting to the cloud. So I have to ask you, since you got the finger on the pulse here, what are we seeing in the market when it comes to migrating and modern modernizing in the cloud? Because that's the next step. They go to the cloud, you guys have done that, doing it, then they go, I gotta modernize, which means kind of upgrading or refactoring. What's your take on that? >>Yeah, absolutely. Look, the first step is to help our customers assess their infrastructure and licensing and entire ID operations. Once we've done the assessment, we then create their migration plans. A lot of our customers are at that inflection point. They're, they're looking at their real estate, ex data center, real estate. They're looking at their contracts with colocation vendors. They really want to exit their data centers, right? And VMware cloud and AWS is a perfect solution for customers who wanna exit their data centers, migrate these applications onto the AWS platform using VMC on aws, get rid of additional real estate overheads, power overheads, be socially and environmentally conscious by doing that as well, right? So that's the migration story, but to your point, it doesn't end there, right? Modernization is a critical aspect of the entire customer journey as as well customers, once they've migrated their ID applications and infrastructure on cloud get access to all the modernization services that AWS has. They can correct easily to our data lake services, to our AIML services, to custom databases, right? They can decide which applications they want to keep and which applications they want to refactor. They want to take decisions on containerization, make decisions on service computing once they've come to the cloud. But the most important thing is to take that first step. You know, exit data centers, come to AWS using vmc or aws, and then a whole host of modernization options available to them. >>Yeah, I gotta say, we had this right on this, on this story, because you just pointed out a big thing, which was first order of business is to make sure to leverage the on-prem investments that those customers made and then migrate to the cloud where they can maintain their applications, their data, their infrastructure operations that they're used to, and then be in position to start getting modern. So I have to ask you, how are you guys specifically, or how is VMware cloud on s addressing these needs of the customers? Because what happens next is something that needs to happen faster. And sometimes the skills might not be there because if they're running old school, IT ops now they gotta come in and jump in. They're gonna use a data cloud, they're gonna want to use all kinds of machine learning, and there's a lot of great goodness going on above the stack there. So as you move with the higher level services, you know, it's a no brainer, obviously, but they're not, it's not yesterday's higher level services in the cloud. So how are, how is this being addressed? >>Absolutely. I think you hit up on a very important point, and that is skills, right? When our customers are operating, some of the most critical applications I just mentioned, core banking, core insurance, et cetera, they're most of the core applications that our customers have across industries, like even, even large scale ERP systems, they're actually sitting on VMware's vSphere platform right now. When the customer wants to migrate these to cloud, one of the key bottlenecks they face is skill sets. They have the trained manpower for these core applications, but for these high level services, they may not, right? So the first order of business is to help them ease this migration pain as much as possible by not wanting them to, to upscale immediately. And we VMware cloud and AWS exactly does that. I mean, you don't have to do anything. You don't have to create new skill set for doing this, right? Their existing skill sets suffice, but at the same time, it gives them that, that leeway to build that skills roadmap for their team. DNS is invested in that, right? Yes. We want to help them build those skills in the high level services, be it aml, be it, be it i t be it data lake and analytics. We want to invest in them, and we help our customers through that. So that ultimately the ultimate goal of making them drop data is, is, is a front and center. >>I wanna get into some of the use cases and success stories, but I want to just reiterate, hit back your point on the skill thing. Because if you look at what you guys have done at aws, you've essentially, and Andy Chassey used to talk about this all the time when I would interview him, and now last year Adam was saying the same thing. You guys do all the heavy lifting, but if you're a VMware customer user or operator, you are used to things. You don't have to be relearn to be a cloud architect. Now you're already in the game. So this is like almost like a instant path to cloud skills for the VMware. There's hundreds of thousands of, of VMware architects and operators that now instantly become cloud architects, literally overnight. Can you respond to that? Do you agree with that? And then give an example. >>Yes, absolutely. You know, if you have skills on the VMware platform, you know, know, migrating to AWS using via by cloud and AWS is absolutely possible. You don't have to really change the skills. The operations are exactly the same. The management systems are exactly the same. So you don't really have to change anything but the advantages that you get access to all the other AWS services. So you are instantly able to integrate with other AWS services and you become a cloud architect immediately, right? You are able to solve some of the critical problems that your underlying IT infrastructure has immediately using this. And I think that's a great value proposition for our customers to use this service. >>And just one more point, I want just get into something that's really kind of inside baseball or nuanced VMC or VMware cloud on AWS means something. Could you take a minute to explain what on AWS means? Just because you're like hosting and using Amazon as a, as a work workload? Being on AWS means something specific in your world, being VMC on AWS mean? >>Yes. This is a great question, by the way, You know, on AWS means that, you know, VMware's vse platform is, is a, is an iconic enterprise virtualization software, you know, a disproportionately high market share across industries. So when we wanted to create a cloud product along with them, obviously our aim was for them, for the, for this platform to have the goodness of the AWS underlying infrastructure, right? And, and therefore, when we created this VMware cloud solution, it it literally use the AWS platform under the eighth, right? And that's why it's called a VMs VMware cloud on AWS using, using the, the, the wide portfolio of our regions across the world and the strength of the underlying infrastructure, the reliability and, and, and sustainability that it offers. And therefore this product is called VMC on aws. >>It's a distinction I think is worth noting, and it does reflect engineering and some levels of integration that go well beyond just having a SaaS app and, and basically platform as a service or past services. So I just wanna make sure that now super cloud, we'll talk about that a little bit in another interview, but I gotta get one more question in before we get into the use cases and customer success stories is in, in most of the VM world, VMware world, in that IT world, it used to, when you heard migration, people would go, Oh my God, that's gonna take months. And when I hear about moving stuff around and doing cloud native, the first reaction people might have is complexity. So two questions for you before we move on to the next talk. Track complexity. How are you addressing the complexity issue and how long these migrations take? Is it easy? Is it it hard? I mean, you know, the knee jerk reaction is month, You're very used to that. If they're dealing with Oracle or other old school vendors, like, they're, like the old guard would be like, takes a year to move stuff around. So can you comment on complexity and speed? >>Yeah. So the first, first thing is complexity. And you know, what makes what makes anything complex is if you're, if you're required to acquire new skill sets or you've gotta, if you're required to manage something differently, and as far as VMware cloud and AWS on both these aspects, you don't have to do anything, right? You don't have to acquire new skill sets. Your existing idea operation skill sets on, on VMware's platforms are absolutely fine and you don't have to manage it any differently like, than what you're managing your, your ID infrastructure today. So in both these aspects, it's exactly the same and therefore it is absolutely not complex as far as, as far as, as far as we cloud and AWS is concerned. And the other thing is speed. This is where the huge differentiation is. You have seen that, you know, large banks and large telcos have now moved their workloads, you know, literally in days instead of months. >>Because because of VMware cloud and aws, a lot of time customers come to us with specific deadlines because they want to exit their data centers on a particular date. And what happens, VMware cloud and AWS is called upon to do that migration, right? So speed is absolutely critical. The reason is also exactly the same because you are using the exactly the same platform, the same management systems, people are available to you, you're able to migrate quickly, right? I would just reference recently we got an award from President Zelensky of Ukraine for, you know, migrating their entire ID digital infrastructure and, and that that happened because they were using VMware cloud database and happened very swiftly. >>That's been a great example. I mean, that's one political, but the economic advantage of getting outta the data center could be national security. You mentioned Ukraine, I mean Oscar see bombing and death over there. So clearly that's a critical crown jewel for their running their operations, which is, you know, you know, world mission critical. So great stuff. I love the speed thing. I think that's a huge one. Let's get into some of the use cases. One of them is, the first one I wanted to talk about was we just hit on data, data center migration. It could be financial reasons on a downturn or our, or market growth. People can make money by shifting to the cloud, either saving money or making money. You win on both sides. It's a, it's a, it's almost a recession proof, if you will. Cloud is so use case for number one data center migration. Take us through what that looks like. Give an example of a success. Take us through a day, day in the life of a data center migration in, in a couple minutes. >>Yeah. You know, I can give you an example of a, of a, of a large bank who decided to migrate, you know, their, all their data centers outside their existing infrastructure. And they had, they had a set timeline, right? They had a set timeline to migrate the, the, they were coming up on a renewal and they wanted to make sure that this set timeline is met. We did a, a complete assessment of their infrastructure. We did a complete assessment of their IT applications, more than 80% of their IT applications, underlying v vSphere platform. And we, we thought that the right solution for them in the timeline that they wanted, right, is VMware cloud ands. And obviously it was a large bank, it wanted to do it safely and securely. It wanted to have it completely managed, and therefore VMware cloud and aws, you know, ticked all the boxes as far as that is concerned. >>I'll be happy to report that the large bank has moved to most of their applications on AWS exiting three of their data centers, and they'll be exiting 12 more very soon. So that's a great example of, of, of the large bank exiting data centers. There's another Corolla to that. Not only did they manage to manage to exit their data centers and of course use and be more agile, but they also met their sustainability goals. Their board of directors had given them goals to be carbon neutral by 2025. They found out that 35% of all their carbon foot footprint was in their data centers. And if they moved their, their ID infrastructure to cloud, they would severely reduce the, the carbon footprint, which is 35% down to 17 to 18%. Right? And that meant their, their, their, their sustainability targets and their commitment to the go to being carbon neutral as well. >>And that they, and they shift that to you guys. Would you guys take that burden? A heavy lifting there and you guys have a sustainability story, which is a whole nother showcase in and of itself. We >>Can Exactly. And, and cause of the scale of our, of our operations, we are able to, we are able to work on that really well as >>Well. All right. So love the data migration. I think that's got real proof points. You got, I can save money, I can, I can then move and position my applications into the cloud for that reason and other reasons as a lot of other reasons to do that. But now it gets into what you mentioned earlier was, okay, data migration, clearly a use case and you laid out some successes. I'm sure there's a zillion others. But then the next step comes, now you got cloud architects becoming minted every, and you got managed services and higher level services. What happens next? Can you give us an example of the use case of the modernization around the NextGen workloads, NextGen applications? We're starting to see, you know, things like data clouds, not data warehouses. We're not gonna data clouds, it's gonna be all kinds of clouds. These NextGen apps are pure digital transformation in action. Take us through a use case of how you guys make that happen with a success story. >>Yes, absolutely. And this is, this is an amazing success story and the customer here is s and p global ratings. As you know, s and p global ratings is, is the world leader as far as global ratings, global credit ratings is concerned. And for them, you know, the last couple of years have been tough as far as hardware procurement is concerned, right? The pandemic has really upended the, the supply chain. And it was taking a lot of time to procure hardware, you know, configure it in time, make sure that that's reliable and then, you know, distribute it in the wide variety of, of, of offices and locations that they have. And they came to us. We, we did, again, a, a, a alar, a fairly large comprehensive assessment of their ID infrastructure and their licensing contracts. And we also found out that VMware cloud and AWS is the right solution for them. >>So we worked there, migrated all their applications, and as soon as we migrated all their applications, they got, they got access to, you know, our high level services be our analytics services, our machine learning services, our, our, our, our artificial intelligence services that have been critical for them, for their growth. And, and that really is helping them, you know, get towards their next level of modern applications. Right Now, obviously going forward, they will have, they will have the choice to, you know, really think about which applications they want to, you know, refactor or which applications they want to go ahead with. That is really a choice in front of them. And, but you know, the, we VMware cloud and AWS really gave them the opportunity to first migrate and then, you know, move towards modernization with speed. >>You know, the speed of a startup is always the kind of the Silicon Valley story where you're, you know, people can make massive changes in 18 months, whether that's a pivot or a new product. You see that in startup world. Now, in the enterprise, you can see the same thing. I noticed behind you on your whiteboard, you got a slogan that says, are you thinking big? I know Amazon likes to think big, but also you work back from the customers and, and I think this modern application thing's a big deal because I think the mindset has always been constrained because back before they moved to the cloud, most IT, and, and, and on-premise data center shops, it's slow. You gotta get the hardware, you gotta configure it, you gotta, you gotta stand it up, make sure all the software is validated on it, and loading a database and loading oss, I mean, mean, yeah, it got easier and with scripting and whatnot, but when you move to the cloud, you have more scale, which means more speed, which means it opens up their capability to think differently and build product. What are you seeing there? Can you share your opinion on that epiphany of, wow, things are going fast, I got more time to actually think about maybe doing a cloud native app or transforming this or that. What's your, what's your reaction to that? Can you share your opinion? >>Well, ultimately we, we want our customers to utilize, you know, most of our modern services, you know, applications should be microservices based. When desired, they should use serverless applic. So list technology, they should not have monolithic, you know, relational database contracts. They should use custom databases, they should use containers when needed, right? So ultimately, we want our customers to use these modern technologies to make sure that their IT infrastructure, their licensing, their, their entire IT spend is completely native to cloud technologies. They work with the speed of a startup, but it's important for them to, to, to get to the first step, right? So that's why we create this journey for our customers, where you help them migrate, give them time to build the skills, they'll help them mo modernize, take our partners along with their, along with us to, to make sure that they can address the need for our customers. That's, that's what our customers need today, and that's what we are working backwards from. >>Yeah, and I think that opens up some big ideas. I'll just say that the, you know, we're joking, I was joking the other night with someone here in, in Palo Alto around serverless, and I said, you know, soon you're gonna hear words like architectural list. And that's a criticism on one hand, but you might say, Hey, you know, if you don't really need an architecture, you know, storage lists, I mean, at the end of the day, infrastructure is code means developers can do all the it in the coding cycles and then make the operations cloud based. And I think this is kind of where I see the dots connecting. Final thought here, take us through what you're thinking around how this new world is evolving. I mean, architecturals kind of a joke, but the point is, you know, you have to some sort of architecture, but you don't have to overthink it. >>Totally. No, that's a great thought, by the way. I know it's a joke, but it's a great thought because at the end of the day, you know, what do the customers really want? They want outcomes, right? Why did service technology come? It was because there was an outcome that they needed. They didn't want to get stuck with, you know, the, the, the real estate of, of a, of a server. They wanted to use compute when they needed to, right? Similarly, what you're talking about is, you know, outcome based, you know, desire of our customers and, and, and that's exactly where the word is going to, Right? Cloud really enforces that, right? We are actually, you know, working backwards from a customer's outcome and using, using our area the breadth and depth of our services to, to deliver those outcomes, right? And, and most of our services are in that path, right? When we use VMware cloud and aws, the outcome is a, to migrate then to modernize, but doesn't stop there, use our native services, you know, get the business outcomes using this. So I think that's, that's exactly what we are going through >>Actually, should actually, you're the director of global sales and go to market for VMware cloud on Aus. I wanna thank you for coming on, but I'll give you the final minute. Give a plug, explain what is the VMware cloud on Aus, Why is it great? Why should people engage with you and, and the team, and what ultimately is this path look like for them going forward? >>Yeah. At the end of the day, we want our customers to have the best paths to the cloud, right? The, the best path to the cloud is making sure that they migrate safely, reliably, and securely as well as with speed, right? And then, you know, use that cloud platform to, to utilize AWS's native services to make sure that they modernize their IT infrastructure and applications, right? We want, ultimately that our customers, customers, customer get the best out of, you know, utilizing the, that whole application experience is enhanced tremendously by using our services. And I think that's, that's exactly what we are working towards VMware cloud AWS is, is helping our customers in that journey towards migrating, modernizing, whether they wanna exit a data center or whether they wanna modernize their applications. It's a essential first step that we wanna help our customers with >>One director of global sales and go to market with VMware cloud on neighbors. He's with aws sharing his thoughts on accelerating business transformation on aws. This is a showcase. We're talking about the future path. We're talking about use cases with success stories from customers as she's thank you for spending time today on this showcase. >>Thank you, John. I appreciate it. >>Okay. This is the cube, special coverage, special presentation of the AWS Showcase. I'm John Furrier, thanks for watching.

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

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

(upbeat music) >> Live from Orlando Florida. It's the Cube. Covering Cisco Live 2018. Brought to Cisco NetApp and the Cube's ecosystem partners. >> Welcome back to the Cube's Live coverage here in Orlando Florida for Cisco Live 2018. It's the Cube's coverage. >> I'm John Furrier. The host. Here for three days of wall-to wall-coverage. Our next guest is Shubha Govil. Whose the director of product management for Cisco DevNet. Welcome to the Cube. Thanks for coming on. >> Thanks John. Thanks for having me on Cube. >> Great conversation before the cameras came out. We're talking about development and Cloud Native. But we're super impressed with the work you guys have done at DevNet. Certainly it's the top story of the show here is that Cisco has now crossed over the flywheel of innovation where 500,000 registered developers. >> Developers. Not visitors to a website. >> Yes. Or some marketing program. >> Correct. >> Real engaging developers. >> Absolutely. >> Congratulations. >> Thank you John. Thank you. >> A couple of years. Four years and you're here. You've got DevNet. And DevNet Create. Which we've been covering extensively as well. >> Yes. >> Which is the Cloud Native world coming together. >> Yes. >> This is for the first time in Cisco's history where you have now a clear line of sight for network engineers network developers network experts who have been certified in the CCIE and other certifications. CCNA, CCNP. All the stuff you guys do. You can now see a clear line where you can extend the capabilities and knowledge and expertise in power of networking. >> Absolutely. >> Up the stack. >> Absolutely. >> Finally Cisco's moving up the stack. >> Yes. >> Tell us what's going on in the product side? >> Yeah Absolutely. And I'm gonna talk about very specific example today. And today if you heard the keynote speak. And Susie opened up a few things and announcement. One of them was DNA developer center. And I'm gonna talk about that. Because part of it is how network is an open platform now. And that was part of the announcement. You will hear a lot about that. And linking it back to Dev reports. Quite right. They should care about why they should look into it. So three things I'm gonna talk about. DNA, developer center and what they can find there. And once they go there and they really start learning about our platform on API's on DevNet. What cord exchange does for them. And how they can start not only programming the Intent based on our Intent API's and what they want network to do for them but also sharing some community cord. Are using that community cord. Community Cord if they are just getting started. Right? So on DNA Developers Center we have four capabilities highlighted. These are the API's. Whether they are Intent API's Integration API's to connect with other third parties. Or SDK's to manage multi-party devices. Or there for ITSM or a specific use case integrations. >> So hold up. Go slow. >> I'm kind of not on the uptake as you are on this. Because you're in it. IF DNA is a set of abstractions API's on top of the equipment. >> Correct. >> So it's not natively. It's a set of API. >> Set of API's. >> So that people could use those API's to create services. >> To manage their network wealth. To automate and drive these right use cases. So I might. >> Give me an example. >> Yeah let's talk about an example. Intent. My intent might be to. We were talking about radio conferences awhile back. And I come from that environment. I want to drive a Butler QS for certain level of execs. Right? If they are on the call this was the thing of like eight ten years back. If my execs are on a call make sure they have the best experience. So the QS quality of your network should be set up to a level that there's no disruption. There's no latency in the call. Right? So that's an intent. That's a business intent. Give best experience to my execs. >> So really that's combining policy and QOS together to make it meet the outcome. Which is no latency. >> To meet the outcome. But for the network engineer now let's connect back to the developer. The network engineer whose trying to make this intent possible for the execs. There's a places they need to set up the SQSS. And won't it be easy of them if there was a simple API that they can use to create that solution to drive that policy across the devices. Whether Cisco devices or non Cisco devices. >> This has been the challenge for network engineers in general. Because you want to have things in control and locked down but as you want to do more things that are programmable. >> Correct. >> There's been some provisioning and some configuration management things. >> Correct. >> You're saying, hey you're gonna lock down all the architecture and then move up. Use the API's to do better integration. Make things run smoothly without disrupting the network. Is that right? >> That's part of it. But also it's about making it easy for them. Correct? Simplify the process of doing it. The process of making it happen was long steps of CLI command. That now that network engineer was going continuously. A lot of the time people actually tells us that they would have this cut and paste copy of the command. That they will take from one place go to the next place next device and next device. And continue to do that step. And that's the productivity game we are driving by simplifying where one API call can go across all the devices and make that change happen. >> We've heard that a lot from on DevNet and the hallway conversations that said DevNet's made my life easier. >> Yes. >> I don't have to do those mundane tasks. >> Exactly. >> That were part of getting things done. Okay. Let me ask you personal question. As director of product management for DevNet. What is your product scope? What are you working on? Can you take a minute? >> That's a very good question. And that's where some of these offers we were talking about earlier come in to play. So for example, within Devnet we create a lot of offers to make developers lives simple. Whether we are talking about giving them the best quality of learning content. Or giving them hosted Sandbox environment to try and test. All of that requires a lot of product management knowledge and the need. But really what the 2ADS we have work more closely to get them out to market. One is the thing called Code Exchange. It's a tool for our developer committee. Where we have aggregated the public git code across the Cisco technologies. >> That's on GitHub I think. >> GitHub code right. Absolutely. But the second powerful thing on top of that is our Ecosystem Exchange. This is where we are bringing an aggregated view of every partner out there. Every Cisco partner whose creating great solutions on our API's in a single place our developers can go and find that solution. To really address the business outcome they are looking to address. >> Shubha, I want you to put some color commentary around of some of the feedback you've heard. We hear people of the DevNet community saying I've come to Cisco Live and I spend all my week here in DevNet. Because it really is kind of like a kid in the candy store. (Shubha laughs) >> From a computer science or developer prospective. >> Yeah. >> What are some of the cool examples and demos that you guys have here? What's your favorite? What are some of the things that are jumping out that people are gravitating towards? >> I will tell you one of the most popular sessions that I have seen in the last few days here is Network Programmability for Networking Juniors. That's one. There's also a very Network Programmability one-on-one. Coding one-on-one class. It's basic Python. But applying it in network context. Those are some of the most popular sessions that I have seen. But when it comes to cool demos there's a cool demo around Flex IQ. I think you might be talking to Ashish later about that. >> Yes. >> And really it's a retail scenario how you are tracking. Using the location based service example. But in this case camera feed. Really analyzing where people are. And you'll get to hear more about this. >> We took a ad. I saw the demo. >> Yeah. >> The Flex IQ. First of all I love the name. I said trademark it immediately. (Shubha laughs) Get it out there. First use wins. And it's already out there. But it's really taking a A access point. >> This is an access point. >> And it plugs into a camera. And a great example of some of the coolness you can do with a preexisting condition. In this case an access point. >> So each of these information points that data one that they are collecting. Whether it's a camera feed. It's a location service. Like information about the devices and the environment. Each set of data is the relevance in this. Which is driving the newest use cases. And this data is coming through API's that have labeled but I'd say morockie access point API. All the camera API that are labeled that have enabled C Space. >> This is really the aha moment for me. I've been following Cisco really since the 90's. >> Yeah. >> Or at least when they formed. Being the young gun at the time. Younger than I am now. 30 years ago. But it was really networking. Connecting companies together. It was the plumbing. It was the core. >> Yes. Unstoppable since then. Now the success is still there. But it's really the problem solving is never going away. I saw this security challenges that were outlined in the keynote. We all know Cybe Ops is a huge issue. Cloud is here. You've got industrial IOT going on. And IOT. But these examples that DevNet is showing is that these new capabilities with I won't say a hack but a maker faire culture. >> It is a maker culture right. Which is lot of DIY stuff. So this lot of learning by playing with the API's and multiple one of them. And you'd really find use cases you have never addressed before. We also have a design thinking workshop here going on. And part of it is really thinking about the use cases from the user prospective. What you are trying to address. Before finding the cool technologies. Really understand what your users' needs are. >> Yeah. >> And we are doing a lot of things around that. And bringing it connecting it back to the APIs. Once we learn the right needs. And finding these use cases that were never possible before. >> Well I talked to Susie all the time about this. >> Yeah. >> And I know she's really hardcore on this. But you guys have nailed the community aspect as well. You've brought that open source ethos into the formula. Which makes it more collaborative. No one wants to be alone. I mean the last thing a network engineer wants to do is be the old way of being tied to the chair on the network. Troubleshooting problems. They want to have more collaboration As some of this creativity kicks in. So it's really a new time. How are you guys handling this? Is it like people are having an awakening moment? Or what are you guys doing to nature this? What are some of the exciting things? >> And the best part about the community is that communities learning with each other. Right? It's this feeling of we are enabling our community both traditionally and through even like Cisco Live and DevNet Create. We bring them together to be able to learn from each other much as we learn with them. And trying to define the right use cases and solutions. And that's what the company's behind. The 500,000 developers who are coming and learning with us. They have found the use cases they were addressing for their business. They also found a new skill set that they were looking to learn before. >> Yeah. >> And a lot of them have come along where they are showing their tech cred in the community. Really being the community leaders. >> You know it's been kind of a downer some of the narrative I've seen from press outlets other press outlets and other kind of naysayers has been Hey network guys. You're gonna be automated away. Go learn how to code to save your career. Actually that's not happening. >> That is not happening at all. >> The power of networking certainly as security moves down lower on the stack. And policy and these cool service oriented service meshes. Kubernetes. Really points to the relevance of the network engineer more than ever. You've got SDN. Software Defined Data Center. That's not going away. Automation is going to take mundane tasks away. >> Yes. >> But actions happening at the app layer. >> They have that expertise and 20 years plus experience knowing how networks should be running to make these things possible. The use cases around the applications possible. >> They're more relevant than ever. >> They are more relevant than ever. I would say. Exactly. That's the key. >> Well you guys are at the beginning I think of another set of inflection point. Certainly DevNet's gone in a quick four years. You're connecting to the Cloud Native World with DevNet Create. Which is phenomenal. Those are two worlds that are coming together. I just see another inflection point coming. Maybe it's a million developers. But you've been success in the enterprise where it's been really difficult. Even Microsoft with their legacy developer program .net. The Visual Basic and all the MSDM stuff. >> At the by GitHub >> Yup. >> To kind of maintain relevance. Other companies like Oracle VM wear and other ones they're having a hard time. You guys are just kicking butt. >> So part of it for us is not only focusing on traditional infrastructure. But also talking about the app developer. So these application developers who did not know about network at all. A lot of times they had to fight with their networking juniors to get their application the particular function they wanted to have. Right? So that what we are enabling by bringing them together. Also we have been running small programs like we are trying new markets. Global markets. China, India and some of the things like really reaching out to the big large hackathons. Which are traditionally. For example in India we were recently doing a smart India hackathon. >> Nice. >> There are 500,00 students participated in solving real problems for the country. And DevNet was the provider of applications and API's. Bringing them into the application world with the understanding of network. >> A lot of growth in India and China. Certainly massive new developers coming on board. Okay final question to wrap up the segment. I gotta get your prospective. Take your DevNet hat off for a second. >> Okay. Put your Cisco hat on. >> Sure. For the folks who couldn't make Cisco Live this year what's the big story coming out of the event this year? You guys have been successful with the 500,000 developers. What's the big story developing here? What should people know is the most important story for Cisco Live 2018? >> I think the biggest story I would like to call out is that network is open for business. Network is really open for you to really come and make your intent. Your use cases. Your business outcomes possible. And that's the biggest story I will call out. >> Shubha Govil here product management for DevNet. Here on the Cube. Live coverage. Day two of three days. I'm John Furrier. Stay with us for more live coverage. As we start winding down day two. A lot of great action. The network is programmable. It's creating value and new use cases. And the developers are in the center of the action. The network engineers seeing a clear path of the Cloud and more. We'll be back with more after this short break. (upbeat music)