(upbeat music) >> Welcome back, everyone. Live coverage here at KubeCon + CloudNativeCon here in Detroit, Michigan. I'm John Furrier, your host of theCUBE for special one-on-one conversation with Scott Johnston, who's the CEO of Docker, CUBE alumni, been around the industry, multiple cycles of innovation, leading one of the most important companies in today's industry inflection point as Docker what they've done since they're, I would say restart from the old Docker to the new Docker, now modern, and the center of the conversation with containers driving the growth of Kubernetes. Scott, great to see you. Thanks for coming on theCUBE. >> John, thanks for the invite. Glad to be here. >> You guys have had great success this year with extensions. Docker as a business model's grown. Congratulations, you guys are monetizing well. Pushing up over 50 million. >> Thank you. >> I hear over pushing a hundred million maybe. What the year to the ground will tell me, but it's good sign. Plus you've got the community and nurturing of the ecosystem continuing to power away and open source is not stopping. It's thundering away growth. Younger generation coming in. >> That's right. >> Developer tool chain that you have has become consistent. Almost de facto standard. Others are coming in the market. A lot of competition emerging. You got a lot going on right now. What's going on? >> Well, I know it's fantastic time in our industry. Like all companies are becoming software companies. That means they need to build new applications. That means they need developers to be productive and to be safely productive. And we, and this wonderful CNCF ecosystem are right in the middle of that trend, so it's fantastic. >> So you have millions of developers using Docker. >> Tens of millions. >> Tens of millions of developed Docker and as the market's changing, I was commenting before we came on camera, and I'd love to get your reaction, comment on it. You guys represent the modernization of containers, open source. You haven't really changed how open source works, but you've kind of modernized it. You're starting to see developers at the front lines, more and more power going to developers. >> Scott: That's right. >> They want self-service. They vote with their code. >> That's right. >> They vote with their actions. >> Scott: That's right. >> And if you take digital transformation to its conclusion, it's not IT serves the business or it's a department, the company is IT. >> That's right. >> The company is the application, which means developers are running everything. >> Yes, yes. I mean, one of the jokes, not jokes in the valley is that Tesla is in a car company. Tesla is a computer company that happens to have wheels on the computer. And I think we can smile at that, but there's so many businesses, particularly during COVID, that realize that. What happened during COCID? If you're going to the movies, nope, you're now going to Netflix. If you're going to the gym, now you're doing Peloton. So this realization that like I have to have a digital game, not just on the side, but it has to be the forefront of my business and drive my business. That realization is now any industry, any company across the board. >> We've been reporting aggressively for past three years now. Even now we're calling some things supercloud. If companies, if they don't realize that IT is not a department, they will probably be out of business. >> That's a hundred percent. >> It's going to transform into full on invisible infrastructure. Infrastructure as code, whatever you want to call that going, configuration, operations, developers will set the pace. This has a lot to do with some of your success. You're at the beginning of it. This is just the beginning. What can you talk about that in your mind is contributing to the success of Docker? I know you're going to say team, everything, I get that, but like what specifically in the industry is driving Docker's success right now? >> Well, it did. We did have a fantastic team. We do have a fantastic team and that is one of the reasons, primary reasons our success. But what is also happening, John, is because there's a demand for applications, I'll just throw it out there. 750 million new applications are coming in the market in the next two years. That is more applications that have been developed in the entire 40 years history of IT. So just think about the productivity demands that are coming at developers. And then you also see the need to do so safely, meaning ship quickly, but ship safely. And yet 90 some percent of every application consists of open source components that are now on attack surface for criminals. And so typically our industry has had to say one or the other, okay, you can ship quickly but not safely, or you can ship safely, but it's not going to go fast. And one of the reasons I think Docker is where it is today is that we're able to offer both. We're able to unlock that you can ship quickly, safely using Docker, using the Docker toolchain, using integrations we have with all the wonderful partners here at CNCF that is unique. And that's a big reason why we're seeing the success we're seeing. >> And you're probably pleased with extensions this year. >> Yes. >> The performance of extensions that you launched at DockerCon '22. >> Yes. Well, extensions are part of that story and that developers have multiple tools. They want choice, developers like choice to be productive and Docker is part of that, but it's not the only solution. And so Docker extensions allow the monitoring providers and the observability and if you want a separate Kubernetes stack, like all of that flexibility, extensions allows. And again, offers the power and the innovation of this ecosystem to be used in a Docker development and context. >> Well, I want to get into some of the details of some of your products and how they're evolving. But first I want to get your thoughts on the trend line here that we reported at the opening segment. The hot story is WebAssembly, the Wasm, which really got a lot of traction or interest. People enthous about it. >> Interest, yeah. >> Lot of enthusiasm. Confidence we'll see how that evolves, but a lot of enthusiasm for sure. I've never seen something this hyped up since Envoy, in my opinion. So a lot of interest from developers. What is Wasm or WebAssembly is actually what it is, but Wasm is the codeword or nickname. What is Wasm? >> So in brief, WebAssembly is a new application type, full stop. And it's just enough of the components that you need and it's just a binary format that is very, very secure. And so it's lightweight, it's fast and secure. And so it opens up a lot of interesting use cases for developer, particularly on the edge. Another use case for Wasm is in the browser. Again, lightweight, fast, secure also. >> John: Sounds like an app server to me. >> And so we think it's a very, very interesting trend. And you ask, Okay, what's Docker's role in that? Well, Docker has been around eight years now, eight plus years, tens of millions developers using it. They've already made investments in skills, talent, automation, toolchains, pipelines. And Docker started with Linux containers as we know, then brought that same experience to Windows containers, then brought it to serverless functions. About 25% of Amazon Lambdas are OCI image containers. And so we were seeing that trend. We were also seeing the community actually without any prompting from us, start to fork and play with Docker and apply it to Wasm. And we're like, Huh, that's interesting. What if we helped get behind that trend, such that you changed just one line of a Docker file, now you're able to produce Wasm objects instead of Linux containers and just bring that same easy to use. >> So that's not a competition to Docker's? >> Not a competition at all. In fact, very complimentary. We showed off on Monday at the Wasm day, how in the same Docker compose application, multi-service application. One service is delivered via Linux container, Another service is delivered via Wasm. >> And Wasm is what? Multiple languages? 'Cause what is it? >> Yes. So the binary can be compiled from multiple languages. So RAS, JavaScript, on and on and on. At the end of the day, it's a smaller binary that provides a function, typically a single function that you can stand up and deploy on an edge. You can stand up and deploy on the server side or stand up and deploy on the browser. >> So from a container standpoint, from your customer standpoint, what a Linux container is is a similar thing to what a Wasm container is. >> They could implement the same function. That's right. Now a Linux container can have more capabilities that a function might not have, but that's. >> John: From a workflow standpoint. >> That's right. And that's more of a use case by use case standpoint. What we serve is we serve developers and we started out serving developers with Linux containers, then Windows containers, then Lambdas, now Wasm. Whatever other use case, what other application type comes along, we want to be there to serve developers. >> So one of the things I want to get your thoughts on, because this has come up in a couple CUBE interviews before, and we were talking before we came on camera, is developers want ease of use and simplicity. They don't want more steps to do things. They don't want things harder. >> That's right. So the classic innovation is reduce the time it takes to do something, reduce the steps, make it easier. That's a formula of success. >> Scott: That's right. >> When you start adding more toolchains into the mix, you get tool sprawl. So that's not really, that's antithesis to developer. So the argument is, okay, do I have to use a new tool chain for Wasm? Is that a fact or no? >> That's exactly right. That was what we were seeing and we thought, well, how can Docker help with this situation? And Docker can help by bringing the same existing toolchain that developers are already familiar with. The same automation, the same pipelines. And just by changing a line of Docker file, changing a single line of composed file, now they get the power of Wasm unlocked in the very same tools they were using before. >> So your position is, hey, don't adopt some toolchain for Wasm. You can just do it in line with Docker. >> No need to, no need to. We're providing it right there out of the box, ready for them. >> That's raise and extend, as they would say, build Microsoft strategy there. That's nice. Okay, so let's get back into like the secure trusted 'cause that was another theme at DockerCon. We covered that deeply. Software supply chain, I was commenting on my intro with Savannah and Lisa that at some point open source means so plentiful. You might not have to write code. You got to glue together. So as code proliferates, the question what's in there? >> That's right. This is what they call the software supply chain. You've been all over this. Where are we with this? Is it harder now? Is it easier? Was there progress? Take us through what's the state of the art. I think we're early on this one, John, in the industry because I think the realization of how much open source is inside a given app is just now hitting consciousness. And so the data we have is that for any given application, anywhere from 75 to 85% is actually not unique to the developer or the organization. It's open source components that they have put together. And it's really down to that last 15, 25%, which is their own unique code that they're adding on top of all this open source code. So right there, it's like, aha, that's a pretty interesting profile or distribution of value, which means those open source components, where are they finding them? How are they integrating them? How do they know those open source components are going to be supported and trusted and secured? And that's the challenge for us as an industry right now is to make it just obvious where to get the components, how safe they are, who's standing behind them, and how easy it is to assemble them into a working application. >> All right. So the question that I had specifically on security 'cause this had come up before. All good on the trusted and I think that message is evergreen. It's a north star. That's a north star for you. How are you making images more secure and how are you enabling organizations to identify security issues in containers? Can you share your strategy and thoughts on that particular point? >> Yes. So there's a range of things in the secure software supply chain and it starts with, are you starting with trusted open source components that you know have support, that you know are secured? So in Docker Hub today, we have 14 million applications, but a subset of that, we've worked with the upstream providers to basically designate as trusted open source content. So this is the Docker official images, Docker verified publisher images, Docker sponsored open source. And those different categories have levels of certification assurance that they must go through. Generate an SBOM, so you know what's inside that container. It has to be scanned by a scanning tool and those scanning results have to be made available. >> John: Are you guys scanning that? >> So we provide a scanner, they can use another scanner as long as they publish the results of that scan. And then the whole thing is signed. >> Are you publishing the results on your side too? >> Yeah, we published our results through an open database that's accessible to all. >> Free. >> Free, a hundred percent free. You come in and you can see every image on hub. >> So I'm a user, for free I can see security vulnerabilities that are out there that have been identified. >> By version, by layer, all the way through. And you can see tracking all the way back to the package that's upstream. So you know how to remediate and we provide recommendations on how to remediate that with the latest version. >> John: And you don't charge for that. >> We don't charge for that. We do not charge for that. And so that's the trusted upstream. >> So organization can look at the scan, they can look at the scan data and hopefully, what happens if they're not scanned? >> So we provide scanning tools both for the local environments for Docker Desktop, as well as for hub. So if you want to do your own scan, so for example, when you're that developer adding the 15, 25%, you got to scan your stuff as well. Not just leave it up to the already scanned components. And so we provide tools there. We also provide tools to track the packages that that developer might be including in their custom code, all the way back upstream to whatever MPM repo or what have you that they picked up. And then if there's a CVE 30 days later, we also track that as well. We say, Hey, that package was was safe 29 days ago, but today CVE just came out, better upgrade to the latest version and get that out there. So basically if you get down to it, it's like start with trusted components and then have observability not just on the moment. >> And scan all the time. >> Scan all the time and scanning gives you that observability and importantly not just at that moment, but through the lifecycle of the application, through lifecycle of the artifact. So end-to-end 24/7 observability of the state of your supply chain. That's what's key, John. >> That's the best practice. >> That's the key. That's the key. >> Awesome, I agree. That's great. Well, I'm glad we've dug into that's super important. Obviously organizations can get that scanning that's exceed the vulnerabilities, that can take action. That's going to be a big focus here for you, security. It's not going to stop, is it? >> It's never going to stop because criminals are incentive to keep attacking. And so it's the gift that keeps on giving, if you will. >> Okay, so let's get into some of the products. Docker Desktop seems to be doing well. Docker Hub has always been a staple of it. And how's that going? >> Yeah, Docker Hub has 18 million monthly actives hitting it and that's growing by double digits year over year. And what they're finding, going back to our previous thread, John, is that they're coming there for the trusted content. In fact, those three categories that I referenced earlier are about 2000 applications of the 14 million. And yet they represent 56% of the 15 billion downloads a month from Docker Hub. Meaning developers are identifying that, hey, I want trusted source. We raise those in the search results and we have a visual cue. And so that's the big driver of hub's growth right now, is I want trusted content, where do I go? I go to Hub, download that trusted open source and I'm ready to go. >> I have been seeing some chatter on the internet and some people's sharing that they're looking at other places, besides hub, to do some things. What's your message to folks out there around Docker Hub? Why Docker Hub and desktop together? 'Cause you mentioned the toolchain before, but those two areas, I know they've been around for a while, you continue to work on them. What's the message to the folks out there about stay with the hub? >> Sure. I mean the beauty of our ecosystem is that it's interoperable. The standards for build, share and run, we're all using them here at CNCF. So yes, there's other registries. What we would say is we have the 18 million monthly active that are pulling, we have the worldwide distribution that is 24/7 high, five nines reliability, and frankly, we're there to provide choice. And so yes, we have have our trusted content, but for example, the Tanzu apps, they also distribute through us. Red Hat applications also distribute through us because we have the reach and the distribution and offer developers choice of Dockers content, choice of Red Hats content, choice of VMware's, choice of Bitnami, so on so forth. So come to the hub for the distribution to reach and that the requirements we have for security that we put in place for our publishers, give users and publishers an extra degree of assurance. >> So the Docker Hub is an important part of the system? >> Scott: Yes, very much so. >> And desktop, what's new with desktop? >> So desktop of course is the other end of the spectrum. So if trusted components start up on Docker Hub, developers are pulling them down to the desktop to start assembling their application. And so the desktop gives that developer all the tools he or she needs to build that modern application. So you can have your build tooling, your debug tooling, your IDE sitting alongside there, your Docker run, your Docker compose up. And so the loop that we see happening is the dev will have a database they download from hub, a front-end, they'll add their code to it and they'll just rapidly iterate. They'll make a change, stand it up, do a unit test, and when they're satisfied do a git commit, off it goes into production. >> And your goal obviously is to have developers stay with Docker for their toolchain, their experience, make it their home base. >> And their trusted content. That's right. And the trusted content and the extensions are part of that. 'Cause the extensions provide complimentary tooling for that local experience. >> You guys have done an amazing job. I want to give you personal props. I've been following Docker from the beginning when they had the pivot, they sold the enterprise to Mirantis, went back to the roots, modernized, riding the wave. You guys are having a good time. I got to ask the question 'cause people always want to know 'cause open source is about transparency. How you guys making your money? Business is good. How's that work and what was the lucky, what was the not lucky strike, but what was the aha moment? What was the trigger that just made you just kick in this new monetization growth wave? >> So the monetization is per seat, per developer seat. And that changed in November 2019. We were pricing on the server side before, and as you said, we sold that off. And what changed is some of the trends we were talking about that the realization by all organizations that they had to become software companies. And Docker provided the productivity in an engineered desktop product and the trusted content, it provided the productivity safely to developers. And frankly then we priced it at a rate that is very reasonable from an economic standpoint. If you look at developer productivity, developers are paid anywhere from 150 to 300 to 400, 500,000 even higher. >> But when you're paying your developers that much, then productivity is a premium. And what we were asking for from companies from a licensing standpoint was really a modest relative to the making those developers product. >> It's not like Oracle. I mean talk about extracting the value out of the customer. But your point is your positioning is always stay quarter of the open source, but for companies that adopt the structural change to be developer first, a software company, there's a premium to pay because you devalue there. >> And need the tooling to roll it out at scales. So the companies are paying us. They're rolling it out to tens of thousand developers, John. So they need management, they need visibility, they need guardrails that are all around the desktop. So, but just to put a stat on it, so to your point about open source and the freemium wheel working, of our 13 million Docker accounts, 12 are free, about a million are paid for accounts. And that's by design because the open source. >> And you're not gouging developers per se, it's just, not gouging anyone, but you're not taking money out of their hands. It's the company. >> If the company is paying for their productivity so that they can build safely. >> More goodness more for the developer. >> That's right. That's right. >> Gouging would be more like the Oracle strategy. Don't comment. You don't need to comment. I keep saying that, but it's not like you're taxing. It's not a heavy. >> No, $5 a month, $9 a month, $24 a month depending on level. >> But I think the big aha to me and in my opinion is that you nailed the structural change culturally for a company. If they adopt the software ecosystem approach for transforming their business, they got to pay for it. So like a workflow, it's a developer. >> It's another tool. I mean, do they pay for their spreadsheet software? Do they pay for their back office ERP software? They do >> That's my point. >> to make those people popular or sorry, make those people successful, those employees successful. This is a developer tool to make developer successful. >> It's a great, great business model. Congratulations. What's next for you guys? What are you looking for? You just had your community events, you got DockerCon coming up next year. What's on the horizon for you? Put a plugin for the company. What are you looking for? Hiring? >> Yeah, so we're growing like gangbusters. We grew from 60 with the reset. We're now above 300 and we're continuing to grow despite this economic climate. Like our customers are very much investing in software capabilities. So that means they're investing in Docker. So we're looking for roles across the board, software engineers, product managers, designers, marketing, sales, customer success. So if you're interested, please reach out. The next year is going to be really interesting because we're bringing to market products that are doubling down on these areas, doubling down a developer productivity, doubling down on safety to make it even more just automatic that developers just build so they don't have to think about it. They don't need a new tool just to be safer. We hinted a bit about automating SBOM creation. You can see more of that pull through. And in particular, developers want to make the right decision. Everyone comes to work wanting to make the right decision. But what they often lack is context. They often lack like, well, is this bit of code safe or not? Or is this package that I just downloaded over here safe or not? And so you're going to see us roll out additional capabilities that give them very explicit contextual guidance of like, should you use this or not? Or here's a better version over here, a safer version over there. So stay tuned for some exciting stuff. >> It's going to be a massive developer growth wave coming even bigger we've ever seen. Final questions just while I got you here. Where do you see WebAssembly, Wasm going? If you had to throw a dart at the board out a couple years, what does it turn into? >> Yeah, so I think it's super exciting. Super exciting, John. And there's three use cases today. There's browser, there's edge, and there's service side in the data center of the cloud. We see the edge taking off in the next couple years. It's just such a straight line through from what they're doing today and the value that standing up a single service on the edge go. The service side needs some work on the Wasm runtime. The Wasm runtime is not multi-threaded today. And so there's some deep, deep technical work that's going on. The community's doing a fantastic job, but that'll take a while to play through. Browsers also making good progress. There's a component model that Wasm's working on that'll really ignite the industry. That is going to take another couple years as well. So I'd say let's start with the edge use case. Let's get everyone excited about that value proposition. And these other two use cases will come along. >> It'll all work itself out in the wash as open source always does. Scott Johnston, the Chief Executive Officer at Docker. Took over at the reset, kicking butt and taking names. Congratulations. You guys are doing great. Continue to power the developer movement. Thanks for coming on. >> John, thanks so much. Pleasure to be here. >> We're bringing you all the action here. Extracting the signal from the noise. I'm John Furrier, day one of three days of wall-to-wall live coverages. We'll be back for our next guest after this short break. (gentle music)

