(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)

>> Male narrator: From around the globe, it's the CUBE with digital coverage of DockerCon Live 2020 brought to you by Docker and its ecosystem partners. >> Hey, welcome back everyone to the DockerCon Virtual Conference. DockerCon 20 being held digitally online is the CUBE's coverage. I'm John for your host of the CUBE. This is the CUBE virtual CUBE digital. We're getting all the remote interviews. We're here in our Palo Alto studio, quarantined crew, all getting the data for you. Got Peter Guangeti who's the Chief Marketing Officer Cockroach Labs, a company that we became familiar with last year. They had the first multicloud event in the history of the industry last year, notable milestone. Hey first, it's always good you're still around. So first you got the first position, Peter. Great to see you. Thanks for coming on the CUBE for DockerCon 20. >> Thank you, John. Thanks for having me. >> So it's kind of interesting, I mentioned that tidbit to give you a little bit of love on the fact that you guys ran or were a part of the first multicloud conference in the industry. Okay, now that's all everyone's talking about. You guys saw this early. Take a minute to explain Cockroach Labs. Why you saw this trend? Why you guys took the initiative and took the risk to have the first ever multicloud conference last year? >> So that's news to me that we were the first, actually. That's a bit of a surprise, cause for us we see multicloud and hybrid cloud as the obvious. I think the credit really for this belongs with folks like Gartner and others who took the time to listen to their customer, right? Took the time to understand what was the need in the market, which, you know, what I hear when I talk to CEOs is cloud is a capability, not a place, right? They're looking at us and saying, "yes, I have a go to cloud strategy, "but I also have made massive investments in my data center. "I believe I don't want to be locked in yet again "to another vendor with proprietary PIs, "proprietary systems, et cetera." So, what I hear when I talk to customers is, "I want to be multicloud show me how, "show me how to do that in a way "that isn't just buying from multiple vendors, right?" Where I've cost arbitrage, show me a way where I actually use the infrastructure in a creative way. And that really resonates with us. And it resonates with us for a few reasons. First is, we built a distributed SQL database for a reason, right? We believed that what you really need in the modern age for global applications is something that is truly diverse and distributed, right? You can have a database that behaves like a single database that lives in multiple locations around the world. But then you also have things like data locality. It's okay with German data stays in Germany because of German law. But when I write my application, I never write each of these things differently. Now, the other reason is, customers are coming to us and saying, "I want a single database that I can deploy "in any of the cloud providers." Azure SQL, and that is a phenomenal product. Google Spanner is a phenomenal product. But once I do that, I'm locked in. Then all I have is theirs. But if I'm a large global auto manufacturer, or if I'm a startup, that's trying to enter multiple markets at the same time. I don't want that. I want to be able to pick my infrastructure and deploy where I want, how I want. And increasingly, we talk to the large banks and they're saying, "I spent tens or even hundreds of millions of dollars "on data centers. "I don't want to throw them out. "I just want better utilization. "And the 15 to 20% that I get "from deploying software on bare metal, right? "I want to be able to containerize. "I want to be able to cloudify my data center "and then have ultimately what we see more and more "as what they call a tripod strategy "where your own data center and two cloud providers "behaving as a single unit "for your most important applications." >> That's awesome. I want to thank you for coming on to, for DockerCon 20, because this is an interesting time where developers are going to be called to the table in a very aggressive way because of COVID-19 crisis is going to accelerate until they pull the future forward ahead of most people thought. I mean, we, in the industry, we are inside the ropes, if you will. So we've been talking about stainless applications, stateful databases, and all the architectural things that's got that longer horizon. But this is an interesting time because now companies are realizing from whether it's the shelter in place at scale problems that emerge to the fact that I got to have high availability at a whole nother level. This kind of exposes a major challenge and a major opportunity. We're expecting projects to be funded, some not to be funded, things to move around. I think it's going to really change the conversation as developers get called in and saying, "I really got to look at my resources at scale. "The database is a critical one because you want data "to be part of that, this data plane, if you will, "across clouds." What's your reaction to this? Do you agree with that, the future has been pulled forward? And what's Cockroach doing to help developers do manage this? >> Yeah, John, I think you're exactly right. And I think that is a story that I'm glad that you're telling. Because, I think there's a lot of signal that's happening right now. But we're not really thinking about what the implications are. And we're seeing something that's I think quite remarkable. We're seeing within our existing customer base and the people we've been talking to, feast or famine. And in some cases, feast and famine in the same company. And what does that really mean? We've looked at these graphs for what's going to happen, for example, with online delivery services. And we've seen the growth rates and this is why they're all so valued. Why Uber invested so big in Uber eats and these other vendors. And we've seen these growth rates the same, and this is going to be amazing in the next 10 years, we're going to have this adoption. That five, 10 years happened overnight, right? We were so desperate to hold onto the things that are what mattered to us. And the things that make us happy on any given day. We're seeing that acceleration, like you said. It's all of that, the future got pulled forward, like you had said. >> Yeah. >> That's remarkable, but were you prepared for it? Many people were absolutely not prepared for it, right? They were on a steady state growth plan. And we have been very lucky because we built an architecture that is truly distributed and dynamic. So, scaling and adding more resilience to a database is something we all learned to do over the last 20 years, as data intensive applications matter. But with a distributed SQL and things like containerization on the stateless side, we know we can just truly elastically scale, right? You need more support for the application of something like Cockroach. You literally just add more nodes and we absorb it, right? Just like we did with containerization, where you need more concurrency, you just add more containers. And thank goodness, right, because I think those who were prepared for those things need to be worked with one of the large delivery services. Overnight, they saw a jump to what was their peak day at any point in time now happening every single day. And they were prepared for that because they already made these architectural decisions. >> Yeah. >> But if you weren't in that position, if you were still on legacy infrastructure, you were still trying to do this stuff manually, or you're manually sharding databases and having to increase the compute on your model, you are in trouble and you're feeling it. >> That's interesting Peter to bring that up and reminds me of the time, if you go back in history a little bit, just not too far back, I mean, I'm old enough to go back to the 80s, I remember all the different inflection points. And they all had their key characteristics as a computer revolution, TCP IP, and you pick your spots, there's always been that demarcation point or lions in where things change. But let's go back to around 2004 and then 2008. During that time, those legacy players out there kind of was sitting around, sleeping at the switch and incomes, open-source, incomes, Facebook, incomes, roll your own. Hey, I'm going to just run. I'm going to run open-source. I'm going to build my own database. And that was because there was nothing in the market. And most companies were buying from general purpose vendors because they didn't have to do all the due diligence. But the tech-savvy folks could build their own and scale. And that changed the game that became the hyperscale and the rest is history. Fast forward to today, because what you're getting at is, this new inflection point. There's going to be another tipping point of trajectory of knowledge, skill that's completely different than what we saw just a year ago. What's your reaction to that? >> I think you're exactly right. We saw and I've been lucky enough, same like you, I've been involved in the web since the very early days. I started my career at the beginning. And what we saw with web 1.0 and the shift to web 2.0, web 2.0 would not have happened without source. And I don't think we give them enough credit if it wasn't for the lamp stack, if it wasn't for Linux, if it wasn't for this wave of innovation and it wasn't even necessarily about rolling around. Yeah, the physics of the world to go hire their own engineers, to go and improve my SQL to make it scale. That was of course a possibility. But the democratization of that software is where all of the success really came from. And I lived on both sides of it in my career, as both an app developer and then as a software executive. In that window and got to see it from both sides and see the benefit. I think what we're entering now is yet another inflection point, like you said. We were already working at it. I think, the move from traditional applications with simple logic and simple rules to now highly data intensive applications, where data is driving the experience, models are driving the experience. I think we were already at a point where ML and AI and data intensive decision-making was going to make us rewrite every application we had and not needed a new infrastructure. But I think this is going to really force the issue. And it's going to force the issue at two levels. First is the people who are already innovating in each of these industries and categories, were already doing this. They were already cloud native. They were already built on top of very modern third generation databases, third generation programming languages, doing really interesting things with machine learning. So they were already out innovating, but now they have a bigger audience, right? And if you're a traditional and all of a sudden your business is under duress because substantial changes in what is happening in the market. Retailers still had strength with footprint as of last year, right? We don't be thinking about e-commerce versus traditional retail. Yeah, it was on a slow decline. There were lots of problems, but there was still a strength there, that happened changed overnight. Right now, that new sources have dried up, so what are you going to do? And how are you going to act? If you've built your entire business, for example, on legacy databases from folks like Oracle and old monolithic ways of building out patients, you're simply not adaptable enough to move with changing times. You're going to have to start, we used to talk about every company needed to become a software company. That mostly happened, but they weren't all very good software companies. I would argue that the next generation used to to be a great software company and great data scientists. We'll look at the software companies that have risen to prominence in the last five to 10 years. Folks like Facebook, folks like Google, folks like Uber, folks like Netflix, they use data better than anyone else in their category. So they have this amazing app experience and leverage data and innovate in such a way that allow them to just dominate their category. And I think that is going to be the change we see over the next 10 years. And we'll see who exits what is obviously going to be a jail term. We'll see who exits on top. >> Well, it's interesting to have you on. I love the perspective and the insights. I think that's great for the folks out there who haven't seen those ways before. Again, this wave is coming. Let's go back to the top when we were talking about what's in it for the developer. Because I believe there's going to be not a renaissance, cause it's always been great, but the developers even more are going to be called to the front lines for solutions. I mean, these are first-generation skill problems that are going to be in this whole next generation, modern era. That's upon us. What are some of the things that's going to be that lamp stack, like experience? What are some of the things that you see cause you guys are kind of at a tail sign, in my opinion, Cockroach, because you're thinking about things in a different construct. You're thinking about multicloud. You're thinking about state, which is a database challenge. Stateless has kind of been around restful API, stateless data service measures. Kubernetes is also showing a cloud native and the microservices or service orientation is the future. There's no debate on that. I think that's done. Okay, so now I'm a developer. What the hell am I going to be dealing with for the next five years? What's your thoughts? >> Well, I think the developer knows what they're already facing from an app perspective. I think you see the rapid evolution in languages, and then, in deployment and all of those things are super obvious. You need just need to go and say I'm sure that all the DockerCon sessions to see what the change to deployment looks like. I think there are a few other key trends that developers should start paying attention to, they are really critical. The first one, and only loosely related to us, is ML apps, right? I think just like we saw with dev and ops, suddenly come together so we can actually develop and deploy in a super fast iterative manner. The same things now are going to start happening with data and all of the work that we do around deploying models. And I think that that's going to be a pretty massive change. You think about the rise of tools like TensorFlow, some of the developments that have happened inside of the cloud providers. I think you're seeing a lot there as a developer, you have to start thinking as much like a data scientist and a data engineer as simply somebody writing front end code, right? And I think that's a critical skill that the best developers already building will continue. I think then the data layer has become as important or more important than any other layer in the stack because of this. And you think about once again, how the leaders are using data and the interesting things that they're doing, the tools you use matter, right? If you are spending a lot of your time trying to figure out how to shard something how to make it scale, how to make it durable when instead you should be focused on just the pure capability, that's a ridiculous use of your time, right? That is not a good use of your time. We're still using 20 to 25 year old open-source databases for many of these applications when they gave up their value probably 10 years ago. Honestly, you know, we keep all paper over it, but it's not a great solution. And unfortunately, no SQL will fix some of the issues with scaling elasticity, it's like you and I starting a business and saying, "okay, everyone speaks English, "but because we're global, "everyone's going to learn Esperanto, right?" That doesn't work, right? So works for a developer. But if you're trying to do something where everyone can interact, this is why this entire new third generation of new SQL databases have risen. We took the distributed architecture SQL. >> Hold up for a second. Can you explain what that means? Cause I think a key topic. I want to just call that out. What is this third generation database mean? Sorry, I speak about it. Like everyone sees it. >> I think it's super important. It's just a highlight. Just take a minute to explain it and we can get into it. There is an entire new wave of database infrastructure that has risen in the last five years. And it started actually with Google. So it started with Google Spanner. So Google was the first to face most of these problems, right? They were the first to face web scale. At least at the scale, we now know it. They were the first to really understand the complexity of working with data. They have their own no SQL. They have their own way of doing things internally and they realized it wasn't working. And what they really needed was a relational database that spoke traditional ANSI SQL, but scaled, like there are no SQL counterparts. And there was a white paper that was released. That was the birth of Spanner. Spanner was an internal product for many, many years. They released the thinking into the wild and then they just started this way with innovation. That's where our company came from. And there were others like us who said, "you're right. "Let's go build something that behaves," like we expect a database to behave with structure and this relational model and like anyone can write simple to use it. It's the simplest API for most people with data, but it behaves like all the best distributed software that we've been using. And so that's how we were born. Our company was founded by ex Googlers who had lived in this space and decided to go and scratch the itch, right? And instead of doing a product that would be locked into a single cloud provider, a database that could be open-source, it could be deployed anywhere. It could cross actual power providers without hiccups and that's been the movement. And it's not just us, there were other vendors in this space and we're all focused on really trying to take the best of the both worlds that came before us. The traditional relational structure, the consistency and asset compliance that we all loved from tools like Oracle, right? And Microsoft who we really enjoyed. But then the developer friendly nature and the simple elastic scalability of distributed software and, that's what we're all seeing. Our company, for example, has only been selling a product for the last two years. We found it five years ago, it took us three years just to rank in the software that we would be happy selling to a customer. We're on what we believe is probably a 10 to 15 year product journey to really go and replace things like Oracle. But we started selling the product two years ago and there is 300% growth year over year. We're probably one of the fastest growing software companies in America, right? And it's all because of the latent demand for this kind of a tool. >> Yeah, that's a great point. I'm a big fan of this third wave. Can I see it? If you look at just the macro tailwinds in the industry, billions of edged devices, immersion of all kinds of software. So that means you can't have one database. I always said to someone, in (mumbles) and others. You can't have one database. It's physically impossible. You need data and whatever database fits the scene, wherever you want to have data being stored, but you got to have it real time. You got to have actionable, you have to have software intelligence into how to manage the data. So I think the data control plane or that layer, I think it's the next interoperability wave. Because without data, nothing really works. Machine learning doesn't really work well. You want the most data. I think cybersecurity is a great early use case because they have to leverage data fast. And so you start to see some interesting financial services, cyber, what's your thoughts on this? Can you share from the Cockroach Labs perspective, from your database, you've got a cloud. What are some of the adoption use cases? Who are those leaders? You can name names if you have them, if not, name the use case. What's the Cockroach approach? Who's winning with it? What's it look like? >> Yeah, that's a great question. And you nailed it, right? The data volumes are so large and they're so globally distributed. And then when you start layering again, the data streaming in from devices that then have to be weighed against all of these things. You want a single database. But you need one that will behave in a way that's going to support all of that and actually is going to live at the edge like you're saying. And that's where we have been shining. And so our use cases are, and unfortunate, I can't name any names, but, for example, in retail. We're seeing retailers who have that elasticity and that skill challenge with commerce. And what they're using us for is then, we're in all of the locations where they do business, right? And so we're able to have data locality associated with the businesses and the purchases in those countries. And however, only have single apps that actually bridge across all of those environments. And with the distributed nature, we were able to scale up and scale down truly elastically, right? Because we spread out the data across the nodes automatically. And, what we see there is, you know, retailers do you have up and down moments? Can you talk about people who can leverage the financial structure of the cloud in a really thoughtful way? Retail is a shining example of that. I remember having customers that had 64 times the amount of traffic on cyber Monday that they had on the average day. In the old data center world, that's what you bought for. That was horrendous. In a cloud environment, still horrendous, even public cloud providers. If you're having to go and change your app to ramp every time, that's a problem with something like a distributed database. and with containerization, you could scale much more quickly and scale down much more. That's a big one for streaming media, is another one. Same thing with data locality in each of these countries, you think about it, somebody like Netflix or Hulu, right? They have shows that are unique to specific countries, right? They haven't have that user behavior, all that user data. You know data sovereignty, you know, what you watch on Netflix, there's some very rich personal data. And we all know how that metadata has been used against people. Or so it's no surprise that you now have countries that I know there's going to be regulation around where that data can live and how it can. And so once again, something like Cockroach where you can have that global distribution, but take a locality, or we can lock data to certain nodes in certain locations. That's a big one. >> There's no doubt in my mind. I think there's such a big topic. We probably do more interviews just on the COVID-19 data problem that they have. The impact of getting this right, is a nerd problem today. But it is a technology solution for society globally in the future. Zero doubt in my mind on that. So, Peter, I want you to get the last word and to give a plugin to the developers that are watching out there about Cockroach. Why should they engage with you guys? What can you offer? Is there anything new you want to share about the company to the audience here at DockerCon 2020? Take us home in the next segment. >> Thank you, John. I'll keep the sales pitch to a minimum. I'm a former developer myself. I don't like being sold, so I appreciate it. But we believe we're building, what is the right database for the coming wave of cognitive applications. And specifically we've built what we believe is the ideal database for distributed applications and for containerized applications. So I would strongly encourage you to try it. It is open-source. It is truly cloud native. We have free education, so you can try it yourself. And once you get into it, it is traditional SQL that behaves like Postgres and other tools that you've already known of. And so it should be very familiar, you know, if you've come up through any of these other spaces will be very natural. Postgres compatible integrates with a number of ORM. So as a developer, just plugged right into the tools you use and we're on a rapid journey. We believe we can replace that first generation of technology built by the Oracles of the world. And we're committed to doing it. We're committed to spending the next five to 10 years in hard engineering to build that most powerful database to solve this problem. >> Well, thanks for coming on, sharing your awesome insight and historical perspective. get it out of experience. We believe and we want to share the audience in this time of crisis, more than ever to focus on critical nature of operations, because coming out of this, it is going to be a whole new reality. And I think the best tech will win the day and people will be building new things to grow, whether it's for profit or for societal benefit. The impact of what we do in the next year or two will determine a big trajectory and new technology, new approaches that are dealing with the realities of infrastructure, scale, working at home , sheltering in place to coming back to the hybrid world. We're coming virtualized, Peter. We've been virtualized, the media, the lifestyle, not just virtualization in the networking sense, but, fun times it was going to be challenging. So thanks for coming on. >> Thank you very much, John. >> Okay, we're here for DockerCon 20 virtual conferences, the CUBE Virtual Segment. I want to thank you for watching. Stay with me. We've got stream all day today and check out the sessions. Jump in, it's going to be on demand. There's a lot of videos it's going to live on and thanks for watching and stay with us for more coverage and analysis. Here at DockerCon 20, I'm John Furrier. Thanks for watching >> Narrator: From the CUBE studios in Palo Alto in Boston, connecting with thought leaders all around the world. This is the CUBE conversation.

>> 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)