>>Welcome back to the cubes coverage of dr khan 2021. I'm john for your host of the cube. We're here with Amanda Silver, corporate vice president, product developer division at Microsoft. Amanda, Great to see you you were on last year, Dr khan. Great to see you again a full year later were remote. Thanks for coming on. I know you're super busy with build happening this week as well. Thanks for making the time to come on the cube for Dr khan. >>Thank you so much for having me. Yeah, I'm joining you like many developers around the globe from my personal home office, >>developers really didn't skip a beat during the pandemic and again, it was not a good situation but developers, as you talked about last year on the front lines, first responders to creating value quite frankly, looking back you were pretty accurate in your prediction, developers did have an impact this year. They did create the kind of change that really changed the game for people's lives, whether it was developing solutions from a medical standpoint or even keeping systems running from call centres to making sure people got their their their goods or services and checks and and and kept sanity together. So. >>Yeah absolutely. I mean I think I think developers you know get the M. V. P. Award for this year because you know at the end of the day they are the digital first responders to the first responders and the pivot that we've had to make over the past year in terms of supporting remote telehealth, supporting you know online retail, curbside pickup. All of these things were done through developers being the ones pushing the way forward remote learning. You know my kids are learning at home right behind me right now so you might hear them during the interview that's happening because developers made that happen. >>I don't think mom please stop hogging the band with, they've got a gigabit. Stop it. Don't be streaming. My kids are all game anyway, Hey, great to have you on and you have to get the great keynote, exciting to see you guys continue the collaboration with Docker uh with GIT hub and Microsoft, A great combination, it's a 123 power punch of value. You guys are really kind of killing it. We heard from scott and dan has been on the cube. What's your thoughts on the partnership with the developer division team at Microsoft with Doctor, What's it all about this year? What's the next level? >>Well, I mean, I think, I think what's really awesome about this partnership is that we all have, we all are basically sharing a common mission. What we want to do is make sure that we're empowering developers, that we're focused on their productivity and that we're delivering value to them so they can do their job better so that they can help others. So that's really kind of what drives us day in and day out. So what we focus on is developer productivity. And I think that's a lot of what dana was talking about in her session, the developer division. Specifically, we really try to make sure that we're improving the state of the art from modern developers. So we want to make sure that every keystroke that they take, every mouse move that they make, it sounds like a song but every every one of those matter because we want to make sure that every developers writing the code that only they can write and in terms of the partnership and how that's going. You know my team and the darker team have been collaborating a ton on things like dr desktop and the Doctor Cli tool integrations. And one of the things that we do is we think about pain points and various workflows. We want to make sure that we're shaving off the edges of all of the user experience is the developers have to go through to piece all of these applications together. So one of the big pain points that we have heard from developers is that signing into the Azure cloud and especially our sovereign clouds was challenging. So we contributed back to uh back to doctor to actually make it easier to sign into these clouds. And so dr developers can now use dr desktop and the Doctor Cli to actually change the doctor context so that its Azure. So that makes it a lot easier to connect the other. Oh, sorry, go ahead. No, I was just >>going to say, I love the reference of the police song. Every breath you take, every >>mouth moving. Great, >>great line there. Uh, but I want to ask you while you're on this modern cloud um, discussion, what is I mean we have a lot of developers here at dr khan. As you know, you guys know developers in your ecosystem in core competency. From Microsoft, Kublai khan is a very operator like focus developed. This is a developer conference. You guys have build, what is the state of the art for a modern cloud developer? Could you just share your thoughts because this comes up a lot. You know, what's through the art? What's next jan new guard guard? It's his legacy. What is the state of the art for a modern cloud developer? >>Fantastic question. And extraordinarily relevant to this particular conference. You know what I think about often times it's really what is the inner loop and the outer loop look like in terms of cycle times? Because at the end of the day, what matters is the time that it takes for you to make that code change, to be able to see it in your test environment and to be able to deploy it to production and have the confidence that it's delivering the feature set that you need it to. And it's, you know, it's secure, it's reliable, it's performance, that's what a developer cares about at the end of the day. Um, at the same time, we also need to make sure that we're growing our team to meet our demand, which means we're constantly on boarding new developers. And so what I take inspiration from our, some of the tech elite who have been able to invest significant amounts in, in tuning their engineering systems, they've been able to make it so that a new developer can join a team in just a couple of minutes or less that they can actually make a code change, see that be reflected in their application in just a few seconds and deploy with confidence within hours. And so our goal is to actually be able to take that state of the art metric and democratize that actually bring it to as many of our customers as we possibly can. >>You mentioned supply chain earlier in securing that. What are you guys doing with Docker and how to make that partnership better with registries? Is there any update there in terms of the container registry on Azure? >>Yeah, I mean, you know, we, we we have definitely seen recent events and and it almost seems like a never ending attacks that that you know, increasingly are getting more and more focused on developer watering holes is how we think about it. Kind of developers being a primary target um for these malicious hackers. And so what it's more important than ever that every developer um and Microsoft especially uh really take security extraordinarily seriously. Our engineers are working around the clock to make sure that we are responding to every security incident that we hear about and partnering with our customers to make sure that we're supporting them as well. One of the things that we announced earlier this week at Microsoft build is that we've actually taken, get have actions and we've now integrated that into the Azure Security Center. And so what this means is that, you know, we can now do things like scan for vulnerabilities. Um look at things like who is logging in, where things like that and actually have that be tracked in the Azure security center so that not just your developers get that notification but also your I. T. Operations. Um In terms of the partnership with dR you know, this is actually an ongoing partnership to make sure that we can provide more guidance to developers to make sure that they are following best practices like pulling from a private registry like Docker hub or at your container registry. So I expect that as time goes on will continue to more in partnership in this space >>and that's going to give a lot of confidence. Actually, productivity wise is going to be a big help for developers. Great stuff is always good, good progress. They're moving the needle. >>Last time we >>spoke we talked about tools and setting Azure as the doctor context duty tooling updates here at dot com this year. That's notable. >>Yeah, I mean, I think, you know, there's one major thing that we've been working on which has a big dependency on docker is get help. Code space is now one of the biggest pain points that developers have is setting up a new DEV box, which they often have to do when they are on boarding a new employee or when they're starting a new project or even if they're just kicking the tires on a new technology that they want to be able to evaluate and sometimes creating a developer environment can actually take hours um and especially when you're trying to create a developer environment that matches somebody else's developer environment that can take like a half a day and you can spend all of your time just debugging the differences in environment variables, for example, um, containers actually makes that much easier. So what you can do with this, this services, you can actually create death environment spun up in the cloud and you can access it in seconds and you get from there are working coding environment and a runtime environment and this is repeatable via containers. So it means that there's no inadvertent differences introduced by each DEV. And you might be interested to know that underneath this is actually using Docker files and dr composed to orchestrate the debits and the runtime bits for a whole bunch of different stacks. And so this is something that we're actually working on in collaboration with the with the doctor team to have a common the animal format. And in fact this week we actually introduced a couple of app templates so that everybody can see this all in action. So if you check out a ca dot m s forward slash app template, you can see this in action yourself. >>You guys have always had such a strong developer community and one thing I love about cloud as it brings more agility, as we always talk about. But when you start to see the enterprise grow into, the direction is going now, it's almost like the developer communities are emerging, it's no longer about all the Lennox folks here and the dot net folks there, you've got windows, you've got cloud, >>it's almost >>the the the solidification of everyone kind of coming together. Um and visual studio, for instance, last year, I think you were talking about that to having to be interrogated dr composed, et cetera. >>How do you see >>this melting pot emerging? Because at the end of the day, you pick the language you love and you got devops, which is infrastructure as code doesn't matter. So give us your take on where we are with that whole progress of of making that happen. >>Well, I mean I definitely think that, you know, developer environments and and kind of, you know, our approach to them don't need to be as dogmatic as they've been in the past. I really think that, you know, you can pick the right tool and language and stand developer stack for your team, for your experience and you can be productive and that's really our goal. And Microsoft is to make sure that we have tools for every developer and every team so that they can build any app that they want to want to create. Even if that means that they're actually going to end up ultimately deploying that not to our cloud, they're going to end up deploying it to AWS or another another competitive cloud. And so, you know, there's a lot of things that we've been doing to make that really much easier. We have integrated container tools in visual studio and visual studio code and better cli integrations like with the doctor context that we had talked about a little bit earlier. We continue to try to make it easier to build applications that are targeting containers and then once you create those containers it's much easier to take it to another environment. One of the examples of this kind of work is now that we have WsL and the Windows subsystem for Lennox. This makes it a lot easier for developers who prefer a Windows operating system as their environment and maybe some tools like Visual Studio that run on Windows, but they can still target Lennox with as their production environment without any impedance mismatch. They can actually be as productive as they would be if they had a Linux box as their Os >>I noticed on this session, I got to call this out. I want to get your reaction to it interesting. Selection of Microsoft talks, the container based development. Visual studio code is one that's where you're going to show some some some container action going on with note and Visual Studio code. And then you get the machine learning with Azure uh containers in the V. S. Code. Interesting how you got, you know, containers with V. S. And now you've got machine learning. What does that tell the world about where Microsoft's at? Because in a way you got the cutting edge container management on one side with the doctor integration. Now you get the machine learning which everyone's talking about shifting, left more automation. Why are these sessions so important? Why should people attend? And what's the what's the bottom line? >>Well, like I said, like containers basically empower developer productivity. Um that's what creates the reputable environments, that's what allows us to make sure that, you know, we're productive as soon as we possibly can be with any text act that we want to be able to target. Um and so that's kind of almost the ecosystem play. Um it's how every developer can contribute to the success of others and we can amor ties the kinds of work that we do to set up an environment. So that's what I would say about the container based development that we're doing with both visual studio and visual studio code. Um in terms of the machine learning development, uh you know, the number of machine learning developers in the world is relatively small, but it's growing and it's obviously a very important set of developers because to train a machine learning uh to train an ml model, it actually requires a significant amount of compute resources, and so that's a perfect opportunity to bring in the research that are in a public cloud. Um What's actually really interesting about that particular develop developer stack is that it commonly runs on things like python. And for those of you who have developed in python, you know, just how difficult it is to actually set up a python environment with the right interpreter, with the right run time, with the right libraries that can actually get going super quickly, um and you can be productive as a developer. And so it's actually one of the hardest, most challenging developer stacks to actually set up. And so this allows you to become a machine learning developer without having to spend all of your time just setting up the python runtime environment. >>Yeah, it's a nice, nice little call out on python, it's a double edged sword. It's easier to sling code around on one hand, when you start getting working then you gotta it gets complicated can get well. Um Well the great, great call out there on the island, but good, good, good project. Let me get your thoughts on this other tool that you guys are talking about project tie. Uh This is interesting because this is a trend that we're seeing a lot of conversations here on the cube about around more too many control planes. Too many services. You know, I no longer have that monolithic application. I got micro micro applications with microservices. What the hell is going on with my services? >>Yeah, I mean, I think, you know, containers brought an incredible amount of productivity in terms of having repeatable environments, both for dev environments, which we talked about a lot on this interview already, but also obviously in production and test environments. Super important. Um and with that a lot of times comes the microservices architecture that we're also moving to and the way that I view it is the microservices architecture is actually accompanied by businesses being more focused on the value that they can actually deliver to customers. And so they're trying to kind of create separations of concerns in terms of the different services that they're offering, so they can actually version and and kind of, you know, actually improve each of these services independently. But what happens when you start to have many microservices working together in a SAS or in some kind of aggregate um service environment or kind of application environment is it starts to get unwieldy, it's really hard to make it so that one micro service can actually address another micro service. They can pass information back and forth. And you know what used to be maybe easy if you were just building a client server application because, you know, within the server tear all of your code was basically contained in the same runtime environment. That's no longer the case when every microservices actually running inside of its own container. So the question is, how can we improve program ability by making it easier for one micro service that's being used in an application environment, be to be able to access another another service and kind of all of that context. Um and so, you know, you want to be able to access the service is the the api endpoint, the containers, the ingress is everything, make everything work together as though it felt just as easy as as um you know, server application development. Um And so what this means as well is that you also oftentimes need to get all of these different containers running at the same time and that can actually be a challenge in the developer and test loop as well. So what project tie does is it improves the program ability and it actually allows you to just write a command like thai run so that you can actually in stan she ate all of these containers and get them up and running and basically deploy and run your application in that environment and ultimately make the dev testing or loop much faster >>than productivity gain. Right. They're making it simple to stand up. Great, great stuff. Let me ask you a question as we kind of wrap down here for the folks here at Dakar Con, are >>there any >>special things you'd like to talk about the development you think are important for the developers here within this space? It's very dynamic. A lot of change happening in a good way. Um, but >>sometimes it's hard to keep >>track of all the cool stuff happening. Could you take a minute to, to share your thoughts on what you think are the most important develops developments in this space? That that might be interesting to ducker con attendees. >>I think the most important things are to recognize that developer environments are moving to containerized uh, environments themselves so that they can be repeated, they can be shared, the work, configuring them can be amortized across many developers. That's important thing. Number one important thing. Number two is it doesn't matter as much what operating system you're running as your chrome, you know, desktop. What matters is ultimately the production environment that you're targeting. And so I think now we're in a world where all of those things can be mixed and matched together. Um and then I think the next thing is how can we actually improve microservices, uh programming development together um so that it's easier to be able to target multiple micro services that are working in aggregate uh to create a single service experience or a single application. And how do we improve the program ability for that? >>You know, you guys have been great supporters of DACA and the community and open source and software developers as they transform and become quite frankly the superheroes for the transformation, which is re factoring businesses. So this has been a big thing. I'd love to get your thoughts on how this is all coming together inside Microsoft, you've got your division, you get the developer division, you got GIT hub, got Azure. Um, and then just historically, and he put this up last year army of an ecosystem. People who have been contributing encoding with Microsoft and the partners for many, many decades. >>Yes. The >>heart Microsoft now, how's it all working? What's the news? I get Lincoln, Lincoln, but there's no yet developer model there yet, but probably is soon. >>Um Yeah, I mean, I think that's a pretty broad question, but in some ways I think it's interesting to put it in the context of Microsoft's history. You know, I think when I think back to the beginning of my career, it was kind of a one stack shop, you know, we was all about dot net and you know, of course we want to dot net to be the best developer environment that it can possibly be. We still actually want that. We still want that need to be the most productive developer environment. It could we could possibly build. Um but at the same time, I think we have to recognize that not all developers or dot net developers and we want to make sure that Azure is the most productive cloud for developers and so to do that, we have to make sure that we're building fantastic tools and platforms to host java applications, javascript applications, no Js applications, python applications, all of those things, you know, all of these developers in the world, we want to make sure it can be productive on our tools and our platforms and so, you know, I think that's really kind of the key of you know what you're speaking of because you know, when I think about the partnership that I have with the GIT hub team or with the Azure team or with the Azure Machine learning team or the Lincoln team, um A lot of it actually comes down to helping empower developers, improving their productivity, helping them find new developers to collaborate with, um making sure that they can do that securely and confidently and they can basically respond to their customers as quickly as they possibly can. Um and when, when we think about partnering inside of Microsoft with folks like linkedin or office as an example, a lot of our partnership with them actually comes down to improving their colleagues efficiency. We build the developer tools that office and lengthen are built on top of and so every once in a while we will make an improvement that has, you know, 5% here, 3% there and it turns into an incredible amount of impact in terms of operations, costs for running these services. >>It's interesting. You mentioned earlier, I think there's a time now we're living in a time where you don't have to be dogmatic anymore, you can pick what you like and go with it. Also that you also mentioned just now this idea of distributed applications, distributed computing. You know, distributed applications and microservices go really well together. Especially with doctor. >>Can you share >>your thoughts on the framework that you guys released called Dapper? >>Yeah, yeah. We recently released Dapper. It's called D A P R. You can look it up on GIT hub and it's a programming model for common microservices pattern, two common microservices patterns that make it really easy and automatic to create those kinds of microservices. So you can choose to work with your favorite state stores or databases or pub sub components and get things like cloud events for free. You can choose either http or g R B C so that you can get mesh capabilities like service discovery and re tries and you can bring your own secret store and easily be able to call it from any environment variable. It's also like I was talking about earlier, multi lingual. Um so you don't need to embrace dot net, for example, as you're programming language to be able to benefit from Dapper, it actually supports many programming languages and Dapper itself is actually written and go. Um and so, you know, all developers can benefit from something like Dapper to make it easier to create microservices applications. >>I mean, always great to have you on great update. Take a minute to give an update on what's going on with your division. I know you had to build conference this week. V. S has got the new preview title. We just talked about what are the things you want to get to plug in for? Take a minute to get to plug in for what you're working on, your goals, your objectives hiring, give us the update. >>Yeah, sure. I mean, you know, we we built integrated container tools in visual studio uh and the Doctor extension and Visual Studio code and cli extensions. Uh and you know, even in this most recent release of our Visual Studio product, Visual Studio 16 10, we added some features to make it easier to use DR composed better. So one of the examples of this is that you can actually have uh Oftentimes you need to be able to use multiple doctor composed files together so that you can actually configure various different container environments for a single single application. But it's hard sometimes to create the right Yeah. My file so that you can actually invoke it and invoke the the container and the micro services that you need. And so what this allows you to do is to actually have just a menu of the different doctor composed files so that you can select the runtime and test environment that you need for the subset of the portion of the application that you're working on at the end of the day. This is always about developer productivity. You know, like I said, every keystroke matters. Um and we want to make sure that you as a developer can focus on the code that only you can Right. >>Amanda Silver, corporate vice president product development division of Microsoft. Always great to see you and chat with you remotely soon. We'll be back in in real life with real events soon as we come out of the pandemic and thanks for sharing your insight and congratulations on your success this year and and congratulations on your announcement here at Dakar Gone. >>Thank you so much for having me. >>Okay Cube coverage for Dunkirk on 2021. I'm John for your host of the Cube. Thanks for watching. Mhm