(upbeat music) >> Narrator: From around the globe, It's theCUBE with digital coverage of DockerCon live 2020 brought to you by Docker and its ecosystem partners. >> Hello, welcome back to our DockerCon 2020 DockerCon 20 coverage this is theCUBE virtual here in the Palo Alto studios with our quarantine crew, I'm John Furrier your host, got two great guests here. Scott Johnson is the CEO of Docker and Peter McKay CEO of Snyk hot security startup with some big news, you guys have rolled out, but really it's got an impact to developers. Scott and Peter great to see you guys again. >> Great to see John. >> Good to see you John. I'm glad we can at least talk remotely. I wish we were face to face, but obviously we're living in a time of crisis were you starting to see a Cambrian explosion starting to emerge where all people are recognizing that a lot is going to come out of this. You guys have announced a strategic alliance. Can you guys take a minute to explain what is this alliance and what does it mean ? Scott, we'll start with you. >> Absolutely, and thank you, Peter, thank you, John, for this chance to share with you all that's going on it's very exciting. Look, what we saw together as teams, both, both Peter's and ours was the developer experience is getting better and better in terms of faster and faster iterations but we weren't in the world of the Docker Desktop and Docker Hub experience having kind of scary as a first pass citizen that was really right in front and center with developer workflow. And so in working with Peter's team, we realized that the two companies had the same vision of like, let's bring that developer for security just right in center, in the user experience in the command line, in the tooling and just make it natural. So that developers could continue to iterate rapidly, continue to ship value, ship features fast. But in addition to doing that, do so in a secure fashion and in a secure manner. And really that's what this partnership is about is making security just kind of built in natural developer friendly developer first. We're very very excited to partner with Snyk and then bring this to development community. >> Peter, you guys have a unique business model, you're developer first security. What does this mean to you? Docker has got millions of developers out there who know containers, there's certainly developer first. What does this alliance mean to you guys as Snyk? >> Yeah, when you think of the developer community, you think of Docker, I mean, that's when we looked at the front end of our funnel, the people who we go after and our users, it's developers, and when you think developers, you think Docker and so we've got... Scott and I got together I'd say four or five months ago where we started talking about building a tighter relationship together the synergies between what he was doing and the team was doing, we're doing at Docker. And what we were trying to do is kind of embed the developer experience and develope and integrate security into that really made a very compelling value proposition together for developers and embedding that security into that application development into your containers and your image and your application development life cycle just made it a better developer experience overall. >> We've been talking to a lot of developers, certainly for DockerCon and just outside of the industry anecdotally, is that Docker really revolutionized, container ideas has been such a great win for developers. Containerizing applications really has changed the game, has spawned the generation of Kubernetes and cloud native microservices. What specifically is going on with you guys in this partnership? Where's the security fit in because can I just do a scan and scan the vulnerabilities? I mean, what's unique here? What does this mean for developers? What's going on with the alliance? >> Yeah, I'll take it first, Peter, but then jump in. So John, in the history of application development, so often security is not addressed until the end. And so developers they're shipping rapidly. They're they're iterating quickly, but then it gets, right before production and the alarm goes off and security team swoops in and security is often seen as a point of friction or a way to delay applications from getting the market and delivering value quickly. And this partnership completely reverses that where instead of having security be further down the stream of the tool chain or the application development life cycle, we're pulling it right up in front and having it be right alongside all the other activities that a developer is doing around building their code around, testing their code around, running their code locally. And it's the whole shift left I'm mean I'm sure you've seen out there and we are shifting this as far left it can be where it's right there on the local Docker Desktop in the command line as a primary emotion and its primary tool to building a great secure application as any other aspect of the tool chain. And that was really the focus of the partnership, which is like, make this just native and as far left as possible and not make security an afterthought or something that gets taken place by other Ops people downstream. >> Peter. >> If you think can about... That's the whole concept of how Snyk was founded. We all came from an application security background where it was security tools for security people, and it really... The whole industry needed this fundamental shift in the approach. And as Scott said that whole shifting left concept to really scale security in the right way and is to embed it into that application development life cycle into embedded into the tools that developers use each and every day. So they wanted to be a security expert, a developer doesn't need to be someone who knows all the vulnerabilities, they just need to know how to develop the most creative, indeed the most agile organization to develop, much better applications. And if they can do it in a more secure way they would obviously do it, but don't make them do something dramatically different and don't ask them to be security experts. And that's what we've tried to do in the partnership with Docker allows us to embed that continuous security insights into that whole development loop to when they develop these applications, they're secure when they're done and all the way through that development life cycle, you're testing for vulnerabilities in auto remediating along the way. So it allows them to develop very creative at the pace in which they want to develop. And it makes them more secure by doing it. >> Yeah, let me pick up on Peter's point there, which is so often security has been something that's discovered late in the process, right? Either just before production or sometimes even in production. And then just think about that feedback loop. It's got to go all the way back upstream all the way to the element team developers got to go find what they're working on. Well, maybe not hours ago, it could have been days ago could even be weeks ago and then both figure out how to remediate, get it all the way through the inner loop and the outer loop. We're completely blowing that up and disrupting that by bringing it all the way forward such that the feedback is right then and there with the developer in the moment on the laptop, in their inner loop and giving them the immediate response that they need and the single they need to take action remediate and then move on to the next creative thing they can do is they're just thinking about shortening that whole feedback loop. And really as Peter said, building security in from the get go because the signal is there to give them a indication of what they need to do right then and there. >> Great, I want to get into the... I mean, I can see the workflow advantage, so I totally get that. I've heard on theCUBE many times that security has got to be built in from the beginning. We've heard that before many times, I don't think I've heard security discussed this way, combined with the trends arounds automation. So can you guys talk about how that fits in? Because I get shifting left all that workflow, all goodness. But now I'm assuming there's a whole op side of security. And then if I'm trying to automate things and that's the real trend we're seeing here, how does that all work? Does that all come together? And it's this kind of unique that you guys are doing? Can you unpack that a little bit and clarify? >> Yeah, I mean, this has been something that we've been focused on quite a bit. I mean, the first it's... Used to be that you used to find a lot of vulnerability and yes we find a lot of vulnerabilities. And what we tried to do is focused on the prioritization and really hear the critical ones that developers need to fix first, second, third, and fourth based on severity. And we build that all in and that's something that we learned that we built into the process. And then last phase is this auto remediation. To the extent we can auto correct and auto fix, which is becoming increasingly a bigger part because the more you learn about the vulnerabilities in some of the fixes, the more you can automate and remediate that just makes the whole development process that much more productive and efficient. And that's really what we're trying to do, not only just find vulnerabilities, prioritize them, what are the ones that are what the team feels as severity one twos and threes embed that into the process. So you fix these are the ones you're fixing first, second, and third, into the extent they could be auto remediated, then fix them automatically. So we're trying to build that increasingly into the application. >> So, is this the first secure containerization deployment model? I mean, have other people have been doing this? I mean, is this new to Docker new to the industry? What's what's going on? >> Well, so we're here to talk about the partnership and of course there's a wealth of a very active ecosystem in and around security and other spaces. But we think this is the first that brings it this close to the developer in the moment in the command line on the desktop. And thus we think it has a lot of value to offer development team. >> I'll put my developer hat on. I'm one of the millions of developers, containers are part of my daily design coding, What's in it for me? Why does it matter to me as a developer? What does it do for me? Save time? What's the impact for the developer? >> Well, you think about... I mean, just look at the old model, right? The old model is you develop an application, you send it to the security team and they'll audit it. They'll tell you all the vulnerabilities and then they'll ship it back to you. You fix it, then they'll check it again. And they were waiting in the queue and then they'll tell you what's wrong and they'll send it back and think of that long. It's just like... Can you remember in the early day, when they a quality issue, fix it earlier in the life cycle of an application, don't wait till the end where the quality is embedded into the process. And so what you find is, the developers are embracing this and we have our like Docker, you have a freemium where developers can try it and realize that look, and I'm going to have to do security anyway, I mean, I have to develop secure application. If I can use a tool that's built for me and embedded into my development life cycle so I don't have to be a security expert and I don't have to wait for the security teams, to tell me what's wrong. And I can embed this all the way through and then not have to go through that painful step at the very end, to go through that security audit. I would do that any day of the week-- >> (mumbles) it back to you, do the scans, "Hey, you got to fix this." And then developer Scott your point moves on. They're coding, right? I mean, that's a problem. >> Developers want to ship, right? I mean, going back to your point, John, like one of the revolutions of Docker is that it is given the expectation that developers can ship faster. And right now in much of the state of the state, because security is important, like it can serve as a gate. And as Peter just walked you through it can slow down developer shipping and having impact. And so for you, the developer, John, like this gives you freedom to ship early often, high-frequency everything the promise of the container development model. This really unleashes that. >> Yeah 'cause that rails around the security policies too allows them to be projected in as syntax, if you will, or as part of the coding environment so I don't have to worry about it. I mean, at the end of the day, it's peace of mind, more than anything, time is certainly a pain in the butt, but yeah, as a developer, the creativity we needed more than ever. Okay, so with the COVID crisis-- >> One last point I want to make on that, sorry, it's also the security teams want it to because they don't want to be the bottleneck. They don't want to be doing this at the last minute and having all the pressure on them. I mean, they know that a big chunk of their business is going through these applications. So a lot of the budget dollars that come from people buying Snyk and embedding it into the process is from security because they can't keep up this digital transformation and what companies are going through. They don't want to be, there's one of two things. Either they're going to be the bottleneck or the developers are going to go around them and just put an application in the cloud in it and ship the container, put it anywhere then going around security. So they don't want that either. So there's just a very tight alignment between developers want to ship fast and security teams want to do the same. >> I hate to say it, but the whole agility is now not only just normal for us insiders in the industry. It's proven now with this COVID crisis that you have to be fast, you have to be at scale. And I think this speaks to some of the experiences you guys had in the industry, you were talking earlier. If you're not moving at the pace that you need to move at the scale you need the automation it's proven cloud native is going is completely ratified in my mind. There's no doubt, that means microservices is front and center and this change that's happening right now. And when we come out of this pandemic, there's going to be growth winners and not growth winners. We flat line to decline or winners, and it's all going to be based on microservices. So for the developers out there going to be called into the office as someday or in a Zoom, let's get these apps double down on this, kill that project. There's going to be those conversations >> It's happening right now, John. So look, what's happening, as a result of COVID an entire bodies of human activity are shifting from offline online. Like social, consumer, B2B, healthcare going down the list, finance, commerce, retail, like massive tectonic shift going from offline online. That means massive demand for new applications, new application development, and quickly, some this shift is happening and there's a bunch of businesses that didn't have exposure to digital they're like, "Oh my goodness, I need a digital strategy. "I need a digital channel. "I need a digital revenue stream." And so the demand for new applications quickly is exploding through the roof. And we see this across the board in our industry right now which is very, very fortunate given the other circumstances and other industries, but you're absolutely right. Like this lets them ship faster. And now is the time when they need to ship and ship fast. >> And the budgets are going to be allocated on these new projects was just a nuance in your point, it's new projects and then there's fixing modernizing the old stuff. Because look at Walmart, Walmart got hamstrung on the eCommerce side, they just killed their jet acquisition. They spent $3 billion on, this is the reality. This is not like just a strategy to do innovation, innovation strategy or some walk down, digital transformation lane. This is happening, it has to be done. What do they do? >> Its interesting and it starts, we always say, we start with the new and replaced the old. We start with a new application, it usually is always the case where we usually start with a lot of the companies is a new (mumbles) on application. And then it expands from there. And so know you look at what you used to be the best practices were tech companies, and then it moved to financial services, industries and insurance and then in retail, now you look at manufacturing, you look across the board, as Scott said, this offline to online, is driving so much of the empowering developers to take on more responsibility and to own more of it, but to be faster and to be more agile. And that's really, what's driving this big shifts in the market. And like you said earlier, if they're not there, they're in trouble because this market is driving that direction. >> I want to get both of your comments on this final question, because even with the progression of the developers from the Steve bomber developer development developers, speech on YouTube to developers on the front lines, cloud native, and now today it's been a progression. And I think it's always been the developers on the front lines are getting closer to the front lines. I think now it's even more compelling because there's a scale and agility speed game going on. So I think it's just another step function, developer relevance. It's not so much, they've never been close to, they have been getting closer they're in the business conversation and the ones that could move fast are the ones going to deliver the value. So if automation is in the playbook, if cloud need is not in the playbook, this is going to be the new developer equation, the ones that meet that will be successful. Can you guys react to that and your thoughts? >> Go ahead Peter. >> I mean, I think what we're trying to do is make that developer experience just one from just the partnership with Docker and is a key, just making it really easy, do the integration, do a lot of the work, make the developer experience as seamless as possible, make it very efficient for them, make it easy for them to try and buy, make it just a great experience and allow them to, or empower them to take on more of the responsibility of getting that App published and in the containers out the door. And that's what we're excited about with the partnership with Docker is that with the number of developers that they have, the work that we do together, and the roadmap that we have is really making that experience just an incredible journey for our developer and that's what we want to continue to make sure we foster. >> Scott, the new relevance of developers, your thoughts. >> Yeah, I would only--building on Peter's point, observed that a lot of the developer expectations are informed by the stack and what's possible. And to your points earlier about the previous waves, John, like, developers are important, but their full potential if you will was perhaps muted or gated because there was not a clean abstraction between the application on the underlying infrastructure. And now, as we know, Dockerization and the surrounding ecosystem of Kubernetes and other tools, we have a much cleaner separation between the Application and the infrastructure, and that allows and set expectations for a much higher cadence of release much faster, time to value, much more agile operations in terms of responding to competitors and the market and your customers. And so with that expectation, how do you unleash that? And this partnership is really key to that, by taking the friction out. As we talked about kind of historical security models and bringing a new model that bring the security way left right into the developers around that experience. And then in some sense, really fulfills that ability to move quickly, react in an agile fashion and have an impact as quickly as possible. >> That's awesome security built into the workflow, automated industry first, guys thanks so much for a great partnership, but the final work at the plugin for the relationship going forward, how's that work is going to be available is integration code is it development? Give a quick plug for what's happening, the relationship and what's happening going forward? >> Look, Docker only succeeds if the ecosystem succeeds. and we're very very proud and humbled to join arms with Peter and the Snyk team as a partner in the security ecosystem. And so you'll see us not only in this integrated developer experience on the command line, which is going to be very, very valuable to developers that we've been talking about, but you'll see us out there promoting the solution in different forms and community groups. And so it doesn't stop and end with the DockerCon experience, look for us in the year ahead to do more and more together. >> Awesome. >> I agree and I think that just culturally and the way the organizations work really well together, I think this is a beginning of a longer journey and a longer partnership we're going to have together with Scott and the team, so we're excited. I think the validation, the early validation we've got from the development teams that we've been talking to around the world, I think there's tremendous desire for this to happen, and we're excited to launch the journey together, with Scott and team. >> It's been a lot of fun watching this progression, like you said, create that headroom, the developable, we'll take it right up and there'll be another step function, more progression. Great job guys. Congratulations on the great partnership >> We need to security built in, we need more creativity. We need that, we need this new modern era to be flourishing. Thanks for your time, appreciate it. >> Thanks John. >> Thank you. >> theCUBE coverage, virtual CUBE coverage of DockerCon 20. I'm John Furrier your host, along with Docker for DockerCon 20 #Docker 20. Thanks for watching and stay tuned for our next segment of DockerCon 20 virtual. (upbeat music)

>> 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 around the globe. It's the view with digital coverage of Docker con live 2020 brought to you by Docker and its ecosystem partners. >>LeBron. Welcome back to DockerCon 2020 hashtag Docker 20 this is the cube and Dockers coverage of Docker con 20 I'm Sean for you and the Palo Alto studios with our quarantine crew. We've got a great interview segment here in 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 the cube. >>Thanks for having me. >>Amanda, tell us a bit about what your role is at Microsoft. You guys are well known in the developer community to develop an ecosystem when even when I was in college going way back, very modern. Now cloud is, is the key code to cloud. That's the theme. Tell us about your role at Microsoft. >>Yeah. So I basically run the product, uh, product design and user research team that works on our developer tools that Microsoft and so that includes the visual studio product as well as visual studio code. Um, that's become pretty popular in the last few years, but it also includes things like the.net runtime and the TypeScript programming language as well as all of our Azure tooling. >>What's your thoughts on the relationship with Docker? I'll show you the news extension of an existing relationship. Microsoft's got a lot of tools. You've got a lot of things you guys are doing, bringing the cloud to every business. Tell us about your thoughts on this relationship with Donker. >>Yeah, well we're very excited about the partnership for sure. Um, you know, 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. Uh, we really see a unique opportunity to make the experience really great for Docker, for the Docker community by creating more integrated and seamless experience across Docker, desktop windows and visual studio. And we really appreciate how, how Docker is kind of, you know, supported our windows ecosystem to run in Docker as well. >>Scott, this relationship and an extension with Microsoft is really, uh, I think impressive and also notable because Microsoft's got so many, 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 reflective of the new Docker. Uh, could 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's 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 us. The reality that developers love voice and no one's gonna change their minds on choice. And third is just acknowledging that there's so much creativity and so much energy. The four walls of Docker that we'd be building, not the big advantage of that and welcome it and embrace it and provide that as a phenomenal experience part of Alfred's. So this is a great example of that. The sneak partnership we announced last week is a grant to have that and you're going to see many more of uh, partnerships like this going forward that are reflective of exactly this point. >>You've been a visionary on the product side of the 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, right? Because developers want to focus on their app. They don't want to focus on duct taping and springing together different siloed pools, right? So you can see in the demo and you'll see in, uh, demonstrations later throughout the conference. Just the seamless experience that a developer gets in the document man line inter-operating with visual studio code with the Docker command line and then deploying to Azure and what's 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 the figuration around default settings around uh, security, user management, all of that is abstracted out and taken away from the developer so they can focus on applications and getting those applications deployed to the proudest quickly as possible. Getting their app from code to cloud is the wok word or the or the call to action for this partnership. And we think we really hit it out of the park with the integration that you saw, >>Great validation and a critical part of the workflow. You guys have been part of Amanda, we're living in a time we're doing these remote interviews. The coven crisis has shown the productivity gains of working at home and working in sheltering in place, but also as highlighted, the focus of developers mainly who have also worked at home. They've kind of used to this. Do you see the rigs? I saw her at Microsoft build some amazing rigs from the studio. So these guys streaming their code demos. This is, um, a Cambrin explosion of new kinds of productivity. And yet the world's getting more complex at scale. This is what cloud does. What's your thoughts on this? Cause the tooling is more tools than ever, right? So I still gotta deploy code. It's gotta be more agile. It's gotta be faster. It's gotta 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, don't you still got to do their job? >>Yeah, well, absolutely. And now, even more than ever. I mean, I think we've, we've certainly seen over the past few months, uh, uh, a more rapid acceleration of digital transformation. And it's really happened in the past few years. Uh, you know, paper processes are now becoming digit digital processes. All of a sudden, you know, 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 lifestyle. Um, but even more so, you know, we now have remote development teams actually working from home as well in a variety of different kinds of, uh, environments. Whether they're using their own personal machine to connect to their infrastructure or they're using a work issued machine. You know, it's more important than ever that developers are productive, but they are productive as a team. Right? 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, uh, what Docker really enables is, uh, with, with containerization is to make the infrastructure consistent and repeatable so that as developers are moving through the life cycle from their local, local dev desktop and developing on their local desktop to a test environment and to staging and to production, it's really, it's infrastructure of or, or developers as well as operations. And so it's that, that infrastructure that's completely customizable for what the developer's operating system of choices, 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, really fast iteration cycle but also to have that consistency across all of their development team. And you know, we, we now need to think about things like how are we actually going to bring on interns for the summer, uh, 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 helped with that >>As your container instances and a visual studio cloud that you guys have has had great success. Um, there's a mix and match formula here. At the end of the 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 on the front lines and they're shipping in real time, this is a big part of the value proposition that you guys are bringing to the table. >>Yeah, I mean the, the core message is that any developer and their code is welcome, uh, and that we really want to support them and power them and increase their velocity and the impact that they can have. Um, and so, you know, having things like the fact that the Docker CLI is natively integrated into the Azure experience, uh, is a really important aspect of making sure that developers are feeling welcome and feeling comfortable. Um, and now that the Docker CLI tools are, that are part of Docker desktop, have access to native commands that work well with Azure container instances. Uh, Azure container instances, if anybody's on familiar with that, uh, is the simplest and fastest way to kind of set up containers and Azure. And, 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 that really consistent experience across our service services and our tools and 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, we've integrated these as a design point since very early on in our partnership when we've been partnering with, with Docker for quite a while. >>Amanda, I want to ask you about the, the, the, 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? Uh, every day developer out there? >>Um, I, I mean, I really think it means you know, your productivity on your terms. Um, and so, you know, Microsoft has been a developer company since the very, very beginning with, you know, bill Gates and, and, uh, GW basic. Um, and it's actually similar for Docker, right? They really have a developer first point of view, uh, which certainly speaks to my heart. And so one of the things that we're really trying to do with, 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.net and C-sharp or Java. Uh, we really want to make sure that we have a super simple experience that you can actually initiate all of these commands, create, you know, Docker container images and use the compose Docker compose files. >>Um, and then, you know, 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. Um, so we, 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, you know, we really want you to be able to look at containers up in the Azure. Uh, up that are deployed into Azure and make sure that they're running and healthy and that if there, 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 when to see environment variables or other details. >>Yeah, that's awesome. You know, writing code, managing code, and then you've got to deploy, right? So what I've been loving about the, the past generation of agile is deployment's been fast to deploy all the time. Scott, this brings up that the ease of use, but you want to actually leverage automation. This is the trend that you want to get in. You want, you don't want, 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? >>So that was a big part of this partnership, John, that the Docker in Microsoft embarked on and as you saw from the demo and the keynote, um, all within the man line, the developers able to do in two simple commands, deploy an app, uh, defining compose from the 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 that took a lot of hardcore engineering work on part of Docker and Microsoft together to simplify that and make that easy and that, that goes exactly to your point. We just like the simpler you can make it more, you can abstract a way to kind of underlying plumbing and infrastructure. The faster devs can get there. Their application from code to cloud. >>Scott, you've been a product CEO, you've been a product person, a CEO, but you have a product background. You've been involved with the relationship with Microsoft for a long time. What's the state of the market right now? I mean, obviously Microsoft has evolved. Look at 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 on developers to do more and more, 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's might not be known to everyone on today's, uh, day's event. But Microsoft came to the very first Docker con event, uh, way back in June, 2014 and I had the privilege of, of reading them and welcoming them and they're, they were full on ready to see what all the excitement about Docker was about and really embrace it. And you mentioned kind of openness and Microsoft's growth over that, uh, over time in that dimension. And we think kind of Docker together with Microsoft have really shown what an open developer community can do. And 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 of a sudden the promise of right ones and use the same primitives, the same formats, the same fan lines, uh, 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 of open standards based, developer facing friendliness, ease of use, fast time to deploy. And this, 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, it's 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, 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 like the one we've announced >>Yesterday and highlighted, you know, but >>Uh, make it just easy for development teams to choose their tools and build their apps and deploy them onto Azure. It's possible. So, uh, it's, it's a phenomenal plan, one for developers and we're very excited and proud of partner with Microsoft on it. >>Amanda, on your side, I see DACA has got millions of developers. You guys got millions of developers even more. How do you see the developers in Microsoft side engaging with Docker desktop and Docker hub? Where does it all fit? >>I think it's a great question. I mean, I mentioned earlier how the Docker context can help individuals and teams kind of work in their environments work. Let me try that over. I mentioned earlier how I, how I see Docker context really improving the way that individuals and teams work with their environments and making sure that they're consistent. But I think this really comes together as we work with Docker desktop and Docker hub. Uh, when developers sign into 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 they're running them in. And so, you know, once you sign into the hub, you can see all the contexts that map to the logical environments that they have access to like dev and QA and maybe staging. And another use case that's really important is that, you know, we can access the same integration environment. >>So, so I could have, you know, microservices that I've been working on, but I can also see microservices that my, my teammates and their logs, uh, from the services that they've been working on, which I think is really, really great and certainly helps with, with team productivity. The other thing too is that this also really helps with hybrid cloud deployments, right? Where, you know, you might have some on premises, uh, hosted containers and you might have some that's hosted in a public cloud. And so you can see all of those things, uh, through your Docker hub. >>Well, I got to say I love the code to cloud tagline. I think that's very relevant and, and catchy. Um, and I think, I guess to me what I'm seeing, and I'd love to get your thoughts, Amanda, on this, as 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 tense and anxiety with the covert 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 and you've seen these ways before, but now in this time, what are you most excited about? What are you optimist about? What's your view on the opportunities? Can you share your thoughts? Because people are going to get back to work or they're working now remotely, but when we go back to hybrid world, they're going to be jamming on projects. >>Yeah, for sure. But I mean, people are jamming on projects right now. And I think that, you know, in a lot of ways, uh, developers are our first responders in, you know, in that they are, developers are always trying to support somebody else, right? We're trying to somebody else's workflow and you know, so we have examples of people who are, uh, creating new remote systems to be able to, uh, schedule meetings in hospitals or the doctors who are actually the first, first responders taking care of patients. But at the end of the day, it's the developer who's actually creating that solution, right? And so we're being called the duty right now. Um, and so we need to make sure that we're actually there to support the needs of our users and that we're, we're basically cranking on code as fast as we can. Uh, 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 freely. And so, uh, I think that, you know, 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 amazing insight. And I think that's, you know, the current situation in the community matters because there's a lot of um, frontline work being done to your point. But then we've 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 comradery going on and massive community involvement. I'm seeing more of, you know, 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, right? Um, and we're going to build our way out of this. Um, and it is the community that's responding. And so in some sense, Microsoft and Docker are there to support that, that community energy and give them the tools to go. And identify and have an impact as quickly as possible. We have referenced in the keynote, um, completely bottoms up organic adoption of Docker desktop and Docker hub in racing to provide solutions against the COBIT 19 virus. Right? It's a, 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 uh, cools and containers and data analysis all in service to the photo at 19 battle that's being fought. And then as you said, John, as we, as we get through this, the other side, there's entire industries that are completely rethinking their approach that were largely offline before that. 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 go on 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. You know, I'm a big fan of from day one. I know you guys have pivoted on a new trajectory which is 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 from some, some, some uh, data for the folks that aren't in the community or might want to join with folks in the community who want to get an update? >>Yeah, it's a, it's a great, great kind of question. I mean, you know, 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 uh, and learning to create, you know, digital solutions overall. There's a massive developer shortage across the world. Um, there's so much opportunity for developers to kind of, you know, address a lot of the needs that we're seeing out of organizations again across the world. Um, and so I think it's just a really exciting time to be a developer. Uh, and you know, my, my uh, my only hope is that basically we're, we're building tools that actually enable them to solve problems. >>Awesome insight and thank you so much for your time code to cloud developers are cranking away that the first responders are 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. Okay. This is the cubes coverage. We are Docker con 2020 digital is the cube virtual. I'm Sean for bringing all the action. More coverage. Stay with us for more Docker con virtual. After this short break.