>>from around the globe. It's the >>Cube with digital >>coverage of AWS reinvent 2020 sponsored by Intel, >>AWS and >>our community partners. >>Welcome back to the cubes ongoing coverage of this year's AWS reinvent. You know, normally we'd be in the middle of the San Sands Convention Center. We have two sets and 50,000 of our closest friends. We'd be deking out on cloud. Seems like a long time ago, but the show must go on. And it does. Joe Duffy is here. He's the co founder and CEO of Gloomy, and Justin Fits you is the vice president engineering for Cloud Engineering for snowflake. Welcome, gentlemen. Good to see you. >>It's good to be here, >>Joe. I love what you guys are doing. You know, leading your customers to the cloud and really attacking that I t labor problem that we've dealt with for years and years by playing a role in transforming what I would say is I t ops into cloud ups with programmable infra infrastructure practices. So take >>a >>moment to tell us. Why did you and your co founder start the company how you got it off the ground? People are always interested in how you got it funded. You got a couple of Seattle VCs, Madrona and Tola involved. Any a just got involved. So congrats on that. What's the story of your company? >>Yeah. So my background and my co founder Eric's background. You know, we spent multiple decades at Microsoft just really obsessing over developer platforms and productivity and trying to make you know developers lives as as as as productive as possible. You know, help them harness the power of software >>toe create, >>you know, innovative new applications and really spent time on technologies like Visual Studio and Ahmed. And and, you know, it really struck us that the cloud is changing everything about how we develop software. And yet from our perspective, coming from developer landed had almost changed nothing. You know, most of our customers were still, you know, developing software like they did 15 years ago, where it was a typical enter your application, they'd kind of write the code and then go to their I t team and say, Hey, we need to run this somewhere. Can you provisioned a few virtual machines? Can you prevision You know, maybe a database or two and and And so And then we went and talked Thio, you know, infrastructure teams and found out Hey, you know, folks were really toiling away with tools that air a pale in comparison when it comes to the productivity that we we were accustomed Thio on the developer side. And then frequently we heard from leaders that there were silos between the organizations. They couldn't build things quickly enough. They couldn't move quickly enough in cloud Native and the new public cloud capabilities just really were pushed pushing on that, really, you know. But the most innovative companies we kept hearing were the ones who figured this out, who really figured out how to move faster in the cloud. Companies like Snowflake really are leveraging the cloud toe transform entire businesses. You look at uber lyft Airbnb, these companies that really harnessed the cloud toe not just from a technical productivity standpoint, but really transform the business. Eh? So that was the opportunity that we saw Kalemie was Let's take a step back. We call this cloud engineering. Let's imagine a world where every developers, a cloud developer and infrastructure teams are enabling that new way of building. >>Great. So you mentioned cloud engineering. Now, Justin, you've done a bit a bit of cloud engineering yourself in your day. You know, the Cube has been following Snowflake very closely since it launched really mid last decade. And we've we've covered your novel, architectural approach and your cloud only mantra. Talk about that. And have there been any changes in how you're thinking about cloud adoption and how that's as that's increased and you've seen new use cases emerged. >>Yeah, so I think, you know, obviously Snowflake was was built on the foundation of cloud first, and in fact, cloud Onley are only platform and only infrastructure is is based on the cloud. But, you know, for us, it was absolutely key on. How do you develop a platform and a product that's completely elastic? Lee, scalable on drily, really allows for kind of the paper use and paper consumption model. We didn't really it would be very difficult for us to offer this and Thio offer a product in this way. On def, you start to think about kind of from a cloud engineering perspective. Um, we don't have the typical network engineers. A typical data center engineers that you that you might have seen previously. Instead, we're shifting our model in our what we do include engineering away from kind of an operations model or even devotes model towards the software engineering model. E. I think that's the That's the big shift to cloud engineering is that we're looking to hire and we're building a team of software engineers to build systems and platforms and and tooling Thio have the system self managed as much as possible, and it changes to our infrastructure that we look at any changes in our platform are all through, commits and and deployed via pipelines, as opposed to having Operator's log on and make these changes. And so that's the shift that I think we're seeing. And that's to kind of match the overall stuff like Model of Cloud, first and on and where the product is like just going. >>Like you said in cloud only, Justin, you use Pollux me in your own engineering and also in your product externally. Is that correct? And how so? >>Yeah, we actually use it in, specifically and, um, in our platform, in order to kind of deployed to manage and, uh, just operate a kind of our overall cloud infrastructure. We specifically use it more focused on the good days and and continue ization side of things. But that use cases kind of rapidly expanding across the organization. >>So I'm curious of what do you guys we're seeing in the market place? Joe, you know, thinking about cloud broadly, What's the impact that you're seeing on businesses? Who are the big players that you see out there? Maybe you could talk about some of the differentiation that you've noticed. >>Yeah, I think this notion of plot engineering, you know, even 3.5 years ago when we got started was in its infancy. You know, we definitely saw that. Hey, you know, the world is moving and shifting left, you know, it's just was saying and really, people are looking for new ways to empower developers, but that empowerment has to come with guard rails, right? And so what we're seeing is oftentimes, teams are now modernizing their entire platform infrastructure platform, and they're looking to technologies like kubernetes to do that. But increasingly, you know, aws, Azure gp. You know, when we started, um, there weren't any great managed kubernetes clusters. And now today, fast forward. You know Onley 3.5 years and and many of our customers are using flew me to help them get up and running with the chaos in AWS, for example, you look at a lot of folks transforming on Prem as well again many times, adopting kubernetes is sort of a if they intend to stay on Prem. You know, Thio, at least modernize their approach to application infrastructure delivery. That's where Pollux me really can help. It could be a bridge. Thio hate from on Prem to the public cloud. There's certainly a lot of folks doing great work in the space, you know, I think VM Ware has really kind of emerged as sort of vanguard thought leader in this in this space, especially with, you know, hep dio and now kind of pivotal joining the story. We see other, you know, great companies like hash in court, for we're doing good work in this space. Um, certainly we integrate with a lot of their technologies on you. Combine those with the public cloud providers. There's also a lot of just smaller startups in the space which you know, strikes in my heart. I love I love supporting the startup ecosystem. You know, whether that's for cell or net lif I or server list. You know, really trying to help developers harness more of the cloud. I think that's an emerging trend that we're gonna see accelerating in the coming years. >>Yeah. Thank you. You've mentioned a number of interesting emerging tools companies in the ecosystem. I mean, Justin talked about kubernetes. Are there other tooling that you're using that that might be, you know, some of your customers might like toe to know about. >>Yeah, I think so. So one thing I wanted to actually follow up with what Joe said here is is around kind of the multi cloud nature of what we do is is the tools, like gloomy are critical for us to be able to abstract away specific cloud provider AP ice and such and so given Snowflake operates on all three major public clouds and offers a seamless experience amongst all three of them. We have to have something that abstracts some of that complexity and some of those technical details away. Andi, that's why I kind of blew me, made sense in in this case and has helped us kind of achieved that cloud neutrality piece. Um, in terms of other tools that that you're thinking that we're talking about, I think Bellamy is doing a great job kind of on some of these on some of the kind of that interaction and infrastructure and sensation. But we're looking for tooling to kind of look for the overall workflow automation piece on orchestration. So what sits on top of say, you're using intervals using terra form? You may be using Polonia's well, but what kind of orchestrates all these pieces together? Onda, How do you kind of build workflow automation? And I think there's a lot of companies and technology providers that air starting up in this area to kind of stitch all these pieces together so that you kind of have a seamless kind of work flow across across your infrastructure. >>Got it. So, Joe, I'm kind of curious you talked a little bit about your background at Microsoft, and you're even a TMC where you're helping, you know, people manage Luns. It was a sort of skill set that is not in high demand today. Early. Shouldn't be people really need to transform? I've said that a lot in the queue, but But, you know, maybe talk a little bit about the experiences that you've had in the past that informed the direction that Pollux me is taking and where you see it going specifically. I mean, I've been talking a lot about the next decade of cloud is not gonna be the same as the last decade of the cloud. How did you How do you see it? >>Yeah, I think I recognize a clear trend, you know, in with cloud computing. Uh, you know, back I can't remember 13 years ago, maybe 15 years ago, When, when When the Azure project started. You know Dave Cutler, who actually founded the anti project at Microsoft, Actually, was was one of the first engineers that started Azure. And he called it a cloud operating system. And, you know, I think that vision of hey, the cloud is the new operating system is something that we're still just chipping away at. And that was that was a clear trend, you know, having seen these transformations in the past, you know the shift from, you know, dos to windows from windows to mobile Thio, client server thio now the cloud every step of the way. We always transform the way we build applications. And I think where we're at now is horse, really in the midst of a transition that I think we'll look back. You never know when it's happening right? But you can always look back in hindsight and see that it did happen. And I think the trend that we're going through now with service meshes and just, you know, micro services and service list is really we're building distributed applications. These clouds made of applications, they're distributed applications. And that was the trend that I, I recognized, also recognizes another trend, which is, you know, we spent 30 years building great tools. You know, I d s test frameworks sharing and reuse package managers. We figured out static analysis and how to fix security problems in this in in programming languages that we've got today. Let's not go rebuild all that. Let's leverage that, and and so that's what Eric and I said they want, you know, Let's stand on the shoulders of giants. Let's leverage all this good work that has come before us. Let's just apply that to the infrastructure domain and really try toe smooth things out. Give us a new sort of level playing field to build on. From here is we go forward and I'm excited that Parliament gives us that foundation that we can now build on top of >>Great and Justin, of course, were covered. Aws reinvent you guys. It was kind of your your first platform. It's your largest, the largest component of your business. And I have been saying, Ah lot that, you know the early days of cloud was about infrastructure last 32 throw in some database. But really, there's a new workload that's emerging. And you guys are at the heart of that where people are putting governed data giving access to that data, making it secure, uh, sharing that data across an ecosystem so that new workload is really driving new innovation. I wonder how you see that what you see the next half a decade or decades looking like in terms of innovation? >>Yeah, I think I think it za valid point, which is, um, it's less about infrastructure and more about the services that you're providing with that infrastructure. And what what value are you able to add and So I think that's it, Snowflake. The thing that we're really focused on, which is abstract away, all these tunes and all these knobs and such, and the how much remember you have on a specific and a piece of infrastructure or describes or anything like that. So what's the business value? And how can we present that business value in a uniform way, regardless of kind of the underlying service provider on baby to a different class of business users, someone who wants a low data and just two analysts against that they really don't want to understand what's happening underneath. And I think that's that's where this club engineering piece comes in. Um, and what my team is doing is really focused on How do we abstract away that kind of lower level infrastructure and scalability pieces and allow the application developers to develop this application that is providing business value in a transparent and seamless way and in elastic way such that we can scale up and down we can. We have the ability, obviously, to replicate both within regions and clouds, but also across different clouds. So from a business resiliency and and up time point of view. That's that's something that's been really important. Um, and I think also how do we security is? Becoming is obviously a huge, huge importance, given the classifications type of day that people are putting within our platform. So how are we able Thio ensure that there is a pipeline where developers have reviews and commits of any kind of changes going into the system and their arm's length away, and could be fully audited for various clients and regular regulatory needs? And that's something that kind of this suffer engineering cloud engineering concept has really helped develop and allowed us Thio obviously be successful with various different types of industries. >>Joe, we're almost out of time. I wonder if you could bring us home. I mean, some of the things Justin was talking about I mean, I definitely see a lot of potential disruption coming from the world of developers. Uh, he was talking. He was talking about consumption models different than many of the SAS pricing models. And how do you How do you see it? Developers air kind of the really the new source of innovation. Your final thoughts. >>Yeah. I think we're democratizing access to the cloud for everybody. I think you know it's not just about developers, but it's It's really all engineers of all backgrounds, its developers, its infrastructure engineers, its operations engineers, its security engineers. You know, Justin's mentioning compliance and security. These air really critical elements of how we deliver software into the cloud. So I think you know what you're going to see is you're gonna see a lot of new, compelling experiences built thanks to cloud capabilities. You know, the fact that you've got a I and M l and all these infinitely scalable data services like snowflake and, you know, just an arm's length away that you can use as building blocks in your applications. You know, application developers love that. You know, if we can just empower them to run fast, they will run fast, and we'll build great applications. And infrastructure teams and security engineers will be central to enabling that that new future. I think you also see that you know infrastructure and cloud services will become accessible to an entirely new audience. You know, kids graduating from college, they understand Java script. They understand python now they can really just harness the cloud to build amazing new experiences. So I think we're still, you know, still early days on the transition to the cloud. I know where many years on the journey, but we've got many, many years, you know, in our future. And it's very exciting. >>Well, thank you, guys, Joe and Justin. I really appreciate it. Congratulations on your respective success. I know is Joe said you got a lot more work to do, but I really appreciate you coming on the Cube. >>Awesome. Thank you. You're >>welcome. All right, so we're here covering reinvent 2020. The virtual edition. Keep it right there for more great content. Were unpacking the cloud and looking to the future. You're watching the cube?

>> Narrator: From around the globe, it's theCUBE with digital coverage of Dockercon Live 2020, brought to you by Docker and it's ecosystem partners. >> Everyone welcome back to Dockercon 2020, #Docker20. This is theCUBE and Docker's coverage of Dockercon 20. I'm John Furrier in the Palo Alto studios with our quarantine crew, we got a great interview segment here and big news around developer workflow code to cloud. We've got Amanda Silver, Corporate Vice President, product for developer tools at Microsoft and Scott Johnson, the CEO of Docker. Scott had a great Keynote talking about this relationship news has hit about the extension of the Microsoft partnership. So congratulations, Amanda, welcome to theCUBE. >> Thanks for having me. >> Amanda, tell us about what your role is at Microsoft. You guys are well known in the developer community. You had to develop a ecosystem even when I was in college going way back. Very modern now, the cloud is the key, code to cloud, that's the theme. Tell us about your role at Microsoft. >> Yeah, so I basically run the product, Product Design and User Research team that works on our developer tools at Microsoft. And so that includes the Visual Studio product as well as Visual Studio code that's become pretty popular in the last few years but it also includes things like the dotNET runtime and the TypeScript programming language, as well as all of our Azure tooling. >> What's your thoughts on the relationship with Docker? Obviously the news extension of an existing relationship, Microsoft's got a lot of tools, you got a lot of things you guys are doing, bringing the cloud to every business. Tell us about your thoughts on this relationship with Docker? >> Yeah well, we're very excited about the partnership for sure. Our goal is really to make sure that Azure is a fantastic place where all developers can kind of bring their code and they feel welcome. They feel natural. We really see a unique opportunity to make the experience really great for the Docker community by creating more integrated and seamless experience across Docker desktop, Windows and Visual Studio and we really appreciate how Docker has kind of, supported our Windows ecosystem to run in Docker as well. >> Scott, this relationship and an extension with Microsoft is really, I think, impressive and also notable because Microsoft's got so many tools out there and they have so successful with Azure. You guys have been so successful with your developer community but this also is a reflective of the new Docker. Can you share your thoughts on how this partnership with Microsoft, extending the way it is, with the growth of the cloud is a reflection of the new Docker? >> Yeah, absolutely John, it's a great question. One of the things that we've really been focused on since November is fully embracing the ecosystem and all the partnerships and all the possibilities of that ecosystem and part of that is just reality that we're a smaller company now and we can't do it all, nor should we do it all. Part of it's the reality that developers love choice and no one's going to change their minds on choice, and third is just acknowledging that there's so much creativity and so much energy outside the four walls of Docker that we'd be silly not to take advantage of that and welcome it and embrace it and provide that as a phenomenal experience for our developers. So this is a great example of that. The Snyk partnership we announced last week is a great example of that and you're going to see many more partnerships like this going forward that are reflective of exactly this point. >> You've been a visionary on the product side, interviewed before. Also deploying is more important than ever, that whole workflow simplifying, it's not getting complex, people want choice, building code, managing code, deploying code. This has been a big focus of yours. Can you just share your thoughts on where Microsoft comes in? Because they got stuff too, you've got stuff, it all works together. What's your thoughts? >> Right, so it needs to work together because developers want to focus on their app. They don't want to focus on duct taping and stringing together different siloed pools. So you can see in the demo and you'll see in demonstrations later throughout the conference, just the seamless experience that a developer gets in the Docker command line inner operating with Visual Studio Code, with the Docker command line and then deploying to Azure and what's wonderful about the partnership is that both parties put real engineering effort and design effort into making it a great experience. So a lot of the complexities around configuration, around default settings, around security, user management, all of that is abstracted out and taken away from the developers so they can focus on applications and getting those applications deployed to the cloud as quickly as possible. Getting their apps from code to cloud is the watchword or the call to action for this partnership and we think we've really hit it out of the park with the integration that you saw. >> Great validation in the critical part of the workflow you guys been part of. Amanda, we're living in a time we're doing these remote interviews. The COVID crisis has shown the productivity gains of working at home and working, sheltering in place but it also has highlighted the focus of developers, mainly who have also worked at home. They're been kind of used to this, you see the rigs. I saw at Microsoft build some amazing rigs from the studio, so these guys streaming their code demos. This is a Cambrian explosion of new kinds of productivity. You got the world's getting more complex at scale. This is what cloud does. What's your thoughts on this? 'Cause the tooling, there's more tools than ever, right? >> Yeah. >> I still got to deploy code. It's got to be more agile, it's got to be faster, it's got to be at scale. This is what you guys believe in. What's your thinking on all these tooling and abstraction layers? And the end of the day, developers still got to do their job. >> Yeah, well, absolutely. And now even more than ever, I think we've certainly seen over the past few months, a more rapid acceleration of digital transformation that has really happened in the past few years. Paper processes are now becoming digital processes all of a sudden. Everybody needs to work and learn from home and so there's just this rapid acceleration to kind of move everything to support our new remote first lifestyle. But even more so, we now have remote development teams actually working from home as well in a variety of different kinds of environments, whether they're using their own personal machine to connect to their infrastructure or they're using a work issued machine. It's more important than ever that developers are productive but they are productive as a team. Software is a team sport, we all need to be able to work together and to be able to collaborate. And one of the most important aspects of agility for developers is consistency. And what Docker really enables with containerization, is to make the infrastructure consistent and repeatable so that as developers are moving through the lifecycle from their local desktop and developing on their local desktop, to a test environment and to staging and to production, it's really, it's infrastructure for developers as well as operations. And so, that infrastructure, that's completely customizable for what the developers operating system of choice is, what their app stack is, all of those dependencies kind of running together. And so that's what really enables developers to be really agile and have a really fast iteration cycle but also to have that consistency across all of their development team. And we now need to think about things like, how are we actually going to bring on interns for the summer and make sure that they can actually set up their developer boxes in a consistent way that we can actually support them and things like Docker really help with that. >> As your container instances and Visual Studio cloud that you guys have has had great success. There's a mix and match formula here and the other day, developers want to ship the code. What's the message that you guys are sending here with this because I think productivity is one, simplification is the other but as developers, we're on the front lines and they're shipping in real time. This is a big part of the value proposition that you guys bringing to the table. >> Yeah, the core message is that any developer and their code is welcome (laughs) and that we really want to support them, empower them and increase their velocity and the impact that they can have. And so, having things like the fact that the Docker CLI is natively integrated into the Azure experience is a really important aspect of making sure that developers are feeling welcome and feeling comfortable. And now that the Docker CLI tools that are part of Docker desktop have access to native commands that work well with Azure container instances, Azure container instances, if anybody is unfamiliar with that, is the simplest and fastest way to kind of set up containers in Azure and so we believe that developers have really been looking for a really simple way to kind of get containers on Azure and now we have that really consistent experience across our servers, services and our tools. Visual Studio code and Visual Studio extensions make full use of Docker desktop and the Docker CLI so that they can get that combination of the productivity and the power that they're looking for. And in fact, we've integrated these as a design point since very early on in our partnership when we've been partnering with Docker for quite a while. >> Amanda, I want to ask you about the tool chain. We've heard about workflows, making it simpler. Bottom line from a developer standpoint, what's the bottom line for me? What does this mean to me, everyday developer out there? >> I really think it means, your productivity on your terms. And so, Microsoft has been a developer company since the very beginning with Bill Gates and GW Basic. And it's actually similar for Docker. They really have a developer first point of view, which certainly speaks to my heart and so one of the things that we're really trying to do with Docker is to make sure that we can create a workflow that's super productive at every stage of the developer experience, no matter which stack they're actually targeting, whether there's targeting Node or Python, or dotNET and C Sharp or Java, we really want to make sure that we have a super simple experience that you can actually initiate all of these commands, create Docker container images and use the Docker compose files. And then, just kind of do that consistently, as you're deploying it all the way up into your infrastructure in Azure. And the other thing that we really want to make sure is that that even post deployment, you can actually inspect and diagnose these containers and images without having to leave the tool. So we also think about the process of writing the code but also the process of kind of managing the code and remediating issues that might come up in production. And so we really want you to be able to look at containers up in the Azure, that are deployed into Azure and make sure that they're running and healthy and that if something's wrong, that you can actually open up a shell and be in an interactive mode and be able to look at the logs from those containers and even inspect one to see environment variables or other details. >> Yeah, that's awesome. Writing code, managing code and then you got to deploy, right? So what I've been loving about the past generation of Agile is deployment's been faster to play off all the time. Scott, this brings up that the ease of use but you'll want to actually leverage automation. This is the trend that you want to get into. You want to make it easy to write code, manage code but during the deployment phase, that's a big innovation. That's the last point, making that better and stronger. What's your thoughts on simplifying that? >> Well, as a big part of this partnership, John, that Docker and Microsoft embarked on, as you saw from the demo in the keynote, all within the Docker command line, the developer's able to do it in two simple commands, deploy an app, define and compose from their desktop to Azure. And there's a whole slew of automation and pre-configured smart defaults or sane defaults that have gone on behind the scenes and it a lot of hardcore engineering work on part of Docker-Microsoft together to simplify that and make that easy. And that goes exactly to your point, which is, the simpler you can make it, make an abstract way to kind of underline plumbing and infrastructure, the faster Devs can get their application from code to cloud. >> Scott, you've been a product CEO, you've been a product person now you're the CEO but you have a product back when you've been involved with a relationship with Microsoft for a long time. What's the state of the market right now? I see Microsoft has evolved because just the performance, corporate performance, the shift to the cloud has been phenomenal. Now developers getting more empowered, there's more demand for the pressure to put developers to do more and more creativity. So you've seen this evolve, this relationship, what does it mean? >> Yeah, it's honestly a wonderful question, John and I want to thank Amanda and the entire Microsoft team for being long standing partners with us on this journey. So it might not be known to everyone on today's day's event but Microsoft came to the very first Dockercon event way back in June 2014 and I had the privilege of greeting them and welcoming them and then they were full on, ready to see what all the excitement about Docker was about and really embraced it. And you mentioned kind of openness in Microsoft's growth over time in that dimension and we think Docker, together with Microsoft have really shown what an open developer community can do. That started back in 2014 and then we embarked on an open source collaboration around the Docker command line of the Docker engine, bringing that Docker engine from Linux and now moving it to Windows applications. And so all the sudden the promise of write once and use the same primitives, the same formats, the same command lines, as you can with Linux onto Windows applications, we brought that promise to the market. And it's been an ongoing journey together with Microsoft on open standards base, developer facing friendliness, ease of use, fast time to deploy and this partnership that we announced yesterday and we highlighted at the keynote is just another example of that ongoing relationship, laser-like focused on developer productivity and helping teams build great apps. >> Why do you like Azure in the cloud for Docker? Can you share why? >> Well, as Amanda has been sharing, it's super focused on, what are the needs of developers to help them continue to stay focused on their apps and not have their cognitive load burdened by other aspects of getting their apps to the cloud and Azure does a phenomenal job of simplifying and providing sane defaults out of the box. And as we've been talking about, it's also very open to partner integrations like the one we've announced yesterday and highlighted that make it just easy for development teams to choose their tools and build their apps and deploy them onto Azure as quickly as possible. So it's a phenomenal platform for developers and we're very excited and proud to partner with Microsoft on it. >> Amanda on your side, I see Docker's got millions of developers. you guys got millions of developers even more. How do you see the developers in Microsoft's side engaging with Docker desktop and Docker hub? Where does it all fit? I mentioned earlier how I see Docker context really improving the way that individuals and teams work with their environments in making sure that they're consistent but I think this really comes together as we work with Docker desktop and Docker Hub. When developers sign in to Docker Hub from Docker desktop, everything kind of lights up and so they can see all of the images in their repositories and they can also see the cloud environments that they're running them in. And so, once you sign into the Hub, you can see all the contexts that map to the logical environments they have access to, like Dev, NQA and maybe staging. And another use case that's really important is that we can access the same integration environment. So, I can have microservices that I've been working on but I can also see microservices that my teammates and their logs from the services that they've been working on, which I think is really great and certainly helps with team productivity. The other thing too, is that this also really helps with hybrid cloud deployments, where, you might have some on-premises hosted containers and you might have some that's hosted in a public cloud. And so you can see all of those things through your Docker Hub. >> Well, I got to say, I love the code to cloud tagline, I think that's very relevant and catchy. And I think, I guess to me what I'm seeing and I'd love to get your thoughts, Amanda on this is you oversee a key part of Microsoft's business that's important for developers, just the vibe and people are amped up right now. I know people are tensed, anxiety with the COVID-19 crisis but I think people are generally agreeing that this is going to be a massive inflection point for just more headroom needed for developers to accelerate their value on the front lines. What's your personal take on this? You've seen these waves before but now in this time, what are you most excited about? What are you optimistic about? What's your view on the opportunities? Can you share your thoughts, because people are going to get back to work. They're working now remotely but if we go back to hybrid world, they're going to be jamming on projects. >> Yeah, for sure but people are jamming on projects right now and I think that in a lot of ways, developers are first responders in that they are... Developers are always trying to support somebody else. We're trying to support somebody else's workflow and so we have examples of people who are creating new remote systems to be able to schedule meetings in hospitals for the doctors who are actually the first responders taking care of patients but at the end of the day, it's the developer who's actually creating that solution. And so we're being called to duty right now and so we need to make sure that we're actually there to support the needs of our users and that we're basically cranking on code as fast as we can. And to be able to do that, we have to make sure that every developer is empowered and they can move quickly but also that they can collaborate really quickly. And so I think that Docker Hub, Docker kind of helps you ensure that you have that consistency but you also have that connection to the infrastructure that's hosted by your your organization. >> I think you nailed, that's amazing insight. I think that's... The current situation in the community matters because there's a lot of frontline work being done to your point but then we got to rebuild, the modernization is happening as well coming out of this so there's going to be that. And there's a lot of camaraderie going on and massive community involvement I'm seeing more of. The empathy but also now there's going to be the building, the creation, the new creation. So, Scott, this is going to call for more simplicity and to abstract away the complexities. This is the core issue. >> Well, that's exactly right. And it is time to build and we're going to build our way out of this and it is the community that's responding. And so in some sense, Microsoft and Docker are there to support that moory energy and give them the tools to go and identify and have an impact as quickly as possible. I referenced in the keynote, completely bottoms up organic adoption of Docker desktop and Docker Hub in racing to provide solutions against the COVID-19 virus. It's a war against this pandemic that is heavily dependent on applications and data. And there's over 200 projects, community projects on Docker Hub today, where you've got tools and containers and data analysis all in service to the COVID-19 battle that's being fought. And then as you said, John, as we get through the other side, there's entire industries that are completely rethinking their approach that were largely offline before but now see the imperative and the importance of going online. And that tectonic shift, nearly overnight of offline to online behavior and commerce and social and going down the list, that requires new application development. And I'm very pleased about this partnership is that together, we're giving developers the tools to really take advantage of that opportunity and go and build our way out of it. >> Well, Scott, congratulations on a great extended partnership with Microsoft and the Docker brand. I'm a big fan from day one. I know you guys have pivoted on a new trajectory, which is phenomenal, very community oriented, very open source, very open. So congratulations on that. Amanda, thanks for spending the time to come on. I'll give you the final word. Take a minute to talk about what's new at Microsoft for the folks that know Microsoft, know they have a developer mindset from day one. Cloud is exploding, code to cloud. What's the update? What's the new narrative? What should people know about Microsoft with developer community? Can you share some data for the folks that aren't in the community or might want to join or the folks in the community who want to get an update? >> Yeah, it's a great kind of question. Right now, I think we are all really focused on making sure that we can empower developers throughout the world and that includes both those who are building solutions for their organizations today but also, I think we're going to end up with a ton of new developers over this next period, who are really entering the workforce and learning to create digital solutions. Overall, there's a massive developer shortage across the world. There's so much opportunity for developers to kind of address a lot of the needs that we're seeing out of organizations, again, across the world. And so I think it's just a really exciting time to be a developer and my only hope is that basically we're building tools that actually enable them to solve the problem. >> Awesome insight, and thank you so much for your time. Code to cloud developers are cranking away, they're the first responders, going to take care of business and then continue to build out the modern applications. And when you have a crisis like this, people cut right through the noise and get right to the tools that matter. So thanks for sharing the Microsoft-Docker partnership and the things that you guys are working on together. Thanks for your time. >> Thank you. >> Thank you. >> Okay, this is theCUBE's coverage. We are at Dockercon 2020 Digital. This is theCUBE Virtual. I'm John Furrier, bringing all the action, more coverage. Stay with us for more Dockercon Virtual after this short break. (gentle music)

>> From the silicon angle media office in Boston Massachusetts, it's the Cube. Now here's your host, Dave Vellante. >> Hello everyone and welcome to this week's episode of wiki buns cube insights, powered by ETR. In this breaking analysis, I plan to look deeper into the cloud market and specifically the business results and the momentum of the big three U.S cloud players. Now, Google last week opened up a bit and they not only broke out YouTube's revenues but also its cloud business. And quite a bit more detailed now like Microsoft the numbers are still somewhat opaque and hard to compare with AWS numbers which I find much cleaner. Nonetheless by squinting through the data, we're able to better understand the momentum that these three companies have in cloud and of course the ETR spending data, gives us an added data-driven dimension that is really insightful and helpful. Today we're focusing on, the big three in cloud. Amazon's AWS, Google's cloud platform GCP and Microsoft Azure. Now to meet the other U.S players are not hyper scalars and they're really not even in the discussion other than is an extension of their existing business. As an example, it would take IBM and Oracle between four and six years to spend as much on capex as Google spends, in four months. Now coming back to the big three. Each of these companies is coming at the opportunity with a different perspective. But Amazon and Microsoft, have been on a collision course for quite some time now. Google of course aspires to get into that conversation. Amazon in my opinion is the gold standard in cloud and I specifically refer to infrastructure as a service. They created the market and have earned the right to define the sector. Competitors like Microsoft are smart to differentiate and I'm going to discuss that. But first, let's take a listen as to how Amazon's CEO Andy Jassy Amazon web services CEO Andy Jassy, thinks about the goals of the AWS business. Roll the clip please. >> A high-level are top-down aggressive goals that we want every single customer who uses our platform to have an outstanding customer experience. And we want that outstanding customer experience in part is that their operational performance and their security are outstanding. But also that it allows them to build projects and initiatives that change their customer experience and allow them to be a sustainable successful business over a long period of time and then, we also really want to be the technology infrastructure platform under all the applications of people build. >> So, what's interesting to me here is how Jesse thinks about the AWS platform. It's a platform, to build applications. It's not a SaaS, it's not a platform which AWS can use to sell its software packages, it's a place to build apps. Any application, any workload, any place in the world. So when I say AWS has clean numbers, it's because they have a clean business. Infrastructure is what they do, period. That's what they report in their numbers and it's clean. Now compare that with Microsoft. Microsoft is doing incredibly well in the cloud and will come back to that, but Microsoft is taking a much different approach to the market. They report cloud revenue but it comprises public, private and hybrid. It includes SQL Server, Windows Server, Visual Studio, System Center, GateHub and Azure. And also support services and consulting. But the key here is they defined cloud to their advantage which is smart trying to differentiate with a multi cloud any cloud, any edge, story. Think Microsoft Azure stack slash Microsoft Ark etc. Now Google as we know is coming at this as a late comer. They admit they're a challenger. Their starting point is G suite. Their cloud focus is infrastructure and analytics. So, with that as some background let's take a look at the wiki bond estimates for I as revenue in 2019. What we have here is our estimates of AWS Azure and GCPs is IaaS and PaaS revenue, for 2018 and 2019. We've tried to strip out everything else so we can make an apples-to-apples comparison with Amazon. So let's start with Amazon. The street is concerned about the growth rate of AWS. It grew 35% last quarter, which admittedly is slowing down. But it did just under 10 billion. Think about that. AWS will probably hit a 50 billion dollar run rate this year 50 billion and it's growing in the double digits. AWS is going to be larger than Oracle this year and Cisco is next in its sights. it's like Drew Brees knocking down records in the NFL. Microsoft is very strong but remember, these are estimates. They report as your growth, but they don't really give us a dollar figure. We have to infer that from other data. So the narrative on Microsoft is they're catching up to AWS and in one-dimension that's true because they're growing faster than AWS. But AWS in 2019 grew by an amount almost equal to Asher's entire business in 2018. Now Google is hard to peg. The only thing we know is Google said it's cloud business was 9 billion in 2019, up from 5.8 billion in 18 and 4 billion in 17. So we're seeing an accelerating growth rate. That they said is largely attributable to GCP and they told us that GCP is growing significantly faster than their overall business. Which remember includes, G suite, cloud business that is. Okay. So that's the picture. Now, I want to take a minute to talk about the profitability of the cloud. On the Microsoft earnings call, Heather Bellini of Goldman Sachs, she was effusive she's an analyst exclaiming how impressed she was with the fact that Microsoft has been consistently increasing its cloud gross margins each quarter. I think was up five points in the last quarter. And on the Google call, Heather again was praising Google CEO Sundar Pichai on gross margin guidance for GCP. Which Sundar didn't answer. As well, Andy Jassy said in the Q blast reinvent that the cloud was higher margin than retail but it's scale, it's a relatively low margin business. As compared to software. I would like to comment on all this. First I think Jesse is sandbagging. AWS is a great margin business in my opinion. AWS has operating margins consistently in the mid 20s like 26% last quarter. Now, Bellini on the earnings call, was pressing on gross margins which in my opinion are even more impressive. Here's why. This is a chart I drew a long long time ago. It's a very basic view of the economics of the different sectors of the technology business. Namely hardware, software and services. Now, that each have a different margin profile as we're showing here. On the vertical axes, marginal cost that is the incremental cost of producing one additional unit of a product or service. On the horizontal axis, is volume. And we're showing the Pre-Cloud Era on the left and the Post-Cloud Era on the right-hand side of the chart. And you can see each segment has a different cost and hence different margin profile. In Hardware, you have economies at volume but you have to purchase and assemble components and so at some point your marginal cost hit a floor. Professional services have a diseconomies of scale. Meaning at higher volume, things get more complex and you have more overhead. Now that red line is software and everybody loves software because the marginal costs go to zero and your gross margin approaches the cost of distributing the software. Back in the old days, it really came down to the cost of a what our custom distributed a disk or a CD. So software gross margins are absolutely huge. Now let me call your attention to the green line that we've labeled outsourcing. In the pre-cloud era, outsourcing companies could get some economies but it really wasn't game changing. But in the post-cloud world the hyper scalars are driving automation. Now I'm exaggerating the margin impact because the cloud players still have to buy hardware and they have other costs. But the point is, gross margin and outsourcing IT to a cloud player is far more attractive to the vendor at scale. So Heather Bellini, was essentially asking Sachini Adela how is it that you can keep expanding your gross margins each quarter and she was trying to understand, if GCP gross margins were tracking similar to where AWS and Azure were back when they were smaller. And I think these curves at least give us some guidance. All right, so now let's pivot into the ETR data. This chart shows net score which remember, refers to spending velocity for each of the big three cloud players. Over the past nine surveys for cloud computing the cloud computing sector. Now three things stand out. First is that AWS remains very strong with net scores solidly in the 60% plus range. Second, is Azure has sustained a clear momentum lead over AWS, since the July 18 survey. And the third, is look at GCP's uptick. It's very notable and quite encouraging for Google. Now, let's take another cut on this data and drill into the larger companies, in the ETR data set. Look what happens when you isolate on Fortune 500. Two points here, AWS actually retakes the lead over azure, in net score or spending velocity even though Azure remains very strong. Amazon's showing in large accounts is very very impressive. Nearly back to early 2018 peak levels at 76%. So really strong net scores. The second point is GCPs uptrend holds firm and actually increases slightly, in these larger accounts. So it appears, that the big brands which perhaps used to shy away from cloud, are now increasingly adopting. Now, one of the things ETR does that I love is these drill downs, where they'll ask specific questions that are both timely and relevant. So we want to know, what every salesperson wants to know. Why do they buy? And that's what this chart shows. It shows data from the ETR drill downs and on the left hand in the green or the y the buys from Microsoft AWS and Google cloud. For Microsoft CIOs a compatibility with existing skills and the organization's IT footprint then its feature set etc. Look here's the deal, this is mr. softies huge advantage. It's just simpler to migrate work to Azure if you're already running Microsoft apps. And if Microsoft continues to deliver adequate features it's a no-brainer for many customers. For AWS, the pluses are ROI near-term and long-term and I've said many times, best cloud in terms of reliability, uptime, security AWS has the best cloud for infrastructure. And if you're not incurring huge migration cost or if you're not Walmart, why wouldn't you go, with the best cloud? Now GCP comes down to the tech. Google has good tech and IT guys. They're geeks. And geeks love Tech. And when it comes to analytics, Google is very very strong as well. Now the right-hand side of this chart shows why this is not in my opinion a winner-take-all game. The chart shows the percent of workloads in the cloud today in two years and three years across different survey dates. Today it's between 25% and 35% and it's headed upwards to 50% , this is a huge growth opportunity for these companies. You know sometimes people say to me that Google doesn't care about the cloud because it's such a small piece of their business or well they can't be number one or number two so they'll exit it. I don't buy this for a second. This is a trillion dollar business. Google is in it for the long game, and in my opinion, is going to slowly gain share over time. All right let's wrap up by looking forward to 2020 and beyond. The first thing I want to say is feel good for Google for reporting its cloud revenues but I think Google has to show more in cloud. I understand it's a good first step but IT buyers are still going to want to see more transparency. The other point I want to make is we are entering a new era the story of the past isn't going to be the same as this decade. Buyers aren't afraid of cloud anymore. It has become a mandate. The dominant services of the past and compute storage and networking to still be there but they're evolving, to support analytics, with AI and new types of database services. And these are becoming platforms for business transformation. Competition is, as we've seen, much more real today. Buyers have optionality. And that's going to create more innovation. SaaS, continues to be a huge factor but more so than ever. And hybrid and multi cloud is increasingly real and it's become a challenge for IT buyers so, I expect AWS is going to enter the ring in a bigger way to expand its Tim. Finally developers are no longer tinkerers, they are product creators. Now they said, there's a huge market. And the big tree can all participate as well as overseas players like, Ali Baba. As a customer it's becoming a more and more complicated situation. Cloud is not just about experimentation or startups it's increasingly about something that you really need to get right. Where to bet, migration and managing risks all become much more critical. On one hand, optionality is a good thing but if you make the wrong bet, it could be costly if you don't have a good exit strategy. Now as always, I really appreciate the comments that I get on my LinkedIn post and on Twitter I'm @DVellante So thanks for watching and thanks for your comments and your feedback This is Dave Vellante for the cube insights powered by ETR. We'll see you next time. (upbeat music)