>> Live from San Francisco, it's theCUBE, covering DockerCon '18, brought to you by Docker and it's ecosystem partners. >> Welcome back to theCUBE, we are live at DockerCon 2018 in San Francisco on a spectacular day. I am Lisa Martin with my with my co-host for the day, John Troyer, and we're very pleased to welcome back to theCUBE a distinguished CUBE alumni and Docker veteran, Steve Johnston, Chief Product Officer at Docker. Welcome back. >> Thank you, thank you very much. That's Scott Johnston but that's okay. >> What did I say? Steve? >> Steve. That's okay. >> Oh, I gave you a new name. >> You know, I get that all the time. >> I'm sorry, Scott. >> That's alright. >> This event, between five and six thousand people. >> Yes. >> You were saying in your general session in keynote this morning, that this is the fifth DockerCon. You started a few years ago with just 300 people and when I was walking out of the keynote this morning, I took a photograph, incredible. People as far as the eye can see. It was literally standing room only. >> It's crazy, right? And you think about four years ago, June 2014 when we did our very first DockerCon, here in San Francisco, 300 people, right? And we've gone from 300 to over 5,000 in that time, grown the community, grown the products, grown the partnerships and it's just, it's very humbling, honestly, to be part of something that's literally industry changing. >> You gave some great numbers during your keynote. You talked about 500 customers using Docker Enterprise Edition. >> Yes. >> Some big names. >> Yes. >> MET Life, Visa, PayPal, McKesson, who was on stage and that was a really interesting. McKesson is what, 183 years old? >> Healthcare company, yeah. >> Talking about data, life and death type of data. >> Right. >> Their transformation working with Docker and containers was really pretty impressive. >> It's exciting that companies get their hands on the technology and they start maybe on a small project or a small team but very quickly they see the potential impact of the solution and very quickly, it's almost infectious inside the organization and more and more teams want to jump on, understand how they can use it to help with their applications, their business to get impact in their operations and it just spreads, spreads like wildflower. That was really the story that McKesson was sharing, just how quickly they were seeing the adoption throughout their org. >> I thought that was really interesting and they did point it out on stage, how that developer adoption did help them go to the next level. >> Yes. >> And kind of transform their whole pipeline. >> Yes. >> Now Scott, you've been here the whole line of time and that through line has been, for Docker, that developer experience. >> That's exactly right. >> Now, as Product Lead here, you've got the Docker Desktop side and the Docker EE side and it's clear, there were some great announcements about desktop here, previews today but how do you balance the enterprise side with the developer centric desktop side and that developer experience idea? >> No, it's a great question, John. I'd reshape it almost to say, it's a continuous platform from developer experience to the operation side and you have to stand back and kind of see it as one and less about trading off one versus the other and how do you create an experience that carries all the way through. So a lot of Gareth's demonstration and the Lily Mason play, was showing how you can create apps in Docker very easily as a developer but those same artifacts that they put their apps in to carry all the way through into production, all the way through into operations. So it's about providing a consistent user experience, consistent set of artifacts that can be used by all the different personas that are building software so that they can be successful moving these Docker applications through the entire application development life cycle. Does that make sense? >> It does, thank you. I'd love to get your perspective, when you're talking with enterprises who might have some trepidation about the container journey, they probably know they have to do it to stay agile and competitive. I think in the press release, I believe it was you, that was quoted saying, "An estimated 85% of enterprise organizations are in a multi Cloud world." >> That's right. >> In a multi Cloud strategy. >> That's right. >> So when you're talking with customers, what's that executive conversation like? C level to C level, what are some of the main concerns that you hear and how influential are the developers in that C suite saying, "Hey guys, we've got to go this direction"? >> No, that's right. That's a great question, Lisa and what we hear again, and again, and again, is a realization going on in the C suite, that having software capabilities is strategic to their business, right? That was not always the case, as much as a decade ago, as recently as a decade ago, inside kind of big manufacturing businesses or big verticals that weren't kind of tech first, IT was a back office, right? It was not front and center but now they're seeing the disruption that software can have in other verticals and they're saying, "Wait a minute, we need to make software capabilities a core capability in our business." And who starts that whole cycle? It's the developers, right? If the developers can integrate with the lines of business, understand their objectives, understand how software can help them achieve those objectives, that's where it kicks off the whole process of, "Okay, we're going to build competitive applications. We then need an operations team to manage and deploy those applications to help us deploy them in a competitive way by taking them to the Cloud." So developers are absolutely pivotal in that conversation and core to helping these very large, Fortune 500, hundred year old companies, transform into new, agile, software driven businesses. >> Modernizing enterprise apps has been a theme >> Yes. >> also at Docker for a few years now. >> Yup. >> Up on stage Microsoft demonstrating the results of a multiyear partnership >> That's right. >> between Microsoft and Docker both with Docker integrating well with Windows server as well as, you talked about, Kubernetes now. >> That's right. >> Can you talk a little bit about what the implications of this are? The demo on stage, of course, was a very old enterprise app written in dot net, with just a few clicks, up and running in the Cloud on Kubernetes no less. >> That's right. >> Managed by Docker, that's actually very cool. You want to talk a little bit about, again, your conversations? >> Absolutely. >> Is this all about Cloud native or how much of your conversations are also supporting enterprise apps? >> Tying back to Lisa's question, so how do we help these organizations get started on their transformation? So they realize they need to transform, where do you start? Well guess what? 90% of their IT budget right now is going into these legacy applications and these legacy infrastructures, so if you start there and it can help modernize what they already have and bring it to modern platforms like Docker and Kubernetes, modern platforms like Window Server 2016, it's a modern operating system, modern platforms like Clouds, that's where you can create a lot of value out of existing application assets, reduce your costs, make these apps agile, even though they're thirteen years old and it's a way for the organization to start to get comfortable with the technology, to adopt it in a surface area that's very well known, to see results very, very quickly and then they gain the confidence to then spread it further into new applications, to spread it further into IOT, to spread it further into big data. But you've got to start it somewhere, right? So the MTA, Modernized Traditional Apps, is a very practical, pragmatic but also high, very quick, return way to get started. >> Oh, go ahead. >> Well I just, the other big announcement involving Kubernetes was managing Kubernetes in the Cloud and I wanted to make sure we hit that. >> That's right, that's right. >> Because I think if people aren't paying attention, they're just going to hear multi Cloud and they're going to go on and say, "Well everybody does multi Cloud, Docker's no different, Docker's just kind of catching up." Actually, this tech preview, I think, is a step forward. I think it's something- >> Thank you. >> I haven't actually seen in practice, so I'm kind of curious, again, how you as an engineering leader make those trade offs. Kind of talk a little bit about what you did and how deciding, "Well there's multi Cloud but the devil's in the details." You actually have integrated now with the native Kubernetes in these three Clouds, EKS, AKS and GKE. >> GKE, no that's right. No, it's a great question, John. The wonderful and fascinating but double edged sword of technology is that the race is always moving the abstraction up, right? You're always moving the abstraction up and you're always having to stay ahead and find where you can create real value for your customers. There was two factors that were going on, that you saw us kind of lean in to that and realize there's an opportunity here. One is, the Cloud providers are doing a wonderful job investing in Kubernetes and making it a manage service on their platforms, great. Now, let's take advantage of that because that's a horizontal infrastructure piece. At parallel we were seeing customers want to take advantage of these different Clouds but getting frustrated that every time they went to a different Cloud they were setting up another stack of process and tooling and automation and management and they're like, "Wait a minute. This is going to slow us down if we have to maintain these stacks." So we leaned in to that and said, "Okay, great. Let's take advantage of commoditized infrastructure, hosting Kubernetes. Let's also then take advantage of our ability to ingest and onboard them into Docker Enterprise Edition, and provide a consistent experience user based APIs, so that the enterprise doesn't get tied into these individual silos of tools, processes and stacks." Really, it's the combination of those two that you see a product opportunity emerged that we leaned heavily into and you saw the fruits of this morning. >> I saw a stat on the docker.com website that said that customers migrating to EE containers can reduce total cost by around 50%? >> Yes. >> That's a significant number. >> It's huge, right? You're reducing your cost of maintaining a ten year old app by 50% and you've made it Cloud portable, and you've made it more secure by putting it in the Docker container than outside and so it's like, "Why wouldn't you invest in that?" It shows a way to get comfortable with the technology, free up some cashflow that then you can pour back into additional innovation, so it's really a wonderful formula. That again, is why we start a lot of customers with their legacy applications because it has these types of benefits that gets them going in other parts of their business. >> And as you mentioned, 90% of an enterprise IT budget is spent keeping the lights on. >> That's right. >> Which means 10% for innovation and as we've talked about before, John, it's the aggressively innovating organizations that are the winners. >> That's exactly right and we're giving them tools, we're giving them a road map even, on how they can become an aggressively innovating organization. >> What about the visibility, in terms of, you know, an organization that's got eight different IT platforms, on prem, public Cloud, hybrid- >> Right. >> What are you doing with respect to being able to deliver visibility across containers and multiple clusters? >> That's right. Well that's a big part of today's announcement, was being able ... Every time we ingest one of these clusters, whether it's on prem, whether it's in the Cloud, whether it's a hosted Kubernetes cluster, that gives us that visibility of now we can manage applications across that, we can aggregate the logging, aggregate the monitoring. You can see, are your apps up, down, are they running out of resources? Do you need to load balance them to another cluster? So it's very much aligned with the vision that we shared on stage, which is fully federated management of the applications across clusters which includes visibility and all the tools necessary for that. >> Scott, I wanted to ask about culture and engineering culture >> Thank you. >> The DockerCon here is very, I think we called it humane in our intro, right? There's childcare on site, there's spoustivities, there's other places to take care of the people who are here and give them a great experience and a lot of training, of course, and things like that. But internally, engineering, there's a war for talent. Docker is very small compared to the Googles of the world but yet you have a very ambitious agenda. The theme of choice today, CLI versus GUI, Kubernetes versus Swarm, Lennox and Windows, not versus, Lennox and Windows, you know and, and, and, and now all these different Clouds and on prem. That's very ambitious and each "and" there takes engineering resources, so I'm kind of curious how the engineering team is growing, how you want to build the culture internally and how you use that to attract the right people? >> Well it certainly helps to be the start up that kicked off this entire movement, right? So a lot of credit to Solomon Hykes, our founder, and the original crew that ... Docker was a Skunkworks project in the previous version of our company and they had the vision to bring it forward and bring it to the world in an opensource model which at the time was a brand new language, go language. That was a catalyst that really got the company off and running in 2013/2014. We're staying true to that in that there's still a very strong opensource culture in the company and that attracts a lot of talent, as well as continuing to balance enterprise features and innovation and you see a combination of that on stage. You're also going to see a wonderful combination of that on the show floor, both from our own employees but also from the community. And I think that's the third dimension, John, which is being humble and call it "aware" that innovation doesn't just come from inside our four walls but that we give our engineers license to bring things in from the outside that add value to their projects. The Kubernetes is a great example of that, right? Our team saw the need for orchestration, we had our own IP in the form of Swarm, but they saw the capabilities of Kubernetes is very complimentary to that, or some customers were preferring to deploy that. So, no ifs, ands or buts, let's take advantage of that innovation, bring it inside the four walls and go. So, it's that kind of flexibility and awareness to attract great engineers who want to work on cutting edge, industry building technologies but also who are aware enough of, there's exciting things happening outside with the community and partnering with that community to bring those into the platform as well. >> So Scott, you guys are doing a lot of collaboration internally, but you're also doing a lot of collaboration with customers. How influential are customers to the development of Docker technologies? >> At ground zero, literally and we have at DockerCon, we call it a customer advisor group, where the customers who have been with us, who have deployed with us in production, we have them. And it's a very select group, it's about twelve to sixteen, and they tell us straight talk in terms of where it's working, where we need to improve. They give us feedback on the road map and so that happens every DockerCon, so that's once every six months. But then we actually have targets inside engineering and product management to be out in the field on a regular basis to make sure we're continuing to get that customer feedback. Innovation's a tricky balance, right? Because you want to be out in front and go where folks aren't asking you to, but you know there's opportunity, at the same time here, where they are today, and make sure you're not getting too far ahead. It's the old joke, Henry Ford, where if he's just listened to his customers, he would have made faster horses but instead he was listening to their problems, their real problems which was transportation and his genius, or his innovation, was to give them the Model T, right? We're trying to balance that ourselves inside Docker. Listen to customers but also know where the innovation, where the technology can take you to give you new solutions, hopefully many of which you saw on stage today. >> We did, well Scott, thanks so much for stopping by theCUBE again and sharing some of the exciting announcements that Docker has made and what you're doing to innovate internally and for the external enterprise community. We appreciate your time. >> Thank you, Lisa. Thank you, John. >> We want to thank you for watching theCUBE. Again, Lisa Martin with John Troyer, live in San Francisco at DockerCon 2018. Stick around, John and I will be right back with our next guest. (upbeat techno music)

(bright upbeat music) >> Greetings, brilliant community and thank you so much for tuning in to theCUBE here for the last three days where we've been live from Detroit, Michigan. I've had the pleasure of spending this week with Lisa Martin and John Furrier. Thank you both so much for hanging out, for inviting me into the CUBE family. It's our first show together, it's been wonderful. >> Thank you. >> You nailed it. >> Oh thanks, sweetheart. >> Great job. Great job team, well done. Free wall to wall coverage, it's what we do. We stay till everyone else-- >> Savannah: 100 percent. >> Everyone else leaves, till they pull the plug. >> Lisa: Till they turn the lights out. We're still there. >> Literally. >> Literally last night. >> Still broadcasting. >> Whatever takes to get the stories and get 'em out there at scale. >> Yeah. >> Great time. >> 33. 33 different segments too. Very impressive. John, I'm curious, you're a trend watcher and you've been at every single KubeCon. >> Yep. >> What are the trends this year? Give us the breakdown. >> I think CNCF does this, it's a hard job to balance all the stakeholders. So one, congratulations to the CNCF for another great KubeCon and CloudNativeCon. It is really hard to balance bringing in the experts who, as time goes by, seven years we've been all of, as you said, you get experts, you get seniority, and people who can be mentors, 60% new people. You have vendors who are sponsoring and there's always people complaining and bitching and moaning. They want this, they want that. It's always hard and they always do a good job of balancing it. We're lucky that we get to scale the stories with CUBE and that's been great. We had some great stories here, but it's a great community and again, they're inclusive. As I've said before, we've talked about it. This year though is an inflection point in my opinion, because you're seeing the developer ecosystem growing so fast. It's global. You're seeing events pop up, you're seeing derivative events. CNCF is at the center point and they have to maintain the culture of developer experts, maintainers, while balancing the newbies. And that's going to be >> Savannah: Mm-hmm. really hard. And they've done a great job. We had a great conversation with them. So great job. And I think it's going to continue. I think the attendance metric is a little bit of a false positive. There's a lot of online people who didn't come to Detroit this year. And I think maybe the combination of the venue, the city, or just Covid preferences may not look good on paper, on the numbers 'cause it's not a major step up in attendance. It's still bigger, but the community, I think, is going to continue to grow. I'm bullish on it. >> Yeah, I mean at least we did see double the number of people that we had in Los Angeles. Very curious. I think Amsterdam, where we'll be next with CNCF in the spring, in April. I think that's actually going to be a better pulse check. We'll be in Europe, we'll see what's going on. >> John: Totally. >> I mean, who doesn't like Amsterdam in the springtime? Lisa, what have been some of your observations? >> Oh, so many observations. The evolution of the conference, the hallway track conversations really shifting towards adjusting to the enterprise. The enterprise momentum that we saw here as well. We had on the show, Ford. >> Savannah: Yes. We had MassMutual, we had ING, that was today. Home Depot is here. We are seeing all these big companies that we know and love, become software companies right before our eyes. >> Yeah. Well, and I think we forget that software powers our entire world. And so of course they're going to have to be here. So much running on Kubernetes. It's on-prem, it's at the edge, it's everywhere. It's exciting. Woo, I'm excited. John, what do you think is the number one story? This is your question. I love asking you this question. What is the number one story out KubeCon? >> Well, I think the top story is a combination of two things. One is the evolution of Cloud Native. We're starting to see web assembly. That's a big hyped up area. It got a lot of attention. >> Savannah: Yeah. That's kind of teething out the future. >> Savannah: Rightfully so. The future of this kind of lightweight. You got the heavy duty VMs, you got Kubernetes and containers, and now this web assembly, shows a trajectory of apps, server-like environment. And then the big story is security. Software supply chain is, to me, was the number one consistent theme. At almost all the interviews, in the containers, and the workflows, >> Savannah: Very hot. software supply chain is real. The CD Foundation mentioned >> Savannah: Mm-hmm. >> they had 16,000 vulnerabilities identified in their code base. They were going to automate that. So again, >> Savannah: That was wild. >> That's the top story. The growth of open source exposes potential vulnerabilities with security. So software supply chain gets my vote. >> Did you hear anything that surprised you? You guys did this great preview of what you thought we were going to hear and see and feel and touch at KubeCon, CloudNativeCon 2022. You talked about, for example, the, you know, healthcare financial services being early adopters of this. Anything surprise either one of you in terms of what you predicted versus what we saw? Savannah, let's start with you. >> You know what really surprised me, and this is ironic, so I'm a community gal by trade. But I was really just impressed by the energy that everyone brought here and the desire to help. The thing about the open source community that always strikes me is, I mean 187 different countries participating. You've got, I believe it's something like 175,000 people contributing to the 140 projects plus that CNCF is working on. But that culture of collaboration extends far beyond just the CNCF projects. Everyone here is keen to help each other. We had the conversation just before about the teaching and the learnings that are going on here. They brought in Detroit's students to come and learn, which is just the most heartwarming story out of this entire thing. And I think it's just the authenticity of everyone in this community and their passion. Even though I know it's here, it still surprises me to see it in the flesh. Especially in a place like Detroit. >> It's nice. >> Yeah. >> It's so nice to see it. And you bring up a good point. It's very authentic. >> Savannah: It's super authentic. >> I mean, what surprised me is one, the Wasm, or web assembly. I didn't see that coming at the scale of the conversation. It sucked a lot of options out of the room in my opinion, still hyped up. But this looks like it's got a good trajectory. I like that. The other thing that surprised me that was a learning was my interview with Solo.io, Idit, and Brian Gracely, because he's a CUBE alumni and former host of theCUBE, and analyst at Wikibon, was how their go-to-market was an example of a modern company in Covid with a clean sheet of paper and smart people, they're just doing things different. They're in Slack with their customers. And I walked away with, "Wow that's like a playbook that's not, was never, in the go-to-market VC-backed company playbook." I thought that was, for me, a personal walk away saying that's important. I like how they did that. And there's a lot of companies I think could learn from that. Especially as the recession comes where partnering with customers has always been a top priority. And how they did that was very clever, very effective, very efficient. So I walked away with that saying, "I think that's going to be a standard." So that was a pleasant surprise. >> That was a great surprise. Also, that's a female-founded company, which is obviously not super common. And the growth that they've experienced, to your point, really being catalyzed by Covid, is incredibly impressive. I mean they have some massive brand name customers, Amex, BMW for example. >> Savannah: Yeah. >> Great point. >> And I interviewed her years ago and I remember saying to myself, "Wow, she's impressive." I liked her. She's a player. A player for sure. And she's got confidence. Even on the interview she said, "We're just better, we have better product." And I just like the point of view. Very customer-focused but confident. And I just took, that's again, a great company. And again, I'm not surprised that Brian Gracely left Red Hat to go work there. So yeah, great, great call there. And of course other things that weren't surprising that I predicted, Red Hat continued to invest. They continue to bring people on theCUBE, they support theCUBE but more importantly they have a good strategy. They're in that multicloud positioning. They're going to have an opportunity to get a bite at the apple. And I what I call the supercloud. As enterprises try to go and be mainstream, Cloud Native, they're going to need some help. And Red Hat is always has the large enterprise customers. >> Savannah: What surprised you, Lisa? >> Oh my gosh, so many things. I think some of the memorable conversations that we had. I love talking with some of the enterprises that we mentioned, ING Bank for example. You know, or institutions that have been around for 100 plus years. >> Savannah: Oh, yeah. To see not only how much they've innovated and stayed relevant to meet the demands of the consumer, which are only increasing, but they're doing so while fostering a culture of innovation and a culture that allows these technology leaders to really grow within the organization. That was a really refreshing conversation that I think we had. 'Cause you can kind of >> Savannah: Absolutely. think about these old stodgy companies. Nah, of course they're going to digitize. >> Thinking about working for the bank, I think it's boring. >> Right? >> Yeah. And they were talking about, in fact, those great t-shirts that they had on, >> Yeah, yeah, yeah, yeah. were all about getting more people to understand how fun it is to work in tech for ING Bank in different industries. You don't just have to work for the big tech companies to be doing really cool stuff in technology. >> What I really liked about this show is we had two female hosts. >> Savannah: Yeah. >> How about that? Come on. >> Hey, well done, well done on your recruitment there, champ. >> Yes, thank you boss. (John laughs) >> And not to mention we have a really all-star production team. I do just want to give them a little shout out. To all the wonderful folks behind the lines here. (people clapping) >> John: Brendan. Good job. >> Yeah. Without Brendan, Anderson, Noah, and Andrew, we would be-- >> Of course Frank Faye holding it back there too. >> Yeah, >> Of course, Frank. >> I mean, without the business development wheels on the ship we'd really be in an unfortunate spot. I almost just swore on television. We're not going to do that. >> It's okay. No one's regulating. >> Yeah. (all laugh) >> Elon Musk just took over Twitter. >> It was a close call. >> That's right! >> It's going to be a hellscape. >> Yeah, I mean it's, shit's on fire. So we'll just see what happens next. I do, I really want to talk about this because I think it's really special. It's an ethos and some magic has happened here. Let's talk about Detroit. Let's talk about what it means to be here. We saw so many, and I can't stress this enough, but I think it really matters. There was a commitment to celebrating place here. Lisa, did you notice this too? >> Absolutely. And it surprised me because we just don't see that at conferences. >> Yeah. We're so used to going to the same places. >> Right. >> Vegas. Vegas, Vegas. More Vegas. >> Your tone-- >> San Francisco >> (both laugh) sums up my feelings. Yes. >> Right? >> Yeah. And, well, it's almost robotic but, and the fact that we're like, oh Detroit, really? But there was so much love for this city and recognizing and supporting its residents that we just don't see at conferences. You uncovered a lot of that with your swag-savvy segments, >> Savannah: Yeah. >> And you got more of that to talk about today. >> Don't worry, it's coming. Yeah. (laughs) >> What about you? Have you enjoyed Detroit? I know you hadn't been here in a long time, when we did our intro session. >> I think it's a bold move for the CNCF to come here and celebrate. What they did, from teaching the kids in the city some tech, they had a session. I thought that was good. >> Savannah: Loved that. I think it was a risky move because a lot of people, like, weren't sure if they were going to fly to Detroit. So some say it might impact the attendance. I thought they did a good job. Their theme, Road Ahead. Nice tie in. >> Savannah: Yeah. And so I think I enjoyed Detroit. The weather was great. It didn't rain. Nice breeze outside. >> Yeah. >> The weather was great, the restaurants are phenomenal. So Detroit's a good city. I missed some hockey games. I'd love to see the Red Wings play. Missed that game. But we always come back. >> I think it's really special. I mean, every time I talked to a company about their swag, that had sourced it locally, there was a real reason for this story. I mean even with Kasten in that last segment when I noticed that they had done Carhartt beanies, Carhartt being a Michigan company. They said, "I'm so glad you noticed. That's why we did it." And I think that type of, the community commitment to place, it all comes back to community. One of the bigger themes of the show. But that passion and that support, we need more of that. >> Lisa: Yeah. >> And the thing about the guests we've had this past three days have been phenomenal. We had a diverse set of companies, individuals come on theCUBE, you know, from Scott Johnston at Docker. A really one on one. We had a great intense conversation. >> Savannah: Great way to kick it off. >> We shared a lot of inside baseball, about Docker, super important company. You know, impressed with companies like Platform9 it's been around since the OpenStack days who are now in a relevant position. Rafi Systems, hot startup, they don't have a lot of resources, a lot of guerilla marketing going on. So I love to see the mix of startups really contributing. The big players are here. So it's a real great mix of companies. And I thought the interviews were phenomenal, like you said, Ford. We had, Kubia launched on theCUBE. >> Savannah: Yes. >> That's-- >> We snooped the location for KubeCon North America. >> You did? >> Chicago, everyone. In case you missed it, Bianca was nice enough to share that with us. >> We had Sarbjeet Johal, CUBE analyst came on, Keith Townsend, yesterday with you guys. >> We had like analyst speed dating last night. (all laugh) >> How'd that go? (laughs) >> It was actually great. One of the things that they-- >> Did they hug and kiss at the end? >> Here's the funny thing is that they were debating the size of the CNC app. One thinks it's too big, one thinks it's too small. And I thought, is John Goldilocks? (John laughs) >> Savannah: Yeah. >> What is John going to think about that? >> Well I loved that segment. I thought, 'cause Keith and Sarbjeet argue with each other on Twitter all the time. And I heard Keith say before, he went, "Yeah let's have it out on theCUBE." So that was fun to watch. >> Thank you for creating this forum for us to have that kind of discourse. >> Lisa: Yes, thank you. >> Well, it wouldn't be possible without the sponsors. Want to thank the CNCF. >> Absolutely. >> And all the ecosystem partners and sponsors that make theCUBE possible. We love doing this. We love getting the stories. No story's too small for theCUBE. We'll go with it. Do whatever it takes. And if it wasn't for the sponsors, the community wouldn't get all the great knowledge. So, and thank you guys. >> Hey. Yeah, we're, we're happy to be here. Speaking of sponsors and vendors, should we talk a little swag? >> Yeah. >> What do you guys think? All right. Okay. So now this is becoming a tradition on theCUBE so I'm very delighted, the savvy swag segment. I do think it's interesting though. I mean, it's not, this isn't just me shouting out folks and showing off t-shirts and socks. It's about standing out from the noise. There's a lot of players in this space. We got a lot of CNCF projects and one of the ways to catch the attention of people walking the show floor is to have interesting swag. So we looked for the most unique swag on Wednesday and I hadn't found this yet, but I do just want to bring it up. Oops, I think I might have just dropped it. This is cute. Is, most random swag of the entire show goes to this toothbrush. I don't really have more in terms of the pitch there because this is just random. (Lisa laughs) >> But so, everyone needs that. >> John: So what's their tagline? >> And you forget these. >> Yeah, so the idea was to brush your cloud bills. So I think they're reducing the cost of-- >> Kind of a hygiene angle. >> Yeah, yeah. Very much a hygiene angle, which I found a little ironic in this crowd to be completely honest with you. >> John: Don't leave the lights on theCUBE. That's what they say. >> Yeah. >> I mean we are theCUBE so it would be unjust of me not to show you a Rubik's cube. This is actually one of those speed cubes. I'm not going to be able to solve this for you with one hand on camera, but apparently someone did it in 17 seconds at the booth. Knowing this audience, not surprising to me at all. Today we are, and yesterday, was the t-shirt contest. Best t-shirt contest. Today we really dove into the socks. So this is, I noticed this trend at KubeCon in Los Angeles last year. Lots of different socks, clouds obviously a theme for the cloud. I'm just going to lay these out. Lots of gamers in the house. Not surprising. Here on this one. >> John: Level up. >> Got to level up. I love these 'cause they say, "It's not a bug." And anyone who's coded has obviously had to deal with that. We've got, so Star Wars is a huge theme here. There's Lego sets. >> John: I think it's Star Trek. But. >> That's Star Trek? >> John: That's okay. >> Could be both. (Lisa laughs) >> John: Nevermind, I don't want to. >> You can flex your nerd and geek with us anytime you want, John. I don't mind getting corrected. I'm all about, I'm all about the truth. >> Star Trek. Star Wars. Okay, we're all the same. Okay, go ahead. >> Yeah, no, no, this is great. Slim.ai was nice enough to host us for dinner on Tuesday night. These are their lovely cloud socks. You can see Cloud Native, obviously Cloud Native Foundation, cloud socks, whole theme here. But if we're going to narrow it down to some champions, I love these little bee elephants from Raft. And when I went up to these guys, I actually probably would've called these my personal winner. They said, again, so community focused and humble here at CNCF, they said that Wiz was actually the champion according to the community. These unicorn socks are pretty excellent. And I have to say the branding is flawless. So we'll go ahead and give Wiz the win on the best sock contest. >> John: For the win. >> Yeah, Wiz for the win. However, the thing that I am probably going to use the most is this really dope Detroit snapback from Kasten. So I'm going to be rocking this from now on for the rest of the segment as well. And I feel great about this snapback. >> Looks great. Looks good on you. >> Yeah. >> Thanks John. (John laughs) >> So what are we expecting between now and KubeCon in Amsterdam? >> Well, I think it's going to be great to see how they, the European side, it's a chill show. It's great. Brings in the European audience from the global perspective. I always love the EU shows because one, it's a great destination. Amsterdam's going to be a great location. >> Savannah: I'm pumped. >> The American crowd loves going over there. All the event cities that they choose are always awesome. I missed Valencia cause I got Covid. I'm really bummed about that. But I love the European shows. It's just a little bit, it's high intensity, but it's the European chill. They got a little bit more of that siesta vibe going on. >> Yeah. >> And it's just awesome. >> Yeah, >> And I think that the mojo that carried throughout this week, it's really challenging to not only have a show that's five days, >> but to go through all week, >> Savannah: Seriously. >> to a Friday at 4:00 PM Eastern Time, and still have the people here, the energy and all the collaboration. >> Savannah: Yeah. >> The conversations that are still happening. I think we're going to see a lot more innovation come spring 2023. >> Savannah: Mm-hmm. >> Yeah. >> So should we do a bet, somebody's got to buy dinner? Who, well, I guess the folks who lose this will buy dinner for the other one. How many attendees do you think we'll see in Amsterdam? So we had 4,000, >> Oh, I'm going to lose this one. >> roughly in Los Angeles. Priyanka was nice enough to share with us, there was 8,000 here in Detroit. And I'm talking in person, we're not going to meddle this with the online. >> 6500. >> Lisa: I was going to say six, six K. >> I'm going 12,000. >> Ooh! >> I'm going to go ahead and go big I'm going to go opposite Price Is Right. >> One dollar. >> Yeah. (all laugh) That's exactly where I was driving with it. I'm going, I'm going absolutely all in. I think the momentum here is building. I think if we look at the numbers from-- >> John: You could go Family Feud >> Yeah, yeah, exactly. And they mentioned that they had 11,000 people who have taken their Kubernetes course in that first year. If that's a benchmark and an indicator, we've got the veteran players here. But I do think that, I personally think that the hype of Kubernetes has actually preceded adoption. If you look at the data and now we're finally tipping over. I think the last two years we were on the fringe and right now we're there. It's great. (voice blares loudly on loudspeaker) >> Well, on that note (all laugh) On that note, actually, on that note, as we are talking, so I got to give cred to my cohosts. We deal with a lot of background noise here on theCUBE. It is a live show floor. There's literally someone on an e-scooter behind me. There's been Pong going on in the background. The sound will haunt the three of us for the rest of our lives, as well as the production crew. (Lisa laughs) And, and just as we're sitting here doing this segment last night, they turned the lights off on us, today they're letting everyone know that the event is over. So on that note, I just want to say, Lisa, thank you so much. Such a warm welcome to the team. >> Thank you. >> John, what would we do without you? >> You did an amazing job. First CUBE, three days. It's a big show. You got staying power, I got to say. >> Lisa: Absolutely. >> Look at that. Not bad. >> You said it on camera now. >> Not bad. >> So you all are stuck with me. (all laugh) >> A plus. Great job to the team. Again, we do so much flow here. Brandon, Team, Andrew, Noah, Anderson, Frank. >> They're doing our hair, they're touching up makeup. They're helping me clean my teeth, staying hydrated. >> We look good because of you. >> And the guests. Thanks for coming on and spending time with us. And of course the sponsors, again, we can't do it without the sponsors. If you're watching this and you're a sponsor, support theCUBE, it helps people get what they need. And also we're do a lot more segments around community and a lot more educational stuff. >> Savannah: Yeah. So we're going to do a lot more in the EU and beyond. So thank you. >> Yeah, thank you. And thank you to everyone. Thank you to the community, thank you to theCUBE community and thank you for tuning in, making it possible for us to have somebody to talk to on the other side of the camera. My name is Savannah Peterson for the last time in Detroit, Michigan. Thanks for tuning into theCUBE. >> Okay, we're done. (bright upbeat music)