>> Announcer: Live from Orlando, Florida, it's theCUBE, covering Microsoft Ignite, brought to you by Cohesity. >> Good morning, everyone, and welcome back to theCUBE's live coverage of Microsoft Ignite. 26,000 people from around the world have descended onto the Orlando, here in Orlando, for Microsoft Ignite. I'm your host, Rebecca Knight, along with my cohost, Stu Miniman. We are joined by Christina Warren. She is the senior cloud advocate at Microsoft. Thank you so much for coming on the show. >> Thanks so much for having me. >> So I'd love to have you talk a little bit about your work as a senior cloud advocate. And you are responsible for a lot of the video strategy of Channel 9. >> Yeah, I am. So we have a cloud advocacy scene within developer relations, and most of our advocates are focused on either kind of a specific technology area or a specific audience. I'm a little bit different in that I am kind of of a, I call myself, I'm kind of a jack of all trades, master of none. So I go across a lot of different technology areas, but I look at our video content and our video strategies that we have at Channel 9 and our YouTube channel, Microsoft Developer, and some of our other channels, and I think about what are they types of stories we want to tell, what's content do we want to create for our audience, and how can we bring new developers into our ecosystem, as well. >> So what are those stories? I mean, what do you, what are you hearing from customers and what are you hearing also from colleagues at Microsoft that say, "Here's something that we need to tell the world about"? >> Yeah, so I think it's really interesting. I think there are a lot of things. One, there, we were talking a little bit before the show. There's kind of an insatiable, I think, need for a lot of people how to get started, whether it's getting started coding, if you're wanting to learn Python or learn JavaScript or something else, or even if you're just wanting to, you're starting to get into infrastructure, and you're wanting to learn, okay, how do I, you know, spin things up on the cloud. How do I set things up? And having some of that base fundamentals content is really important, but I also think sometimes it's about troubleshooting, and it's about figuring out what are the new services. What can this do for me? And I think a lot of times, when I think about the stories we want to tell, it's not, oh look at how great our service or our product is but it's this is designed to ease my pain points and make my life as a developer or an ops person easier. >> Christina, in the early days, everybody thought that, you know, the promise of cloud was it, it was supposed to be simple and inexpensive, and unfortunately, we learned it is neither of those things by default, so, you know, how do we help people to go from, you know, it's only 20% of applications today are in the cloud. You know, really simplicity is something we need to attack, and education is one of those areas that we need, you know. Give us some examples of some of the things that your team's doing to try to help us get to the majority of environments and work loads. >> Yeah, so a great example is, you know, .NET Core 3.0 launched a couple of months ago, and there's been a big push there with cloud-native apps and cloud-native applications, and so we have like a new video series, The Cloud Native Show, that my colleague Shane Boyer heads up, where they go through kind of all the steps of cloud-native development. And what's great about this is that you have existing .NET developers who have not, to your point, you know, 80% of applications are still not on the cloud, so they're going from that older environment. And then this is saying, you can take the skills you already have, but this is how you think about these things in this new environment. And for a lot of things when it comes to tech, if you're, the way I can always think about things is the next generation of developers, they don't know a non-cloud world. They're literally cloud-first, and I think that's an important thing for all of us to consider is that the next generation developers, the kids who are in high school now, the kids who are in college, they don't know, you know, the pain of having to provision and deal with their own, you know, servers or data centers. They've only known the cloud. And so, but that's an interesting opportunity both to create cloud-first content for them, but for the people who have been using things to say, okay, what you've already been doing, there are changes, but you're not starting from zero, and you can take some of the things you already know and just move that into, into the new world. >> Yeah, well, one of the interesting things we've found this week is that when we talk about engaging with Microsoft, it's not just .NET, it's not just Windows, or Azure. We talked yesterday with Donovan Brown and Scott Hanselman, and it's you know, any app, any language, your tools, pulling those off together. That's really challenging from, you know, creating content out there, because, you know, you're not going to recreate the entire internet there. So how do you tie in what you're doing with other resources and have that, you know, communication, collaboration out there in the industry? >> So a lot of it I think from what I do and what a lot of us do, I look, I used to be a journalist, so I look at what's interesting to me and what stories I would want to tell and what things I would want to know more about. And so, you know, Visual Studio Online, which was announced this week, massive announcement. I'm super excited about that. I am super excited about what that means, and I know that the audience is going to be excited about that. So I look at an announcement like that, and I'm like okay, what kind of content can we work with with those product teams to do? What sort of tutorials would I like to build? What things would I want to know more about if, if I were, you know, really experienced or just getting started? And I think some other areas are, for instance, Windows Subsystem for Linux 2, WSL 2 will be coming out in the future. That's a great opportunity for people who are both familiar with Linux and might not be familiar with Linux to kind of get started and using Windows as their development platform. And so when I see trends like that happening or things around, you know, containers, you know, Kubernetes, you know, containerize all the things, start thinking about, okay, what are the opportunities? What are cool examples? What would I want to see as somebody who, who's tuning in? That's what I always try to think about is what would. I just try to think about it like a journalist. You know, what would an interesting story be to tell from my perspective? What would I want to know more about? And then we can go from there and work with the product groups and work with some of the other teams to make sure that we can tell those stories. >> So, I'm curious. As a former journalist, you spent a decade as a digital editor and reporter and commentator. What made you want to make the leap to big tech? >> You know, okay, so media is not a great place right now. So that's number one. Number two, you know, I was very technical as a journalist, and it was interesting because when I made that transition, I then had to really actually shore up my tech skills. And I said, okay, I have some of the basics, but I really need to like double down and invest in myself and invest in learning more. But I always, even when I was a journalist, I loved telling developer stories, and I loved advocating for developers. Even when I was, I was working at really mainstream places like Mashable, where, you know, they would send me to developer conferences, and I wouldn't just go to the press things. I would want to go to the sessions and talk to the developers and find out, okay, what are you excited about? What are the opportunities you see to build things? What's coming around that has you excited? I've always loved that. And so when the opportunity presented itself for me to be able to do that at Microsoft, I was like, oh, you know, I'd never considered that before, but that's really interesting, and that would be a interesting way of maybe seeing if I can do something else. >> One of the skills that you, that you, is common between what you do now and as work as a journalist is breaking down this technical language and making it accessible for a wider audience, particularly at more mainstream publications. What is your advice for people in terms of how to do that? Because on this show, we have a lot of technically-minded people who can really go deep into technology. But how do you then make it accessible? What is, what is your advice? >> I always try to think of who is your muse as someone who might not know what's, all the intricacies that are going on but is an intelligent person that can understand. So for me, I always use my mom. Now this was easier when I was a tech journalist than it is what I do now because she understands even less what I do now, but I try to think about, okay, how would I explain this to her? She doesn't need to know all of the intricacies, the nitty-gritty. But how could I explain something to her that would be technically accurate but would get the basic idea? And I think a lot of times when it comes to breaking down content, it's just getting to the essence of what problem is this solving, what is this doing that's better or worse, and how does it do it and in starting from there. And it, a lot of times it just takes a lot of work, and you figure out as you go along what getting feedback from users, frankly, based on they might be asking more clarifying questions, or maybe they'll want to know more about something or less about something else. This is confusing for me. And just modulating that as you go along. >> Yeah, Christina, it makes me laugh, actually. When I started blogging, my mother was one of the people that would read, and she would say, "Oh, yes, I heard about this cloud thing before. "I watched it on NPR." It's a nuanced and complicated message. I actually, I roll my eyes a little bit back at the old Microsoft to the cloud videos there, because it was like it didn't resonate. It's the stories that you're telling these days. How do you balance there's the outcomes is, yes, we want to, you know, solve, you know, some of the great challenges and help healthcare, but, you know, underneath, there's some nitty-gritty developer and infrastructure things that get solved. How do you make sure there's the connections between, you know, what the products do and the outcomes? >> Yeah, that's really interesting. You're right, it is a challenge. I think the, the important thing here is not every message has to have all of those components. So you can tell different stories. You could tell one story that's just more focused on the outcome and is just more focused on the opportunity and what's happening in healthcare, and you could have another story that might be about this is what's going on underneath that is allowing those things to happen. >> Yeah, do you, do you have any favorite, you know, outcome stories from Microsoft? >> Gosh, you know, yesterday, during Scott Hanselman's developer keynote, he was, he was, I didn't even know about the Chipotle case study. That was so interesting to me and seeing what they're doing with the different technology. That's, that was a really, that's just the first one that comes to mind I thought was really cool. I'm really excited about the opportunities we have in Quantum, and I'm really excited about opportunities in healthcare because, you know, I think we've all been to the doctor, and we've seen how much IT and how much tech infrastructure could help not just the process of diagnosing and helping things but just, even just the minutia of data entry and record delivery and keeping track of everything. So there, a lot of the things we've done there have been really interesting. >> One of the things you said is you love telling developer stories, and I'm a journalist, too. And I cover entrepreneurs, and I feel the same way about telling entrepreneur stories. Talk about some of the common characteristics you've seen. I mean, we can't obviously generalize an entire population of people, but talk about what you have seen as sort of the common elements of their personalities and their approach to solving problems. >> Right, so I think it's interesting. When I think about any developers, which are a little bit different than enterprise devs, although there are some similarities, you know, you start with, and I know for me when I start first started coding and when I first started building websites and then other things, like, for me, I wanted to either solve a problem, or I wanted to create something that other people could, could see. And so a lot of times that probably one of the more commonalities is, you know, developers, they're in many ways wanting to scratch their own itch. I wanted to do something, I couldn't figure out how to do it, so I built this myself, found out other people were using it, too, and I added features to it. I mean, I think that's what's so great about open-source is that people have the opportunity to collaborate either contributing code or even, you know, doing bug reports and or sharing ideas. And so I, one of the more common elements is I wanted to do something, or I had a really interesting idea, and I didn't see anyone else doing it, and so I just decided to build it myself. It's not that different from entrepreneurs, right. Like it's I see, I see a business opportunity, I see a business I want to do, so I'm going to build it. And that's, wanting to build things is probably the most common thing I see. >> Yeah, Christina, any common conversations or things that are coming up that, you know, people that aren't at this show, you'd like to share? >> Oh, gosh, I mean, I think there's been so much good stuff. I mentioned Visual Studio Online, which I think is really exciting because I'm really excited about being able to like be on my iPad and also code. Like, that's going to be really great. Also, I think the Arc stuff, the Azure Arc stuff is really interesting, the idea of being able to not just be focused on, you know, one platform, but being able to control all of your infrastructure no matter where it is is really, really, that's a really compelling story. That's something that makes me really excited because I love to just automate and simplify things, so anything that can make, you know, the life easier, I think is great. >> As a former journalist, I'd love your thoughts on the state of news today. I know you said you got out of it because it's not a great career path, but the overreach of social media, the spread of fake news, the real and perceived media biases. I'm interested in your thoughts about where we are today, particularly as it relates to coverage of technology. >> It's interesting. I think in some ways technology. For a really long time, most technology coverage was almost cheerleaderish. You could even look back even 20 years when the dot-com crash happened, and I was in high school then, but I was following all of that avidly. The after flow of that, the business press was maybe a little bit burned, but the technology press was still very much gung ho and was still very much cheerleading. That's changed a little bit as we've started to have to grapple with some of the consequences, good and bad, that happened with tech and with the internet. Right now, I almost feel like maybe we've gone a little bit over the edge a little bit more, and some of the critiques are fair, and some of them maybe are just, you know, it's popular to kind of be more negative. So that's been an interesting change, I think to see. You're right, though, when it comes to the spreading of kind of misinformation or people just reading things in headlines, it's really difficult I think, for people to find authoritative voices and things they can trust. Weirdly, though, I do actually think this is an opportunity for the big tech companies to help. This is things that AI could really play a big role in. These are things that could really kind of help, you know, recognize patterns of scan bots and of other things that aren't there and filter that out. But I think even when, I still feel good about journalism as a medium. I still think that the press is one of the most important assets we have, and even when we are going through shakier times, there are opportunities. I think that we will, it'll find it's way. And honestly, I really do think that technology is one of those things that will help get the real things, the important stories out there. >> All right, so, Christina, I guess final word is how should people think of Microsoft in 2019? >> We're here to help. You know, I think that we are, we are a technology company that is, that is creating the tools so that you can build and solve the problems that you need to solve. >> All right, that's a, that's a great note to end on. Thank you so much for coming on the show, Christina. >> Thank you so much for having me. >> Stay tuned for more of theCUBE's live coverage of Microsoft Ignite coming up in just a little bit. (upbeat instrumental music)

>> Announcer: Live from Orlando, Florida it's theCUBE! Covering Microsoft Ignite, brought to you by Cohesity. >> Hello, and happy taco Tuesday CUBE viewers! You are watching theCUBE's live coverage of Microsoft's Ignite here in Orlando, Florida. I'm your host Rebecca Knight, along with Stu Miniman. We're joined by Scott Hanselman, he is the partner program manager at Microsoft. Thank you so much for coming on theCUBE! >> Absolutely, my pleasure! >> Rebecca: And happy taco Tuesday to you! Will code for tacos. >> Will code for tacos. >> I'm digging it, I'm digging it >> I'm a very inexpensive coder. >> So you are the partner program manager, but you're really the people's programmer at Microsoft. Satya Nadella up on the main stage yesterday, talking about programming for everyone, empowering ordinary citizen developers, and you yourself were on the main stage this morning, "App Development for All", why is this such a priority for Microsoft at this point in time? >> Well there's the priority for Microsoft, and then I'll also speak selfishly as a priority for me, because when we talk about inclusion, what does that really mean? Well it is the opposite of exclusion. So when we mean inclusion, we need to mean everyone, we need to include everyone. So what can we do to make technology, to make programming possible, to make everyone enabled, whether that be something like drag and drop, and PowerApps, and the Power platform, all the way down to doing things like we did in the keynote this morning with C# on a tiny micro-controller, and the entire spectrum in between, whether it be citizen programmers in Excel using Power BI to go and do machine learning, or the silly things that we did in the keynote with rock, paper scissors that we might be able to talk about. All of that means including everyone and if the site isn't accessible, if Visual Studio as a tool isn't accessible, if you're training your AI in a non-ethical way, you are consciously excluding people. So back to what Satya thinks is why can't everyone do this? SatyaSacha thinks is why can't everyone do this? Why are we as programmers having any gate keeping, or you know, "You can't do that you're not a programmer, "you know, I'm a programmer, you can't have that." >> So what does the future look like, >> Rebecca: So what does the future look like, if everyone knows how to do it? I mean, do some imagining, visioning right now about if everyone does know how to do this, or at least can learn the building blocks for it, what does technology look like? >> Well hopefully it will be ethical, and it'll be democratized so that everyone can do it. I think that the things that are interesting, or innovative today will become commoditized tomorrow, like, something as simple as a webcam detecting your face, and putting a square around it and then you move around, and the square, we were like, "Oh my God, that was amazing!" And now it's just a library that you can download. What is amazing and interesting today, like AR and VR, where it's like, "Oh wow, I've never seen augmented reality work like that!" My eight-year-old will be able to do it in five years, and they'll be older than eight. >> So Scott, one of the big takeaways I had from the app dev keynote that you did this morning was in the past it was trying to get everybody on the same page, let's move them to our stack, let's move them to our cloud, let's move them on this programming language, and you really talked about how the example of Chipotle is different parts of the organization will write in a different language, and there needs to be, it's almost, you know, that service bus that you have between all of these environments, because we've spent, a lot of us, I know in my career I've spent decades trying to help break down those silos, and get everybody to work together, but we're never going to have everybody doing the same jobs, so we need to meet them where they are, they need to allow them to use the tools, the languages, the platforms that they want, but they need to all be able to work together, and this is not the Microsoft that I grew up with that is now an enabler of that environment. The word we keep coming back to is trust at the keynote. I know there's some awesome, cool new stuff about .net which is a piece of it, but it's all of the things together. >> Right, you know I was teaching a class at Mesa Community College down in San Diego a couple of days ago and they were trying, they were all people who wanted jobs, just community college people, I went to community college and it's like, I just want to know how to get a job, what is the thing that I can do? What language should I learn? And that's a tough question. They wonder, do I learn Java, do I learn C#? And someone had a really funny analogy, and I'll share it with you. They said, well you know English is the language, right? Why don't the other languages just give up? They said, you know, Finland, they're not going to win, right? Their language didn't win, so they should just give up, and they should all speak English, and I said, What an awful thing! They like their language! I'm not going to go to people who do Haskell, or Rust, or Scala, or F#, and say, you should give up! You're not going to win because C won, or Java won, or C# won. So instead, why don't we focus on standards where we can inter-operate, where we can accept that the reality is a hybrid cloud things like Azure Arc that allows us to connect multiple clouds, multi-vendor clouds together. That is all encompassing the concept of inclusion, including everyone means including every language, and as many standards as you can. So it might sound a little bit like a Tower of Babel, but we do have standards and the standards are HTTP, REST, JSON, JavaScript. It may not be the web we deserve, but it's the web that we have, so we'll use those building block technologies, and then let people do their own thing. >> So speaking of the keynote this morning, one of the cool things you were doing was talking about the rock, paper, scissors game, and how it's expanding. Tell our viewers a little bit more about the new elements to rock, paper, scissors. >> So folks named Sam Kass, a gentleman named Sam Kass many, many years ago on the internet, when the internet was much simpler web pages, created a game called Rock, Paper, Scissors, Lizard, Spock, and a lot of people will know that from a popular TV show on CBS, and they'll give credit to that show, in fact it was Sam Kass and Karen Bryla who created that, and we sent them a note and said, "Hey can I write a game about this?" And we basically built a Rock, Paper, Scissors, Lizard, Spock game in the cloud containerized at scale with multiple languages, and then we also put it on a tiny device, and what's fun about the game from a complexity perspective is that rock, paper, scissors is easy. There's only three rules, right? Paper covers rock, which makes no sense, but when you have five, it's hard! Spock shoots the Rock with his phaser, and then the lizard poisons Spock, and the paper disproves, and it gets really hard and complicated, but it's also super fun and nerdy. So we went and created a containerized app where we had all different bots, we had node, Python, Java, C#, and PHP, and then you can say, I'm going to pick Spock and .net, or node and paper, and have them fight, and then we added in some AI, and some machine learning, and some custom vision such that if you sign in with Twitter in this game, it will learn your patterns, and try to defeat you using your patterns and then, clicking on your choices and fun, snd then, clicking on your choices and fun, because we all want to go, "Rock, Paper, Scissors shoot!" So we made a custom vision model that would go, and detect your hand or whatever that is saying, this is Spock and then it would select it and play the game. So it was just great fun, and it was a lot more fun than a lot of the corporate demos that you see these days. >> All right Scott, you're doing a lot of different things at the show here. We said there's just a barrage of different announcements that were made. Love if you could share some of the things that might have flown under the radar. You know, Arc, everyone's talking about, but some cool things or things that you're geeking out on that you'd want to share with others? >> Two of the things that I'm most excited, one is an announcement that's specific to Ignite, and one's a community thing, the announcement is that .net Core 3.1 is coming. .net Core 3 has been a long time coming as we have began to mature, and create a cross platform open source .net runtime, but .net Core 3.1 LTS Long Term Support means that that's a version of .net core that you can put on a system for three years and be supported. Because a lot of people are saying, "All this open source is moving so fast! "I just upgraded to this, "and I don't want to upgrade to that". LTS releases are going to happen every November in the odd numbered years. So that means 2019, 2021, 2023, there's going to be a version of .net you can count on for three years, and then if you want to follow that train, the safe train, you can do that. In the even numbered years we're going to come out with a version of .net that will push the envelope, maybe introduce a new version of C#, it'll do something interesting and new, then we tighten the screws and then the following year that becomes a long term support version of .net. >> A question for you on that. One of the challenges I hear from customers is, when you talk about hybrid cloud, they're starting to get pulled apart a little bit, because in the public cloud, if I'm running Azure, I'm always on the latest version, but in my data center, often as you said, I want longer term support, I'm not ready to be able to take that CICD push all of the time, so it feels like I live, maybe call it bimodal if you want, but I'm being pulled with the am I always on the latest, getting the latest security, and it's all tested by them? Or am I on my own there? How do you help customers with that, when Microsoft's developing things, how do you live in both of those worlds or pull them together? >> Well, we're really just working on this idea of side-by-side, whether it be different versions of Visual Studio that are side-by-side, the stable one that your company is paying for, and then the preview version that you can go have side-by-side, or whether you could have .net Core 3, 3.1, or the next version, a preview version, and a safe version side-by-side. We want to enable people to experiment without fear of us messing up their machine, which is really, really important. >> One of the other things you were talking about is a cool community announcement. Can you tell us a little bit more about that? >> So this is a really cool product from a very, very small company out of Oregon, from a company called Wilderness Labs, and Wilderness Labs makes a micro-controller, not a micro-processor, not a raspberry pie, it doesn't run Linux, what it runs is .net, so we're actually playing Rock, Paper, Scissors, Lizard, Spock on this device. We've wired it all up, this is a screen from our friends at Adafruit, and I can write .net, so somehow if someone is working at, I don't know, the IT department at Little Debbie Snack Cakes, and they're making WinForms applications, they're suddenly now an IOT developer, 'cause they can go and write C# code, and control a device like this. And when you have a micro-controller, this will run for weeks on a battery, not hours. You go and 3D print a case, make this really tiny, it could become a sensor, it could become an IOT device, or one of thousands of devices that could check crops, check humidity, moisture wetness, whatever you want, and we're going to enable all kinds of things. This is just a commodity device here, this screen, it's not special. The actual device, this is the development version, size of my finger, it could be even smaller if we wanted to make it that way, and these are our friends at Wilderness Labs. and they had a successful Kickstarter, and I just wanted to give them a shout out, and I just wanted to give them a shoutout, I don't have any relationship with them, I just think they're great. >> Very cool, very cool. So you are a busy guy, and as Stu said, you're in a lot of different things within Microsoft, and yet you still have time to teach at community college. I'm interested in your perspective of why you do that? Why do you think it's so important to democratize learning about how to do this stuff? >> I am very fortunate and I think that we people, who have achieved some amount of success in our space, need to recognize that luck played a factor in that. That privilege played a factor in that. But, why can't we be the luck for somebody else, the luck can be as simple as a warm introduction. I believe very strongly in what I call the transitive value of friendship, so if we're friends, and you're friends, then the hypotenuse can be friends as well. A warm intro, a LinkedIn, a note that like, "Hey, I met this person, you should talk to them!" Non-transactional networking is really important. So I can go to a community college, and talk to a person that maybe wanted to quit, and give a speech and give them, I don't know, a week, three months, six months, more whatever, chutzpah, moxie, something that will keep them to finish their degree and then succeed, then I'm going to put good karma out into the world. >> Paying it forward. >> Exactly. >> So Scott, you mentioned that when people ask for advice, it's not about what language they do, is to, you know, is to,q you know, we talk in general about intellectual curiosity of course is good, being part of a community is a great way to participate, and Microsoft has a phenomenal one, any other tips you'd give for our listeners out there today? >> The fundamentals will never go out of style, and rather than thinking about learning how to code, why not think about learning how to think, and learning about systems thinking. One of my friends, Kishau Rogers, talked about systems thinking, I've hade her on my podcast a number of times, and we were giving a presentation at Black Girls Code, and I was talking to a fifteen-year-old young woman, and we were giving a presentation. It was clear that her mom wanted her to be there, and she's like, "Why are we here?" And I said, "All right, let's talk about programming "everybody, we're talking about programming. "My toaster is broken and the toast is not working. "What do you think is wrong?" Big, long, awkward pause and someone says, "Well is the power on?" I was like, "Well, I plugged a light in, "and nothing came on" and they were like, "Well is the fuse blown?" and then one little girl said "Well did the neighbors have power?", And I said, "You're debugging, we are debugging right?" This is the thing, you're a systems thinker, I don't know what's going on with the computer when my dad calls, I'm just figuring it out like, "Oh, I'm so happy, you work for Microsoft, "you're able to figure it out." >> Rebecca: He has his own IT guy now in you! >> Yeah, I don't know, I unplug the router, right? But that ability to think about things in the context of a larger system. I want toast, power is out in the neighborhood, drawing that line, that makes you a programmer, the language is secondary. >> Finally, the YouTube videos. Tell our viewers a little bit about those. you can go to D-O-T.net, so dot.net, the word dot, you can go to d-o-t.net, so dot.net, the word dot, slash videos and we went, and we made a 100 YouTube videos on everything from C# 101, .net, all the way up to database access, and putting things in the cloud. A very gentle, "Mr. Rodgers' Neighborhood" on-ramp. A lot of things, if you've ever seen that cartoon that says, "Want to draw an owl? "Well draw two circles, "and then draw the rest of the fricking owl." A lot of tutorials feel like that, and we don't want to do that, you know. We've got to have an on-ramp before we get on the freeway. So we've made those at dot.net/videos. >> Excellent, well that's a great plug! Thank you so much for coming on the show, Scott. >> Absolutely my pleasure! >> I'm Rebecca Knight, for Stu Miniman., stay tuned for more of theCUBE's live coverage of Microsoft Ignite. (upbeat music)