(upbeat music) >> Hello, brilliant humans and welcome back to theCUBE. We're live from Detroit, Michigan. My name is Savannah Peterson. Joined here with John Furrier, John, so exciting, day three. >> Day three, cranking along, doing great, final day of KubeCon, it wraps up. This next segment's going to be great. It's about WebAssembly, the hottest trend here, at KubeCon that nobody knows about cause they just got some funding and it's got some great traction. Multiple players in here. People are really interested in this and they're really discovering it. They're digging into it. So, we're going to hear from one of the founders of the company that's involved. So, it'll be great. >> Yeah, I think we're right at the tip of the iceberg really. We started off the show with Scott from Docker talking about this, but we have a thought leader in this space. Please welcome Matt Butcher the CEO and co-founder of Fermyon Thank you for being here. Welcome. >> Yeah, thanks so much for having me. Favorite thing to talk about is WebAssembly after that is coffee but WebAssembly first. >> Hey, it's the morning. We can talk about both those on the show. (all chuckles) >> It might get confusing, but I'm willing to try. >> If you can use coffee as a metaphor to teach everyone about WebAssembly throughout the rest of the show. >> All right. That would be awesome. >> All right I'll keep that in mind. >> So when we were talking before we got on here I thought it was really fun because I think the hype is just starting in the WebAssembly space. Very excited about it. Where do you think we're at, set the stage? >> Honestly, we were really excited to come here and see that kind of first wave of hype. We came here expecting to have to answer the question you know, what is WebAssembly and why is anybody looking at it in the cloud space, and instead people have been coming up to us and saying, you know this WebAssembly thing, we're hearing about it. What are the problems it's solving? >> Savannah: Yeah. >> We're really excited to hear about it. So, people literally have been stopping us in restaurants and walking down the street, hey, "You're at KubeCon, you're the WebAssembly people. Tell us more about what's going on." >> You're like awesome celeb. I love this. >> Yeah, and I, >> This is great >> You know the, the description I used was I expected to come here shouting into the void. Hey, you know anybody, somebody, let me tell you about WebAssembly. Instead it's been people coming to us and saying "We've heard about it. Get us excited about it," and I think that's a great place to be. >> You know, one of the things that's exciting too is that this kind of big trend with this whole extraction layer conversation, multicloud, it reminds me of the old app server days where, you know there was a separation between the back end and front end, and then we're kind of seeing that now with this WebAssembly Wasm trend where the developers just want to have the apps run everywhere and the coding to kind of fall in, take a minute to explain what this is, why it's important, why are people jazzed about there's other companies like Cosmonic is in there. There's a lot of open source movement behind it. You guys are out there, >> Savannah: Docker. >> 20 million in fresh funding. Why is this important? What is it and why is it relevant right now? Why are people talking about it? >> I mean, we can't... There is no penasia in the tech world much for the good of all of us, right? To keep us employed. But WebAssembly seems to be that technology that just sort of arose at the right time to solve a number of problems that were really feeling intractable not very long ago. You know, at the core of what is WebAssembly? Well it's a binary format, right? But there's, you know, built on the same, strain of development that Java was built on in the 90's and then the .net run time. But with a couple of little fundamental changes that are what have made it compelling today. So when we think about the cloud world, we think about, okay well security's a big deal to us. Virtual machines are a way for us to run other people's untrusted operating systems on our hardware. Containers come along, they're a... The virtual machine is really the heavyweight class. This is the big thing. The workhorse of the cloud. Then along come Containers, they're a little slimmer. They're kind of the middleweight class. They provide us this great way to sort of package up just the application, not the entire operating system just the application and the bits we care about and then be able to execute those in a trusted environment. Well you know, serverless was the buzzword a few years ago. But one thing that serverless really identified for us is that we didn't actually have the kind of cloud side architecture that was the compute layer that was going to be able to fulfill the promise of serverless. >> Yeah. >> And you know, at that time I was at Microsoft we got to see behind the curtain and see how Azure operates and see the frustration with going, okay how do we get this faster? How do we get this startup time down from seconds to hundreds of milliseconds, WebAssembly comes along and we're able to execute these things in sub one millisecond, which means there is almost no cost to starting up one of these. >> Sub one millisecond. I just want to let everyone rest on that for a second. We've talked a lot about velocity and scale on the show. I mean everyone here is trying to do things faster >> Yep >> Obviously, but that is a real linchpin that makes a very big difference when we're talking about deploying things. Yeah. >> Yeah, and I mean when you think about the ecological and the cost impact of what we're building with the cloud. When we leave a bunch of things running in idle we're consuming electricity if nothing else. The electricity bill keeps going up and we're paying for it via cloud service charges. If you can start something in sub one millisecond then there's no reason you have to leave it running when nobody's using it. >> Savannah: Doesn't need to be in the background. >> That's right. >> So the lightweight is awesome. So, this new class comes up. So, like Java was a great metaphor there. This is kind of like that for the modern era of apps. >> Yeah. >> Where is this going to apply most, do you think? Where's it going to impact most? >> Well, you know, I think there are really four big categories. I think there's the kind of thing I was just talking about I think serverless and edge computing and kind of the server class of problem space. I think IOT is going to benefit, Amazon, Disney Plus, >> Savannah: Yes, edge. >> And PBS, sorry BBC, they all use WebAssembly for the players because they need to run the same player on thousands of different devices. >> I didn't even think about that use case. What a good example. >> It's a brilliant way to apply it. IOT is a hard space period and to be able to have that kind of layer of abstraction. So, that's another good use case >> Savannah: Yeah. >> And then I think this kind of plugin model is another one. You see it was Envoy proxy using this as a way to extend the core features. And I think that one's going to be very, very promising as well. I'm forgetting one, but you know. (all chuckles) I think you end up with these kind of discreet compartments where you can easily fit WebAssembly in here and it's solving a problem that we didn't have the technology that was really adequately solving it before. >> No, I love that. One of the things I thought was interesting we were all at dinner, we were together on Tuesday. I was chatting with Paris who runs Deliveroo at Apple and I can't say I've heard this about too many tools but when we were talking about WebAssembly she said "This is good for everybody" And, it's really nice when technologies come along that will raise the water level across the board. And I love that you're leading this. Speaking of you just announced a huge series aid, 20 million dollars just a few days ago. What does that mean for you and the team? >> I mean there's a little bit of economic uncertainty and it's always nice, >> Savannah: Just a little bit. >> Little bit. >> Savannah: It's come up on the show a little bit this week >> Just smidge. and it's nice to know that we're at a critical time developing this kind of infrastructure layer developing this kind of developer experience where they can go from, you know, blinking cursor to deployed application in two minutes or less. It would be a tragedy if that got forestalled merely because you can't achieve the velocity you need to carry it out. So, what's very exciting about being able to raise around like that at this critical time is that gives us the ability to grow strategically, be able to continue releasing products, building a community around WebAssembly as a whole and of course around our products at Fermyon is a little smaller circle in the bigger circle, and that's why we are so excited about having closed around, that's the perfect one to extend a runway like that. >> Well I'm super excited by this because one I love the concept. I think it's very relevant, like how you progress heavyweight, middleweight, maybe this is lightweight class. >> I know, I'm here for the analogy. No, it's great, its great. >> Maybe it's a lightweight class. >> And we're slimming, which not many of us can say in these times so that's awesome. >> Maybe it's more like the tractor trailer, the van, now you got the sports car. >> Matt: Yeah, I can go.. >> Now you're getting Detroit on us. >> I was trying for a coffee, when I just couldn't figure it out. (all chuckles) >> So, you got 20 million. I noticed the investors amplify very good technical VC and early stage firm. >> Amazing, yeah. >> Insight, they do early stage, big early stage like this. Also they're on the board of Docker. Docker was intent to put a tool out there. There's other competition out there. Cosmonic is out there. They're funded. So you got VC funded companies like yourselves and Cosmonic and others. What's that mean? Different tool chains, is it going to create fragmentation? Is there a common mission? How do you look at the competition as you get into the market >> When you see an ecosystem form. So, here we are at KubeCon, the cloud native ecosystem at this point I like to think of them as like concentric rings. You have the kind of core and then networking and storage and you build these rings out and the farther out you get then the easier it is to begin talking about competition and differentiation. But, when you're looking at that core piece everybody's got to be in there together working on the same stuff, because we want interoperability, we want standards based solutions. We want common ways of building things. More than anything, we want the developers and operators and users who come into the ecosystem to be able to like instantly feel like, okay I don't have to learn. Like you said, you know, 50 different tools for 50 different companies. "I see how this works", and they're doing this and they're doing this. >> Are you guys all contributing into the same open source? >> Yep, yeah, so... >> All the funding happens. >> Both CNCF and the ByteCode Alliance are organizations that are really kind of pushing forward that core technology. You know, you mentioned Cosmonic, Microsoft, SOSA, Red Hat, VMware, they're all in here too. All contributing and again, with all of us knowing this is that nascent stage where we got to execute it. >> How? >> Do it together. >> How are you guys differentiating? Because you know, open source is a great thing. Rising Tide floats all boats. This is a hot area. Is there a differentiation discussion or is it more let's see how it goes, kind of thing? >> Well for us, we came into it knowing very specifically what the problem was we wanted to solve. We wanted this serverless architecture that executed in sub one millisecond to solve, to really create a new wave of microservices. >> KubeCon loves performance. They want to run their stuff on the fastest platform possible. >> Yeah, and it shouldn't be a roadblock, you know, yeah. >> And you look at someone like SingleStore who's a database company and they're in it because they want to be able to run web assemblies close to the data. Instead of doing a sequel select and pulling it way out here and munging it and then pushing it back in. They move the code in there and it's executing in there. So everybody's kind of finding a neat little niche. You know, Cosmonic has really gone more for an enterprise play where they're able to provide a lot of high level security guarantees. Whereas we've been more interested in saying, "Hey, this your first foray into WebAssembly and you're interested in serverless we'll get you going in like a couple of minutes". >> I want to ask you because we had Scott Johnston on earlier opening keynote so we kind of chatted one-on-one and I went off form cause I really wanted to talk to him because Docker is one of the most important companies since their pivot, when they did their little reset after the first Docker kind of then they sold the enterprise off to Mirantis they've been doing really, really well. What's your relationship to Docker? He was very bullish with you guys. Insights, joint investor. Is there a relationship? You guys talk, what's going on there? >> I mean, I'm going to have to admit a little bit of hero worship on my part. I think Scott is brilliant. I just do, and having come from the Kubernetes world the Fermyon team, we've always kind of kept an eye on Docker communicated with a lot of them. We've known Justin Cormack for years. Chris Cornett. (indistinct) I mean yeah, and so it has been a very natural >> Probably have been accused of every Docker Con and we've did the last three years on the virtual side with them. So, we know them really well. >> You've always got your finger on the pulse for them. >> Do you have a relationship besides a formal relationship or is it more of pass shoot score together in the industry? >> Yeah. No, I think it is kind of the multi-level one. You come in knowing people. You've worked together before and you like working with each other and then it sort of naturally extends onto saying, "Hey, what can we do together?" And also how do we start building this ecosystem around us with Docker? They've done an excellent job of articulating why WebAssembly is a complimentary technology with Containers. Which is something I believe very wholeheartedly. You need all three of the heavyweight, middleweight, lightweight. You can't do all the with just one, and to have someone like that sort of with a voice profoundly be able to express, look we're going to start integrating it to show you how it works this way and prevent this sort of like needless drama where people are going, oh Dockers dead, now everything's WebAssembly, and that's been a great.. >> This fight that's been going on. I mean, Docker, Kubernetes, WebAssembly, Containers. >> Yeah. >> We've seen on the show and we both know this hybrid is the future. We're all going to be using a variety of different tools to achieve our goals and I think that you are obviously one of them. I'm curious because just as we were going on you mentioned that you have a PhD in philosophy. (Matt chuckles) >> Matt: Yeah. >> Which is a wild card. You're actually our second PhD in philosophy working in a very technical role on the show this week, which is kind of cool. So, how does that translate into the culture at Fermyon? What's it like on the team? >> Well, you know, a philosophy degree if nothing else teaches you to think in systems and both human systems and formal systems. So that helps and when you approach the process of building a company, you need to be thinking both in terms of how are we organizing this? How are we organizing the product? How do we organize the team? We have really learned that culture is a major deal and culture philosophy, >> Savannah: Why I'm bringing it up. >> We like that, you know, we've been very forward. We have our chip values, curiosity, humility inclusivity and passion, and those are kind of the four things that we feel like that each of us every day should strive to be exhibiting these kinds of things. Curiosity, because you can't push the envelope if you don't ask the hard questions. Humility, because you know, it's easy to get cocky and talk about things as if you knew all the answers. We know we don't and that means we can learn from Docker and Microsoft >> Savannah: That's why you're curious. >> And the person who stops by the booth that we've never met before and says, "hey" and inclusivity, of course, building a community if you don't execute on that well you can't build a good community. The diversity of the community is what makes it stronger than a singular.. >> You have to come in and be cohesive with the community. >> Matt: Yeah. >> The app focus is a really, I think, relevant right now. The timing of this is right online. I think Scott had a good answer I thought on the relationship and how he sees it. I think it's going to be a nice extension to not a extension that way, but like. >> It probably will be as well. >> Almost a pun there John, almost a pun. >> There actually might be an extension, but evolution what we're going to get to which I think is going to be pure application server, like. >> Yep, yep. Like performance for new class of developer. Then now the question comes up and we've been watching developer productivity. That is a big theme and our belief is that if you take digital transformation to its conclusion IT and developers aren't a department serving the business they are the business. That means the developer workflows will have to be radically rebuilt to handle the velocity and new tech for just coding. I call it architectural list. >> I like that. I might steal that. >> It's a pun, but it's also brings up the provocative question. You shouldn't have to need an architecture to code. I mean, Java was great for that reason in many ways. So, if that happens if the developers are running the business that means more apps. The apps is the business. You got to have tool chains and productivity. You can't have fragmentation. Some people are saying WebAssembly might, fork tool chains, might challenge the developer productivity. what's your answer to that? How would you address that objection? >> I mean the threat of forking is always lurking in the corner in open source. In a way it's probably a positive threat because it keeps us honest it keeps us wanting to be inclusive again and keep people involved. Honestly though, I'm not particularly worried about it. I know that the W-3 as a standards body, of course, one of the most respected standards bodies on the planet. They do html, they do cascading style sheets. WebAssembly is in that camp and those of us in the core are really very interested in saying, you know, come on in, let's build something that's going to be where the core is solid and you know what you got and then you can go into the resurgence of the application server. I mean, I wholeheartedly agree with you on that, and we can only get there if we say, all right, here are the common paradigms that we're all going to agree to use, now let's go build stuff. >> And as we've been saying, developers are setting, I think are going to set the standards and they're going to vote with their code and their feet, if you will. >> Savannah: A hundred percent. >> They will decide if you're not aligning with what they want to do. okay. On how they want to self-serve and or work, you'll figure that out. >> Yep, yep. >> You'll get instant feedback. >> Yeah. >> Well, you know, again, I tell you a huge fan of Docker. One of the things that Docker understood at the very outset, is that they had an infrastructure tool and developers were the way to get adoption, and if you look at how fast they got adoption versus many, many other technologies that are profoundly impacted. >> Savannah: Wild. >> Yeah. >> Savannah: It's a cool story. >> It's because they got the developers to go, "This is amazing, hey infrastructure folks, here's an infrastructure tool that we like" and the infrastructure folks are used to code being tossed over the wall are going, "Are you for real?" I mean, and that was a brilliant way to do it and I think that what.. >> John: Yeah, yeah. >> We want to replay in the WebAssembly world is making it developer friendly and you know the kind of infrastructure that we can actually operate. >> Well congratulations to the entire community. We're huge fans of the concept. I kind of see where it's going with connect the dots. You guys getting a lot of buzz. I have to ask you, my final question is the hype is beyond all recognition at this point. People are super pumped and enthusiastic about it and people are looking at it maybe some challenging it, but that's all good things. How do you get to the next level where people are confident that this is actually going to go the next step? Hype to confidence. We've seen great hype. Envoy was hyped up big time before it came in, then it became great. That was one of my favorite examples. Hype is okay, but now you got to put some meat on the bone. The sizzle on the stake so to speak. So what's going to be the stake for you guys as you see this going forward? What's the need? >> Yeah, you know, I talk about our first guiding story was, you know, blinking cursor to deployed application in two minutes. That's what you need to win developers initially. So, what's the next story after that? It's got to be, Fermyon can run real world applications that solve real world problems. That's where hype often fails. If you can build something that's neat but nobody's quite sure what to do with it, to use it, maybe somebody will discover a good use. But, if you take that gambling asset, >> Savannah: It's that ending answer that makes the difference. >> Yeah, yeah. So we say, all right, what are developers trying to build with our platform and then relentlessly focus on making that easier and solving the real world problem that way. That's the crucial thing that's going to drive us out of that sort of early hype stage into a well adopted technology and I talk from Fermyon point of view but really that's for all of us in the WebAssembly. >> John: Absolutely. >> Very well stated Matt, just to wrap us up when we're interviewing you here on theCUBE next year, what do you hope to be able to say then that you can't say today? >> All this stuff about coffee we didn't cover today, but also.. (all chuckles) >> Savannah: Here for the coffee show. Only analogies, that's a great analogy. >> I want to walk here and say, you know last time we talked about being able to achieve density in servers that was, you know, 10 times Kubernetes. Next year I want to say no, we're actually thousands of times beyond Kubernetes that we're lowering people's electricity bill by making these servers more efficient and the developers love it. >> That your commitment to the environment is something I want to do an entirely different show on. We learned that 7-8% of all the world's powers actually used on data centers through the show this week which is jarring quite frankly. >> Yeah, yeah. Tragic would be a better way of saying that. >> Yeah, I'm holding back so that we don't go over time here quite frankly. But anyways, Matt Butcher thank you so much for being here with us. >> Thank you so much for having me it was pleasure.. >> You are worth the hype you are getting. I am grateful to have you as our WebAssembly thought leader. In addition to Scott today from Docker earlier in the show. John Furrier, thanks for being my co-host and thank all of you for tuning into theCUBE here, live from Detroit. I'm Savannah Peterson and we'll be back with more soon. (ambient music)

(upbeat synth intro music) >> Hey everyone and welcome to Detroit, Michigan. theCUBE is live at KubeCon CloudNativeCon, North America 2022. Lisa Martin here with John Furrier. John, this event, the keynote that we got out of a little while ago was, standing room only. The Solutions hall is packed. There's so much buzz. The community is continuing to mature. They're continuing to contribute. One of the big topics is Cloud Native at Scale. >> Yeah, I mean, this is a revolution happening. The developers are coming on board. They will be running companies. Developers, structurally, will be transforming companies with just, they got to get powered somewhere. And, I think, the Cloud Native at Scale speaks to getting everything under the covers, scaling up to support developers. In this next segment, we have two Kube alumnis. We're going to talk about Cloud Native at Scale. Some of the things that need to be there in a unified architecture, should be great. >> All right, it's going to be fantastic. Let's go under the covers here, as John mentioned, two alumni with us, Madhura Maskasky joins us, co-founder of Platform9. Sirish Raghuram, also co-founder of Platform9 joins us. Welcome back to theCUBE. Great to have you guys here at KubeCon on the floor in Detroit. >> Thank you for having us. >> Thank you for having us. >> Excited to be here >> So, talk to us. You guys have some news, Madhura, give us the sneak peak. What's going on? >> Definitely, we are very excited. So, we have John, not too long ago we spoke about our very new open source project called Arlon. And, we were talking about the launch of Arlon in terms of its first release and etcetera. And, just fresh hot of the press, we, Platform9 had its 5.6 release which is its most recent release of our product. And there's a number of key interesting announcements that we'd like to share as part of that. I think, the prominent one is, Platform9 added support for EKS Kubernetes cluster management. And, so, this is part of our vision of being able to add value, no matter where you run your Kubernetes clusters, because, Kubernetes or cluster management, is increasingly becoming commodity. And, so, I think the companies that succeed are going to add value on top, and are going to add value in a way that helps end users, developers, DevOps solve problems that they encounter as they start running these environments, with a lot of scale and a lot of diversity. So, towards that, key features in the 5.6 six release. First, is the very first package release of the product online, which is the open source project that we've kicked off to do cluster and application, entire cluster management at scale. And, then there's few other very interesting capabilities coming out of that. >> I want to just highlight something and then get your thoughts on this next, this release 5.6. First of all, 5.6, it's been around for a while, five reps, but, now, more than ever, you mentioned the application in Ops. You're seeing WebAssembly trends, you're seeing developers getting more and more advanced capability. It's going to accelerate their ability to write code and compose applications. So, you're seeing a application tsunami coming. So, the pressure is okay, they're going to need infrastructure to run all that stuff. And, so, you're seeing more clusters being spun up, more intelligence trying to automate. So you got the automation, so you got the dynamic, the power dynamic of developers and then under the covers. What does 5.6 do to push the mission forward for developers? How would you guys summarize that for people watching? what's in it for them right now? >> So it's, I think going back to what you just said, right, the breadth of applications that people are developing on top of something like Kubernetes and Cloud Native, is always growing. So, it's not just a number of clusters, but also the fact that different applications and different development groups need these clusters to be composed differently. So, a certain version of the application may require some set of build components, add-ons, and operators, and extensions. Whereas, a different application may require something entirely different. And, now, you take this in an enterprise context, right. Like, we had a major media company that worked with us. They have more than 10,000 pods being used by thousands of developers. And, you now think about the breadth of applications, the hundreds of different applications being built. how do you consistently build, and compose, and manage, a large number of communities clusters with a a large variety of extensions that these companies are trying to manage? That's really what I think 5.6 is bringing to the table. >> Scott Johnston just was on here early as the CEO of Docker. He said there's more applications being pushed now than in the history of application development combined. There's more and more apps coming, more and more pressure on the system. >> And, that's where, if you go, there's this famous landscape chart of the CNCF ecosystem technologies. And, the problem that people here have is, how do they put it all together? How do they make sense of it? And, what 5.6 and Arlon and what Platform9 is doing is, it's helping you declaratively capture blueprints of these clusters, using templates, and be able to manage a small number of blueprints that helps you make order out of the chaos of these hundreds of different projects, that are all very interesting and powerful. >> So Project Arlon really helping developers produce the configuration and the deployment complexities of Kubernetes at scale. >> That's exactly right. >> Talk about the, the impact on the business side. Ease of use, what's the benefits for 5.6? What's does it turn into for a benefit standpoint? >> Yeah, I think the biggest benefit, right, is being able to do Cloud Native at Scale faster, and while still keeping a very lean Ops team that is able to spend, let's say 70 plus percent of their time, caring for your actual business bread and butter applications, and not for the infrastructure that serves it, right. If you take the analogy of a restaurant, you don't want to spend 70% of your time in building the appliances or setting up your stoves etcetera. You want to spend 90 plus percent of your time cooking your own meal, because, that is your core key ingredient. But, what happens today in most enterprises is, because, of the level of automation, the level of hands-on available tooling, being there or not being there, majority of the ops time, I would say 50, 70% plus, gets spent in making that kitchen set up and ready, right. And, that is exactly what we are looking to solve, online. >> What would a customer look like, or prospect environment look like that would be really ready for platform9? What, is it more apps being pushed, big push on application development, or is it the toil of like really inefficient infrastructure, or gaps in skills of people? What does an environment look like? So, someone needs to look at their environment and say, okay, maybe I should call platform9. What's it look like? >> So, we generally see customers fall into two ends of the barbell, I would say. One, is the advanced communities users that are running, I would say, typically, 30 or more clusters already. These are the people that already know containers. They know, they've container wise... >> Savvy teams. >> They're savvy teams, a lot of them are out here. And for them, the problem is, how do I manage the complexity at scale? Because, now, the problem is how do I scale us? So, that's one end of the barbell. The other end of the barbell, is, how do we help make Kubernetes accessible to companies that, as what I would call the mainstream enterprise. We're in Detroit in Motown, right, And, we're outside of the echo chamber of the Silicon Valley. Here's the biggest truth, right. For all the progress that we made as a community, less than 20% of applications in the enterprise today are running on Kubernetes. So, what does it take? I would say it's probably less than 10%, okay. And, what does it take, to grow that in order of magnitude? That's the other kind of customer that we really serve, is, because, we have technologies like Kube Word, which helps them take their existing applications and start adopting Kubernetes as a directional roadmap, but, while using the existing applications that they have, without refactoring it. So, I would say those are the two ends of the barbell. The early adopters that are looking for an easier way to adopt Kubernetes as an architectural pattern. And, the advanced savvy users, for whom the problem is, how do they operationally solve the complexity of managing at scale. >> And, what is your differentiation message to both of those different user groups, as you talked about in terms of the number of users of Kubernetes so far? The community groundswell is tremendous, but, there's a lot of opportunity there. You talked about some of the barriers. What's your differentiation? What do you come in saying, this is why Platform9 is the right one for you, in the both of these groups. >> And it's actually a very simple message. We are the simplest and easiest way for a new user that is adopting Kubernetes as an architectural pattern, to get started with existing applications that they have, on the infrastructure that they have. Number one. And, for the savvy teams, our technology helps you operate with greater scale, with constrained operations teams. Especially, with the economy being the way it is, people are not going to get a lot more budget to go hire a lot more people, right. So, that all of them are being asked to do more with less. And, our team, our technology, and our teams, help you do more with less. >> I was talking with Phil Estes last night from AWS. He's here, he is one of their engineer open source advocates. He's always on the ground pumping up AWS. They've had great success, Amazon Web Services, with their EKS. A lot of people adopting clusters on the cloud and on-premises. But Amazon's doing well. You guys have, I think, a relationship with AWS. What's that, If I'm an Amazon customer, how do I get involved with Platform9? What's the hook? Where's the value? What's the product look like? >> Yeah, so, and it kind of goes back towards the point we spoke about, which is, Kubernetes is going to increasingly get commoditized. So, customers are going to find the right home whether it's hyperscalers, EKS, AKS, GKE, or their own infrastructure, to run Kubernetes. And, so, where we want to be at, is, with a project like Arlon, Sirish spoke about the barbell strategy, on one end there is these advanced Kubernetes users, majority of them are running Kubernetes on AKS, right? Because, that was the easiest platform that they found to get started with. So, now, they have a challenge of running these 50 to 100 clusters across various regions of Amazon, across their DevTest, their staging, their production. And, that results in a level of chaos that these DevOps or platform... >> So you come in and solve that. >> That is where we come in and we solve that. And it, you know, Amazon or EKS, doesn't give you tooling to solve that, right. It makes it very easy for you to create those number of clusters. >> Well, even in one hyperscale, let's say AWS, you got regions and locations... >> Exactly >> ...that's kind of a super cloud problem, we're seeing, opportunity problem, and opportunity is that, on Amazon, availability zones is one thing, but, now, also, you got regions. >> That is absolutely right. You're on point John. And the way we solve it, is by using infrastructure as a code, by using GitOps principles, right? Where you define it once, you define it in a yaml file, you define exactly how for your DevTest environment you want your entire infrastructure to look like, including EKS. And then you stamp it out. >> So let me, here's an analogy, I'll throw out this. You guys are like, someone learns how to drive a car, Kubernetes clusters, that's got a couple clusters. Then once they know how to drive a car, you give 'em the sports car. You allow them to stay on Amazon and all of a sudden go completely distributed, Edge, Global. >> I would say that a lot of people that we meet, we feel like they're figuring out how to build a car with the kit tools that they have. And we give them a car that's ready to go and doesn't require them to be trying to... ... they can focus on driving the car, rather than trying to build the car. >> You don't want people to stop, once they get the progressions, they hit that level up on Kubernetes, you guys give them the ability to go much bigger and stronger. >> That's right. >> To accelerate that applications. >> Building a car gets old for people at a certain point in time, and they really want to focus on is driving it and enjoying it. >> And we got four right behind us, so, we'll get them involved. So that's... >> But, you're not reinventing the wheel. >> We're not at all, because, what we are building is two very, very differentiated solutions, right. One, is, we're the simplest and easiest way to build and run Cloud Native private clouds. And, this is where the operational complexity of trying to do it yourself. You really have to be a car builder, to be able to do this with our Platform9. This is what we do uniquely that nobody else does well. And, the other end is, we help you operate at scale, in the hyperscalers, right. Those are the two problems that I feel, whether you're on-prem, or in the cloud, these are the two problems people face. How do you run a private cloud more easily, more efficiently? And, how do you govern at scale, especially in the public clouds? >> I want to get to two more points before we run out of time. Arlon and Argo CD as a service. We previously mentioned up coming into KubeCon, but, here, you guys couldn't be more relevant, 'cause Intuit was on stage on the keynote, getting an award for their work. You know, Argo, it comes from Intuit. That ArgoCon was in Mountain View. You guys were involved in that. You guys were at the center of all this super cloud action, if you will, or open source. How does Arlon fit into the Argo extension? What is Argo CD as a service? Who's going to take that one? I want to get that out there, because, Arlon has been talked about a lot. What's the update? >> I can talk about it. So, one of the things that Arlon uses behind the scenes, is it uses Argo CD, open source Argo CD as a service, as its key component to do the continuous deployment portion of its entire, the infrastructure management story, right. So, we have been very strongly partnering with Argo CD. We, really know and respect the Intuit team a lot. We, as part of this effort, in 5.6 release, we've also put out Argo CD as a service, in its GA version, right. Because, the power of running Arlon along with Argo CD as a service, in our mind, is enabling you to run on one end, your infrastructure as a scale, through GitOps, and infrastructure as a code practices. And on the other end, your entire application fleet, at scale, right. And, just marrying the two, really gives you the ability to perform that automation that we spoke about. >> But, and avoid the problem of sprawl when you have distributed teams, you have now things being bolted on, more apps coming out. So, this is really solves that problem, mainly. >> That is exactly right. And if you think of it, the way those problems are solved today, is, kind of in disconnected fashion, which is on one end you have your CI/CD tools, like Argo CD is an excellent one. There's some other choices, which are managed by a separate team to automate your application delivery. But, that team, is disconnected from the team that does the infrastructure management. And the infrastructure management is typically done through a bunch of Terraform scripts, or a bunch of ad hoc homegrown scripts, which are very difficult to manage. >> So, Arlon changes sure, as they change the complexity and also the sprawl. But, that's also how companies can die. They're growing fast, they're adding more capability. That's what trouble starts, right? >> I think in two ways, right. Like one is, as Madhura said, I think one of the common long-standing problems we've had, is, how do infrastructure and application teams communicate and work together, right. And, you've seen Argo's really get adopted by the application teams, but, it's now something that we are making accessible for the infrastructure teams to also bring the best practices of how application teams are managing applications. You can now use that to manage infrastructure, right. And, what that's going to do is, help you ultimately reduce waste, reduce inefficiency, and improve the developer experience. Because, that's what it's all about, ultimately. >> And, I know that you just released 5.6 today, congratulations on that. Any customer feedback yet? Any, any customers that you've been able to talk to, or have early access? >> Yeah, one of our large customers is a large SaaS retail company that is B2C SaaS. And, their feedback has been that this, basically, helps them bring exactly what I said in terms of bring some of the best practices that they wanted to adopt in the application space, down to the infrastructure management teams, right. And, we are also hearing a lot of customers, that I would say, large scale public cloud users, saying, they're really struggling with the complexity of how to tame the complexity of navigating that landscape and making it consumable for organizations that have thousands of developers or more. And that's been the feedback, is that this is the first open source standard mechanism that allows them to kind of reuse something, as opposed to everybody feels like they've had to build ad hoc solutions to solve this problem so far. >> Having a unified infrastructure is great. My final question, for me, before I end up, for Lisa to ask her last question is, if you had to explain Platform9, why you're relevant and cool today, what would you say? >> If I take that? I would say that the reason why Platform9, the reason why we exist, is, putting together a cloud, a hybrid cloud strategy for an enterprise today, historically, has required a lot of DIY, a lot of building your own car. Before you can drive a car, or you can enjoy the car, you really learn to build and operate the car. And that's great for maybe a 100 tech companies of the world, but, for the next 10,000 or 50,000 enterprises, they want to be able to consume a car. And that's why Platform9 exists, is, we are the only company that makes this delightfully simple and easy for companies that have a hybrid cloud strategy. >> Why you cool and relevant? How would you say it? >> Yeah, I think as Kubernetes becomes mainstream, as containers have become mainstream, I think automation at scale with ease, is going to be the key. And that's exactly what we help solve. Automation at scale and with ease. >> With ease and that differentiation. Guys, thank you so much for joining me. Last question, I guess, Madhura, for you, is, where can Devs go to learn more about 5.6 and get their hands on it? >> Absolutely. Go to platform9.com. There is info about 5.6 release, there's a press release, there's a link to it right on the website. And, if they want to learn about Arlon, it's an open source GitHub project. Go to GitHub and find out more about it. >> Excellent guys, thanks again for sharing what you're doing to really deliver Cloud Native at Scale in a differentiated way that adds ostensible value to your customers. John, and I, appreciate your insights and your time. >> Thank you for having us. >> Thanks so much >> Our pleasure. For our guests and John Furrier, I'm Lisa Martin. You're watching theCUBE Live from Detroit, Michigan at KubeCon CloudNativeCon 2022. Stick around, John and I will be back with our next guest. Just a minute. (light synth outro music)