>> Announcer: Live from Orlando Florida, it's theCUBE, covering Microsoft Ignite. Brought to you by Cohesity. >> Good morning everyone. You are watching theCUBE's live coverage of Microsoft Ignite 2019 here in Orlando, Florida. I'm your host Rebecca Knight, co-hosting alongside of Stu Miniman. We are joined by Donovan Brown. He is the Principal Cloud Advocate Manager of Methods and Practices Organizations at Microsoft. (laughing) A mouthful of a title. >> Yes. >> Rebecca: We are thrilled to welcome you on. >> Thank you so much. >> You are the man in the black shirt. >> I have been dubbed the man in the black shirt. >> So tell us what that's all about. You're absolutely famous. Whenever we were saying Donovan Brown's going to be here. "The man in the black shirt?" >> Yes. >> So what's that about? >> So it was interesting. The first time I ever got to keynote in an event was in New York in 2015 for Scott Guthrie, the guy who only wears a red shirt. And I remember, I was literally, and this is no exaggeration, wearing this exact black shirt, right, because I bring it with me and I can tell because the tag in the back is worn more than the other black shirts I have just like this one. And I bring this one out for big events because I was in a keynote yesterday and I knew I was going to be on your show today. And I wore it and it looked good on camera. I felt really good. I'm an ex-athlete. We're very superstitious. I'm like I have to wear that shirt in every keynote that I do from now on because if you look further back, you'll see me in blue shirts and all other colored shirts. But from that day forward, it's going to be hard pressed for you to find me on camera on stage without this black shirt on or a black shirt of some type. And there's a really cool story about the black shirt that was. This is what\ I knew it was a thing. So I pack about six or seven black shirts in every luggage. I'm flying overseas to Germany to go Kampf to do a keynote for, I think it was Azure Saturday. Flights were really messed up. they had to check my bag which makes me very uncomfortable because they lose stuff. I'm not too worried about it, it'll be okay. Check my bag, get to Europe. They've been advertising that the black shirt is coming for months and they lose my luggage. And I am now, heart's pounding out of my chest. (laughing) We go to the airport. I'm shopping in the airport because I don't even have luggage. I cannot find a black shirt and I am just thinking this is devastating. How am I going to go to a conference who's been promoting "the black shirt's coming" not wearing a black shirt? And my luggage does not show up. I show up at the event I'm thinking okay, maybe I'll get lucky and the actual conference shirt will be black and then we're all good. I walk in and all I see are white shirts. I'm like this could not be worse. And then now the speakers show up. They're wearing blue shirts, I'm like this cannot be happening. So I'm depressed, I'm walking to the back and everyone's starts saying, "Donovan's here, Donovan's here." And I'm looking to find my polo, my blue polo I'm going to put on. They're like no, no, no, no Donovan. They printed one black shirt just for me. I was like oh my goodness, this is so awesome. So I put the black shirt on, then I put a jacket on over it and I go out and I tell the story of how hard it was to get here, that they lost my luggage, I'm not myself without a black shirt. But this team had my back. And when I unzipped my shirt, the whole place just starts clapping 'cause I'm wearing >> Oh, I love it. >> a black shirt. >> Exactly. So now to be seen without a black shirt is weird. Jessica Dean works for me. We were in Singapore together and it was an off day. So I just wore a normal shirt. She had to take a double take, "Oh no, is that Donovan, my manager "'cause he's not wearing a black shirt?" I don't wear them all the time but if I'm on camera, on stage you're going to see me in a black shirt. >> Rebecca: All right, I like it. >> Well, Donovan, great story. Your team, Methods and Practices makes up a broad spectrum of activities and was relatively recently rebranded. >> Yeah. >> We've talked to some of your team members on theCUBE before, so tell our audience a little bit about the bridges Microsoft's building to help the people. >> Great. No, so that's been great. Originally, I built a team called The League. Right, there's a really small group of just DevOps focused diehards. And we still exist. A matter of fact, we're doing a meet and greet tonight at 4:30 where you can come and meet all five of the original League members. Eventually, I got tasked with a much bigger team. I tell the story. I was in Norway, I went to sleep, I had four direct reports. I literally woke up and I had 20 people reporting to me and I'm like what just happened? And the team's spanned out a lot more than just DevOps. So having it branded as the DevOps Guy doesn't really yield very well for people who aren't diehard DevOps people. And what we feared was, "Donovan there's people who are afraid of DevOps "who now report to you." You can't be that DevOps guy anymore. You have to broaden what you do so that you can actually focus on the IT pros in the world, the modern operations people, the lift and shift with Jeremy, with what Jeramiah's doing for me right, with the lift and shift of workloads . And you still have to own DevOps. So what I did is I pulled back, reduced my direct reports to four and now I have teams underneath me. Abel Wang now runs DevOps. He's going to be the new DevOps guy for me. Jeramiah runs our lift and shift. Rick Klaus or you know the Hat, he runs all my IT Pro and then Emily who's just an amazing speaker for us, runs all of my modern operations. So we span those four big areas right. Modern operations which is sort of like the ops side of DevOps, IT pros which are the low level infrastructure, diehard Windows server admins and then we have DevOps run by Abel which is still, the majority of The League is over there. And then we have obviously the IT pros, modern ops, DevOps and then the left and shift with Jeramiah. >> I'd like to speak a little bit as to why you've got these different groups? How do you share information across the teams but you know really meet customers where they are and help them along 'cause my background's infrastructure. >> Donovan: Sure. >> And that DevOps, was like that religion pounding at you, that absolutely, I mean, I've got a closet full of hoodies but I'm not a developer. Understand? >> Understood. (laughs) It's interesting because when you look at where our customers are today, getting into the cloud is not something you do overnight. It takes lots of steps. You might start with a lift and shift, right? You might start with just adding some Azure in a hybrid scenario to your on-prem scenario. So my IT pros are looking after that group of people that they're still on prem majority, they're trying to dip those toes into the cloud. They want to start using things like file shares or backups or something that they can have, disaster recovery offsite while they're still running the majority of what they're doing on-prem. So there's always an Azure pool to all four of the teams that I actually run. But I need them to take care of where our customers are today and it's not just force them to be where we want them tomorrow and they're not ready to go there. So it's kind of interesting that my team's kind of have every one of those stages of migration from I'm on-prem, do I need to lift and shift do I need to do modern operations, do I need to be doing full-blown DevOps pull all up? So, I think it's a nice group of people that kind of fit the spectrum of where our customers are going to be taking that journey from where they are to enter the cloud. So I love it. >> One of the things you said was getting to the cloud doesn't happen overnight. >> No, it does not. >> Well, you can say that again because there is still a lot of skepticism and reluctance and nervousness. How do you, we talked so much about this digital transformation and technology is not the hard part. It's the people that pose the biggest challenges to actually making it happen. >> Donovan: Right. >> So we're talking about meeting customers where they are in terms of the tools they need. But where do you meet them in terms of where they are just in their approach and their mindset, in terms of their cloud readiness? >> You listen. Believe it or not, you can't just go and tell people something. You need to listen to them, find out what hurts and then start with that one thing is what I tell people. Focus on what hurts the most first. Don't do a big bang change of any type. I think that's a recipe for disaster. There's too many variables that could go wrong. But when I sit down with a customer is like tell me where you are, tell me what hurts, like what are you afraid of? Is it a compliancies? Let me go get you in contact with someone who can tell you about all the comp. We have over 90 certifications on Azure. Let me. whatever your fear is, I bet you I can get you in touch with someone that's going to help you get past that fear. But I don't say just lift, shift, move it all like stop wasting, like no. Let's focus on that one thing. And what you're going to do is you're going to start to build confidence and trust with that customer. And they know that I'm not there just trying to rip and replace you and get out high levels of ACR. I'm trying to succeed with you, right, empower every person in every organization on the planet to achieve more. You do that by teaching them first, by helping them first. You can sell them last, right? You shouldn't have to sell them at all once they trust that what we we're trying to do together is partner with you. I look at every customer more as a partner than a customer, like how can I come with you and we do better things together than either one of us could have done apart. >> You're a cloud psychologist? Almost, right because I always put myself in their position. If I was a customer, what would I want that vendor to do for me? How would they make me feel comfortable and that's the way that I lead. Right, I don't want you going in there selling anything right. We're here to educate them and if we're doing our job on the product side, the answer is going to be obvious that you need to be coming with us to Azure. >> All right. So Donovan, you mentioned you used to be an athlete? >> Donovan: Yes. >> According to your bio, you're still a bit of an athlete. >> Donovan: A little bit, a little bit. >> So there's the professional air hockey thing which has a tie to something going on with the field. Give us a little bit of background. I've got an air hockey table in my basement. Any tips for those of us that aren't, you know? You were ranked 11th in the world. >> At one point, yeah, though I went to the World Championships. It was interesting because that World Championships I wasn't prepared. My wife plays as well. We were like we're just going to go, we're going to support the tournament. We had no expectations whatsoever. Next thing you know, I'm in the round playing for the top 10 in the world. And that's when it got too serious for me and I lost, because I started taking it too serious. I put too much pressure on myself. But professionally, air hockey's like professional foosball or pool. It's grown men taking this sport way too seriously. It's the way I'd describe it. It is not what you see at Chuck E. Cheese. And what was interesting is Damien Brady who works for me found that there is an AI operated air hockey table here on this floor. And my wife was like, oh my gosh, we have to find this machine. Someone tape Donovan playing it. Six seconds later, my first shot I scored it. And I just looked at the poor people who built it and I'm like yeah, I'm a professional air hockey player. This thing is so not ready for professional time but they took down all my information and said we'd love to consult with you. I said I'd love to consult with you too because this could be a lot of fun. Maybe also a great way for professionals to practice, right, because you don't always have someone who's willing to play hours and hours which it takes to get at the professional level. But to have an AI system that I could even teach up my attack, forcing me to play outside of my comfort zone, to try something other than a left wall under or right well over but have to do more cuts because it knows to search for that. I can see a lot of great applications for the professionalized player with this type of AI. It would actually get a lot better. Literally, someone behind me started laughing. "That didn't take long" because it in six seconds I had scored on it already. I'm like okay, I was hoping it was going to be harder than this. >> I'm thinking back to our Dave Cahill interview of AI for everyone, and this is AI for professional air hockey players. >> It is and in one of my demos, Kendra Havens showed AI inside of your IDE. And I remember I tell the story that I remember I started writing software back in the 90s. I remember driving to a software store. You remember we used to have to drive and you'd buy a box and the box would be really heavy because the manuals are in there, and not to mention a stack of floppy discs that you're going to spend hours putting in your computer. And I bought visual C++ 1.52 was my first compiler. I remember going home so excited. And it had like syntax highlighting and that was like this cool new thing and you had all these great breakpoints and line numbers. And now Kendra's on stage typing this repetitives task and then the editor stops her and says, "It looks like you need to do this a little bit more. "You want me to do this for you?" And I'm like what just happened? This is not syntax highlighting. This is literally watching what you do, identifying a repetitive task, seeing the pattern in your code and suggesting that I can finish writing this code for you. It's unbelievable. >> You bring up a great point. Back when I used to write, it was programming. >> Yes. >> And we said programming was you learn the structure, you learn the logic and you write all the lines of what's going to be there. Coding on the other hand usually is taking something that is there, pulling in the pieces, making the modification. >> Right. >> It sounds like we're talking about even the next generation where the intelligence is going to take over. >> It's built right inside of your IDE which is amazing. You were talking about artificial intelligence, not only for the air hockey. But I love the fact that in Azure, we have so many cognitive services and you just like pick these off the shelf. When I wanted to learn artificial intelligence when I was in the university, you had to go for another language called Lisp. That scared half of us away from artificial intelligence because you have to learn another language just to go do this cool thing that back then was very difficult to do and you could barely get it to play chess, let alone play air hockey. But today, cognitive services search, decision-making, chat bots, they're so easy. Anyone, even a non developer, can start adding the power of AI into their products thanks to the stuff that we're doing in Azure. And this is just lighting up all these new possibilities for us, air hockey, drones that are able to put out fires. I've just seen amazing stuff where they're able to use AI and they add it with as little as two lines of code. And all of a sudden, your app is so much more powerful than it was before. >> Donovan, one of the things that really struck me over the last couple years, looking at Microsoft, is it used to be, you'd think about the Microsoft stack. When I think about developers it's like, oh wait are you a .NET person? Well, you're going to be there. The keynote this morning, one of your team members was on stage with Scott Hanselman and was you know choose your language, choose your tools and you're going to have all of them out there. So talk to us a little bit about that transition inside Microsoft. >> Sure. One of the mantras that I've been saying for a while is "any language, any platform". No one believes me . So I had to start proving it. I'm like so I got on stage one year. It was interesting and this is a really rough year because I flew with three laptops. One had Mac OS on it, one of them had Linux on it and one of them had Windows. And what I did is I created a voting app and what I would do is I'd get on stage and say okay everyone that's in this session, go to this URL and start voting. They got to pick what computer I use, they got to pick what language I programmed in and they got to pick where in Azure-eyed I deployed it to. Was it to an app service was it to Docker? I'm like I'm going to prove to you I can do any language in any platform. So I honestly did not know what demo I was going to do. 20 minutes later, after showing them some slides, I would go back to the app and say what did you pick? And I would move that computer in front of me and right there on stage completely create a complete CI/CD pipeline for the language that that audience chose to whatever resources that they wanted on whatever platform that they wanted me. Was like, have I proven this to you enough or not? And I did that demo for an entire year. Any language that you want me to program in and any platform you want me to target, I'm going to do that right now and I don't even know what it's going to be. You're going to choose it for me. I can't remember the last time I did a .NET demo on stage. I did Python this week when I was on stage with Jason Zander. I saw a lot of Python and Go and other demos this year. We love .NET. Don't get us wrong but everyone knows we can .NET. What we're trying to prove right now is that we can do a lot of other things. It does not matter what language you program in. It does not matter where you want to deploy. Microsoft is here to help you. It's a company created by developers and we're still obsessed with developers, not just .NET developers, all developers even the citizen developer which is a developer which is a developer who doesn't have to see the code anymore but wants to be able to add that value to what they're doing in their organization. So if you're a developer, Microsoft is here to help full-stop. It's a powerful mission and a powerful message that you are really empowering everyone here. >> Donovan: Right. >> Excellent. >> And how many developers only program in one language now, right? I thought I remember I used to be a C++ programmer and I thought that was it, right. I knew the best language, I knew the fastest language. And then all of a sudden, I knew CSharp and I knew Java and I knew JavaScript and I brought a lot of PowerShell right now and I write it on and noticed like wow, no one knows one language. But I never leave Visual Studio code. I deploy all my workloads into Azure. I didn't have to change my infrastructure or my tools to switch languages. I just switched languages that fit whatever the problem was that I was trying to solve. So I live the mantra that we tell our customers. I don't just do .NET development. Although I love .NET and it's my go-to language if I'm starting from scratch but sometimes I'm going to go help in an open source project that's written in some other language and I want to be able to help them. With Visual Studio online, we made that extremely easy. I don't even have to set up my development machine anymore. I can only click a link in a GitHub repository and the environment I need will be provisioned for me. I'll use it, check in my commits and then throw it away when I'm done. It's the world of being a developer now and I always giggle 'cause I'm thinking I had to drive to a store and buy my first compiler and now I can have an entire environment in minutes that is ready to rock and roll. It's just I wish I would learn how to program now and not when I was on bulletin boards asking for help and waiting three days for someone to respond. I didn't have Stack Overflow or search engines and things like that. It's just an amazing time to be a developer. >> Yes, indeed. Indeed it is Donovan Brown, the man in the black shirt. Thank you so much for coming on theCUBE. >> My pleasure. Thank you for having me. >> It was really fun. Thank you. >> Take care. >> I'm Rebecca Knight for Stu Miniman. Stay tuned for more of theCUBE's live coverage of Microsoft Ignite. (upbeat music)