>>Hello and welcome back to the live coverage of the Cube here. Live in Detroit, Michigan for Cub Con, our seventh year covering all seven years. The cube has been here. M John Fur, host of the Cube, co-founder of the Cube. I'm here with Lisa Mart, my co-host, and our new host, Savannah Peterson. Great to see you guys. We're wrapping up day one of three days of coverage, and our guest analyst is Sario Wall, who's the cube analyst who's gonna give us his report. He's been out all day, ear to the ground in the sessions, peeking in, sneaking in, crashing him, getting all the data. Great to see you, Sarvi. Lisa Savannah, let's wrap this puppy up. >>I am so excited to be here. My first coupon with the cube and being here with you and Lisa has just been a treat. I can't wait to hear what you have to say in on the report side. And I mean, I have just been reflecting, it was last year's coupon that brought me to you, so I feel so lucky. So much can change in a year, folks. You never know where you're be. Wherever you're sitting today, you could be living your dreams in just a few >>Months. Lisa, so much has changed. I mean, just look at the past this year. Events we're back in person. Yeah. Yep. This is a big team here. They're still wearing masks, although we can take 'em off with a cube. But mask requirement. Tech has changed. Conversations are upleveling, skill gaps still there. So much has changed. >>So much has changed. There's so much evolution and so much innovation that we've also seen. You know, we started out the keynote this morning, standing room. Only thousands of people are here. Even though there's a mass requirement, the community that is CNCF Co Con is stronger than I, stronger than I saw it last year. This is only my second co con. But the collaboration, what they've done, their devotion to the maintainers, their devotion to really finding mentors for mentees was really a strong message this morning. And we heard a >>Lot of that today. And it's going beyond Kubernetes, even though it's called co con. I also call it cloud native con, which I think we'll probably end up being the name because at the end of day, the cloud native scaling, you're starting to see the pressure points. You're start to see where things are breaking, where automation's coming in, breaking in a good way. And we're gonna break it all down Again. So much going on again, I've overs gonna be in charge. Digital is transformation. If you take it to its conclusion, then you will see that the developers are running the business. It isn't a department, it's not serving the business, it is the business. If that's the case, everything has to change. And we're, we're happy to have Sarib here with us Cube analysts on the badge. I saw that with the press pass. Well, >>Thank you. Thanks for getting me that badge. So I'm here with you guys and >>Well, you got a rapport. Let's get into it. You, I >>Know. Let's hear what you gotta say. I'm excited. >>Yeah. Went around, actually attend some sessions and, and with the analysts were sitting in, in the media slash press, and I spoke to some people at their booth and the, there are a few, few patterns, you know, which are, some are the exaggeration of existing patterns or some are kind of new patterns emerging. So things are getting complex in open source. The lawn more projects, right. They have, the CNCF has graduated some projects even after graduation, they're, they're exploring, right? Kubernetes is one of those projects which has graduated. And on that front, just a side note, the new projects where, which are entering the cncf, they're the, we, we gotta see that process and the three stages and all that stuff. I tweeted all day long, if you wanna know what it is, you can look at my tweets. But when I will look, actually write right on that actually after, after the show ends, what, what I saw there, these new projects need to be curated properly. >>I think they need to be weed. There's a lot of noise in these projects. There's a lot of overlap. So the, the work is cut out for CNCF folks, by the way. They're sort of managerial committee or whatever you call that. The, the people who are leading it, they're try, I think they're doing their best and they're doing a good job of that. And another thing actually, I really liked in the morning's keynote was that lot of women on the stage and minorities represented. I loved it, to be honest with you. So believe me, I'm a minority even though I'm Indian, but from India, I'm a minority. So people who have Punjab either know that I'm a minority, so I, I understand their pain and how hard it is to, to break through the ceiling and all that. So I love that part as well. Yeah, the >>Activity is clear. Yeah. From day one. It's in the, it's in the dna. I mean, they'll reject anything that the opposite >>Representation too. I mean, it's not just that everyone's invited, it's they're celebrated and that's a very big difference. Yeah. It's, you see conferences offer discounts for women for tickets or minorities, but you don't necessarily see them put them running where their mouth is actually recruit the right women to be on stage. Right. Something you know a little bit about John >>Diversity brings better outcomes, better product perspectives. The product is better with all the perspectives involved. Percent, it might go a little slower, maybe a little debates, but it's all good. I mean, it's, to me, the better product comes when everyone's in. >>I hope you didn't just imply that women would make society. So >>I think John men, like slower means a slower, >>More diversity, more debate, >>The worst. Bringing the diversity into picture >>Wine. That's, that's how good groups, which is, which is >>Great. I mean, yeah, yeah, >>Yeah, yeah. I, I take that mulligan back and say, hey, you knows >>That's >>Just, it's gonna go so much faster and better and cheaper, but that not diversity. Absolutely. >>Yes. Well, you make better products faster because you have a variety >>Of perspectives. The bigger the group, there's more debate. More debate is key. But the key to success is aligning and committing. Absolutely. Once you have that, and that's what open sources has been about for. Oh God, yeah. Generations >>Has been a huge theme in the >>Show generations. All right, so, so, >>So you have to add another, like another important, so observation if you will, is that the security is, is paramount right. Requirement, especially for open source. There was a stat which was presented in the morning that 60% of the projects in under CNCF have more vulnerabilities today than they had last year. So that was, That's shocking actually. It's a big jump. It's a big jump. Like big jump means jump, jump means like it can be from from 40 to 60 or or 50 or 60. But still that percentage is high. What, what that means is that lot more people are contributing. It's very sort of di carmic or ironic that we say like, Oh this project has 10,000 contributors. Is that a good thing? Right. We do. Do we know the quality of that, where they're coming from? Are there any back doors being, you know, open there? How stringent is the process of rolling those things, which are being checked in, into production? You know, who is doing that? I've >>Wondered about that. Yeah. The quantity, quality, efficacy game. Yes. And what a balance that must be for someone like CNCF putting in the structure to try and >>That's >>Hard. Curate and regulate and, and you know, provide some bumpers on the bowling lane, so to speak, of, of all of these projects. Yeah. >>Yeah. We thought if anybody thought that the innovation coming from, or the number of services coming from AWS or Google Cloud or likes of them is overwhelming, look at open source, it's even more >>Overwhelming. What's your take on the supply chain discussion? More code more happening. What are you hearing there? >>The supply chain from the software? Yeah. >>Supply chain software, supply chain security pays. Are people talking about that? What are you >>Seeing? Yeah, actually people are talking about that. The creation, the curation, not creation. Curation of suppliers of software I think is best done in the cloud. Marketplaces Ive call biased or what, you know, but curation of open source is hard. It's hard to know which project to pick. It's hard to know which project will pan out. Many of the good projects don't see the day light of the day, but some decent ones like it becomes >>A marketing problem. Exactly. The more you have out there. Exactly. The more you gotta get above the noise. Exactly. And the noise echo that. And you got, you got GitHub stars, you got contributors, you have vanity metrics now coming in to this that are influencing what's real. But sometimes the best project could have smaller groups. >>Yeah, exactly. And another controversial thing a little bit I will say that is that there's a economics of the practitioner, right? I usually talk about that and economics of the, the enterprise, right? So practitioners in our world, in software world especially right in systems world, practitioners are changing jobs every two to three years. And number of developers doubles every three years. That's the stat I've seen from Uncle Bob. He's authority on that software side of things. Wow. So that means there's a lot more new entrance that means a lot of churn. So who is watching out for the enterprise enterprises economics, You know, like are we creating stable enterprises? How stable are our operations? On a side note to that, most of us see the software as like one band, which is not true. When we talk about all these roles and personas, somebody's writing software for, for core layer, which is the infrastructure part. Somebody's writing business applications, somebody's writing, you know, systems of bracket, some somebody's writing systems of differentiation. We talk about those things. We need to distinguish between those and have principle based technology consumption, which I usually write about in our Oh, >>So bottom line in Europe about it, in your opinion. Yeah. What's the top story here at coupon? >>Top story is >>Headline. Yeah, >>The, the headline. Okay. The open source cannot be ignored. That's a headline. >>And what should people be paying attention to if there's a trend coming out? See any kind of trends coming out or any kind of signal, What, what do you see that people should pay attention to here? The put top >>Two, three things. The signal is that, that if you are a big shop, like you'd need to assess your like capacity to absorb open source. You need to be certain size to absorb the open source. If you are below that threshold, I mean we can talk about that at some other time. Like what is that threshold? I will suggest you to go with the managed services from somebody, whoever is providing those managed services around open source. So manage es, right? So from, take it from aws, Google Cloud or Azure or IBM or anybody, right? So use open source as managed offering rather than doing it yourself. Because doing it yourself is a lot more heavy lifting. >>I I, >>There's so many thoughts coming, right? >>Mind it's, >>So I gotta ask you, what's your rapport? You have some swag, What's the swag look >>Like to you? I do. Just as serious of a report as you do on the to floor, but I do, so you know, I come from a marketing background and as I, I know that Lisa does as well. And one of the things that I think about that we touched on in this is, is you know, canceling the noise or standing out from the noise and, and on a show floor, that's actually a huge challenge for these startups, especially when you're up against a rancher or companies or a Cisco with a very large budget. And let's say you've only got a couple grand for an activation here. Like most of my clients, that's how I ended up in the CU County ecosystem, was here with the A client before. So there actually was a booth over there and I, they didn't quite catch me enough, but they had noise canceling headphones. >>So if you just wanted to take a minute on the show floor and just not hear anything, which I thought was a little bit clever, but gonna take you through some of my favorite swag from today and to all the vendors, you know, this is why you should really put some thought into your swag. You never know when you're gonna end up on the cube. So since most swag is injection molded plastic that's gonna end up in the landfill, I really appreciate that garden has given all of us a potable plant. And even the packaging is plantable, which is very exciting. So most sustainable swag goes to garden. Well done >>Rep replicated, I believe is their name. They do a really good job every year. They had some very funny pins that say a word that, I'm not gonna say live on television, but they have created, they brought two things for us, yet it's replicated little etch sketch for your inner child, which is very nice. And given that we are in Detroit, we are in Motor City, we are in the home of Ford. We had Ford on the show. I love that they have done the custom K eight s key chains in the blue oval logo. Like >>Fords right behind us by the way, and are on you >>Interviewed, we had 'em on earlier GitLab taking it one level more personal and actually giving out digital portraits today. Nice. Cool. Which is quite fun. Get lap house multiple booths here. They actually IPOed while they were on the show floor at CubeCon 2021, which is fun to see that whole gang again. And then last but not least, really embracing the ship wheel logo of a Kubernetes is the robusta accrue that is giving out bucket hats. And if you check out my Twitter at sabba Savvy, you can see me holding the ship wheel that they're letting everyone pose with. So we are all in on Kubernetes. That cove gone 2022, that's for sure. Yeah. >>And this is something, day one guys, we've got three. >>I wanna get one of those >>Hats. We we need to, we need a group photo >>By the end of Friday we will have a beverage and hats on to sign off. That's, that's my word. If I can convince John, >>Don, what's your takeaway? You guys did a great kind of kickoff about last week or so about what you were excited about, what your thoughts were going to be. We're only on day one, There's been thousands of people here, we've had great conversations with contributors, the community. What's your take on day one? What's your, what's your tagline? >>Well, Savannah and I had at we up, we, we were talking about what we might see and I think we, we were right. I think we had it right. There's gonna be a lot more people than there were last year. Okay, check. That's definitely true. We're in >>Person, which >>Is refreshing. I was very surprised about the mask mandate that kind of caught me up guard. I was major. Yeah. Cause I've been comfortable without the mask. I'm not a mask person, but I had to wear it and I was like, ah, mask. But I understand I support that. But whatever. It's >>Corporate travel policy. So you know, that's what it is. >>And then, you know, they, I thought that they did an okay job with the gates, but they wasn't slow like last time. But on the content side, definitely Kubernetes security, top line headline, Kubernetes at scale security, that's, that's to me the bumper sticker top things to pay attention to the supply chain and the role of docker and the web assembly was a surprise. You're starting to see containers ecosystem coming back to, I won't say tension growth in the functionality of containers cuz they have to solve the security problem in the container images. Okay, you got scanning technology so it's a little bit in the weeds, but there's a huge movement going on to fix that problem to scale it so it's not a problem area contain. And then Dr sent a great job with productivity interviews. Scott Johnston over a hundred million in revenue so far. That's my number. They have not publicly said that. That's what I'm reporting from sources extremely well financially. And they, and they love their business model. They make productivity for developers. That's a scoop. That's new >>Information. That's a nice scoop we just dropped there on the co casually. >>You're watching that. Pay attention to that. But that, that's proof. But guess what, Red Hat's got developers too. Yes. Other people have to, So developers gonna go where it's the best. Yeah. Developers are voting with their code, they're voting with their feet. You will see the winners with the developers and that's what we've talked about. >>Well and the companies are catering to the developers. Savannah and I had a great conversation with Ford. Yeah. You saw, you showed their fantastic swag was an E for Ev right behind us. They were talking about the, all the cultural changes that they've really focused on to cater towards the developers. The developers becoming the influencers as you say. But to see a company that is as, as historied as Ford Motor Company and what they're doing to attract and retain developer talent was impressive. And honestly that surprised me. Yeah. >>And their head of deb relations has been working for, for, for 29 years. Which I mean first of all, most companies on the show floor haven't been around for 29 years. Right. But what I love is when you put community first, you get employees to stick around. And I think community is one of the biggest themes here at Cuco. >>Great. My, my favorite story that surprised me and was cool was the Red Hat Lockheed Martin interview where they had edge deployments with micro edge, >>Micro shift, >>Micro >>Shift, new projects under, there's, there are three new projects under, >>Under that was so, so cool because it was an edge story in deployment for the military where lives are on the line, they actually had it working. That is a real world example of Kubernetes and tech orchestrating to deploy the industrial edge. And I think that's proof in my mind that Kubernetes and this ecosystem is gonna move faster through this next wave of growth. Because once things start clicking, you get hybrid on premise to super cloud and edge. That was, that was my favorite cause it was real. That was real >>Story that it can make is literally life and death on the battlefield. Yeah, that was amazing. With what they're doing and what >>They're talking check out the Lockheed Martin Red Hat edge story on Silicon Angle and then a press release all pillar. >>Yeah. Another actually it's impressive, which we knew this which is happening, but I didn't know that it was happening at this scale is the finops. The finops is, I saw your is a discipline which most companies are adopting bigger companies, which are spending like hundreds of millions dollars in cloud average. Si a team size of finops for finops is seven people. And average number of tools is I think 3.5 or around 3.7 or something like that. Average number of tools they use to control the cost. So finops is a very generic term for years. It's not financial operations, it's the financial operations for the cloud cost, you know, containing the cloud costs. So that's a finops that is a very emerging sort of discipline >>To keep an eye on. And well, not only is that important, I talked to, well one of the principles over there, it's growing and they have real big players in that foundation. Their, their events are highly attended. It's super important. It's just, it's the cost side of cloud. And, and of course, you know, everyone wants to know what's going on. No one wants to leave there. Their Amazon on Yeah, you wanna leave the lights on the cloud, as we always say, you never know what the bill's gonna look like. >>The cloud is gonna reach $3 billion in next few years. So we might as well control the cost there. Yeah, >>It was, it was funny to get the reaction I found, I don't know if I was, how I react, I dunno how I felt. But we, we did introduce Super Cloud to a couple of guests and a, there were a couple reactions, a couple drawn. There was a couple, right. There was a couple, couple reactions. And what I love about the super cloud is that some people are like, oh, cringing. And some people are like, yeah, go. So it's a, it's a solid debate. It is solid. I saw more in the segments that I did with you together. People leaning in. Yeah. Super fun. We had a couple sum up, we had a couple, we had a couple cringes, I'll say their names, but I'll go back and make sure I, >>I think people >>Get 'em later. I think people, >>I think people cringe on the, on the term not on the idea. Yeah. You know, so the whole idea is that we are building top of the cloud >>And then so I mean you're gonna like this, I did successfully introduce here on the cube, a new term called architectural list. He did? That's right. Okay. And I wanna thank Charles Fitzgerald for that cuz he called super cloud architectural list. And that's exactly the point of super cloud. If you have a great coding environment, you shouldn't have to do an architecture to do. You should code and let the architecture of the Super cloud make it happen. And of course Brian Gracely, who will be on tomorrow at his cloud cast said Super Cloud enables super services. Super Cloud enables what Super services, super service. The microservices underneath the covers have to be different. High performing, automated. So again, the debate and Susan, the goal is to keep it open. And that's our, that's our goal. But we had a lot of fun with that. It was fun to poke the bear a little bit. So >>What is interesting to see just how people respond to it too, with you throwing it out there so consistently, >>You wanna poke the bear, get a conversation going, you know, let let it go. We'll see, it's been positive so far. >>There, there I had a discussion outside somebody who is from Ford but not attending this conference and they have been there for a while. I, I just some moment hit like me, like I said, people, okay, technologists are horizontal, the codes are horizontal. They will go from four to GM to Chrysler to Bank of America to, you know, GE whatever, you know, like cross vertical within vertical different vendors. So, but the culture of a company is local, right? Right. Ford has been building cars for forever. They sort of democratize it. They commercialize it, right? But they have some intense culture. It's hard to change those cultures. And how do we bring in the new thinking? What is, what approach that should be? Is it a sandbox approach for like putting new sensors on the car? They have to compete with te likes our Tesla, right? Yeah. But they cannot, if they are afraid of deluding their existing market or they're afraid of failure there, right? So it's very >>Tricky. Great stuff. Sorry. Great to have you on as our cube analyst breaking down the stories. We'll document that, that we'll roll out a post on it. Lisa Savannah, let's wrap up the show for day one. We got day two and three. We'll start with you. What's your summary? Quick bumper sticker. What's today's show all about? >>I'm a community first gal and this entire experience is about community and it's really nice to see the community come together, celebrate that, share ideas, and to have our community together on stage. >>Yeah. To me, to me it was all real. It's happening. Kubernetes cloud native at scale, it's happening, it's real. And we see proof points and we're gonna have faster time to value. It's gonna accelerate faster from here. >>The proof points, the impact is real. And we saw that in some amazing stories. And this is just a one of the cubes >>Coverage. Ib final word on this segment was well >>Said Lisa. Yeah, I, I think I, I would repeat what I said. I got eight, nine years back at a rack space conference. Open source is amazing for one biggest reason. It gives the ability to the developing nations to be at somewhat at par where the dev develop nations and, and those people to lift up their masses through the automation. Cuz when automation happens, the corruption goes down and the economy blossoms. And I think it's great and, and we need to do more in it, but we have to be careful about the supply chains around the software so that, so our systems are secure and they are robust. Yeah, >>That's it. Okay. To me for SAR B and my two great co-host, Lisa Martin, Savannah Peterson. I'm John Furry. You're watching the Cube Day one in, in the Books. We'll see you tomorrow, day two Cuban Cloud Native live in Detroit. Thanks for watching.

>> Speaker: From around the Globe, it's theCUBE with digital coverage of DockerCon Live 2020, brought to you by Docker and its ecosystem partners. >> Hello, how you doing? Welcome to DockerCon. We're kind of halfway through now, I guess. Thank you for joining us on this session. So my name is Elton, I'm a Docker Captain. And I'm joined by Julie who was also a Docker Captain. This is actually this session was Julie's idea. We were talking about this learning of Docker and how it's a light bulb moment for lots of people. But Julie, she came up with this great idea for DevOps. So I'll let Julie introduce herself, and tell you a bit about what we're going to talk about. >> Thanks, Elton. So I'm Julie Lerman. I'm a Software Coach. I'm a developer. I've been a developer for over 30 years. I work independently and I'm a Docker captain. Also a Microsoft Regional Director. I wouldn't let them put it on there, because it makes people think I work for Microsoft but I don't. (he laughs) >> Yeah, so it's a weird title. So the Microsoft ID the Regional Director, it's like a kind of Uber, MVP. So I'm an MVP. And that's fine. That's just like a community recognition, just like you get with a Docker captain. So MVP is kind of like the micro version, Julie's MVP too. But then you get the Regional Director which is something that MVP get. >> Doesn't matter. >> I'm not surprised Julie. >> Stop, a humble man. (he laughs) >> We've been using Docker for years 10 years between. >> You probably, how long ago was your Docker aha moment? >> So 2014 I first started using Docker, so I was working on a project, where I was assaulting for a team who were building an Android tablet, and they were building the whole thing, so they Spec out the tablet, they got a bill over in the far East. They were building their own OS their own app to run on and of course all that stacks within it. But they was all talking to the services that were running in the power they wanted to use as your for that and .NET that was on-prem, though that technology historically . So I came in to do the .NET stuff is running in as your, but I got really friendly with the Linux guys. It was very DevOps, it was one team who did the whole thing. And they were using Docker for that their build tools, and for have the and the CI tools, and they were running their own get server and it was all in. >> Already until 2014. That's pretty cool. >> Yeah, pretty early introduction to it. And it was super cool. So I'd always been interested in Linux, but never really dug into it. Because the entry bar was so high runs nothing in it. So you read about this great open source project, and then you go and look at the documentation and you have to download the source code and build it and it's like, well, I'm not going to be doing that stuff. And then Docker came along. I do Docker run. (he laughs) >> Well, I would say it was a little definitely delayed from that. I'm still thinking Wait, when you first started saying that this company was building their own android system, you start thinking, they're building software, but no, they weren't building everything, which is pretty amazing. So, I have to say it took me quite a while, but I was also behind on understanding virtual machines. (both laughs) So, Docker comes along, and I have lots of friends who are using it, I spent a lot of time with Michelle Noorali this Monday, and she's big container person. And most of the people I hear talking about Docker are really doing DevOps, which is not my thing. As a developer, I always just said, let somebody else do that stuff. I want to code an architect and do things like that. And I also do a lot of data work. I'm not like a big data person doing analytics. Or I'm not a DBA. I'm more very involved in getting data in and out of applications. So my aha moment, I would say was like, four years ago, after Microsoft moved SQL Server over to Linux, and then put it inside a Docker image. So that was my very first experience, just saying, oh, what does this do and I downloaded the image. And Docker run. And then like literally I was like, holy smokes. SQL Servers already installed. The containers up like that, and then it's got to run a couple of Bashan SQL scripts to get all the system tables, and databases and things like that. So that's another 15 seconds. But that was literally for me. The not really aha, it was more like OMG, and I'll keep the EFF out just to keep it clean here. It was my OMG moment with Docker. So getting that start, then I worked with the SQL Server image and container and did some different things, with that in applications. And then eventually, expanded my knowledge out bit by bit, and got a deeper understanding of it and tried more things. So I get to a comfort level and then add to it and add to it. >> Yeah. And I think that the great thing about that is that as you're going on that journey that aha moments keep coming, along we had another aha moment this week, with the new announcement that you can use your Docker compose files, and use your Docker commands to spin stuff up running in as your container instances. So like that you've kept up that learning journey is there if you want to go down, How do I take my monolithic application, and break up into pieces and run those in containers? Like suddenly the fact that you can just glue all these things together in run it on one platform, and manage everything in the same way? And these light bulbs keep on coming. So, you've seen the modernization things that people are doing that's a lot of the work that I do now, and taking these big applications, you just write a Docker file, and you've got your 15 year old .NET application running in the container. And you can run that in the cloud with no changes to code, and not see them. But that's super powerful for people. >> And I think one of the really important things, especially for people like you and I, who are also teachers, and is to try to really remember that moment, because I know a lot of times, when people are deeply expert in something it they forget how hard it was, or what it felt like not to understand it that context. So I still have held on to that. So when I talk, I like to do introduction, I like to help people get that aha moment. And then I say, Okay, now go on to the, they're really expert people. You're ready to learn more, but it's really important to especially, maybe we're teachers, conference speakers, book authors, pluralsight, etc. But lots of other people, who are working on teams they might already be somebody who's gotten there with Docker, and they want to help their teammates understand Docker. So I think it's really important to, for everybody who wants to share that to kind of have a little empathy, and remember what that was like, and understand that sometimes it just takes explaining it a different way explaining maybe, just tweaking your expression, or some of the words or your analogies. >> Yeah, that's definitely true. And you often find this it's a technology, that people really become affectionate for, they have a real deep feeling for documents, once they start using it, and you get these internal champions in companies who say, "This is the stuff I've been using, I've been using this at home or whatever." And they want to bring it into their project, and it's pretty cool to be able to say to them this is, take me on the same journey that you've been on, or you've been on a journey, which was probably slightly more investment for you, because you had to learn from scratch. But now you can relay that back into your own project. So you can take, you don't have to take everyone from scratch like you did. You can say, here's the Docker file for our own application. This is how it works. And bringing things into the terms that people are using everyday , I think is something that's super powerful. Why because you're completely strange. (he laughs) >> Oh, I was being really cool about your video. (both laughs) Maybe it's just how it streaming back to me. I think the teacher thing again, like we'll work a little harder and, bump our knees and stub our toes, or tear our hair out or whatever pain we have to go through, with that learning because, it's also kind of obsessive. And you can steer people away from those things, although it's also helpful to let them be aware like this might happen, and if it does, it's because of this. But that's not the happy path. >> Yeah, absolutely. And I think, it's really interesting talking to people about the time you're trying to get to what problem are they trying to solve? It's interesting, you talk about DevOps there, and how that sort of not an area, that you've done a lot of stuff in. Writing a couple of organizations, whether they're really trying hard to move that model, and trying to break down the barriers, between the team who build the software, and the team who run the software, but they have those barriers, but 20 years, it's really hard to write that stuff down. And it's a big cultural shift, it needs a lot of investment. But if you can make a technological change as well, if you can get people using the same tools, the same languages, the same processes to do things, that makes it so much easier. Like now my operators are using Docker files, on there and the security team are going into the Docker file and cozening it, or DevOps team or building up my compose file, and everyone's using the same thing, it really helps a lot, to bind people together to work on the same area. >> I also do a lot of work in domain Dave Vellante design, and that whole idea of collaboration, and bringing together teams, that don't normally work together, and bringing them together, and enabling them to find a way to collaborate giving them tools for collaboration, just like what you're saying with, having the same terms and using the same tools. So that's really powerful. You gave me a great example of one of your clients, aha moments with Docker. Do you remember which that was? The money yes, it's a very powerful Aha. >> Yes. >> She cherish that. >> The company that I've worked for before, when I was doing still get thought that I can sort a thing, and they knew I'd go into containers. I was working for Docker at the time. And I went in just as if I wasn't a sales pitch or anything, I was just as a favor to talk to them about what containers would look like if payments, their operation, big heavy Windows users, huge number of environment, lots of VMs that are all running stuff, to get the isolation, and give them what they needed. And I did this presentation of IT. So it wasn't a technical thing. It was very high level, it was about how containers kind of work. And I'm fundamentally a technical person, so I probably have more detail in there. And then you would get from a sales pitch, but it was very much about, you can take your applications, you can wrap them up the running these things for containers, you still get the isolation, you can run loads more of them on the same hardware that you've got, and you don't pay a Windows license each of those containers, you pay a license for the server that the right one. >> That's it, that's the moment. >> And the head of IT said that's going to save us millions of dollars. (he laughs) And that was his aha moment. >> I'm going to wrap that into my conference session, about getting to the Docker, for sure getting that aha moment. My experience is less that but wow, I mean, that's so powerful. When you're talking to come C level people about making those kinds of changes, because you need to have their buy in. So as a developer and somebody who works with developers, and that's kind of my audience, my experience more has been, when I'm giving conference presentations, and I'll start out in a room of people, and I have to say, when I'm at .NET focus conference, I find that the not there yet with Docker. Part of the audience is a big one. So I kind of do a poll at the beginning of the talk. Who's heard of Docker, obviously, they're in the room, but curious because you still don't really understand it. And that's usually a bulk of the room. And what I like to ask at the end is, of all of you that, that first group, like, do you feel like you get it now, like you just get what it is and what it does, as opposed to I don't know what this thing is. It's for rocket scientists. Is that's how I felt about it. I was like, I'm just a developer. It wasn't my thing. But now, I'm still not doing DevOps, I use Docker as a really important tool, during development and test and that's actually one of it I'm going to be talking about that. But it's my session a little later. Oh, like the next hour. It's about using Docker, that my aha Docker, SQL Server, in an image and but using that in Dave Vellante, it's not about the DevOps and the CI/CD and Kubernetes, I can spell it. (he laughs) Especially when I get to say k eight s, Like I even know the cool Lingo (mumbles) on Twitter. (he laughs) >> I think that's one of the cool things about this technology stack in particular, I think to get the most out of it, you need to dig in really light if you want to, if you're looking at doing this stuff in production, if you're attracted by the fact that I can have a managed container platform in anytime. And I can deploy my app, everywhere using the same set of things that compose files or humidity files or whatever. And if you really want to take advantage of that, you kind of have to get down to the principles understand all go on a proper kind of learning journey. But if you don't want to do that, you can kind of stop wherever it makes sense for you. So like even when I'm talking to different audiences, is a lot strangely enough, I did a pool size large bin this morning. It was quite a specific topic. It was about building applications in containers. So is about using containers, to compile your app and then package it, so you can build anywhere. But even a session like that, the first maybe two minutes, I give a lightning quick overview, of what containers are and how you use them. Here's exactly like you say, people will come to a session, if it's got Docker or humanities in the title. But if they don't have the entry requirements. They've never really used this stuff. And we were up here and it's a big dump for them. So I try and always have that introductory slide. >> I had to do that on the fly. >> Sorry. >> I've done that on the fly in conference, because yes, doing like, ASP.NET Core with Entity Framework and containers. And, 80% of the room, really didn't know anything about Docker. So, instead of talking like five minutes about Docker and then demoing the rest, I ended up spending more time talking about Docker, to make sure everybody was really you could tell that difference when they're like oh, like that they understood enough, in order to be follow along and understand the value of what it was that I was there to show, about it in that core, I'm also this is making me remember that first time I actually use Docker compose, because it was a while, I was just using the SQL Server, Docker image, in on my development machine for quite a while. And because I wasn't deploying, I was learning and exploring and so I was on my development machine, so I didn't need to do anything else. So the first time I really started orchestrating, that was yet another aha moment. But I was ready for it then. I think you know if you start with Docker compose and you don't haven't done the other, maybe I would write but I was ready, because I'd already gotten used to using the tooling and, really understanding what was going on with containers. Then that Docker compose was like yeah. (he laughs) >> It's just the next one, in the line is a great comment actually in the chat about someone in the chat. >> From chat? >> Yeah, from Steve saying, that he could see there would be an aha moment for his about security. And actually that's absolutely, it's so when security people, first want to get their head around containers, they get worried that if someone can compromise the app in the container, they might get a break out, and get to all the other containers. And suddenly, instead of having one VM compromised, you have 100 containers compromised. But actually, when you dig into it so much easier to get this kind of defense in depth, when you're building in containers, because you have your tape on an image that's owned by your team who produced the path, whether or not they will have their own images, that are built with best practices. You can sign your images, through your platform doesn't run anything that isn't signed, you have a full history of exactly what's in the source code is what's in production, there's all sorts of, ways you can layer on security that, attract that side of the audience. >> I've been looking at you this whole time, and like I forgot about the live chat. There's the live chat. (he laughs) There's Scott Johnston in live chat. >> Yes. >> People talking about Kubernetes and swarm. I'm scrolling through quickly to see if anybody's saying, well, my aha moment was. >> There was a good one. What was this one from Fatima earlier on, Maya was pointing out with almost no configuration onto a VM, and couldn't believe it never looked back on us. >> Yeah. >> That's exactly, on one command, if your image is mostly built, SaaS has some sensible defaults, it just all works. And everyone's (mumbles). >> Yeah, and the thing that I'm doing in my session is, what I love. the fact that for development team, Development Testing everybody on the team, and then again on up the pipeline to CI/CD. It's just a matter of, not only do you have your SaaS code, but in your SaaS code, you've got your Docker compose, and your Docker compose just makes sure, that you have the development environment that you need, all the frame, everything that you need is just there, without having to go out and find it and install it. >> There were no gap in a development environment with CI build the production. So I'm hearing, you don't hear but I can hear that we need to wrap up. >> Oh, yeah. >> Get yourself prepared for your next session, which everyone should definitely, I'll be watching everyone else do. So thanks everyone for joining. Thanks, Julie for a great idea for a conversation, was about 4050 we'll have a beer with and I would, I would Yeah. >> Yeah, we live many thousands of miles away from one another. >> Well, hopefully next year, there will be a different topic on how we can all meet some of you guys. >> And I do need to point out, the last time we were together, Elton, I got a copy of Alan's book and he signed it. (both laughs) And we took a picture of it. >> There are still more books on the stand >> Yeah, I know that's an old book, but it's the one that you signed. Thank you so much. >> Thanks everyone for joining and we'll enjoy the rest of the topic home. >> Bye. (soft music)

>> Live from San Francisco, it's theCUBE! Covering DockerCon 18, brought to you by Docker and it's ecosystem partners. >> Welcome back to theCUBE, I'm Lisa Martin with John Troyer we are live from DockerCon 2018 on a sunny day here in San Francisco at Moscone Center. Excited to welcome to theCUBE Chris Brown the Technical Marketing Manager at Nutanix, Chris welcome to theCUBE! >> Thank you so much for having me. >> So you've been with Nutanix for a couple years, so we'll talk about Nutanix and containers, you have a session control and automate your container journey with Nutanix. Talk to us about what you're gonna be talking about in the session, what's Nutanix's role in helping the customers get over this trepidation of containers? >> Yeah, definitely, and it's, it's a 20 minute session, so we've got a lot of information to cover there 'cause wanna go over a little bit about, you know, who Nutanix is from the beginning to end but, the main part I'm gonna be focusing on in that session is talking about how we, with our com product, can automate VMs and containers together and how we're moving towards being able to, you know, define you application in a blueprint and understand what you're trying to do with your application. You know, one of the things I always say is that nobody runs Sequel because they love running Sequel, they run Sequel to do something, and our goal with the com is to capture that something, what it depends on, what it relies on. Once we understand what this particular component is supposed to do in your application, we can change that, we can move that to another cloud, or we can move it to containers without losing that definition, and without losing its dependence on the other pieces of the infrastructure and exchange information back and forth. So we're talking a little bit about what we're doing today with com and where we're going with it to add Kubernetes support. >> Chris, we're sitting here in the ecosystem expo at DockerCon and your booth is busy, there's a lot of good activity. Are people coming up to you and asking, do they know Nutanix, do they understand who you are, do they just say oh you guys sell boxes? You know you're both a, you're a systems provider, you're a private cloud provider, and a hybrid-cloud provider, do people understand that, the crowd here, and what kinda conversations are you having? >> It's actually really interesting 'cause we're seeing a broad range of people, some customers are comin' up, or some people are coming up that they don't reali--they don't know that other pieces, places their company use Nutanix, but they wanted to learn more about us, so they've got some sort of initiative that you know, a lot of times it is around containers, around understanding, you know, they're starting to figure out, you know, how do we deploy this, how do we connect? You know, we've got something we wanna deploy here and there how do we do that in a scalable way? But we also have some that have no idea who we are and just comin' up like so you've got a booth and some awesome giveaways, (laughing) what do I have to do to get that, and what do you do? And you know, I really kinda summarize it as two main main groups of people that I've seen is, one of 'em is, the people who've been doing containers for forever, they know it, they've been doing it, they're very familiar with the command line, they're ret-- any gooey is too much gooey for them. And then we've got the people who are just getting started, they've kinda been told hey, containers are coming, we need to figure out how to do this, or we've got, we need to start figuring out our containers strategy. And so they're here to learn and figure out how to begin that. And so it's really interesting because those, the ones that are just getting started or just learning, we obviously help out a ton because the people who came before had to go through all the fire, all the configuration, all of the challenges, and figure out there own solutions where as we can, now we kinda come in, there's a little bit more opinionated example of how to do these things. >> So DockerCon, this year is the fifth DockerCon, they've got between five thousand and six thousand people, I was talking with John earlier and Steve Singh as well, that how I really impressed when I was leaving the general session, it was standing room only a sea of heads so they've got, obviously developers here right, sweet spot, IT folks, enterprise architects, and execs, you talked about Nutanix getting those the two polar opposite ends of the spectrum, the container lovers, the ones who are the experts, and the ones going I know I have to do this. I'm curious, what target audience are you talking to that goes hey I'm tasked with doing this, are those developers, are those IT folks, are you talking with execs as well, give us that mix. >> For the most part they are IT folks, you're artusional operators who are trying to figure out this new shift in technology and we have to talk to some developers, and it's actually been interesting to have speak with developers because you know, in general that's not, that hasn't been Nutanix's traditional audience, we've sold this product called infrastructure to develop. But developers, the few developers I've talked to have gotten really receptive and really excited about what we can do and how we can help them do their job faster by getting their IT people on board but for the most part it'd be traditional IT operators who're looking at this new technology and you know, givin' it kind of a little squinty eye, trying to figure out where it's going, because at the end of the day, with any shift in IT, there's never a time where something is completely sunset, I mean people are still using mainframes today, people will be using mainframes forever, people are just starting their virtualization journey today they're just going from bare metal to VMs, so, and then even with that shift, there's always something that gets left behind, so, they're trying to figure out how can we get used to this new container shift because at the end of the day not everything is gonna be containerized because there's just simply some things that won't be able to or they'll scope out the project and then it'll end up falling by the wayside or budget will go somewhere else. So they're trying to figure out how they can understand the container world from the world that they come from, the VM-centric world, and then, you know, it's really interesting to talk to them and show them how we're able to bring those two together and give you, not only bring the container journey up another step, but also carry your VMs along the way as well. >> Chris, Nutanix is at a, the center of several different transitions, right, both old school hardware to kind of hyper converge, but not now also kind of private hybrid-cloud to more kind of multi-cloud, hybrid-cloud. When we're not at DockerCon, so when you're out in the field, how real is multi-cloud, how real is containers in a normal enterprise? >> Definitely, so, multi-cloud is a very hot topic for sure, everyone, there's no company, no IT department that doesn't have some sort of cloud strategy or analyzing it or looking at it. The main way that we get there, or one of the core tools we have is com once again, so, and I'm obviously biased because that's my wheelhouse, right, in marketing, so I talk about that day in day out, but, with com you can add, we support today AHV and EXSi both on and off Nutanix, as well as AWS, AWS gov cloud and GCP, and Azure's coming in down the line that's where Kubernetes will come in as well, so we see a lot of people looking a this and saying hey you know, we do wanna be able to move into AWS, we do wanna be able to move into GCP and use those clouds or unify them together, and some com lets us do that. There's a couple other of prongs to that as well, one of them is Beam, Nutanix Beam, which is a product we announced at DotNext last month, which is around multi-cloud cost optimization, Beam came from an acquisition that of bought metric--the company was called milinjar, I'm probably saying that horribly wrong, but made a product called bought metric which we've rebranded and are integrating into the platform as Nutanix Beam. So what that allows you to do is, you can, it's provided as a SaaS service, so you can go use it today, there's a trial available, all that, you give it AWS credentials and it reaches out and takes a look at your billing account and says hey, we noticed that these VMs are running 50% of the time at no capacity, or they're not being used at all, you can probably cut that down shrink these and save it or hey we noticed that in general you're using this level, this baseline level, you should buy these in reserved instances to save this much per month. And it presents all that up in a really easy to use interface, and then, depending on how you wanna use it, you can even have it automatically go and resize your VMs for you, so it can say, hey you've got a T2 medium or an M2 medium running, it really would make a lot more sense as a you know M2 small. You can, it'll give you the API call, you can go make it on your own, or you can have, if you give crede-- authorization of course, it can go ahead and run that for you and just downsize those and start saving you that money, so that's another fork of that, the multi-cloud strategy. And the last one is one of the other announcements we made around last month which was around--excuse me extract for VMs, so extract is a portfolio of products, we've got extract for DBs where we can scan your sequel databases and move into ESXi or AHV, both from bare metal, or wherever the sequel databases running, extract for VMs allows us to scan the ESXi VMs, and move them over to AHV. And then, we're taking extract for VMs to the next step and being able to scan your AWS VMs and pull them on, back on-prem, if that's what you're looking for as well, so that's right now in beta and they're working on fine tuning that. Because at the end of the day, it's not just enough to view and manage, we really need to get to someplace where we can move workloads between, and put the workload in the right place. Because really with IT, it's always a balance of tools, there's never one golden bullet that solves every problem, every time a new project comes out you're trying to choose the right tool based on the expertise of the team, based on what tools are already in use, based on policy. So, we wanna be able to make sure that we have the tool sets across, that you can choose and change those choices later on, and always use the right thing for the particular application you're running. >> Choice was a big theme this morning during the general session where Docker was talking about choice agility and security. I'm curious with some of the things that were announced, you know they're talking about the only multi-cloud, multi-OS, multi-Linux, they also were talking about, they announced this federated, containerized application management saying hey, containers have always been portable but management hasn't been. I'm curious what your perspectives are on some of the of the evolution that Docker is announcing today, and how will that help Nutanix customers be able to successfully navigate this container journey? >> Definitely. And--(clears throat) you know federation's critical, being able to, container management in general is always a challenge, one of the things that I've heard time and time again is that getting are back to work for Kubernetes has always been very difficult. (laughs) And so, getting that in there, getting, that is such a basic feature that people expect, you're getting the ability to properly federate roles or federate out authentication is huge. There's a reason that SAML took the world by storm, it's that nobody wants to manage passwords, you wanna rely on some external source of truth, being able to pull that in, being able to use some cloud service and have it federated against having Docker federated against other pieces is very important there. I might've gone way off there, but whatever. (laughing) >> No, no, absolutely. >> And then, the other piece of it is that we, with a multi-cloud, with the idea of it doesn't matter whether you're running on-prem or in the cloud or, that is what people need, that's one of the true promises of containers has always been is the portability, so seeing the delivery of that is huge, and being able to provision it on-prem, on Nutanix obviously because that's who I'm here from. (laughing) but, and being able to provision to the cloud and bring those together, that's huge. >> Chris you talked about Kubernetes couple times now, obviously a big topic here, seems to be kind of emerging de facto application deployment configuration for multi-cloud. What's Nutanix doing with Kubernetes? >> Yeah, so I've definitely, Kubernetes is, it's really in many ways winning that particular battle, I mean don't get me wrong Swarm is great, and the other pieces are great, but, Kubernetes is becoming the de facto standard. One of the things we're working on is bringing containers as a service through Kubernetes, natively on Nutanix, to give you an easy way to manage, through Prism manage containers just the way you manage VMs, manage Kubernetes clusters, and you know it's, it's really important that that's, that is just one solution, because we, there's as many different Kubernetes orchestration engines as you can name, every, any name you bring in, so that's my-- >> It's like Linux, back in the day, they're a lot of different distributions or there're a lot of different ways to consume Kubernetes. >> Exactly. And so, we wanna be able to bring a opinionated way of consuming Kubernetes to the platform natively, just as a, so it's a couple of clicks away, it's very easy to do. But that's not the only way that we're doing it, we're also we do have a partnership with Docker where we're doing things like deploying Docker EE through com, or Docker, it's of course all sorts of legalese but, they're working on that so it's natively in everyone's Prism central you can just one click deploy Docker EE, we have a demo running at our booth deploying rancher using com as well, because we wanna be able to provide whatever set of infrastructure makes the most sense for the customer based on, this is what they've used in the past, this is what they're familiar with, or this is what they want. But we also want to offer an opinionated way to deliver containers as a service so that those of you that don't know, or just trying to get started, or that that's what they're looking for, this, when you've got a thousand choices to make everyone's gonna make slightly different ones. So we can't ever offer one, no one can offer the true, this is the only way to do Kubernetes, we need to offer flexibility across as well. >> One of the words we here all the time at trade shows is flexibility. So, love customer stories, as a customer marketing person, I think there's no greater brand validation you can get than the voice of the customer, and I was looking on the Docker website recently and they were saying: customers that migrate to Docker Enterprise Edition, are actually reducing costs by 50%, so, you're a marketing guy, what're some of your favorite examples of customers where Nutanix is really helping them to just kill it on their container journey? >> Yeah, so, there's a, wish I'd thought of this sooner, I shoulda. (laughing) No, but we have a, one of our customers actually, I, this always brings a smile to my face 'cause they they came and saw us last year at the booth, they're one of our existing long time customers, and they're looking to adopt Docker. They came up and we gave 'em a demo, showed them how all the pieces were doing all of the, and he's just looking at it and he's like man, I need this in my life right now, and it was mostly a demo around Docker EE, using the unified control plane, and showing off, using Nutanix drivers showing how we can back up the data and protect individual components of the containers in a very granular fashion. He's like man I need this in my life, this is incredible, and he went and grabbed his friend ran him over, and was like dude we're already using Nutanix look what they can do! And the perfect example of the two kinds of customers, this guy goes like hold on a second, jumps on the command line, like oh yeah I do this all the time from there. (laughing) >> But, that was the, that light up, the light in the eyes of the customer where they were like, this, I need to be able to see this, to be able to use this, and be able to integrate this, that's, I will not forget that anytime soon. That's really why I think we're going down a very good path there, because the ability to, when you have these tinkerers, the people who are really good at code, I mean I spend a lot of time on the command line myself even though I'm in marketing, so, I don't know what I'm doing there, Powerpoints maybe? (laughing) Just because I can understand it from the command line or an expert can understand it, doesn't mean you can share that. I've been tryin' to hand off some of the gear that I manage off to another person, and was like oh you just type out all these commands, and they're like I have no idea what's going on here. (laughing) And so, seeing the customers be able to, to understand what they're more in depth coworkers have done in a gooey fashion, that's just really, that makes a lot of sense to me and it's, I like that a lot. >> It's great. >> Are you seeing any, and the last question is, as we wrap up, some of the, one of the stats actually that was mentioned in the Docker press release this morning about the new announcements was, 85% of enterprise organizations have multi-cloud, and then we were talking with Scott Johnston, their Chief Product Officer, that said, upwards of 90% of IT budgets are spent on keeping the lights on for existing applications, so, there's a lot of need there for enterprises to go this road. I'm wondering, are you seeing at Nutanix, any particular industries that are really leading edge here saying hey we have a lot of money that we're not able to use for innovation, are you seeing that in any specific industries, or is it kinda horizontal? >> I, to be honest, I've seen it kind of horizontally, I mean I've had, I've spoken to many different customers, mostly around com because, but, and they come from all different walks of life. I've seen, I've talked to customers from sled, who've been really excited about their ability to start better doing hadoop, because they do thousands of hadoop clusters a year for their researchers. I've talked to, you know in the cloud or on-prem, or across. I've talked to people in governments, I've talked to people in hospitals and, you know, all sorts of-- >> I can imagine oil and gas, some of those industries that have a ton of data. >> Yeah and it's actually, the oil and gas is really fascinating because a lot of times they, for in a rig, they wanna be able to use compute, but they can't exactly get to a cloud, so how do you, how do you innovate there and on the edge, without, how do you make a change in the core without making it on the edge, and how do you bring those together? So it's, there's really a lot of really fascinating things happening around that, but, I haven't noticed any one industry in particular it's, it's across, it's that everyone is, but then again, by the time they get to me, it's probably self selected. (laughing) But it's across horizontally, is that everyone is looking at how can we use this vast storage, I just found out this is already being used in my environment because it's super easy, how do I, how do I keep a job? (chuckles) Or how do I adopt this and free up my investments in keeping the lights on into innovation, how do I save time, how do I-- Because one of the things that I've noticed with all of this cloud adoption or container adoption all of that is that many times a customer will start making this push, not always from a low level, maybe from a high level, but, they start making this push because they hear it's faster and better and that it'll just solve all their problems if they just start using this. And, because they rush into they don't often they don't solve the fundamental problems that gave 'em the issue to begin with, and so they're just hoping that this new technology fixes it. So, now there's, I am seeing some customers shift back and say hey, I do wanna adopt that, but I need to do it in a smart way, 'cause we just ran to it and that caused us problems. >> Well it sounds like with all the momentum, John, that we've heard in the keynote, the general session this morning, and with some of the guests, you know, I think even Steve Singh was saying only about half of the audience is actually using containers so it's sounds like, with what you're talking about, with what we've heard consistently today, it's sort of the tip of the iceberg, so lots of opportunity. Chris thank you so much for stopping by theCUBE and sharing with us all the exciting things that are going on at Nutanix with containers and more. >> Thank you so much for having me, it was a lot of fun. >> And we wanna thank you for watching theCUBE, Lisa Martin with John Troyer, from DockerCon 2018 stick around we will be right back with our next guest. (bubbly music)