[Music] [Music] [Music] [Laughter] [Laughter] [Laughter] [Laughter] [Music] [Music] [Music] [Music] you you [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Applause] [Music] wake up feeling blessed peace you warned that Russia ain't afraid to show it I'll expose it if I dressed up riding in that Chester roasted nigga catch you slippin on myself rocks on I messed up like yes sir [Music] [Music] [Music] [Music] our program [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] you are not welcome to Red Hat summit 2018 2018 [Music] [Music] [Music] [Laughter] [Music] Wow that is truly the coolest introduction I've ever had thank you Wow I don't think I feel cool enough to follow an interaction like that Wow well welcome to the Red Hat summit this is our 14th annual event and I have to say looking out over this audience Wow it's great to see so many people here joining us this is by far our largest summit to date not only did we blow through the numbers we've had in the past we blew through our own expectations this year so I know we have a pretty packed house and I know people are still coming in so it's great to see so many people here it's great to see so many familiar faces when I had a chance to walk around earlier it's great to see so many new people here joining us for the first time I think the record attendance is an indication that more and more enterprises around the world are seeing the power of open source to help them with their challenges that they're facing due to the digital transformation that all of enterprises around the world are going through the theme for the summit this year is ideas worth exploring and we intentionally chose that because as much as we are all going through this digital disruption and the challenges associated with it one thing I think is becoming clear no one person and certainly no one company has the answers to these challenges right this isn't a problem where you can go buy a solution this is a set of capabilities that we all need to build it's a set of cultural changes that we all need to go through and that's going to require the best ideas coming from so many different places so we're not here saying we have the answers we're trying to convene the conversation right we want to serve as a catalyst bringing great minds together to share ideas so we all walk out of here at the end of the week a little wiser than when we first came here we do have an amazing agenda for you we have over 7,000 attendees we may be pushing 8,000 by the time we got through this morning we have 36 keynote speakers and we have a hundred and twenty-five breakout sessions and have to throw in one plug scheduling 325 breakout sessions is actually pretty difficult and so we used the Red Hat business optimizer which is an AI constraint solver that's new in the Red Hat decision manager to help us plan the summit because we have individuals who have a clustered set of interests and we want to make sure that when we schedule two breakout sessions we do it in a way that we don't have overlapping sessions that are really important to the same individual so we tried to use this tool and what we understand about people's interest in history of what they wanted to do to try to make sure that we spaced out different times for things of similar interests for similar people as well as for people who stood in the back of breakouts before and I know I've done that too we've also used it to try to optimize room size so hopefully we will do our best to make sure that we've appropriately sized the spaces for those as well so it's really a phenomenal tool and I know it's helped us a lot this year in addition to the 325 breakouts we have a lot of our customers on stage during the main sessions and so you'll see demos you'll hear from partners you'll hear stories from so many of our customers not on our point of view of how to use these technologies but their point of views of how they actually are using these technologies to solve their problems and you'll hear over and over again from those keynotes that it's not just about the technology it's about how people are changing how people are working to innovate to solve those problems and while we're on the subject of people I'd like to take a moment to recognize the Red Hat certified professional of the year this is known award we do every year I love this award because it truly recognizes an individual for outstanding innovation for outstanding ideas for truly standing out in how they're able to help their organization with Red Hat technologies Red Hat certifications help system administrators application developers IT architects to further their careers and help their organizations by being able to advance their skills and knowledge of Red Hat products and this year's winner really truly is a great example about how their curiosity is helped push the limits of what's possible with technology let's hear a little more about this year's winner when I was studying at the University I had computer science as one of my subjects and that's what created the passion from the very beginning they were quite a few institutions around my University who were offering Red Hat Enterprise Linux as a course and a certification paths through to become an administrator Red Hat Learning subscription has offered me a lot more than any other trainings that have done so far that gave me exposure to so many products under red hair technologies that I wasn't even aware of I started to think about the better ways of how these learnings can be put into the real life use cases and we started off with a discussion with my manager saying I have to try this product and I really want to see how it really fits in our environment and that product was Red Hat virtualization we went from deploying rave and then OpenStack and then the open shift environment we wanted to overcome some of the things that we saw as challenges to the speed and rapidity of release and code etc so it made perfect sense and we were able to do it in a really short space of time so you know we truly did use it as an Innovation Lab I think idea is everything ideas can change the way you see things an Innovation Lab was such an idea that popped into my mind one fine day and it has transformed the way we think as a team and it's given that playpen to pretty much everyone to go and test their things investigate evaluate do whatever they like in a non-critical non production environment I recruited Neha almost 10 years ago now I could see there was a spark a potential with it and you know she had a real Drive a real passion and you know here we are nearly ten years later I'm Neha Sandow I am a Red Hat certified engineer all right well everyone please walk into the states to the stage Neha [Music] [Applause] congratulations thank you [Applause] I think that - well welcome to the red has some of this is your first summit yes it is thanks so much well fantastic sure well it's great to have you here I hope you have a chance to engage and share some of your ideas and enjoy the week thank you thank you congratulations [Applause] neha mentioned that she first got interest in open source at university and it made me think red hats recently started our Red Hat Academy program that looks to programmatically infuse Red Hat technologies in universities around the world it's exploded in a way we had no idea it's grown just incredibly rapidly which i think shows the interest that there really is an open source and working in an open way at university so it's really a phenomenal program I'm also excited to announce that we're launching our newest open source story this year at Summit it's called the science of collective discovery and it looks at what happens when communities use open hardware to monitor the environment around them and really how they can make impactful change based on that technologies the rural premier that will be at 5:15 on Wednesday at McMaster Oni West and so please join us for a drink and we'll also have a number of the experts featured in that and you can have a conversation with them as well so with that let's officially start the show please welcome red hat president of products and technology Paul Cormier [Music] Wow morning you know I say it every year I'm gonna say it again I know I repeat myself it's just amazing we are so proud here to be here today too while you all week on how far we've come with opens with open source and with the products that we that we provide at Red Hat so so welcome and I hope the pride shows through so you know I told you Seven Summits ago on this stage that the future would be open and here we are just seven years later this is the 14th summit but just seven years later after that and much has happened and I think you'll see today and this week that that prediction that the world would be open was a pretty safe predict prediction but I want to take you just back a little bit to see how we started here and it's not just how Red Hat started here this is an open source in Linux based computing is now in an industry norm and I think that's what you'll you'll see in here this week you know we talked back then seven years ago when we put on our prediction about the UNIX error and how Hardware innovation with x86 was it was really the first step in a new era of open innovation you know companies like Sun Deck IBM and HP they really changed the world the computing industry with their UNIX models it was that was really the rise of computing but I think what we we really saw then was that single company innovation could only scale so far could really get so far with that these companies were very very innovative but they coupled hardware innovation with software innovation and as one company they could only solve so many problems and even which comp which even complicated things more they could only hire so many people in each of their companies Intel came on the scene back then as the new independent hardware player and you know that was really the beginning of the drive for horizontal computing power and computing this opened up a brand new vehicle for hardware innovation a new hardware ecosystem was built around this around this common hardware base shortly after that Stallman and leanness they had a vision of his of an open model that was created and they created Linux but it was built around Intel this was really the beginning of having a software based platform that could also drive innovation this kind of was the beginning of the changing of the world here that system-level innovation now having a hardware platform that was ubiquitous and a software platform that was open and ubiquitous it really changed this system level innovation and that continues to thrive today it was only possible because it was open this could not have happened in a closed environment it allowed the best ideas from anywhere from all over to come in in win only because it was the best idea that's what drove the rate of innovation at the pace you're seeing today and it which has never been seen before we at Red Hat we saw the need to bring this innovation to solve real-world problems in the enterprise and I think that's going to be the theme of the show today you're going to see us with our customers and partners talking about and showing you some of those real-world problems that we are sought solving with this open innovation we created rel back then for this for the enterprise it started it's it it wasn't successful because it's scaled it was secure and it was enterprise ready it once again changed the industry but this time through open innovation this gave the hardware ecosystem a software platform this open software platform gave the hardware ecosystem a software platform to build around it Unleashed them the hardware side to compete and thrive it enabled innovation from the OEMs new players building cheaper faster servers even new architectures from armed to power sprung up with this change we have seen an incredible amount of hardware innovation over the last 15 years that same innovation happened on the software side we saw powerful implementations of bare metal Linux distributions out in the market in fact at one point there were 300 there are over 300 distributions out in the market on the foundation of Linux powerful open-source equivalents were even developed in every area of Technology databases middleware messaging containers anything you could imagine innovation just exploded around the Linux platform in innovation it's at the core also drove virtualization both Linux and virtualization led to another area of innovation which you're hearing a lot about now public cloud innovation this innovation started to proceed at a rate that we had never seen before we had never experienced this in the past in this unprecedented speed of innovation and software was now possible because you didn't need a chip foundry in order to innovate you just needed great ideas in the open platform that was out there customers seeing this innovation in the public cloud sparked it sparked their desire to build their own linux based cloud platforms and customers are now are now bringing that cloud efficiency on-premise in their own data centers public clouds demonstrated so much efficiency the data centers and architects wanted to take advantage of it off premise on premise I'm sorry within their own we don't within their own controlled environments this really allowed companies to make the most of existing investments from data centers to hardware they also gained many new advantages from data sovereignty to new flexible agile approaches I want to bring Burr and his team up here to take a look at what building out an on-premise cloud can look like today Bure take it away I am super excited to be with all of you here at Red Hat summit I know we have some amazing things to show you throughout the week but before we dive into this demonstration I want you to take just a few seconds just a quick moment to think about that really important event your life that moment you turned on your first computer maybe it was a trs-80 listen Claire and Atari I even had an 83 b2 at one point but in my specific case I was sitting in a classroom in Hawaii and I could see all the way from Diamond Head to Pearl Harbor so just keep that in mind and I turn on an IBM PC with dual floppies I don't remember issuing my first commands writing my first level of code and I was totally hooked it was like a magical moment and I've been hooked on computers for the last 30 years so I want you to hold that image in your mind for just a moment just a second while we show you the computers we have here on stage let me turn this over to Jay fair and Dini here's our worldwide DevOps manager and he was going to show us his hardware what do you got Jay thank you BER good morning everyone and welcome to Red Hat summit we have so many cool things to show you this week I am so happy to be here and you know my favorite thing about red hat summit is our allowed to kind of share all of our stories much like bird just did we also love to you know talk about the hardware and the technology that we brought with us in fact it's become a bit of a competition so this year we said you know let's win this thing and we actually I think we might have won we brought a cloud with us so right now this is a private cloud for throughout the course of the week we're going to turn this into a very very interesting open hybrid cloud right before your eyes so everything you see here will be real and happening right on this thing right behind me here so thanks for our four incredible partners IBM Dell HP and super micro we've built a very vendor heterogeneous cloud here extra special thanks to IBM because they loaned us a power nine machine so now we actually have multiple architectures in this cloud so as you know one of the greatest benefits to running Red Hat technology is that we run on just about everything and you know I can't stress enough how powerful that is how cost-effective that is and it just makes my life easier to be honest so if you're interested the people that built this actual rack right here gonna be hanging out in the customer success zone this whole week it's on the second floor the lobby there and they'd be glad to show you exactly how they built this thing so let me show you what we actually have in this rack so contained in this rack we have 1056 physical chorus right here we have five and a half terabytes of RAM and just in case we threw 50 terabytes of storage in this thing so burr that's about two million times more powerful than that first machine you boot it up thanks to a PC we're actually capable of putting all the power needs and cooling right in this rack so there's your data center right there you know it occurred to me last night that I can actually pull the power cord on this thing and kick it up a notch we could have the world's first mobile portable hybrid cloud so I'm gonna go ahead and unplug no no no no no seriously it's not unplug the thing we got it working now well Berg gets a little nervous but next year we're rolling this thing around okay okay so to recap multiple vendors check multiple architectures check multiple public clouds plug right into this thing check and everything everywhere is running the same software from Red Hat so that is a giant check so burn Angus why don't we get the demos rolling awesome so we have totally we have some amazing hardware amazing computers on this stage but now we need to light it up and we have Angus Thomas who represents our OpenStack engineering team and he's going to show us what we can do with this awesome hardware Angus thank you Beth so this was an impressive rack of hardware to Joe has bought a pocket stage what I want to talk about today is putting it to work with OpenStack platform director we're going to turn it from a lot of potential into a flexible scalable private cloud we've been using director for a while now to take care of managing hardware and orchestrating the deployment of OpenStack what's new is that we're bringing the same capabilities for on-premise manager the deployment of OpenShift director deploying OpenShift in this way is the best of both worlds it's bare-metal performance but with an underlying infrastructure as a service that can take care of deploying in new instances and scaling out and a lot of the things that we expect from a cloud provider director is running on a virtual machine on Red Hat virtualization at the top of the rack and it's going to bring everything else under control what you can see on the screen right now is the director UI and as you see some of the hardware in the rack is already being managed at the top level we have information about the number of cores in the amount of RAM and the disks that each machine have if we dig in a bit there's information about MAC addresses and IPs and the management interface the BIOS kernel version dig a little deeper and there is information about the hard disks all of this is important because we want to be able to make sure that we put in workloads exactly where we want them Jay could you please power on the two new machines at the top of the rack sure all right thank you so when those two machines come up on the network director is going to see them see that they're new and not already under management and is it immediately going to go into the hardware inspection that populates this database and gets them ready for use so we also have profiles as you can see here profiles are the way that we match the hardware in a machine to the kind of workload that it's suited to this is how we make sure that machines that have all the discs run Seth and machines that have all the RAM when our application workouts for example there's two ways these can be set when you're dealing with a rack like this you could go in an individually tag each machine but director scales up to data centers so we have a rules matching engine which will automatically take the hardware profile of a new machine and make sure it gets tagged in exactly the right way so we can automatically discover new machines on the network and we can automatically match them to a profile that's how we streamline and scale up operations now I want to talk about deploying the software we have a set of validations we've learned over time about the Miss configurations in the underlying infrastructure which can cause the deployment of a multi node distributed application like OpenStack or OpenShift to fail if you have the wrong VLAN tags on a switch port or DHCP isn't running where it should be for example you can get into a situation which is really hard to debug a lot of our validations actually run before the deployment they look at what you're intending to deploy and they check in the environment is the way that it should be and they'll preempts problems and obviously preemption is a lot better than debugging something new that you probably have not seen before is director managing multiple deployments of different things side by side before we came out on stage we also deployed OpenStack on this rack just to keep me honest let me jump over to OpenStack very quickly a lot of our opens that customers will be familiar with this UI and the bare metal deployment of OpenStack on our rack is actually running a set of virtual machines which is running Gluster you're going to see that put to work later on during the summit Jay's gone to an awful lot effort to get this Hardware up on the stage so we're going to use it as many different ways as we can okay let's deploy OpenShift if I switch over to the deployed a deployment plan view there's a few steps first thing you need to do is make sure we have the hardware I already talked about how director manages hardware it's smart enough to make sure that it's not going to attempt to deploy into machines they're already in use it's only going to deploy on machines that have the right profile but I think with the rack that we have here we've got enough next thing is the deployment configuration this is where you get to customize exactly what's going to be deployed to make sure that it really matches your environment if they're external IPs for additional services you can set them here whatever it takes to make sure that the deployment is going to work for you as you can see on the screen we have a set of options around enable TLS for encryption network traffic if I dig a little deeper there are options around enabling ipv6 and network isolation so that different classes of traffic there are over different physical NICs okay then then we have roles now roles this is essentially about the software that's going to be put on each machine director comes with a set of roles for a lot of the software that RedHat supports and you can just use those or you can modify them a little bit if you need to add a monitoring agent or whatever it might be or you can create your own custom roles director has quite a rich syntax for custom role definition and custom Network topologies whatever it is you need in order to make it work in your environment so the rawls that we have right now are going to give us a working instance of openshift if I go ahead and click through the validations are all looking green so right now I can click the button start to the deploy and you will see things lighting up on the rack directors going to use IPMI to reboot the machines provisioned and with a trail image was the containers on them and start up the application stack okay so one last thing once the deployment is done you're going to want to keep director around director has a lot of capabilities around what we call de to operational management bringing in new Hardware scaling out deployments dealing with updates and critically doing upgrades as well so having said all of that it is time for me to switch over to an instance of openshift deployed by a director running on bare metal on our rack and I need to hand this over to our developer team so they can show what they can do it thank you that is so awesome Angus so what you've seen now is going from bare metal to the ultimate private cloud with OpenStack director make an open shift ready for our developers to build their next generation applications thank you so much guys that was totally awesome I love what you guys showed there now I have the honor now I have the honor of introducing a very special guest one of our earliest OpenShift customers who understands the necessity of the private cloud inside their organization and more importantly they're fundamentally redefining their industry please extend a warm welcome to deep mar Foster from Amadeus well good morning everyone a big thank you for having armadillos here and myself so as it was just set I'm at Mario's well first of all we are a large IT provider in the travel industry so serving essentially Airlines hotel chains this distributors like Expedia and others we indeed we started very early what was OpenShift like a bit more than three years ago and we jumped on it when when Retta teamed with Google to bring in kubernetes into this so let me quickly share a few figures about our Mario's to give you like a sense of what we are doing and the scale of our operations so some of our key KPIs one of our key metrics is what what we call passenger borders so that's the number of customers that physically board a plane over the year so through our systems it's roughly 1.6 billion people checking in taking the aircrafts on under the Amarillo systems close to 600 million travel agency bookings virtually all airlines are on the system and one figure I want to stress out a little bit is this one trillion availability requests per day that's when I read this figure my mind boggles a little bit so this means in continuous throughput more than 10 million hits per second so of course these are not traditional database transactions it's it's it's highly cached in memory and these applications are running over like more than 100,000 course so it's it's it's really big stuff so today I want to give some concrete feedback what we are doing so I have chosen two applications products of our Mario's that are currently running on production in different in different hosting environments as the theme here is of this talk hybrid cloud and so I want to give some some concrete feedback of how we architect the applications and of course it stays relatively high level so here I have taken one of our applications that is used in the hospitality environment so it's we have built this for a very large US hotel chain and it's currently in in full swing brought into production so like 30 percent of the globe or 5,000 plus hotels are on this platform not so here you can see that we use as the path of course on openshift on that's that's the most central piece of our hybrid cloud strategy on the database side we use Oracle and Couchbase Couchbase is used for the heavy duty fast access more key value store but also to replicate data across two data centers in this case it's running over to US based data centers east and west coast topology that are fit so run by Mario's that are fit with VMware on for the virtualization OpenStack on top of it and then open shift to host and welcome the applications on the right hand side you you see the kind of tools if you want to call them tools that we use these are the principal ones of course the real picture is much more complex but in essence we use terraform to map to the api's of the underlying infrastructure so they are obviously there are differences when you run on OpenStack or the Google compute engine or AWS Azure so some some tweaking is needed we use right at ansible a lot we also use puppet so you can see these are really the big the big pieces of of this sense installation and if we look to the to the topology again very high high level so these two locations basically map the data centers of our customers so they are in close proximity because the response time and the SLA is of this application is are very tight so that's an example of an application that is architectures mostly was high ability and high availability in minds not necessarily full global worldwide scaling but of course it could be scaled but here the idea is that we can swing from one data center to the unit to the other in matters of of minutes both take traffic data is fully synchronized across those data centers and while the switch back and forth is very fast the second example I have taken is what we call the shopping box this is when people go to kayak or Expedia and they're getting inspired where they want to travel to this is really the piece that shoots most of transit of the transactions into our Mario's so we architect here more for high scalability of course availability is also a key but here scaling and geographical spread is very important so in short it runs partially on-premise in our Amarillo Stata Center again on OpenStack and we we deploy it mostly in the first step on the Google compute engine and currently as we speak on Amazon on AWS and we work also together with Retta to qualify the whole show on Microsoft Azure here in this application it's it's the same building blocks there is a large swimming aspect to it so we bring Kafka into this working with records and another partner to bring Kafka on their open shift because at the end we want to use open shift to administrate the whole show so over time also databases and the topology here when you look to the physical deployment topology while it's very classical we use the the regions and the availability zone concept so this application is spread over three principal continental regions and so it's again it's a high-level view with different availability zones and in each of those availability zones we take a hit of several 10,000 transactions so that was it really in very short just to give you a glimpse on how we implement hybrid clouds I think that's the way forward it gives us a lot of freedom and it allows us to to discuss in a much more educated way with our customers that sometimes have already deals in place with one cloud provider or another so for us it's a lot of value to set two to leave them the choice basically what up that was a very quick overview of what we are doing we were together with records are based on open shift essentially here and more and more OpenStack coming into the picture hope you found this interesting thanks a lot and have a nice summer [Applause] thank you so much deeper great great solution we've worked with deep Marv and his team for a long for a long time great solution so I want to take us back a little bit I want to circle back I sort of ended talking a little bit about the public cloud so let's circle back there you know even so even though some applications need to run in various footprints on premise there's still great gains to be had that for running certain applications in the public cloud a public cloud will be as impactful to to the industry as as UNIX era was of computing was but by itself it'll have some of the same limitations and challenges that that model had today there's tremendous cloud innovation happening in the public cloud it's being driven by a handful of massive companies and much like the innovation that sundeck HP and others drove in a you in the UNIX era of community of computing many customers want to take advantage of the best innovation no matter where it comes from buddy but as they even eventually saw in the UNIX era they can't afford the best innovation at the cost of a siloed operating environment with the open community we are building a hybrid application platform that can give you access to the best innovation no matter which vendor or which cloud that it comes from letting public cloud providers innovate and services beyond what customers or anyone can one provider can do on their own such as large scale learning machine learning or artificial intelligence built on the data that's unique probably to that to that one cloud but consumed in a common way for the end customer across all applications in any environment on any footprint in in their overall IT infrastructure this is exactly what rel brought brought to our customers in the UNIX era of computing that consistency across any of those footprints obviously enterprises will have applications for all different uses some will live on premise some in the cloud hybrid cloud is the only practical way forward I think you've been hearing that from us for a long time it is the only practical way forward and it'll be as impactful as anything we've ever seen before I want to bring Byrne his team back to see a hybrid cloud deployment in action burr [Music] all right earlier you saw what we did with taking bare metal and lighting it up with OpenStack director and making it openshift ready for developers to build their next generation applications now we want to show you when those next turn and generation applications and what we've done is we take an open shift and spread it out and installed it across Asia and Amazon a true hybrid cloud so with me on stage today as Ted who's gonna walk us through an application and Brent Midwood who's our DevOps engineer who's gonna be making sure he's monitoring on the backside that we do make sure we do a good job so at this point Ted what have you got for us Thank You BER and good morning everybody this morning we are running on the stage in our private cloud an application that's providing its providing fraud detection detect serves for financial transactions and our customer base is rather large and we occasionally take extended bursts of traffic of heavy traffic load so in order to keep our latency down and keep our customers happy we've deployed extra service capacity in the public cloud so we have capacity with Microsoft Azure in Texas and with Amazon Web Services in Ohio so we use open chip container platform on all three locations because openshift makes it easy for us to deploy our containerized services wherever we want to put them but the question still remains how do we establish seamless communication across our entire enterprise and more importantly how do we balance the workload across these three locations in such a way that we efficiently use our resources and that we give our customers the best possible experience so this is where Red Hat amq interconnect comes in as you can see we've deployed a MQ interconnect alongside our fraud detection applications in all three locations and if I switch to the MQ console we'll see the topology of the app of the network that we've created here so the router inside the on stage here has made connections outbound to the public routers and AWS and Azure these connections are secured using mutual TLS authentication and encrypt and once these connections are established amq figures out the best way auda matically to route traffic to where it needs to get to so what we have right now is a distributed reliable broker list message bus that expands our entire enterprise now if you want to learn more about this make sure that you catch the a MQ breakout tomorrow at 11:45 with Jack Britton and David Ingham let's have a look at the message flow and we'll dive in and isolate the fraud detection API that we're interested in and what we see is that all the traffic is being handled in the private cloud that's what we expect because our latencies are low and they're acceptable but now if we take a little bit of a burst of increased traffic we're gonna see that an EQ is going to push a little a bi traffic out onto the out to the public cloud so as you're picking up some of the load now to keep the Layton sees down now when that subsides as your finishes up what it's doing and goes back offline now if we take a much bigger load increase you'll see two things first of all asher is going to take a bigger proportion than it did before and Amazon Web Services is going to get thrown into the fray as well now AWS is actually doing less work than I expected it to do I expected a little bit of bigger a slice there but this is a interesting illustration of what's going on for load balancing mq load balancing is sending requests to the services that have the lowest backlog and in order to keep the Layton sees as steady as possible so AWS is probably running slowly for some reason and that's causing a and Q to push less traffic its way now the other thing you're going to notice if you look carefully this graph fluctuate slightly and those fluctuations are caused by all the variances in the network we have the cloud on stage and we have clouds in in the various places across the country there's a lot of equipment locked layers of virtualization and networking in between and we're reacting in real-time to the reality on the digital street so BER what's the story with a to be less I noticed there's a problem right here right now we seem to have a little bit performance issue so guys I noticed that as well and a little bit ago I actually got an alert from red ahead of insights letting us know that there might be some potential optimizations we could make to our environment so let's take a look at insights so here's the Red Hat insights interface you can see our three OpenShift deployments so we have the set up here on stage in San Francisco we have our Azure deployment in Texas and we also have our AWS deployment in Ohio and insights is highlighting that that deployment in Ohio may have some issues that need some attention so Red Hat insights collects anonymized data from manage systems across our customer environment and that gives us visibility into things like vulnerabilities compliance configuration assessment and of course Red Hat subscription consumption all of this is presented in a SAS offering so it's really really easy to use it requires minimal infrastructure upfront and it provides an immediate return on investment what insights is showing us here is that we have some potential issues on the configuration side that may need some attention from this view I actually get a look at all the systems in our inventory including instances and containers and you can see here on the left that insights is highlighting one of those instances as needing some potential attention it might be a candidate for optimization this might be related to the issues that you were seeing just a minute ago insights uses machine learning and AI techniques to analyze all collected data so we combine collected data from not only the system's configuration but also with other systems from across the Red Hat customer base this allows us to compare ourselves to how we're doing across the entire set of industries including our own vertical in this case the financial services industry and we can compare ourselves to other customers we also get access to tailored recommendations that let us know what we can do to optimize our systems so in this particular case we're actually detecting an issue here where we are an outlier so our configuration has been compared to other configurations across the customer base and in this particular instance in this security group were misconfigured and so insights actually gives us the steps that we need to use to remediate the situation and the really neat thing here is that we actually get access to a custom ansible playbook so if we want to automate that type of a remediation we can use this inside of Red Hat ansible tower Red Hat satellite Red Hat cloud forms it's really really powerful the other thing here is that we can actually apply these recommendations right from within the Red Hat insights interface so with just a few clicks I can select all the recommendations that insights is making and using that built-in ansible automation I can apply those recommendations really really quickly across a variety of systems this type of intelligent automation is really cool it's really fast and powerful so really quickly here we're going to see the impact of those changes and so we can tell that we're doing a little better than we were a few minutes ago when compared across the customer base as well as within the financial industry and if we go back and look at the map we should see that our AWS employment in Ohio is in a much better state than it was just a few minutes ago so I'm wondering Ted if this had any effect and might be helping with some of the issues that you were seeing let's take a look looks like went green now let's see what it looks like over here yeah doesn't look like the configuration is taking effect quite yet maybe there's some delay awesome fantastic the man yeah so now we're load balancing across the three clouds very much fantastic well I have two minute Ted I truly love how we can route requests and dynamically load transactions across these three clouds a truly hybrid cloud native application you guys saw here on on stage for the first time and it's a fully portable application if you build your applications with openshift you can mover from cloud to cloud to cloud on stage private all the way out to the public said it's totally awesome we also have the application being fully managed by Red Hat insights I love having that intelligence watching over us and ensuring that we're doing everything correctly that is fundamentally awesome thank you so much for that well we actually have more to show you but you're going to wait a few minutes longer right now we'd like to welcome Paul back to the stage and we have a very special early Red Hat customer an Innovation Award winner from 2010 who's been going boldly forward with their open hybrid cloud strategy please give a warm welcome to Monty Finkelstein from Citigroup [Music] [Music] hi Marty hey Paul nice to see you thank you very much for coming so thank you for having me Oh our pleasure if you if you wanted to we sort of wanted to pick your brain a little bit about your experiences and sort of leading leading the charge in computing here so we're all talking about hybrid cloud how has the hybrid cloud strategy influenced where you are today in your computing environment so you know when we see the variable the various types of workload that we had an hour on from cloud we see the peaks we see the valleys we see the demand on the environment that we have we really determined that we have to have a much more elastic more scalable capability so we can burst and stretch our environments to multiple cloud providers these capabilities have now been proven at City and of course we consider what the data risk is as well as any regulatory requirement so how do you how do you tackle the complexity of multiple cloud environments so every cloud provider has its own unique set of capabilities they have they're own api's distributions value-added services we wanted to make sure that we could arbitrate between the different cloud providers maintain all source code and orchestration capabilities on Prem to drive those capabilities from within our platforms this requires controlling the entitlements in a cohesive fashion across our on Prem and Wolfram both for security services automation telemetry as one seamless unit can you talk a bit about how you decide when you to use your own on-premise infrastructure versus cloud resources sure so there are multiple dimensions that we take into account right so the first dimension we talk about the risk so low risk - high risk and and really that's about the data classification of the environment we're talking about so whether it's public or internal which would be considered low - ooh confidential PII restricted sensitive and so on and above which is really what would be considered a high-risk the second dimension would be would focus on demand volatility and responsiveness sensitivity so this would range from low response sensitivity and low variability of the type of workload that we have to the high response sensitivity and high variability of the workload the first combination that we focused on is the low risk and high variability and high sensitivity for response type workload of course any of the workloads we ensure that we're regulatory compliant as well as we achieve customer benefits with within this environment so how can we give developers greater control of their their infrastructure environments and still help operations maintain that consistency in compliance so the main driver is really to use the public cloud is scale speed and increased developer efficiencies as well as reducing cost as well as risk this would mean providing develop workspaces and multiple environments for our developers to quickly create products for our customers all this is done of course in a DevOps model while maintaining the source and artifacts registry on-prem this would allow our developers to test and select various middleware products another product but also ensure all the compliance activities in a centrally controlled repository so we really really appreciate you coming by and sharing that with us today Monte thank you so much for coming to the red echo thanks a lot thanks again tamati I mean you know there's these real world insight into how our products and technologies are really running the businesses today that's that's just the most exciting part so thank thanks thanks again mati no even it with as much progress as you've seen demonstrated here and you're going to continue to see all week long we're far from done so I want to just take us a little bit into the path forward and where we we go today we've talked about this a lot innovation today is driven by open source development I don't think there's any question about that certainly not in this room and even across the industry as a whole that's a long way that we've come from when we started our first summit 14 years ago with over a million open source projects out there this unit this innovation aggregates into various community platforms and it finally culminates in commercial open source based open source developed products these products run many of the mission-critical applications in business today you've heard just a couple of those today here on stage but it's everywhere it's running the world today but to make customers successful with that interact innovation to run their real-world business applications these open source products have to be able to leverage increase increasingly complex infrastructure footprints we must also ensure a common base for the developer and ultimately the application no matter which footprint they choose as you heard mati say the developers want choice here no matter which no matter which footprint they are ultimately going to run their those applications on they want that flexibility from the data center to possibly any public cloud out there in regardless of whether that application was built yesterday or has been running the business for the last 10 years and was built on 10-year old technology this is the flexibility that developers require today but what does different infrastructure we may require different pieces of the technical stack in that deployment one example of this that Effects of many things as KVM which provides the foundation for many of those use cases that require virtualization KVM offers a level of consistency from a technical perspective but rel extends that consistency to add a level of commercial and ecosystem consistency for the application across all those footprints this is very important in the enterprise but while rel and KVM formed the foundation other technologies are needed to really satisfy the functions on these different footprints traditional virtualization has requirements that are satisfied by projects like overt and products like Rev traditional traditional private cloud implementations has requirements that are satisfied on projects like OpenStack and products like Red Hat OpenStack platform and as applications begin to become more container based we are seeing many requirements driven driven natively into containers the same Linux in different forms provides this common base across these four footprints this level of compatible compatibility is critical to operators who must best utilize the infinite must better utilize secure and deploy the infrastructure that they have and they're responsible for developers on the other hand they care most about having a platform that can creates that consistency for their applications they care about their services and the services that they need to consume within those applications and they don't want limitations on where they run they want service but they want it anywhere not necessarily just from Amazon they want integration between applications no matter where they run they still want to run their Java EE now named Jakarta EE apps and bring those applications forward into containers and micro services they need able to orchestrate these frameworks and many more across all these different footprints in a consistent secure fashion this creates natural tension between development and operations frankly customers amplify this tension with organizational boundaries that are holdover from the UNIX era of computing it's really the job of our platforms to seamlessly remove these boundaries and it's the it's the goal of RedHat to seamlessly get you from the old world to the new world we're gonna show you a really cool demo demonstration now we're gonna show you how you can automate this transition first we're gonna take a Windows virtual machine from a traditional VMware deployment we're gonna convert it into a KVM based virtual machine running in a container all under the kubernetes umbrella this makes virtual machines more access more accessible to the developer this will accelerate the transformation of those virtual machines into cloud native container based form well we will work this prot we will worked as capability over the product line in the coming releases so we can strike the balance of enabling our developers to move in this direction we want to be able to do this while enabling mission-critical operations to still do their job so let's bring Byrne his team back up to show you this in action for one more thanks all right what Red Hat we recognized that large organizations large enterprises have a substantial investment and legacy virtualization technology and this is holding you back you have thousands of virtual machines that need to be modernized so what you're about to see next okay it's something very special with me here on stage we have James Lebowski he's gonna be walking us through he's represents our operations folks and he's gonna be walking us through a mass migration but also is Itamar Hine who's our lead developer of a very special application and he's gonna be modernizing container izing and optimizing our application all right so let's get started James thanks burr yeah so as you can see I have a typical VMware environment here I'm in the vSphere client I've got a number of virtual machines a handful of them that make up my one of my applications for my development environment in this case and what I want to do is migrate those over to a KVM based right at virtualization environment so what I'm gonna do is I'm gonna go to cloud forms our cloud management platform that's our first step and you know cloud forms actually already has discovered both my rev environment and my vSphere environment and understands the compute network and storage there so you'll notice one of the capabilities we built is this new capability called migrations and underneath here I could begin to there's two steps and the first thing I need to do is start to create my infrastructure mappings what this will allow me to do is map my compute networking storage between vSphere and Rev so cloud forms understands how those relate let's go ahead and create an infrastructure mapping I'll call that summit infrastructure mapping and then I'm gonna begin to map my two environments first the compute so the clusters here next the data stores so those virtual machines happen to live on datastore - in vSphere and I'll target them a datastore data to inside of my revenue Arman and finally my networks those live on network 100 so I'll map those from vSphere to rover so once my infrastructure is map the next step I need to do is actually begin to create a plan to migrate those virtual machines so I'll continue to the plan wizard here I'll select the infrastructure mapping I just created and I'll select migrate my development environment from those virtual machines to Rev and then I need to import a CSV file the CSV file is going to contain a list of all the virtual machines that I want to migrate that were there and that's it once I hit create what's going to happen cloud forms is going to begin in an automated fashion shutting down those virtual machines begin converting them taking care of all the minutia that you'd have to do manually it's gonna do that all automatically for me so I don't have to worry about all those manual interactions and no longer do I have to go manually shut them down but it's going to take care of that all for me you can see the migrations kicked off here this is the I've got the my VMs are migrating here and if I go back to the screen here you can see that we're gonna start seeing those shutdown okay awesome but as people want to know more information about this how would they dive deeper into this technology later this week yeah it's a great question so we have a workload portability session in the hybrid cloud on Wednesday if you want to see a presentation that deep dives into this topic and how some of the methodologies to migrate and then on Thursday we actually have a hands-on lab it's the IT optimization VM migration lab that you can check out and as you can see those are shutting down here yeah we see a powering off right now that's fantastic absolutely so if I go back now that's gonna take a while you got to convert all the disks and move them over but we'll notice is previously I had already run one migration of a single application that was a Windows virtual machine running and if I browse over to Red Hat virtualization I can see on the dashboard here I could browse to virtual machines I have migrated that Windows virtual machine and if I open up a tab I can now browse to my Windows virtual machine which is running our wingtip toy store application our sample application here and now my VM has been moved over from Rev to Vita from VMware to Rev and is available for Itamar all right great available to our developers all right Itamar what are you gonna do for us here well James it's great that you can save cost by moving from VMware to reddit virtualization but I want to containerize our application and with container native virtualization I can run my virtual machine on OpenShift like any other container using Huebert a kubernetes operator to run and manage virtual machines let's look at the open ship service catalog you can see we have a new virtualization section here we can import KVM or VMware virtual machines or if there are already loaded we can create new instances of them for the developer to work with just need to give named CPU memory we can do other virtualization parameters and create our virtual machines now let's see how this looks like in the openshift console the cool thing about KVM is virtual machines are just Linux processes so they can act and behave like other open shipped applications we build in more than a decade of virtualization experience with KVM reddit virtualization and OpenStack and can now benefit from kubernetes and open shift to manage and orchestrate our virtual machines since we know this virtual machine this container is actually a virtual machine we can do virtual machine stuff with it like shutdown reboot or open a remote desktop session to it but we can also see this is just a container like any other container in openshift and even though the web application is running inside a Windows virtual machine the developer can still use open shift mechanisms like services and routes let's browse our web application using the OpenShift service it's the same wingtip toys application but this time the virtual machine is running on open shift but we're not done we want to containerize our application since it's a Windows virtual machine we can open a remote desktop session to it we see we have here Visual Studio and an asp.net application let's start container izing by moving the Microsoft sequel server database from running inside the Windows virtual machine to running on Red Hat Enterprise Linux as an open shipped container we'll go back to the open shipped Service Catalog this time we'll go to the database section and just as easily we'll create a sequel server container just need to accept the EULA provide password and choose the Edition we want and create a database and again we can see the sequel server is just another container running on OpenShift now let's take let's find the connection details for our database to keep this simple we'll take the IP address of our database service go back to the web application to visual studio update the IP address in the connection string publish our application and go back to browse it through OpenShift fortunately for us the user experience team heard we're modernizing our application so they pitched in and pushed new icons to use with our containerized database to also modernize the look and feel it's still the same wingtip toys application it's running in a virtual machine on openshift but it's now using a containerized database to recap we saw that we can run virtual machines natively on openshift like any other container based application modernize and mesh them together we containerize the database but we can use the same approach to containerize any part of our application so some items here to deserve repeating one thing you saw is Red Hat Enterprise Linux burning sequel server in a container on open shift and you also saw Windows VM where the dotnet native application also running inside of open ships so tell us what's special about that that seems pretty crazy what you did there exactly burr if we take a look under the hood we can use the kubernetes commands to see the list of our containers in this case the sequel server and the virtual machine containers but since Q Bert is a kubernetes operator we can actually use kubernetes commands like cube Cpl to list our virtual machines and manage our virtual machines like any other entity in kubernetes I love that so there's your crew meta gem oh we can see the kind says virtual machine that is totally awesome now people here are gonna be very excited about what they just saw we're gonna get more information and when will this be coming well you know what can they do to dive in this will be available as part of reddit Cloud suite in tech preview later this year but we are looking for early adopters now so give us a call also come check our deep dive session introducing container native virtualization Thursday 2:00 p.m. awesome that is so incredible so we went from the old to the new from the close to the open the Red Hat way you're gonna be seeing more from our demonstration team that's coming Thursday at 8 a.m. do not be late if you like what you saw this today you're gonna see a lot more of that going forward so we got some really special things in store for you so at this point thank you so much in tomorrow thank you so much you guys are awesome yeah now we have one more special guest a very early adopter of Red Hat Enterprise Linux we've had over a 12-year partnership and relationship with this organization they've been a steadfast Linux and middleware customer for many many years now please extend a warm welcome to Raj China from the Royal Bank of Canada thank you thank you it's great to be here RBC is a large global full-service is back we have the largest bank in Canada top 10 global operate in 30 countries and run five key business segments personal commercial banking investor in Treasury services capital markets wealth management and insurance but honestly unless you're in the banking segment those five business segments that I just mentioned may not mean a lot to you but what you might appreciate is the fact that we've been around in business for over 150 years we started our digital transformation journey about four years ago and we are focused on new and innovative technologies that will help deliver the capabilities and lifestyle our clients are looking for we have a very simple vision and we often refer to it as the digitally enabled bank of the future but as you can appreciate transforming a hundred fifty year old Bank is not easy it certainly does not happen overnight to that end we had a clear unwavering vision a very strong innovation agenda and most importantly a focus towards a flawless execution today in banking business strategy and IT strategy are one in the same they are not two separate things we believe that in order to be the number one bank we have to have the number one tactic there is no question that most of today's innovations happens in the open source community RBC relies on RedHat as a key partner to help us consume these open source innovations in a manner that it meets our enterprise needs RBC was an early adopter of Linux we operate one of the largest footprints of rel in Canada same with tables we had tremendous success in driving cost out of infrastructure by partnering with rahat while at the same time delivering a world-class hosting service to your business over our 12 year partnership Red Hat has proven that they have mastered the art of working closely with the upstream open source community understanding the needs of an enterprise like us in delivering these open source innovations in a manner that we can consume and build upon we are working with red hat to help increase our agility and better leverage public and private cloud offerings we adopted virtualization ansible and containers and are excited about continuing our partnership with Red Hat in this journey throughout this journey we simply cannot replace everything we've had from the past we have to bring forward these investments of the past and improve upon them with new and emerging technologies it is about utilizing emerging technologies but at the same time focusing on the business outcome the business outcome for us is serving our clients and delivering the information that they are looking for whenever they need it and in whatever form factor they're looking for but technology improvements alone are simply not sufficient to do a digital transformation creating the right culture of change and adopting new methodologies is key we introduced agile and DevOps which has boosted the number of adult projects at RBC and increase the frequency at which we do new releases to our mobile app as a matter of fact these methodologies have enabled us to deliver apps over 20x faster than before the other point about around culture that I wanted to mention was we wanted to build an engineering culture an engineering culture is one which rewards curiosity trying new things investing in new technologies and being a leader not necessarily a follower Red Hat has been a critical partner in our journey to date as we adopt elements of open source culture in engineering culture what you seen today about red hearts focus on new technology innovations while never losing sight of helping you bring forward the investments you've already made in the past is something that makes Red Hat unique we are excited to see red arts investment in leadership in open source technologies to help bring the potential of these amazing things together thank you that's great the thing you know seeing going from the old world to the new with automation so you know the things you've seen demonstrated today they're they're they're more sophisticated than any one company could ever have done on their own certainly not by using a proprietary development model because of this it's really easy to see why open source has become the center of gravity for enterprise computing today with all the progress open-source has made we're constantly looking for new ways of accelerating that into our products so we can take that into the enterprise with customers like these that you've met what you've met today now we recently made in addition to the Red Hat family we brought in core OS to the Red Hat family and you know adding core OS has really been our latest move to accelerate that innovation into our products this will help the adoption of open shift container platform even deeper into the enterprise and as we did with the Linux core platform in 2002 this is just exactly what we did with with Linux back then today we're announcing some exciting new technology directions first we'll integrate the benefits of automated operations so for example you'll see dramatic improvements in the automated intelligence about the state of your clusters in OpenShift with the core OS additions also as part of open shift will include a new variant of rel called Red Hat core OS maintaining the consistency of rel farhat for the operation side of the house while allowing for a consumption of over-the-air updates from the kernel to kubernetes later today you'll hear how we are extending automated operations beyond customers and even out to partners all of this starting with the next release of open shift in July now all of this of course will continue in an upstream open source innovation model that includes continuing container linux for the community users today while also evolving the commercial products to bring that innovation out to the enterprise this this combination is really defining the platform of the future everything we've done for the last 16 years since we first brought rel to the commercial market because get has been to get us just to this point hybrid cloud computing is now being deployed multiple times in enterprises every single day all powered by the open source model and powered by the open source model we will continue to redefine the software industry forever no in 2002 with all of you we made Linux the choice for enterprise computing this changed the innovation model forever and I started the session today talking about our prediction of seven years ago on the future being open we've all seen so much happen in those in those seven years we at Red Hat have celebrated our 25th anniversary including 16 years of rel and the enterprise it's now 2018 open hybrid cloud is not only a reality but it is the driving model in enterprise computing today and this hybrid cloud world would not even be possible without Linux as a platform in the open source development model a build around it and while we have think we may have accomplished a lot in that time and we may think we have changed the world a lot we have but I'm telling you the best is yet to come now that Linux and open source software is firmly driving that innovation in the enterprise what we've accomplished today and up till now has just set the stage for us together to change the world once again and just as we did with rel more than 15 years ago with our partners we will make hybrid cloud the default in the enterprise and I will take that bet every single day have a great show and have fun watching the future of computing unfold right in front of your eyes see you later [Applause] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] anytime [Music]