>> Live from San Francisco, it's theCUBE covering DockerCon '18, brought to you by Docker and its ecosystem partners. >> Welcome back to theCUBE, we are live at DockerCon 2018 on a stunning day in San Francisco at Moscone West. I'm Lisa Martin with John Troyer and we're excited to welcome two new folks to theCUBE from Skytap. We've got Lucas Welch, the senior director of communications and Hamish Hill, technical product marketing manager. Hey, guys. >> Great to be here, thanks for having us. >> And thanks for adding a lot of color, Lucas, to our set. >> Well, I just wanted to bring enough flair that you could realize I might have something interesting to say. >> Awesome, so speaking of interesting things, tell us about Skytap, what do you guys do, who are you, where are you based? >> Great, so Skytap. Founded in 2006, so relatively old by start-up standards but it's allowed us to learn a lot about where clouded option has been going. And what we've seen is there really is an overlooked challenge that enterprises are facing today, right? So, cloud native development, growing rapidly, gonna continue to develop, but what do you do with all your old stuff, your existing applications? And so Skytap is a cloud purpose-built for modernizing those traditional applications and we do that through a process we call IPA, although we don't advocate that you drink on the job. It's Infrastructure, Process, and Architecture. And the idea is to really get yourself to true modernization and making the most of cloud, and containers, and all of the modern technologies we can see on the show floor behind us, you first need to modernize the infrastructure, get yourself out of the data center. From there, in eliminating that barrier, you're gonna be able to modernize the processes. How do you develop, how do you change your applications? And by getting better in that regard, adopting things like DevOps and agile methodologies, finally you can start to make changes to the application themselves. So, in short order, we are the cloud for modernizing traditional applications and we like to see ourselves as complementary to the folks at AWS behind us and others who are best for that cloud native web scale development of new applications. >> Great conversation this morning at the Key Note about modernizing applications. I think it's on everybody's mind because the world does not start fresh and new every day, right? We all are working with things that we've been carrying, for some cases, for years and decades. So Docker is talking about, in fact we modernized a .NET application, I think, this morning so they showed a little bit of a demo with that and kubernetes. Can you talk a little bit about how you work with Docker and, you know, some of the challenges that you work with in terms of modernizing applications? >> Yeah, Docker has a great framework with what they have with their MTA. Actually, our VP of Product, Dan Jones, presented yesterday on making modernization magical and really looking at how Skytap complements what Docker has with their MTA framework. And I think Skytap provides, with our IPA approach, a great platform for enterprises to execute the Docker MTA approach and beyond that, sort of what Skytap provides is the abilities, sort of, to move out of the data center and get away from the hardware side of things, and start to leverage some of the scale that you can get out of the cloud. >> What are some of the things that an enterprise, that a legacy application expects that it's not gonna have if you just lift and shift it. You know, why do we need Skytap? >> Yeah, I think what's important to remember is often, even just lifting and shifting it is very difficult because if you want a monolithic or traditional application that's very much wed to the infrastructure it was built on five, 10, 15 years ago, taking that and putting it in a hyper scale provider often means you gotta rewrite from scratch and that's a really arduous process, often one that creates a skills challenge in and of itself because not only do you need people to manage the existing application, you need a whole set of new skills to take a cloud-like approach to that development. So that can create a lot of challenges and so what we see here at DockerCon, really the reason we're here, is both Docker and Skytap see the next wave of cloud, the next wave of modern development, is gonna be, "How do we bring all these benefits we've seen "in Cloud Native development "to those existing applications?" and what we see ourselves doing is eliminating that infrastructure barrier so then you can really start using containers to their full benefit, whether it's in Skytap cloud, in another cloud, or both. >> So, just to follow up a little bit. So it's not just some services like, I don't know, you've gotta have authentication, and you've gotta have storage, and you've gotta have all the things that an old legacy application, sitting in a data center, expects. But it sounds like, also, there's operational services as well and being able to operate with that kind of cloud-level agility? >> Yeah, what we provide with Skytap is, you know, we have a concept of a Skytap environment and so within that environment, you can have your traditional X86, sort of, VMware-based workloads. We also support IBM power systems. So we're the only cloud that can run AIX workloads and Linux on power and so alongside that, what we get is sort of the combination of being able to bring in containers as well and so as organizations go through that modernization journey, being able to receive or see value in the hybrid applications, sort of, along the way. >> We saw a lot of stats, thanks Lucas, this morning I think one of the first ones that I saw was in the press release that Docker released which was, this morning, 85% of enterprise organizations are running a multi-cloud strategy, so that's pretty pervasive. We're also seeing stats like, up to 90%, we had Scott Johnston on earlier, their Chief Product Officer, up to 90% of enterprises are spending, sorry. Enterprises are spending up to 90% of their IT budgets just keeping the lights on for traditional applications. As you said, lift and shift isn't practical for a number of reasons. You also talked about, you know, skill-set changes there. So I'm curious, what are some of the, kind of, common challenges you're seeing in the customer environment where they might be trepidatious to go to the container journey and how specifically does Skytap and Docker knock those out of the park? >> Yeah, well those stats, I think, are really indicative of the challenge and then the new approaches that companies are trying to take to solve that challenge which is, you have so much invested in what's made your company successful, and if you're a long-standing enterprise doing well on your market, you've been doing this for 10, 15, 20, maybe more, years and you've done very well to get yourself to where you are. You've invested millions, if not billions in your infrastructure, your talent, and the people that build the systems that run your business so to burn that all to the ground and start from scratch doesn't make a lot of sense and so, I think, one challenge you run into is inertia, right. It's like "Hey, we did well to get here, "why do we need to suddenly change everything we're doing?" And Skytap's recommendation is you don't need to change everything, but you do need to prepare to be able to change much more rapidly as our economy continues to be more driven by digital technique. So you have inertia as a challenge. I think you also have that idea that if you're spending 90%, as you said, right, of what you just got with the lights on, where's the money and where's the time gonna come for net new and how can you bring those two together? And so that's really where I think Skytap would play a big role is bridging that gap from where you are today, allowing you to leverage the people that you have, the skills that they have, the technology that you have invested in. So you don't have to throw that all out overnight. And instead you can get more and more value out of it as you bring it into the cloud, gain incremental agility, and then, over time, make the modernization and evolutionary changes you want to make based on business needs, not having technology drive what your business does. >> How much of that is a cultural change that you guys can help companies understand is essential? Because culture, change in culture is obviously, especially with large enterprises, they can't pivot that quickly, but culture is essential for a company to successfully undergo digital transformation. I'm just wondering, what kind of conversations are you seeing with that inertia? How much of it is culture needs to change and mindsets to embrace, you know, moving forward? >> Yeah, I mean, we see a lot of this in the conversations we have with customers. We see a lot of it comes out of the market from what analysts sort of have to say as well and I think reasons out of an analyst article that was shared sort of publicly so it talks about, actually, enterprises who have adopted DivOps first are actually more successful in the move to containerization and that's what we see, sort of, with the customers that come to us. And what we're able to provide and what the customers see in Skytap is, actually, the simplicity of the UI that we provide is, actually, a good step from what they currently have without sort of needing to get into what can often be multiple UI's and screens in some of the hyper scale cloud providers. And then on top of that, sort of, the on-demand access to environment so you're taking away, sort of, what is typically a reactive approach from corporate IT when they need to reach out and go, "Hey, I need "another environment or I need another BM like this." And these organizations, it's often taking maybe six to eight weeks to get those environments turned around. We can provision a complex environment in less than, sort of, 30 seconds in Skytap. So it enables those teams to be a lot more productive in what they're doing. And there's sort of the first phase of deciding to sort of adopt the changing culture before sort of even getting into that move from, sort of, after linking in with legacy applications, you've gotta waterfall SDLC, and so actually moving from there into, sort of, more agile approaches and looking at how you can increase release cadence and what, sort of, comes into that from a people aspect, and a process change, and a methodology, and how Skytap, sort of, supports that along with integration with other third party's automation tools as well. >> Yeah, I think you nailed it on the culture point and I just wanted to not forget about people as being a big part of culture, right? And you have, fear is a very real thing, right? Fear of change, fear of net new. And so in our own adoption of Docker, and containers, and kubernetes internally. SO our cloud runs on a very large kubernetes cluster of containerized services so internally, over the last few years, we went through our own modernization journey. And I think that, paired with some research we've seen, we recently did a study with 451 Research looking at what enterprise tech leaders are experiencing. The fear of change, the reticence to change, and then just the lack of knowledge of, "Okay, what is required of me?" Like, "You're asking me to change overnight. "All of a sudden I have to take classes at night "while I do my day job." I think these are really, very realistic and human questions to ask and I think you need to take that into account when you're looking at digital transformation, modernization, so thinking about, "Hey, how do we communicate, "with transparency, what we expect and the time frame?" Let's be upfront about the challenges we expect to run into and where we're gonna have problems and how we'll deal with those together. And make sure the communication is crisp, and clear, and consistent, so that people at least know what's going on, even if they may not like it upfront. >> Well, Lucas, you brought up kubernetes and containers, right? We're here at DockerCon, so, obviously, containers on the tip of everybody's tongue. But you also work with legacy apps, which traditionally, I suppose at this point, traditional means a VM. So how does that go together? What are you looking at your customers? Are they able to transition to more containerized infrastructure? Are they sticking with VMs? I mean, how do modern containers fit into the Skytap platform here? >> Yeah, I think we're seeing a lot of adoption with our customers who are moving into Skytap with their traditional applications and we continue to, sort of, learn and observe what they're doing. For us, there's two types of customers that move to Skytap. The first of those are really looking to migrate their whole data center or evacuate the data centers going, "Where can I put these legacy applications?" You know, there's not many places they can sort of go and so they move them into Skytap, get them up and running in there, and sort of see some benefits in that. And then, almost organically, start to look at going, well how else can I make, or get my team to be sort of more cloud-native or cloud reading. It's sort of an evolution of the people component we were talking about before and sort of going, all right, well as I get my teams more ready for cloud native, they start to sort of move towards containers and cloud native services. For our, sort of, other organizations that come in are those who already know and probably have already experienced, you know, other cloud, sort of, modernizations and are looking at what have they been able to achieve and what do they learn from that. And seen the value in actually Skytap and actually come to us with the approach of going, "Right, we want to come in here. "We want to move to more agile sort of methods. "We want to, sort of, start to take our traditional "monolithic applications, break it down "into into microservices, and move it into containers." >> I'm curious. One of the things that Steve Singh, the CEO of Docker, said this morning during his keynote was, about half the room, there's about five to six thousand people here at DockerCon, their fifth conference, that only about half of them are already on this containerization journey. I'm curious, and I know there's no one-size-fits-all, but when you're talking to customers who are at the preface of going, "All right, we've gotta do this. "This is really an essential component "of our transformation." What's the time frame that they could look to see measurable business impact once they start working with Skytap and Docker on this container journey? >> Yeah, well, I think we've gotta move away collectively as an industry from the idea that there's a Big Bang or silver bullet approach to change, right? I spent the five previous years before joining Skytap last year at a company called Chef Software, competes with Puppet, who's here on the show floor. Automation software. And what I saw there in terms of both DevOps adoption, adoption of automation, and the transition to the cloud, is that if you think you can get everybody full sale on the same amount of change at the same time, to do that effectively in a relatively reasonable amount of time, you're going to not only fail, but by failing, you actually set yourself further back than had you taken a more iterative approach. So I think from a time perspective, I think the first answer is you'll never be done so presume that the journey will continue into perpetuity because continuing to gain agility, continuing to get better at delivering software, to deliver value to customers, I don't see an end to that in any sort of near-term in our economy so I think that's gonna go on for a long time. So digital transformation, modernization, whatever buzz word people may want to use, the idea of evolving and changing is an ongoing process. I think, then, business leaders will say, "Well, that's baloney, I need change now. "I want results." I think, start with a project that has a deadline associated with it, alright? We need to be able to deliver our customer banking app online, via mobile, by January. Okay, well, bite that off singularly and so that you focus on that first, you learn from how you do that process, and then you can take those learnings, communicate them, and pick another project and another project. So we recommend kind of an iterative, progressive approach that will put time and measurable goals around a specific project, meet those deadlines, hopefully, if you're successful, and then give you a lot to learn and operate off of the next time. >> That's great. I'm really kind of curious about looking forward and economic models. You know, everything is as a service at this point. You have a lot of traditional providers, the Dells and HPEs of the world who sell a lot of hardware still and sell a lot of things upfront and they, the analysts and everyone else scratching their heads about how they get to sell more services along with that. Skytap's already there. You're selling your cloud provider, you're selling a service, in some ways you're replacing some of the infrastructure or, you know, an adjunct to it. I'm just kind of curious, going forward, I mean, is this the future of cloud? As a service provider, how do you see the economic model of the DNA of Skytap partnering with people? We've ended up talking about process and people more than we've ended up talking about technology today. Which is kind of fascinating. But is that, project us into the future, what do you all see? >> Yeah, I think what we see today with cloud, and the microservices and container model is really the evolution of what was sort of the virtual data center and developing in sort of VMs. And so sort of going a step beyond that, we're seeing the container model grow and as you rightly pointed out, we talked a lot about people and process and I think that sort of was what's holding back a little of the enterprise adoption today and I think as organizations get into this sort of process and mindset, almost and sort of going, "Hey, things are gonna continue to evolve over time "and our organizations need to be "ready to adopt a lot of these." And this isn't just sort of your development level as well as looking at right, well how does your corporate IT teams, how do your security teams and other parts of the business realize this is gonna continue to evolve really quickly? And I think that's what we're gonna continue to see, sort of up front and it's gonna drive a lot of the adoption of the cloud native services and containers but it's gonna take a bit of time for some organizations to get there. >> Yeah, I have a soapbox, I want to stand on it real quickly. I think cloud is the way forward, right? So no one wants to be in the infrastructure business long-term. So I think regardless of what your deployment model will be, most businesses, five, 10, 15, 20 years from now, I don't see them owning a lot of data center real estate, right? So make the infrastructure someone else's problem. Whether that's Skytap, whether that's AWS, whether that's Azure, or, frankly, whether that's all of us, to your multi-cloud statistic, right? We see the same thing. It's much like the data center was today and has been for a long time. Use the right tool for the right job. You've got a mix of technologies so you're not locked in to any single vendor and you're able to fit technology to your business needs so I think, one, we're going cloud and that's gonna be the way it is. I think, two, is open source, right? I mean, that's where containers gained all their momentum where Docker did a fantastic job of really giving a vibrant community of developers an opportunity to do their work much more easy, much easier and much faster. And so I think you'll continue to see open source play a much larger component in how, even very large, long-standing businesses, develop what they're doing. And then you bring those two together, right? You look at, how can the cloud ecosystem best support open source tools to deliver and develop software that's gonna add value at the end of the day. >> Guys, I wish we had more time. Thank you so much for stopping by and sharing with us what Skytap is doing and how you're enabling customers to not just evolve from a technology standpoint but, I think, as we've all talked about here, really, what might even be more important is evolve the people and the processes. So thanks Lucas, thanks Hamish. Thanks for your time. >> Thank you so much for having us. >> We wanna thank you for watching theCUBE. Again, I'm Lisa Martin with John Troyer from DockerCon 2018. Stick around, we'll be right back with our next guest. (upbeat music)

>> Live from San Francisco, it's theCUBE, covering DockerCon 18, brought to you by Docker and its ecosystem partners. >> Welcome to theCUBE. We are live in San Francisco at DockerCon 2018. I am Lisa Martin with my co-host for the day, John Troyer. John, it is not only a stunning day in San Francisco, beautiful blue skies, this is a packed event. Their fifth DockerCon event and they've got between 5,000 and 6,000 people. We just came from the general session keynote, and it was standing room only as far as the eyes could see. >> Yeah, looks like a good crowd here, a lot of energy. Docker keynotes, always super interesting, they always do a lot of demos, they bring up a lot of employees. It's not just like a parade of middle-aged executives, always is super dynamic, a lot of demos. Really liked the keynote this morning. >> I did too. The energy you mentioned was great. It kicked off with... who's the name of that gentleman that is one of the rally guys for... >> Franco Finn. >> Franco Finn, who has worked for the Warriors, the 2018 Golden State Warriors, NBA Champs. So that was a great way to kick it off, but also Steve Singh had great energy, their CEO, we're gonna have him on shortly today. Scott Johnston, and as you talked about their employees and also customers. They have some really great numbers. They've got, I think, about 120 sessions this year at DockerCon. Nine big enterprise customers talking about how they are approaching containerization with DockerCon. One of them was McKesson, which is a 183 year old company with a lot of staff that gave a really compelling keynote or a, yeah, a keynote this morning about how they are moving and modernizing their data center with Docker. >> A really nice story, a really an emphasis on trust, an emphasis on developer usability, and I liked one of the points was, once we got the developers using it it became easier, and I think using the whole platform. Lisa, I think they hit a lot of familiar things for Docker: so, developer experience, really big for Docker. That's they way they started, that's what they're still counting on. When Steve Singh got up, he talked about community, their very first thing. Over half the people here, first time at DockerCon and over half of the folks are just using containers in the late last year. That means this whole journey is just starting. There's a lot of white space in the container world. So developer experience, a big announcement, preview announcement for Docker Desktop, being able to create apps off of templates and things like that but very developer-focused shows as opposed to some of the more IT-focused. There's a broad mix here but definitely a lot of developers here at the show. >> A lot of developers, as you said, but also, you're right, it is a mix. It's IT professionals, it's enterprise architects, and it's executives and that's one of the... one of the targeted audiences that, I think, both Steve Singh and Scott Johnston talked about, so it'll be great to explore. As the CEO and the Chief Product Officer respectfully, what are they hearing from enterprise customers who have a lot of challenges with legacy applications that are very difficult to manage and I also read some stats, they had some stats in the press release this morning, but 80% of enterprise IT budgets are spent keeping the lights on for enterprise apps which leaves about 20% for innovation and of course, as we know, organizations that can aggressively innovate are the ones that win. So I'm not only looking forward to hearing with Docker Desktop, what they're doing to make it easy, easier, for developers to get in there and play around on both on Mac and Windows but also the executive conversation. What are they hearing from the executives and where is containerization, you know, from the c-sweep to the board room. >> Yeah, modernizing enterprise apps also has been a Docker theme for the last few years. Microsoft, the big guest up on stage, they've been a multi-year partnership with Microsoft and Docker, putting Docker with Windows together. The big announcement today, pre-technology preview of Kubernetes and Windows Server and the big demo was, they took a very old .net application and, you know, put it up on Kubernetes on Windows with just a couple of clicks. So again, I think that message to the executives is, "You're very safe in Docker's hands "We've got the developer experience covered, "we've got the partnerships." And then going big on Windows, I think choice was another theme that I heard ... >> Yes, it was. Steve talked a lot about choice. >> Um, to the execs here as well, both GUI and CLI, right? A lot of the cloud is very CLI-focused, very Linux-focused. Docker says "We're in on Windows, we support Windows "just as well as Linux so don't hate on the GUI. "You can use a GUI or you can use a CLI." No religion actually too, in terms of Linux versus Windows but Kubernetes, I thought, was a very big. Got mentioned a lot in the keynote this morning, Lisa. >> It did and you talked about choice. One of the things that Steve Singh mentioned from an executive's perspective is, three things that Docker is aiming to deliver. That sounds to me, as a marketer, like competitive differentiation. Talked about choice so that organizations can run apps wherever it makes sense for them, managing applications on any infrastructure, and, as you said earlier, about a few clips, managing their container infrastructures across multiple clouds in just a few clicks. They also talked about being, they also talked a number of times, not just in the press release but also this morning in the keynote, about no vendor lock-in. John, we hear that a lot, it sounds like a marketing term. What are you expecting to hear? What does that mean for Docker? >> I'm not so sure that lock-in is always important for every enterprise, in that any choice you make, it has a certain element of lock-in but it's an active argument or debate online that I see a lot. "Are you locked in when you go to a certain cloud? "Are you locked in when you choose a certain provider," whether it's open-sourced or not. Certainly a lot of Docker is open source. A lot of your choices are protected and they are really trying to say "We're going to be a platform that's going to "service a lot of different abilities to deploy." The big announcement that finished off the keynote was Docker Enterprise Edition can now manage Kubernetes. Not only Kubernetes in the cloud. Kubernetes on Prim, Kubernetes in the cloud managed by Docker, but can actually work with the native Kubernetes cluster managers of the clouds, of the three major clouds: Google GKE, Azure AKS, and AWS EKS. I think I got all those names right. But that's big because a lot of folks say "run anywhere" but they mean "run within our environment anywhere" and what Docker has done in Tech Preview is to connect its platform with the native platforms, orchestration platforms, of the three different clouds so that you can run on Prim, manage via Docker, or you can connect into the cloud's own cluster orchestration. And if they can deliver on that, the devil is in the details, but if they can deliver on that, that's actually a very nice feature to avoid that sort of lock-in. >> And that also goes to, John, one of the major things which is agility and one of the things that they've talked about is, containers today are portable but one of the challenges is that management of containers has not been portable. I think they said that 85% approximately of enterprise I.T. organizations that they has surveyed are running a multi-cloud strategy so they've gotta be able to really deliver this single pane of glass management so they talked about federated application or federated management of containerized applications. I think that's kind of what you're referring to in terms of getting away from the silos and enabling organizations to have that portability and especially as multi-national organizations need to have different access, different security, policies may be maintained across multiple locations. >> Indeed, right. These are global organizations that are betting on container technology. They do need access to be running apps, either parts of apps or services on different clouds. You might be running a Google cloud in Europe, you might be running an AWS here or vice versa. You might have some on-Prim stuff. We've seen a lot of that. I think another theme that we'll hit on, Lisa, along with that multi-cloud portfolio aspect, is the time to value. It's been a theme of this conference season. This last month or two, you and I have both been at a lot of different conference centers and I think time to value, being able to spin up apps within weeks or months that actually work and have value versus the old way, which was years and I think the theme for 2018 is that it's real. People are actually doing it and we'll talk to a couple of customers, I hope, today. >> And that's essential because enterprises, while there's still trepidation with moving into the container journey, they don't really have a choice to be able to aggressively innovate to be able to be leaders and compete with these cloud-native organizations. They don't have the luxury of time to rip and replace old enterprise applications and put them on a container or a micro-service's space archicture, they've got to be able to leverage something like containers to maximize time to value to deliver differentiating services. >> Absolutely. I'm very interested in being here today and we'll see what the day brings us. >> I think we're gonna have a lot of fun today, John. I think they kicked off things with great energy. I loved how, you know, they always do demos, right, on main stage during general sessions, and we were at SAP last week and of course, one of the demos didn't work. That's just the nature of trying to do things live. I liked how they were very cheeky with the praying to the demo Gods with the fortune cookies. I thought that was really good but the demos were simple. They were very clearly presented and I'm excited with you to dig in to what are they doing. Also what is setting them apart and how are they enabling enterprise organizations like MetLife, like McKesson, PayPal, Splunk to be able to transform to compete. >> Absolutely. One last thing about the conference, Lisa, is I do want to call out. It's a very humane conference. Not only do they have kind of a cheeky sense of humor here at Docker, but there's child care onsite, and there's spouse-tivities, there are activities for if you bring your spouse or family to the conference. They're trying to do a lot of things to make the conference experience good and successful and friendly and humane for people here at the show which I really appreciate. >> I like that, humane conference. You're right. We don't always see that. Well, John and I are going to be here all day talking with Docker executives, customers, partners and we're excited to have you with us. Lisa Martin for John Troyer. You're watching theCUBE at DockerCon 2018. We'll be right back with our first guest. (techno music)