>> Announcer: Live from the Moscone Center, it's theCUBE covering AWS Summit San Francisco, 2018, brought to you by Amazon Web Services. (techy music playing) >> Welcome back, I'm Stu Miniman joined by my cohost Jeff Frick, and this is theCUBE's live coverage of AWS Summit San Francisco. We are thrilled to welcome back to the program Sandy Carter, who's a vice president with Amazon Web Services. Been with the company about a year. We've had you on the program many times, but first time since you've been at AWS, so... >> That's right, I'm celebrating my year yesterday with Amazon Web Services. >> Stu: And no cake, all right. >> I had a cake yesterday, actually, cake and champagne, by the way. (laughing) >> Sandy, we always love to hear, you know, you talk to so many customers, you know, bring us back for a little bit. What brought you to AWS, what's exciting to your customers when you're talking to them today? >> Well, you know, I really love innovation, I love being innovative, and you know, bar none Amazon is the most innovative company out there today, but really what brought me to Amazon was their focus on the customer, really "obsession" on the customer. When they say obsession they really mean obsession. They work backwards from the customer. We really have this big, big thrust. In fact, one of my favorite stories is when I first came to Amazon we'd be in these meetings and people would say, "Well, what does Low Flying Hawk think about this," or "What does Low Flying Hawk think about that," and I was like, "Who is Low Flying Hawk?" Well, he's a person who would give comments on a forum and just a person who wasn't even spending millions of dollars with Amazon but just had a lot of big clout. We actually just opened a building named Low Flying Hawk, believe it or not. >> Jeff: Have you identified this person? >> They do know who he is, yes. (laughing) But it's really, it just symbolizes the focus that Amazon has on the customer and why that's so important. >> And Sandy, at re:Invent you actually, you spoke to the analyst, I was listening to the session. It's not just kind of, people think AWS they think public cloud. You work for Amazon, it's everything kind of across what you think of Amazon.com, AWS, everything from drones and using Kindles and everything like that. Can you give us a little bit of kind of that pan view of how Amazon looks at innovation? >> Yeah, so it's really interesting. Amazon is very methodical in the way that we innovate, and what we do is we really try to understand the customer. We work backwards from the customer, so we do a press release first, we do frequently asked questions next, and then we do a narrative-- >> You're saying you do an internal press release, yes, yes. >> Yeah, internal press release. Internal frequently asked questions, and then we review a six-page document, no PowerPoints whatsoever, which enables us to debate and learn from each other and just iterate on the idea that makes it better and better and better so that when we come out with it it's a really powerful idea and powerful concept, something that the customers really want. >> So, we'll ask you what you're doing now, but one more kind of transition question, what was your biggest surprise? You know, there's a lot of kind of mystery from people on the outside looking in in terms of culture, and we know it's car driving and innovative growing like crazy company, not only in business but in terms of people. What was your biggest surprise once you kind of got on the inside door? >> My biggest surprise was just how incredibly encouraging and supportive the team is at AWS. My boss is Matt Garman, he's been supportive since day one, you know, Andy, they just cheer you on. They want you to do well and I've really never been at a company that everybody's really pulling for you to be successful, not political infighting but really pulling for you to be successful. So, that's really was the biggest surprise to me, and then that customer obsession. Like, it's not customer focus, it really is customer obsession. >> Right, I think it's so well illustrated by the, again not AWS, but Amazon with the store, right, with no cash register, no people. >> Sandy: Amazon Go. >> To think about that-- >> Sandy: Yeah. >> From the customer point of view is nobody likes to stand in line at the grocery store, so it's such a clean illustration of a customer centric way to attack the problem. >> And I love that because what we did is we opened up the beta first for employees, so we would go in and play with it and test it out, and then we opened it up in Seattle and we would give customer tours. Now it's open to the public in Seattle, so it just again shows you that iterative process that Amazon uses and it's super cool, have you guys been? >> Jeff: Have not been. >> Ugh, in fact, my daughter went in. She put on a mask, she was going to fool the system but it wasn't fooled. All the ML and all the AI worked brilliantly. >> I love how everyone loves to get so creative and try to, you know, get through the system, right, try to break the system. >> I know, but my daughter, that's what I would figure for sure. (laughing) >> So, what are you working on now? You've been there a year, what are you working on? >> So, we are innovating around the enterprise workload, so we know that a lot of startups and cloud native companies have moved to the cloud, but we're still seeing a lot of enterprises that are trying to figure out what their strategy is, and so, Stu and Jeff, what I've been working on is how do we help enterprises in the best way possible. How can we innovate to get them migrated over as fast as possible? So for instance, we have Windows that runs on AWS. It's actually been running there longer than with any other vendor and we have amazing performance, amazing reliability. We just released an ML, machine learning OMI for Windows so that you can use and leverage all that great Windows support and applications that you have, and then you guys saw earlier I was talking to VMware. We know that a lot of customers want to do hybrid cloud on their journey to going all-in with the cloud, and so we formed this great partnership with VMware, produced an offering called VMware Cloud on AWS and we're seeing great traction there. Like Scribd's network just talked about how they're using it for disaster recovery. Other customers are using it to migrate. One CIO migrated 143 workloads in a weekend using that solution. So, it just helps them to get to that hybrid state before they go all-in on the cloud. >> So, are they, I was going to say, are they building a mirror instance of what their on-prem VMware stack is in the Amazon version? Is that how they're kind of negotiating that transition or how does that work? >> So, with VMware they don't have to refactor, so they can just go straight over. With Microsoft workloads what we're seeing a lot of times is maybe they'll bring a sequel app over and they'll just do a lift and shift, and then once they feel comfortable with the cloud they'll go to Aurora, which as you've found was the fastest growing service that AWS has ever had, and so we see a lot of that, you know, movement. Bring it over, lift and shift, learning and you know, if you think about it, if you're a large enterprise one of your big challenges is how do I get my people trained, how do I get them up to speed, and so we've done... Like, we've got a full dot net stack that runs on AWS, so their people don't even have to learn a new language. They can develop in Visual Studio and use PowerShell but work on AWS and bring that over. >> You know, Sandy, bring us inside your customers because the challenge for most enterprises is they have so many applications. >> Sandy: Yeah. >> And you mentioned lift and shift. >> Sandy: Yeah. >> You know, I know some consultant's out there like, "Lift and shift is horrible, don't do it." It's like, well, there's some things you'll build new in the cloud, there's some things you'll do a little bit, and there's some stuff today lift and shift makes sense and then down the road I might, you know, move and I've seen, you know, it was like the seven Rs that Amazon has as to do you re-platform, refactor-- >> That's right. >> You know, all that and everything, so I mean, there's many paths to get there. What are some of the patterns you're hearing from customers? How do they, how is it easier for them to kind of move forward and not get stuck? >> Well, we're seeing a lot of data center evacuations, so those tend to be really fast movement and that's typically-- >> Jeff: Data center evacuation-- >> Yeah, that's what-- >> I haven't heard that one. >> Yeah, that's what, evacuation, they've got to get out of their data center buyer for a certain date for whatever reason, right? They had a flood or a corporate mandate or something going on, and so we are seeing those and those are, Stu, like lift and shift quickly. We are seeing a lot of customers who will create new applications using containers and serverless that we talked about today a lot, and that's really around the innovative, new stuff that they're doing, right. So, Just Eat, for instance, is a large... They do online food service out of the UK. I love their solution because what they're doing is they're using Alexa to now order food, so you can say, "Alexa, I want a pizza delivered "in 20 minutes, what's the best pizza place "that I can get in 20 minutes?" Or "I want sushi tonight," and Alexa will come back and say, "Well, it's going to take "an hour and a half, you had sushi two days ago. "Maybe you want to do Thai food tonight." (laughing) And so it's really incredible, and then they even innovated and they're using Amazon Fire for group ordering. So, if there's a big football game or something going on they'll use Amazon Fire to do that group ordering. All that is coming in through Alexa, but the back end is still Windows on AWS. So, I love the fact that they're creating these new apps but they're using some of that lift and shift to get the data and the training and all that moving and grooving, too. >> Yeah, what do you, from the training standpoint, how, you know, ready are customers to retrain their people, you know, where are there shortages of skillsets, and how's Amazon, you know, helping in that whole movement? >> Well, training is essential because you've got so many great people at enterprises who have these great skills, so what we see a lot of people doing is leveraging things like dot net on AWS. So, they actually... They have something they know, dot net, but yet they're learning about the cloud, and so we're helping them do that training as they're going along but they still have something very familiar. Folks like Capital One did a huge training effort. They trained 1,000 people in a year on cloud. They did deep dives with a Tiger Team on cloud to get them really into the architecture and really understanding what was going on, so they could leverage all those great skills that they had in IT. So, we're seeing everything from, "I got to use some of the current tools that I have," to "Let me completely move to something new." >> And how have you, you've been in the Bay Area also for about a year, right, if I recall? >> Actually, I just moved, I moved to Seattle. >> Jeff: Oh, you did make the move, I was going to say-- >> I did. (laughing) >> "So, are they going to make you move up north?" >> I did because I was-- >> You timed it in the spring, not in November? >> I did, there you go. (laughing) When it's nice and sunny, but it's great. >> Exactly. >> It's great to live in Seattle. Amazon has such a culture that is in person, you know, so many people work there. It's really exhilarating to go into the office and brainstorm and whiteboard with people right there, and then our EBCs are there, so our executive briefing center is there, so customers come in all the time because they want to go see Amazon Go, and so it's really an exciting, energizing place to be. >> Yeah, I love the line that Warner used this morning is that AWS customers are builders and they have a bias for action. So, how do you help customers kind of translate some of the, you know, the culture that Amazon's living and kind of acting like a startup for such a large company into kind of the enterprise mindset? >> That's a great question, so we just proposed this digital innovation workshop. We are doing this now with customers. So, we're teaching them how to work backwards from the customer, how to really understand what a customer need is and how to make sure they're not biased when they're getting that customer need coming in. How to do, build an empathy map and how to write that press release, that internal press release and think differently. So, we're actually teaching customers to do it. It's one of our hottest areas today. When customers do that they commit to doing a proof of concept with us on AWS on one of the new, innovative ideas. So, we've seen a lot of great and exciting innovation coming out of that. >> All right, well, Sandy Carter, so glad we could catch up with you again. Thanks for bringing discussion of innovation, what's happening in the enterprise customers to our audience. For Jeff Frick, I'm Stu Miniman, we'll be back will lots more coverage here, you're watching theCUBE. (techy music playing)

>> Hi I'm Peter Burris and welcome to another Wikibon Action Action Item Quick Take. Jim Kobielus, Microsoft seems to be gettin' ready to do a makeover of application development. What's going on? >> Yeah, that's pretty exciting, Peter. So, last week, on the 7th, Microsoft added in one of their Developer Days and now something called AI Platform for Windows and let me explain why that's important. Because that is going to bring Machine Learning down to the desktop applications, anything that's written to run on Windows 10. And why that's important is that, starting with Visual Studio 15.7, they'll be an ability for developers who don't know anything about Machine Learning to be able to, in a very visual way, create Machine Learning models, that they can then have trained in the cloud, and then deployed to their Windows applications, whatever it might be, and to do real-time, local inferencing in those applications, without need for round-tripping back to the cloud. So, what we're looking at now is they're going to bring this capability into the core of Visual Studio and then they're going to be backwards compatible with previous versions of Visual Studio. What that means is, I can just imagine, over the next couple of years, most Windows applications will be heavily ML enabled, so that more and more of the application logic at the desktop in Windows, will be driven by ML, they'll be less need for apps, as we've known them, historically, pre-packaged bundles of code. It'll be dynamic logic. It'll be ML. So, I think this is really marking the beginning of the end of the app era at the device level, I think. So, I'm really excited and we're looking forward to hearing more about Microsoft, where they're going with AI Platform for Windows, but I think that's a landmark announcement we'll stay tuned for. >> Excellent. Jim Kobielus, thank you very much. This has been another Wikibon Action Item Quick Take. (soft digital music)